I know we have a bunch of proxy issues here, and that's been wreaking havoc on my ability to install...well... anything.
So for laughs, I thought, what if I create an image, move it to a thumb drive and install from that.
But if I move such, I get an error that some properties can't be moved.
Are these properties the reason for the failure to install from that thumb drive?
Everything seems to move to the thumb drive fine and goes through the install process only to error out.
I looked thru the log file and well, when it got to the "failed" portion, it was a ton of meaningless (to me) text.
Would a blocked proxy cause something like this at the install satge?
Solved! Go to Solution.
I know we have a bunch of proxy issues here, and that's been wreaking havoc on my ability to install...well... anything.
So for laughs, I thought, what if I create an image, move it to a thumb drive and install from that.
But if I move such, I get an error that some properties can't be moved.
Are these properties the reason for the failure to install from that thumb drive?
Everything seems to move to the thumb drive fine and goes through the install process only to error out.
I looked thru the log file and well, when it got to the "failed" portion, it was a ton of meaningless (to me) text.
Would a blocked proxy cause something like this at the install satge?
Solved! Go to Solution.
Solved by The_Angry_Elf. Go to Solution.
Solved by TravisNave. Go to Solution.
When you move a deployment to another source, there are some files you have to go in and edit that are coded for the original source. You can't just copy and install and expect it to work. There's surgery involved because Autodesk doesn't make relative pathing.
When you move a deployment to another source, there are some files you have to go in and edit that are coded for the original source. You can't just copy and install and expect it to work. There's surgery involved because Autodesk doesn't make relative pathing.
I think I'll just do as I've done in the past and make an image on a network drive that everyone can access. Problem is finding that location...LOL
I think I'll just do as I've done in the past and make an image on a network drive that everyone can access. Problem is finding that location...LOL
OK, created a new deployment on the server where access is available.
I run the process and point to the newly created "Autodesk" folder under "Programs".
I then get prompted with an error saying the file is outside the network, ummm...no, it's not, it's on a network drive. 1st red flag. But it offers the option to continue. Continuing then fails with the "unable to download. Retrying may fix the problem". Retrying does not fix this btw.
So I look at the log file and I see these:
1. "Symlink is not allow!" - No idea what that is, need to google it.
2. File not found: \\our network drive name\deployments\image\Collection.xml" - Again, no idea about this xml file, google time.
3."Destination folder is not clear or compatible: \\our network drive name\deployments" - say what? It's brand new, nothing in it.
4. "Error: CURL Error Code : 6 "
5. "AdHttlLibException thrown with error code: 1006"
6. GetUpi2.SendHttpPostRequest failed. Error code: 1006"
7. "Request error code: -105"
8. "Download error: -105"
9. "Download request failed"
Ideas?
OK, created a new deployment on the server where access is available.
I run the process and point to the newly created "Autodesk" folder under "Programs".
I then get prompted with an error saying the file is outside the network, ummm...no, it's not, it's on a network drive. 1st red flag. But it offers the option to continue. Continuing then fails with the "unable to download. Retrying may fix the problem". Retrying does not fix this btw.
So I look at the log file and I see these:
1. "Symlink is not allow!" - No idea what that is, need to google it.
2. File not found: \\our network drive name\deployments\image\Collection.xml" - Again, no idea about this xml file, google time.
3."Destination folder is not clear or compatible: \\our network drive name\deployments" - say what? It's brand new, nothing in it.
4. "Error: CURL Error Code : 6 "
5. "AdHttlLibException thrown with error code: 1006"
6. GetUpi2.SendHttpPostRequest failed. Error code: 1006"
7. "Request error code: -105"
8. "Download error: -105"
9. "Download request failed"
Ideas?
Well, it's correct, no Collection.xml file on any computer, just a HTML file named "Collection."
Question now is, what is this file and more importantly, how do I get it or do I simply just need to create the file and locate it accordingly?
Well, it's correct, no Collection.xml file on any computer, just a HTML file named "Collection."
Question now is, what is this file and more importantly, how do I get it or do I simply just need to create the file and locate it accordingly?
OK, this is now getting beyond wanting to deal with.
No image, whether I make it a deployment on a network drive or an install and have it on a local C drive, the install fails!!!
OK, this is now getting beyond wanting to deal with.
No image, whether I make it a deployment on a network drive or an install and have it on a local C drive, the install fails!!!
Found the fix for all this and as I expected, but hoped wasn't the case, it all boils back to our proxy issues I've been fighting since March.
See fix here: Solved: Install Images fail - Autodesk Community - Subscription, Installation and Licensing
Found the fix for all this and as I expected, but hoped wasn't the case, it all boils back to our proxy issues I've been fighting since March.
See fix here: Solved: Install Images fail - Autodesk Community - Subscription, Installation and Licensing
Can't find what you're looking for? Ask the community or share your knowledge.