HomeEnd User SetupPrinter Friendly Version

End User Setup

Install and configure your client or workstation software.

1. Before You Install

1.1. Windows and Office Versions Supported by Palisade

International language versions of this article:

Which software platforms or operating systems are supported by Palisade?

Palisade's 7.x releases are supported on Microsoft Office 2007 and newer, running on Windows XP and newer.

For older releases, see the compatibility charts below. If you have an older version and need to upgrade for compatibility with Microsoft Office or Windows, please see Upgrading Palisade Software. Customers with a current maintenance agreement can receive the upgrade to our latest versions at no charge; others please contact your Palisade sales manager.

Please note: Some functions in our software may work in some Office or Windows version that are not supported. But some functions will not work, or not work correctly, not necessarily with an obvious failure mode. We strongly recommend against running our software with unsupported Office or Windows versions, and we cannot assist with troubleshooting on unsupported platforms.

Hardware:

Please see Hardware Requirements or Recommendations.

Microsoft Office Versions:

Palisade products with these version numbers require Microsoft Office for Windows to be installed on the same computer. Mac users, please see @RISK on the Apple Mac. Lotus, OpenOffice, LibreOffice, and StarOffice products are not supported.

Palisade version:7.x6.3
6.2
6.1
6.05.75.5.15.5.0
5.0
4.5.7
1.0.9
4.1.4r34.1.4r24.1.4
Excel 2016, build
16.0.4229.1002 or newer
         
Excel 2013 32- or 64-bit        
Excel 2010 64-bit      
Excel 2010 32-bit     
Excel 2007   
Excel 2003    
Excel 2002/XP      
Excel 2000      
Project 2016, build
16.0.4229.1002 or newer
         
Project 2013 32- or 64-bit        
Project 2010 64-bit        
Project 2010 32-bit      
Project 2007     
Project 2003     
Project 2002/XP        
Project 2000        

Notes:

  • In releases 6.0 and above, one Palisade installer works with both 32-bit Excel and 64-bit Excel. Excel is required; Project is optional.
  • For Click-to-Run and Office 365, see Click-to-Run and Office 365 with Palisade Software.
  • With @RISK 7.0, if you have Project 2007 you may need to apply the patch mentioned in this article.
  • To check your version of @RISK for Project within 4.1.4, navigate to the Palisade installation folder, then to subfolder RISKPJ41, and double-click the Version History file.

Windows Versions:

Palisade version:7.x6.3
6.2
6.1
6.0
5.75.5
5.0
@RISK for
Project
4.1.4r3
4.1.4r2
4.1.4
RDK/BDK/
EDK/RODK
4.1.2
Windows 10    
Windows 8.1   
Windows 8 
Windows 7
Windows Vista
Windows XP
Windows Server See notes below.
Windows RT Not supported.

Notes:

  • Windows Server versions are not listed in the chart, because we have not done extended Quality Assurance of our end-user software with any Windows Server version. We are not aware of any incompatibilities between any Windows Server version and any version of our software.
  • Vista and above: Right-click the installer and select Run as Administrator; simply double-clicking may not work. After install and activation, the applications do not need admin rights.
  • All of our installers work in 32-bit and 64-bit Windows; but the RDK, BDK, EDK, and RODK must run in 32-bit processes. In 64-bit Windows, all products install in C:\Program Files (x86).
  • Windows 8.1 with our 6.0 and 6.1 installers: Please see Installing Palisade Software 6.0 or 6.1 in Windows 8.1 before installing.
  • Windows 8 with our 5.7 and 6.0 installers: Please see Installing Palisade Software 5.7 or 6.0 in Windows 8 before installing.
  • Palisade's Server Manager for network licenses is compatible with Windows XP and later, including Windows Server 2003–2016.

If you have a system with a standalone or enterprise version of our software, before you upgrade Windows, please deactivate the software to preserve the license; then reactivate it after upgrading. See Transferring Standalone Software 6.x/7.x to a New Computer or Transferring Standalone Software 5.x to a New Computer for the transfer procedure.

UNIX:

At the present time, Palisade products are not supported on UNIX or Linux.

Last edited: 2017-02-24

1.2. Click-to-Run and Office 365 with Palisade Software

This article summarizes Click-to-Run (CTR) and other deployment methods as they relate to Palisade software. Click-to-Run is not a version of Microsoft Office; it is a method of deployment, of getting the program to run on your computer.

Click-to-Run in Office 2013/2016 is implemented in a different way from Click-to-Run in Office 2010. See also these Microsoft articles:

  • For Office 2013/2016: Overview of Click-to-Run — though the article mentions only Office 2013, the sidebar at left identifies it as an Office 2016 deployment guide.
  • For Office 2010: What is Click-to-Run? (via www.archive.org)

Does Palisade software work with Microsoft Office 365?

Office 365 isn't actually a product; it's a subscription-based method of licensing for many products, including Office 2013 or 2016, Office Online (formerly Office Web Apps), and Office Mobile (formerly Pocket Office). Of that list, Palisade add-ins work only with Office 2013 or Office 2016.

