We have seen cases were the deployment of a language pack has failed.. When analyzing the installer logs, the noted error message was 1603.
We have a solution posted to resolve this error here.
However in this case the solution did not work for us. After some troubleshooting, we found that the deployment image had the service pack integrated into the deployment.
As a workaround, we removed the service pack from the image and the product installed. Once done, we installed the latest update to complete the installation process.
When attempting to install Alias Design 2015 on a system where Alias Surface 2015 is already installed, the installation option may be greyed out. This can occur if the Alias Surface was installed and the latest service packs where applied. To resolve this issue, you will need to remove the latest Alias Surface Service Packs.
Please see also the following link for other helpful suggestions:
Thanks to Philipp Wronski for sharing this tip with the community.
1. We analysed the installation log file and there was a problem with VCRedist so we hacked it out from setup.ini file. The workflow is noted here:
2. We then tried installation of again and this time, there was a 997 error:
...so I applied this solution:
I then needed to update article to include 3 GUID values for AutoCAD LT for the security exception and get a better image of the registry.
We needed to use Orca on the following msi files: AcadltLP.msi. acadlt.msi, AcadltPS.msi.
I also tweaked and improved this solution to use a MSDN site to get Orca.
3. AutoCAD LT 2015 finally installed! But when we launched it, there is a side by side installation error and this means we actually needed VCRedist installed, even though it was listed as installed in the Control Panel.
4. I manually tried to run all the .exe files in the following 2 folders:
...and I got the 997 error again!
5. We needed to add the VCRedist GUID values to the security exceptions list. To get the GUID values for the VCRedist, we needed to use verbose logging to get the GUIDS for those products.
a. We needed to enable verbose logging. I tweaked and improved this solution by adding a note to use a Microsoft Fix It tool.
b. I deleted all the files in %temp% folder.
c. I ran the first .exe file noted here:
d. I copied all the log files from %temp% back into the same folder for analysis later . i.e.
e. I then repeat for each folder. i.e.
NOTE: The name of the .exe file for the folders are above are called: vcredist_x64.exe & vcredist_x86.exe.
f. I then just opened each of the log files generated and searched for "ProductCode". The result is the article below:
g. Just add all the GUID's into the .reg file. Example is below for AutoCAD LT 2015 (3 GUIDs) + VCRedist (6 GUIDs). If you have this problem, just download the file below and rename .txt to .reg and then double click it to import it into your registry.
AutoCAD LT 2015Error 997 Registry Fix: SecRepWhtlst+VREDIST
As you can see, we applied many articles to solve one problem. I would like to thank the technical guru Jeremy Hanson for helping me on this case and Gary A Johnston for confirming that this worked.
Deployment - Installing
In this article, search for: What if I don’t want to include Autodesk Application Manager in our network deployments?
To easily hack the setup.ini file, you can watch this video example of hacking out .NET:
Uninstall via command line [SCCM] of the Application Manager:
Thanks to Chris H. for coming that this solution worked!
Buried in one of the blog posts for installing software on Windows 7, is this tip:
Microsoft Fix It tool on How to enable Windows Installer logging.
We used to use this workflow which is a bit more labour intensive:
Another time saving Microsoft Fix It Tool on How to disable IPv6 or its components in Windows is noted here:
Please check out this solution:
The workflow is also noted here:
Just an FYI, the realm of Roaming Profiles is not supported by Autodesk due to the differences of setup for each network at each of site.
For sites that have mastered this setup for Autodesk Civil 3D 2015, please note the following solutions:
One of the programs that is part of Autodesk Civil 3D is a completely separate application but it is a part of the install as a subcomponent is Storm & Sanitary Analysis. Please check out this article:
Thanks to Dave Meyer for sharing this tip with the community.
If you use Revit 2014 with the Globe Link for Autodesk Revit 2014 [Release Date: 2013-05-03], please note the following article if you get an error that you need the Google Earth.msi file.
Thanks to Amy Nowacki for confirming that this solution worked.
Just an FYI...
Thanks to Alison Gangler for sharing this with the community.