Create Migration Workspace Returns "Domain not Found" Errors

auustinreeves

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

auustinreeves

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.

View solution in original post

MikeMillerGIS

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?

MikeMillerGIS

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?

auustinreeves

@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.

MikeMillerGIS

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.

auustinreeves

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

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

MikeMillerGIS

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

auustinreeves

Just tried a new clone. Same errors

auustinreeves

I'll try a new clone now

MikeMillerGIS

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.