Parameters for C++ Prereq being seen as missing files
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Our newer Revit distributions have an issue where the install will fail unless C++ Redist x86 for 2015-20XX is already installed. We could tell the Revit installer's attempt to install the included 2015-2019 Redist was not working, so pre-install would skip that hiccup.
I looked deeper today and found what seems to be the issue in the installer log.
[ PluginManager::PerformOperation ] Starting Installation of [GUID] name: Microsoft Visual C++ 2015-2019 Redistributable (x86) )
[ CommandHandler::Install ] Command Handler Install called...
[ Autodesk::DDAUtils::FileUtils::IsExecutable ] File: /q doesn't exists
[ Autodesk::DDAUtils::FileUtils::IsExecutable ] File: /norestart doesn't exists
[ CommandHandler::HandleRequest ] Executing package install command: "[NETWORKLOCATION]\image\RVT_2022_en-US\3rdParty\x86\VCRedist\2019\vcredist_x86.exe" /q /norestart
[ PluginManager::PerformOperation ] Fail when performing Installation of [GUID] name: Microsoft Visual C++ 2015-2019 Redistributable (x86) )
Source of the issue seems obvious now, its reading the parameters as missing files instead. But I cannot find where the issue is coming from for certain.
Within pkg.vcredist2019x86.xml, it shows as
<InstallFile type="EXE" contents="File" installParams="/q /norestart" file="3rdParty/x86/VCRedist/2019/vcredist_x86.exe">
Within setup.ini, it shows as
[VCREDIST2019X86]
PLATFORM=ALL
PRODUCT_NAME=Microsoft Visual C++ 2015-2019 Redistributable (x86)
EXE_PATH=3rdParty\x86\VCRedist\2019\vc_redist.x86.exe
EXE_PARAM=/install /quiet /norestart /log %tmp%\vcredist_x86_2019.log
IGNORE_FAILURE=YES
VC_FUNC=VCRedistCheckx86
VC_SOURCE=Setup\SetupUi.dll
VC_SOURCE_II=AdAppMgrSetup.dll
VC_PARAM=14.0;27702
Based on the error, it looks to be pulling parameters from the PKG file. But the formatting within that file looks correct and mirrors the parameters seen in other PKG XML files.
Is there somewhere else that this error or typo might be hiding? Or is there something I might be missing in the XML that could lead to the package install command being executed incorrectly?
