Palisade Knowledge Base

Knowledge Books

• Knowledge Books
• Standalone Licenses
• Network Guide
• More on Networks
• End User Setup
• Techniques and Tips
• Troubleshooting
• Licencias individuales
• Guía para Administradores de Red
• Licencias de red
• Configuración de usuario final
• Técnicas y Consejos
• Soluciones
• Licenças Standalone
• Licenças de Rede
• Configuração do usuário final
• Técnicas e Dicas
• Soluções
• Obsolete Articles

• Main Support Page

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

1.14. Microsoft Components Required for Palisade 7.x Software Install

Disponible en español: Componentes de Microsoft necesarios para la instalación del Software de Palisade 7.x

Applies to:  All products, release 7.x

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

There are certain prerequisites, yes. Our installer checks for components (1) and (2) 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, try installing (1) and (2) manually and then re-running our installer. In a scripted install with an MSI installer, you must install components (1) and (2) before running our installer.

1. Microsoft .NET Framework 4 Client Profile should already be on Windows 8, 8.1, and 10 installations, and on Windows 7 if all updates have been applied. In Programs and Features, locate and click a menu item Turn Windows Features On and Off and click it.

   • If .NET 4 is on that second page, it's part of Windows and you don't need to install it but you might need to enable it (black box or tick mark) or repair it (see Microsoft .NET Framework Repair Tool).
   • If .NET 4 is not listed on that page, it's not part of your version of Windows. Install or reinstall it from
     http://www.microsoft.com/en-us/download/details.aspx?id=24872.

   (If you have .NET 4-point-anything, you don't need to install .NET 4.0. If you have the full version .NET 4, or another version with a CLR of 4 in the chart at .NET Framework Versions and Dependencies, you should be fine.)

2. Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 — install from
   http://www.microsoft.com/en-us/download/details.aspx?id=40784
   In 32-bit Windows: Install the 32-bit (x86) version.
   In 64-bit Windows (even with 32-bit Office): Install both the x86 version and the x64 version.
   Don't install the "arm" version.

3. Needed by end-user software, not installers: Visual Basic 6 Runtime.
   This is usually present as part of Microsoft Windows, and therefore our installers do not check whether it is present. Please follow the link to check that it is present and up to date, and to install it if necessary.

4. Needed by end-user software, not installers: Visual Basic for Applications.
   This is usually installed by the Microsoft Office installer, and therefore our installers do not check whether it is present. Please follow the link to check that it is present and enabled, and to install it if necessary.

5. 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 Microsoft 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.

6. 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-06-05