Office 2013/2016 with Office 365 licensing has two deployment methods, Click-to-Run and Office On Demand. Click-to-Run is fine; Office On Demand will not work with many add-ins, including Palisade add-ins. (Microsoft ended Office On Demand in November 2014; see We're making some changes to Office 365 ProPlus.)

How can I tell if I have Office 2013/2016 Click-to-Run?

Method 1: In Excel, click File » Account, and then "look at the options under Office on the right. If you see Office Updates with an Update Options button next to it, just above About Excel, you have a Click-to-Run version. If you see only About Excel, but nothing about updates, you have an MSI version," meaning that it is installed locally on your computer like most programs. (Source: Click to run, CTR, Office 365, Office on Demand. What does it all MEAN? — not an official Microsoft page, but this information matches our testing. The author was talking about PowerPoint, but I substituted Excel because the information is the same.)

Method 2: If Office 2013 is installed in the default location, which it almost always is, you can tell by its location whether it is compatible with Palisade software:

  • Compatible deployment of Office 2013 CTR: C:\Program Files\Microsoft Office 15\Root\Office15\Excel.exe.
  • Compatible deployment of Office 2016 CTR: C:\Program Files\Microsoft Office 16\Root\Office16\Excel.exe.
  • Full MSI install of Office 2013, also compatible: C:\Program Files\Microsoft Office\Office15\Excel.exe or C:\Program Files (x86)\Microsoft Office\Office15\Excel.exe.
  • Full MSI install of Office 2016, also compatible: C:\Program Files\Microsoft Office\Office16\Excel.exe or C:\Program Files (x86)\Microsoft Office\Office16\Excel.exe.
  • An incompatible deployment of Office 2013/2016 On Demand will be under C:\Users\username\Microsoft Office 15\Root or C:\Users\username\Microsoft Office 16\Root — notice that the path begins C:\Users.

Microsoft's own article Update Office 2013 or Office 365 lists Click-to-Run version numbers for Office 2013.

If I have Office 2013/2016 Click-to-Run, Web Apps, or On Demand, can I run Palisade software?

The answer is Yes for Office 2013/2016 Click-to-Run. We tested build 15.0.4551.1011, and it worked with our software; we haven't seen any problems with newer builds. If you have an earlier build of Office 2013 Click-to-Run, and you have any problems with our software, please update your Office 2013 to the current build.

Released versions of Office 2016 Click-to-Run work with releases 7.x of Palisade software.

The Office On Demand deployment of Office 2013 is not compatible with our software. Office Web Apps (now called Office Online) have a different architecture from Excel and do not support Visual Basic for Applications, which is needed by our add-ins. Microsoft advises us that you should contact Microsoft directly for assistance in changing any of those into a deployment that is compatible with add-ins. However, there is also an article on Microsoft's Web site: How to Get the Full Installation of Microsoft Office 2013.

How can I tell if I have Office 2010 Click-to-Run?

The easiest way is to open Computer or My Computer. If you have a Q: or R: drive that you did not create yourself, if was most likely created by installing a Click-to-Run Office 2010.

If I have Office 2010 Click-to-Run, can I run Palisade software?

No. According to Click-to-Run: Known issues, "Many add-ins might not function as expected when used with Click-to-Run. You might see error messages stating that an add-in failed to load or couldn't be found."

Microsoft's advice in this case is to follow the step-by-step procedure in Click-to-Run: Switch to using an MSI-based Office edition. If you need assistance with the process, please contact Microsoft.

See also: Windows and Office Versions Supported by Palisade.

Last edited: 2015-12-31

1.3. Hardware Requirements or Recommendations

Language versions:

Applies to: All products, workstation or client software
(For network server system requirements, please see the Guide for Administrators.)

How much RAM do I need to run @RISK and your other software? How powerful a CPU is recommended? How many cores do I want?

How much RAM and how much processor speed are "enough" depends on many factors: the complexity of your model, what other applications and processes are running, which Windows version and which Office version you have, your own requirements for turnaround, and so on. And the best configuration today may no longer be the best tomorrow, when your needs may have changed and new hardware is available. But we can give some general guidelines.

The answer to the question of minimum configuration is simple: If you can run Microsoft Office on a Windows machine, you can run our software. That said, more RAM is good, a faster processor is good, and more CPUs (for @RISK simulations) are usually good.

For memory requirements, please see Memory Used by @RISK Simulations. Remember that the computer is not just running a simulation: Windows itself and your other programs will also need memory.

Multiple CPUs, such as a dual or quad core processor, will speed up simulations with some releases of @RISK; our other products use only one CPU. Please see CPUs used by @RISK for more on multiple CPUs.

There's an interaction between a sufficient amount of RAM and the number of CPUs (cores) used by @RISK in a simulation. Each core in a multi-CPU simulation runs its own copy of Excel, and therefore the more cores you use, the more RAM you need. If you run your simulation with multiple CPUs enabled, then more cores is usually good; with multiple CPUs disabled, you're using only one core, and you'll want it to be as fast as possible. In either case, during a simulation bring up the Windows Task Manager with Ctrl-Shift-Esc, select the Processes tab, then View » Select Columns to select "Memory - Peak Working Set". Observe how much RAM Excel (and @RISK) use during a simulation. If using just one core, then make sure you have that much RAM (plus 1 GB or so for Windows), and if using multiple cores, multiply that amount of RAM by the number of cores.

Disk space is unlikely to be an issue with any modern computer. A complete install of the DecisionTools Suite is under half a GB as of this writing (July 2015, 7.0.0). For best functioning of Windows, you do want a minimum of 10% free space on your disk, and more free space is better.

See also:

Last edited: 2015-08-13

1.4. Office 2016 and Palisade Software

Applies to:
The DecisionTools Suite, releases 7.x
@RISK, releases 7.x
BigPicture, releases 1.x
Evolver, releases 7.x
NeuralTools, releases 7.x
PrecisionTree, releases 7.x
StatTools, releases 7.x
TopRank, releases 7.x

Is your software compatible with the preview versions of Excel and Project 2016?

Palisade software products beginning with release 7.0.0 do support Office 2016. If you have a 1.x–6.x release and want to use Office 2016, you will need to upgrade your Palisade software.

See also:

Last edited: 2016-07-06

1.5. Office 2013 and Palisade Software

Applies to: All Palisade end-user software

Is your software compatible with Excel 2013 and Project 2013?

Since release 6.1, issued in February 2013, our software has been fully compatible with Excel 2013, provided that Excel is fully installed on the local computer. For more, please see Click-to-Run and Office 365 with Palisade Software.

If you have an earlier release of @RISK or other Palisade software, please see Upgrading Palisade Software to obtain the latest release.

See also:

Last edited: 2016-07-06

1.6. @RISK in the Cloud (Amazon Workspaces)

Disponible en español: @RISK en la Nube (Amazon Workspaces)
Disponível em português: @RISK na nuvem (Amazon Workspaces)

Applies to: @RISK, Evolver, NeuralTools, PrecisionTree, StatTools, TopRank, releases 6.0 and newer

We would like to move to a cloud-based computing environment.  Do you have a cloud-enabled version of @RISK or other Palisade software?

We have tested @RISK in the common cloud environment, Amazon Workspaces. As with any remote login scenario, a regular standalone license cannot be used in the cloud. A Concurrent Network license does work. We know of no technical reason that would prevent a Concurrent Network license from working in similar virtual-machine configurations in the cloud.

You would install both server and client software on the cloud server.  There is no need to install the client software on end users' real machines, though you could. For more, please see Citrix and Remote Desktop? (7.x) or Citrix and Remote Desktop Services (6.x).

As always, we encourage you to contact your Palisade sales manager for a test license so that you can make sure the product works to your satisfaction in your targeted environment.

See also: Windows and Office Versions Supported by Palisade

Last edited: 2015-06-08

1.7. @RISK with SharePoint or OneDrive for Business

Applies to: All products

Can I use @RISK (BigPicture, Evolver, NeuralTools, PrecisionTree, StatTools, TopRank) with SharePoint or with OneDrive for Business?

Yes to both. Just open your Excel files in the desktop version of Excel. There are multiple paths to do that, and they are nicely shown in Microsoft's video Viewing and editing documents in OneDrive for Business. Although you can make some edits to your Excel file in your browser through OneDrive for Business, it's not possible to run @RISK or other Palisade software in a Web browser.

If you're using @RISK with a project file, you may need to update the link to the project file. In @RISK, click Project » Project Settings » General. Click the Change button, and browse to the location of your project file. If you're not sure where OneDrive or SharePoint has stored the project file, open it in Microsoft Project, click File » Info and look for the location near the top of the Info window, just below the project file's name.

Note: OneDrive and OneDrive for Business are not the same. OneDrive for Business (formerly SkyDrive Pro) integrates with Microsoft Office, and OneDrive (formerly SkyDrive) does not. For details of the differences, please see What is OneDrive for Business?

Last edited: 2016-04-26

1.8. @RISK on the Microsoft Surface

Disponible en español: @RISK en Microsoft Surface
Disponível em português: @RISK no Microsoft Surface

Applies to: @RISK, Evolver, NeuralTools, PrecisionTree, StatTools, TopRank, releases 6.0 and newer

Do the new Microsoft Surface tablets support @RISK and other Palisade software?

Surface Pro runs Windows 8 and Office, and Palisade software is fully compatible with Windows 8. So Palisade software is fully compatible with the Surface Pro, just as it is with any Windows laptop.

The original Surface, which runs Windows RT, is not compatible with our software.

As always, we encourage you to test the software yourself with a trial version, to verify that the product works to your satisfaction with your spreadsheet models in your targeted environment. If you presently have our software on your desktop computer and want to add it to your Surface, please contact your Palisade sales manager about an auxiliary license (available in some regions).

See also: Windows and Office Versions Supported by Palisade.

Last edited: 2015-07-24

1.9. @RISK on the Apple Mac

Disponible en español: @RISK en Apple Mac
Disponível em português: @RISK no Apple MAC

Applies to: BigPicture, @RISK, Evolver, NeuralTools, PrecisionTree, StatTools, TopRank, releases 6.0 and newer

Can I install @RISK and other Palisade software on a Mac?

Yes, but in Windows. Microsoft Office for Mac is not supported.

Palisade software is supported in these Windows environments hosted on the Mac:

  • Windows XP through Windows 10 running using BootCamp.
  • Windows XP through Windows 10 emulation using Parallels, VirtualBox, or VMWare. (Parallels users, launch Microsoft Excel for Windows in Parallels before launching @RISK or any of the DecisionTools. To avoid the need to launch Excel first, use the Registry editing technique described in Which Version of Excel Is Opened by Palisade Software?)

If you have a Mac, you might like to review the Apple Store's article Mac Basics — Windows on a Mac.

See also: Windows and Office Versions Supported by Palisade

Last edited: 2017-01-17

1.10. @RISK on a Cluster

Disponible en español: @RISK en Cluster
Disponível em português: @RISK em um Cluster

Applies to: @RISK 5 and newer

Can RISK share out a simulation among multiple computers, using HPC Services for Excel or other technology?

@RISK 5, 6, and 7 do not support clustered computers or other forms of distributed computing. For lengthy simulations, we recommend running @RISK Industrial Edition on a computer with plenty of RAM and a sufficient number of fast CPUs.

See also: CPUs Used by @RISK

Last edited: 2016-04-26

1.11. @RISK and Application Virtualization

Disponible en español: @RISK y Aplicación Virtualización
Disponível em português: @RISK e virtualização de aplicação

Applies to:  All products

PRELIMINARY INFORMATION — SUBJECT TO CHANGE

Is Palisade software compatible with App-V, ThinApp, XenApp, and other virtualization software options?

We have installed XenApp on a local server and run some informal tests of our software under XenApp. We also did a quick test of @RISK under App-V. In both cases our tests succeeded: our software installed without issue and the functions we tried worked. However, Palisade software has not gone through Quality Assurance testing in those environments, and therefore they are not officially supported. We do not have any experience with ThinApp at this time. We will be looking at all of these technologies in the future to make a complete determination of compatibility.

If you're contemplating deploying one of these platforms, we encourage you to perform your own testing and determine that the software features you need will work correctly. Palisade will be happy to give you a limited-time test license so that you can perform this testing.

Virtualization is not compatible with standalone licenses, and will require a Concurrent Network license.

Last edited: 2016-07-25

1.12. 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 you have .NET 4.5, 4.5.x, 4.6, or 4.6.x, 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

1.13. 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

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

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

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

Question:
Are there any prerequisites for installing releases 5.x of Palisade software?

Response:
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 just 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 the following components yourself before running our installer.

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

(1) Microsoft Windows Installer 3.1 or later

(2) Microsoft .NET 2.0, 1.1, or both

  • All products 5.7 and later require .NET 2.0 only.
  • The DecisionTools Suite 5.5.1 and earlier require both .NET 1.1 and 2.0.
  • @RISK, Evolver, PrecisionTree, and StatTools 5.5.1 and earlier require .NET 2.0 only.
  • NeuralTools 5.5.1 and earlier require .NET 1.1 only.

(.NET 2.0 is already installed in Windows 7 and may be already installed in earlier Windows. For Windows 8 with Palisade 5.7 software, see Installing Palisade Software 5.7 or 6.0 in Windows 8.)

(3) Microsoft Visual C++ 2005 Redistributable

(4) SQL is optional with @RISK and the DecisionTools Suite (all 5.x releases); it is not used with Evolver, NeuralTools, PrecisionTree, StatTools, or TopRank. If installing @RISK or the DecisionTools Suite, you may or may not want to install SQL, depending on how your users will use @RISK. Please see SQL—Do I Need to Install It? for more.

last edited: 2014-01-17

1.15. Installing Palisade Software 6.0 or 6.1 in Windows 8.1

Disponible en español: Instalación del software de Palisade 6.0 o 6.1 en Windows 8.1
Disponível em português: Instalando o Software Palisade 6.0 ou 6.1 no Windows 8.1

Applies to:
      The DecisionTools Suite releases 6.0 and 6.1 under Windows 8.1
      @RISK releases 6.0 and 6.1 under Windows 8.1
      Evolver releases 6.0 and 6.1 under Windows 8.1
      NeuralTools releases 6.0 and 6.1 under Windows 8.1
(PrecisionTree and StatTools are not affected.)

If you're eligible to upgrade to a later release, just follow the instructions in Upgrading Palisade Software and your installer will work with Windows 8.1.

The rest of this article applies to users of 6.0 or 6.1 who are not eligible to upgrade.

Palisade software releases 6.0 and 6.1 require Microsoft .NET 2.0. In Windows versions prior to Windows 8, either this component was already present in Windows or our installers installed it automatically. Windows 8 and 8.1 architecture is different, and .NET 2.0 is now part of "Microsoft .NET Framework 3.5", which is not part of our installer.

Before installing any of the Palisade products mentioned above in Windows 8.1, check whether .NET Framework 3.5 is installed:

  1. Open Control Panel. (Move the mouse to the lower right corner of the desktop and select Settings » Control Panel.)
  2. Click the Programs category or the Programs and Features icon.
  3. Click Turn Windows features on or off.
  4. In the list, find .NET Framework 3.5 and see whether it is installed. A check mark or black square indicates that it is installed.

If .NET Framework 3.5 is installed, you can close Control Panel and run the Palisade installers. If .NET Framework 3.5 is not installed, install it using one of these two methods:

Installing .NET Framework 3.5 in Control Panel:

  1. In the list of Windows features, click the box next to .NET Framework 3.5.
  2. Confirm that you want to Download from Windows Update, which will let Windows download and install the required files.
  3. If the installation of .NET Framework 3.5 succeeds, you can then install the Palisade software.

On some computers, this process will not finish successfully. For instance, if you have no Internet connection then Windows Update cannot run. Also, certain Windows settings redirect Windows Update to a different location and prevent the update from running. (If you receive a message that you have no Internet connection, when in fact you do, that is the explanation.) Whatever the reason for failure, you can use Palisade's installer instead.

Installing .NET Framework 3.5 with a Palisade installer:

(This will work with 32-bit or 64-bit Windows 8, including 8.1.)

  1. Download from http://download6.palisade.com/dotNET/35 to any computer. In your browser, click Save, not Open or Run.
  2. Copy the file to the computer where you intend to install the Palisade software. Right-click the file, select Run as administrator, and follow the instructions.
  3. After the installation of .NET Framework 3.5, you can install the Palisade software.

last edited: 2013-09-17

1.16. Installing Palisade Software 5.7 or 6.0 in Windows 8

This article relates to releases that are no longer sold, but it is retained for the benefit of our customers with existing licenses.

Disponible en español: Instalación de Palisade Software 5.7 o 6.0 en Windows 8
Disponível em português: Instalando o Software Palisade 5.7 ou 6.0 no Windows 8

Applies to:
        The DecisionTools Suite releases 5.7 and 6.0 under Windows 8
        @RISK releases 5.7 and 6.0 under Windows 8
        Evolver releases 5.7 and 6.0 under Windows 8
        NeuralTools releases 5.7 and 6.0 under Windows 8
(PrecisionTree and StatTools are not affected.)

If you're eligible to upgrade to the current release, just follow the instructions in Upgrading Palisade Software and your installer will work with Windows 8.

The rest of this article applies to users of 5.7 or 6.0 who are not eligible to upgrade.

Palisade software releases 5.7 and 6.0 require Microsoft .NET 2.0. In Windows versions prior to Windows 8, either this component was already present in Windows or our installers installed it automatically. Windows 8 architecture is different, and .NET 2.0 is now part of "Microsoft .NET Framework 3.5", which is not part of our installer.

Before installing any of the products mentioned above in Windows 8, check whether .NET Framework 3.5 is installed, as follows:

  1. Open Control Panel. (Move the mouse to the lower right corner of the desktop and select Settings » Control Panel.)
  2. Click the Programs category or the Programs and Features icon.
  3. Click Turn Windows features on or off.
  4. In the list, find .NET Framework 3.5 and see whether it is installed. A check mark or black square indicates that it is installed.

If .NET Framework 3.5 is installed, you can close Control Panel and run the Palisade installers. If .NET Framework 3.5 is not installed, install it using one of these two methods:

Installing .NET Framework 3.5 in Control Panel:

  1. In the list of Windows features, click the box next to .NET Framework 3.5.
  2. Confirm that you want to Download from Windows Update, which will let Windows download and install the required files.
  3. If the installation of .NET Framework 3.5 succeeds, you can then install the Palisade software.

On some computers, this process will not finish successfully. For instance, if you have no Internet connection then Windows Update cannot run. Also, certain Windows settings redirect Windows Update to a different location and prevent the update from running. (If you receive a message that you have no Internet connection, when in fact you do, that is the explanation.) Whatever the reason for failure, you can use Palisade's installer instead.

Installing .NET Framework 3.5 with a Palisade installer:

(This will work with 32-bit or 64-bit Windows 8, including 8.1.)

  1. Download from http://download6.palisade.com/dotNET/35 to any computer. In your browser, click Save, not Open or Run.
  2. Copy the file to the computer where you intend to install the Palisade software. Right-click the file, select Run as administrator, and follow the instructions.
  3. After the installation of .NET Framework 3.5, you can install the Palisade software.

last edited: 2014-03-14

1.17. Permissions Needed to Install and Run the Software

Disponible en español: Permisos Necesarios para Instalar y Ejecutar el Software
Disponível em português: Permissões necessárias para instalar e executar o Software

Applies to: All products, all releases

@RISK and other Palisade products run on a standard user profile, don't they? Some companies limit all employees to the basic user profile and withhold "power user" access for routine work. These companies want Palisade software to work on the plain user profile rather than change company policy.

We need to distinguish between installing the software and running the software.

To run the software, almost any account is sufficient. You need only the typical limited permissions, such as being able to create files in the system TEMP folder, to view the folder where the Palisade software was installed, and to read and write to HKEY_CURRENT_USER in the System Registry. A Windows 7 "regular user" should have no difficulties.

To install the software, you need full administrative rights. Some examples include the ability to add and change System Registry keys including HKEY_LOCAL_MACHINE, and the ability to write to files in the Windows system folder. (That's not a complete list.)

Many companies make their users administrative users, but with some particular privileges removed. If that's your situation, please ask an IT person to do the installation for you. Remember, you need full administrative rights.

After installing the software, you will need to activate the software (applies to standalone versions and Enterprise workstations). This is a security measure, similar to what Windows XP does, and it prevents one copy from being installed and run on multiple computers. We recommend that the activation be done in the same full administrator account that installed the software; it will then be authorized for all Windows accounts on that computer.

Last edited: 2012-09-02

2. Configuring Excel

2.1. Should I Install 64-bit Excel?

Applies to: All products

Does @RISK come in a 64-bit edition?

With recent versions of @RISK and all our other tools, the installer automatically detects 32-bit Excel or 64-bit Excel and works with it. There's no need for separate Palisade installers for 32-bit and 64-bit code.

I currently have 32-bit Excel. If I switch to 64-bit Excel, will I get faster performance?

In most situations, no. If you work with large simulations in @RISK, more than 2 GB★ of data, you may benefit from 64-bit Excel. See Memory Used by @RISK Simulations to estimate the size of your simulation data. Most @RISK models will not run faster in 64-bit Excel. The same is true for the other tools: unless you have a really massive workbook, larger than 2 GB★, you will not see faster performance from 64-bit Excel.

64-bit Office is recommended when you have gigabytes of data and you have enough physical memory to store it, because then the data can all be held in RAM without being paged out to disk. There is no speed improvement from 64-bit code as such, only from holding data in RAM and not paging it out to disk. If your data size is under 2 GB★, you can more easily hold all data in RAM by simply not running other memory-hungry applications at the same time.

In Choose the 32-bit or 64-bit Version of Office 2016, which actually applies to Office 2010–2016, Microsoft says "We recommend the 32-bit version of Office, because it helps prevent compatibility issues with most other applications, especially third-party add-ins." For this reason, by default Office installs itself as a 32-bit application, even in 64-bit Windows. The same article warns that third-party add-ins and controls may not work with 64-bit Excel. Palisade software works with 64-bit Excel, but not all other add-ins do.

Microsoft's article 64-bit Editions of Office 2010 says, "this additional capacity is needed only by those Microsoft Excel users who require Excel spreadsheets that are larger than 2 gigabytes★ (GB). The 32-bit version of Office 2010 provides the same functionality and is also compatible with 32-bit add-ins." Later, the article says that 64-bit "Project 2010 provides improved capacity, especially when you are dealing with many subprojects to a large project." Again, unless you are simulating really massive projects there is no need for 64-bit Office.

★ In June 2016, Microsoft released a Large Address Aware update to Excel 2013 and 2016, which changed the 2 GB limit on address space. With this update installed, 32-bit Excel in 64-bit Windows will automatically be able to use a 4 GB address space. If you have 32-bit Excel 2013 or 2016 in 64-bit Windows, getting this update is a much simpler solution than installing 64-bit Excel.

The same update increases the address space of 32-bit Excel 2013 and 2016 to 3 GB in 32-bit Windows, but to activate it you must set an option in your boot file. Please read the Large Address Aware article carefully before you set the option in your boot file, because that may cause other system issues.

Last edited: 2016-08-12

2.2. Visual Basic for Applications

Disponible en español: Visual Basic para Aplicaciones

Applies to: Palisade software used with Excel, releases 5.x–7.x

Does Palisade software use Visual Basic? How do I install that on my computer?

There are actually two things called Visual Basic: Visual Basic for Applications, which is part of Microsoft Office, and the Visual Basic 6 Runtime, which is part of Windows. Both are needed for most Palisade software; this article is about Visual Basic for Applications (VBA).

All Palisade products except the Palisade Custom Runtime use Visual Basic for Applications (VBA), which is a component of Excel in Microsoft Office. In a normal install of Office, VBA is installed automatically. However, sometimes people doing a custom install of Microsoft Office will change options to exclude VBA. Excel installed in that way will not support our add-ins.

To make sure you have VBA installed, launch Excel and press Alt+F11. If the Visual Basic Editor comes up, you have VBA. If it does not, close Excel and enable that feature in Office. The exact process varies with Office and Windows versions, but it will be something like this:

  1. In Control Panel » Programs and Features, locate Microsoft Office, right-click it, and select Change.
  2. On the next panel, select Add or Remove Features.
  3. Under Office Shared Features, set Visual Basic for Applications to Run from My Computer. Click Continue.
  4. If the installer says that you need to restart Windows, do so. If the installer doesn't prompt you to restart Windows, then there is no need.

See also: Visual Basic 6 Runtime

Last edited: 2017-05-16

2.3. Recommended Option Settings for Excel

Applies to: All products, when used with Excel 2013 and 2016

Are there any special settings I need to make in Excel to use it with @RISK (BigPicture, Evolver, ...)?

In Excel 2007 or later, ensure that multi-threaded calculation is enabled.

  • Excel 2010–2016: Click File » Options » Advanced » Formulas » Enable multi-threaded calculations.
  • Excel 2007: Click the round Office button and then Excel Options » Advanced » Formulas » Enable multi-threaded calculations.

Note: Though this is a global Excel option, it can also be changed by opening a workbook where the option was set differently. Check the status of the option while your particular workbook is open.

In addition, if you have Excel 2013 or 2016, and you have Palisade release 7.0.1 or earlier, you should disable the Excel start screen, as follows:

  1. Launch Excel. It doesn't matter whether you open a workbook or not.
  2. Click File » Options » General.
  3. Remove the check mark from the last option, "Show Start screen".
  4. Click OK and close Excel. (You must close Excel after clicking OK. After this, it will remember the setting.)

We recommend this because, if the Excel start screen is enabled, some add-ins may not load correctly. This can lead to intermittent errors at any point during your Excel session. By un-checking the option, you don't lose any functionality, since you can always click the File tab in the Excel menu.

See also: Getting Better Performance from Excel

Last edited: 2017-02-02

2.4. Excel Macro Security Settings

Applies to:  All products that run as Excel add-ins

I know that Palisade add-ins include some macro code, but I am concerned about security.  How should I set up Excel for the greatest possible security that is compatible with Palisade software?

Recent versions of our products (starting in about 2003) are digitally signed.  Excel treats digitally signed macros differently from those that are not digitally signed, and this lets you maintain a higher level of security while still running macros from trusted sources like Palisade.

With digitally signed versions of our software, here are the recommended settings:

  • In Excel 2010 or newer, click File » Options » Trust Center » Trust Center Settings » Macro Settings. Select "Disable all macros except digitally signed macros" or "Disable all macros with notification" and click OK.

    In Trust Center Settings » Add-ins, if "Disable all Application Add-ins" has a check mark, remove it.

    Also in Trust Center Settings » Add-ins, "Require Application Add-ins to be signed by Trusted Publisher" should not be checked (ticked). If you do need this option checked, add your Palisade folder as a trusted location, as follows. In Excel Options » Trust Center » Trust Center Settings » Trusted Locations, click "Add new location". Browse to the Palisade folder — usually C:\Program Files (x86)\Palisade or C:\Program Files\Palisade — select "Subfolders of this location are also trusted", and click OK.

  • In Excel 2007, click the round Office button, then Excel Options » Trust Center » Trust Center Settings » Macro Settings. Select "Disable all macros except digitally signed macros" or "Disable all macros with notification" and click OK.

  • In Excel 2003, click Tools » Macro » Security and select Medium or High. In the same dialog, on the Trusted Publishers tab, make sure that "Trust all installed add-ins and templates" has a check mark. Click OK.

If you have versions of our products that were released before 2003, you will need to set macro security to Low in Excel 2003, and you will not be able to run those older products at all in Excel 2007 or later.

See also: Group Policy and Office Customization Tool Settings: Technical Reference

Last edited: 2014-11-17

2.5. Excel Shows Palisade Add-ins as Inactive

Disponible en español: Add-Ins de Palisade en la Lista de Excel
Disponível em português: Suplementos da Palisade na lista do Excel

Applies to: All Palisade software, releases 5.x–7.x

Excel 2007 and newer:
I have installed one or more of @RISK, BigPicture, Evolver, NeuralTools, PrecisionTree, StatTools, and TopRank. They are in Excel's list of Inactive Application Add-ins. Is something wrong?

Excel 2003 and older:
I have installed one or more of @RISK, Evolver, NeuralTools, PrecisionTree, StatTools, and TopRank. I notice that their add-ins are listed in Excel's Tools » Add-ins list, but the boxes are not checked (ticked). Is something wrong?

Nothing is wrong. It is normal for @RISK and our other add-ins to show in Excel as inactive, even when they are running. (It is not normal for them to show as disabled. If any of our add-ins are in the list of Disabled Application Add-ins in Excel 2007 or newer, use the Manage control at the bottom to manage disabled items and re-enable them.)

Our add-ins need to be active only if you want our software to open automatically every time you open Excel. Please see Opening Palisade Software Automatically Whenever Excel Opens for more information and a caution relating to @RISK 6.0.

Additional keywords: Inactive add-ins, Inactive addins, Addins inactive, Add-ins inactive

Last edited: 2016-12-13

2.6. I Installed the Software But I Don't See It in Excel

 

This article has been withdrawn, because it overlapped almost completely with I've installed the software. Why don't I see it in Excel?

Please refer to that article, which now contains all information from both articles.

Last edited: 2017-04-04

2.7. Opening Palisade Software Automatically Whenever Excel Opens

Disponible en español: Apertura Del Software Palisade Automáticamente Cada vez que Inicia Excel
Disponível em português: Abrindo Software da Palisade junto com Excel

Applies to:
@RISK 5.x–7.x
Evolver 5.x–7.x
NeuralTools 5.x–7.x
PrecisionTree 5.x–7.x
RISKOptimizer 5.x only (For 6.x and newer, set @RISK to run automatically, not RISKOptimizer.)
StatTools 5.x–7.x
TopRank 5.x–7.x

There is never a requirement to add our add-ins or toolbars to Excel manually. Ordinarily, you open our software via a desktop shortcut if available, or through the start menu (All Programs or Programs and then Palisade DecisionTools). This can be done when Excel is already running, or when Excel is not running. If Excel is not running, our software will launch Excel automatically.

But some users prefer to double-click on workbooks (.XLS, .XLSX, .XLSM, etc.) to open Excel. In this case you must then start StatTools, @RISK, or our other software tools as a separate step. This article explains how to make any of our software tools open automatically, every time Excel opens. It's also possible to give this treatment to just one Excel workbook, if the workbook has macros enabled; see Setting References in Visual Basic.

Caution: If you plan on opening multiple instances of Excel, please do not configure our software to open automatically. Palisade software is not designed to run simultaneously in multiple instances of Excel, and you will get a message such as "Object initialized twice." (It's perfectly okay to have single instances of different Palisade applications running in the same instance of Excel, as long as they all have the same release number.)

Caution: A 5.x release, a 6.x release, and a 7.x release can coexist on the same computer, but they must not run at the same time. If you have one version starting automatically, don't run a different version until you first remove the first version from automatic startup.

For starting @RISK (Evolver, PrecisionTree, ...) automatically with Excel, please select your release below.

With releases 6.1–6.3 and 7.x:

  1. Launch the tool that you want to run automatically with Excel.

  2. In Excel 2010, 2013, or 2016, click File » Options » Add-Ins, then at the bottom of the page select "Manage Excel Add-Ins" and click Go.
    In Excel 2007, click the round Office button, then Excel Options, then Add-Ins, then at the bottom of the page select "Manage Excel Add-Ins" and click Go.
    In Excel 2003, with Palisade releases 6.x, click Tools » Add-Ins. (Excel 2003 is not compatible with Palisade releases 7.0 and newer.)

  3. You will see your currently running Palisade add-ins listed, along with any others that you have run previously. Put check mark(s) on the one(s) that you want to open automatically.
    Caution: Don't click the Browse button and go searching for add-ins; only the ones listed here are candidates.
    Exception: In 6.x/7.x, RISKOptimizer is part of @RISK. If you want RISKOptimizer to start every time Excel starts, tick the box for @RISK, not RISKOptimizer.

From now on, when Excel opens, the desired Palisade tool will open automatically with it. This applies when you double-click an Excel workbook or start Excel via a program shortcut.

If you change your mind later, go back to the Add-Ins list and uncheck the ones that you no longer want to load automatically. You will still be able to load them through the desktop icon or through the Windows Start button.

With release 6.0:

The above procedure will work for Evolver 6.0, NeuralTools 6.0, PrecisionTree 6.0, StatTools 6.0, and TopRank 6.0. However, it is not recommended for @RISK 6.0. @RISK 6.0 had a problem: If the @RISK or RISKOptimizer add-in is checked as described above, @RISK may crash at the end of a simulation that uses multiple CPUs. @RISK releases 6.1.1 and later do not have the problem.

With releases 5.5.1–5.7.1:

  1. Launch the tool that you want to run automatically with Excel.

  2. In Excel 2010 (no newer Excels), click File » Options » Add-Ins, then at the bottom of the page select "Manage Excel Add-Ins" and click Go.
    In Excel 2007, click the round Office button, then Excel Options, then Add-Ins, then at the bottom of the page select "Manage Excel Add-Ins" and click Go.
    In Excel 2003 or below, click Tools » Add-Ins.

  3. You will see your currently running Palisade add-ins listed, along with any others that you have run previously. Put check mark(s) on the one(s) that you want to open automatically.
    Caution: Don't click the Browse button and go searching for add-ins; only the ones listed here are candidates.

From now on, when Excel opens, the desired Palisade tool will open automatically with it. This applies when you double-click an Excel workbook or start Excel via a program shortcut.

If you change your mind later, go back to the Add-Ins list and uncheck the ones that you no longer want to load automatically. You will still be able to load them through the desktop icon or through the Windows Start button.

With release 5.0 or 5.5.0:

  1. Open just Excel (not @RISK).

  2. In Excel 2007, click the round Office button, then Excel Options, then Add-Ins, then at the bottom of the page select "Manage Excel Add-Ins" and click Go.
    In Excel 2003 or below, click Tools » Add-Ins.

  3. On the Add-Ins dialog, click Browse.

  4. In the window that opens, navigate to your @RISK installation folder. The most likely location is C:\Program Files\Palisade or C:\Program Files (x86)\Palisade, but it's possible that the Palisade software is installed elsewhere.

  5. Select the subfolder and double-click the add-in indicated in the table:

    To open this software automatically with ExcelSelect this folderDouble-click
    this file*
    And the add-ins list will show
    Evolver 5.0 or 5.5 Evolver5 Evolver.xla Evolver for Excel 5.0 or Evolver 5.5
    NeuralTools 5.0 or 5.5 NeuralTools5 NeuralTools.xla NeuralTools Add-In for Microsoft Excel or NeuralTools 5.5
    PrecisionTree 5.0 or 5.5 PrecisionTree5 PTree.xla PrecisionTree 2.0 or 5.5
    @RISK 5.0 or 5.5 RISK5 Risk.xla @RISK for Excel 5.0 or 5.5
    RISKOptimizer 5.0 or 5.5 RISKOptimizer5 RISKOpt.xla Evolver for Excel 5.0 or RISKOptimizer 5.5
    StatTools 5.0 or 5.5 StatTools5 StatTools.xla StatTools for Microsoft Excel or StatTools 5.5
    TopRank 5.0 or 5.5 TopRank5 TopRank.xla Toprank or TopRank 5.5
    *If you don't see the ".xla" file extension, choose the file with this name, right-click it, and select Properties. Verify that the type is Microsoft Office Excel Add-In, cancel the Properties dialog, and double-click the file.
  6. You are now back in the Add-Ins dialog, with a new entry checked, as shown in the last column of the table.

  7. If you wish, you can browse to additional Palisade add-ins to make multiple tools open automatically with Excel. (RISKOptimizer includes Evolver, so you can't open both of them automatically with Excel.) But add only the tools that you really do use almost every time you open Excel; otherwise you will just make Excel open slower for no good purpose.

  8. Click OK, then close Excel (File » Exit).

From now on, when Excel opens the desired Palisade tool will open automatically with it. This applies when you double-click an Excel workbook or start Excel via a program shortcut.

If you change your mind later, go back to the Add-Ins list and uncheck the add-in that you browsed to.

last edited: 2016-05-02

3. Configuring Windows

3.1. Making File Extensions Visible

What is a file extension?

Nearly all files in Windows have a "file extension", usually three or four letters after a dot. For example, a file called MyModel.xlsx has a file extension of XLSX. The file extension tells Windows what program to run when you double-click the file — for an XLSX file, that's Microsoft Excel. Most Windows installations are pre-configured to hide the file extensions, so a file actually called MyModel.xlsx would appear in Explorer as MyModel. You can right-click the file and select Properties » Details to see its full name, or look at the Type column in Explorer to find a description of the file type, such as Microsoft Excel Worksheet.

Why do I care?

Usually you don't. But you may need to send us a file of a type that your mailer rejects, or we may need to send you one. The standard way to do this is for the sender to change the extension to TXT, and the receiver to change it back to ZIP or REG or XLSM or whatever. If extensions are hidden, you can't do that, so you need a way to display file extensions.

How do I make file extensions visible so that I can change them?

In Windows 10 and Windows 8.1:

    1. Double-click This PC or any folder icon.
    2. Select the View tab of the ribbon.
    3. Check (tick) the File name extensions box.

In Windows 8:

    1. Double-click Computer or any folder icon.
    2. Select the View tab of the ribbon.
    3. Check (tick) the File name extensions box.

In Windows 7 and Vista:

    1. Double-click Computer or any folder icon.
    2. Click the down arrow next to Organize, and select Folder and search options. If you don't see Organize, press Alt+T, release the Alt key, and press letter O.
    3. In the Folder Options dialog, select the View tab.
    4. Remove the check mark from the box labeled Hide extensions for known file types. (It's a couple of lines below the first set of radio buttons.) Click OK.

In Windows XP:

    1. Double-click My Computer or any folder icon.
    2. In the menu, click Tools » Folder Options.
    3. In the Folder Options dialog, select the View tab.
    4. Remove the check mark from the box labeled Hide extensions for known file types. (It's just below the first set of radio buttons.) Click OK.

Additional keywords: Change file extensions, edit file extensions, filename extensions

Last edited: 2016-02-26

3.2. Virtual Memory Settings

Applies to: @RISK, all versions

Should I change my Windows virtual memory settings for use with @RISK simulations?

Left to manage virtual memory on its own, Windows will not go above 3 times your physical RAM, or 4 GB if you have less than 1.33 GB physical RAM. (Reference: "System-managed page files" in How to determine the appropriate page file size for 64-bit versions of Windows, accessed 2015-02-27.)

If you're running large simulations, "System managed" may not be the best choice. To find how much memory your simulation needs, see Memory Used by @RISK Simulations. You will want your page file size to be at least that much, plus more to allow for other programs. However, don't set it so large that your disk has little free space; that can degrade Windows performance.

To specify the size of the page file or virtual memory:

  1. Open System Properties:

    • In Windows 7 or 8, right-click Computer, select Properties, and select Advanced System Settings.
    • In Windows XP, open Control Panel and select System.
  2. On the Advanced tab, under Performance, click Settings » Advanced » Change.

  3. If "Automatically manage paging file size for all drives" appears, remove the check mark. (Windows XP doesn't have this box in the dialog.)

  4. Change "System managed size" to "Custom size". Set the initial and maximum size to the same number, so that Windows won't waste time resizing the page file during your simulation.  (You may or may not need to reboot after changing this setting; Windows will tell you if you do.)

  5. If you had to change the setting, click OK to close each screen; if the setting was already correct, click Cancel to close each screen.

Last edited: 2015-02-27

3.3. Group Policy and Office Customization Tool Settings: Technical Reference

Disponible en español: Política y Herramientas de Personalización de Office: Referencia técnica
Disponível em português: Políticas de Grupo e Configurações de Ferramentas de Personalização do Office: Referência Técnica

Which settings in the Group Policy Editor or Office Customization Tool are important for proper operation of @RISK and other Palisade add-ins to Excel?

Our software is designed to work with the default settings, but some organizations alter these. The attached file is a list of the settings that can interfere with operation of Palisade software.

Palisade Technical Support has a tool called PalDiagnostics that can diagnose problematic policy settings as well as other issues. A Palisade technical support representative can interpret the output of PalDiagnostics and suggest appropriate corrections.

See also:

Last edited: 2016-08-10

3.4. Visual Basic 6 Runtime

Disponible en español: Visual Basic 6 Runtime

Applies to: Palisade software used with Excel, releases 5.x–7.x

Does Palisade software use Visual Basic? How do I install that on my computer?

There are actually two things called Visual Basic: Visual Basic for Applications, which is part of Microsoft Office, and the Visual Basic 6 Runtime, which is part of Windows. Both are needed for most Palisade software; this article is about the Visual Basic 6 Runtime.

In a normal installation of Windows and Office, this is already present and there is no need to install it. This article tells you how to verify that you have it, and what to do if you don't.

All Palisade products except the Palisade Custom Runtime use the Visual Basic 6 Runtime—also known as the Visual Basic 6 Redistributable or Redistribution Pack—which has been part of Windows since Windows XP. The main file for the VB6 Runtime is MSVBVM60.DLL, located in C:\Windows\System32, C:\Windows\SysWOW64, or both.

  1. In File Explorer, locate the file and select Properties. On the Details tab, check the file version and verify that it is at least 6.0.9802 (for Windows XP) or 6.0.9815 (for Windows 7 through Windows 10). If it is outdated, download and install the latest. As of this writing (2016-12-02), the latest version is Service Pack 6, which was released in 2004. It's available at http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=24417.

    If it's up to date, but you're having a problem that referred you to this article re-register it with the following steps.

  2. Open the administrative command prompt. You must run this procedure in an administrative command prompt; even if you have administrative privileges, you cannot run this successfully via a Start » Run window.

  3. Enter one of these commands, depending on the actual location where you found MSVBVM60.DLL, and press Enter:
    • regsvr32 C:\Windows\SysWOW64\msvbvm60.dll
    • regsvr32 C:\Windows\System32\msvbvm60.dll

    It's okay if the file is not in both locations, as long as it's in at least one of them.

  4. You should get the response "DllRegisterServer in C:\Windows\SysWow64\msvbvm60.dll succeeded" or "DllRegisterServer in C:\Windows\System32\msvbvm60.dll succeeded". If you do, type EXIT to close the command prompt, and proceed to try @RISK or any of our tools. If the regsvr32 command gives any other response, please send a screen shot to Palisade Technical Support with your serial number, a reference to this article, and details of your original issue.

See also: Visual Basic for Applications

Last edited: 2017-05-16

3.5. Firewall Settings for Palisade Standalone Software

Disponible en español: Configuraciones del Firewall para los productos de Palisade

I want to block direct Internet access, and only open specific ports for specific applications.  Which I/O ports does your standalone software use?  Which sites, servers, or IP addresses?

During normal operation, our software doesn't require any Internet access at all.  It does try occasionally to check for updates so that it can notify you, but if it can't perform the check it will still function normally and won't display any error message.

An Automatic Activation or Automatic Deactivation, if you select that option, will try to communicate with our server. But if you have no Internet, or if the communication fails owing to your firewall or any other reason, you can always use the Manual option. With Manual Activation and Manual Deactivation, the software guides you to save an XML-type request file to a folder on your computer. You then email the file to us, or submit it on our Web site. Either way, you receive back a response file, which you load into the Palisade software on your computer to finish the activation or deactivation. (If the computer with the Palisade software has no email or Web access, you can copy the files to and from a computer that does. If security reasons prevent your exchanging XML files with Palisade, please contact Palisade Technical Support, and we will help you with another method of activation.)

How should I adjust my company firewall to allow automatic activations and deactivations?

This is not required if you use the Manual option mentioned above. But if you prefer to enable the Automatic options, here's how to do it.

Automatic Activation and Automatic Deactivation use port 80.  Make sure you allow both directions: from you to us, and from us back to you.  If the software can't communicate through port 80 with our server, you'll get a failure message and you can then use the Manual option or else register Palisade as a trusted site in your corporate firewall and/or the individual computer firewall.

If you need to specify servers, we recommend specifying *.palisade.com.  This is the most flexible method, and will still work whatever changes we may make in the future.

If your firewall won't let you use wildcards, specify service.palisade.com and service2.palisade.com.

If you must use IP addresses, as of June 2015 the IP addresses for those servers are 24.39.172.83 and 24.39.172.67.  However, we advise against using IP addresses, because these may change without notice.

See also: For network software (client and server), please see Network Ports and Firewalls (7.x) or Network Ports and Firewalls (6.x).

Last edited: 2015-10-29

3.6. Data Execution Prevention

How should I set DEP (Data Execution Prevention) for compatibility with Palisade software?

The simple answer is: don't. Windows default settings for DEP are just fine with Palisade software, but our software will not work with certain non-default settings. DEP policy can also be manipulated independently of the Windows policy, for example by using Microsoft's Enhanced Mitigation Experience Toolkit (EMET), an optional Windows component. We don't recommend changing DEP policy via EMET either.

Please read on for more about the compatibility of Palisade software with different Windows DEP policies and EMET policies.

A. Windows DEP Settings: WMIC and BCDEDIT

This command will check the DEP setting:

wmic OS Get DataExecutionPrevention_SupportPolicy

Either open a command prompt and type or paste that command, or open a Start » Run window and type or paste

cmd /k wmic OS Get DataExecutionPrevention_SupportPolicy

It will return one of these values:

2 OptIn (the Windows default) Only Windows system components and services have DEP applied.

3 OptOut DEP is enabled for all processes. Administrators can create a list of specific applications that will not have DEP applied.

1 AlwaysOn DEP is enabled for all processes.

0 AlwaysOff DEP is not enabled for any processes.

Our software should work with the default value 2 or the non-default values 0 and 3.

Only the value 1 is a problem. The value 1 turns DEP on for all processes. Palisade software can run with DEP on when the policy is set to 3, but the value 1 also turns off the setting called "ATL Thunk Emulation" for all processes. If Data Execution Prevention is On and ATL Thunk Emulation is Off, Palisade software will not run.

If the value 1 is returned, open an administrative command prompt. Enter this command:

bcdedit.exe /set {current} nx OptIn

Restart Windows — not just logging off and on, but a system restart — and use the wmic command again to verify that the value is now 2.

B. DEP Policy in EMET or Another Tool

DEP settings via EMET or another system tool can be a problem, even if wmic returns the desired value of 2. To test for this problem, download and run the attached program, StatusOfDataExecutionPrevention.exe.

Any result is fine, except for Data Execution Prevention = On with ATL Thunk Emulation = Off. That result indicates settings incompatible with our software. The bcdedit command in Part A should have fixed this. If it did not, then DEP has been set via a policy independent of the Windows settings, most likely via the EMET tool.

The possible DEP policies in EMET are similar to the Windows policies. If DEP is set to "Always On" in EMET, Palisade software will not run, just like with the Windows AlwaysOn policy (wmic value 1). However, EMET's "Application Opt Out" policy is different from the Windows OptOut policy (wmic value 3). Both of them turn DEP on for processes that are not on the list of exceptions. The difference lies in how they handle "ATL Thunk Emulation", which breaks Palisade software if set to off. The Windows OptOut policy doesn't turn ATL Thunk Emulation off, but EMET's "Application Opt Out" does turn ATL Thunk Emulation off on Windows 8.1 and higher.

Therefore, if DEP is set via EMET, and the EMET policy needs to be set to "Application Opt Out" for some reason, you will need to add some Palisade processes to the list of exceptions. You can find these processes in subfolders under your Palisade install folder, which by default is C:\Program Files (x86)\Palisade or C:\Program Files\Palisade. Under Palisade, look at the folder for each of your installed products, such as RISK7 or StatTools6. You want to disable DEP for each "OutOfProcess" executable file in each product folder. If you have the DecisionTools Suite, look in the folders for all the components: BigPicture (DecisionTools Suite 7 only), Evolver, NeuralTools, PrecisionTree, RISK, StatTools, and TopRank.

Last edited: 2017-01-11

3.7. PaaS or IaaS with PCR

Applies to: Palisade Custom Runtime

Is the Palisade Custom Runtime compatible with PaaS and IaaS?

Yes, PCR is compatible with PaaS (Platform as a Service) and IaaS (Infrastructure as a Service) solutions. But note that PCR will only work if the operating system used with PaaS or IaaS is Windows.

As always, we recommend testing in your specific target environment, early on in the development process.

Last edited: 2016-03-29

4. Optional Components

4.1. SQL — Do I Need to Install It?

Disponible en español: SQL – Es necesario instalarlo?
Disponível em português: SQL — Preciso instala-lo?

Applies to: @RISK 5.x–7.x

At the end of my install of @RISK or The DecisionTools Suite, I see the Finish button but I also see an option to install SQL.  How do I decide whether to install it or not?

SQL is optional.  You may or may not need it if you want to use the @RISK Library feature of @RISK's Professional and Industrial Editions. Only the @RISK Library feature depends on SQL; no other features of @RISK and none of the other DecisionTools Suite applications use SQL.

The @RISK Library lets you store customized probability distributions and simulation results. You can reuse these model components and share them with other users. (@RISK simulation results can also be stored in the Excel workbook or in an external .RSK5 file, but the @RISK Library makes it easier to manage them.) See "Library" in the video Guided Tour of @RISK; the Library is similar in other @RISK versions.

Here's your road map for deciding whether to install SQL:

  • If you don't want to use the @RISK Library feature, don't install SQL. (If you later change your mind and want to use the @RISK Library, you can install SQL then, with no need to reinstall @RISK.)

  • If you have @RISK Standard, don't install SQL. The @RISK Library feature that uses SQL is not available in @RISK Standard Edition.

  • If you want to use the @RISK library with @RISK 6.2.0 or later, you need SQL Server only on the computers that host SQL databases. If databases are on the local computer, it needs an SQL Server. If all databases are on remote computers, the local computer can have SQL Server or SQL Native Client. (The remote computers that host @RISK Library databases don't need @RISK.)
    See SQL Versions and Installation: SQL with @RISK 6.2 and later.

  • If you want to use the @RISK Library with @RISK 5.0 through @RISK 6.1.2, you need to install SQL Server on the local computer even if the database(s) will all be on remote computers.
    See SQL Versions and Installation: SQL with @RISK 6.1 and earlier.

See also: SQL for @RISK Library on Another Computer

Last edited: 2015-06-11

4.2. SQL Versions and Installation

Disponible en español: Versiones de SQL e instalación
Disponível em português: Versões e instalações do SQL

Applies to:  @RISK 5.x–7.x

Which version of SQL should I install to work with @RISK? Does it need to be a local install, or can I connect to a remote server?

You may or may not need to install SQL. The @RISK Library feature is the only dependency of @RISK on SQL; see SQL — Do I Need to Install It? If you do need to install SQL, please choose the right section below, because major changes were made with the release of @RISK 6.2.

SQL with @RISK 6.2 and newer:

@RISK Libraries can be on your local computer, remote computers, or a mix. If you want to create and use libraries on your local computer, you must have compatible SQL server software installed.  If you want to create and use libraries on a server or another computer, your local computer needs SQL server or SQL client software. The remote computer that hosts the databases must have compatible SQL server software and the operating system must be a Windows Server edition. (See also SQL for @RISK Library on Another Computer.)

Any Microsoft SQL Server software 2005 or later, including the free Server Express, will work with @RISK 6.2 and newer. On 32-bit Windows, you will install 32-bit SQL. On 64-bit Windows, we have seen 32-bit or 64-bit SQL work with @RISK in 32-bit or 64-bit Excel. Here are some of your options:

SQL with @RISK 6.1 and earlier:

The Library feature of @RISK is powered by a local install of SQL, even if all your @RISK Library databases are stored on a remote computer. This means that a compatible version of SQL is listed in Programs and Features or Add or Remove Programs in Control Panel, in the same list as @RISK or the DecisionTools Suite. In contrast to the SQL program, the databases can be local, remote, or a mix.

We have tested @RISK 5.x, 6.0, and 6.1 with Microsoft SQL Server 2005 Express and Microsoft SQL Server 2008 Express. Your options:

Last edited: 2015-06-11

4.3. Non-English Versions of Palisade 7.x Software

Applies to:  All products, release 6.1–6.3

Which localized versions are available?

Releases 7.x are localized for Chinese, English, French, German, Japanese, Portuguese, Russian, and Spanish.

How do I specify my preferred language?

You specify one of the languages as your preferred language in a dialog box at install time. Later, when running the application, the end user can change languages at any time through the Utilities » Application Settings dialog.

Can I specify a language in a silent or scripted install?

Yes. Please see Silent Install of Non-English 7.x Software.

Is a separate activation required for each language?

No, one Activation ID covers all available languages.

Is an Internet connection required when specifying or changing languages?

The program installer contains program text — menus, icons, dialogs, messages, windows, graphs, reports, and so on — for all localized versions, and all languages are installed regardless of your preferred language. The English and Spanish documentation files — help files, user manuals, and example spreadsheets — are also installed regardless of your preferred language. There is nothing to download when changing language to English or Spanish. There is also no need to download anything if you are content with the program in your language but the documentation files in English or Spanish.

For Chinese, French, German, Japanese, Portuguese, or Russian, the documentation files require a download. If you select one of those languages when installing the program, the installer will try to download the documentation files and install them for you. Likewise, if you change languages through the software's Utilities » Application Settings dialog, and the documentation files aren't already on your computer in that language, the software will try to download and install the documentation for you.

If the download of documentation fails for any reason, the program will operate in the specified language but the documentation will still be in English or Spanish. In that case, please contact Palisade Technical Support for a Language Pack. Include the software serial number and the three-digit software version from the Help » About screen in your email. The one Language Pack covers all six languages.

My Windows language is not one of the listed ones. Can I still use the software?

Yes, but you must install and run the program in English. (Exception: Software versions 7.0.0 and 7.0.1 do not function correctly with Windows in Korean.)

Additional keywords:  Local language support, International language setting, Localization

Last edited: 2017-02-17

4.4. Silent Install of Non-English 7.x Software

Applies to: All products, standalone or network versions, releases 7.x

I'm doing a silent install of your 7.x product. I'd like the application to come up automatically in our local language the first time it runs, without making the end user navigate an English-language menu to set the language. How can I do this?

For English or Spanish, install Part A only. For the other languages, install part A and then part B.

Part A: Do this for all languages.

You need the MSI installer for the appropriate product — @RISK, DecisionTools Suite, StatTools, etc. Palisade Technical Support can supply the installer on request; please include your serial number in your email so that we send you the right installer.

You will use the basic instructions for the MSI, depending on whether you're installing standalone software or a network client:

However, you will add a ProductLanguage parameter to the MSI command line to specify the target language. The installer itself will use the language currently selected in Windows, but the default for the end user application will be set to the product language you specify on the MSI command line:

  • For CN: ProductLanguage=2052
  • For DE: ProductLanguage=1031
  • For EN: ProductLanguage=1033
  • For ES: ProductLanguage=1034
  • For FR: ProductLanguage=1036
  • For JP: ProductLanguage=1041
  • For PT: ProductLanguage=1046
  • For RU: ProductLanguage=1049

Example: Standalone @RISK in Spanish:

msiexec /i Risk7-Setup.msi /qn ProductLanguage=1034
PALACTIVATIONID=RNA-7777777-AV3W7H-XYZ
USERNAME="Mary Smith" COMPANYNAME="Hometown Bank"

Example: @RISK Concurrent Network client in Portuguese:

msiexec /i Risk7-cust-Setup.msi ProductLanguage=1046
SETUPEXEDIR=C:\TEMP /qn
USERNAME="Maria Duarte" COMPANYNAME="Banco Nacional"

Part B: Additional step for CN/DE/FR/JP/PT/RU.

If you install the product in English or Spanish, Part A is sufficient. If you selected one of the other languages, the text of all program dialogs and messages is installed in that language, but the examples and documentation will be in English. For languages other than English and Spanish, you must separately run the language resources installer to install documentation and examples in the selected language. There is just one language resources installer, and it covers all products in all six languages.

Download the MSI installer for language resources from this link. There is just one language resources install, regardless of product or language. The command line looks like this:

  • Without progress bar:
    msiexec /i LanguageResources7-Setup.msi /qn MYLANG=
    language

  • With progress bar:
    msiexec /i LanguageResources7-Setup.msi /qb MYLANG=language

The language can be any one of Chinese, French, German, Japanese, Portuguese, or Russian. If you want to install documentation and examples for more than one language, run the installer again for each extra language. If you want to install documentation and examples for all six languages, use MYLANNG=ALL instead of specifying a language.

Additional keywords: Local language support, International language setting, Localization

Last edited: 2015-08-20

4.5. Non-English Versions of Software Releases 6.x

Applies to:
All products, release 6.1–6.3

For release 7, see Non-English Versions of Palisade 7.x Software.

Which localized versions are available?

Release 6.1 is localized for Chinese, English, French, German, Japanese, Portuguese, and Spanish. Releases 6.2 and later are localized for Chinese, English, French, German, Japanese, Portuguese, Russian, and Spanish.

How do I specify my preferred language?

You specify one of the languages as your preferred language in a dialog box at install time. Later, when running the application, the end user can change languages at any time through the Utilities » Application Settings dialog.

Can I specify a language in a silent install?

Yes. Please see Silent Install of Non-English 6.x Software.

Is a separate activation required for each language?

No, one Activation ID covers all available languages.

Is an Internet connection required when specifying or changing languages?

It is helpful but not required. The program installer contains program text — menus, icons, dialogs, messages, windows, graphs, reports, and so on — for all localized versions, and all languages are installed regardless of your preferred language.  There is nothing to download when changing the language of the program text.

The documentation files — help files, user manuals, and example spreadsheets — are a separate download. (If you have release 6.1.1, the program is localized but the documentation files are not.) If you select a non-English language when installing the program, the installer will try to download the documentation files and install them for you. Likewise, if you change languages through the software's Utilities » Application Settings dialog, and the documentation isn't already on your computer in that language, the software will try to download and install the documentation for you.

If the download of documentation fails for any reason, the program will operate in the specified language but the documentation will still be in English. In that case, you can download and install the documentation yourself by following one of these links:

My Windows language is not one of the listed ones. Can I still use the software?

Yes, but you must install and run the program in English. (Exception: The software does not function correctly with Windows in Korean.)

Additional keywords:  Local language support, International language setting, Localization

Last edited: 2014-11-06

4.6. Silent Install of Non-English 6.x Software

Disponible en español: Instalación Silenciosa de Software 6.x en otros idiomas
Disponível em português: Instalação em segundo plano para Software 6.x em idiomas diferentes do Inglês

Applies to:  All products, standalone or network versions, releases 6.1 through 6.3

If you have release 7.x software, see Silent Install of Non-English 7.x Software.

I'm doing a silent install of your 6.x product. I'd like the application to come up automatically in our local language the first time it runs, without making the end user navigate an English-language menu to set the language. How can I do this?

You'll need to obtain the appropriate language pack from us, and install it after installing the program. Here is the procedure.

  1. Contact Technical Support to request installers for the program and the language pack. Include this information in your email:

    • Your software serial number.
    • The language(s) you want.
    • The three-digit version number of the software version that you want to install.
    • MSI or EXE install? (MSI installs are available for program versions 6.2.0 and later, but the language packs are available only as EXE installs.)

    We'll send you a program installer and language pack installer(s) for the version you specify. If you don't specify, we'll send you the latest one you qualify for.

  2. Perform the silent install of the program. Choose the appropriate instructions:

    You need one extra command-line argument in addition to the ones shown in those articles. Specify a language with one of these arguments:

    • /L1031 for German
    • /L1034 for Spanish
    • /L1036 for French
    • /L1041 for Japanese
    • /L1046 for Portuguese
    • /L1049 for Russian
    • /L2052 for Chinese (Simplified)
  3. Perform the silent install of the language pack, with the /s /v/qn arguments. Example:

    DTS6-Resource-FR-Setup.exe /s /v/qn

    There is just one language pack for each language. If you're installing multiple products, for example @RISK and StatTools, run all the program installers and then install the language pack.

Additional keywords:  Local language support, International language setting, Localization

Last edited: 2014-11-06

4.7. SQL on 64-Bit Systems with @RISK 5

Applies to:
@RISK for Excel 5.x

Question:
I have 64-bit Windows, but your SQL installer seems to be 32 bits.

Response:
It's true that the SQL Server 2005 Express installer is a 32-bit installer, but it will work with @RISK, even on 64-bit Windows, if you have 32-bit Excel.  If you have 64-bit Excel, you need SQL Server 2008 Express in 64 bits. 

Please see SQL Versions and Installation for links and further details.

last edited: 2013-09-27

4.8. Non-English Versions of Software Release 5.7

This article relates to releases that are no longer sold, but it is retained for the benefit of our customers with existing licenses. For current information, please see Non-English Versions of Palisade 7.x Software.

Applies to:
@RISK for Excel 5.7
The DecisionTools Suite 5.7
Evolver 5.7
NeuralTools 5.7
PrecisionTree 5.7
StatTools 5.7
If you have a later release, please see Non-English Versions of Software Releases 6.x.

Question 1:
I received an Activation ID and a link to an English-language add-in for Excel. But I would like to install it in (Chinese, French, German, Japanese, Portuguese, Spanish). Must I install the English version first?

Response 1:
You can install English first and then another language, you can install the other language alone, or you can install English after installing another language. Here's how:

  1. Please visit our Web page at http://www.palisade.com/Updates and select your preferred language in the box immediately below "Software Updates and Upgrades". Then choose the correct product and edition. Caution: @RISK cannot be activated if your license is for the Suite, and the Suite cannot be activated if your license is for @RISK. If you don't see your product and edition listed, or you're not sure, please contact Technical Support at support@palisade.com and include your serial number in your message.

  2. Download and install your preferred language version.

You can repeat this for additional languages.

You will need to activate the first language version that you install, using the Activation ID you were given, but additional languages will share in the same activation and will not need to be activated separately.

Question 2:
I already have release 5.7 of the software in English or another language. Can I add a language?

Response 2:
Yes, you can install an additional language by following the procedure in Response 1 above. You will not need to reactivate the product, because one Activation ID covers all languages.

Question 3:
I already have software release 5.0 or 5.5. Can I install language versions in 5.7?

Response 3:
Yes, if your maintenance contract is up to date. In that case, follow the installation instructions in Response 1. If you have multiple languages, you will need to upgrade all of them, or else uninstall the unused ones before beginning the upgrade. It is not possible to have version 5.0 or 5.5 on the same computer with 5.7.

If your maintenance contract is not up to date, please see Non-English versions of @RISK 5.5.

Question 4:
I have multiple languages installed. How can I switch between them?

Response 4:
In the @RISK Utilities menu (the monkey-wrench or spanner icon), click Application Settings and choose your desired language. The program and most documentation will appear in that language, but the Six Sigma manual and help file will still appear in English.

Non-English editions of Palisade products require the correct Windows code page. For example, to use the Japanese version of @RISK, you must be on a computer with the active code page set to Japanese. If you are running on Japanese windows, this will automatically be set by default. However, if you are running Japanese @RISK on a non-Japanese machine, you will need to change the default Windows setting, which can be found on the Advanced tab in the Regional and Language Options in Control Panel.

last edited: 2013-02-23/p>

4.9. Non-English versions of @RISK 5.5

This article relates to discontinued products, but is retained for the benefit of our customers with existing licenses. For current information, please see Non-English Versions of Palisade 7.x Software.

Applies to:
@RISK 5.5 in French, German, Japanese, Portuguese, or Spanish
(If you have 5.7, please see Non-English Versions of Software Release 5.7.)

Question:
I already have English-language @RISK or DecisionTools. What do I have to do to install a second-language version of @RISK?

Response:
If you are a new customer, with no @RISK or DecisionTools Suite 5.x on your computer, you can purchase and install a non-English @RISK without installing English @RISK.

If you already have 5.0 or 5.5 software on your computer, please read the section below that applies to you. If you have any questions, please contact Technical Support before you install anything.

Standalone users

If you have standalone DecisionTools 5.0, you cannot just install a second-language @RISK on top of it. You must have current maintenance and must follow this install order:

  1. Deactivate DecisionTools 5.0 (There is no need to uninstall it.)
  2. Request a new 5.5 Activation ID from your Palisade sales manager.
  3. Install DecisionTools 5.5; click "Next" when prompted for activation.
  4. Install second-language @RISK 5.5 of the same edition (Industrial or Professional); click "Next" when prompted for activation.
  5. Activate DecisionTools 5.5, including second-language @RISK, using the new Activation ID.

If you have activated a standalone DecisionTools 5.5, your course of action depends on whether it has a 5.5 Activation ID or a 5.0 one:

  • If you have a 5.5 Activation ID (first two digits 45 or greater), you can simply install the second-language @RISK of the same edition (Industrial or Professional).
  • If you have a 5.0 Activation ID (first two digits 12 or 13), you must deactivate DecisionTools 5.0 and then follow steps 2, 4, 5 above.

If you have an activated standalone @RISK 5.0 with current maintenance, you can install a second-language @RISK 5.5 on top of it without first installing English @RISK 5.5. It must be the same edition (Industrial, Professional, Standard). No new Activation ID is required.

If you have an activated standalone @RISK 5.5 in English, you can install a second-language @RISK 5.5 on top of it. Again, it must be the same edition (Industrial, Professional, Standard), and no new Activation ID is required.

Network users

Network users with a 5.0 license cannot install a second-language @RISK. You must first upgrade to a 5.5 license. If you have current maintenance, the upgrade is free, and we encourage you to work with us to smooth the transition.

Network users with a license for @RISK 5.5 or DecisionTools Suite 5.5 don't have to do anything on the server side. On the client side, an individual client can install second-language @RISK of the same edition (Industrial, Professional, Standard) using the standalone installer. If in doubt, please email your serial number or Activation ID to support@palisade.com and we'll make sure you get the correct installer.

Students

Students with 5.0 cannot install a foreign-language @RISK and cannot upgrade to 5.5. You must buy a new 5.5 license.

Students with activated 5.5 can install a foreign-language @RISK of the same edition (Industrial or Professional) on top of it.

last edited: 2011-03-01

5. Further Information

5.1. Overview of 6.x/7.x Commercial Licenses

Disponible en español: Resumen de las Licencias 6.x/7.x
Disponível em português: Visão Geral das Licenças 6.x/7.x

Applies to: All products, releases 6.x/7.x, commercial licenses
For academic licenses, see 6.x/7.x Academic Licensing Options.
For Developer Kits 4.x, see Developer Kit License Types.

What licensing options do you offer for your software?

We offer license types for students, academic faculty, and commercial users, for single workstations or for a network. Here are the commercial license types:

Name of LicenseLicense LocationActivatable or Certificate
(See below.)
Usual
Duration
End User
Computer
Your
Server
★ Enterprise licenses, and all certificates, are issued for a year at a time.
Standalone   Usually activatable; certificate on request Permanent★
Concurrent Network   Usually activatable; certificate on request Permanent★
Enterprise Network End user and server both have license. Always activatable Permanent★

What is an activatable license? What is a certificate license?

  • An activatable license, also known as a trusted storage license, is a string of letters and digits called an Activation ID. Before use, it must be activated against our server. See Activating Palisade 6.x/7.x Standalone Software, or for network licenses see the 7.x Network Guide or 6.3 Network Guide.

    Activation can be automatic or manual. Automatic Activation needs direct communication between your server or computer and our license server. If that fails because of your firewall, Manual Activation is available: the software creates a digitally signed XML request file, you email the file to us or upload it to our Web page, you get a response file the same way, and you load the response file in the software.

    Before you wipe a hard drive or decommission a computer or server where a license is activated, you must deactivate the license. You must also deactivate the license as part of transferring it. Deactivation can also be automatic or manual. See Transferring Standalone Software 6.x/7.x to a New Computer, Moving 7.x Concurrent Network to a New Server, Moving 7.x Enterprise Network to a New Server, Moving 6.x Concurrent Network to a New Server, or Moving 6.x Enterprise Network to a New Server.

  • A certificate license is a text file, digitally signed and locked to the MAC address of your license server or your end user's computer. Other types of licenses, which are usually activatable, can be changed to certificates in special circumstances. The most common of these is an ultra-secure environment where you are prohibited from exchanging the information necessary to complete a Manual Activation.

    There is no deactivation process for a certificate license. Instead, you ask Palisade for a new license when you need to move it to a new computer or server. Therefore, certificate licenses are issued for no more than a year at a time.

What is a standalone license?

A standalone license is for use on a single computer. An optional auxiliary license (available in some regions) will let you install and use the software on a second computer, provided that you are the only user on both computers. Most standalone licenses are perpetual, but student standalone licenses bought directly from Palisade are good for a year.

Most standalone licenses are of the activatable type: you receive an Activation ID, and you must activate it against our server. See Activating Palisade 6.x/7.x Standalone Software. You must also deactivate the license as part of transferring it, or before you wipe the computer's hard drive for any reason; see Transferring Standalone Software 6.x/7.x to a New Computer.

For users in ultra-secure areas, who cannot perform the usual activation process, Technical Support can change your activatable license to a certificate type. See "Manual Activation — No Internet" in Activating Palisade 6.x/7.x Standalone Software.

For the full license terms of standalone licenses, please see End User License Agreement (EULA).

What is a Concurrent Network license? What is an Enterprise Network license?

Please see Overview of 6.x/7.x Network Licenses.

What kind of free technical support is available?

When you have a maintenance contract, Tech Support will help make sure that can install and activate your software and that it's working correctly; Tech Support will also answer reasonable questions about product features. For larger questions about how to design your model, please contact your Palisade sales manager to book some time with one of our consultants.

Even without a maintenance contract, commercial users can get reasonable help for questions and problems about installation and activation. Installation is usually routine and does not require help from Palisade.

See also: Scope of Free Support.

How do I request technical support?

Commercial users can email Technical Support (include your serial number), phone us at +1 607 277-8000, or use live chat on our Web page. When requesting support by phone or live chat, please have your serial number handy.

Is remote access possible? I have the software installed on my office computer, and I want to log in from my laptop and run the software.

Remote access is allowed for Concurrent Network licenses, but not for any other type. See "Using ... via remote access or Terminal Services is not allowed ...".

If you have a standalone license, you can buy an auxiliary license (available in some regions) that will let you install and run the software on a second computer, such as a laptop.

Do you offer a corporate license?

The Concurrent Network and Enterprise Network licenses suit most corporations. However, please discuss any special requirements with your Palisade sales manager. He or she will work with you to come up with a software and license solution that will work well in your environment.

Last edited: 2016-08-02

5.2. Academic Licensing Options (6.x/7.x)

Disponible en español: Resumen de las Licencias 6.x/7.x
Disponível em português: Visão Geral das Licenças 6.x/7.x

Applies to: All products, releases 6.x/7.x, academic licenses
For commercial licenses, see Overview of 6.x/7.x Commercial Licenses.
For Developer Kits 4.x, see Developer Kit License Types.

What licensing options do you offer for your software?

We offer license types for students, academic faculty, and commercial users, for single workstations or for a network. Here are all the academic license types:

UsersName of LicenseLicense LocationActivatable or Certificate
(See below.)
Usual
Duration
End User
Computer
Your
Server
☆ Palisade Tech Support may issue a certificate to work around specific problems.
★ All certificates are issued for a year at a time.
Faculty Standalone Academic   Always activatable☆ Permanent★
Concurrent Network   Usually activatable; certificate on request Permanent★
Students Standalone (bought by student)   Always activatable☆ 1 year
Course — Workstation Setup
(bought by the school)
  Always certificate 1 year
Course — Client-Server Setup
(bought by the school)
  Usually activatable; certificate on request 1 year
Textbook (free with book purchase)   Always certificate 1 or 2 years

What is an activatable license? What is a certificate license?

  • An activatable license, also known as a trusted storage license, is a string of letters and digits called an Activation ID. Before use, it must be activated against our server. See Activating Palisade 6.x/7.x Standalone Software, or for network licenses see the 7.x Network Guide or 6.3 Network Guide.

    Activation can be automatic or manual. Automatic Activation needs direct communication between your server or computer and our license server. If that fails because of your firewall, Manual Activation is available: the software creates a digitally signed XML request file, you email the file to us or upload it to our Web page, you get a response file the same way, and you load the response file in the software.

    Before you wipe a hard drive or decommission a computer or server where a license is activated, you must deactivate the license. You must also deactivate the license as part of transferring it. Deactivation can also be automatic or manual. See Transferring Standalone Software 6.x/7.x to a New Computer, Moving 7.x Concurrent Network to a New Server, or Moving 6.x Concurrent Network to a New Server.

  • A certificate license is a text file, digitally signed and locked to the MAC address of your license server or your end user's computer. Textbook licenses are always certificates. Course workstation certificates are not tied to a specific computer but can be used on a specified number of student computers. Other types of licenses, which are usually activatable, can be changed to certificates in special circumstances.

    There is no deactivation process for a certificate license. Instead, you ask Palisade for a new license when you need to move it to a new computer or server. Therefore, certificate licenses are issued for no more than a year at a time.

What is a standalone license?

A standalone license is for use on a single computer. An optional auxiliary license (available to faculty in some regions) will let you install and use the software on a second computer, provided that you are the only user on both computers. Standalone academic licenses are perpetual.

Most standalone licenses are of the activatable type: you receive an Activation ID, and you must activate it against our server. See Activating Palisade 6.x/7.x Standalone Software. You must also deactivate the license as part of transferring it, or before you wipe the computer's hard drive for any reason; see Transferring Standalone Software 6.x/7.x to a New Computer.

For the full license terms of standalone licenses, please see End User License Agreement (EULA).

Student licenses bought directly from Palisade last for one year from first activation. They have watermarks on graphs, but no restrictions on model size or software features. Except for the watermark, a student license functions exactly like a commercial license for the DecisionTools Suite Industrial Edition.

What is a Concurrent Network license?

Please see Overview of 6.x/7.x Network Licenses.

What is a course license?

Course licenses are sold to accredited colleges and universities for use in instruction. The school's IT department can select workstation setup, client-server setup, or both.

  • Client-server setup is designed for a computer lab, where the computers are all on your network at all times. It's implemented as a concurrent network, so you can install the client software on any number of computers, but no more than the contracted number of students can use the software simultaneously.

  • Workstation setup is best when students will install the software on their own computers. It's similar to a standalone license, except that there is a pre-activated license certificate rather than an Activation ID. After the initial installation, the student's computer does not need to communicate with your server.

What is a textbook license?

If you bought a qualifying textbook, you can install a free license. You'll need to have your textbook with you during the install.

Textbook licenses are good for one or two years, depending on the title. A textbook license comes with certain restrictions on model size, and graphs are watermarked, but you can use all the features of the DecisionTools Suite Industrial Edition except the @RISK Library.

What kind of free technical support is available?

Tech Support will help make sure that can install and activate your software and that it's working correctly; Tech Support will also answer reasonable questions about product features. Installation is usually routine and does not require help from Palisade.

See also: Scope of Free Support.

How do I request technical support?

Academic faculty can email Technical Support (include your serial number), phone us at +1 607 277-8000, or use live chat on our Web page. When requesting support by phone or live chat, please have your serial number handy.

Students with course licenses who need help with installation should look to their school's IT department first; the IT department will contact Palisade if they cannot solve the problem. Students who bought licenses directly from Palisade, or who are using textbook software, can email Technical Support with installation problems (include your serial number or the title and edition of your textbook); support by phone and live chat is not available. For help in learning to use the products, students should consult their professors or the extensive video tutorials and help files.

Is remote access possible? I have the software installed on my office computer, and I want to log in from my laptop and run the software.

Remote access is allowed for Client-Server Setup only, but not for any other type. See "Using ... via remote access or Terminal Services is not allowed ...".

In some regions, if you have a standalone academic license then you can buy an auxiliary license that will let you install and run the software on a second computer, such as a laptop.

Last edited: 2016-08-02

5.3. Citrix Servers, Terminal Services, Remote Desktop, XP Mode

Disponible en español: Servidores Citrix, Servicios de Terminal, Escritorio Remoto, Windows XP Mode
Disponível em português: Servidores Citrix, Serviços de Terminal, Área de Trabalho Remota, Windows XP Mode

Applies to:  All products

Can I install and run Palisade software on a Citrix server or Terminal Services?  Can I log in to my office computer from a remote location and run the software?

A Concurrent Network license is required with Citrix servers and Terminal Services (also known as Remote Desktop Services). A Concurrent Network license is also required for any other form of remote login.

With a standalone license, you must be physically present at the computer that is running our software.  If you try to run a standalone license remotely, you'll get an error message or an activation screen. (The same is true for an Enterprise Network license also.)

If you don't actually need to log in remotely, but simply want to use the software on two computers, ask your Palisade sales manager about possible alternatives.

(Windows XP Mode in Windows 7 is implemented as a form of remote desktop, so you can't run a standalone copy of our software in XP Mode. But there is no need to do that, because our software is fully compatible with Windows 7 in 32-bit or 64-bit form.)

See also: Citrix and Remote Desktop? in our 7.x Network Guide

Additional keywords: Thin client, RDP

Last edited: 2016-08-18

5.4. End User License Agreement (EULA)

Applies to:
All end user software, releases 7.x (both standalone and network clients)

The End User License Agreement (EULA) that the installer presents to you is not currently saved on your computer after the install.  A copy of the English text is attached in Microsoft Word format.

Additional keywords: Standalone EULA, Network client EULA

See also: Network Server License Agreement.

Last edited: 2016-01-15

5.5. Product Tutorials

Applies to:
Palisade software release 5.5.1, 5.7, and 6.x/7.x

Question:
Do you have any materials to help a new user of these versions get started and become familiar with the features of the software?

Response
Yes, we have a series of short videos that form our "Getting Started Tutorials". We recommend them as a good overview to using our products, both for new users and for experienced users who might not be familiar with all the features.

To access the tutorial for a particular Palisade application, run the application and then select its Help menu. In 6.x /7.x, under Help select Videos; in 5.x, under Help select "Getting Started Tutorial".

You can also view the tutorials and many more videos directly on the Web.  Many are available in multiple languages. Please visit http://palisade.com and hover your mouse on Support in the horizontal menu beneath the banner. A menu will open; hover on Videos and you will see the available selections.

Last edited: 2016-03-02

5.6. User Manuals and Readme Files for Releases 7.x

Applies to:
All products, releases 7.x

Where are system requirements, installation instructions, and so forth?

The Readme files for current and past software releases can be downloaded from Palisade's Web page, Product Manuals and Documentation. (Other than product name, the information is the same for all of our current products.)

See also:

Where is the user manual for my software?

The most convenient way to access the manual is through the software.  For instance, to read the @RISK documentation, run @RISK (click the Windows Start button, then All Programs or Programs, then Palisade DecisionTools, then @RISK 7). Click the question-mark-in-a-circle icon. The first item, Documentation, leads to the help file and the user manual for the @RISK application. The second item, Developer Kit (XDK), leads to the help file and the manual for the Visual Basic interface to @RISK.

User manuals, help files, and example spreadsheets are available in the same languages as the software itself. If your computer doesn't have the necessary language pack when you select a language, the software will try to download it. 

You can also download the user manuals for current and past software releases from Palisade's Web page, Product Manuals and Documentation.

last edited: 2016-07-06

5.7. Version Histories for Releases 5.x–7.x

Applies to:  All products

I'm thinking about upgrading. What new features will I get?

Version histories for the latest releases of all our products are found here:

I've just upgraded to the latest release. What are the significant changes from my older version?

You can get a high-level view of the major changes by clicking What's New in the product's Help menu.

For more detail, read the appropriate version history on your computer, or at one of the above links.  On your computer, follow this procedure:

  1. Open Computer or My Computer.
  2. Navigate to the Palisade installation folder. (By default, this is C:\Program Files\Palisade or C:\Program Files (x86)\Palisade.)
  3. Open the product folder, such as RISK6 or NeuralTools5.
  4. Within that folder, double-click the Documentation folder.  Within Documentation, double-click the appropriate language folder.
  5. Double-click Version History.

What about the network Server Manager? What changes have been made there?

The version history for Server Manager is included in the 7.x Network Guide.

Additional keywords:  change log, version log, new features, software changes

Last edited: 2016-08-15

5.8. User Manuals and Readme Files for Releases 6.x

Applies to:
All products, releases 6.x

(If you have 7.x software, please see User Manuals and Readme Files for Releases 7.x.)

Where are system requirements, installation instructions, and so forth?

The Readme files for current and past software releases can be downloaded from Palisade's Web page, Product Manuals and Documentation. (Other than product name, the information is the same for all of our current products.)

See also:

Where is the user manual for my software?

The most convenient way to access the manual is through the software.  For instance, to read the @RISK documentation, run @RISK (click the Windows Start button, then All Programs or Programs, then Palisade DecisionTools, then @RISK 6). Click the question-mark-in-a-circle icon. The first item, Documentation, leads to the help file and the user manual for the @RISK application. The second item, Developer Kit, leads to the help file and the manual for the Visual Basic interface to @RISK.

Beginning with release 6.1.2, user manuals, help files, and example spreadsheets are available in the same languages as the software itself.  If your computer doesn't have the necessary language pack when you select a language, the software will try to download it.  For more information, see Non-English Versions of Software Releases 6.x.

You can also download the user manuals for current and past software releases from Palisade's Web page, Product Manuals and Documentation.

last edited: 2016-07-06

5.9. User Manuals for Releases 5.x

Applies to:
All products, releases 5.x
(If you have 6.x software, see User Manuals for Releases 6.x.)

Question:
Where is the user manual for my software?

Response:
In releases 5.0, 5.0.1, and 5.5.0, click the Windows Start button, then All Programs or Programs, then Palisade DecisionTools, and you can then select the user manuals.

Beginning with release 5.5.1, Palisade removed the documentation links to simplify the Start menu. You can still find them in the menus of the individual tools.

For instance, to read the @RISK documentation, run @RISK (click the Windows Start button, then Programs or All Programs, then Palisade DecisionTools, then @RISK for Excel). Click the question-mark-in-a-circle icon. The first item, Documentation, leads to the user manual and the help file. The second item, Developer Kit, leads to the help file and the manual for the Visual Basic interface to @RISK.

The user manuals for release 5.7.1 can also be downloaded from Palisade's Web page, Product Manuals and Documentation.

last edited: 2013-01-03

5.10. Scope of Free Support

Applies to: All end-user software products

What services are available from Tech Support? Am I eligible for software upgrades? What is covered by my maintenance contract?

This is part of the full End User License Agreement, but for convenience we reproduce the relevant section here.

14.  SOFTWARE MAINTENANCE, SUPPORT SERVICES, AND UPDATES.

If the Software was provided with Software Maintenance, you are entitled to Software updates and upgrades and Support Services free of charge during the Maintenance Period only, provided the Software is used in compliance with this Agreement in all material respects.  Software updates and upgrades and Support Services provided under your Software Maintenance plan are for your use only and not for distribution to or use by others.  Without a current Software Maintenance plan, Software Maintenance may not be available to you.  If the Software is used in breach of this Agreement, you will not be able to receive Software Maintenance, even if you have paid the Software Maintenance fee.

Support Services are available for commercial clients in the form of live support via telephone, e-mail, web portal, or web chat during Palisade technical support operating hours.  Telephone and chat support is not available for student versions of Software. Support Services are not available at your physical site.  Self-serve support in the form of searchable knowledge base articles, forums, and other resources is available 24 hours per day, 7 days per week.
Support Services are limited to: assistance with Software installation, activation, transfers, error messages, bugs, or operational problems.  Support Services are limited to the platforms and Software versions listed at www.palisade.com. [The charts at Windows and Office Versions Supported by Palisade give most of this information.]
Support Services do not include: auditing and de-bugging of models; complete installation services; Software training; consulting or model building; automation or customization of models; hardware troubleshooting or diagnosis; or any other services not specified above.

During the provision of Support Services, you agree to follow Palisade recommendations and provide all information reasonably requested by Palisade to resolve a problem.  Such information may include but is not limited to: your name and company; serial number or activation ID; Software name and version; host application and operating system information; error messages; screen captures; access to view your computer via Webex or similar desktop-sharing software as much as is feasible; and models or output data as much as is feasible.  You also agree to install the latest updates, upgrades, or patches Palisade recommends to resolve a problem.

[Emphasis and links added for convenience in reading.]

Article posted: 2016-07-11

5.11. Support for Student Licenses

Applies to: The DecisionTools Suite — student edition, textbook edition, and university course license

I bought a student license from Palisade, or my school had me install a course license, or I got the software free with a textbook. What kind of support do you offer?

Support includes installation and activation, problems with operating the software, and basic questions about features. For model design or homework, please consult your professor.

We'll gladly help you in email, but unfortunately we don't have the resources to support student licenses in live chat or by phone.

Common problems, questions, and error messages may not even need a personal response. Please check out our searchable Knowledge Base, 24/7 at kb.palisade.com.

Email us at support@palisade.com and you should hear back within 24 hours (usually sooner), apart from weekends. You can speed things up by including your serial number or book title and ISBN. Be as specific as possible with your question or problem. If you're getting an error message, attach a screen shot. If the software seems to be misbehaving, attach your workbook.

Be sure you list Palisade.com as an allowed email sender. If you don't hear back from us, check your spam folder to see if our reply got trapped there.

Last edited: 2015-02-26

5.12. Upgrading Palisade Software

Disponible en español: Actualización de software de Palisade
Disponível em português: Atualizando o Software Palisade

Our current release is 7.5.1. (For a high-level view, see What's New in The DecisionTools Suite 7. For a change log of each release, please see Version Histories for Releases 7.x.)

Upgrades to 7.5.1 are free of charge if you have a current maintenance contract. Otherwise, please contact your Palisade sales office to obtain a price quote for the upgrade to 7.5.1.

For information about upgrading your license type, please select the appropriate link:

Standalone upgrade instructions:

Network upgrade instructions:

If you are receiving an update notice when you launch the software, and you can't update or prefer not to, please see "An update is available." (6.x) or "Update Available" (7.x).

See also:

Last edited: 2017-02-17

5.13. Palisade Product Lifecycle Policy

Palisade product lifecycles begin when a product is released and end when a product is no longer supported or sold. Following are descriptions of the Palisade product lifecycle policy based on whether or not you continue to purchase a current maintenance plan for your software.

For Products with Current Maintenance

As long as you keep maintenance for your Palisade software continuously in effect, Palisade will provide the following support to you at no charge:

  • Upgrades to the latest available version of the same product. (For the procedures, please see Upgrading Palisade Software.)
  • Assisted support for product activation, for a minimum of 10 years from the release date of each version.
  • Assistance with technical questions about product features and operation, for at least five years from the release date of each version. After that, we may ask you to upgrade to a current version (at no charge) to continue receiving in-maintenance assistance of this type. Example: If successive product releases are in 2008, 2009, and 2010, the 2008 version will be supported until at least 2013 (five years from release).

For Products without Current Maintenance

If you do not keep a current maintenance plan for your Palisade software, you are not entitled to assisted technical support or free upgrades beyond the first 12 months after you purchase your new software. Palisade will provide support for product activation (but not other issues) for a minimum of 10 years from the release date of each version, though there will be a charge for non-automated assistance.

For All Users

If new hardware or new versions of Windows or Office are not compatible with your existing Palisade software, for continued technical support you may need to upgrade to a current version of our software.

Additional keywords: Support policy

last edited: 2013-04-15