Trying to install Prognosis 11.5. Sometimes it installs other times not.
When it doesn't it gives the error:
"Product: Prognosis -- Prognosis includes both 32-bit and 64-bit components and requires both Microsoft Visual C++ 2013 Redistributables. Please install Microsoft Visual C++ 2013 Redistributable (x86) and try again."
This error is not correct as both redistributables are already installed. Yet it won't let me move forward.
The error "Product: Prognosis -- Prognosis includes both 32-bit and 64-bit components and requires both Microsoft Visual C++ 2013 Redistributables. Please install Microsoft Visual C++ 2013 Redistributable (x86) and try again" is misleading if the Microsoft Visual C++ 2013 Redistributable (x86) libraries have already been installed.
If the installed "Microsoft Visual C++ 2013 Redistributable (x86)" libraries are newer than the ones provided in the Prognosis Installer, the error is returned.
So you are saying if someone has a newer 2013 version but also have the ones needed by the installer it still doesn't work?
The prerequistes I have on my PC are the ones that are in the Prerequisites folder that came with the install. They are also the newest version of 2013 I have installed so no other version should be taking over. I still get the message.
I can go through uninstalling and re-installing but this makes it difficult when needing to push to many PCs using SCCM as PCs have different versions of the redistributables. My script ensures that PCs get the ones requested by the installer. But as evident that doesn't matter as I continue to get the error.
This needs to be deployed silently to the end users, so my script first installs the 2013 Redistributables then installs Prognoisis using the MSI. If there is a way to completely install (both Prognosis & Prereqs) silently using the .exe let me know.
The Microsoft Visual C++ Redistributable error is because Prognosis looks for a specific version of the C++ libraries. Although Prognosis workes with the newer versions of the 2013 and 2017 C++ libraries, if the C++ libraries detected by the Prognosis installer do not exactly match the version Prognosis is expecting, the error will be returned.
If the C++ library versions being installed exactly match the versions provided by the Prognosis installer, the error is likely returned because the required C++ is present, but a newer version is also present. The solution has been to remove all the 2013 and 2017 C++ libraries installed and let the Prognosis installer add the required C++ libraries. This process works for very well for an attended Prognosis installation, but may need some modification for unattended installations.
Use the following for unattended Prognosis installations:
So I manually uninstalled all 2013 and 2017 versions from my PC then ran the install script:
"vcredist2013_x64.exe" /install /quiet /norestart
"vcredist2017_x64.exe" /install /quiet /norestart
"vcredist2013_x86.exe" /install /quiet /norestart
"vcredist2017_x86.exe" /install /quiet /norestart
msiexec.exe /i prognosis11.5.0.msi /quiet ACCEPTENDUSERLICENSEAGREEMENT=1 ADDLOCAL=WindowsClient
It installed all of the prereqs, but I get the same error. The only 2013 and 2017 redistributables on my PC are the ones that are included with Prognosis.
The unattended installation failures will need additional investigation. The complexity of this issue would best be addressed by opening a Support case to work directly with the Support team. Please let me know if you additional questions.
Having looked at the planning phase in session one of this series, we will turn our focus to the readiness phase. The all important technical capabilities assessment, ensuring the network, endpoints and users are adequately prepared for the move.
Hear first hand from IR's Global Head of Information Systems and Technology, Jason Schwendinger, on how he has been tackling these issues.Join webinar