Palisade Knowledge Base

Home → End User Setup → Before You Install → Microsoft Components Required for Palisade 6.x Software Install

1.15. Microsoft Components Required for Palisade 6.x Software Install

Disponible en español: Componentes de Microsoft necesarios para la instalación del Software de Palisade 6.x
Disponível em português: Componentes da Microsoft requeridos para a instalação do Software Palisade 6.x

Applies to:  All products, release 6.x
(If you have 7.x software, please see Microsoft Components Required for Palisade 7.x Software Install.)

Are there any prerequisites for installing releases 6.x of Palisade software?

There are certain prerequisites, yes. Our installer checks for them and installs them if they are not present, so for an attended install you should be able to run our installer and let it install what it needs. But if there are install problems, or especially if you're doing a scripted install, you may choose to install components (1) through (5) before running our installer.

You can find Microsoft Windows Installer and .NET at Microsoft's Download Center, but please download .NET and Visual C++ from our site because specific sub-versions are required.

(1) Microsoft Windows Installer 3.1 or later

Please download and install this from Microsoft.com if it is not already on the target computer.

(2) Microsoft .NET 2.0

Windows 7 and Vista come with .NET 2.0 already installed.

Windows XP does not come with .NET 2.0.

Windows 8.0 (original Windows 8) does not come with .NET 2.0. Our 6.1 and later installers install it. If you have 6.0, see Installing Palisade Software 5.7 or 6.0 in Windows 8.

Windows 8.1 does not come with .NET 2.0. Our 6.2 and later installers do install .NET 2.0. If you're installing Palisade software 6.0 or 6.1, see Installing Palisade Software 6.0 or 6.1 in Windows 8.1.

(3) Microsoft Visual C++ 2005 Redistributable

This is Microsoft Visual C++ 2005 Redistributable 8.0.59193 and is required on all setups.

  • Link: http://download6.palisade.com/D6/620/Prerequisites/vcredist_x86_2005.exe
  • Optional command line (with user interface): vcredist_x86_2005.exe
  • Optional command line (no user interface):
    vcredist_x86_2005.exe /q:a /c:"VCREDI~1.EXE /q:a /c:""msiexec /i vcredist.msi /qn"" "
    Caution! You need to use the short filename following the first /c. It is usually VCREDIST~1.EXE, but can vary from one computer to the next. To discover the short filename, at the command prompt type
    dir /x vcredist_x86_2005.exe

(4) Microsoft Visual C++ 2010 Redistributable (32-bit)

This installs as Microsoft Visual C++ 2010 x86 Redistributable 10.0.40219 and is required on all setups, even if you have 64-bit Windows or Office.

(5) Microsoft Visual C++ 2010 Redistributable (64-bit)

This installs as Microsoft Visual C++ 2010 x86 Redistributable 10.0.40219. It is required on all 64-bit Windows, even if you have 32-bit Office. Don't install it on 32-bit Windows.

(6) Visual Basic for Applications and Visual Basic 6 Runtime

Visual Basic for Applications and Visual Basic 6 Runtime are usually present as part of Microsoft Office and Microsoft Windows, respectively, and therefore our installers do not check whether these are present. Please follow those links to check that both are present and to install them if necessary.

(7) optional: Microsoft Project

Microsoft Project, if present, enables simulation of .MPP files as well as Excel workbooks in @RISK Professional and Industrial editions. Please see Windows and Office Versions Supported by Palisade for compatible versions of Microsoft Project.

@RISK senses Project at run time, by looking at the Windows association for .MPP files. Therefore you can install Project before or after @RISK or the DecisionTools Suite, or not install it if simulation of .MPP files is not wanted.

(8) optional: Microsoft SQL

Microsoft SQL, if present, enables the @RISK Library feature in @RISK Professional and Industrial Editions. Please see SQL—Do I Need to Install It? for more.

@RISK senses the presence of SQL at run time. You can install SQL before or after @RISK, or not at all, depending on whether your users want the @RISK Library feature and whether databases will be local or on a remote machine. Please see SQL Versions and Installation.

Last edited: 2017-05-16

This page was: Helpful | Not Helpful