Revit Architecture 2012 fails on Visual C++ 2005 SP1 install

[rturcotte10]

Hi Autodesk Support,

I have a user who we can't get Revit Architecture 2012 to install. We get an error when installing the Visual C++ redistributable.

It is very very similar to this KB article: http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=17570140&linkID=9338138 however there is no fix for this for Revit Architecture. Is there a fix for this that is not posted on the website?

That KB hotfix fixed it for a previous trial install of Revit.

The computer is Windows 7 32-bit SP1. We don't know what is causing this Visual C++ issue. It has worked on other computers.

Here is a list of Visual C++ redistribs on the computer:

Microsoft Visual C++ 2005 Redistributable

Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 (9.0.30729)

Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148 (9.0.30729.4148)

Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 (9.0.30729.6161)

Microsoft Visual C++ 2008 x86 ATL Runtime 9.0.30729 (9.0.30729)

Microsoft Visual C++ 2008 x86 CRT Runtime 9.0.30729 (9.0.30729)

Microsoft Visual C++ 2008 x86 MFC Runtime 9.0.30729 (9.0.30729)

Microsoft Visual C++ 2008 x86 OpenMP Runtime 9.0.30729 (9.0.30729)

Microsoft Visual C++ 2010 x86 Redistributable - 10.0.30319 (10.0.30319)

Here is the error log of the most recent install attempt

2012/5/22:15:08:20    kroyal    DECO-WD-003987    === Setup started on DECO-WD-003987 by kroyal ===
2012/5/22:15:08:20    kroyal    DECO-WD-003987    Launch
2012/5/22:15:08:34    kroyal    DECO-WD-003987    PageOpen    LaunchDialog        
2012/5/22:15:08:43    kroyal    DECO-WD-003987    PageOpen    LicenseDialog        
2012/5/22:15:08:47    kroyal    DECO-WD-003987    PageOpen    ProductSelectionDialog2        
2012/5/22:15:09:05    kroyal    DECO-WD-003987    PageOpen    LicenseDialog        
2012/5/22:15:09:07    kroyal    DECO-WD-003987    PageOpen    LaunchDialog        
2012/5/22:15:09:26    kroyal    DECO-WD-003987    PageOpen    LicenseDialog        
2012/5/22:15:09:39    kroyal    DECO-WD-003987    PageOpen    ProductInfoDialog        
2012/5/22:15:10:55    kroyal    DECO-WD-003987    PageOpen    ProductSelectionDialog2        
2012/5/22:15:11:00    kroyal    DECO-WD-003987    PageOpen    FullProgressDialog        
2012/5/22:15:11:01    kroyal    DECO-WD-003987    Installing Microsoft Visual C++ 2005 SP1 Redistributable ATL Security Update (x86): C:\Autodesk\Autodesk_Revit_Architecture_2012_English_Win_32-64bit\3rdParty\x86\VCRedist\2005SP1ATL\vcredist_x86.exe /q:a /T:C:\Windows\temp /c:"VCREDI~3.EXE /q:a /c:""msiexec /i vcredist.msi /qn /l*v C:\Users\kroyal\AppData\Local\Temp\vcredist_x86_2005.log"" "
2012/5/22:15:11:03    kroyal    DECO-WD-003987    Install    Microsoft Visual C++ 2005 SP1 Redistributable ATL Security Update (x86)    Failed    Installation aborted, Result=1603

Any help would be appreciated.

[TravisNave]

Your product is failing to install because the prerequiste program required by the installer is newer than the version being installed. Please uninstall the prerequisite program causing the issue and run your installer again.

For more information about this process, please see my KB link here:

http://forums.autodesk.com/t5/Installation-Licensing/Some-Products-Fail-to-Install-Result-1603/td-p/...

Good Luck!

[rturcotte10]

Thanks! I had not seen that guide so I'll give that a try.

[Anonymous]

This is an absured solution, to uninstall the pre-reqs.  I have OTHER software installed that requires these newer pre-reqs.  So, uninstalling them to install AutoCAD will break the other software.  Then I have to update the pre-reqs again.

Is there any chance of getting this fixed in future deployment solutions?

[TravisNave]

It is what it is.  The absurdity of it is not in question.  However, this is the current work-around.  I can attest from hundreds of installs concerning this problem that it does not break other programs because the prerequisite gets reinstalled with the software.  Beyond that, Windows Update can take it the rest of the way if necessary.  I suspect this won't be a problem in future releases, but for now this is how we get past the issue.  Sorry.