We have an production Oracle Geodatabase with an ArcFM-ified electric geometric network. We created a replica Oracle Geodatabase in which we dropped all geometric networks and un-ArcFM-ified all classes. However, when we try to open some of the feature classes, such as GIS.Transformer, in ArcGIS Pro we get the error message:
Unable to create object class extension COM object
We have triple-checked in ArcCatalog that the class is a simple Point feature class. Any ideas on why we would be getting this message would be much appreciated.
Thx,
Ed
I should have also noted that the new replica geodatabase is archive-enabled. We used ArcCatalog to enable the archiving. Would this cause heartburn for ArcGIS Pro?
Ed
So... I dug in closer and examined the Definition column GDB_Items table (sorry ESRI folks) for one of the problem classes. In this case it was a CapacitorBank -- previously an ArcFM Simple Junction, but as presented in ArcCatalog now just a "Point" feature class. What I found in the EXTCLSID tag in the Definition XML was this:
<EXTCLSID>{91BC9A23-B210-4EE5-B524-93BCD640E58D}</EXTCLSID>
Which, per the SE ArcFM site is an ArcFM class extension for simple junction features (below).
How this remained after I had "un-ArcFM-ified" the feature class I don't know.
However, I modified the Definition XML to remove the class extension (again, sorry ESRI) so it now looks like this:
<EXTCLSID />
I *now* can add the feature class to an ArcGIS Pro map.
Pretty sure there has to be a better way to do this.
Ed
It seems the steps that created this condition (at least in our case) were:
- Drop the geometric network
- Un-ArcFM-ify all classes in the feature dataset
It seemed that after dropping the network all contained classes were un-ArcFM-ified, so that afterward the "Un-ArcFM" operation actually did nothing. However, one of these steps did not perform exactly as expected. So that while after the steps were completed it *seemed* that the ArcFM class extensions were removed, in fact they were not.
Ultimately the work-around appears to be:
- Re-ArcFM-ify the classes
- Confirm the classes are actually ArcFM classes
- Un-ArcFM-ify the classes
I tried these steps in a test environment and afterward was able to add them all to an ArcGIS Pro project.
(Hopefully the last post in this thread)
Ed