X-ray Error

13399
36
Jump to solution
10-15-2012 09:42 AM
Labels (1)
PatriciaMoehring
Occasional Contributor
Trying to export xml of one dataset and getting error -- "XML Export Datasets Error: Unable to cast COM object of type 'System._ComObject' to interfacet type 'ESRI.ArcGIS.Catalog.IGxObject'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{BDBBB3EB-D0B2-11D1-AED9-080009EC734B}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

I don't know what this means or why it isn't working. Seems like I'm doing exactly what Steve is doing in the video?

Any ideas?
1 Solution

Accepted Solutions
LindsayThomas
Esri Contributor
Hi Patricia,

We have logged this issue as a bug. (this issue occurs in the 10.0.82 version of the addin)

In the meantime, we have a workaround for you (I past this on to the tech support person who was helping you as well, but thought I would response so others can see the workaround)

Workaround

In Step 4 B. of the help http://resources.arcgis.com/en/help/localgovernment/10.1/index.html#/Migrating_your_data_to_the_Loca...

We say select the feature class in the Catalog Tree. This will expose a bug. You will get the error message you posted below when importing the xml to the gdb if your selection is in the catalog tree only.

If you select in the Content tab when selecting the feature dataset\class to get the spatial reference you will not get this error. (ensure that the content tab has a selection)

hopefully this helps.

Cheers,
Lindsay Thomas

View solution in original post

36 Replies
SteveGrise
New Contributor III
Could you post your xml workspace document or email it to me?

Steve
0 Kudos
ScottOppmann
Esri Contributor
Steve -

We were able to reproduce this error late today and will get with you on the details.  We'll also be updating the help documentation to clarify the specific steps required. 



Scott
0 Kudos
LindsayThomas
Esri Contributor
Hi Patricia,

We have logged this issue as a bug. (this issue occurs in the 10.0.82 version of the addin)

In the meantime, we have a workaround for you (I past this on to the tech support person who was helping you as well, but thought I would response so others can see the workaround)

Workaround

In Step 4 B. of the help http://resources.arcgis.com/en/help/localgovernment/10.1/index.html#/Migrating_your_data_to_the_Loca...

We say select the feature class in the Catalog Tree. This will expose a bug. You will get the error message you posted below when importing the xml to the gdb if your selection is in the catalog tree only.

If you select in the Content tab when selecting the feature dataset\class to get the spatial reference you will not get this error. (ensure that the content tab has a selection)

hopefully this helps.

Cheers,
Lindsay Thomas
AndrewFarrar
Occasional Contributor
I have a similar problem when trying to import the LocalGovernment.xml to a file geodatabase.  I get the same exact error message except that it comes up as an "XML Import Error:"  I followed the workaround on this thread assuming that it may be the same issues (selecting all of the inputs from the "Contents" tab in arccatalog.  I'm curious if there has been any more development on this issue?  I'm following step-by-step the directions and doing everything locally.

Any help would be much appreciated!  Thanks!

Andrew
0 Kudos
SteveGrise
New Contributor III
Hi folks, new versions of the Addins for 10.0 and 10.1 were posted today - includes fixes that are intended to solve this issue.
0 Kudos
AndrewFarrar
Occasional Contributor
Thanks for the update Steve.  I was able to work around it, but hopefully the new versions have really fixed it.
0 Kudos
by Anonymous User
Not applicable
I have a little different problem. I made some significant changes (feature class/domain/attribute additions) for a public safety implementation using the X-Ray spreadsheets, and now I am getting an error on import.

OS/Software
Windows 7 x64
ArcGIS for Desktop Advanced 10.1 SP1 (Build 3143)
X-Ray v10.1.90 November 16, 2012 (this was the latest download I could find)

After making the necessary modifications in the spreadsheets, both for the datasets and the domains, I tried both the Import to Geodatabase and the Import Using Geoprocessing... options. Here are the errors respectively:

Import to Geodatabase
XML Import Error:The table name is invalid.

Import Using Geoprocessing...
GeoProcessing Error Messages:


Python Error messages:
Traceback Info:
File "C:\Users\jwood\AppData\Roaming\ESRI\Desktop10.1\ArcToolbox\My Toolboxes\ImportUsingGeoprocessing.py", line 116, in main
createFields(dataset)

File "C:\Users\jwood\AppData\Roaming\ESRI\Desktop10.1\ArcToolbox\My Toolboxes\ImportUsingGeoprocessing.py", line 320, in createFields
fullClassPath= findClassPath(className)

File "C:\Users\jwood\AppData\Roaming\ESRI\Desktop10.1\ArcToolbox\My Toolboxes\ImportUsingGeoprocessing.py", line 573, in findClassPath
fds.Reset()


Error Info:
<type 'exceptions.AttributeError'>: 'list' object has no attribute 'Reset'

Completed script ImportUsingGeoprocessing...
Failed to execute (ImportUsingGeoprocessing).
Failed at Thu Feb 07 09:34:07 2013 (Elapsed Time: 22.00 seconds)


I did not manipulate any table names or add any tables to the LGIM 10.1 schema. Neither error message tells me which object it's having a problem with. Anybody have any ideas?

Many thanks in advance,
James
0 Kudos
ScottOppmann
Esri Contributor
James -

I would suggest you use X-Ray to validate your XML workspace before attempting to import it.  You'll find the Validate tool under theTools dropdown.  The validate tool will check your XML workspace document and give you a report of the errors. 

The error you mention below sounds like the name you assigned to the feature class may not match the name of the worksheet. Also keep in mind the Import Using Geoprocessing only works with simple features and does not support many of the complex data types that are in the Local Government Information Model (parcel fabric, etc.).  This tool (while powerful) should really only be used to cycle on simple changes (new feature classes, tables, domains, etc.) you want to make to you current model.  

Scott
by Anonymous User
Not applicable
Scott,

Thanks very much for the suggestion. I've validated both my modified XML workspace and the original XML workspace provided with the LGIM 10.1 download. They are both in the attached zip file. I'm assuming the Errors are the ones that are causing problems, as the Warnings seem less prohibitive, especially since I am importing into a file geodatabase. There are 20 errors present from the validation of the original download (which surprised me, but obviously some errors are OK), and I have 28. The problem is that none of the listed feature and relationship classes in the Errors list are any of the ones that I modified. Furthermore, all of the missing classes with their associated datasets have a tab present in the GISDatasets workbook. The two that are missing associate datasets are actually pointers to Parcel Fabric sublayers which do not have a spreadsheet tab (there is only the one tab for ParcelFabric). All of the type mismatches have to do with the attachment relationship classes (which are similar in the original validation). That leaves the one NoDatasetName, which seems to suggest that there is either an empty spreadsheet cell defining the name or an empty spreadsheet tab, but I have gone through all of the tabs in the GISDatasets workbook and did not find anything missing in that regard (i.e., all B1 cells are populated, all FeatureDataset definitions are either populated or null [for some root-level relationship classes] and there are no empty tabs). BTW, a great way to surf through the tabs is to use Ctrl+PageUp/PageDown.

So, I'm left scratching my head, and I may be misinterpretting the validation output, but at least this gives me something to go on to keep digging.

Thanks again,
James
0 Kudos