Failed to register as versioned

8511
12
Jump to solution
02-10-2015 09:13 AM
ChrisGoessl
New Contributor III

Here is my issue. I created a checked out replica feature class (StreetSigns), was able to syncronize the data back to the SDE with reconcile and post information checked. The process was completed and closed down. I deleted the replicated feature class.

 

Now I am getting this error.

"Failed to register as versioned. Operation not supported on a table that is moving edits to base."

 

This error is coming when I am creating a version for a feature class that is located in the same dataset as the StreetSigns. I have stopped all services thinking that it might be a schema lock, but I still get the same error message.

 

Also, the StreetSigns feature class had a representation for symbology and now over half of the symbols are missing.

 

I have checked all versions and ensured that all have been reconciled and posted. No issues with any of the versions.

 

I am in need of some guidence

Tags (2)
1 Solution

Accepted Solutions
ChrisGoessl
New Contributor III

I had to remove all of the FC that were not versioned. Unversioned the Feature Set, copied the FC's back into the Feature Set, and than versioned without the edits to base.

Thanks for everyone's assistance.

Chris

View solution in original post

12 Replies
JakeSkinner
Esri Esteemed Contributor

Hi Chris,

It looks like the feature dataset was registered as versioned with the option to move edits to base.  If this is not required, you can perform the following steps:

1.  Reconcile/post all versions

2.  Perform compress

3.  Unregister feature dataset as versioned

4.  Re-register feature dataset as versioned w/o the option to move edits to base

0 Kudos
ChrisGoessl
New Contributor III

Jake,

Thanks for the suggestion.

I performed the Reconcile and Post all versions.

I performed a compress of the database

I do not have the option to Unregister the feature dataset.

I click the register as versioned and I still get the same error.

0 Kudos
AsrujitSengupta
Regular Contributor III

R-Click on each feature class present in that feature dataset>Properties>General Tab> check whether any of them is Registered as Versioned with Edits moving to Base

0 Kudos
ChrisGoessl
New Contributor III

It appears that the majority of the feature classes are "Registered as Versioned with Edits moving to Base" (106 feature calsses)

There are a couple (five) that are not versioned at all.

0 Kudos
AsrujitSengupta
Regular Contributor III

Yes, this seems to be occurring because of that then. Because of those 5 FCs, the Unregister option is greyed out.

If this is feasible, copy those 5 FCs out from that dataset to a File gdb>delete those 5 FCs from the dataset> Now the option to Unregister should be available> Unregister as Versioned> Add those 5 FCs back into the dataset> Register as Versioned.

OR

Copy the entire Feature Dataset to a File gdb> Delete the dataset from the sde gdb> Copy\Paste it back from the File gdb.

Note: Make sure you have a database backup before trying these.

ChrisGoessl
New Contributor III

I had to remove all of the FC that were not versioned. Unversioned the Feature Set, copied the FC's back into the Feature Set, and than versioned without the edits to base.

Thanks for everyone's assistance.

Chris

GailJorgenson
New Contributor III

Thanks for this post.  I was having the same problem and the instructions helped me to resolve the issue with my gdb.

Gail

0 Kudos
DanaNolan
Regular Contributor

I get this error whenever a new table (unversioned) is added, usually feature-linked annotation file since I don't think about registering those. I have been able to solve this by doing an Analyze on the new table, Create Versioned View, and Register as Versioned. This often requires closing ArcCatalog and re-opening to get the Register as Versioned to ungray. Honestly, I am not sure that the order matters or that it works the same way every time.

If there is a nonspatial table involved in a relationship to your feature class, this also needs the same handling. Thanks to ESRI SDE support from last year's UC, I was able to find the offending table and make our features editable again.

0 Kudos
GailJorgenson
New Contributor III

Thanks, Dana.

I am wondering when you are analyzing the new table & creating the versioned view...are you using a tool for this?  And, is the table in your gdb when you are using the tool or is it just a file outside the gdb?

Gail

0 Kudos