Revit 2017 Installation Issues (Failed Installation aborted, Result=1603)

[bakerjonEH7XP]

Hello All,

Hoping that someone here might have run across this Revit 2017 installation issue before; we cannot seem to get around it when installing on any of our German (and Thai & Mexican) based client systems (no issues in the USA at all – as far as we know). When remotely installing Building Design Suite Ultimate 2017 on those systems, the installs fail at the same location (at Revit interval), rollbacks begin, and the following is included at the bottom of the resulting log file:

2017/6/12:17:23:07      <UserAccount-Admin>          <ComputerName>        Install    Autodesk® Revit® 2017               Failed    Installation aborted, Result=1603

2017/6/12:17:25:      <UserAccount-Admin>       <ComputerName>      Rollback            Microsoft Visual C++ 2015 Redistributable (x64)        Failed    Failure is ignored, Result=1619

2017/6/12:17:25:15 :    <UserAccount-Admin>     <ComputerName>      Rollback          Microsoft Visual C++ 2015 Redistributable (x86)        Failed    Failure is ignored, Result=1619

2017/6/12:17:25:28         <UserAccount-Admin>     <ComputerName>            === Setup ended ===

I have tried the following, but have had zero-luck with any of the attempts:

• Ran diagnostics through AIDA, but no issues were detected
• Temporarily disabled Windows Firewall
• Manually removed preexisting/previous-version Autodesk keys, files, and folders from client system (2016 an earlier evidently installed and ran fine without issues)
• Ran a system diagnostic with disk cleanup
• Ran a registry diagnostic with cleanup/repair
• Verified necessary permission levels, Read/Write/Admin privileges
• Verified necessary disk space for installation
• Verified regional settings are set to “en-US” (United States – English), which is also what we successfully use locally (USA).
• *Only running/live anti-virus is Microsoft System Center Endpoint, which is the same that we run here in our US corporate office and haven’t had any documented issues with up to this point. I inquired about having it temporarily paused during the installation, but it doesn’t appear to be anything that I can control (corporate policy).   

Does anyone possibly know what factors could be contributing to this failure? Any recommendations would be greatly appreciated.

Thanks in advance.

[Mark.Lancaster]

@bakerjonEH7XP

Welcome to the Autodesk User's Community..

Without seeing your entire installation log file, I can only speculate the 1603 error is the first error of the failure.  If that's the case, I have to say, sorry that you are faced with this problem..  A 1603 failure on a core Autodesk product..  Not good. 

See @TravisNave and my information in this posting.   Some users have had success in reinstalling Windows but that's not really a viable solution.   If something does work for you please let us know because to this date no one has indicated any success in getting over the 1603 error on a core product installation.

Finally thing.  It sounds like you are installing software in many different countries.   Do you have a global licensing agreement with Autodesk?  If not how are you accessing software for these other locations/countries?  Meaning you can't be using USA purchased license in other countries.

[natasha.l]

Hello @bakerjonEH7XP,

Not sure what the entire log shows but it may be related to a similar issue associated with an msi file but first check Autodesk Personal Accelerator for Revit 2017 Install.log. 

Error 1603 when installing Autodesk Personal Accelerator for Revit 2017

Let us know how it turns out. 

Please "Accept As Solution" if a reply has helped resolved the issue or answered your question, to help others in the community.

[natasha.l]

Hello @bakerjonEH7XP,

Please let us know if you are still experiencing this issue with Revit. Let us know if any of the suggestions helped you out &"Accept As Solution" if a reply has helped resolved the issue or answered your question, to help others in the community.

Thank you. 

[bakerjonEH7XP]

Hi natashal84,

Apologies for the slow response, have been troubleshooting this for nearly three days now. Thank you for your link and suggestion. I used it to modify a copy of the PACR.msi, but regretfully, the BDSU2017 installations still failed at the same intervals and produced the same errors. At this point, both Revit 2017 and Inventor 2017 both fail to install, both producing the same errors. I was able to get AutoCAD 2017 to install through a stand-alone deployment, however, it consecutively crashed during launch/initialization every time. Ran standard troubleshooting on those fatals (i.e. certified hardware, updated drivers, Windows/IE updates, C++ Redists, .Net, etc.) but was never able to get it to stabilize. In the end, I had to resort to uninstalling any/all Autodesk 2017 products/apps from the system and reinstall BDSU2016 on it instead (which installed, launched, and operated without any issues). I’ve submitted our log files and running documentation to our reseller and requested they run it up the chain and see what Autodesk recommends. If anything of value comes back down that chain, I’ll be sure to post it here as well. Thanks again for the assist, it is genuinely appreciated!

