topic Re: Unregistering as versioned corrupted Feature Class. help. in Geodatabase Questions

Unregistering as versioned corrupted Feature Class. help.

JerryGarcia — Fri, 09 Nov 2018 01:35:34 GMT

Two feature classes apparently were corrupted when I 'unregistred as versioned'.

I cannot open, delete, or change the name of the feature classes. This creates a huge problem since code is dependent on the name. Super frustrating...

See attached picture with error message:

Open Failed

Error opening feature class.

The item does not have a definition.

The XML being loaded could not be parsed. [physical name: GIS.DATACREATOR.COUNTIES]

XML Parsing failed.

Reason:An invalid character was found in text content.

------------

At the very least, I'd like to remove (delete) the feature class so I can rebuild it...

Any assistance is very much appreciated!

GDB stored in SQL Server. ArcGIS 10.5.1.

Re: Unregistering as versioned corrupted Feature Class. help.

BillFox — Fri, 09 Nov 2018 01:48:21 GMT

try the metadata view & repair tools

Re: Unregistering as versioned corrupted Feature Class. help.

BillFox — Fri, 09 Nov 2018 01:50:14 GMT

Repair Version Metadata—Help | ArcGIS Desktop

Re: Unregistering as versioned corrupted Feature Class. help.

JerryGarcia — Fri, 09 Nov 2018 20:37:38 GMT

Thanks for the suggestion. But, this did not resolve the issue. The repair tool did not find any problems.

Any more suggestions would be appreciated. This is a major headache. Thanks!

Re: Unregistering as versioned corrupted Feature Class. help.

George_Thompson — Mon, 12 Nov 2018 12:44:09 GMT

I would suggest contacting Esri Technical Support and working with an analyst on this one. It seems that a backup may need to be taken and provided for them to review.

Re: Unregistering as versioned corrupted Feature Class. help.

JerryGarcia — Mon, 12 Nov 2018 13:42:52 GMT

Thanks for the feedback. Working with Esri tech support would take forever. I don't have time for that. I took a back-up of database and will attempt to remove all artifacts for the corrupt feature class via SQL Server Management Studio. Thanks!

Re: Unregistering as versioned corrupted Feature Class. help.

George_Thompson — Mon, 12 Nov 2018 14:01:29 GMT

I can respect the time perspective but would highly recommend it. There may be another reason that the FC did not get unregistered correctly.

You can do it manually, but I would not recommend it due to all the dependencies that are within the Geodatabase.

Re: Unregistering as versioned corrupted Feature Class. help.

EdwardBlair — Sun, 28 Jun 2020 18:18:09 GMT

I've run into the same issue in a SQL*Server instance running ArcGIS 10.6.1. Did you ever find a resolution? Any info would be greatly appreciated.

Thx,

Re: Unregistering as versioned corrupted Feature Class. help.

EdwardBlair — Sun, 28 Jun 2020 18:34:59 GMT

Kind of interesting. As look at the GDB_ITEMS table in SQL*Server Management studio the row for my problem feature class does indeed have a NULL Definition field. Not sure how that could happen - I've never touched the database outside ArcGIS -- though I've been using ArcPython to update class properties (i.e., add fields, domains, etc.)

Wonder if I could copy a Definition field from another class into my null field... which might allow me to delete the class.

Re: Unregistering as versioned corrupted Feature Class. help.

ColinWerle1 — Mon, 29 Jun 2020 16:34:49 GMT

It is typically not recommended to manually edit the geodatabase items through the backend because it can lead to unexpected behaviors. In this circumstance restoring a database backup is likely the safest solution. If you restore the database to the condition prior to unregistering as versioned, do you see the Definition field populated?

It may be a good idea to do a clean export and re-import of the data from that backup. When you export the feature class to a file geodatabase and re-import it, it will not be registered as versioned. However, it would be worth going through the workflow of registering and unregistering as versioned to see if the issue persists.