Select to view content in your preferred language

10.1 Losing Data when Stopping Edit Session

641
3
08-10-2012 07:54 AM
KevinNelson
Deactivated User
I just upgraded from 10.0 to 10.1 yesterday and it's been giving me some problems.

I tried merging several polygons located in a file geodatabase(created in 10). They saved fine but when I ended the editing session they all disappeared. I also had the same problem when copying and pasting polygons from one shapefile into one located in a file geodatabase.

When I tried importing a polygon shapefile into a file geodatabase it also failed, giving me the folowing warninig:

WARNING 000117: Warning empty output generated.

I've also tried creating a new file geodatabase. When I try to create a Feature Dataset within it, it fails giving me the following message.

Failed to create the feature dataset
The item was not found. [ItemType: {74737149-DCB5-4257-8904-B9724E32A530}]

Has anyone experienced similar issues? Any help/suggestions would be much appreciated.

Thanks,
Kevin
Tags (2)
0 Kudos
3 Replies
stevecater
Deactivated User
Did you ever figure out what caused that error?
0 Kudos
KevinNelson
Deactivated User
I haven't found a solution yet. Sorry
0 Kudos
BonnieWeller
Occasional Contributor
I had something similar happen to me when editing a feature dataset. I finally figured out that if you import a feature class into the feature dataset while you are editing and do NOT save your edits, all the data in the imported feature dataset gets blown away. If you save your edits, then this does not happen. If no edits are made and you exit the editing session (thus do not get prompted to save your edits) the imported feature class attribute data goes bye-bye.

I was in and out of editing sessions so often that I did not pay attention to whether I was in an editing session when I imported a new feature class into the dataset. I was messing around with topolgy rules, adding data as I went along. Mainly my error, but ESRI programing rules should not allow you to be able to add features to a dataset during an edit session when this type of thing can happen. Thank goodness I work on copies and not the original data.

Not sure this fits your situation but I came across this when searching for why my data was getting blown away and finally did my own troubleshooting based upon a momentary epiphany. If not you, then perhaps someone else will benefit from my post.
0 Kudos