nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Getting an error message "Invalid XML Workspace Document provided" when trying to import data into a new enterprise geodatabase.

LClark1102

I used the Export XML Workspace Document tool to export data from an existing eGDB with the intention of using it to copy all of the data to a newly created eGDB. However, I'm getting the message as shown in the screenshot below. Anyone know what the issue could be?

I've used this method in the past to import the schema only to a new geodatabase. Could it be due to the fact that I'm trying to export the entire database? The XML is about 8GB.

If this isn't a viable method for a database this large, could anyone recommend a different method?

Thanks.

Trouver plus de publications taguées avec

Geodatabase

Desktop

Accepted answers

LClark1102

Hi everyone, I appreciate the responses. I was attempting to copy data over to another database on someone's behalf, but it turned out the database they shared hadn't been enabled as an enterprise geodatabase. So the problem was on my end. I wish I had double-checked before posting, but at least I'll know better in the future. Thanks again for the answers that were provided!

All comments

Robert_LeClair

Hmm...interesting. So in the Export XML Workspace Document GP tool, there is a caution message that says the following: "The output XML workspace document can be very large when you copy both the data and the schema. Generally, this is not recommended for copying geodatabase data. Alternatives for copying geodatabase data include using the Copy tool or the Clip tool to extract subsets of the data. In addition, the Package toolset contains tools that consolidate, package, and share layers, map documents, address locators, and geoprocessing results."

8 GB is pretty big so size could be the issue perhaps.

MikeVolz

Have you tried just performing this workflow on the schema as a test?

MobiusSnake

I've run into something similar, have you tried exporting your file with a zip extension rather than as XML? In my experience this behaves differently than zipping a previously-exported XML file, you want to actually specify a .zip extension at the time you run the Export XML Workspace Document tool. (It supports .xml, .zip and .z extensions, as does the Import XML Workspace Document tool.)

LClark1102

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.