Select to view content in your preferred language

Error with Utility Network Migration Toolset

610
5
Jump to solution
03-17-2025 03:31 PM
BrandoCrozier
Emerging Contributor

We are running the Migrate to Utility Network tool from the UtilityNetworkMigration.atbx (Version 3.3.1) found here: https://community.esri.com/t5/arcgis-utility-network-blog/get-started-with-the-migration-toolset/ba-... 

During the run we received:

arcgisscripting.ExecuteError: ERROR 003050: The item was not found. [Custom_Projects\main.UtilityNetwork]
ERROR 160722: The item was not found. [Custom_Projects\main.UtilityNetwork]
Failed to execute (ImportXMLWorkspaceDocument).


Failed script Migrate to Utility Network...
Failed to execute (MigrateToUtilityNetwork).

 

We investigated the created mobile Geodatabase and found that main.UtilityNetwork existed at ["Custom_Projects\UN\Prototypes\UN_Simple_Migration_001\MigrationDatabase\MigrationDatabase.geodatabase"].

Has someone faced this before? Why is the tool looking in the wrong place?

See attached for complete Error Report.

0 Kudos
2 Solutions

Accepted Solutions
gis_KIWI4
Frequent Contributor

@BrandoCrozier - I have not seen this error and the tool seems to work fine when we used it.
I think the issue might be Output Folder path. 
Looking at the text file attached I think the issue is that couple of parameters are left blank when the tool runs. It could be that that the tool is having trouble setting these parameters as the output folder defined in your code is a UNC path. 
gis_KIWI4_0-1742254910321.png

Below is a snapshot of the what it looks on my end.
You can see that the Output Utility Network is a full path (in your its blank) 
I think the code cannot understand the UNC path \\gismisc\Custom_Projects\UN\Prototypes\UN_Simple_Migration_001


gis_KIWI4_1-1742254997308.png

Could you try using an absolute path? 





View solution in original post

0 Kudos
BrandoCrozier
Emerging Contributor

@MikeMillerGIS @gis_KIWI4 - Thanks for the suggestions. The first try we went for was mapping the UNC path to a Drive Letter. It worked!!!

So, to clarify, we are using a network share. We just have the network share mapped to a drive letter.

View solution in original post

0 Kudos
5 Replies
gis_KIWI4
Frequent Contributor

@BrandoCrozier - I have not seen this error and the tool seems to work fine when we used it.
I think the issue might be Output Folder path. 
Looking at the text file attached I think the issue is that couple of parameters are left blank when the tool runs. It could be that that the tool is having trouble setting these parameters as the output folder defined in your code is a UNC path. 
gis_KIWI4_0-1742254910321.png

Below is a snapshot of the what it looks on my end.
You can see that the Output Utility Network is a full path (in your its blank) 
I think the code cannot understand the UNC path \\gismisc\Custom_Projects\UN\Prototypes\UN_Simple_Migration_001


gis_KIWI4_1-1742254997308.png

Could you try using an absolute path? 





0 Kudos
MikeMillerGIS
Esri Frequent Contributor

I think something is up with using a network share as it is looking for CustomProjects\UtilityNetwork.  In the output folder, there should be a XXX_classes.xml file.  Can I get a copy of that?  That would help identify what is wrong.  The failure is importing that file, which lays down the structure of the Utility Network.

0 Kudos
BrandoCrozier
Emerging Contributor

Thanks @MikeMillerGIS!

The file is at \\gismisc\Custom_Projects\UN\Prototypes\UN_Simple_Migration_001\MigrationDatabase.

Included is a copy.

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

Sadly that file imports fine and is valid.  So there is something else at play here.  It has to be network related.  I tested from my laptop to a server in data center with unc path and could not repo even with really slow network times.  

 

Can you move it all locally and see what happens?

 

 

0 Kudos
BrandoCrozier
Emerging Contributor

@MikeMillerGIS @gis_KIWI4 - Thanks for the suggestions. The first try we went for was mapping the UNC path to a Drive Letter. It worked!!!

So, to clarify, we are using a network share. We just have the network share mapped to a drive letter.

0 Kudos