topic Re: Create Migration Workspace Returns "Domain not Found" Errors in ArcGIS Utility Network Questions

Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves — Wed, 22 Jul 2026 23:40:11 GMT

Hello,

As the title states, I am getting a list of errors specifying "Domain Not Found" for every domain in the Asset Package. The Asset Package and Source GDB contain the same domains (Water UN Expanded defaults). The tool worked yesterday; now it is erroring, and I cannot figure out why.

Any thoughts?

Thanks

Re: Create Migration Workspace Returns "Domain not Found" Errors

MikeMillerGIS — Thu, 23 Jul 2026 00:34:12 GMT

We typically see that when a database is corrupt. What are the inputs(source data and asset package), where are they located. I see you are using a network share for your atbx,

If you try to apply the asset package before running the tool, are there any errors?

Re: Create Migration Workspace Returns "Domain not Found" Errors

MikeMillerGIS — Thu, 23 Jul 2026 00:35:01 GMT

I also see you have an active map, we have seen where this causes the corruption. If you delete the map and restart pro or use a new pro session, does it complete?

Re: Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves — Thu, 23 Jul 2026 16:35:47 GMT

@MikeMillerGIS, yes, I am on a network for my org. The inputs are:

I did just notice the (aqua) missing parameters that I normally see on this tool's msgs.

I just tried a C: (documents) fresh UN aprx template in a new pro session, and now cannot even do my "Change Asset Package Spatial Reference" tool. No active maps. Same exact error of no domains found. They are definitely there, haha.

Re: Create Migration Workspace Returns "Domain not Found" Errors

MikeMillerGIS — Fri, 24 Jul 2026 14:03:38 GMT

That means something is corrupt with that asset package. Any chance you can zip it up and send it to me. Want to see what is going on.

Re: Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves — Fri, 24 Jul 2026 14:21:12 GMT

Will do. I'll send it over in a few.

Just confused as to why the freshly downloaded AP threw the same error.

Re: Create Migration Workspace Returns "Domain not Found" Errors

MikeMillerGIS — Fri, 24 Jul 2026 14:22:36 GMT

I wonder if it is the python environment then. Are you using a python clone? Maybe try a new clone?

Re: Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves — Fri, 24 Jul 2026 14:25:28 GMT

I'll try a new clone now

Re: Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves — Fri, 24 Jul 2026 14:56:16 GMT

Just tried a new clone. Same errors

Re: Create Migration Workspace Returns "Domain not Found" Errors

MikeMillerGIS — Fri, 24 Jul 2026 15:13:35 GMT

I just tried Change AP spatial reference on they AP you sent and it works fine. Tried 3.7.0, then installed 3.7.1 and both work.

Re: Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves — Fri, 24 Jul 2026 15:34:26 GMT

hmm

Re: Create Migration Workspace Returns "Domain not Found" Errors

SahilBhouraskar — Thu, 30 Jul 2026 09:56:12 GMT

Re: Create Migration Workspace Returns "Domain not Found" Errors

gis_KIWI4 — Thu, 30 Jul 2026 04:11:29 GMT

@auustinreeves - We have seen errors like this in cases where the tool/AP/GDB was not stored locally on the computer i.e in a shared drive. Is our running locally on your machine?

Re: Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves — Thu, 30 Jul 2026 16:24:45 GMT

My org works off a shared drive/VM environment. Maybe for some reason, that finally made it hiccup like it is.

I am going to attempt a fresh AP and GDB in a new C: aprx.

Thank you for sharing that you've had issues with this before.

Re: Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves — Tue, 04 Aug 2026 16:34:58 GMT

So the issue is something with shared network drives. Tool executions were successful when testing aprx/tbx/gdb in a C: location. Also successful tool operations when setting tool outputs in my original aprx (shared network location) to C: location.

To clarify, the C: of my virtual machine, that is - not my physical machine's C:.

So, the ever-standing good practice of avoiding shared drives still stands. Thanks @MikeMillerGIS for testing this out with me.