topic Create Migration Workspace FileNotFound Error in ArcGIS Utility Network Questions

Create Migration Workspace FileNotFound Error

AnthonyHanna — Wed, 23 Jul 2025 15:52:49 GMT

Hello all,

I am attempting to migrate our geometric network of electric distribution data over to the Utility Newark, closely following the path in the electric foundation model. I am using ArcGis Pro 3.5.1, udms 3.5. The Create Migration Workspace tool successfully created many excel files from the point feature classes listed in DataMapping spreadsheet. However, an error stating 'FileNotFoundError: No such file or directory' stops the tool in its tracks when encountering PriOHElectricLineSegment while traversing down the DataMapping spread sheet. My understanding is that the create migration workspace tool should be creating this file. Any help is much appreciated. See below for the error given and the attached file for the full error.

FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Temp\\UNmigrationTest\\UNFremontTest\\WorkingData\\MigrationWorkspace\\FremontMigration\\FremontMigrationWorkspace1\\DataLoadingWorkspace\\DataMapping\\Polylines\\PriOHElectricLineSegment_Single Phase Primary Overhead-ElectricLine_Medium Voltage Overhead Conductor.xlsx'

Failed script Create Migration Workspace...
Failed to execute (CreateMigrationWorkspace).

Re: Create Migration Workspace FileNotFound Error

VenkataKondepati — Wed, 23 Jul 2025 17:41:56 GMT

Hi @AnthonyHanna,

I’ve worked through a few of these UN migrations, and that error looks familiar.

What’s happening here is that the Create Migration Workspace tool is trying to generate an Excel file for the PriOHElectricLineSegment, but it fails when it hits a really long or complex Asset Type name. In your case, it’s trying to name the file:

sql

PriOHElectricLineSegment_Single Phase Primary Overhead-ElectricLine_Medium Voltage Overhead Conductor.xlsx

That’s likely hitting a Windows file path limit or tripping over special characters when it tries to save the workbook — hence the FileNotFoundError.

Here’s what I’d do:

Go into your DataMapping.xlsx
Find the entry for PriOHElectricLineSegment
Shorten or clean up the Asset Type name — remove long descriptors or special characters
Save and re-run the tool

The tool uses those field values to name the Excel files, so cleaning them up usually solves it.

Regards,

Venkat

Re: Create Migration Workspace FileNotFound Error

AnthonyHanna — Wed, 23 Jul 2025 19:27:27 GMT

Hello Venkat,

Thank you for your advice, I will give it a try.

Update: Shortening the name of the Target Asset type created some new errors, but I was able to shorten the name of the Source Subtype Name and corresponding SubtypeCD text in the source file geodatabase. Thank you for your help Venkat.

Anthony

Re: Create Migration Workspace FileNotFound Error

RobertKrisher — Wed, 23 Jul 2025 19:45:25 GMT

This is most likely a path issue, but instead of adjusting the file name or asset type name (or subtype code/name in the source database), the first thing I'd recommend trying is using a shorter Windows path. Instead of trying to have it put everything in a folder like this: "C:\\Temp\\UNmigrationTest\\UNFremontTest\\WorkingData\\MigrationWorkspace\\FremontMigration\\FremontMigrationWorkspace1\\DataLoadingWorkspace\\DataMapping\\Polylines\\PriOHElectricLineSegment_Single Phase Primary Overhead-ElectricLine_Medium Voltage Overhead Conductor.xlsx"

Try something like "C:\\UNmigrationTest" as your output directory.

Which would give you a path like this: "C:\\UNmigrationTest\\DataLoadingWorkspace\\DataMapping\\Polylines\\PriOHElectricLineSegment_Single Phase Primary Overhead-ElectricLine_Medium Voltage Overhead Conductor.xlsx"

Re: Create Migration Workspace FileNotFound Error

VanessaSimps — Thu, 24 Jul 2025 00:25:26 GMT

I was trying to use the 3.3 version of the toolbox tools and was getting a ton of errors until I adjusted to using a non UNC path and also making the mapped network drive path as close to the folder as I could to save pull in the layers to the wizard as well as where the output data would go. I finally got this to work today! Not sure I totally understand why the tools can't use the UNC, but am glad I came across this hint to shorten the window path.