I'm receiving the above error when I try to manually install AutoCad 2012 on a PC from a folder on our network containing the software files. I've installed the software on numerous other PCs in our organization with no issues. What is the problem with this one? I've attached the log file for your review/comment.
Thank you in advance!
Solved! Go to Solution.
Try installing the application locally instead of over the network and do so under a different user account with local admin rights, UAC off, and anti-virus disabled. That should be a good start.
Thank you for your suggestions; however, all the other installations I performed successfully were done in the exact same way. So, I don't think any of those things will make any difference. Did you look at the log file?
Yes. Since the log file only contains a generic 1603 without a root cause for failure, we're only left with a laundry list of things to try. This is usually the first step, since it seems to resolve many of these strange occurrences. All the prereqs and the materials library installed.
It must have been something with the user's userid. I did copy the files from the installation path on the network to a folder on the user's PC's HDD, then ran the install from the local machine, under a PC Admin userid. That worked like a champ! Thank you!!
My pleasure Kim. I'll close out the support call. Let us know if you have any other problems!
I had the same thing happen recently. I created my deployment files several months ago and I installed it just fine on my workstation. This week I started installing to other workstations but before I did I edited my deployments to include AutoCAD 2012 SP2 and Fusion 2012 SP3. Every workstation I tried I had the installation fail. So I recreated my deployments and did not add either service pack, then the installations went fine. After AutoCAD and Fusion installed I manually applied the Service PAcks successfully.
My suggestion, if you want to modify your deployment or move it to another server, it would be better to recreate one than modify the existing one, you can add language pack, service pack to your new deployment, since I got some reports that after modified, the deployment doesn't work any more for some reasons, and recreate one can solve the problem.