Select to view content in your preferred language

Experience Builder Developer Edition 1.16 Long Paths

123
1
Jump to solution
3 weeks ago
Labels (1)
cdevault_pickett
Regular Contributor

I have installed Experience Builder Developer Edition 1.16 on two machines a development machine and a production machine. I had some issues on the production machine installing some widgets so when I went to delete the folder and start over I was greeted with the attached error. It seems like there's new new file paths beyond Window's limits. Just throwing this out there, my development machine had long file paths enabled, so once I can restart my production server I'll test my theory. But it might be a good idea to make sure you have long file paths enabled before deploying 1.16.

Here is one example. This does not exist in my 1.15 deployments. 

E:\arcgis-experience-builder-1.16\ArcGISExperienceBuilder\client\node_modules\@arcgis\map-components\dist\types\data\arcgis-web-compoments\actions-runner-1\_work\arcgis-web-components\arcgis-web-components\packages\map-packages\map-components\.stencil

Edit: long file paths is already enabled on this Windows Server.

0 Kudos
1 Solution

Accepted Solutions
cdevault_pickett
Regular Contributor

After discovering that long file paths was already enabled on the server (which was running Windows Server 2016) I decided to try it out on Windows Server 2022. I did not have any issues with these long file paths on Windows Server 2022 and have moved my Experience Builder Developer Edition to this server. 

Just putting this here in case anyone else has any issues. 

View solution in original post

0 Kudos
1 Reply
cdevault_pickett
Regular Contributor

After discovering that long file paths was already enabled on the server (which was running Windows Server 2016) I decided to try it out on Windows Server 2022. I did not have any issues with these long file paths on Windows Server 2022 and have moved my Experience Builder Developer Edition to this server. 

Just putting this here in case anyone else has any issues. 

0 Kudos