Getting "Path too long" when running the HOL about partsunlimited HOT 8 CLOSED

Dave,

The instructions for that lab were just (as in 5 minutes ago) updated. I think the updates will help you with the issue you are seeing. Could you give the HOL another try and let us know?

Thanks,
Elizabeth

from partsunlimited.

Thanks Elizabeth. I will give this a try in the morning. 

Dave Burnison
[email protected]

Sent from Outlook for iPhone

_____________________________

From: Elizabeth Maher [email protected]
Sent: Thursday, February 18, 2016 5:42 PM
Subject: Re: [PartsUnlimited] Getting "Path too long" when running the HOL (#55)
To: Microsoft/PartsUnlimited [email protected]
Cc: dburnison [email protected]

Dave,

The instructions for that lab were just (as in 5 minutes ago) updated. I think the updates will help you with the issue you are seeing. Could you give the HOL another try and let us know?

Thanks,
Elizabeth

—
Reply to this email directly or view it on GitHub.

from partsunlimited.

1_Initialize_log.txt
1_Release_log.txt
2_Download artifacts_log.txt

Elizabeth,

I went through the lab again and updated the things that looked like had changed and tried to test this again but, got the same error.

##[error]The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

I have attached the log files.

Should I have started from scratch instead of updating the build and release that I used originally?

If needed, I can work with someone on Tuesday to troubleshoot this issue.

from partsunlimited.

Sorry - these are more issues due to the invalid path. You should use $(Build.StagingDirectory) instead of anywhere you see "C:\Agent\HOL". Hope to have this fix into the HOL very soon.

from partsunlimited.

This has now been updated https://github.com/Microsoft/PartsUnlimited/blob/hands-on-labs/docs/HOL_PartsUnlimited_WebSite_Continuous_Integration/HOL_PartsUnlimited_WebSite_Continuous_Integration_with_Visual_Studio_Online_Build.md Can you please see if you still have problems?

from partsunlimited.

@dburnison Are you still getting this issue? Open to help figure out what's going on.

from partsunlimited.

Sorry for not responding sooner. I was able to get past the issue. Part of it was my own doing as I had entered some data in the wrong field when configuring the Azure Resource Group task. The updates that were made to the lab did help make things more clear. I did find a couple of issues such as didn't realize that the Resource Group Name cannot contain any spaces and I had to select "Azure Resource Manager" rather than "Azure" when creating the service endpoint.

from partsunlimited.

Glad you got past it - thanks for the response!

from partsunlimited.