[bakerjonEH7XP]

Hi Mark.Lancaster,

Yep, you got it… 1603 is the leader to a number of subsequent failures, and thanks for the link and recommendation. Regretfully, after 3 days of dedicated troubleshooting, I have yet to successfully install BDSU2017 or PDS2017. A stand-alone deployment for AutoCAD/Mechanical 2017 made its way in, however, would fatal out during launch each and every attempt. I’ve resorted to uninstalling any/all Autodesk 2017 products/apps from that system and have reinstalled BDSU2016 (which installed, initialized, and operates without any issues). If anything, it buys some time while our reseller runs our logs by Autodesk to see if they have recommendations. And to answer your question, yes, the company has an agreement in place with Autodesk and haven’t had any issues up until this 2017 version. May test the water with 2018 and see where that gets me… if I come across anything of value, I’ll be sure to post it back here for others (looking through the forum threads, it seems like this has become a fairly common occurrence). Thanks again!

[natasha.l]

Hello @bakerjonEH7XP,

Thank you for coming back and letting us know, the community greatly appreciates your contribution to returning to keep us updated. 

[dthede]

I had a very similar problem as described above, except mine occurred with installing from a deployment of BDSP 2017, which had been used successfully on other systems.  In this particular context, Revit 2016 and Revit 2018 were already on the target machine.

The 1603 failure & subsequent ROLLBACKs occurred immediately after attempted installation of Revit Personal Accelerator, as shown in the main log file, and in the detailed (millisecond) log file.  My speculation is that there may be a bad interaction among the the new and existing Personal Accelerator and the Performance Reporting Tools.

My cure is a workaround, as follows:

1. Used the BDSP Suite's .DLM download to install only Revit 2017 and the associated Revit Content Libraries 2017 on the target machine.
2. restart
3. install the relevant updates and desired add-ins appropriate to Revit 2017 "manually."  That is, the updates and add-ins that I normally would have included in the deployment were copied to the target system and installed from it. (Made appropriate "un-adjustments" for the .MSP renaming trick.)
4. restart
5. Used the BDSP Suite's .DLM download to install, rather than "Create Deployment," again. This time, the installation wizard  sees that Autodesk Revit 2017 and the Content Libs are shown as "Installed." It plainly shows with a check mark and the word "Installed" highlighted.
6. Installed the remaining desired components and subcomponents.
7. Installation completed with AutoCAD Performance Reporting Tool labeled as "FAILED."
8. Installed the various updates and desired add-ins appropriate to the non-Revit components of the BDSP 2017.
9. restarted
10. started and exercised each 2017 application.

[David_W_Koch]

---

@natasha.l wrote:

Hello @bakerjonEH7XP,

Not sure what the entire log shows but it may be related to a similar issue associated with an msi file but first check Autodesk Personal Accelerator for Revit 2017 Install.log. 

Error 1603 when installing Autodesk Personal Accelerator for Revit 2017

Let us know how it turns out. 

Please "Accept As Solution" if a reply has helped resolved the issue or answered your question, to help others in the community.

---

@natasha.l

I had this exact error just now, installing Revit 2017 and Navisworks Simulate 2017 from the 2017 Building Design Suite Premium installation files (not a deployment) on a computer that already had Revit 2014, 2016 and 2018 installed, using Remote Desktop from my computer.

Unfortunately, the link in the article you mentioned that is supposed to lead to the Microsoft Orca download does not work, and searching the Microsoft Support site for Orca does not return anything useful.  Without that editor, the solution given is useless.

I am going to try to do the installation directly on the computer, rather than via Remote Desktop, and will drop Navisworks Simulate this time, but I do not have a lot of confidence this will work.  I will note that I had previously used the same installation files to successfully install Revit 2017 on my computer.

[David_W_Koch]

Surprisingly enough, that worked.  And then I was able to install Navisworks Simulate 2017 separately.  Not sure if being directly at the computer, rather than via Remote Desktop made the difference or not, but I am declaring victory and moving on.

One other note:  for both installs, I unchecked the Autodesk Desktop App and BOTH times it installed it anyway.  What is up with that?  We do not want users installing updates on their own.