HomeTroubleshootingPrinter Friendly Version

Troubleshooting

Common problems and solutions.

1. Installation

1.1. .NET on 64-bit Systems

I'm trying to install your software, but I get a message from the .NET portion of the install that it's a 32-bit program and is incompatible with my 64-bit Windows system. Help!

Please install .NET yourself, then re-run our installer. It will sense that the .NET components are installed and will not try to install them again.

last edited: 2015-09-28

1.2. Install Failure: .NET 1.1

Applies to:
The DecisionTools Suite 5.0 through 5.5.1
NeuralTools 5.0 through 5.5.1

Problem:
My install fails because it can't download and install Microsoft .NET 1.1.

Response:
Do you have Vista Home Premium? Customers have reported that the Microsoft Internet Explorer 7 bundled with Vista Home Premium will not allow Microsoft .NET 1.1 to download and install.

The solution in this case is to use a different browser if you already have one installed, or to download and install Internet Explorer 8.

last edited: 2012-02-07

1.3. Installer Freezes at 100%

The installer seems to run, but when the progress bar is completely full (100% complete) the installer just hangs.

When the installer hangs with a full progress bar, that usually means that the installer doesn't have sufficient privilege.

  • If you have Windows 7, 8, 10, or Vista, log on to Windows as a full administrator, right-click the installer, and select Run As Administrator. (Both you and the installer program must have full privilege.)
  • If you have Windows XP, log on to Windows as a full administrator and repeat the install.

If that doesn't solve the problem, please look for any security software you might have that could be interfering. We know our installer works just fine on an out-of-the-box Windows PC, and we know also that the well-known antivirus and firewall programs are not an issue. But if you have some less common security software, try disabling it and repeating the install.

The Microsoft tool Fix problems that programs cannot be installed or uninstalled fixes some common installation problems, such as an installer hanging at 100% complete.

If that also fails, please contact Palisade Technical Support. We have a license repair tool that may solve the problem.

Last edited: 2015-09-30

1.4. EXE Installer Rolls Back without Explanation

Applies to: Installers for 6.x/7.x

I have full administrative rights. I right-clicked the installer and selected Run as administrator. There are no error messages, but then at the end of the install I get a message like this one:

Setup Completed
The installer was interrupted before DecisionTools Suite 7.0 could be completely installed.
Your system has not been modified. To complete installation at another time, please run setup again.

But I didn't interrupt the installer; it just decided on its own to roll back the install. How do I install the software?

It looks like one or more of your C++ runtimes is not working correctly.

For some customers, the solution is as follows:

  1. See Microsoft Components Required for Palisade 7.x Software Install or Microsoft Components Required for Palisade 6.x Software Install and manually install the necessary components directly from Microsoft's site. If you have issues with those installs, including error messages of any kind, please contact Microsoft support.
  2. After you have installed all the required components without any kind of error message, rerun Palisade's installer. It will not try to reinstall the components that you installed separately, and this should be enough to let the installation finish normally.

If the installation still has the same problem, something more serious is going on. Please follow this procedure:

  1. Uninstall all versions of Microsoft Visual C++ Redistributable, from highest to lowest, making note of each one as you go.
  2. Restart Windows.
  3. Reinstall them, from lowest to highest, using the links you find at The Latest Supported Visual C++ Downloads. (There's no need to install any that you didn't uninstall.) If one of the versions you're installing is 2010, also install the Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update.
  4. Rerun Palisade's installer. If it needs any versions of Microsoft Visual C++ Redistributable that you don't already have, it will reinstall them, but it won't reinstall any that you've already installed.

If the problem still remains, manually replace the DLLs in the System32 folder, as explained in solution 10 of 0xc00007b Error Fix. (Solutions 1–9 are general solutions which may not necessarily apply to the Visual C++ Redistributable issues specifically.)

Last edited: 2016-04-21

1.5. MSI Installer Runs, Then Rolls Back

Applies to: All products, releases 6.x/7.x (MSI installers)

I ran the MSI installer for one of your products. It seemed to get close to completion, but then started rolling back. There was no explanation or error message.

You must install certain Microsoft components before running one of our MSI installers. (Our EXE installers install these prerequisites automatically, if they are not automatically installed.) Please select the article for the software version you are installing:

Whether you are scripting the install or running the MSI by double-clicking, those Microsoft components must be installed first.

Last edited: 2015-09-30

1.6. Installer Just Shows a Windows Installer Help Message

Applies to:  All products, releases 6.x/7.x

When I run the installer, after the "extracting MSI" phase it just pops up a Windows Installer help message, like this:

Most occurrences of this problem are due to insufficient permissions, either running the installer within your browser or not running it as administrator. When you download the installer, and your browser prompts you for what to do, be sure to choose Save, not Run or Open. Then right-click the saved file and select Run As Administrator.

If that doesn't solve the problem, then something in your Windows setup is preventing the downloaded EXE-type installer from launching the extracted MSI-type installer. (Unfortunately, we have not been able to reproduce the problem here, so we're not sure just which setting is the problem.) Here is the workaround:

  1. Install the prerequisites listed in Microsoft Components Required for Palisade 7.x Software Install or Microsoft Components Required for Palisade 6.x Software Install. The instructions indicate which components should or should not be installed in your particular flavor of Windows.

  2. Open your temporary folder. Locate the extracted MSI-type installer file, right-click it, and select Run as administrator.

    TIP: To make the extracted installer easier to find, switch to Details view and sort by date modified. The file name is DTS63.msi, RISK63.msi, or similar. You may not be able to see the ".msi" part, but the file type is Windows Installer Package.

    If you can't find it, please contact Technical Support with your serial number and ask for a link to download the MSI installer for your product. When you download the link, select Save, not Run or Open; right-click the saved file and select Run as administrator.

Last edited: 2015-09-28

1.7. Problems in Silent Install

A few users have had problems with the silent install of 5.x, 6.x, or 7.x. We have not been able to reproduce them here, but as a service we pass on solutions that worked for those users.

PalFlex5 error:
Certain computers get a PalFlex5 error with the silent install of 5.7. If you get that error during silent install, please see this article: "PalFlex5.dll" during silent install of 5.7

Error in MSVC++ Redistributable install:
Some customers have reported that during a silent install with the /qb or /qn switch, they get a popup message "Another program is being installed. Please wait until that installation is complete, and then try installing this software again." If that happens to you, try replacing /qb or /qn with /qr (reduced interface). We are grateful to the customer who found this workaround.

We had one customer report that just replacing /qb or /qn with /qr did not work for him. After experimentation, he shared this additional possible solution with us:
"The program install works, using the command line 'setupprogram.exe /S /V/qr/NORESTART' from SCCM (Microsoft's Systems Centre Configuration Manager) if we tick the box to 'Allow users to interact with this program' and configure the advert to run 'whether or not a user is logged on'."

You may find it more convenient to install the prerequisites yourself in your script before running our installer. For the prerequisites, please see Microsoft Components Required for Palisade 7.x Software Install, Microsoft Components Required for Palisade 6.x Software Install, or Microsoft Components Required for Palisade 5.x Software Install.

last edited: 2015-09-28

1.8. Need 64-bit Version of Palisade Software

Applies to:
@RISK 5,7 and newer
BigPicture, all releases
Evolver 5.7 and newer
NeuralTools 5.7 and newer
PrecisionTree 5.7 and newer
StatTools 5.7 and newer
TopRank 5.7 and newer

I have 64-bit Excel, but @RISK installed in C:\Program Files (x86). I must have received the 32-bit version by mistake. How do I get the 64-bit version?

We have just the one version, and it works with both 32-bit and 64-bit Excel. Our software always installs in C:\Program Files (x86) because the code is mixed 32-bit and 64-bit. When our software runs as an add-in to 64-bit Excel, an "out-of-process server" runs automatically and makes the connection between 32-bit and 64-bit code. You don't have to set any options in the software to help it work with 64-bit Excel.

If your system is set up so that only specified .EXE files can run, you should add permission for the OutOfProcessServer files that you find in subfolders under C:\Program Files (x86)\Palisade.

See also: Should I Install 64-bit Excel?

Last edited: 2016-04-15

1.9. Textbook Software Installs as Trial Version

Applies to:
DecisionTools Suite, textbook edition

Problem:
I installed the textbook edition of the software, but when I launch it it tells me that it is a trial version, or License Manager says "There is no available license". What Activation ID should I use?

Response:
The textbook software does not require activation, if installed correctly. During installation, you need to extract all files from the .ZIP file to your desktop, and then run the installer. If you run the installer from within the .ZIP file (compressed folder), it will not find your textbook license and will install itself as a trial.

To solve this problem, simply reinstall the software correctly.  After installing, you can delete the files that you extracted to your desktop.

Additional keywords: No license available

last edited: 2017-02-03

1.10. "Another installation is in progress."

Applies to:  All products

You try to install Palisade software, and you get this message:

Error 1500. Another installation is in progress.

Maybe a previous installer crashed, maybe it didn't. What should you do?

First, try using Task Manager » Processes to end the msiexec.exe process, or just restart Windows. (Don't simply log off and on, but actually restart Windows.)

If that doesn't let you install, there are one or more System Registry keys telling Windows that an install is in progress. To fix this, please follow the procedure in Microsoft's Fix problems that programs cannot be installed or uninstalled.

We have also had customers tell us that they cleared the error condition as follows: run services.msc, change the Windows Installer service to Disabled, reboot, and then change Windows Installer service to Manual.  (This was suggested by Another Installation Already in Progress (But it's Not).  Please observe the usual caveats, as this is not a Microsoft site.)

Last edited: 2016-06-16

1.11. "Could not access network location"

I bought a textbook, and I'm trying to install the software that comes with the textbook. During install, I get this message:

Error 1606. Could not access network location http://download.palisade.com/....cab

The textbook installer first creates a license and then downloads the main software installer as a CAB-type file. Something on your system is preventing that second download. Please contact Palisade Technical Support for assistance. To avoid delays, please include a screen shot of the error message, plus the title and edition of your textbook and the ISBN.

I'm trying to install Palisade software in a virtual machine. During install, I get this message:

Error 1606. Could not access network location \\vmware-host\Shared Folders\...

This is usually a VMWare issue. Please follow these procedures from the VMWare Knowledge Base and VMWare users:

If you need further assistance, please contact VMWare for support, or if possible install the software in your real machine. Palisade Technical Support is unable to troubleshoot issues with VMWare's shared folders.

1.12. "Could not access VBScript run time for custom action"

Applies to:
@RISK 5.0 installer under Windows Vista only

Problem:
When installing @RISK in my Windows Vista system, I got the error message

Error 2738. Could not access VBScript run time for custom action

Response:
There are a few different issues involved here, all unique to Windows Vista:

  • Make sure to "Run as Administrator". Even when you are logged in as the Administrator, you may not be actually executing programs as an Administrator. When launching the @RISK for Excel installation file (or doing many other tasks, for that matter), make sure to right-click on the file and choose "Run as Administrator" (second item in the list). If you don't, then you are most likely running the program with limited permissions, and things such as registry keys and system files will not be created or updated properly.

  • Register the VBSCRIPT.DLL file. Vista does not register this file by default. To register this file manually, click Start » Run, or Start » All Programs » Accessories » Run. Type

    regsvr32 vbscript.dll

    into the box and press Enter. You should see a dialog indicating that registration of the file succeeded. If that fails, click Start » All Programs » Accessories, right-click on Command Prompt, and select Run as administrator. Type in

    regsvr32 vbscript.dll

    and press Enter. You should get a dialog stating that the registration succeeded.

    NOTE: If you are running a 64-bit version of Windows Vista, register the VBSCRIPT.DLL file by running C:\windows\syswow64 instead of the system command prompt.

  • Once you have the VBSCRIPT.DLL file registered, launch the @RISK for Excel installer. Again, make sure you are using the "Run as administrator" option to launch the installer.

last edited: 2012-11-17

1.13. "Could not open key" during install of 5.5

Applies to:
Palisade software version 5.5 installers

Problem:
When I try to run the installer, I get the message

Error 1402. Could not open key: HKEY_LOCAL_MACHINE32\Software\Wow6432Node\FLEXlm License Manager. Verify that you have sufficient access to that key, or contact your support personnel.

Response:
Our software is compatible with 64-bit Windows, but a small number of users have experienced this problem on install.

The first thing to check is that you have truly extracted all of the ZIP file components from the archive into an empty directory. Attempting to run the installer from within the ZIP file -- even if the ZIP file appears to open in a separate window -- will not actually extract all of the files or make use of them properly.

If the problem persists, please contact Palisade Technical Support for an alternative installer that will work around the problem. Please include your Activation ID or the details of your course license.

last edited: 2010-01-12

1.14. "Error 1304. Error writing to file OptQuestNET.dll."

Applies to: All products, releases 7.x

My installation fails with his message:

Error 1304. Error writing to file OptQuestNET.dll. Verify that you have access to that directory.

What directory is it talking about?

The error message is unfortunately misleading. The real problem is that our 7.x releases require .NET 4.0 or 4.5, and it is not installed on this computer. Our EXE installer installs it automatically, but if you're using an MSI installer you need to install .NET and other prerequisites before running our installer. Please see Microsoft Components Required for Palisade 7.x Software Install.

Last edited: 2015-07-22

1.15. "Error 1316. A network error occurred" in a 6.x/7.x install

Applies to: All products, 6.x/7.x, standalone or network client

While installing an upgrade of @RISK or other software, I get this error message or a similar one:

Error 1316. A network error occurred while attempting to read from the file C:\Windows\Installer\DTS62.msi

Error 1316 doesn't actually have anything to do with networking.  It seems to occur during the upgrade process of many vendors' products, but not many users of any one product. We at Palisade have seen this problem only rarely.

The simplest solution for a standalone version is:

  1. Uninstall your existing version of the software, in Control Panel » Programs and Features. You'll be asked whether to deactivate the license; answer No.
  2. Install the new version. (The upgrade installer also functions as a full installer.) During install, on the Customer Information screen, be sure to select "I am upgrading" in the bottom section, so that the upgrade will carry your license forward.

The simplest solution for a Concurrent Network client is:

  1. Uninstall your existing version of the software, in Control Panel » Programs and Features.
  2. Install the new version. (The upgrade installer also functions as a full installer.)

Last edited: 2015-09-14

1.16. "Error 1316. A network error occurred" in StatTools 5.5 install

Applies to: StatTools 5.5
(For a similar error with any 5.7 network installer, please see Server Install (5.7): "A network error occurred while attempting to read from the file ...". For this error with 6.x, please see "A network error occurred" in a 6.x/7.x install.)

Problem:
While installing StatTools, I get this error message:

Error 1316. A network error occurred while attempting to read from the file C:\Documents and Settings\All Users\Application Data\Local Cache\...\StatTools 5.0 for Excel, Industrial Edition.msi

Solution:
The Microsoft Windows Installer Cleanup Utility may be able to repair this condition; please contact Technical Support at support@palisade.com for a download link and instructions.

last edited: 2009-12-31

1.17. "Error 1316. The specified account already exists."

Applies to: All products

During install, I get this message:

Error 1316. the specified account already exists.

Are you installing with full administrative rights? To make certain that you are, right-click the installer and select Run as administrator.

The next most likely explanation is some bad registry entries. Microsoft offers a tool to solve these sorts of install and uninstall problems; please see Fix problems that block programs from being installed or removed. When the fix-it tool asks what you're trying to install, select "not listed" unless you're installing the exact same version that was previously installed. For example, both 7.5.0 and 7.5.1 would show up as 7.5 in the list in the fix-it tool, but they are different installers so you would select "not listed" if you're installing 7.5.1 over 7.5.0.

Last edited: 2017-01-20

1.18. "Error 1324. The path My Documents contains an invalid character."

When I run your installer, I get the message

Error 1324.
The path My Documents contains an invalid character.

or

Error 1324.
The path My Pictures contains an invalid character.

Is your My Pictures or My Documents folder actually on a remote computer on your local network? Just disconnect from the network temporarily to do the install.

If the folder is not on your own computer or your LAN, or if it is but the above doesn't work for you, please contact Palisade Technical Support for assistance.

Last edited: 2017-06-09

1.19. "Error 1905. Module ... failed to unregister."

Applies to:
All products, releases 5.x and newer

While reinstalling Palisade software, I get the error message

Error 1905. Module C:\Program Files\ ... failed to unregister. HRESULT -2147220472. Contact your support personnel.

The error message could mention any file name. Here are a few that we have in tickets in the Tech Support database: AtRiskOL.dll, PalGraph7Server.exe, PTreeOutOfProcessServer.exe, RiskOpt6DE.dll, StatTools5_EN.dll. But you could get this message with any file in our software.

For some reason, the installer is having trouble getting access to files that are already installed, possibly because something is still running. This procedure seems to work:

  1. Restart your computer — not just logging off and on, but a full restart.
  2. Save your license file, if you have a .LIC file in C:\Program Files (x86)\Palisade\System or C:\Program Files (x86)\Palisade\System.
  3. Deletie the folder C:\Program Files (x86)\Palisade folder or C:\Program Files\Palisade.
  4. Run REGEDIT, and go to to HKEY_LOCAL_MACHINE\Software\WOW6432Node in 64-bit Windows, or HKEY_LOCAL_MACHINE\Software\Palisade in 32-bit Windows. Under that key, delete the Palisade subkey.

This should let you reinstall the software.

Last edited: 2016-11-04

1.20. "Error 1935. An error occurred during the installation of assembly ..."

Disponible en español: "Error 1935. Ocurrió un error durante la instalación del ensamblado ..."

Applies to: All releases 6.x/7.x

When I try to install Palisade software, I get the error message

Error 1935. An error occurred during the installation of assembly component

followed by a long code in { } braces, or

Error 1935. An error occurred during the installation of assembly

followed by a Microsoft product name, such as Microsoft VC80.CRT.

This happens occasionally, and for most people the cure is simple: restart Windows (Start » Restart, not just logging off and on), then right-click the installer and select Run As Administrator.

If that doesn't work for you, there is a problem installing one or more of the Microsoft components that are included in the installer. These components are listed in Microsoft Components Required for Palisade 6.x Software Install or Microsoft Components Required for Palisade 7.x Software Install. Please install them manually, in order — but read the notes for each one because some may not apply to your situation.  (You can skip the installs of Project and SQL for now.)

If the Microsoft components all install without error, re-run our installer (again, Run As Administrator). It will sense that the components have been installed and will not try to install them again. This should get you past the problem and allow our software to install.

If one of the Microsoft components fails to install, do not go on to the next. Instead, you will need to fix the problem that prevents it from installing. If a Microsoft component doesn't install, there may be some problem in your Windows installation. You can try to repair it from your Windows install disk, if you have one, or by following this procedure:

  • Click the Start button and type cmd in the search window.  You should see cmd.exe at the top of the results, or close to the top.  Right-click it and select Run As Administrator.
  • In the Administrator window that opens, type this command: sfc /scannow

After SFC finishes successfully, close the window and then retry the Microsoft component install that failed.  If SFC fails, or if the same Microsoft component still will not install, please ask your IT department for assistance because this is an issue in your installation of Windows.

Last edited: 2015-09-14

1.21. "Error 2908. Could not register component"

Applies to: All Palisade software, releases 5.x/6.x

When I try to install Palisade software, I get the error message

Error 2908. Could not register component

followed by a long code in { } braces.

It looks like your .NET 2.0 installation is damaged. The solution is to uninstall and reinstall .NET 2.0, which our software uses. However, there may be higher versions of . NET on your computer, and those will also need to be uninstalled and reinstalled in a particular order.

Important: If you log in to your Windows computer using a nonstandard method (e.g., fingerprint reader, face recognition device, or voice recognition tool), turn off or uninstall the tool BEFORE you uninstall .NET. That way, if your tool requires .NET Framework, it won't prevent you from logging back in to your Windows computer.

  1. It's not required, but you may want to run the .NET Framework Setup Verification Tool first. If .NET passes verification, then it's not likely that uninstalling and reinstalling .NET will accomplish anything.

  2. Open Control Panel » Programs and Features, or click the Start button and enter programs and features in the search window. (In Windows XP, open Control Panel and then Add or Remove Programs.)

  3. Uninstall everything that starts with "Microsoft .NET", from highest version number down to lowest version number.

  4. Download and install all of the following that pertain to your versions of Windows, from lowest to highest number:

  5. Install the Palisade software.

Last edited: 2015-02-26

1.22. "Failed to load FNP_Act_Installer.dll"

Applies to: All installers for 5.x releases

Near the end of the install, I get the message

Error: -1
Failed to load FNP_Act_Installer.dll

and then the install fails.

Try a repair install of the product, using the instructions in Repair of Palisade Software.

Last edited: 2008-11-11

1.23. "Invalid Key Code" (Releases 1.x and 4.x)

Applies to:
All products, versions 1.x and 4.x

Problem:
While installing Palisade software, I type my serial number and key code when prompted, but I get the message "invalid key code".

Solution:
There are several possible causes and cures:

  • Make sure you're using the right code. If it has dashes or hyphens in it, it's an ID code or an authorization code, not a key code. Your installation key code was provided when you bought the software. If you can't locate it, call or email Palisade with the serial number and we will help you.

  • Check the code carefully. It contains only the digits 0 (zero) through 9 and the letters A through F. If you see something that looks like a letter I or L or O, it's actually the digit 1 or 0 (zero). If you see a dash or hyphen, it's not a key code at all.

  • If you're copy/pasting the code from an email, make sure you have all the characters but no spaces or tabs. The installers consider every character, even a space, as an intended part of the key code.

  • If you downloaded the installer, make sure you have the right product, the right version, and the right language.

    • @RISK for Excel is sold separately and also as part of The DecisionTools Suite, but they have completely separate installers. The installer for @RISK for Excel sold separately begins with RSK; the installer for the DecisionTools Suite begin with DTS.
    • A standard edition contains the letters STD, a professional edition contains the letters PRO, and an industrial edition contains the letters IND.
    • Non-English versions will have a two-letter suffix, such as _ES for Spanish.

    If you're not sure you have the right installer, please call or email Palisade Technical Support with the file name and your serial number and we will help you.

  • Make sure you have the right key code for this serial number. Sometimes a company will buy a block of serial numbers but mix up which key code goes with which serial number. Again, if you can't sort this out we will be happy to help you.

last edited: 2011-01-24

1.24. "Key not valid for use in specified state."

Applies to: All release 6.x products

During install, I get this message:

Key not valid for use in specified state.

First, make sure that your account has full administrative rights. Partial rights, "domain admin", or "local admin" may not be sufficient. In Vista and later, right-click the installer and select Run As Administrator; in Windows XP just double-click the installer.

Based on Internet research in October 2014, another possibility — unconfirmed at this writing — is a failed Windows update, specifically KB2918614. This update is known to cause problems with the Windows installer service, particularly for programs that install Microsoft Visual C++ Redistributable (which Palisade does). Please see Microsoft's article KB2918614 breaks Windows Installer Service (accessed 2014-10-27).

Last edited: 2014-10-27

1.25. "Msvcrt40.dll could not be opened"

Applies to: @RISK for Project 4.1

When trying to install @RISK, I get this error message:

The file 'C:\Windows\system32\Msvcrt40.dll' could not be opened. Please check that your disk is not full and that you have access to the destination directory.

This appears to be a Windows permissions problem rather than a problem in @RISK. For the solution, please see Microsoft's article msvcrt40.dll could not be opened, and use Method 2 to take ownership of the file. (Our link to the article was correct as of 2015-09-14. If the link does not work for you, try searching at Microsoft.com for the text "msvcrt40.dll could not be opened", with the quote marks.)

Last edited: 2015-09-14

1.26. "PalFlex5.dll" during silent install of 5.7

Applies to: All products, release 5.7

During a silent install of Palisade software release 5.7, I get an error box with just "PalFlex5.dll" in it, or the install simply hangs.

The PalFlex5.dll file, which is part of the Palisade software, requires a component called
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_b77cec8e
The interactive installer installs this component, but the silent installer does not. The silent install works on some PCs but not others, because some PCs already have that component installed.

Before beginning the silent install, run the vcredist_x86.exe update to Visual C++. (Note: The version of this exe is 6.0.2900.2180, but it contains files of the required version, which is 8.0.50727.4053.)

You can download this update from a Web page titled
"Microsoft Visual C++ 2005 Service pack 1 redistributable Package ATL security update"
which contains references to KB973544 and MS09-35. As of 2015-09-14, the URL is
http://www.microsoft.com/en-us/download/details.aspx?id=14431
But if that URL no longer works, use the above information to search for the file.

If the above does not solve the problem, please try what worked for one user: uninstalling and reinstalling the VC++ component.

Last edited: 2015-09-14

1.27. "Setup is unable to install Activation ID ..."

Applies to: All products, releases 6.x/7.x

My install will not finish. I get this message:

Setup is unable to install Activation ID activation-ID. See product Help Menu / License Manager to view available licenses or information on obtaining a new license.

How can I get past this and finish the install?

The message unfortunately does not give you the key piece of information, which is that this affects just the license, not the actual software install. For some reason, the installer was unable to do an Automatic Activation of your Activation ID. The two most likely causes are that your firewall prevents the installer from talking to Palisade's license server, or that the Activation ID is already activated.

Click the OK button to let the install finish. Assuming there are no other error messages, the software will be installed as a 15-day trial.

  1. If your Activation ID is already activated, deactivate it on the old computer before proceeding. (Run the software, click Help » License Manager, and select Deactivate. If Automatic Deactivation fails, select Manual Deactivation and follow the instructions on your screen.)
  2. Run the end-user software. You'll get a pop-up asking you to continue with trial or run License Manager.
  3. Select License Manager, click Activate, and enter your Activation ID.
  4. Select Manual Activation, not Automatic, and follow the instructions on your screen.

Last edited: 2016-03-02

1.28. "This installation package could not be opened."

I'm trying to download and install your software, but the installer puts up this message and refuses to run:

This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.

Please verify that your browser considers the download 100% complete before you start the install. 

If the download is 100% complete and you get this message, most likely there is a problem with the Windows Installer Service on your computer.  Either the service is disabled (blocked from running), or one or more of its files are corrupted.  Please visit Microsoft's article How to Troubleshoot Windows Installer Errors and follow the instructions there.  If you're unable to complete the instructions there, you may need to have your IT department run the procedure for you or unblock the Windows Installer Service.

If you have successfully repaired the Windows Installer Service and still have a problem with the install, please contact Palisade Technical Support.

Last edited: 2016-08-23

1.29. "This installer requires a certificate license ..."

Disponible en español: El instalador requiere una licencia basada en certificado...

Applies to: All Palisade software, release 6.x/7.x

When I try to install a network client, course workstation version, or textbook version, I get this error message:

This installer requires a certificate license (.lic) or network license (.ini) file in the same folder as setup.exe

If you are installing a commercial or academic network client:  During installation, a Palisade_NetworkClient.ini file must be in the same folder as the installer executable.  This file tells the installer how to find your server that holds the license information.  For instructions on creating and using this file, please see the 7.x Network Guide or 6.x Network Guide, specifically "Server Step 4", "Server Step 5", and "Client Setup Procedure".

If you are installing a course license on a standalone workstation:  With your software you received a .lic file containing the license information.  You must have that file in the same folder as the installer during installation. The license file must be named Palisade_Course.lic; if you rename it the installer may fail to find it.

IT personnel:  If you are installing an MSI version of the installer, it may need help in finding your .lic or .ini file.  Use the SETUPEXEDIR keyword to identify the location of the .lic or .ini file.  Please see Scripting the 7.x Client Install or Silent Install of 6.x Network Client.

Additional keywords: SETUPEXEDIR, MSI install

Last edited: 2015-12-01

2. All Products: Startup

2.1. I've installed the software. Why don't I see it in Excel?

Applies to:
The DecisionTools Suite, all releases
BigPicture, all releases
Evolver, all releases
NeuralTools, all releases
PrecisionTree, all releases
@RISK for Excel and RISKOptimizer, all releases
StatTools, all releases
TopRank, all releases

I installed the software, and the install ran to completion, but when I open Excel I don't see @RISK (BigPicture, Evolver, NeuralTools, PrecisionTree, StatTools, TopRank). What is wrong?

Nothing is wrong. By default, our software does not load automatically in Excel.

To launch the software: Either double-click the desktop icon (if you selected desktop icons during install), or click the Start Button and select the Palisade DecisionTools program group. If Excel is already running, the software will attach to the running copy; otherwise the software will launch Excel for you. (If Excel is already running and the software doesn't attach to it, look up the error message in this Knowledge Base or if appropriate see Nothing Happens When I Launch the Software.)

To make the software run automatically every time you run Excel: Please see Opening Palisade Software Automatically Whenever Excel Opens. That article lists some specific add-ins; please don't make any other Palisade add-ins active. Also, please don't manually add any toolbars. That is not necessary to make the software run, and it may actually cause the software to malfunction.

TIP: You can make it easier to launch @RISK without necessarily starting it every time you start Excel. In the Start menu, in the Palisade DecisionTools program group, right-click any of our icons and select Pin to Taskbar or perhaps Pin to Start Menu. Then you always have the software handy, without drilling down into the Start menu or moving windows that are covering a desktop icon.

But shouldn't it be in Excel's add-ins list?

Our software may appear in Excel's list of inactive add-ins. This is normal, not a sign of trouble. It doesn't need to be in Excel's list of active add-ins unless you want it to launch with Excel every time, as mentioned above.

Last edited: 2017-04-04

2.2. Nothing Happens When I Launch the Software

Applies to: @RISK and all other Palisade add-ins for Excel, all releases

I double-click the desktop icon for @RISK (StatTools, PrecisionTree, ...) and it seems like nothing happens. (A message "initializing Microsoft Excel" appears briefly, but that's all.) If I go through the Palisade DecisionTools group in the Windows Start menu, it's the same story.

The cause could be any of these issues.  From most common to most unusual:

A. Excel running but not visible

When you launch @RISK or any other Palisade add-in for Excel, it asks Windows to if there is open copy of Excel. If Windows says "no, there's no Excel running", @RISK will launch Excel and attach to it.

If Excel is already running, Windows will tell @RISK how to find Excel, and @RISK will attach to it. If that copy is not visible — if it's minimized, or hidden behind another window — you won't see @RISK do anything after "initializing". If there are multiple copies of Excel open, Windows won't necessarily choose the one you expect, even if one copy is open and visible on the desktop.

Check the taskbar carefully for copies of Excel, and bring each one in turn to the foreground. Chances are that @RISK just attached to a different copy of Excel from the one you expected, because that's the copy that Windows told it about.

It's also possible for Excel to be running in background, meaning without any indication in the taskbar. To check for this, press Ctrl+Shift+Esc to bring up Task Manager. Look at the Processes or Details tab to see all running processes, including those that don't have a window. Click the Image Name column head to sort the processes by name. If you have one or more copies of Excel that don't have a visible window, click each one and then click End Task or End Process. After killing all background copies of Excel, launch @RISK again.

B. Disabled add-in (Excel 2007 and newer)

If Excel crashes while an add-in from Palisade or another third-party vendor is loaded, Excel may disable that add-in. Check Excel's add-ins list by clicking File » Options » Add-Ins. (In Excel 2007, click the round Office button, then Excel Options at the bottom, then Add-Ins.) There are three lists: active add-ins, inactive add-ins, and disabled add-ins. If @RISK or other Palisade add-ins are disabled, you can re-enable them.

To re-enable disabled add-ins, look for the Manage: Excel Add-Ins box at the bottom of the list of add-ins. Click the drop-down arrow to change that to Disabled Add-Ins, and click Go. Select the add-ins to re-enable, and click the Enable button. There is no need to add Palisade add-ins to Excel's active add-ins list; it's enough that they are not disabled. Now use the desktop icon (if available) or the Start Menu group called Palisade DecisionTools to launch @RISK or whichever application you were trying to use.

C. Antivirus

If you have no invisible copies of Excel, your antivirus software may have blocked a Palisade component based on a false positive. Check your antivirus logs, and unblock the software component. Please report the exact name of the blocked file, and the full name of your antivirus program, to Palisade Technical Support, so that we can contact them to get the false positive corrected.

D. Policy setting

A few IT departments may unintentionally set Windows group policies that interfere with running Palisade software.  If @RISK can't add its tab to the Excel ribbon, please see @RISK Initializes, But No Tab Appears in Ribbon and @RISK Creates Empty Add-Ins Tab in Ribbon.

Last edited: 2015-11-25

2.3. Find and Fix Startup Conflicts (Excel 2007–2016)

Disponible en español: Buscar y corregir Conflictos de Inicio (Excel 2007–2013)
Disponível em português: Procurando e reparando conflitos na inicialização (Excel 2007–2013)

Applies to: All Palisade products running as add-ins to Excel 2016, 2013, 2010, or 2007.
If you have Excel 2000 through 2003, please see Find and Fix Startup Conflicts (Excel 2003 and Earlier).

Palisade software is not behaving correctly, and I think the problem may be a conflict with something else loaded in Excel. Do you have any kind of checklist for diagnosis?

If you have Excel 2013 or 2016, do this first: Open Excel and click File » Options » General. Remove the check mark from the last entry, "Show the Start screen when this application starts". Close Excel and reopen the Palisade software. (Why? One class of add-ins conflicts with some Palisade add-ins only when the Excel Start screen is enabled.) If that solves your issue, you can skip the rest of this article.

There are four potential sources of conflict: Excel add-ins, COM add-ins (two groups in separate lists), and your own automatic startup files.  When there's a startup conflict, turn off all the possible sources at once, then turn them back on again one at a time.  The Excel settings for this are scattered in several places in Excel and even in the System Registry.  We have tried to provide a step-by-step procedure to cover all the cases:

  1. Excel 2010 and later: click the File tab in the ribbon and then Options.
    Excel 2007: click the round Office button, then Excel Options.
    (If you can't even launch Excel, see Removing Excel Add-Ins if Excel Won't Start, below.)

  2. In the options list, click Add-Ins » Manage: Excel Add-Ins » Go. Remove the check marks from all third-party add-ins.

    If you have any Palisade add-ins checked (ticked), remove the check marks.  Our add-ins are designed to run without the check marks, except as explained in Opening Palisade Software Automatically Whenever Excel Opens.

    Excel's own add-ins such as Analysis Toolpak, Conditional Sum Wizard, Internet Assistant, Lookup Wizard, and Solver are not a problem.

    Get back to Options and click Add-Ins again. In the list of Active Add-ins at the top of the right-hand panel, are there any COM add-ins? If so, at the bottom click Manage: COM And-Ins » Go. Remove the check marks from all third-party add-ins. Caution: Some COM add-ins add themselves back if you disable them, either right away or the next time you open Excel. The next time you reopen Excel, verify that your COM add-ins have not re-enabled themselves.

  3. Get back to Options again and click Advanced, then scroll down to the General section. Look at the box labeled "At startup, open all files in". If there is anything in the box, make a note of it, temporarily clear the box, and click OK. (You will put that setting back later, in step 6.)

  4. Close Excel, open My Computer, and do a file search for XLSTART. There will probably be more than one folder with that name. Remove everything from every XLSTART folder. (You will put them back later, in step 7.)

  5. Now, run the Palisade software that was having a problem. If it now behaves correctly, then a startup conflict was responsible for the problem. But if the problem still occurs, please go to step 8.

  6. If Palisade software is now running okay, you can determine which item(s) provided the conflicts. Restore the setting of "At startup, open all files in", close Excel, and reopen our software. If the problem returns, you will have to eliminate items from that folder one by one, closing Excel and reopening our software each time, till the problem no longer occurs.

  7. Close Excel and restore one item to your XLSTART folders, then test our software. Repeat, closing Excel each time, till you've eliminated every conflict and added back every safe item.

  8. Some third-party COM add-ins don't appear in Excel's list, so you can't disable them there but must do it in the System Registry.  With Excel closed, click Start » Run, enter the REGEDIT command, and click OK.  Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins.  If it exists, right-click Addins and export it as a .REG file so that you can restore the settings later.  Then expand Addins and click on each subentry in turn, but not the "BigPicture Support Add-in", which comes from Palisade.  For each subentry, look at LoadBehavior in the right-hand panel and if it is 3 change it to 0.

    Repeat for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\Excel\Addins, whichever one exists.

  9. You might not actually have a startup conflict, but rather an outdated or unstable version of Excel. It's very important to make sure you have the latest Service Pack installed.

    • Excel 2016 is too new for Service Packs, but verify that you have a released copy, not a prebuild.
    • Excel 2013: Click FILE » Account » About Excel. You should have at least Service Pack 1 (SP1), which was released in October 2015.
    • Excel 2010: Click File » Help and then in the right-hand pane click "Additional version and copyright information". A new window will open, and the first line in that window will show the installed Service Pack (SP), if any. As of October  2015, the latest Service Pack is SP2, but if you're reading this article later, please check at Microsoft's site to make sure you aren't missing a new Service Pack.
    • Excel 2007: Click the round Office button, then Excel Options » Resources. Look at the last line in the right-hand panel to make sure Excel has at least SP2 (Service Pack 2) installed. If not, go to Microsoft's site to download the latest (SP3), then install it.
  10. Office 2007 only: We have found that a repair install (not a reinstall) of Office 2007 cures many problems, even right after you have installed an Office 2007 service pack. The procedure for the repair install is explained in Repair of Excel or Project.

Removing Excel Add-Ins if Excel Won't Start:

  1. Click Start » Run, type REGEDIT, and press the Enter key.  (You will probably need administrative rights for this.  If your IT department does this for you, they must log in as you with administrative rights, because this procedure must be performed within your user profile.)

  2. In the left-hand panel, navigate to HKEY_CURRENT_USER\Software\Microsoft\Office.

  3. Under Office, navigate to 12.0\Excel\Options for Excel 2007, 14.0\Excel\Options for Excel 2010, 15.0\Excel\Options for Excel 2013, or 16.0\Excel\Options for Excel 2016.

  4. For safety, make a backup copy of this entry, by right-clicking Options and selecting Export.  Chose any file name and location, but keep the file type as .REG.

  5. In the right-hand panel, right-click on each OPEN value and select Delete.  Answer Yes to the confirming prompt.

  6. Go back to HKEY_CURRENT_USER\Software\Microsoft\Office in the left panel, then down to Excel\Addins under Office. Right-click Addins, select Export, and pick a file name and location. Then, right-click the Addins key and select Delete.

  7. Now, go all the way back to the root of the Registry, then select HKEY_LOCAL_MACHINE\Software\Microsoft\Office\Excel\Addins or HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Office\Excel\Addins, whichever exists. Right-click Addins, select Export, and pick a file name and location. Then, right-click the Addins key and select Delete.

  8. Click File » Exit to close Registry Editor. 

Excel should now start without add-ins.  (Any startup files in your XLSTART folders are still loaded when Excel starts up, so be sure that you've already moved them.)

You can restore the previous values of those keys by double-clicking the .REG files that you saved.

Last edited: 2016-08-31

2.4. Find and Fix Startup Conflicts (Excel 2003 and Earlier)

Disponible en español: Buscar y corregir Conflictos de inicio (Excel 2003 y anteriores)
Disponível em português: Procurando e reparando conflitos na inicialização (Excel 2003 e anteriores)

Applies to:
All Palisade products running as add-ins to Excel 2003 or earlier
If you have Excel 2007 or later, please see Find and Fix Startup Conflicts (Excel 2007–2016).

Problem:
If you get an error message or a series of error messages when starting the software, you may have a conflict with one of your add-ins or startup files. Some possible messages include "Palgraph5 server error" or a runtime error with a long number.

Solution:
First try searching for the particular message in the Knowledge Books, but if you don't find it then you may be able to diagnose any conflicts by starting Excel in Safe Mode. (Excel Safe Mode is different from Windows Safe Mode.  You do not need to restart your computer.)

This procedure applies to Excel 2000 through Excel 2003, but not Excel 2007 or later.

  1. Close Excel if it's already running.

  2. Press and hold the Ctrl key, then click the Windows Start button and select Programs or All Programs » Microsoft Office » Microsoft Excel. Continue holding the Ctrl key down.

  3. When the prompt appears asking whether you want to start Excel in Safe Mode, release the Ctrl key and answer Yes.

    If the above doesn't open Excel in Safe Mode, please see Microsoft's Knowledge Base article How to troubleshoot startup problems in Excel (accessed 2014-01-08) and scroll down to "Let me start it myself".

  4. When Excel has loaded, click Tools » Add-ins. Remove the check marks from all third-party add-ins.

    If you have any Palisade add-ins checked (ticked), remove the check marks.  Our add-ins are designed to run without the check marks, except as explained in Opening Palisade Software Automatically Whenever Excel Opens.

    Excel's own add-ins such as Analysis Toolpak, Conditional Sum Wizard, Internet Assistant, Lookup Wizard, and Solver are not a problem.

  5. Click the Windows Start button, then Programs or All Programs, then Palisade DecisionTools, then the shortcut for the Palisade software tool you are having trouble with.

If the Palisade software now functions correctly, there was a conflict with another add-in or one of your own startup files. These can be specified in several places, so find them all and then eliminate them one by one till you find the conflict:

  • Click Tools » Add-ins. Uncheck all third-party add-ins. (Excel's own add-ins such as Analysis Toolpak, Conditional Sum Wizard, Internet Assistant, Lookup Wizard, and Solver are not a problem.) Then try loading and running the Palisade software.

  • Do a search on your disk for folders named XLSTART. (There will probably be more than one.)  With Excel not running, move all items from each XLSTART folder to another location. Then start the Palisade software and try to run it.

  • Click Tools » Options » General. Look at the box labeled "At startup, open all files in". If the box contains a path, open My Computer and navigate to the path. Close Excel, then move all items from that folder to another location. Try to run the Palisade software.

Removing Excel Add-Ins if Excel 2003 Won't Start:

  1. Click Start » Run, type REGEDIT, and press the Enter key.  (You will probably need administrative rights for this.  If your IT department does this for you, they must log in as you with administrative rights, because this procedure must be performed within your user profile.)

  2. In the left-hand panel, navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Options.

  3. For safety, make a backup copy of this entry:  Right-click Options and select Export.  Chose any file name and location, but keep the file type as .REG.

  4. In the right-hand panel, right-click on each OPEN value and select Delete.  Answer Yes to the confirming prompt.

  5. Click File » Exit to close Registry Editor.  Excel should now start without add-ins.  (Any COM add-ins, and any startup files in your XLSTART folders, will still be loaded.)

last edited: 2014-01-08

2.5. Palisade Software Loads Whenever You Run Excel

Applies to: All products, releases 5.x–7.x

Whenever I double-click an Excel file, or whenever I run Excel directly, @RISK and/or Evolver, NeuralTools, PrecisionTree, StatTools, or TopRank also runs. Why is this happening, and how can I prevent it?

Response:
ds. You have to launch Palisade software explicitly: either double-click one of our desktop icons (if available), or click Start » All Programs » Palisade DecisionTools and then a product shortcut.  (When you launch our software and Excel is already open, our software will attach itself to the running copy of Excel.  If Excel is not already running, our software will launch it for you.)

However, if you enable one or more of the Palisade add-ins in Excel's add-ins list, then Excel will load that add-in automatically whenever Excel itself loads. If you are seeing @RISK (or Evolver, or ...) every time Excel runs, it is because that add-in was checked (ticked) in Excel's add-ins list.

To restore the ability to launch Excel without Palisade, remove the check mark from the list in Excel.

See also:

Last edited: 2015-10-02

2.6. Application Settings Don't Persist

Applies to:
All products, releases 5.x–7.x
BigPicture, release 1.x

I made some changes in Application Settings, and clicked OK. Everything was fine until I closed Excel and reopened my Palisade software. Then I saw that the Application Settings had all reverted to their previous values, and my changes were lost.

The permissions in a portion of your System Registry are wrong.

Palisade software stores Application Settings in the System Registry, in subkeys under HKEY_CURRENT_USER\Software\Palisade. Somehow, you have write access to the keys where Application Settings are stored, but you don't have read access. You may have privilege to fix this, or you may need to call in your IT department. Here is the procedure:

  1. Launch the REGEDIT program. How you do that will vary, depending on your setup:

    • If you have a Windows key on your keyboard, press it and R at the same time, then type REGEDIT in the box and press the Enter key.
    • If you have a start Menu, click Start » Run, type REGEDIT and press the Enter key.
    • In some versions of Windows, bring up a search window and search for the app called REGEDIT.
  2. Navigate to HKEY_CURRENT_USER\Software, and if necessary click the triangle or plus sign to expand it.

  3. Right-click on Palisade and select Permissions. In the Permissions dialog, click the Advanced button.

  4. In the Advanced Security Settings dialog, click your user name (your Windows login), then click the Edit or View button. In the Permission Entry dialog, you should have Full Control. If you do, click Close and go to the next numbered step.

    • If you don't have Full Control, tick that box and click OK.
    • If you can't edit the permission boxes, permissions are inherited from a parent key. Close the Permission Entry dialog, then in the Advanced Security Settings dialog click Disable inheritance » Convert inherited permissions into explicit permissions. Click your user name and the Edit button. Tick the Full Control box and click OK.
  5. Back on the Advanced Security Settings dialog, tick the box Replace all child object permission entries with inheritable permission entries from this object, click Apply, and answer Yes to the confirmation prompt. If you get any kind of failure message, you will need to take ownership of the problem subkey(s). If you're not sure how to do that, do a Web search for "take ownership of registry key".

Last edited: 2015-12-24

2.7. Old Version Appears Even after an Upgrade

Applies to: All Palisade software, version 6.x or 7.x

I upgraded from version 5.x or 6.x to a later release, but when I launch Excel the old software still loads.

You have the old version listed as an active add-in in Excel. The cure is simply to remove it from Excel's list.  Use the instructions below, based on your version of Excel.

There is no need to have any Palisade add-ins checked (ticked) in Excel's add-ins list; they will all run just fine without that.  You would place a check mark in Excel's list for a Palisade add-in only if you want to force that Palisade add-in to start every time Excel starts.  For more, please see Opening Palisade Software Automatically Whenever Excel Opens.

Excel 2010 and newer:

  1. Click File » Options » Add-Ins.
  2. At the bottom of the right-hand pane, click the Go button.
  3. Excel's list of add-ins appears. Remove the check marks from old versions of Palisade software.
  4. Click OK and close Excel.

Excel 2007:

  1. Click the round Office button at the upper left of the Excel window.
  2. At the bottom of the left-hand pane, click Excel Options.
  3. In the middle of the left-hand pane, click Add-Ins.
  4. At the bottom of the right-hand pane, click the Go button.
  5. Excel's list of add-ins appears. Remove the check marks from old versions of Palisade software.
  6. Click OK and close Excel.

Excel 2003 (compatible with Palisade software releases 6.x and older):

  1. Click Tools » Add-Ins.
  2. Excel's list of add-ins appears. Remove the check marks from old versions of Palisade software.
  3. Click OK and close Excel.

Last edited: 2015-10-02

2.8. License Manager Says Maintenance Has Expired, But We Renewed It

Applies to: All Palisade software, releases 6.x/7.x

When I try to run @RISK (PrecisionTree, StatTools, etc.), License Manager pops up and says EXPIRED for my maintenance date.  But I know that my company renewed our maintenance.  How can I run the software?

When you renew maintenance, we update information on our server with the new maintenance date.  However, the Palisade software on your computer caches the maintenance expiration date so that it doesn't need to go out on the Internet every time you run.  Usually the software knows when it is necessary to re-query our server, but if you're not on the Internet or your firewall prevents access to our server then the cache may need to be reset manually.

Please contact Technical Support with a screen shot of License Manager, and they will help you reset the cache so that the software knows your correct maintenance date.

Additional keywords: Wrong maintenance expiration date

Last edited: 2016-04-28

2.9. One User Doesn't Get the Activated License

Applies to:  All products, releases 6.x/7.x

I activated a standalone license on a computer, and it works fine for me, but when another user tries to run on the same computer she still gets the trial license.

The user will need to select the activated license. (If you want to do it for her, you must log in on her Windows account.) Here's the procedure to follow under that user's login:

  1. Launch the software.
  2. If License Manager doesn't come up by itself, click Help » License Manager.
  3. In License Manager, click Select License, select the activated license, and click OK.

For more information about how the software decides which license to use, please see Which License Gets Used?

Last edited: 2015-10-05

2.10. Concurrent Network Client Takes Very Long to Start

Applies to: Concurrent Network clients, releases 6.x/7.x

When I launch the software, the Excel status line seems stuck at "Authorizing...."  If I wait for a long time, it does eventually find a license.  What is taking so long?

Have you redirected any of the Windows special folders to network drives? Flexera introduced a change between FLEXnet Publisher 11.4 (in Palisade's 5.x releases) and FLEXnet Publisher 11.10 (in Palisade's 6.x and 7x releases). Now, FLEXnet checks dates of files in folders that are listed in subkeys under "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" in the System Registry.

If you have redirected any of those to a network drive, try making it local and see if that solves the problem.  If you have any UNC paths in those keys, try replacing them with mapped network drives.

Last edited: 2015-10-05

2.11. Concurrent Network Client Requests Activation ID (5.x only)

Applies to: All 5.x network client software (not 6.0 or newer)

I installed the 5.x network client successfully, but when I try to run it, I get a Palisade License Activation screen asking me for an Activation ID.

Releases 5.x unfortunately displayed an activation prompt whenever there was any kind of problem with the network license. This is fixed in releases 6.x and newer. If you have a current maintenance contract, you can upgrade your network at no charge; just contact your Palisade sales office.

But of course you want to solve the individual user's problem right away, even if you intend to upgrade later.  There are several possible causes, but the most likely is incorrect installation. Here are the things to check:

Was the software installed on this workstation as a network client, and not a standalone trial?

During installation, the Client.ini file must be present in the same folder as the installer executable. Typically this folder is on the server as C:\Program Files\FLEXnet\Palisade\your serial number\ClientInstaller or C:\Program Files (x86)\FLEXnet\Palisade\your serial number\ClientInstaller folder. The network information is in that Client.ini file.

To install the client software, use Network Neighborhood or similar to point to the ClientInstaller folder on the server, then right-click the installer there and select Run As Administrator. If you prefer, you can copy both files to a network share, USB stick, or the client's desktop and do the install that way. The key requirement is that the Client.ini file must be in the same folder as the installer during installation. Otherwise, the installer will appear to succeed but it will not know that you have a network copy and will install a trial standalone copy.

To fix this particular client's installation, please see Changing a 5.x Standalone Copy to a Concurrent Network Client.

To avoid this problem for future client installs, use the ClientInstaller folder as described above.

Are server and client set up to use the same name and port?

On the server, look at your license file. (It is in the same folder as Palisade.exe, and has a .lic extension.) The port number is an optional field on the SERVER line, following the Ethernet address or the word ANY. If no port number is specified, the server dynamically selects a port in the rage 27000 to 27009.

Run LMTools and click System Settings.  The first field, Computer/Hostname, is the name of the server as far as FLEXnet is concerned.

On the client, look in the System Registry, at the key
HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE or
HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE.
The port number precedes the @ sign and server name.  If no port number precedes the @ sign, the client dynamically negotiates a port number 27000 to 27009 with the server.

The server name in the client's System Registry should match the host name in LMTools.  (There are some unusual exceptions, where network administrators use fully qualified domain names or IP addresses.  These must be carefully tested.)

If the license file on the server specifies a port number, the System Registry key on the client must specify the same port number. If the license file on the server does not specify a port number, the System Registry key on the client must not specify a port number.  For more information, please see "Edit the Client.ini file" and "Redirect any installed clients" in Redirecting a 5.x/4.x/1.x Concurrent Client to a New Server.

Can the client communicate with the server?

Verify that the client can communicate with the server using the server name and port number specified in the System Registry key.  If no port number is specified, all ports in the range 27000 through 27009 must be open.

You can test whether a given port is open by using Telnet. (This requires a Telnet client on the client computer and a Telnet server on the server. These are part of Windows, but they might not be turned on. If they're not enabled, you can enable them in Windows Control Panel » Programs and Features » Turn Windows features on or off.) The command format is

telnet myservname 27000

You should get a blank screen if the port is open. If it's not, you should get an error message within about 60 seconds.

Also verify that the firewall on the client is allowing PalFlexServer5.exe to send and receive packets.

Is the license process running on the server?

Run LMTools and select Server Status » Perform Status Enquiry.  If you do not see "Palisade UP within the display", the process is not running.  Try starting it (on the Start/Stop/Reread tab) and re-check status.  If it still is not running, click Config Server » View Log and look at the end of the log for error messages.  Troubleshooting help is at Network Server Issues.

Is a license available?

If all licenses are currently in use, 5.x will pop up a Palisade License Activation screen without providing an explanation. Please see Monitoring License Use on 5.x Concurrent Network for instructions to check the licenses in use and verify that one is available.

Last edited: 2015-10-05

2.12. @RISK Creates Add-Ins Tab in Ribbon, with Tiny Icons

Applies to: All products, releases 6.3.0 and earlier, running under Excel 2007 or newer
(This article is written in terms of @RISK, but the same problem could happen with any of our add-ins.)

When I launch @RISK, I don't get an @RISK tab in the ribbon. Instead, small versions of the @RISK icons populate an Add-Ins tab in the ribbon.

Or, when I try to launch @RISK, I get a pop-up a message such as:

Cannot run the macro "C:\Program Files\Palisade\RISK6\Risk.xla'!RiskEvent_ExecuteCommand'. The macro may not be available in this workbook or all macros may be disabled.

(The path may vary, but the macro name at the end is always RiskEvent_ExecuteCommand.)

If @RISK creates an Add-Ins tab but doesn't put any icons in it, see @RISK Creates Empty Add-Ins Tab in Ribbon.

Our initial Risk.xla add-in loads helper add-ins. There is a policy setting called "Automation Security". The normal value of this is 1. But if it is set to 3, then Excel will not allow add-ins to load other add-ins. @RISK is unable to load the file that creates the @RISK tab in the ribbon, or @RISK fails with the message above.

You can determine the value of this setting from within Excel, as follows:

  1. Press Alt+F11 to open the Visual Basic Editor, then Ctrl+G to open the Immediate Window.

  2. Copy/paste the text

    ?Application.AutomationSecurity

    (including question mark) into the Immediate Window and press Enter.

If the value displayed is 1, this setting is not the problem. Please contact Technical Support for assistance.

If the value displayed is 3, this is why @RISK cannot run. Please see "@RISK cannot be started because of the following Office security setting" for permanent and temporary solutions.

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

Last edited: 2016-05-02

2.13. @RISK Creates Empty Add-Ins Tab in Ribbon

Applies to: All products, running under Excel 2007 or later
(This article is written in terms of @RISK, but the same problem could happen with any of our add-ins.)

When I launch @RISK, I don't get an @RISK tab in the ribbon. Instead, an Add-Ins tab appears, but there are no icons in it.

If @RISK creates an Add-Ins tab and populates it with miniature versions of the @RISK icons, see @RISK Creates Add-Ins Tab in Ribbon, with Tiny Icons.

Either Visual Basic for Applications (VBA) is not installed, or there's something wrong with the installation. To test this, in Excel press Alt+F11. If the Visual Basic Editor comes up, then VBA is installed, but it may not be installed correctly. Please perform a Repair of Excel.

If the Visual Basic Editor does not appear when you press Alt+F11, then VBA is not installed. Follow these steps to install it:

  1. Close all instances of your Microsoft Office applications.
  2. In Control Panel » Programs and Features, select your Microsoft Office and click Change or Modify.
  3. The Office installer will launch. Select Add or Remove Features and click Continue.
  4. The next panel in the dialog shows installation options. In the list, under Microsoft Office, find Office Shared Features and click the + sign at its left.
  5. In the sub-list that opens, find Visual Basic for Applications and change it to Run from My Computer. Click Continue, and VBA will be installed.

Last edited: 2015-09-03

2.14. @RISK Initializes, But No Tab Appears in Ribbon

Applies to: All products, running under Excel 2007 or newer
(This article is written in terms of @RISK, but the same problem could happen with any of our add-ins.)

If one of these more accurately describes your situation, please refer to that article instead of this one:

When I launch @RISK, I see the initialization window, and the status messages at the bottom of the Excel window. There's no error message, but the @RISK tab doesn't appear, and there's no Add-Ins tab.

There are several possible causes and cures for this problem. In no particular order:

  1. You may simply need to tell Excel to trust our software.
    1. To test this, launch Excel only.
    2. Click File » Open, and navigate to C:\Program Files (x86)\Palisade (if it exists) or C:\Program Files\Palisade.
    3. Under that folder, open the folder for your software, such as RISK7 or StatTools6. If you have the DecisionTools Suite, it doesn't matter which product folder you select.
    4. Then double-click the appropriate add-in, which will be Risk.xla, Evolver.xla, NeuralTools.xla, Ptree.xla, StatTools.xla, TopRank.xla, or BigPicture.xlam.
    5. If you get a security popup, look in the dialog for a check box labeled Trust all from this publisher, and tick it. If the software then opens normally, you have solved the problem and you won't get the security prompt in the future.
    6. If you get "Error in loading DLL", use this Microsoft article to uninstall Office completely. We recommend the easy Fix It in Option 2.
  2. Your COM Type Library may have outdated entries, or may not be functioning correctly. To check for outdated entries, see Removing Outdated References to Office from the System Registry. If your COM system is not functioning correctly, a repair of Microsoft Office may or may not fix it, but it's definitely worth a try.
  3. Another possibility is a setting in Group Policy or Office Customization Tool, "Disable UI extending from documents and templates" which prevents our software from adding its tab to the Excel ribbon.

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

  4. Did your antivirus software block a Palisade component based on a false positive? Check your antivirus logs, and unblock the software component. Please report the exact name of the blocked file, and the full name of your antivirus program, to Palisade Technical Support, so that we can contact them to get the false positive corrected.
  5. One of the above solutions works for almost everyone with this problem, but for a small minority they all fail. Two users found that after they uninstall 64-bit Office and install 32-bit Office, @RISK works normally. We don't know why.

     If you don't actually need 64-bit Office, and everything else has failed, you might wish to try this option also. Most people need only 32-bit Office; Should I Install 64-bit Excel? can help you decide whether you are one of them.

    We can't guarantee that this "nuclear option" will work for you, but we're not aware of anyone who has tried the other suggestions without success, then switched to 32-bit Office, and not had it solve the problem. If you decide to go this route, then before you uninstall 64-bit Office make sure you have your product key and that it will cover 32-bit Office also. (Most product keys cover both, but we can't help with issues installing or licensing Microsoft software, so check this yourself.)

Last edited: 2017-04-14

2.15. @RISK Turns NumLock Off

Applies to: @RISK 6.x/7.0.0

I have NumLock on, and I'm using Excel 2013 or 2016. When I launch @RISK, NumLock is turned off. What is wrong?

This is actually caused by a bug in Excel. We worked around it beginning with release 7.0.1 of @RISK. If you have current maintenance, your best solution is to upgrade to the current release. Ask Technical Support for an installer. (Include your serial number or Activation ID in your message.)

If you have @RISK 6.x with current maintenance, upgrade to version 7 to resolve this problem (and get great new features). Your Palisade sales office can assist you.

If you have 7.0.0 or older without maintenance, or policy in your organization doesn't allow upgrades, there's an easy fix: in Excel, click File » Options » General and remove the tick mark on the last option, Show the Start screen. Click OK and close Excel.

Last edited: 2017-02-17

2.16. CmdBarData Registry Key

Summary:
A particular key in the Excel Options section of the Windows system registry sometimes grows very long. Excel gets confused, and when you try to run Palisade software you get mysterious run-time error messages. Deleting this key may cure the problem and let Excel interface successfully with Palisade software and other add-ins.

Procedure:

  1. Make sure that Excel is not running.
  2. Click the Windows Start button, then Run. Enter the command REGEDIT and click OK to open the Registry Editor.
  3. Navigate to the key HKEY_CURRENT_USER\Software\Microsoft\Office in the left-hand pane.
  4. Within the Office key, double-click to open the subkey 14.0, 12.0, 11.0, 10.0, or 9.0 depending on your version of Excel.
  5. Within that numbered key, double-click on Excel, then on Options.
  6. Now look at the right-hand pane. Find CmdBarData, right-click on it, and select Delete. When you get the confirming prompt, answer Yes.
  7. Close the Registry Editor with File » Exit.

last edited: 2010-01-11

2.17. "... requires Excel 2007 or higher."

Applies to:
All products, release 7.0.0 or newer

I launch my Palisade software, and I get one of these messages:

@RISK requires Excel 2007 or higher.

BigPicture requires Excel 2007 or higher.

Evolver requires Excel 2007 or higher.

NeuralTools requires Excel 2007 or higher.

PrecisionTree requires Excel 2007 or higher.

StatTools requires Excel 2007 or higher.

TopRank requires Excel 2007 or higher.

Beginning with release 7.0.0, @RISK and our other software require an Excel version that uses the ribbon, rather than the older-style menus. If you're actually running Excel 2003 or earlier, you need to upgrade to a more recent Excel. You'll find a full list of compatible versions in Windows and Office Versions Supported by Palisade.

But I actually do have a later version of Excel!

In that case, please work through this checklist:

  • Do you have a System Registry key HKEY_LOCAL_MACHINE\Software\WOW6432Node\Palisade\Excel Path, or HKEY_LOCAL_MACHINE\Software\Palisade\Excel Path, that points to an old or nonexistent version of Excel? If so, right-click Excel Path and select Delete. Then, when you next run our software, it should connect automatically to your recent Excel.

  • You may be getting a security prompt when Palisade software tries to load itself into Excel. This can occur, for example, when you had two versions of Excel installed, and you uninstalled the one that was previously used with Palisade software. To give you a chance to respond to that prompt, follow this procedure:

    1. Run Excel only, not Palisade software.
    2. Click File » Open. Navigate to C:\Program Files (x86)\Palisade or C:\Program Files\Palisade, whichever exists.
    3. Inside that folder, click the product folder for the product you're trying to run: RISK7, StatTools7, etc.
    4. Double-click the main XLA file for the product you're trying to run: Risk.xla, StatTools.xla, etc. (The .XLA extensions may be visible or hidden, depending on your Windows settings.)
    5. You should now see a permission prompt. Check (tick) the box that says to trust all from this publisher. The software should then finish loading its ribbon.
  • Do you open Excel via some sort of redirection software, such as OpenWith? If so, please follow the directions in Which Version of Excel Is Opened by Palisade Software? The System Registry key you create must point to the real Excel, not the redirector, and Excel must be installed locally on this computer.

  • If the problem remains after following the bullets above, run a repair of Microsoft Office and restart Windows.

Last edited: 2017-01-17

2.18. "/R .xlsx could not be found."

Applies to: @RISK 6.1.1 (fixed in 6.1.2)

When I launch @RISK, I get the message

/R .xlsx could not be found. Check the spelling of the file name, and verify that the file location is correct. If you are trying to open the file from your list of most recently used files, make sure that the file has not been renamed, moved, or deleted.

or a similar message involving "C:\Program" or "ANALYS32" or some other file name or path.

Unfortunately, there was a problem in @RISK 6.1.1. When simulating with multiple CPUs, it may sometimes corrupt Excel's list of add-ins. Then the next time you open Excel, you get messages like the above. Palisade apologizes for this problem.

This error was fixed in @RISK 6.1.2, released 2013-04-16. You will want to upgrade to the current release, if you are eligible.

To clear the error:

  1. Open Excel, if it is not already open.

  2. In Excel 2010 or later, click File » Options » Add-Ins. At the bottom of the right-hand panel, select Excel Add-Ins and click Go.

    In Excel 2007, click the round Office button and then Excel Options » Add-Ins. At the bottom of the right-hand panel, select Excel Add-Ins and click Go.

    In Excel 2003, click Tools » Add-Ins.

  3. Remove the check mark from @RISK, if there is one. Remove the check marks from Excel's own add-ins, including Analysis Toolpak, Analysis Toolpak VBA, Euro Currency Tools, HTML Assistant, and Solver. If you have any third-party add-ins checked, you do not need to remove those check marks.

  4. Click OK. You may see a message telling you that an add-in cannot be located and asking permission to remove it from the list; click Yes.

  5. Close Excel.

Many people have some Excel add-ins checked although they don't actually use them. If you don't need Analysis Toolpak or the other Excel add-ins, you can ignore the rest of this article.

But if you need one or more of Excel's own add-ins, before you re-enable them you should upgrade to the current release if you are eligible to upgrade. Otherwise, to prevent a recurrence in @RISK 6.1.1:

  1. Launch Excel (not @RISK).

  2. In Excel 2010 or later, click File » Options » Add-Ins. At the bottom of the right-hand panel, select Excel Add-Ins and click Go.

    In Excel 2007, click the round Office button and then Excel Options » Add-Ins. At the bottom of the right-hand panel, select Excel Add-Ins and click Go.

    In Excel 2003, click Tools » Add-Ins.

  3. Re-enable the Excel add-ins that you need.

  4. Close Excel. Important: Complete the following steps before you run @RISK 6.1.1 again.

  5. Click Start » Run, enter the command REGEDIT and click OK.

  6. Navigate to the key HKEY_CURRENT_USER\Software\Microsoft\Office and double-click the word Office.

  7. Double-click the subkey for your version of Office: 15.0 for Office 2013, 14.0 for Office 2010, 12.0 for Office 2007, or 11.0 for Office 2003.

  8. Under that subkey, double-click Excel and then single-click Options.

  9. In the right-hand panel, you will see an entry OPEN and possibly some additional entries OPEN1, OPEN2, and so on. Look at the ones where the string in the last column begins with /R.

    For each of those, double-click the word OPEN (OPEN1, OPEN2, etc.) in the first column. In the edit window, remove the leading /R and space, then click OK. (You need to double-click the word in the first column, not the text in the third column.)

  10. Close the Registry Editor by clicking the X in the upper right corner.

Last edited: 2017-02-17

2.19. "@RISK cannot be started because of the following Office security setting ... automationsecurity=3"

Applies to: All products, releases 7.0.0 and newer

(This article is written in terms of @RISK, but the same problem could happen with any of our add-ins.)

The software installed just fine, but when I launch it I get

product cannot be started because of the following Office security setting in the registry:

software\policies\microsoft\office\common\security!automationsecurity=3

You, or more likely your IT department, have set a Group Policy setting that does not let @RISK or our other software run.

This policy setting called "Automation Security" determines whether an add-in is allowed to add helper add-ins. Our initial Risk.xla add-in loads helper add-ins, and so do our other procducts. The normal value of the "Automation Security" setting, as recommended by Microsoft, is 1. But if it is set to 3, then Excel will not allow add-ins to load other add-ins, and @RISK fails with the message above. (This setting was always a problem, but beginning with release 7.0.0 our software diagnoses it for you.)

The solution depends on whether you're dealing with a Group Policy setting or a direct edit to the System Registry:

  • Run Regedit, if your Windows login has permission. Check the two keys HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\Common\Security and HKEY_CURRENT_USER\Software\Microsoft\Office\Common\Security. Under each one, delete AutomationSecurity or change its value to 1.

  • If you can't make that change, or if it doesn't stick when you restart Windows, talk to your IT department and get them to make the change for you. They may also need to remove the "Automation Security" policy setting from the Group Policy editor or Office Customization Tool.

As a temporary workaround, you can try enabling @RISK for each session of Excel. Follow this procedure:

  1. Close Excel if it's open, to purge the failed @RISK startup.  Reopen Excel.

  2. Press Alt+F11 and then Ctrl+G to go to the Immediate Window. Paste

    Application.AutomationSecurity = msoAutomationSecurityLow

    into the Immediate Window and press Enter. (Notice that there is no question mark at the start of this command, as you would use to display values.)

  3. Close the Visual Basic Editor but keep Excel open. Launch @RISK from the desktop icon or via Start » Programs » Palisade DecisionTools.

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

Last edited: 2016-05-19

2.20. "@RISK cannot be started because of the following Excel security setting ... noextensibilitycustomizationfromdocument=1"

Applies to: All products, releases 7.0.0 and newer

(This article is written in terms of @RISK, but the same problem could happen with any of our add-ins.)

The software installed just fine, but when I launch it I get

product cannot be started because of the following Excel security setting in the registry:

software\policies\microsoft\office\X.0\common\toolbars\excel!noextensibilitycustomizationfromdocument=1

(X is 12 in Excel 2007, 14 in Excel 2010, 15 in Excel 2013, and so on.)

You, or more likely your IT department, have set a Group Policy or Office Customization Tool setting that does not let @RISK or our other software run. "Disable UI extending from documents and templates" prevents our software from adding its tab to the Excel ribbon. (This setting was always a problem, but beginning with release 7.0.0 our software diagnoses it for you.) Please ask your IT department to remove that policy setting.

As a temporary workaround, you can follow this procedure if you have privilege to edit the System Registry. (The problem key is usually under HKEY_CURRENT_USER, but this procedure will find it wherever it is.)

  1. Open REGEDIT.
  2. Collapse the left-hand panel and click on Computer.
  3. Press Ctrl+F, and in the search window enter "NoExtensibilityCustomizationFromDocument" (without quotes, and upper/lower case doesn't matter). Under Look at, select Values and Match whole string, and deselect Keys and Data.
  4. Click Find Next. Change the displayed value from 1 to 0.
  5. Press F3, and change the value from 1 to 0. Repeat until there are no more hits. (You may find some 0 values along the way. You can ignore those, but keep searching until you've looked at all occurrences.)

Even if you're able to do this edit, you will probably have to do it again after any reboot of Windows. The best procedure is to get your IT department to remove the problem policy setting.

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

Last edited: 2017-04-26

2.21. "ActiveX Component Can't Create Object (@RISK)"

Applies to:

@RISK 5.x–7.x

For run-time error 429 in @RISK 4.x, please contact Palisade Technical Support.

For StatTools and NeuralTools, see "ActiveX Component Can't Create Object (StatTools and NeuralTools)".

When I try to launch @RISK, I get

@RISK Launcher
Run-time error 429
ActiveX component can't create object

First, make sure your Excel and Windows support your version of @RISK.  See Windows and Office Versions Supported by Palisade.

If you have compatible Windows and Excel, then one of the components of @RISK, most likely RiskOL or one of its dependents, is unregistered or misregistered in the System Registry.

Please log on to Windows as a full administrator. Then re-run the installer and when prompted for Modify or Repair select Repair. (In Windows 8, Windows 7, and Vista, you need to log on as a full administrator and also right-click the installer and select Run as administrator.)

Textbook users:

If you have a 7.x textbook version of the software, don't reinstall the textbook version. Instead, contact Palisade Technical support, mention your textbook name, and ask for the latest DTSuite7-Setup.exe. Download that installer to your desktop, then right-click it and select Run as administrator. If you're prompted for Modify or Repair, select Repair. If you see a Customer Information screen during install, change "15-day trial" to "I am upgrading or reinstalling".

If you have a 6.x textbook version, uninstall it in Control Panel, then do a fresh download. (Have your textbook handy, to answer the challenge question.) You'll get the 7.x textbook version automatically.

Last edited: 2016-03-01

2.22. "ActiveX Component Can't Create Object" (StatTools and NeuralTools)

Applies to:
NeuralTools 5.x–7.x
StatTools 5.x–7.x
For @RISK, see "ActiveX Component Can't Create Object (@RISK)".

When I try to launch StatTools or NeuralTools, I get

ActiveX component can't create object

If you get this error the first time you run the Palisade software, make sure it's supported in your Excel and Windows versions.  See Windows and Office Versions Supported by Palisade.

We have seen some cases where this error appears after Windows 10 updates, particularly the Windows 10 Anniversary Update. If your software was previously working in Windows 10, a repair install will fix the problem. Please log on to Windows as a full administrator. Then re-run the installer and when prompted for Modify or Repair select Repair. (In Windows 8, Windows 7, and Vista, you need to log on as a full administrator and also right-click the installer and select Run as administrator.)

Textbook users:

If you have a 7.x textbook version of the software, don't reinstall the textbook version. Instead, contact Palisade Technical support, mention your textbook name, and ask for the latest DTSuite7-Setup.exe. Download that installer to your desktop, then right-click it and select Run as administrator. If you're prompted for Modify or Repair, select Repair. If you see a Customer Information screen during install, change "15-day trial" to "I am upgrading or reinstalling".

If you have a 6.x textbook version, uninstall it in Control Panel, then do a fresh download. (Have your textbook handy, to answer the challenge question.) You'll get the 7.x textbook version automatically.

Last edited: 2016-08-26

2.23. "Authorization failure ... TransactNamedPipe"

Applies to: Palisade software releases 6.x/7.x

When I try to run the software, I get this error message:

Authorization failure
Details:
Unexpected status=0, err=109, for kernel function TransactNamedPipe, after calling TransactNamedPipe.

This error (from the FLEXnet licensing system) seems to occur rarely, but for no very clear reason.

First advice: simply close all instances of Excel and try running the software again.  Usually the error does not repeat, which is one reason it's so difficult to pin down.

If the error does repeat, run the software with administrative rights. This resolved it for both users who reported this experience.  One user right-clicked the @RISK icon and selected Run As Administrator; the other logged in to Windows with an administrator account. If running as administrator succeeds, you may want to try running as a regular user after that. (Our end-user software does not normally require administrative rights to run; a Windows "regular user" account should be fine.  But privileges and access control are more complex in every new version of Windows, and it's possible to create an account that shows as regular user in Control Panel even though it does not have the normal permissions of a regular user.  In that case, running as administrator may be a quicker solution than trying to untangle the details of the permissions.)

Last edited: 2015-10-05

2.24. "Automation error: %1 is not a valid Win32 application"

Applies to:
All products

Problem:
I try to start @RISK or another product, and I get the above error message.

Response:
Check in the root folder of your C: drive for a zero-byte file called Program. (You may need to change Explorer options so that you can view hidden files and folders.) If you find that file, delete it.

If the file doesn't exist, or if deleting it doesn't cure the problem, you may have a problem with the path of a service in Windows. For the problem description and solution, please see Event ID 7000 and "%1 Is Not a Valid Win32 Application" Error Message When You Start a Service in Microsoft's Knowledge Base (accessed 2012-11-09).

last edited: 2012-11-09

2.25. "Automation Error. Element not found."

Applies to:
Evolver 6.x
NeuralTools 6.x
StatTools 6.x
TopRank 6.x

Problem:
I have 64-bit Excel. When trying to launch one of these tools, I get the above error message.

Response:
This is caused by the Skype toolbar. Please see "Method 'ExecuteCommand' of object '_PalUtil' failed" for more details and a solution.

last edited: 2012-02-02

2.26. "Automation error: Interface not registered"

Applies to:
All products

Problem:
When I try to launch @RISK or another Palisade application, I get this message:

Automation error
Interface not registered

Response:
This is actually a problem in your Microsoft Office. Repairing Office should work, or you can reinstall Office.

Last edited: 2014-08-26

2.27. "Automation error: Library not registered"

Applies to:
All products

Problem:
When I try to launch the Palisade software, I get the error message

Automation error: Library not registered

I've tried repairing the Palisade software, but that didn't help.

Response:
This appears to be due to an error in the System Registry entries for Excel, not Palisade. If you have Excel 2007 and you have the option to upgrade to 2010, several users reported that upgrading fixed their problem.

This error is especially likely if you have multiple versions of Excel and uninstall one of them.  In that case, one or more keys in the System Registry are left behind pointing to the version of Excel that no longer exists.  To remove these "orphan" keys, please follow the procedure in Removing Outdated References to Office from the System Registry.

Additional keywords: Error 2147319779, -2147319779

last edited: 2014-02-28

2.28. "Automation error: The callee (server [not server application]) is not available:

Problem:
The following error message appears:

Automation error
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed.

Response:
This may arise from incompatibility with a third-party add-in. The only one that we know of at this writing is Morningstar Commodity Add-In 3.2.6. It is not necessary to uninstall the add-in, but you will need to disable it while running @RISK.

If you recently installed some other third-party add-in and this message began appearing with @RISK, try disabling that add-in and see if @RISK now runs successfully. If it does, please contact Technical Support so that we may update this article.

last edited: 2014-04-16

2.29. "Automation error: The remote procedure call failed."

Applies to: All products, releases 7.x

When I launch the software, I get a popup with this message:

Automation error:
The remote procedure call failed.

Here are the known possible causes, with their cures:

Last edited: 2017-05-04

2.30. "Cannot checkout an uncounted license ..."

Applies to:
All Palisade software releases 5.x

Problem:
When I try to run my software in Terminal Services, Remote Desktop, or similar, I get this error message:

FLEXnet returned error code –103: Cannot checkout an uncounted license within a Windows Terminal Services guest session

Response:
You have a standalone (workstation) copy of the software. Standalone copies are designed to be operated while you are physically present at the computer. By design, it is not possible to remote in and run a standalone copy of the software.

If you wish to use Palisade software with Terminal Services, Remote Desktop, or other forms of remote access, please contact your Palisade sales representative to convert your standalone license to a concurrent network license.

last edited: 2008-10-30

2.31. "ClassFactory cannot supply requested class" (@RISK for Project)

Applies to:
@RISK for Project 4.x
(For this message when starting TopRank, see "ClassFactory cannot supply requested class" (TopRank).)

Problem:
When I try to run @RISK for Project I get this error message:

System Error &H80040111 (-2147221231).
ClassFactory cannot supply requested class

Solution:
Run a repair on Microsoft Project to resolve the issue.

For Microsoft Project 2007 and 2010:

  1. Click the Windows Start button, then Control Panel, then Programs and Features (in Windows 7 and Vista) or Add or Remove Programs (in Windows XP).
  2. Find Microsoft Project in the list of programs that appears.
  3. Highlight Microsoft Project 2007 and select Repair.
    (If Repair does not appear, select Change and in the following dialogs select Repair.)

For Microsoft Project 2003:

  1. Start MS Project (but not any Palisade software). If a blank project doesn't open automatically, open one.
  2. In the menu, click Help and then Detect and Repair.

last edited: 2012-11-22

2.32. "ClassFactory cannot supply requested class" (TopRank)

Applies to: TopRank 5.5
(For this message when starting @RISK for Project, see "ClassFactory cannot supply requested class" (@RISK for Project).)

When I try to run TopRank I get this error message:

Run-time error '-2147221231 (80040111)'
Automation error
ClassFactory cannot supply requested class

The installer program failed to register the TopRankModel.dll file, but you can do this yourself to solve the problem. Please follow these instructions:

  1. Make sure Excel is closed.

  2. Open an elevated command prompt (Start » Run may not work). To do this, click the Windows start button and type CMD The first search result is cmd.exe. Right-click it and select Run As Administrator. (Ask your IT people to perform this procedure if you don't have that option.)

  3. Copy and paste the appropriate command into the Run window:

    • For 32-bit Windows:
      regsvr32 "C:\Program Files\Palisade\TopRank5\TopRankModel.dll"
    • For 64-bit Windows (regardless of whether Excel is 32 or 64 bit):
      regsvr32 "C:\Program Files (x86)\Palisade\TopRank5\TopRankModel.dll"
  4. Click OK.

TopRank should now run normally when you open it.

Last edited: 2015-02-12

2.33. "Compile error in hidden module"

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

When I start one of your products, I get "compile error in hidden module".

This is most likely an issue with other software on your computer. Please try these suggestions:

  • If you have a beta version of Google Desktop, this is a known issue. To fix the problem, simply download and install a later version of Google Desktop.

  • Under certain circumstances, PDFMaker or Norton Antivirus can cause this problem. Please see You receive a 'Compile error in hidden module' error message when you start Word or Excel in the Microsoft Knowledge Base.

  • If you have an early version of Excel XP, this is a known issue. Please download and install the service pack for Excel XP from Microsoft's site.

If the above suggestions don't apply to you or don't resolve the problem, please follow the suggestions in Find and Fix Startup Conflicts (Excel 2007–2013) or Find and Fix Startup Conflicts (Excel 2003 and Earlier).

Last edited: 2015-10-05

2.34. "Compile error in hidden module: AddinInitialization"

Applies to: @RISK 5.x

When I try to launch RISK, I get the error message "Compile error in hidden module: AddinInitialization".

Most likely this is a conflict with another add-in or with one of your own startup files. Please see the appropriate article for your version of Excel:

If you have ruled out startup conflicts, it's possible that an Excel or @RISK file has become corrupted. Please repair Excel and @RISK, as follows:

Last edited: 2010-09-24

2.35. "Could not attach to the already running copy of Microsoft Excel"

Applies to: All Palisade add-ins for Excel

I try to launch @RISK (StatTools, PrecisionTree, ...) but I get this message:

Could not attach to the already running copy of Microsoft Excel because it is invisible or unresponsive.

@RISK was able to launch Excel (or Excel was already running), but Excel is not answering messages from @RISK. Here are the two causes and cures.

Most likely, there is an instance of Excel running in the background that needs to be stopped. To do this:

  1. Bring up Task Manager by selecting Ctrl+Shift+Esc.
  2. Select the Processes tab. (In Windows 8, it's the Details tab. If you don't see the tabs, click More details at lower left.)
  3. Click the column heading Image Name to sort the processes.
  4. Find Excel.exe in the list of processes. Highlight it and click End Process. When asked if you are sure you want to end the task, select Yes.
  5. Close Task Manager by clicking the X at the top right.

You should now be able to launch @RISK (StatTools, PrecisionTree, ...).

If this is an ongoing problem, you should investigate what is spawning these background processes of Excel. For example, some releases of certain third-party Excel add-ins create background processes of Excel and do not terminate them properly.

If there was no background process of Excel, then @RISK was able to start Excel but Excel wouldn't answer messages from @RISK. This can happen when another Excel add-in or startup file takes too long to start, so that @RISK eventually gives up waiting for a response from Excel. You can fix this in any of three ways:

  • Solution 1: Disable the other startups, them add them back one at a time to determine which one is the problem. See Find and Fix Startup Conflicts (Excel 2007–2013).

  • Solution 2: Make @RISK an active add-in. This will cause Excel to load @RISK when Excel is ready, instead of having @RISK load Excel and wait for a response from Excel. See Opening Palisade Software Automatically Whenever Excel Opens.

  • Solution 3: Start Excel yourself. When Excel is open and you see "Ready" in the status bar, then launch @RISK (StatTools, PrecisionTree, ...) from the desktop icon, taskbar icon, or Start menu. This has the disadvantage that you have to do it every time, but it doesn't require you to reconfigure Excel as Solutions 1 and 2 do.  (TIP: in most versions of Windows, you can right-click the Excel icon in the Start menu and select Pin to Taskbar, so that the @RISK icon is always visible.)

Last edited: 2015-08-15

2.36. "Could not contact the Microsoft Excel application"

Applies to:  All Palisade software 5.5.1 and later

When I try to launch @RISK, StatTools, or any of the tools, I get the above error message. What is wrong?

If you're getting this message the first time you try to run the Palisade software, your deployment of Microsoft Office may be a problem. See Click-to-Run and Office 365 with Palisade Software for more information.

Have you upgraded your Microsoft Office or uninstalled a version of Office? Office may have left one or more "orphan" keys behind. You can delete these keys by following the procedure in Removing Outdated References to Office from the System Registry.

Have you previously run the software successfully with this copy of Excel? If so, Windows may have got into a state where the messages from Palisade software to Excel are not being answered. Restart Windows to clear the problem condition.

Are there a lot of files in your temporary folder? This sometimes confuses Excel. See Cleaning Your Temp Folder.

Last edited: 2017-02-15

2.37. "Could not initialize the @RISK-Model application"

Applies to: The DecisionTools Suite 4.0 or 4.5 (CD included in textbook)

I purchased a textbook and installed the software. But when I try to launch it, I get this error message:

Could not initialize the @RISK-Model application

Your textbook software is release 4.5 or older, which is vintage 2005 and is not compatible with recent versions of Excel.  We have released quite a few versions since then, and you need the current release.

  1. Uninstall the 4.0 or 4.5 software in Control Panel » Programs and Features.  The DecisionTools Suite may be under T or D, or under P for Palisade, depending on the exact version.

  2. Visit our textbook software page and enter your book's 13-digit ISBN. If your book is supported, you will be guided to download and install the current software.

If your book is not supported, and you've carefully verified the ISBN, please send a note to our Academic Sales Manager and explain the situation.  Please include the following:

  • Your first and last name
  • Your school
  • The name and course number of your course
  • The title and edition number of the textbook
  • The ISBN of the textbook

Additional keywords: Textbook software, Textbook CD

Last edited: 2014-01-19

2.38. "Could not launch the Excel executable"

Applies to: Palisade add-ins for Excel, all releases

When I try to launch one of the Palisade tools I get the above error message.

If your maintenance contract is current, make sure that you have applied the latest updates for the Palisade products in which this error is occurring. The Web page http://www.palisade.com/Updates/ shows how to get updates, or your Palisade sales manager can assist you.

After applying the update, re-test the problem. If the problem persists, you can force the Palisade product to launch Excel by specifying the path to the Excel.exe in the Windows Registry as follows Please use the technique in Which Version of Excel Is Opened by Palisade Software? to set the Excel path in the System registry.

If you prefer not to edit the System Registry, you can work around the problem by simply opening Excel before @RISK (StatTools, PrecisionTree, ...).

Last edited: 2015-10-05

2.39. "Could not load ATHLIB32.DLL" (Commercial Software)

Applies to: All products, release 5.0 and newer

When I try to launch my software, I get the message

Could not load ATHLIB32.DLL.

If you have a recent textbook, please see "Could not load ATHLIB32.DLL" (Textbook Software). If you upgraded commercial software from 4.0 or 4.5 to a later version, keep reading the present article.

You previously had a 4.x release of our software installed, and you uninstalled it but the add-in is still enabled in Excel. Since the actual add-in file no longer exists on your computer, you get this error. The solution is to remove the add-in from the list, as follows:

  1. Open the Excel add-ins window:

    • Excel 2010: Click File » Options » Add-Ins, then at the bottom of the page select "Manage Excel Add-Ins" and click Go.
    • 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.
    • Excel 2003 or below: Click Tools » Add-Ins.
  2. Remove the check mark from DTools32.

  3. You may see a message similar to this one:

    Cannot find add-in '\DTOOLS\SYSTEM\dtools32.XLL'. Delete from list?

    or

    Cannot find add-in 'C:\Program Files\Palisade\SYSTEM\dtools32.XLL'. Delete from list?

    Click Yes to delete it from the list.

  4. Click OK, and close Excel.

Last edited: 2015-09-29

2.40. "Could not load ATHLIB32.DLL" (Textbook Software)

Applies to: DecisionTools and StatTools Suite: Student Edition, a CD bundled with some textbooks

I installed the software from the CD without a problem. But when I try to launch my software, I get the message

Could not load ATHLIB32.DLL.

or some other error message.

The DecisionTools and StatTools Suite: Student Edition is vintage 2004 software and is not compatible with today's versions of Excel and Windows. Please follow this procedure to unload the obsolete software and install current software for your course work:

  1. In Control Panel, uninstall the old software.

  2. Check for a C:\DTools folder, and if it exists delete it.

    If there is no C:\DTools folder, delete the folder C:\Program Files (x86)\Palisade or C:\Program Files\Palisade, whichever one exists.

  3. If you have Business Analytics: Data Analysis and Decision Making 5th edition, please follow this link to download the software. You will use your textbook to answer a question and unlock the download.

    If you have a different edition, or any other textbook, please email Palisade Technical Support and mention the error message. Give the full title and edition number of the textbook, and we will send you a download link. Email only, please; we're unable to do this by phone or in live chat.

Last edited: 2015-01-26

2.41. "Could not start the Microsoft Excel application"

Applies to: Palisade add-ins for Excel, releases 5.7.1 and 6.x/7.x

When I try to launch one of the Palisade tools, I get the above error message.

@RISK (PrecisionTree, StatTools, ...) can't find Excel.  This can happen after you upgrade Excel or the Palisade software, depending on the exact sequence of events.  To solve the problem, a simple System Registry edit should suffice. Please use the technique in Which Version of Excel Is Opened by Palisade Software? to set the Excel path in the System registry.  (If the path is already set, please verify that it is set correctly.)

If you prefer not to edit the System Registry, you can work around the problem by simply opening Excel before @RISK (StatTools, PrecisionTree, ...).

Last edited: 2015-10-05

2.42. "Error accessing file. Network connection may have been lost."

Applies to:
@RISK 6.x/7.x
@RISK for Project 4.1

When I try to open @RISK for Project, this message pops up:

Error accessing file. Network connection may have been lost.

This is actually a problem in Project, not in @RISK. If you Google the error message, you will find numerous references to this message in various Microsoft Office programs. In a Project context, it appears your Global.mpt is corrupt.

Solution Method 1:

If you don't have any customizations in Global.mpt that you care about, you can try deleting that file and forcing Project to re-create it:

  1. Close Excel and Project if they're open.
  2. Click Start » Run, type
    %APPDATA%\Microsoft\MS Project
    (including % signs), and click OK. When the folder opens, double-click the MS Project version number (Project 2010 = 14, 2007 = 12, 2003 = 11), and double-click 1033.
  3. Rename Global.mpt as Backup_Glob.mpt. (If you see only the name and not the .mpt extension, rename it as Backup_Glob only.)
  4. Open MS Project and save the default Project1 MPP file to any location. This forces MS Project to create a fresh Global.mpt file.
  5. Close MS Project, and you can delete Project1.mpp.

Solution Method 2:

If the above shorter solution doesn't work for you, or if you have customizations that you don't want to lose, please try this solution that we found in an article at Tech Republic. Essentially you will delete and recreate the Global.mpt, but this procedure will lead you to back it up first.

  1. Open and save a new .mpp, say Backup.mpp.
  2. Open the Organizer. (In Project 2010, click File » Info » Organizer. In earlier Project versions, click Tools » Organizer.)
  3. Copy everything except Modules from the Global.mpt to Backup.mpp. Remember to look for the Task and Resource radio buttons and to switch between them on the tabs that have them. If you get a message that "No Group" cannot be copied, click OK. For any warnings about overwriting, click Yes to All.
  4. Close Organizer and save Backup.mpp.
  5. Open the Organizer again and one by one copy all the modules to Backup.mpp. If any that will not copy are not native to MS Project's Global.mpt file, you may need to open Project Visual Basic and copy the content of those modules to a text file or otherwise back them up. You can ignore a problem in copying any modules that are native to MS Project.
  6. Close Organizer, save Backup.mpp, and close MS Project.
  7. Click Start » Run, type
    %APPDATA%\Microsoft\MS Project
    (including % signs), and click OK. When the folder opens, double-click the MS Project version number (Project 2010 = 14, 2007 = 12, 2003 = 11), and double-click 1033.
  8. Rename Global.mpt as Backup_Glob.mpt. (If you see only the name and not the .mpt extension, rename it as Backup_Glob only.)
  9. Reopen MS Project and save the default Project1 MPP file to any location. This forces MS Project to create a fresh Global.mpt file.
  10. Close Project1.
  11. Re-open Backup.mpp created earlier, and copy everything in the Organizer back to the Global.mpt.
  12. Close Microsoft Project, and you can delete Project1.mpp.

Last edited: 2015-10-05

2.43. "Error code 50030 populating a FLEXnet License Specification"

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

When I try to launch the software, I get the error message

Authorization failure
Details:
Error code 50030 populating a FLEXnet License Specification from Trusted Storage

Something is stopping the license service from running.  If you have a Windows policy setting that allows only specified executables, verify that PalFlexServer5.exe, PalFlexServer6.exe, or PalFlexServer7.xe (depending on your software version) has permission to run, and the same for FNPLicensingService.exe.

Click Start » Run, type Services.msc and click OK. FLEXnet Licensing Service should be set to Manual. (FNPLicensingService.exe is the executable for FLEXnet Licensing Service.)

Last edited: 2015-10-05

2.44. "Error in loading DLL" (at Startup)

Applies to: All products, releases 6.x/7.x, with 64-bit Excel 2010, any Excel 2013, or any Excel 2016

When I try to launch the software from a desktop icon or start menu shortcut, I get this message:

Error in loading DLL

(Depending on which product you launch, there may be additional text, but "Error in loading DLL" is the key phrase.)

If the message is "Unable to load DLL", and it mentions a PalFlex file name, please see "Unable to load ... PalFlex_x86.dll".

If you get the message when you open the add-in by File » Open or by Browse, but not when you click the desktop icon or start menu, see @RISK Initializes, But No Tab Appears in Ribbon.

You may unintentionally be loading multiple copies of @RISK. Click File » Options » Add-Ins, then at the bottom of the right-hand panel click Go. In the next dialog, if RISKOptimizer or rpjexcel is checked (ticked), remove the check marks.

If those two don't appear, or they appear but are not ticked, then your Visual Basic 6 Runtime and/or .NET may not be registered properly. Please follow the procedure to re-register Visual Basic 6 Runtime. If the software runs now, you have solved the problem.

If the problem still occurs, your System Registry may contain one or more references to a version of Excel that no longer exists on your computer. To remove these "orphan" keys, please follow the procedure in Removing Outdated References to Office from the System Registry.

See also: Microsoft .NET Framework Repair Tool.

Last edited: 2017-03-13

2.45. "Failed to load ... Palflex5.dll"

Applies to: All Palisade software releases 5.x

When I try to run my Palisade software, I get the message

Failed to load c:\Program Files\Palisade\System\Palflex5.dll

or

Failed to load c:\Program Files (x86)\Palisade\System\Palflex5.dll

The solution requires full administrative rights.

  1. In Computer or My Computer, navigate to the Palisade installation folder, then open the System folder under the Palisade folder. (The full path is shown in the error message.)

  2. Delete these files:

    Palflex5.dll
    Palflex5_libFNP.dll
    Fnpcommssoap.dll
    Fnp_act_installer.dll

  3. Follow the repair procedure in Repair of Palisade Software.

If the above does not work, check your Local Settings folder and make sure that it has not been set to read only.

Last edited: 2012-11-09

2.46. "FAILURE: License is broken."

Applies to:
All products, releases 5.x–7.x, standalone licenses
All products, releases 5.x–7.x, network server licenses

Everything was working fine, but I upgraded to Windows 8.1 or Windows 10, and now I can't run. Help » License Manager tells me "Failure: License is broken."

Windows 10 updates, or upgrading a computer to Windows 8.1 or Windows 10, may break an activated Palisade license, depending on the exact configuration of your computer. The upgrade should have no effect on certificate licenses, including textbook and course licenses. It should also have no effect on network client licenses, though a network server license may be broken.

First, make sure that your existing software is compatible with your new version of Windows. Please see Windows and Office Versions Supported by Palisade. If they are not compatible, you will need to upgrade your Palisade software. Please contact your Palisade sales manager to enter the order for the upgrade; if you have current maintenance there will be no charge. Contact information for all our sales offices is here.

When you have compatible Palisade software, the fix for a broken license is usually straightforward. Please don't try to reactivate your license. Instead, you have two options.

Last edited: 2016-10-25

2.47. Broken License? Do-It-Yourself Repair (7.5.0 or older)

Applies to:
All products, releases 6.0 0–7.5.0, standalone licenses

If you have release 7.5.1 or newer, see Broken License? Do-It-Yourself Repair (7.5.1 or newer).

In the article "FAILURE: License is broken.", you suggest emailing Technical Support for customized instructions. Isn't this something I can fix myself?

Yes, you should be able to, if you follow these directions.

  1. Open the attached KB1395_RepairLicense file in Notepad, Microsoft Word, Outlook, or your favorite text editor.

  2. In License Manager, highlight your Activation ID with your mouse, and press Ctrl+C to copy it.

  3. Click the magnifying glass at the lower left of the License Manager window. An Advanced Options dialog will open. Click View.

  4. A Notepad window will open. Press Ctrl+F to bring up the Find dialog, then Ctrl+V to paste your Activation ID. Click Find Next to find a line consisting of your Activation ID preceded by "Entitlement ID".

  5. Just above that line, you'll see a line consisting of "Fulfillment ID" and your Fulfillment ID, which has the format FID_1f42b49_14edacffcb3__7aea. Highlight just the ID itself, not the words "Fulfillment ID", and press Ctrl+C to copy it.

  6. In the KB1395_RepairLicense file, in step (3), highlight xxx and press Ctrl+V to replace it with the Fulfillment ID. Repeat in step (5).

Now follow your customized instructions.

Last edited: 2016-10-25

2.48. Broken License? Do-It-Yourself Repair (7.5.1 or newer)

Applies to:
All products, release 7.5.1 or newer, standalone licenses

If you have release 7.5.0 or older, see Broken License? Do-It-Yourself Repair (7.5.0 or older).

In the article "FAILURE: License is broken.", you suggest emailing Technical Support for customized instructions. Isn't this something I can fix myself?

Yes, you should be able to. First, try the Repair button in License Manager. It will attempt to communicate with our server to perform an Automatic Repair. If you get a success message, ignore the rest of this article.

If the Automatic Repair button fails, please see the attached instructions to perform a manual repair.

Last edited: 2017-05-08

2.49. "FAILURE: Unable to reach a network server."

Applies to: All 6.x/7.x network client software

I installed the 6.x or 7.x network client successfully, but when I try to run it, I get this error message:

FAILURE: Unable to reach a network server.

followed by

Authorization failure.
Details:
There is no available license for @RISK.

(or whatever product I'm trying to launch).

There are several possible causes. The first thing is to determine whether the problem is on the client or the server, or on your network between them.

Are other clients able to run?

If no clients can run, especially if they used to be able to run, the problem is likely to be on the server rather than the clients. Please follow the troubleshooting tips in this first section.

  • Look at Server Manager's display to verify that a network license has been activated and is still current.

  • Check the server firewall settings to ensure that the server lets Palisade.exe and lmgrd.exe both send and receive. See also Network Ports and Firewalls (7.x) or Network Ports and Firewalls (6.x).

  • Make sure that the license process is running on the server. If Server Manager says "Running", click the Status button and look for "Palisade UP" in the status display. If the status display does not contain "Palisade UP", the license process is not running. In that case, click the magnifying glass in lower left, and then the View button, and look at the last few lines of the display to see the failure reason. Most likely it s a port-number conflict.

  • If you have other FLEXnet software licenses from other vendors running on the same server, verify that they are not using the same lmgrd ports as Palisade. The best way to do this is to leave them all unspecified. But if you specify any of the lmgrd ports, you must specify all of the lmgrd ports, and they must be unique.

    With vendor daemon ports, we don't recommend that you specify any, but if you do then you don't need to specify all of them. For any vendor daemon ports that you do specify, stay away from ports that you specified for lmgrd or for any other software from Palisade or any other vendor, and stay away from the range 27000–27009 if lmgrd ports are unspecified.

  • If you have manually edited your Server.lic file, you may have made a mistake. (We strongly recommend that you never edit this file directly. Instead, use Server Manager to set ports.) The SERVER line can have two or three fields: computer name of the server, Ethernet address, and lmgrd port number.

    • this_host is a valid wild-card for the first field, though Server Manager will change it to the actual computer name.
    • ANY is used in place of the second field when you have only activatable licenses. When you have certificate licenses, the actual Ethernet address appears in the second field and must not be changed, because that would break the digital signature of the file.
    • The third field will not appear if the lmgrd port number is set to Dynamic in Server Manager.

If other clients can run, either this client's settings or network connections are more likely to be the problem. The remainder of this article will help you troubleshoot them.

Are server and client set up to use the same name and LMGRD port?

  1. On the server, launch Server Manager. The first line of the display gives the server name. The communication port is given a line or two below that.

  2. On the client, in License Manager, click Select License » Concurrent Network and it will show you the server name it is trying to reach and the port number it is trying to use.

The server name on the client should match the host name in Server Manager. (There are some unusual exceptions, where network administrators use fully qualified domain names or IP addresses on clients. These must be carefully tested.)

If the server specifies a port number, the client must be using that port. If the server port is dynamic, the client port must also be dynamic. If anything doesn't match, click Edit on the client screen and make the necessary changes. For more information, please see Redirecting 7.x Concurrent Clients to a New Server or Port Number or Redirecting 6.x Concurrent Clients to a New Server or Port Number.

Can the client communicate with the server on the LMGRD port?

Verify that the client can communicate with the server using the server name and port number specified in the System Registry key
HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE or
HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE.
If no port number is specified, all ports in the range 27000 through 27009 must be open.

You can test whether a given port is open by using Telnet. (This requires a Telnet client on the client computer and a Telnet server on the server. These are part of Windows, but they might not be turned on. If they're not enabled, you can enable them in Windows Control Panel » Programs and Features » Turn Windows features on or off.) The command format is

telnet myservname 27000

You should get a blank screen if the port is open. If it's not, you should get an error message within about 60 seconds.

Can the client communicate with the server on the vendor daemon port?

The licensing software uses a second port, called the vendor daemon port. Problems with this port, in the absence of problems with the LMGRD port, are extremely rare but when other issues have been eliminated you should check for them.

  1. On the server, launch Server Manager. Click the magnifying-glass icon at lower left, then the View button. A Notepad window will open. Scroll down near the bottom to find the "Palisade using tcp-port". (Ctrl+F is the search command in Notepad.)

  2. On the client, repeat the above Telnet test but specify the "Palisade using tcp-port" number. If you're checking firewall logs, be aware that the client typically uses a different port to communicate with this server's vendor daemon port. Unlike the LMGRD port, the vendor daemon port is not specified anywhere in the System Registry or elsewhere on the client.

If you have an issue with this port, you will need to adjust your firewall settings; see server firewall information in Network Ports and Firewalls (7.x) or Network Ports and Firewalls (6.x).

Are client and server on different subnets?

If so, you might need to use a fully qualified domain name, portnumber@servername.company.com rather than just portnumber@servername. You can set this in the System Registry key
HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager\PALISADE_LICENSE_FILE or
HKEY_LOCAL_MACHINE\Software\WOW6432Node\FLEXlm License Manager\PALISADE_LICENSE_FILE.
(If you anticipate this problem, and you haven't yet installed the client software, edit the server name in the Palisade_NetworkClient.ini file before installing the client software.)

Additional keywords: Subdomain

Is the client firewall locking out Palisade software?

The client computer's firewall should allow PalFlexServer6.exe or PalFlexServer7.exe to send and receive. See client firewall information in Network Ports and Firewalls (7.x) or Network Ports and Firewalls (6.x).

Does FLEXnet need a longer timeout?

Most clients are fine with the default FLEXnet timeout of 0.1 second, but some have a problem because they need to make too many Internet "hops" to reach your server. If you've eliminated client configuration issues, you may have a timeout problem. Please see FLEXlm License Manager Times Out for more on this possibility.

Last edited: 2017-02-03

2.50. "File not found: DTOOLS5.XLL"

Applies to:
TopRank 5.x

Problem:
When I try to start TopRank, I get the message

Run-time error '53':
File not found: DTOOLS5.XLL

Solution:
Although it's a different message, it's the same issue as "Unable to load C:\Program Files\Palisade\System\Dtools5.xll".

Please follow the procedure in "Unable to load ... Dtools5.xll".

last edited: 2012-01-05

2.51. "FLEXnet returned error code –1"

Applies to:
All Palisade software versions 5.x

Explanation of the error:
Code -1 means that a license could not be read for this product. Some of the possible causes:

  • A standalone product is installed but you have a network license, or vice versa.
  • The wrong product or wrong edition is installed. @RISK as a separate item and @RISK as part of the DecisionTools Suite are two different products, and a license for one doesn't cover the other. Editions could be Industrial, Professional, or Standard.
  • You might not have a license for this release number. For example, if you have a valid license for a given release, and you install a later version but your maintenance was not in effect on the release date, the later version will install a 30-day trial. You'll get a FLEXnet error after the 30 days run out.
  • You might be running Windows emulation on a non-Windows computer such as a Mac.
  • You might be running virtual machine software that does not quite emulate Windows low-level disk reads and writes.
  • You might have a RAID (redundant disk array).
  • You might have had insufficient permission at install time, so the trial license could not be written to Trusted Storage. (Trusted Storage is a non-file area of the hard drive.)
  • You might have had insufficient permission when activating, so the permanent license could not be written to Trusted Storage.
  • Your security software or policy settings might prevent writing to Trusted Storage, or allow the write but then undo it.
  • You might have ghosted or imaged the workstation, and the ghosting or imaging did not properly copy the non-file area of the disk. (If this is a course license, we have a newer form of the software that does support imaging the workstations.)

last edited: 2010-09-23

2.52. "FLEXnet returned error code –5"

Applies to:
All products, release 5.x

Problem:
I activated successfully, but when I try to run the software again I get the error message

FLEXnet returned error code -5: No such feature exists

Solution:
Your activation ID is for one product, but you have installed a different product. The most common case is installing @RISK instead of the DecisionTools Suite or vice versa, but it could be any wrong product or wrong edition (Industrial, Professional, Standard).

Look at the second line of the message, and the Feature name will tell you what you have actually installed. Compare this with your license and you will see the difference. To solve this problem, follow these steps:

  1. In Windows Control Panel, Add or Remove Programs (or Programs and Features), uninstall the incorrect product.
  2. Download and install the correct product. You will not need to activate it again.

Or, if you can't figure this out, please send an email to Technical Support with your Activation ID and a screen shot of the error message, and we will help you.

last edited: 2012-11-09

2.53. "FLEXnet returned error code –7"

Applies to:
All products, release 5.x

Problem:
The license process is running on the server, Palisade Server Manager shows that there are licenses available.  But when I try to run the Concurrent Network software on a client, I get the error message

FLEXnet returned error code –7: No socket connection to license server manager.

Response:
Although the text of this message is different, the causes and cures are the same as for "FAILURE: Unable to reach a network server."

last edited: 2014-02-24

2.54. "FLEXnet returned error code –12"

Applies to: Palisade Concurrent Network software, releases 6.x/7.x

When I try to launch my software, I get this message:

Authorization failure.
Details:
FLEXnet returned error code –12: Invalid returned data from license server system.

This is probably a port-number conflict, which must be resolved by your server administrator.

On the server, the simplest setup is to set both the LMGRD port number and the vendor daemon port number as dynamic (unspecified). It's also okay to specify one but leave the other as dynamic, or to specify both. If you do specify both, they must be different.

Important: If you have FLEXnet products from multiple vendors, either the LMGRD port for all of them (including Palisade) must be dynamic or unspecified, or you must specify LMGRD ports for all of them and you must specify a different LMGRD port for each application (including Palisade). Vendor daemon ports can be mixed between specified and unspecified, but you can't specify the same vendor daemon port for two FLEXnet applications.

If you do leave the lmgrd ports as unspecified, make sure that no non-FLEXnet software is using any of ports 27000–27009.

Last edited: 2017-03-17

2.55. "FLEXnet returned error code –20"

Applies to:
Palisade software releases 5.x

Problem:
When I try to open the software, I get the error message

FLEXnet returned error code –20: lc_flexinit failed

Solution:
Most likely you did not have sufficient privilege when running the installer. To resolve the problem, do not uninstall the software but repeat the install as follows:

  1. Make sure you are logged in to Windows as a full administrator.
  2. If you have Windows 7 or Vista, right-click the installer and select Run As Administrator. If you have Windows XP or earlier, double-click the installer.
  3. If the installer prompts you for Modify or Repair, select Repair.

last edited: 2012-11-09

2.56. "FLEXnet returned error code –97" (standalone)

Applies to: All products, 6.1 Preview

When I launch @RISK or another one of the Palisade applications, I get this error message:

Authorization failure
Details:
FLEXnet returned error code –97: The desired vendor daemon is down.
Check the lmgrd log file, or try lmreread.

I have a standalone copy of the software, not a network client.

Were you running the 6.1 Preview? It had a special form of license, which expired in March 2013. After that date, you might get this error message when you try to run the software.

To solve this, please go to our Free Trial Versions page and select your product. Download and install it. During install, on the Customer Information screen, select "I am upgrading or reinstalling" and leave the Activation ID box blank. If you have current maintenance, the new install will pick up your activation. Otherwise, it will install as a trial, and if you decide to purchase you will be able to activate it without reinstalling the software.

Last edited: 2015-10-05

2.57. "FLEXnet returned error code –97" (network client)

Disponible en español: "FLEXnet generó un código de error -97" cliente de red simultanea

Applies to: All Concurrent Network products, releases 5.x and later

When I launch @RISK or another one of the Palisade applications, I get this error message:

Authorization failure
Details:
FLEXnet returned error code –97: The desired vendor daemon is down.

What is wrong?

This message means that the client could communicate with an LMGRD program on the server, but could not communicate with the Palisade.exe program (the "vendor daemon") on the server. This could be caused by configuration problems on your server or your clients. Your first question is, does this happen on all clients, or are some clients able to run? A server problem will affect all clients. A client problem could affect all clients or only some clients, depending on whether some clients are configured correctly and some incorrectly.

  • (Affects all clients) Port-number conflict among multiple FLEXnet-licensed products. See "Finding and fixing port-number conflicts" in FLEXnet Error: "Exiting due to signal 27".

  • (Affects all clients) Misplaced license file. In Palisade Server Manager, click Open LIC Folder. You should have PalisadeNetwork.lic and Server.lic only. If you have other .lic files there, remove them. (Sysadmins sometimes put a Palisade_Course.lic file in this folder on the server. That's a standalone license and will cause your network license to malfunction.) Click Refresh in Server Manager after removing any wrong file.

  • (Affects all clients) License process not running on the server. Network Server Issues lists the most common problems and their solutions.

    • In 6.x and newer, launch Palisade Server Manager. If the service is not running, start it, click Refresh, and verify that it is still running. If it stops itself, click Open .LIC folder and examine the contents of the PalisadeService.log file.
    • In 5.x, launch LMTools. On the Server Status tab click Perform Status Enquiry. If the service is not running, on the Start/Stop/Reread tab click Start Service; perform a new Status Enquiry to verify that the service is not running. If it is not, go to the Config Services tab and click View Log. Trouble messages will be near the end of the log.
  • (Could affect all clients, or only some clients) Firewall forbidding communications between this client and the server. On the client, either open the appropriate ports or make PalFlexServer7.exe, PalFlexServer6.exe, or PalFlexServer5.exe an exception in the firewall.

  • (Could affect all clients, or only some clients) Any of the causes listed, with solutions, in "FAILURE: Unable to reach a network server."

Last edited: 2016-06-09

2.58. "FLEXnet returned error code –103"

Applies to:
All Palisade software release 5.5

Problem:
When I try to start my Palisade software, I get the error message

FLEXnet returned error code –103

Response:
You have a standalone (workstation) copy of the software. Standalone copies are designed to be operated while you are physically present at the computer. By design, it is not possible to remote in and run a standalone copy of the software.

Please see Cannot checkout an uncounted license ... for a more detailed explanation.

last edited: 2009-07-20

2.59. "FLEXnet returned error code –157"

Applies to: Palisade software, releases 6.x/7.x

When I try to launch my software, I get this message:

Authorization failure.
Details:
FLEXnet returned error code –157: Trusted Storage compromised, repair needed
Trusted Storage is invalid, and needs to be repaired

The license for your Palisade software has been broken by an upgrade to Windows 10 or Windows 8.1, by a backup/restore operation that was less than perfect, by changing your computer's system date, or through other causes. Please contact Palisade Technical Support for help in recovering this license.

Last edited: 2015-10-07

2.60. "Method '~' of object '~' failed" (at Startup)

Applies to: Palisade software 5.x–7.x

When I launch @RISK (or another Palisade add-in) I get "Method ~ of object ~ failed". What is wrong, and how do I fix it?

There are several possible causes. Here are the ones we know of:

  • Check in Excel's Disabled Items, and if the Palisade add-in is listed there, re-enable it. (An item can be marked disabled under some circumstances when Excel crashes.)

    To access disabled items: In Excel 2010 and 2013, select File » Options » Add-Ins » Manage: Disabled Items. In Excel 2003, it's Help » About Microsoft Excel » Disabled Items.

  • Verify that "ignore other applications" is not selected (the box is unchecked).

    In Excel 2010 and 2013, select File » Options » Advanced » General options. In Excel 2003, it's Tools » Options » General.

  • Verify that Visual Basic for Applications is installed and enabled. The easy test for this is to launch Excel and then press Alt-F11. Visual Basic Editor should appear.

    If VBA is not enabled, go to Control Panel » Programs and Features (or Add or Remove Programs) and modify Microsoft Office. VBA is under "Office shared features", and it must be set to "Run from my computer".

  • Run a repair of Microsoft Office to fix any components that may be corrupted.

  • Verify that your version of Palisade software is compatible with your version of Office. Please see Windows and Office Versions Supported by Palisade.

  • If you have Office 2013 or 2010, deployment as Web Apps, On Demand, or some varieties of Office 365 and Click-to-Run may be a problem. See Click-to-Run and Office 365 with Palisade Software for more information.

See also: There are other possible causes for this message. See All Articles about "Method '~' of object '~' failed".

Last edited: 2015-10-07

2.61. "Method 'ExecuteCommand' of object '_PalUtil' failed"

Applies to:
NeuralTools 5.x
StatTools 5.x

When I try to open NeuralTools or StatTools, I get the error message

Method 'ExecuteCommand' of object '_PalUtil' failed

The other applications in the DecisionTools Suite seem to run just fine.

The Palisade software uses Microsoft Visual Basic 6 Runtime, and installing Skype Email Toolbar Beta in 64-bit Windows corrupts this component. More specifically, Skype's toolbar install overwrites some information that the VB6 install places in the System Registry. (The issue occurs with the Email Toolbar install; the Skype application's install is not a problem.)

If you have 64-bit Windows, you can repair this information through either of the methods below. Caution: before any procedure that modifies the System Registry, you should make sure that your system has been backed up.

Method 1: Download the attached batch file to your desktop. Right-click it and select Run As Administrator.

Method 2: Open a command prompt as administrator, and execute this command:

regsvr32 %windir%\SysWOW64\msvbvm60.dll

Either way, if the process succeeds you will see the message: "DllRegisterServer in c:\Windows\SysWOW64\msvbvm60.dll succeeded."

It is best to uninstall your Skype toolbar, because this change may make it unstable or prevent your email from working altogether. You do not need to uninstall the main Skype program.

Last edited: 2012-01-17

2.62. "Method 'ExecuteRiskCommand' of object '_RiskOL' faiied"

Applies to: @RISK 7.x, in 64-bit Excel 2016

When I launch @RISK, I get the message

Method 'ExecuteRiskCommand' of object '_RiskOL' failed

I tried repairing Office and repairing the Palisade software, but the problem remains.

This problem has affected just a few people out of the thousands using 64-bit Excel 2016. Unfortunately, we have not been able to reproduce this here, and we have not been able to find the cause on customer computers.

Your fastest workaround is to uninstall 64-bit Excel and install 32-bit Excel; all four affected users chose to do this, and it solved the problem.

Odds are pretty good that 32-bit Excel will serve your needs fully; see Should I Install 64-bit Excel? However, if you've got the level of memory use mentioned in that article, 32-bit Excel won't be sufficient for you. If that's the case, or if you can't switch to 32-bit Excel for any other reason, please contact Technical Support. Palisade will work with you to try to find a solution.

Last edited: 2016-10-06

2.63. "Method 'InitializeEx2' of object '_RiskOL' failed"

Applies to:
Palisade software release 5.7

Problem:
@RISK (StatTools, PrecisionTree, etc.) won't start up. It just gives me the message:

Method 'InitializeEx2' of object '_RiskOL' failed

or

Method 'InitializeEx' of object '_OptLibrary' failed

Response:
This message usually means you are trying to run the software via some sort of remote login such as Remote Desktop or terminal services. This is not permitted by the license terms for a standalone license. We apologize for the misdirection given by the error message.

You need to be physically present at the computer and directly logged in.

If running via remote login is a requirement for you, please contact your Palisade sales manager about a network license.

Special note for XP Mode in Windows 7: Microsoft has implemented Windows 7's XP Mode as a form of remote desktop, and therefore you cannot run standalone versions of our software in XP Mode in Windows 7. However, there's no need to do that anyway, because all of our recent releases run just fine in 32-bit or 64-bit Windows 7.

last edited: 2012-05-16

2.64. "Microsoft Excel has identified a potential security concern."

When I try to launch Palisade software, I get a popup saying

Microsoft Excel has identified a potential security concern.

Note: The digital signature is valid, but the signature is from a publisher whom you have not yet chosen to trust.

This popup appears because you have the AutomationSecurity policy set to 2 rather than the normal value of 1, which is recommended by Microsoft.

Without changing that policy, you can simply click Trust all from publisher in the dialog.

You know this is safe, because our code was signed with a certificate valid at the time of signing. And you know the code has not been changed since then, or you would get a message telling you that.

See also:

Last edited: 2015-06-01

2.65. "Not enough system resources to display completely."

Applies to: @RISK 6.x/7.x

When I try to open my model, I get the error message

Not enough system resources to display completely.

Or, I can open the model, but after I run a simulation I get that message.

Your model is too large or too complex, or has features that require more system resources than your computer can provide.  Some suggestions:

  • If you are running any memory-hungry or disk-hungry applications, close them before opening your model.
  • If you have other workbooks open and they're not required for the simulation, close them before opening this one.
  • If you can make your model less complex or trim down redundant calculations, this is always a good idea.
  • If the number of iterations is large, try reducing it.  Or use @RISK's convergence monitor to see whether you are specifying more iterations than needed.
  • If you're using Color Cells, try disabling them before opening your model.  (Color Cells can take a lot of system resources, depending on your model.)
  • If you are collecting all distribution samples (Simulation Settings » Sampling tab), switch to None or Distributions Marked with Collect.

See also: "Not enough memory to run simulation"

Last edited: 2015-10-07

2.66. "Object disposed."

Applies to: @RISK 6.x/7.x (possibly other products also)

When I launch @RISK. I get the message

Object disposed.

How do I fix that?

We see this very infrequently, but for the cases we've seen recently, the fix is simple: Just restart Windows. This should be a full restart of Windows, not just logging off and on again.

If you have RISKOptimizer in Excel's list of active ad-ins (File » Options » Add-ins), click the Go button at the bottom of the list and remove the check mark for RISKOptimizer. RISKOptimizer loads automatically when you load @RISK, but it must not be loaded directly as an Excel add-in.

We've also seen this "Object disposed" message associated with permissions problems. If you installed @RISK by just double-clicking the installer, you might want to retry, right-clicking the installer and selecting Run as Administrator. During the install, you'll probably see a selection Modify/Repair/Remove; select Repair.

If these suggestions don't help, please contact Palisade Technical Support with your serial number and we will try to assist you.

Last edited: 2016-04-28

2.67. "Object doesn't support this property or method"

Applies to: All Palisade software, releases 6.x

When I try to launch my Palisade software, I get this error message:

Object doesn't support this property or method

The toolbars appear as expected. Can I ignore this message?

Palisade software releases 6.x require Excel 2003 or newer, and you are using an older version of Excel.  The software will not function correctly in this version of Excel, and you need to upgrade your Excel to a later version.

When you do upgrade Excel and click the @RISK icon (or PrecisionTree, StatTools, ...), the software might still try to launch the older Excel. If this happens, please see "Which Version of Excel Is Opened by Palisade Software?" for a simple update to the System Registry that will tell the software which version of Excel to open.

Last edited: 2012-12-11

2.68. "Object variable or With block variable not set" (Windows 7 and Vista)

Applies to:
Palisade add-ins 5.x–7.x for Excel, running in Windows 7 or Vista.

This may apply to Windows 8 and Windows 10 also, but we don't have any confirmed cases.

When I launch @RISK, I get

Object variable or With block variable not set
Run-time error '-2147024894(80070002)'

If I try opening Excel and then Risk.xla within Excel, I get the same thing.

@RISK 5.x and 6.x require Microsoft .NET 2.0 to run, and @RISK 7.x requires .NET 4.x. From the error number, it looks like your copy of .NET is corrupt. If you have .NET 2.0 SP2 or later, or .NET 4.x, you can download and run the Microsoft .NET Framework Repair Tool

If you have an earlier build of .NET 2.0, please follow the command-line procedure in How to repair the .NET Framework 2.0 and 3.0 on Windows Vista. (Although the article title says "Vista", the text indicates that the procedure also works for Windows 7.) If that is not sufficient, please follow the additional procedure in that article to repair the registry entries.

See also: There are other possible causes for this message. See All Articles about "Object variable or With block variable not set".

Last edited: 2016-11-23

2.69. "Object variable or With block variable not set" (Windows 8)

Applies to: Palisade add-ins for Excel, releases 5.7 through 6.1, running in Windows 8 or 8.1

When I launch @RISK, I get

Object variable or With block variable not set

followed by

Run-time error '-2146232576 (80131700)':
Automation error

If I try opening Excel and then Risk.xla within Excel, I get the same thing.

@RISK 5.x and 6.x require Microsoft .NET 2.0 to run, but Windows 8 does not include that version. In Windows 8 and 8.1, to get .NET 2.0 it's necessary to install .NET 3.5.

If you have Windows 8.1, the @RISK 6.2.0–6.3.1 installers will install .NET for you; for earlier @RISK installers see Installing Palisade Software 6.0 or 6.1 in Windows 8.1.

If you have Windows 8 (not 8.1), the @RISK 6.1.1–6.3.1 installers will install .NET for you; for earlier @RISK installers see Installing Palisade Software 5.7 or 6.0 in Windows 8.

See also: There are other possible causes for this message. See All Articles about "Object variable or With block variable not set".

Last edited: 2016-02-23

2.70. "PalFlexServer6 Application has encountered a problem and needs to close."

Applies to:
DecisionTools Suite 6.0, textbook version only
(August 2012 downloads only)

Problem:
I installed my textbook version without any error messages. But when I launch any of the tools, immediately after startup it gets the above error message, or the following message:

Authorization failure
Details:
Unexpected status=0, err=109, for kernel function TransactNamedPipe, after calling transactNamedPipe.

Response:
There was a problem with an early release of the textbook install for 6.0, which was corrected at the end of August 2012.

If you downloaded early and are experiencing this problem, we apologize for the inconvenience. Please do not uninstall the software. Just repeat the download and install procedure from the beginning. You will get a new version of the software, which does not have this problem.

last edited: 2013-04-25

2.71. "PalGraph7Server has stopped working"

Applies to: @RISK 7.x

@RISK installed without any error messages, but when I launch it I get the message

PalGraph7Server has stopped working

When I click "Close the program", I get

Automation error
The remote procedure call failed

It looks like your installation of .NET 4 is missing or corrupted. To install or repair it, please see item 1 in Microsoft Components Required for Palisade 7.x Software Install.

Last edited: 2017-06-22

2.72. "PalMemLoadDll exception"

Applies to:
Palisade software version 5.x

Problem:
When I launch the software, I get a small message box with "PalMemLoadDll exception" in the title bar and a four-digit number in the middle of the box, but no other text. What is wrong?

Response:
The software is unable to write to your temporary folder. (The four-digit number is just a process number and has no significance for this problem.) Please make sure that your Local Settings and temporary folders are set for full access, not just read access.

(1) Local Settings is usually at C:\Documents and Settings\(your login name)\Local Settings, though in Windows it's possible to redirect it to a different location. If you can't find it, click Start » Run and enter this command:

%TMP%\..

including the percent signs, backslash, and two dots as shown.

(2) The temporary folder is usually a subfolder TEMP within Local Settings. If you can't find it, click Start » Run and enter this command:

%TMP%

including the punctuation as shown.

last edited: 2010-08-16

2.73. "Problem Event name BEX"

Applies to: Palisade products, releases 5.x–7.x

When I try to launch PrecisionTree and some other components of the DecisionTools Suite (not @RISK), I get this error:

PrecisionTree Launcher stopped
Problem Event name BEX
Problem Module Name RpcRtRemopte.dll

(Other modules are also identified as problems, such as CFGMGR32.dll.)

This problem relates to Data Execution Prevention (DEP) in Windows. You can disable DEP for the specific applications that have a problem, as explained near the end of Microsoft's TechNet article Data Execution Prevention. (Look near the end of the article, under "Per-application DEP configuration".)

Last edited: 2015-10-07

2.74. "RISKOptimizer initialization failed"

Applies to:
RISKOptimizer 5.0 only

Problem:
When I try to launch RISKOptimizer, I get this message:

RISKOptimizer initialization failed.
A exception has occurred.

Details:
Error 0000007A opening the Registry key at HKEY_LOCAL_MACHINE.

Solution:

  1. Close Excel.

  2. Start » Run » REGEDIT and click OK.

  3. Navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\Palisade\RISKOptimizer\5.0, or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Palisade\RISKOptimizer\5.0 in 64-bit Windows. Right-click on 5.0 and select Delete.

  4. File » Exit to close the Registry Editor.

  5. Perform a repair of @RISK or the DecisionTools Suite by following the procedure in Repair of Palisade Software.

RISKOptimizer should now run correctly.

last edited: 2012-11-22

2.75. "The current system code page is incompatible with this program."

Applies to: All Palisade software, releases 6.0–7.0 only

When launching the software, I get the message

The current system code page is incompatible with this program. Please see the readme file for more information.

The program then opens, but the text is unreadable.

Your best solution, if you have a current maintenance contract, is to upgrade to the latest version. Starting with 7.5.0, @RISK has improved Unicode support so that code pages are no longer a concern. However, if you don't have a maintenance contract and don't want to purchase an upgrade, you can use the following solution.

Non-English editions of the Palisade DecisionTools releases through 7.0.1 required the correct Windows "code page". For example, to use the Japanese version, Windows must have 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 a Japanese Palisade add-in on a non-Japanese machine, you will need to change the default Windows code page.

To change the code page in Windows 8, Windows 7, and Windows Vista:

  1. Open Control Panel » Region and Language. (It's just Region in Windows 8.)
  2. Select the Administrative tab.
  3. Click the button "Change system locale ..." and select the correct language.

To change the code page in Windows XP:

  1. Open Control Panel » Regional and Language Options.
  2. Select the Advanced tab.
  3. Under "Language for non-Unicode programs", select the correct language.

Additional keywords: Chinese, French, German, Portuguese, Russian, Spanish

Last edited: 2016-07-12

2.76. "The trial license was not successfully loaded"

Applies to:
All products, release 5.x

Problem:
When I try to start a non-networked version of your software, I get the error message

The trial license was not successfully loaded

Response:
This message appears when the software is unable to write or read a license record. Even if you have a purchased license, the message still refers to a trial license because the software looks for a trial license if it fails to find a purchased license.

There are several possible causes for this error message:

  • Insufficient privilege for installation

    Assuming it's a native Windows machine, then most likely the product was not installed with sufficient privilege. While an ordinary user should be able to run our software, it requires full administrative rights at install time.

    Please log on as a full administrator. If you have Windows XP or an earlier Windows, re-run the installer. If you have Windows Vista, please right-click the installer and select Run As Administrator, even though you're already logged on as administrator.

  • Imperfect Windows emulation

    If you're running on a Mac with Windows emulation, or in a virtual machine, the Windows emulation may be very good but not perfect. Our licenses, even trial licenses, are written to a non-file area of your hard drive called Trusted Storage. If your Windows emulation or virtual machine can't handle that, you will be unable to run Palisade software.

  • Security software

    You may have some security software running that interferes with writing to a non-file area of the disk or reading from it. Either disable this software or, if possible, list Palisade software as a trusted exception. (Please consult the documentation for your security software; we're unable to provide detailed instructions.)

  • Course.asr file missing with release 5.5 course license

    If you have a course license, when you install it the Course.asr file must be in the same folder as the installer. If you downloaded a .ZIP file, make sure to extract both the installer and the Course.asr file to your desktop before installing. If you received the course license on a disk, insert the actual disk in your disk drive, or copy all files from it to your desktop.

last edited: 2009-07-10

2.77. "This add-in requires Excel to use the system separators."

Applies to:  All products, releases 6.x/7.x

When I launch the software, I get this error message:

Operation failed.
Details:
This add-in requires Excel to use the system separators.

How do I fix this?

The "separators" are the decimal symbol, digit grouping symbol, and so on. You can set them in Windows Control Panel (Region and Language) and they will apply to all programs. You can also set them in Excel (Decimal separator and Thousands separator in the Advanced Options dialog, in the Editing section). Although you can make Excel's thousands separator and decimal separator different from the Windows settings, our software requires that you not do this. 

In Excel 2003, click Tools » Options, select the International tab, and put a check mark in the box labeled Use system separators.

In Excel 2010 and newer, click File » Options » Advanced, and under Editing options put a check mark in the box labeled Use system separators. (Excel 2007 is the same except that you begin with the round Office button and Excel options.) Here's a screen shot:

Last edited: 2015-10-07

2.78. "This workbook has lost its VBA project."

When I try to launch my Palisade software, I get a pop-up like this one

Repairs to 'Risk.xla'

Excel was able to open the file by repairing or removing the unreadable content.

This workbook has lost its VBA project, ActiveX controls and any other programmability-related features.

You have Visual Basic for Applications disabled, either by a policy setting or because it was disabled during installation of Microsoft Office. Microsoft's articles Some Excel features are unavailable if you disable Visual Basic for Applications and run Excel and Considerations for disabling VBA in Office explain that this makes some Excel features unavailable, including some native Microsoft Excel add-ins and add-ins from third parties.

To solve the problem, re-enable Visual Basic for Applications:

  1. Open Control Panel » Programs and Features (in Windows XP, Add or Remove programs).
  2. Select Microsoft Office and click Change in the menu at the top, or right-click Microsoft Office and select Change.
  3. Select Add or remove features and click Continue.
  4. In the list that appears, click the plus sign to expand Office Shared Features.
  5. Click the drop-down arrow next to Visual Basic for Applications and change it to Run from My Computer. Click Continue.

If VBA was already set to Run from My Computer, you or your IT department have set a system policy to disable it. This prevents many Excel features from working, as explained in the articles cited above. Please ask your IT department to remove the policy setting Disable VBA for Office applications.

That policy setting assigned a value of 1 to the VBAOFF value in the System Registry, according to Method 3 in How to turn off Visual Basic for Applications when you deploy Office, so you may be able to re-enable VBA by changing the value to 0. The VBAOFF value is located in HKEY_LOCAL_MACHINE\Software\WOW6432Node\Policies\Microsoft\Office\nn.0\Common or HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office\nn.0\Common, where nn is 15 for Office 2013, 14 for Office 2010, 12 for Office 2007, or 11 for Office 2013.

Last edited: 2015-06-30

2.79. "Timeout creating the named pipe"

Applies to: Palisade software, releases 6.x/7.x

When I try to launch my software, I get this error message:

Authorization failure
Details: Timeout creating the named pipe \\.\pipe\RPC pipe for PalFlexServer6.exe, processId=0

There are a number of possible causes and cures. Here are the ones we're aware of from customer experiences:

  • Have you tried restarting Windows? Sometimes Windows gets itself into a bad state, and when you restart Windows it repairs itself. This is not just a matter of logging off and on, but restarting Windows (rebooting).

  • Is the FLEXnet Licensing Service enabled? Click Start » Run, enter the command services.msc and press the Enter key. Scroll down to FLEXnet Licensing Service. Look at Startup Type, which should be Manual.  Look also at Status:

    • If Status is Started, the service is installed correctly and running normally.
    • If Status is blank, right-click the service and select Start. If Status changes to Started, the service is installed correctly. If Status does not change, press F5 to refresh the window. If the service cannot start, that's the problem.  First try repairing the Palisade software.  If that does not solve the issue, either contact Technical Support or try uninstalling and reinstalling the software, making sure to run the installer as administrator.
  • Does your installation allow only specified programs to run? Have your administrator specify PalFlexServer6.exe as an allowed program.

  • Do you have Excel 2007? Make sure that your Service Packs are up to date, and then run a repair:
    http://kb.palisade.com/index.php?pg=kb.page&id=112

  • Is your hardware going bad? We have had reports of this error shortly before a hard drive failed. Run the manufacturer's hard-drive checker, and run a good third-party RAM tester.

Last edited: 2015-10-07

2.80. "Timeout error starting ... PalFlexServer.exe"

Applies to: All products, release 6.x/7.x

While trying to launch @RISK (Evolver, PrecisionTree, etc.), I get this error message:

Authorization failure.
Details: Timeout error starting C:\Program Files (x86)\Palisade\System\PalFlexServer7.exe

Or:

Authorization failure.
Details: Timeout error starting C:\Program Files (x86)\Palisade\System\PalFlexServer6.exe

(In 32-bit Windows, "(x86)" is not part of the message.)

PalFlexServer6 or PalFlexServer7 is the license process, and for some reason it's unable to start. Please follow these steps to verify that the license process is not disabled:

  1. Click Start » Run, type services.msc and press the Enter key.
  2. Find FLEXnet Licensing Service in the list, and check its status. It should be set for Manual start. If it's set to Disabled, right-click it, select Properties, change Startup type to Manual, and click OK. (There's no benefit to setting Startup type to Automatic.) Close the Services window.

If you change Startup type to Manual, you should be able to launch the software now. If Startup type was already Manual, or if the software still will not run, please check two other possible causes:

  • Do you have Windows set up to allow only named executables to run? In that case, add PalFlexServer6.exe or PalFlexServer7.exe to the whitelist.

  • Has PalFlexServer6.exe or PalFlexServer7.exe been flagged as a false positive in your antivirus logs? If so, add it to the whitelist in your antivirus program.

Last edited: 2015-10-07

2.81. "Unable to cast COM object"

Applies to: @RISK 7.x

My @RISK was working fine, but some Windows updates ran, and now when I launch @RISK I get this message:

Unable to cast COM object of the type 'System. – Com Object' to interface type'AtRiskOL7.RiskProductionInformation'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{20534293-A49C-4BC4-B89E-3D0FD0CE3184}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))

Unfortunately, Windows 10 updates in October 2016 seem to break @RISK's COM interface for a number of users. We don't yet know if it's just the one mentioned in the error message above, or if other registrations are also broken, and would show up when you access particular features of one or more of the applications.

Therefore, we're presenting two methods to fix the problem. Option A is quicker, but fixes just the COM registrations for the AtRiskOL file listed in the error message. Option B is more work, but should fix any registrations that are broken, even if we don't know about them yet.

Option A — REGSVR32

  1. Open File Explorer: Windows+E, or double-click on any folder. Navigate to C:\Program Files (x86) — if that folder doesn't exist, select C:\Program Files. Double-click Palisade and then double-click RISK7.

  2. Within the RISK7 folder, locate AtRiskOL or AtRiskOL.dll. Press and hold the Shift key on your keyboard, right-click the file, click Copy as Path, and release your Shift key.

  3. In an administrative command prompt, type regsvr32 and press the space bar. Right-click in the window and select Paste. Press the Enter key.

  4. You should see a popup message about successful registration. This completes the fix. But if you get any similar error messages when using @RISK or the other applications, please tell us about them.

Option B — Repair or Upgrade

Last edited: 2017-02-17

2.82. "Unable to create reference to RiskModel6.Server"

Applies to: @RISK 6.x/7.x

When I try to launch @RISK, I get this error message:

Operation Failed
Unable to create reference to RiskModel7.Server
Error in loading DLL

Or:

Operation Failed
Unable to create reference to RiskModel6.Server
Error in loading DLL

However, if I start Excel first and then start @RISK, it runs fine.

Please see "Error in loading DLL" (at Startup).

Last edited: 2015-10-07

2.83. "Unable to load ... PalFlex_x86.dll"

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

At startup, the software will not load but displays a message like one of these:

Unable to load DLL: C:\Program Files(x86)\Palisade\System\PalFlex7_x86.dll
Unable to load DLL: C:\Program Files\Palisade\System\PalFlex7_x86.dll
Unable to load DLL: C:\Program Files(x86)\Palisade\System\PalFlex6_x86.dll
Unable to load DLL: C:\Program Files\Palisade\System\PalFlex6_x86.dll

Could not load DLL: C:\Program Files(x86)\Palisade\System\PalFlex7_x86.dll
Could not load DLL: C:\Program Files\Palisade\System\PalFlex7_x86.dll
Could not load DLL: C:\Program Files(x86)\Palisade\System\PalFlex6_x86.dll
Could not load DLL: C:\Program Files\Palisade\System\PalFlex6_x86.dll

(The path will vary, depending on where you installed the Palisade software. Depending on your Palisade software release and your version of Windows, the file name may be any of PalFlex5.dll, PalFlex5_x64.dll, PalFlex5_x86.dll, PalFlex6_x64.dll, PalFlex6_x86.dll, PalFlex7_x64.dll, PalFlex7_x86.dll.)

The most common root cause of this error is using our installer without full administrative rights, or using a customer-packaged installer. It may also arise from Windows updates. In any case, the immediate problem is probably a missing or improperly installed prerequisite: a particular version of MSVC++ Redistributable or .NET.

Either log on to Windows with full administrative rights and reinstall the software using our EXE installer, or follow these instructions to install the missing or malfunctioning prerequisites .NET, MSVC++ runtime, and Visual Basic runtime:

Last edited: 2017-05-05

2.84. "Unable to load ... Dtools5.xll"

Applies to:
@RISK for Excel 5.x
RISKOptimizer 5.x
PrecisionTree 5.x
Evolver 5.x

Problem:
When I try to start @RISK for Excel or one of the other tools mentioned, I get the message

Unable to load C:\Program Files\Palisade\System\Dtools5.xll

or

Unable to load C:\Program Files (x86)\Palisade\System\Dtools5.xll

Response:
You have @RISK 4.x for Project and one or more of our Excel add-ins installed. Normally they coexist peacefully. But when you run @RISK for Project and have it generate reports in Excel, it loads an add-in called Dtools32, and when @RISK for Project closes it leaves that add-in permanently enabled in Excel. Dtools32 conflicts with our add-in called Dtools5, which is used by @RISK, RISKOptimizer, PrecisionTree, and Evolver. Therefore, the next time you try to run one of those Excel add-ins, you get the above error message.

The cure is to disable the older add-in manually. Open Excel (not @RISK), and follow these instructions:

  • Excel 2010: Select File » Options » Add-Ins. At the bottom of the right-hand panel, select Manage Excel Add-ins and click Go. Remove the check mark at Dtools32, click OK, and close Excel.
  • Excel 2007: Click the round Office button, then select Excel Options » Add-Ins. At the bottom of the right-hand panel, select Manage Excel Add-ins and click Go. Remove the check mark at Dtools32, click OK, and close Excel.
  • Excel 2003: Select Tools » Add-Ins. Remove the check mark at Dtools32, click OK, and close Excel.

This will not recur if you open @RISK for Project and run a simulation. But if you generate reports into Excel from @RISK for Project, you will probably need to disable this add-in manually again before running our Excel add-ins.

last edited: 2012-01-05

2.85. "Unable to load ... Dtools6..."

Applies to: All products, release 6.x

When I try to start @RISK for Excel or one of the other Palisade tools, I get one of these messages

Unable to load C:\Program Files\Palisade\System\Dtools6_x86.xll

Unable to load C:\Program Files (x86)\Palisade\System\Dtools6_x64.xll

Unable to load C:\Program Files (x86)\Palisade\System\Dtools6_x86.xll

If Office is not installed locally on your computer, your deployment of Microsoft Office is the problem. See Click-to-Run and Office 365 with Palisade Software for more information.

When Office is installed locally on the computer (as opposed to Web Apps, Office Online, On Demand, and Office 2010 Click-to-Run), we have not been able to reproduce this problem here at Palisade. But a couple of customers solved it by uninstalling and reinstalling Office, and one solved it by uninstalling and reinstalling the Palisade software. In each case this was a full uninstall/reinstall, not just a repair.

Last edited: 2015-05-08

2.86. "Unable to load ... Dtools7..."

Applies to: All products, release 7.x

When I try to start @RISK for Excel or one of the other Palisade tools, I get one of these messages

Unable to load C:\Program Files\Palisade\System\Dtools7_x86.xll

Unable to load C:\Program Files (x86)\Palisade\System\Dtools7_x64.xll

Unable to load C:\Program Files (x86)\Palisade\System\Dtools7_x86.xll

The needed versions of the Visual C++ libraries are not installed, or not installed properly. Please see Microsoft Components Required for Palisade 7.x Software Install, and install the needed version or versions.

Last edited: 2016-03-01

2.87. "Unable to read product language"

Applies to:
All products, release 5.x and newer

Problem:
When I try to launch one of the tools, I get the message

Operation failed: unable to read product language

Response:
This message usually points to a permissions problem, possibly at install time. Please run a repair of the software by following the instructions in Repair of Palisade Software.

If that doesn't resolve the issue, please contact Technical Support.

last edited: 2011-06-06

2.88. "Unable to set the installed property ..."

Applies To:
@RISK 4.5 for Excel (not including @RISK 4.5.7)
@RISK for Project 4.1.4
@RISK 4.0 for Excel
Evolver
RISKOptimizer

Problem:
@RISK (Evolver, RISKOptimizer) will not start and returns the error message:

Runtime error 1004: Unable to set the installed property of the add-in class.

or

Runtime error 1004: Unable to get the add property of the add-in class.

(Please contact Technical Support if the message is "That function is not valid".)

Response:
This error message can occur for a couple of different reasons. Here are possible causes and cures.

Reason 1: The Dtools32 add-in, which is used by @RISK, has not been properly added to the Excel Add-In collection.

To begin, get into Excel's Add-Ins dialog. This is in different places in different versions of Excel, as follows:

  • Excel 2003 and below: In the menu, click Tools » Add-ins.
  • Excel 2007 (if you are running @RISK for Project 4.1.4r2 or r3): Click the round Office button, then Excel Options » Add-Ins. At the bottom of the right-hand panel, select Excel add-ins and click Go.
  • Excel 2010 (if you are running @RISK for Project 4.1.4r3): Click File » Options » Add-Ins. At the bottom of the right-hand panel, select Excel add-ins and click Go.

After opening Excel's Add-Ins dialog:

  • If Dtools32 is listed but not checked, check it, and then exit Excel.

  • If Dtools32 does not appear in the Add-Ins dialog:

    1. Click the Browse button in the Add-Ins dialog. Use the Browse dialog to navigate to the folder path C:\Program Files (x86)\Palisade\SYSTEM, C:\Program Files\Palisade\SYSTEM, or C:\DTOOLS\SYSTEM, whichever one exists.
    2. Select Dtools32.xll and click the OK button.
    3. Dtools32 should now appear in the Add-Ins dialog with a check mark in the adjacent box. Click OK.
    4. Exit Excel.
  • If Dtools32 is checked:

    1. Remove the check mark beside Dtools32.
    2. Close Excel completely.
    3. Reopen Excel by itself, without attempting to open @RISK.
    4. Get back into the Add-Ins dialog; see above for instructions for your version of Excel.
    5. Click the Browse button in the Add-Ins dialog. Use the Browse dialog to navigate to the folder path C:\Program Files (x86)\Palisade\SYSTEM, C:\Program Files\Palisade\SYSTEM, or C:\DTOOLS\SYSTEM, whichever one exists.
    6. Select Dtools32.xll and click the OK button. You will probably get the message: "A file named Dtools32 already exists in this location. Would you like to replace it?" Select Yes.
    7. Exit Excel.

Launch @RISK. The error message should now be eliminated.

Reason 2: "Trust all installed add-ins and templates" has been turned off in the Macro Security settings.

The following procedure should resolve the error:

  • If you have Excel 2003 or below:

    1. Start Excel and select Tools > Macro > Security from the menu.
    2. Make the Trusted Publishers tab active.
    3. Check the box labeled "Trust all installed add-ins and templates" then hit OK.
    4. Exit Excel.
  • If you have Excel 2007 with @RISK for Project 4.1.4r2 or r3, or Excel 2010 with @RISK for Project 4.1.4r3, see Excel Macro Security settings.

Now the appropriate Palisade add-in should load without incident.

last edited: 2013-02-27

2.89. "Using ... via remote access or Terminal Services is not allowed ..."

Applies to: All products, releases 6.x/7.x

When I launch my Palisade software, I get this error message:

Using productname via remote access or Terminal Services is not allowed for this type of license. To run this Excel add-in, you must be physically present at the computer. However, administrators can use remote access to activate or deactivate licenses. Are you an administrator who wants to manage Palisade licenses on this computer?

Or,

Authorization failure.
Details:
Using productname via remote access or Terminal Services is not allowed.

Palisade licenses for standalone workstations, and for Enterprise Network clients, require you to be physically present at the computer where the software is installed.  These license types do not support running the software in a remote-login session such as Remote Desktop or Terminal Services.  When you launch the software in a remote-login session, this message appears.

Special note for XP Mode in Windows 7: Microsoft has implemented Windows 7's XP Mode as a form of remote desktop, and therefore you cannot run standalone versions of our software in XP Mode in Windows 7. However, there's no need to do that anyway, because all of our recent releases run just fine in 32-bit or 64-bit Windows 7.

Click Yes if you want to run License Manager via remote access. The typical use here is for IT people to activate or deactivate licenses on end users' computers. Such licensing actions are allowed for convenience, but you can't run the actual application.

If running via remote login is a requirement for you, please contact your Palisade sales manager about a Concurrent Network license, which will permit remote access. Another option is an auxiliary license or "laptop license" (available in some regions), a reduced-cost standalone license that you can install on the remote workstation.

Last edited: 2015-07-24

2.90. "You have one or more open workbooks with associated VBA macros. ..."

Applies to: All Palisade add-ins releases 5.x–7.x, running in Excel 2007 or newer

I'm running Excel 2007–2016. I open @RISK and my workbook. @RISK puts up this message:

You have one or more open workbooks with associated VBA macros. Please ensure these macros are enabled before using Palisade DecisionTools add-ins. Failure to enable these macros can lead to unpredictable behavior.

Why is this message appearing, and how can I prevent it?

Why it happens:

In Excel 2007 or newer, a very unfortunate scenario is possible, one that could affect any macro-enabled code and not just the DecisionTools Suite add-ins. If a trusted add-in (macros enabled) is running, and your open workbook contains macros that have not been enabled, Excel and the add-in can become unstable, and all your work can be lost.

This is a bad situation, and there is no way any add-in can prevent it. Again, this can happen when your workbook contains disabled macros. @RISK, PrecisionTree, and our other add-ins all warn you when the potential exists for this situation, so that you can take the necessary action to protect yourself from losing your work.

There is unfortunately the possibility of "crying wolf" here. No add-in can enable macros in your workbook for you, and add-ins can't even detect whether macros have been enabled in user workbooks. (Microsoft Excel very properly makes such action impossible, because they could be exploited by viruses.) This means, unfortunately, that you see the message when you open a workbook that contains macros, even if you have already enabled macros for that workbook. Add-ins must give the warning message for every workbook with macros, or for no workbooks with macros. Because the potential downside is loss of days or weeks of your work, we chose the first course of action.

How to prevent the message:

Option 1: The simplest, safest, and most flexible solution is simply to keep your workbook in a trusted location that you have listed in Excel. Workbooks in trusted locations automatically have their macros enabled, and when a workbook is opened from a trusted location the message does not appear. To manage your trusted locations, please search Excel help, as follows:

  • Excel 2013 or 2016: "Add, remove, or change a trusted location"
  • Excel 2010: "Add, remove, or modify a trusted location for your files"
  • Excel 2007: "Create, remove or change a trusted location for your files"

When you receive a workbook from someone else, consider carefully before you place it in a trusted location.

Note: @RISK 6.2.1 and earlier check only the trusted User Locations, not the trusted Policy Locations. The procedures in Excel's help will suppress the warning message as promised, because they set User Locations. However, if your administrator sets Policy Locations, @RISK will not sense those as trusted, even though Excel does, and @RISK will display the warning message for macro-enabled files opened from those locations. Starting with release 6.3.0, @RISK senses both User Locations and Policy Locations. See also Group Policy and Office Customization Tool Settings: Technical Reference.

Option 2: Does your workbook actually need macros? Sometimes people create a new workbook as a copy of an existing one and then modify parts, or over time a workbook is modified or used differently and its macros are no longer needed. If you don't actually need the macros in your workbook, remove them and save the workbook as an .XLSX type. (You can access all macros by pressing Alt-F11 to bring up the VBA editor. After removing macros, you also need to delete any empty modules that contained macros.) Caution: It is not safe simply to disable macros for a workbook that contains them. That opens you up to the catastrophic scenario described above.

Option 3: For completeness, we mention one last possibility, though it is suitable only in very special situations. You could also prevent the message by choosing the lowest security setting, "Enable all macros", in the Trust Center's Macro Settings. But in general we recommend against that, because it leaves you vulnerable to any malicious code that might be embedded in a workbook.

Last edited: 2015-10-07

2.91. Excel prompts for "VBA Project" or "VBA Converter"

Applies to:
The DecisionTools Suite 4.5.6 and earlier
@RISK for Excel 4.5.6 and earlier
BestFit 4.5.6 and earlier
Evolver 4.0.8 and earlier
NeuralTools 1.0.0
PrecisionTree 1.0.8 and earlier
RISKOptimizer 1.0.8 and earlier
RiskView 4.5.6 and earlier
StatTools 1.1.0 and earlier
TopRank 1.5 and earlier

Problem:
When I launch @RISK, PrecisionTree, StatTools, Palisade software in Excel 2007 or 2010, I get the message

Opening the VBA Project in this file requires a component that is not currently installed...
Search MS Office online for VBA Converters

Response:
You are running an older version of our software. The versions listed above are not compatible with Excel 2007. For the software version required with your versions of Excel and Windows, please see Windows and Office Versions Supported by Palisade.

Please contact your Palisade sales manager to obtain an upgrade to the current version of your product, which will be compatible with Excel 2003 through Excel 2013. If your maintenance plan is current, there is no charge for the upgrade.

While you're waiting for the activation ID for your upgrade, if you'd like to get started with our current release you can download a trial version. When you get the activation ID for your upgrade, just enter it in the trial version to convert it to a permanent version, with no need to download or install anything else.

last edited: 2013-09-16

3. All Products: Other Issues

3.1. Repair of Palisade Software

Disponible en español: Reparación del Software de Palisade
Disponível em português: Reparação do Software Palisade

Applies to:
All products, release 5.0 and newer

Summary:
Users often try to solve problems by uninstalling and reinstalling the software. That may be appropriate in some cases, but usually it is not the best approach. In many cases it is just as effective to repair the software ("do a repair install").

A repair, as opposed to uninstall/reinstall, has the additional benefit that any activations in place are not disturbed, and a trial version remains usable until its original expiration date.

Procedure:
(Note: You must be logged on as a full administrator to install, uninstall, or repair the software.)

Open Windows Control Panel » Programs and Features. (In Windows XP Control Panel, select Add or Remove Programs.) Locate your Palisade software in the list. The DecisionTools Suite might be under D or T; @RISK should be at the near of the list.

Different Windows versions have slightly different repair sequences. One or more of these will work for you:

  • Right-click on the Palisade software line item, and select Repair.
  • Left-click (a normal click) on the Palisade software you want to repair, and select Repair in the menu that appears above the list of programs.
  • If you click on the Palisade software line item and "Click here for support information" appears, click on it, then click Repair. If Repair does not appear, and the only buttons you have are Change and Remove, click Change to trigger the setup program and then select Repair.

If the repair succeeds, you won't see any success or completion message; the window will simply disappear. It's quite unusual for a repair to fail, but if that happens you'll see an error message.

Alternative procedure:
(Note: You must be logged on as a full administrator to install, uninstall, or repair the software.)

Simply re-run the installer. When prompted for Modify, Repair, Remove, select Repair. (If you're not sure you have the correct installer, Palisade Technical Support can send you a link. Include your serial number or the name and edition of your textbook in your email.)

Last edited: 2016-12-15

3.2. Repair of Excel or Project

Disponible en español: Reparación de Excel o Project
Disponível em português: Reparando Excel ou Project

Applies to: All Palisade add-ins for Microsoft Excel or Project

If a Palisade representative suggests a repair of Microsoft Office, or if you want to do it on your own, please follow the steps below. (Depending on how your computer is set up, you may need to get an administrator to do this for you.)  There's no need to reinstall your Palisade software unless a Palisade representative specifically suggests it.

Office 2013 and Office 2016:

See Microsoft's article Repair an Office Application. Although it takes a little longer, we recommend the Full Repair (Online Repair) rather than the Quick Repair, if you're given that option.

An uninstall/reinstall doesn't do much more than a repair, but it does do a few extra things. If you want to try an uninstall/reinstall instead of the repair, see Microsoft's article Uninstall Office 2016, Office 2013, or Office 365 from a PC.

Office 2010:

Please open Excel help and find the topic "Repair or remove your Office programs".  It gives step-by-step instructions for a repair of Excel based on your version of Windows.

Caution: The article also gives uninstall instructions. Make sure you follow the steps for repair, not uninstall.

Office 2007:

1. Click the Windows Start button, then Control Panel, then Programs and Features (in Windows 7 or Vista) or Add or Remove Programs (in Windows XP).

2. Find Microsoft Office 2007 in the list of programs that appears.

3. Highlight Microsoft Office 2007 and select Repair.
If Repair does not appear, and the only buttons you have are Change and Remove, click Change to trigger the setup program and then select Repair.

Office 2003:

1. Start Excel (but not any Palisade software).  If a blank workbook doesn't open automatically, open one.

2. In the menu, click Help and then Detect and Repair.

Last edited: 2017-04-11

3.3. Clean Uninstall and Reinstall of Palisade Software

Disponible en español: Desinstalación y reinstalación del software de Palisade
Disponível em português: Desinstalando e Reinstalando Software da Palisade

Applies to:
All products, all releases

If you have only releases 6.x/7.x, and you want to uninstall/reinstall all Palisade software, use the Shorter Uninstall and Reinstall of Palisade 6.x/7.x Software.

I'm having a problem and I want to solve it by uninstalling and reinstalling the Palisade software. How do I do that?

The first question is not "how?" but "should you?" People often rush to uninstall and reinstall the software when something easier and less disruptive would solve their problem. And the uninstall-reinstall may create new problems or make the original one harder to solve. Please try a repair of your software (releases 5.x and later) or contact Technical Support with details of your problem before taking this drastic step.

If you're reinstalling Windows, don't use this procedure. Deactivate your Palisade software before you reinstall Windows, and then reactivate it again afterward.

But for some problems a clean uninstall and reinstall may be appropriate, and Technical Support will refer you to this article. The procedure below will preserve your license so that you do not need to reactivate or reauthorize your software.

Please perform all of the listed steps in order. This will remove current and old versions of the Palisade software. If you skip steps (except as directed), you may not get the desired benefit. If you get error messages during the install or uninstall steps, please see Fix problems that programs cannot be installed or uninstalled.

Caution: This procedure will wipe all Palisade software off your computer. If you have any Palisade software that you don't want to uninstall, please consult Technical Support before following this procedure.

  1. If you don't have an installation CD, obtain the appropriate installer and place it on your desktop. If it is a ZIP file, double-click it, extract all files from it to your desktop, and close the ZIP file.

  2. If your software is a network client or a course license, also obtain the appropriate .INI or .LIC file and place it on your desktop.

  3. Disconnect from the Internet. (Unplug your Ethernet cable or modem cable, or turn off your wireless connection.) This prevents the uninstall from deactivating your license.

  4. Log on to Windows as a full administrator. You need full administrative rights to uninstall and install software. You don't need administrative rights to authorize or run the Palisade software.

  5. Make sure that Microsoft Excel and Project are not running.

  6. Uninstall all Palisade software using Windows Control Panel » Programs and Features (in Windows XP, Add or Remove Programs). If the uninstaller fails, keep going.

    • @RISK is alphabetized before A.
    • The DecisionTools Suite 5.0 and newer is alphabetized under D, but 4.x is alphabetized under T.
    • A book version might be under D, under T, or under P for Palisade.

    During uninstall, you may be prompted to deactivate a license. You want to uninstall without deactivating the license. (Read the prompt carefully before you click Yes or No.)

  7. Delete the DTools.ini text file from your C:\Windows or C:\Winnt folder, if that file exists. (If you have never installed a 1.x or 4.x version of our software, there may not be a DTools.ini file.)

  8. Look for a DTOOLS folder in the top level under the C drive, and if it exists delete it. (Again, if you have never installed a 1.x or 4.x version, this folder may not exist.)

  9. Look for the folder C:\Program Files (x86)\Palisade or C:\Program Files\Palisade, and if it exists delete it.

  10. If there's any possibility the Palisade software was installed to a non-default location, do a search of your hard disk for file names containing "dtool" and delete the folder that contains those files. Exception: ignore anything under a folder called Recycled.

    Caution: While it's unlikely, it's possible that some non-Palisade files might have "dtool" in their names. If you're not sure about the contents of a folder you find through a search, consult Technical Support before deleting it.

  11. Click the Windows Start button, then All Programs or Programs. Look for a Palisade group, and if it's present right-click on it and select Delete. Also delete any desktop shortcuts to Palisade software.

  12. Click Start » Run, type Regedit and click OK. Make the following edits:

    1. Navigate to HKEY_LOCAL_MACHINE\Software (HKEY_LOCAL_MACHINE\Software\WOW6432Node in 64-bit Windows) and if necessary click the + sign to expand it. Under Software in the left-hand panel, right-click the Palisade subkey and select Delete to delete it and all of its subkeys. (If you have only very old versions, there might not be a Palisade key under Software.)
    2. Still under HKEY_LOCAL_MACHINE\Software (HKEY_LOCAL_MACHINE\Software\WOW6432Node in 64-bit Windows), look for FLEXlm License Manager. If it exists, click once on it and then look at the right-hand panel. If you have a network license for version 5.0 or newer, right-click on PALISADE_LICENSE_FILE and delete it but don't do anything to any other entries you may see. If you have a standalone license for version 5.0 or newer, double-click on PALISADE_LICENSE_FILE to edit it, and delete all text and punctuation except C:\Program Files\Palisade\System or C:\Program Files (x86)\Palisade\System. (If you have only 1.x and 4.x versions, there might not be a FLEXlm License Manager key.)
  13. Reboot your computer.

  14. Launch Excel. You might get the Excel error message "Could not find C:\Program Files\Palisade\SYSTEM\DTools32.xll". (A different path might appear on the message.) If you do not get this error message, close Excel and proceed to step 15. If the error message does appear, follow these steps to eliminate the error:

    1. Get into the Excel Add-Ins dialog. To do this, follow the directions for your version of Excel:
      • Excel 2010 or 2013: Click File » Options » Add-Ins. At the bottom of the dialog, next to Manage, select Excel Add-Ins and click Go.
      • Excel 2007: Click once on the round Office button, then Excel Options, then Add-Ins. At the bottom of the dialog, next to Manage, select Excel Add-Ins and click Go.
      • Excel 2003 or below: Choose Tools » Add-Ins.
    2. In the list of Add-Ins, locate DTOOLS32 and remove the check mark beside it.
    3. When you remove the check mark, a message will appear: "Cannot find add-in 'DTools32.XLL'. Delete from list?" Click the Yes button to delete it from the list.
    4. Close Excel.
  15. Run the installer program(s): In Windows Vista, Windows 7 or later, right-click the installer and select Run As Administrator. In earlier Windows, double-click the installer.

    With releases 6.x/7.x, on the Customer Information screen, select "I am upgrading or reinstalling". Don't enter your Activation ID and don't select a trial license.

    With releases 5.x, don't enter your Activation ID.

  16. If you wish, reconnect to the Internet.

Actions after install:

  • Test the software and make sure it opens without error and that the major functions perform correctly.

  • There should be no need to reactivate or reauthorize the software.

  • If you want shortcuts on your desktop, and the installer did not offer that option, copy the icons from the Start menu, as follows: click the Windows Start button, then All Programs or Programs, then Palisade DecisionTools. Right-click the desired shortcut, drag it to your desktop, and when you release the right mouse button select Copy Here.

  • Do not add any of our files to Excel's add-ins list. Always launch the software by clicking the desktop icon (if available), or by clicking the Windows Start button, then Programs or All Programs, then Palisade DecisionTools. Let the Palisade software open Excel or Project for you.  However, if you want one or more Palisade applications to run automatically every time Excel runs, please see Opening Palisade Software Automatically Whenever Excel Opens.

Last edited: 2017-05-16

3.4. Shorter Uninstall and Reinstall of Palisade 6.x/7.x Software

Applies to:
All products, releases 6.x
All products, releases 7.x
BigPicture, all releases

If you have any earlier versions, see Clean Uninstall and Reinstall of Palisade Software.

I'm having a problem and I want to solve it by uninstalling and reinstalling the Palisade software. How do I do that?

Important: Use this short procedure if you have only Palisade software releases listed in "Applies to" above, and you want to uninstall all your Palisade software. If you don't want to uninstall everything, please contact Technical Support for advice.
 
If you're reinstalling Windows, don't use this procedure. Deactivate your Palisade software before you reinstall Windows, and then reactivate it again afterward.

The first question is not "how?" but "should you?" People often rush to uninstall and reinstall the software when something easier and less disruptive would solve their problem. And the uninstall-reinstall may create new problems or make the original one harder to solve. Please try a repair of your software or contact Technical Support with details of your problem before taking this drastic step.

But for some problems an uninstall and reinstall may be appropriate, and Technical Support will refer you to this article. The procedure below will preserve your license so that you do not need to reactivate or reauthorize your software.

Please perform all of the listed steps in order. This will remove current and old versions of the Palisade software. If you skip steps (except as directed), you may not get the desired benefit. If you get error messages during the install or uninstall steps, please see Fix problems that programs cannot be installed or uninstalled.

  1. Obtain the appropriate installer(s) and place them on your desktop. 6.0.0 through 6.1.1 come in ZIP files, so if you have one of those double-click it, extract all files from it to your desktop, and close the ZIP file. (You may then delete the ZIP file.)

  2. Some license types require a .LIC or .INI file during install.

    • If your software is a network client, obtain the appropriate .INI file from your IT department. and place it on your desktop for use during the reinstall.
    • If there is a .LIC license file in C:\Program Files (x86)\Palisade\System or C:\Program Files\Palisade\System, copy it to your desktop.
  3. Make sure that Microsoft Excel and Project are not running. (If in doubt, press Ctrl+Shift+Esc to launch Task Manager, and look in the Details or Processes tab for Excel.exe and Winproj.exe.)

  4. Uninstall all Palisade software using Windows Control Panel » Programs and Features (in Windows XP, Add or Remove Programs). If the uninstaller fails, keep going.

    • @RISK is alphabetized before A.
    • The DecisionTools Suite is alphabetized under D, but 4.x is alphabetized under T.
    • A book version might be under D, under T, or under P for Palisade.

    During uninstall, you may be prompted to deactivate a license. You want to uninstall without deactivating the license. (Read the prompt carefully before you click Yes or No.)

  5. Look for the folder C:\Program Files (x86)\Palisade or C:\Program Files\Palisade, and if it exists delete it.

  6. If there's any possibility the Palisade software was installed to a non-default location, do a search of your hard disk for file names containing "dtool" and delete the parent of the folder that contains those files. Exception: ignore anything under a folder called Recycled.

    Example: If you find DTools6_x64 in D:\MyStuff\AtRisk\System, the folder is System but you should delete AtRisk, the parent of that folder. Caution: While it's unlikely, it's possible that some non-Palisade files might have "dtool" in their names. If you're not sure about the contents of a folder you find through a search, consult Technical Support before deleting it.

  7. Run REGEDIT, navigate to HKEY_LOCAL_MACHINE\Software\WOW6432Node (HKEY_LOCAL_MACHINE\Software in 32-bit Windows) and click the + sign to expand it. Right-click the Palisade subkey and select Delete to delete it and all of the subkeys below it.

  8. Still under HKEY_LOCAL_MACHINE\Software (HKEY_LOCAL_MACHINE\Software\WOW6432Node in 64-bit Windows), look for FLEXlm License Manager. If it exists, click once on it and then look at the right-hand panel. If you have a network license, right-click on PALISADE_LICENSE_FILE and delete it but don't do anything to any other entries you may see. If you have a standalone license, double-click on PALISADE_LICENSE_FILE to edit it, and delete all text and punctuation except C:\Program Files\Palisade\System or C:\Program Files (x86)\Palisade\System.

  9. Reboot your computer.

  10. Run the installer program(s): In Windows Vista, Windows 7 or later, right-click the installer and select Run as administrator. In Windows XP, double-click the installer (but you must e logged in as a full administrator).

    Important: During install, on the Customer Information screen, select "I am upgrading or reinstalling", if that option appears. Don't enter your Activation ID and don't select a trial license.

Actions after install:

  • Test the software and make sure it opens without error and that the major functions perform correctly.

  • There should be no need to reactivate the software.

  • Do not add any of our files to Excel's add-ins list. Always launch the software by clicking the desktop icon (if available), or by clicking the shortcut in the Palisade DecisionTools group. Let the Palisade software open Excel for you.  However, if you want one or more Palisade applications to run automatically every time Excel runs, please see Opening Palisade Software Automatically Whenever Excel Opens.

Last edited: 2017-03-24

3.5. I try to edit a Palisade 7.0 report, but it looks like I'm editing a different worksheet.

Applies to:
Evolver 7.0.0 in some builds of Excel 2013
NeuralTools 7.0.0 in some builds of Excel 2013
StatTools 7.0.0 in some builds of Excel 2013

Does not apply to:
@RISK, BigPicture, PrecisionTree, and TopRank in any version of Excel
Evolver, NeuralTools, and StatTools in Excel 2007, 2010, or 2016

(For release 6.x, please see I try to edit a Palisade 6.x report, but it looks like I'm editing a different worksheet.)

I generated a report in StatTools, Evolver, or NeuralTools. When I type into the report, my typing doesn't show up in the report worksheet. Instead, it shows up in a different worksheet.

The problem affects reports generated by Evolver, NeuralTools, and StatTools. After the report is generated, Excel is confused about which cell and worksheet are selected. Excel shows you the report sheet as the active one, and a thicker border around one cell indicates that cell is active. However, typing in that cell doesn't have the desired effect: Excel actually places your typed characters in a cell in another sheet. This happens even if you first select another cell on the report sheet. This is most serious for StatTools reports, because some cells in StatTools reports contain parameters that you can change while you analyze the results, like confidence levels in the Confidence Interval analysis.

The source of the problem is the KB 3085502 update to Microsoft Office 2013, published by Microsoft on 2015-09-08. This affects Excel 2013 builds 15.0.4753 through 15.0.4770. (To see if this affects you, find your Excel 2013 build number by clicking File » Account » About Excel.)

The solution is to install the latest Microsoft Office updates.

If you have Office 365, also called Click-to-Run, this should be done automatically for you by Microsoft Office, and will solve the problem.

If you have installer-based (MSI) Excel 2013, this may or may not be done automatically, depending on your Windows Update settings. If you have selected "Give me updates for other Microsoft products" or similar, then the necessary Office update should be installed automatically. As an alternative, you can download and install the KB 3101499 update from November 2015 manually.

Additional keywords: typing goes to wrong worksheet; wrong cells selected

Last edited: 2015-11-12

3.6. I try to edit a Palisade 6.x report, but it looks like I'm editing a different worksheet.

Applies to:
Evolver 6.x in some builds of Excel 2013
NeuralTools 6.x in some builds of Excel 2013
StatTools 6.x in some builds of Excel 2013

Does not apply to:
@RISK, BigPicture, PrecisionTree, and TopRank in any version of Excel
Evolver, NeuralTools, and StatTools in Excel 2007, 2010, or 2016

(For release 7.0.0, please see I try to edit a Palisade 7.0 report, but it looks like I'm editing a different worksheet.)

I generated a report in StatTools, Evolver, or NeuralTools. When I type into the report, my typing doesn't show up in the report worksheet. Instead, it shows up in a different worksheet.

The problem affects reports generated by Evolver, NeuralTools, and StatTools. After the report is generated, Excel is confused about which cell and worksheet are selected. Excel shows you the report sheet as the active one, and a thicker border around one cell indicates that cell is active. However, typing in that cell doesn't have the desired effect: Excel actually places your typed characters in a cell in another sheet. This happens even if you first select another cell on the report sheet. This is most serious for StatTools reports, because some cells in StatTools reports contain parameters that you can change while you analyze the results, like confidence levels in the Confidence Interval analysis.

The source of the problem is the KB 3085502 update to Microsoft Office 2013, published by Microsoft on 2015-09-08. This affects Excel 2013 builds 15.0.4753 through 15.0.4770. (To see if this affects you, find your Excel 2013 build number by clicking File » Account » About Excel.)

The solution is to install the latest Microsoft Office updates.

If you have Office 365, also called Click-to-Run, this should be done automatically for you by Microsoft Office, and will solve the problem.

If you have installer-based (MSI) Excel 2013, this may or may not be done automatically, depending on your Windows Update settings. If you have selected "Give me updates for other Microsoft products" or similar, then the necessary Office update should be installed automatically. As an alternative, you can download and install the KB 3101499 update from November 2015 manually.

Additional keywords: typing goes to wrong worksheet; wrong cells selected

Last edited: 2015-11-12

3.7. After Upgrading, My Standalone License Is Gone

Applies to:
All products, upgrading from one 7.x release to a later 7.x release, standalone licenses
All products, upgrading from one 6.x release to a later 6.x release, standalone licenses

I installed the upgrade, and now I no longer have a license. When I try to activate again, it says that my Activation ID is in use.

Your license is not lost, just masked. You don't need to reactivate it.

During installation of an upgrade, the installer presents a Customer Information screen. In the lower half of that screen, the options are to install a trial, to upgrade, or to activate a new license. The default is a 15-day trial, so if you just click Next — as people tend to do with installers — you get a trial license.

Your real license information is masked by the trial license. To use your real license again, in License Manager click the Select License button, select your activated license, and click OK. This is a per-user setting, so if there are multiple Windows user accounts on this computer then each user will need to use Select License once.

Last edited: 2015-10-07

3.8. After Upgrading, My Network Client License Is Gone

Applies to:
All products, upgrading from one 7.x release to a later 7.x release (network clients)
All products, upgrading from one 6.x release to a later 6.x release (network clients)

I installed the upgrade, and now the software is not using the network license. Either I get a trial prompt, or I get "Authorization failure: There is no available license."

Your network information is not gone, just masked.

During installation of an upgrade, the installer presents a Customer Information screen. In the lower half of that screen, the options are to install a trial, to upgrade, or to activate a new license. The default is a 15-day trial, so if you just click Next — as people tend to do with installers — you get a trial license.

To use your network license again, in License Manager click the Select License button, then Concurrent Network. Select your real license, and click OK. This is a per-user setting, so if there are multiple Windows user accounts on this computer then each user will need to use Select License once.

Last edited: 2015-10-07

3.9. License Lost on Upgrading Windows 8.1 Preview to Final

Applies to: Palisade software releases 5.x–7.x, non-network licenses

I was running Palisade software, with an activated license, under Windows 8.1 Preview. Everything was fine.  I upgraded to final Windows 8.1, and now my license seems to be gone.  It doesn't show up in License Manager.  What happened, and how do I fix it?

We've had several reports of this problem among people who upgraded from Windows 8.1 Preview to final Windows 8.1, though some have done the same Windows upgrade and the Palisade license was unaffected  As far as we know, users upgrading from Windows 8 are not affected.  The key may be in this comment in Stephen Rose's Springboard Series blog:  "It's also important to note that while computers running Windows 8.1 Preview can be updated to the final Windows 8.1 release, this update process will only migrate the data on the device. All applications (from the Windows Store or desktop applications) will need to be reinstalled as part of this process."

Palisade Technical Support can help recover your license. Please click the magnifying-glass icon in License Manager, then the View button. A Notepad window will open. Click File » Save, and save the file to your desktop. Attach the file to an email to Technical Support. In the body of the email, please include your serial number or Activation ID with a brief problem description.

Last edited: 2015-09-14

3.10. Quick Start or Guided Tour Videos Don't Play

Applies to:
@RISK 6.x/7.x
Evolver 6.x/7.x
NeuralTools 6.x/7.x
PrecisionTree 6.x/7.x
StatTools 6.x/7.x
TopRank 6.x/7.x

I click the link to a Quick Start video or Guided Tour video, but I just get a dark screen with no video playing.

These videos require Adobe's Flash Player plugin to run. If your browser doesn't have the plugin, or the plugin is disabled, the videos can't run.

Flash Player Help on Adobe's site includes download and installation instructions.

If Flash Player is installed but disabled, follow the link in step 4 of that same page to get instructions for enabling it in your browser. On the instructions page, make sure you are following the instructions for Windows and not for Mac.

Last edited: 2016-12-12

3.11. Errors on One Computer, OK on Another

Applies to: All Excel add-ins, all releases

I get errors in the cells of my workbook, but a colleague tried it and it works fine on her machine.

When a workbook works on machine A but not B, there are several possible explanations:

  1. Configuration differences: different versions of Excel, different versions of the Palisade software, different sets of add-ins loaded, different personal macro workbooks, and so forth.
  2. Excel is malfunctioning. To resolve this, do a Repair of Excel.

  3. The Palisade software is malfunctioning. To test this, try another workbook, such as one of our examples. In our 5.x–7.x releases, click the help icon (the question mark) on our toolbar and then Example Spreadsheets. In earlier releases, find our examples in the Examples folder under the product folder under the Palisade installation folder.

    If the software works with another workbook, go to item 4 below. But if the second workbook also fails on this machine but is fine on another machine, then you may have a startup conflict, or a problem with your Palisade software.

    To resolve startup conflicts, please see Find and Fix Startup Conflicts (Excel 2007–2016) or Find and Fix Startup Conflicts (Excel 2003 and Earlier).

    To repair or reinstall the software:

    • For releases 5.x–7.x, do a Repair of Palisade Software. Do not uninstall the software, as you may lose your activation.
    • For earlier releases, uninstall the software (Control Panel » Add or Remove Programs, or Programs and Features for Windows 7 or Vista) and then reinstall it. You will not lose your authorization.
  4. Neither is malfunctioning, but there are links within the workbook to some resources that are available on machine B but not on machine A. These might be links to a network location that machine A cannot reach. Or they might be links to a particular location within machine B, and machine A doesn't have the referenced file or doesn't have it in the same location.

Last edited: 2015-10-07

3.12. "Can't find project or library."

Applies to:
@RISK 6.x/7.x, Professional and Industrial Editions
Evolver 6.x/7.x
NeuralTools 6.x/7.x
PrecisionTree 6.x/7.x
StatTools 6.x/7.x

I have some Visual Basic code that uses the automation features of @RISK or another product. I recently upgraded to the current release, and now when I try to run I get this message:

Compile error:
Can't find project or library

What is wrong? This code was working before.

You just need to update your module's references to @RISK in the Visual Basic Editor. Please see Setting References in Visual Basic.

Last edited: 2015-10-07

3.13. Intermittent Errors in Excel 2013 or 2016

I'm getting strange errors in @RISK, but only intermittently. For instance, I might get this popup:

The library survival mutex has not been set for this process.

Or maybe @RISK opens up and instead of a blank workbook there's just a gray background.
Or everything seems normal, but when I click Start Simulation the results window is blank.
Or the Browse Results window is just a white rectangle in the corner of a gray background.
What is going on?

If you're running Palisade software 7.0 or older in Excel 2013 or 2016, the most likely cause is an Excel setting. (This is not an issue with palisade software versions 7.5 and newer.) Click File » Options » General and look at the last option, "Show the Start screen when this application starts". With that option checked, there may be an intermittent conflict with another add-in, such as Solver, when Excel starts up. Such a conflict can have consequences at any point in the whole Excel session, not just the errors mentioned above but almost anything unexpected. To solve the problem, remove the tick mark for the last option, then close and reopen Excel.

If you have an earlier version of Excel, or if the above doesn't cure the problem, try restarting Windows (not just logging off and on). This was the solution for our few pre-Excel-2013 users who got the "library survival mutex" message.

Last edited: 2017-02-02

3.14. All Articles about "Method '~' of object '~' failed"

Applies to: All products

"Method '~' of object '~' failed" is Excel's last-ditch error message. It's Excel's way of saying "Something is wrong, but I can't tell you what." We have identified several occasions when this message pops up, with a cure for each one:

See also: This can also be caused by inappropriate COM type library registrations. See Removing Outdated References to Office from the System Registry for instructions on removing the references.

Additional keywords: Method ~ of object ~ failed; Method of object failed

Last edited: 2016-05-13

3.15. All Articles about "Object variable or With block variable not set"

Applies to: All products

"Object variable or With block variable not set" is a Visual Basic error message. It could originate in Excel itself, in Palisade code, or in your own macros if you have an .XLSM file. Roughly, it means that the VBA code used some variable without first initializing it properly.

Since there's not just one known cause, you may have to try several possibilities. Here is a list of the causes that we have seen when helping customers, and the solutions:

Additional keywords: Object variable, with block, variable not set

Last edited: 2017-04-28

3.16. "PalOutOfProcessServer has stopped working"

Applies to: All products, when used with Excel 2016, Excel 2013, or 64-bit Excel 2010

At some point during execution of @RISK (Evolver, NeuralTools, PrecisionTree, StatTools, or TopRank), I get the message

PalOutOfProcessServer7 has stopped working

or

PalOutOfProcessServer6 has stopped working

This is not a licensing issue, even if you see "Authorizing" in the Excel status line. PalOutOfProcessServer is the bridge from @RISK and our other software to 64-bit Excel 2010, or to Excel 2013 and newer Excels. If PalOutOfProcessServer can't load, then the rest of @RISK can't talk to Excel.

This error could result from a number of different conditions. What follows is a list of the known causes. Please try each of these first, but if none of them resolved the problem please contact Palisade Technical Support.

  • Perhaps our software didn't shut down cleanly the last time. You could open Task Manager and close any open processes related to our software, but it's easier and more effective just to restart Windows.

  • We occasionally see security software blocking one or another of our processes, so try disabling your anti-virus or anti-malware software temporarily and see if that lets everything run normally. If it does, please report the false positive to your anti-malware or anti-virus software vendor.

  • Another possibility is a lack of proper permissions during install. In Windows Vista and later, please reinstall by right-clicking the installer and selecting Run as administrator. In Windows XP, log on with full administrative rights and run the installer by double-clicking. Either way, if you get a screen asking about repair, modify, or remove, select Repair. If you get a Customer Information screen, change 15-day trial to I am upgrading or reinstalling.

Last edited: 2016-02-26

3.17. "Run-time error '-2147417856 (80010100)' "

Applies to: @RISK 6.x/7.x

I get the message

Run-time error '–2147417856 (80010100)'
Automation error
System call failed.

Different conditions can give rise to this error. Following are strategies that have worked for different customers in resolving this error.

  • Close everything and restart Windows – not just log off and on, but a full system restart.

  • Does this happen with more than one model? Check your active add-ins and try disabling them, then adding them back one by one. See Find and Fix Startup Conflicts (Excel 2007–2016).

  • If your simulation is not very large, switch to Multiple CPU: Disabled on the General tab of Simulation Settings.

  • A couple of customers, who had multiple versions of Excel installed, reported that they got this error in Excel 2013 but not 2010 or 2007, with the same model.

  • You may have COM registrations pointing to versions of Microsoft Office Excel or Project that aren't actually installed on your computer. Follow the instructions in Removing Outdated References to Office from the System Registry to remove them.

  • If you're using @RISK for Project release 4.1.4 (not @RISK release 6..x/7.x) and you have any background processes of Excel running, RISK may be unable to connect to Excel and you may get this error. Use Task Manager to check for any Excel.exe processes that don't have visible windows. If you find any, close Microsoft Project, then kill the Excel processes in Task Manager, then reopen @RISK for Project.

Last edited: 2015-12-21

3.18. "Run-time error '-2147417848 (80010108)' "

Applies to: @RISK 6.x/7.x

Before I've been working very long in @RISK, I get this error message

Run-time error '-2147417848 (80010108)':

Automation error

The object invoked has disconnected from its clients.

We've seen this occasionally. We're not sure what causes it, but repairing your Palisade software and Repairing Microsoft Office seems to fix it.

Last edited: 2017-01-17

3.19. "Sorry, we couldn't find StatTools.xla." (or Evolver.xla, etc.)

Applies to:
StatTools 5.x–7.x, running in Excel 2007 or newer
Evolver 5.x–7.x, running in Excel 2007 or newer
NeuralTools 5.x–7.x, running in Excel 2007 or newer
PrecisionTree 5.x–7.x, running in Excel 2007 or newer

StatTools seems to launch okay, and I get the ribbon. But when I click on any of the buttons I get this message:

Run-time error '1004':

Sorry, we couldn't find StatTools.xla. Is it possible it was moved, renamed, or deleted?

Or:

Sorry, we couldn't find Evolver.xla. Is it possible it was moved, renamed, or deleted?

Or:

Sorry, we couldn't find NeuralTools.xla. Is it possible it was moved, renamed, or deleted?

Or:

Sorry, we couldn't find PrecisionTree.xla. Is it possible it was moved, renamed, or deleted?

The StatTools (Evolver, NeuralTools, PrecisionTree) toolbar is loaded, but the computer code that takes action is not. These add-ins contain the static ribbon in each of the supported languages, but no code to perform the actions listed on the buttons:

  • StatToolsExcel12_CN.xlam, StatToolsExcel12_DE.xlam, StatToolsExcel12_EN.xlam, StatToolsExcel12_ES.xlam, StatToolsExcel12_FR.xlam, StatToolsExcel12_JP.xlam, StatToolsExcel12_PT.xlam, StatToolsExcel12_RU.xlam
  • EvolverExcel12_xx.xlam, for the same languages
  • NeuralToolsExcel12_xx.xlam, for the same languages
  • PrecisionTreeExcel12_xx.xlam, for the same languages

For convenience, in this article we'll call these the Palisade "Excel12" add-ins. You should never select any Palisade "Excel12" add-in as an active add-in. (For the add-ins that are safe to use, see Opening Palisade Software Automatically Whenever Excel Opens.)

To fix the problem, follow this procedure:

  1. Launch Excel only.
  2. Click File » Options » Add-ins. (In Excel 2007, click the round Office button and then Options » Add-ins.)
  3. If any Palisade "Excel12" add-ins are in the list of active add-ins at the top of the page, click Go at the bottom, remove the check marks from them, click OK, and close Excel.
  4. If there was no Palisade "Excel12" add-in, or if you remove it but the toolbar is still there, you added the Palisade toolbar by some other means. To remove it, right-click into the toolbar and click Remove custom toolbar. You may have to try clicking different places in the toolbar until the right-click menu offers that option.

You've solved the problem when you can launch Excel without any Palisade toolbars. After that, to launch any of our software, double-click the desktop icon, if you have one, or select the application in the Palisade DecisionTools group in your Windows start menu. If you want StatTools or any of our applications to run every time Excel runs, see Opening Palisade Software Automatically Whenever Excel Opens.

Last edited: 2016-06-24

3.20. "The certificate has expired or is not yet valid."

Looking at the Trusted Publishers information in the Excel Trust Center, I see that our certificate has expired. When I click the View button, I get the message

The certificate has expired or is not yet valid.
Certificate expiration message

How do I obtain a current certificate from Palisade?

There's no need.

All Palisade code is timestamped, meaning that a recognized certificate authority has validated that the code came from us at the time it was created. It doesn't matter to the end user if the certificate expires after that. The expired certificate can't be used to timestamp any new code, but code that was already timestamped while the certificate was in force continues to be valid.

Many articles that explain this can be found by searching "timestamped certificate" (without quotes) on the Web. Here is one, from Stack Overflow. Quote: "Timestamping involves a third party (usually your CA) attesting that you made the signature at a particular time. Regardless of when your certificate expires, somebody receiving the signed code can then verify that your certificate was valid at the time you signed it."

Microsoft's message "This certificate has expired or is not yet valid" is literally true but beside the point. You're not trying to sign code, which can't be done with an expired certificate; you're trying to use code that was signed with a valid certificate in force at the time of signing.

If you were simply exploring in Trust Center and found the expired certificate, there's no cause for alarm and you don't need to take any action. The Certificate Information screen from Excel doesn't make clear the distinction between signing new code and using existing signed code. The certificate needs to be in force when the code is signed, and it was. The certificate does not need to be in force when the signed code is used.

Last edited: 2015-06-01

3.21. "The deactivation cannot proceed because not enough time has passed"

Applies to:
All products, network server and standalone workstation, releases 6.x/7.x
(Does not apply to network clients.)

In License Manager or Server Manager, I clicked Deactivate and selected Automatic. The response was

Automatic Deactivation failed.
The deactivation cannot proceed because not enough time has passed since the last deactivation.

What is wrong?  Why can't I deactivate?  Should I try Manual Deactivation, or reinstall the software?

Please don't reinstall your software, and don't bother with a Manual Deactivation because it would fail with a similar message.

Here's the explanation: The license terms allow for one deactivation in any 90-day period, so you get this message because it's less than 90 days since the last deactivation.

Technical details: The 90-day clock runs between deactivations, not between activations, and it starts when you first deactivate a particular license (Activation ID). Thus, if you activate a license for the first time at the beginning of March, you can deactivate it as soon as you want, without waiting till June.

But once you've done that first deactivation — in May, let's suppose — then the next deactivation must wait 90 days from that deactivation. Whether you reactivate late in May, or in July, you can't deactivate it again till August, 90 days after that deactivation in May.

Though these rules can appear complicated, they ensure you're never without the software, because you never have to wait to activate it. However, you may have to wait to transfer it to another computer.

If you need to move a license less than 90 days after the last move, please send an email to Technical Support. Include your full Activation ID and explain the circumstances of why this move is needed. Technical Support may be able to grant a one-time exemption, depending on the circumstances and the history of this serial number.

But it's more than 90 days since I last deactivated!

Are you trying to move a 6.x license after upgrading to 7.x? Are you trying to move a 5.x license after upgrading to 6.x/7.x? An upgrade license replaces the old license. Though we do let you continue using the old license on the same computer, you can't transfer it to a new computer. For technical reasons connected with how FLEXnet Publisher works, we implement this policy by preventing any deactivations of the old license after the upgrade has been performed.

If this license hasn't been upgraded, did you previously request and receive an exception to the 90-day policy? If so, it may have been done by changing your policy from one deactivation in 90 days to two in 180 days. In this case, you could have done two deactivations within 90 days, but the third will have to wait till 180 days after the first, not 90 days after the second. If you think this may be your situation, please email Palisade Technical Support with your Activation ID to ask about your activation and deactivation history and when you will next be able to deactivate the license.

Last edited: 2016-05-13

3.22. "The specified dimension is not valid for the current chart type."

Applies to: Graphs in all 6.x products (not 7.x)

When I try to create some kinds of graphs in @RISK (PrecisionTree, ...), I get a blank graph and this error message:

The specified dimension is not valid for the current chart type.

There could be different symptoms, such as a message "Method '~' of object '~' failed", or just a blank worksheet with no chart and no message. The common thread is an attempt to have Palisade software create an Excel chart.

Excel refuses to create charts of some types if the default Excel chart type is one of the more complex ones. To fix this, either upgrade your Palisade software to the current release, or set your default chart to a simpler type, such as Clustered Column (Excel's original default) or Line.

In Excel 2007 and Excel 2010:

  1. Click the Insert tab in the ribbon. (It doesn't matter whether you have data pre-selected.)
  2. In the Charts section, click the tiny arrow in the bottom-right corner. An Insert Chart dialog opens.
  3. Select Column in the left panel, and then in the right panel click the first chart.
  4. Click the "Set as Default Chart" button, and then click Cancel. This sets the default chart type without actually creating a chart.

In Excel 2013 and 2016:

  1. Select a cells that contains a number. Click the Insert tab in the ribbon.
  2. In the Charts section, click the "See All Charts" button, which is the tiny arrow in the bottom-right corner. An Insert Chart dialog opens.
  3. Click the All Charts tab in the dialog.
  4. Select Column in the left panel. Then, in the right panel, right-click the first column chart and select "Set as Default Chart".
  5. Click Cancel. This sets the default chart type without actually creating a chart.

There's no need to close and reopen Excel or the Palisade software; you'll be able to create your chart now.

Acknowledgement: This article at ExcelBanter.com explains the source of the error message.

See also: There are other possible causes for "Method '~' of object '~' failed". See All Articles about "Method '~' of object '~' failed".

Last edited: 2017-02-17

3.23. "Unable to load response file."

Applies to: All products, releases 5.x and newer

I'm trying to activate or deactivate my license. I click Load Response File and submit my file, but I get this message:

Unable to load response file.

ERROR: Processing response - {50019,41141,,22}

If you need help please contact Palisade at support@palisade.com.

(The error number may vary.)

The most likely cause is submitting the wrong file.

Sometimes people accidentally submit their request file after clicking Load Response File, instead of their response file. Verify that your file name includes the word "response".

Be sure you're using the right response file for an operation. If you sent the request file to Palisade Technical Support, look at the email response you received and verify that you are using the file that was attached to it.

Also verify that you're using a current response file – right click it and select Properties to check the date and time. The response file should be the most recent response file you have.

Last edited: 2016-03-11

3.24. @RISK Ribbon Grayed Out

Applies to:
@RISK 5.x–7.x
TopRank 5.x–7.x
BigPicture 1.x/7.x

Something happened, and now my @RISK (TopRank, BigPicture) tab on the Excel ribbon is grayed out. The other Excel ribbons seem normal.

(The Results section of the @RISK ribbon is normally grayed out until you've run a simulation. This article is about the situation where almost the whole @RISK, TopRank, or BigPicture ribbon is grayed out.)

Short answer: Click Help » About @RISK (TopRank, BigPicture), and the ribbon will be restored.

Details: This can happen in Excel 2007 or later, and it's due to a bug in Excel's handling of dynamic ribbons. Therefore, it affects @RISK, TopRank, and BigPicture, which have dynamic ribbons, but not the other Palisade products, which don't.

The basic issue is that dynamic ribbons can't be updated while you're in edit mode, with "Edit" showing in the status bar at the bottom of the Excel window. (You get into edit mode by clicking into a cell and typing, or by clicking into the formula bar, among other ways.) But not all operations are prohibited in edit mode. If you do something that should cause the @RISK ribbon to change, Excel actually goes into an indeterminate state and almost all of the @RISK ribbon is gray.

There's a "rescue" built into @RISK, TopRank, and BigPicture as a way around this problem: click the product's Help icon and then select any of the Help menu items. That will cause the ribbon to reset.

Last edited: 2015-10-07

3.25. Borrowing a 5.x License: NLicense Doesn't Display Activation ID

Applies to:
Palisade Concurrent Network releases 5.x

Problem:
I want to borrow a license for off-network use.  As instructed, I copy NLicense.exe from the server to C:\Program Files\Palisade\System on my workstation, and then run the program.  But it opens with only "Enter Activation ID" in the Borrow License box (or it shows an obsolete Activation ID).  How do I make it show the Activation ID so that I don't have to type it in every time?

Response:
You can register the desired Activation ID by making a simple edit to the System Registry.  (Depending on your privilege level on your computer, you may have to get an administrator to do this for you.)

Method A:

  1. Open Notepad or another plain-text editor, and paste in this code, all on one line:
    reg add HKLM\Software\Palisade\network\5000000 /v ActivationID /t REG_SZ /d 99-9999999-ABCDEF-GHI

  2. Change 5000000 to your serial number, and change 99-9999999-ABCDEF-GHI to your Activation ID.

  3. Add a second line, with this command:
    pause

  4. Save the file to your desktop with a .bat extension.  Right-click it and select Run As Administrator.  If asked for permission to change an existing ActivationID, answer Y for yes.

Method B:

  1. Click Start » Run » Regedit.  In the left-hand pane, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Palisade in 64-bit Windows or HKEY_LOCAL_MACHINE\SOFTWARE\Palisade in 32-bit Windows

  2. Double-click on Palisade to expand the folder.

  3. Does a Network key appear under Palisade?  If not, right-click in the blank area in the right-hand pane and create it as a new key.

  4. Double-click on Network in the left pane to expand it.

  5. Now look at your Activation ID. The seven-digit number is your serial number.  Look under Network in the left pane.  Does your serial number appear under Network?  If not, right-click in the blank area in the right-hand pane and create it as a new key.

  6. Double-click the serial number in the left pane.

  7. In the empty part of the right-hand pane, if the value ActivationID does not exist, right-click and select New » String Value (not a new key).  ActivationID is the name of the new value — note the capitalization, and do not put a space before ID.

  8. Double-click on Activation ID in the right-hand pane, and carefully type in your full Activation ID, including the hyphens.

  9. Close Regedit.

Now when you open NLicense and click on your server name in the first box, it will show your Activation ID in the Borrow License box.

last edited: 2012-06-19

4. @RISK for Excel: Simulation

4.1. Progress Window Not Displayed during Simulation

Applies to: @RISK 5.7, 6.x, 7.x

The small progress window is not visible when a simulation is running. The simulation runs properly and results graphs are also displayed properly.

This could be due to a simulation setting, or to the window somehow being moved off screen.

Simulation settings — @RISK 6.2/6.3/7.x:

Beginning with release 6.2, a simulation setting lets you prevent the progress window from appearing during simulation. This setting is stored with the workbook, so possibly this workbook is set to inhibit the progress window.  Open the Simulation Settings dialog, and on the View tab verify that Show Simulation Progress Window is selected.  If it's not selected, select it, click OK, and save the workbook.

Progress window off screen — @RISK 5.7/6.x/7.x:

Beginning with the 5.7 release, the location of the Progress Window is stored in a registry key. It's possible that at some point the Progress Window was moved outside of the visible display area. Deleting the registry key will force @RISK to display the Progress Window in its default, visible location. The steps to take are:

  1. Close all copies of Excel and @RISK.
  2. Launch REGEDIT. This can be done using Start » Run.
  3. Locate the registry key HKEY_CURRENT_USER\Software\Palisade\@RISK for Excel. Click the + sign at the left to expand it, if necessary.
  4. Double-click "7.0", "6.0", or "5.0" for @RISK 7.x, 6.x, or 5.7.
  5. Double-click RiskModel and then Windows.
  6. Right-click on Progress Window and select Delete.
  7. Launch @RISK, open a model, and run a simulation.

The Progress Window should now be visible, and @RISK should remember its position next time.

Last edited: 2015-10-14

4.2. Smart Sensitivity Analysis Occurs Even When Disabled

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

To save time in the simulation startup, I have set Smart Sensitivity Analysis to Disabled. But when I start a simulation, after some other messages in Excel's status line, I see this message:

Smart Sensitivity Analysis: Precedents found for ... of ... @RISK functions, ... of ... for this function. Press Esc to cancel.

Why is Smart Sensitivity Analysis running even though I disabled it?

Do you have any RiskMakeInput( ) functions in your model? RiskMakeInput( ) causes its direct and indirect precedents to be excluded from all sensitivity graphs and reports, whether Smart Sensitivity Analysis is enabled or disabled in Simulation Settings. To know which ones to exclude, @RISK has to trace precedents of each RiskMakeInput( ) function. This precedent tracing uses the same code as Smart Sensitivity Analysis, and that's why you see that notation in the status line.

See also: Excluding an Input from the Sensitivity Tornado

Last edited: 2015-10-16

4.3. Calculation Changed to Manual by a Simulation?

Applies to: @RISK for Excel, all releases

Does @RISK set Excel calculation to Manual? After a simulation I found that my workbook's calculation mode had changed.

It's true that @RISK sets Manual Calculation during a simulation. However, before the simulation @RISK notes the calculation mode, and after the simulation @RISK restores that mode. If you are in Manual Calculation after a simulation, you were in Manual Calculation before the simulation.

For an exception, please see Calculation Changed to Manual while Browsing Results?

In release 5.5, under certain circumstances, an error in the @RISK program did cause it to leave Excel in Manual Calculation after a simulation. This was fixed in release 5.7. Customers with current maintenance contacts are entitled to a free upgrade to the current version of @RISK; please contact your Palisade sales manager for assistance.

Does Excel ever change my calculation mode on its own?

Yes, Excel can silently change the calculation mode in a workbook, so that you don't notice when this happens.

Excel's calculation mode is a global setting but is also stored in each workbook. If the first workbook you open is in Manual Calculation, then all later workbooks opened in that Excel session will also be in Manual Calculation. Any saved workbook will include the current calculation option, with effect the next time you open that workbook in Excel.

Therefore, you should check the calculation mode after opening your workbook(s) but before starting a simulation. In Excel 2007 or newer, click Formulas » Calculation Options. In Excel 2003 or earlier, click Tools » Options » Calculation.

If you find you're in Manual Calculation and you want to be in Automatic Calculation, change it and save every workbook. (You may need to change something in each workbook. Options are not always saved if there were no actual changes to the workbook.)

Last edited: 2017-02-17

4.4. Calculation Changed to Manual while Browsing Results?

I have set Excel calculation to Automatic, but after I ran a simulation I saw that calculation was changed to Manual. The Browse results window is open; does that change calculation mode?

Yes, that's by design. To make browsing work properly, @RISK has to put Excel into Manual calculation mode. If you were in Automatic calculation before Browse Results, you will be in Automatic again when you close that window, or if you change it from a callout to a floating window. (To make that change, click the last icon at the bottom — see illustration.)

Note also that Excel may change calculation mode when you open a workbook, and the change persists even after that workbook is closed. See Calculation Changed to Manual by a Simulation?

Last edited: 2015-06-26

4.5. Multiple CPU -- Only One CPU Runs

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

I have Simulation Settings set to Multiple CPU Enabled, and my computer does have multiple cores, but @RISK uses only one of them. The simulation progress window shows only one CPU; it's just as though @RISK only knows about one CPU on my computer.

@RISK uses a heuristic to guess how long a simulation will take. If @RISK judges that the overhead of starting multiple copies of Excel would outweigh the time saved through parallel processing, it will use only one core even if you have enabled Multiple CPU.

@RISK 6.2.1 and earlier were pretty liberal about making that decision, so a number of short simulations ran in multiple CPUs that actually would have been a bit faster with a single CPU. If you notice that situation, just go into Simulation Settings, change Multiple CPU to Disabled, and save your workbook.

My simulation seems to be taking a long time with a single CPU, and I think it would go faster using multiple CPUs.

First, make sure you have Multiple CPU set to Enabled, on the General tab of Simulation Settings. (This setting is stored in each workbook.) If you do, you can force multiple CPU for all simulations as explained in CPUs Used by @RISK 7.x or CPUs Used by @RISK 4.x–6.x.

My simulation with a project takes a long time, but only one CPU is used.

That is by design. Simulations with Microsoft Project can use only one CPU. However, if @RISK is using the standard engine, you may be able to speed up your simulation by using the accelerated engine. Follow this advice to see if @RISK can use the accelerated engine to simulate this project. (The accelerated engine still uses only one CPU, but on most projects it's significantly faster than the standard engine.)

My simulation used to run in multiple CPUs, but since I upgraded to @RISK 6.3 or newer it uses only one, and the simulation takes longer.

Beginning with 6.3.0, @RISK is more conservative in its estimate, so that some small simulations that used multiple CPUs in earlier versions of @RISK will now run a single CPU. @RISK makes this decision on the basis of how long an Excel recalculation takes. If it seems that your simulations are taking longer with a single CPU, see the System Registry edit in the preceding answer.

I have Simulation Settings set to Multiple CPU Enabled, and my computer does have multiple cores, but @RISK uses only one of them.  The simulation progress window shows all my CPUs, but only one of them actually runs iterations.  The others all say "Excel started".  Then at the end of simulation @RISK hangs and I have to kill those other copies of Excel in Task Manager.

Please check in Excel's disabled items list to see whether any items associated with @RISK have been disabled, particularly RiskSimMultiCpu6.xla or RiskSimMultiCpu7.xla.  (When Excel crashes, it sometimes marks every open add-in as disabled.  The add-in cannot run again until you specifically remove it from the disabled list.)

  • Excel 2010, 2013, or 2016: Click File » Options » Add-Ins.  At the bottom of the right-hand panel, select Manage: Disabled Items, and click Go.
  • Excel 2007: Click the round Office button and then Excel Options » Add-Ins.  At the bottom of the right-hand panel, select Manage: Disabled Items, and click Go.
  • Excel 2003: Click Help » About Microsoft Excel » Disabled Items.

Last edited: 2016-04-15

4.6. Multiple CPU — Blocks of Errors in Simulated Outputs

Applies to: @RISK, all releases

When I disable Multiple CPU, my simulation runs just fine. But when I enable Multiple CPU, the Simulation data window shows blocks of error values in my outputs. For example, I might have numbers for iterations 1–100 and 201–300, but "Error" for iterations 101–200 and 301–400.

There are a few inherent limitations to running multiple CPUs. These come about because a "worker" CPU doesn't have access to the data developed by any other CPU; only the "master" does. During simulation, each worker has a private copy of your workbook. The master tells each worker which iterations to run; the worker runs those iterations and passes the values of @RISK inputs and outputs back to the master. At the end of the simulation, the workers' private copies of the worksheet are destroyed.

If this is your issue, the simplest solution is to go into Simulation Settings and select Multiple CPU: Disabled. If that makes the simulation take too long to run, you're going to have to make some changes in your workbook:

  • If your simulation uses any data from other iterations, or any statistic functions, that information will not be available during simulation, and the iterations done by the worker CPUs will show errors. If the problem is statistic functions that reference @RISK distributions, an easy fix is using the "Theo" functions, which reference the theoretical distributions rather than simulation results: change RiskMean to RiskTheoMean, RiskPtoX to RiskTheoPtoX, and so on. But that's not possible with statistics of @RISK outputs; in that case you must change the logic of your workbook.

  • If you have a macro that stores values in a workbook, and other macro code or worksheet formulas use that stored information in a later iteration, it will not be available to the other CPUs. After the end of the simulation, anything that your macro code wrote to the workbook during iterations run by the master CPU will be in the workbook, but nothing your macro code wrote to the workbook on the worker CPUs will be preserved. If you change your macro to write to an external file, you have to account for contention between multiple copies of the macro trying to write to the same file at the same time. This can be done, but the programming is not trivial.

  • The RISK object model (XDK) is not available on the worker CPUs. If you need to run @RISK automation code (XDK) during a simulation, your only option is to select Multiple CPU: Disabled.

Last edited: 2017-02-07

4.7. Multiple Simulations All Show the Same Data

Applies to: @RISK for Excel 5.0.0 (initial release only)

I'm running multiple simulations, but the Simulation Data report in Excel shows the same data for all of them.

Multiple simulations should have different input data if you tell Excel to use a different random number seed for each simulation, and they should have different output data if the above is true or if you have one or more RiskSimtable( ) functions and later calculations depend on them.

There was a bug in @RISK 5.0.0 that simply duplicates Simulation 1 data for the other simulations in the Simulation data report in Excel. All other graphs and reports are correct. The bug was fixed in @RISK 5.0.1 and never occurred in the @RISK component of The DecisionTools Suite.

If you have @RISK 5.0 initial release (not part of The DecisionTools Suite), please visit palisade.com/Updates to update your software. If you are unable to update your software, here are three alternatives to choose from:

  • Create a separate sheet within your workbook and fill it with RiskData functions. Please see the example in Placing Iteration Data in Worksheet with RiskData( ).

  • If you have many RiskData( ) functions, they may slow down your simulation. As an alternative, you can insert the RiskData functions after the simulation ends, as follows:

    1. Run a simulation.
    2. At end of simulation, in Excel click Insert | Worksheet to insert a blank worksheet.
    3. Highlight (number of iterations per simulation) rows in column A, and type this:
            =RiskData(cell_reference_or_quoted_name_of_input_or_output, 1, COLUMN( ))
      Then press Ctrl-Shift-Enter. The formula will appear in the formula bar with curly braces { }, and the data from simulation #1 will be inserted.
    4. Re-highlight the same cells, and then drag to the right for as many columns as you have simulations. The data from the other simulations will be inserted.
    5. Remember to delete that extra worksheet before running a new simulation, or all those rows and column of RiskData() functions will slow down the simulation.

    If you're handy with VBA programming, you could program a macro to do steps 1-4 automatically at the end of simulation. At the least you could use Excel's Record Macro feature to capture the process as you do it once, and then after that you could run your macro manually.

  • After a simulation, click on the Data icon. The Data window is not the same as the Simulation data report in Excel, and the Data window will bring up the iteration data correctly for all simulations. Then you can highlight them and copy/paste them into your worksheet. This might be a little easier than typing function names.

Additional keywords: Simtable

Last edited: 2013-04-11

4.8. Correlation Matrix from StatTools Not Accepted

Applies to: @RISK for Excel, all releases

I have historical data for several variables that should be correlated. I used StatTools to create a correlation matrix, then copied it into my @RISK model. When I tried to run a simulation, @RISK said the matrix is invalid. What is wrong?

This is due to your data, not an error in StatTools or @RISK. It's common to have some missing data points with historical data, and missing data may lead to a correlation matrix that is not self consistent. (A self-consistent matrix has no negative eigenvalues. For more, please see How @RISK Tests a Correlation Matrix for Validity.)

According to Peter Jäckel, Monte Carlo Methods in Finance (Wiley, 2002), page 60:

Ad hoc correlation matrices, those calculated from incomplete data and those taken from news services, sometimes don't comply with the requirement of symmetry and positive semi-definiteness. ...

In practice, the problem of an invalid correlation matrix, i.e. one that has negative eigenvalues, can also very easily arise in the context of risk analysis for equity portfolios. This is because there are frequently asynchronous gaps in the historical stock exchange time series. The chance that slight inconsistencies in the data from which historical correlation coefficients are calculated can lead to negative eigenvalues grows rapidly as the size of the correlation matrix increases. ... Since equity index or portfolio analysis typically involves many underlying assets, the risk of negative eigenvalues of the correlation matrix calculated from historical data is particularly large.

There are two ways around this:

  • If you have an invalid matrix, you can use RiskCorrectCorrmat( ) to transform it to a valid matrix. You can leave @RISK completely free to make changes, or you can specify adjustment weights for @RISK to use in creating the corrected matrix. Please see How @RISK Adjusts an Invalid Correlation Matrix for details.

  • Or, you can redefine your StatTools data set to include only rows where all variables have data.

But whether the generated correlation matrix is valid or is corrected with RiskCorrectCorrmat( ), you should also apply your own knowledge and judgment to the correlations. There may be factors in the problem you are modeling that make it desirable to specify correlations different from the historical ones.

,

Last edited: 2013-02-24

4.9. Change in Output Mean Inconsistent with Sensitivity Tornado

Applies to:  @RISK 6.x/7.x

Some of my inputs don't appear on the tornado diagram that shows regression coefficients. That makes sense because they have little or no impact on the output. But when I make a Change in Output Mean graph on that output, those inputs do show up with bars. What is wrong?

Most likely there's nothing wrong, and this is just normal statistical variability.

The Change in Output Statistic tornado does not measure the influence of any input on the output. The numbers are purely statistics, based on two parts of the simulation. One end of the bar is the mean of the output values from the iterations with the lowest 10% of input values, and the other end is the mean of the output values from the iterations with the highest 10% of input values.  (For more on how the numbers are computed, please see Interpreting Change in Output Statistic in Tornado Graphs.)

Think of those two groups of iterations as two smaller samples from the simulation. Even if this input has zero impact on the output, you'd expect some difference between the means of two sub-samples from the same simulation. If you look at the standard error of the output (standard deviation divided by the square root of the number of iterations), you should see that the size of these unexpected bars is within a couple of standard errors, meaning that it can be explained by random chance and is not significant.  If the difference is more than a couple of standard errors, then it is significant and may indicate impact of that input on the output.

My input does have some impact on the output, but it is minor. The numbers on the two ends of the bars are too far apart to be explained by statistical variation.

Remember, the Change in Output mean tornado doesn't measure impact. (For that, you want the regression coefficients tornado; see Interpreting Regression Coefficients in Tornado Graphs.) This input could have low impact on the output, as you say, but if it's correlated with other inputs, the output would be affected to a greater degree by the combination of those inputs.

Last edited: 2016-08-29

4.10. Same Input Appears Twice in Tornado Graph

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

In my tornado graph, I see that two of the bars have the same label. Why is this happening, and how can I fix it?

This occurs because you have two inputs with the same name. This can happen in several ways. You might have actually assigned the same name to both inputs. More likely, you didn't assign names to the two inputs, and @RISK gave them default names based on nearby text.

To solve the problem, open the Model Window and find the inputs with duplicate names. Click in the Name column for one or both of them, and enter the desired name.

Are the same-named inputs in the same cell? In that case, you might actually want to combine them. Here are some guidelines:

  • Are you modeling a risk that may or may not occur, with a range of possible severities? You might have a formula like
    =RiskBernoulli(0.4)*RiskTriang(10,25,40)
    or
    =IF(RiskBinomial(1,0.4)=1, RiskTriang(10,25,40), 0)
    (It could be any continuous distribution, not just RiskTriang.) To model a maybe-yes-maybe-no risk, RiskCompound is a better choice:
    =RiskCompound(RiskBernoulli(0.4),RiskTriang(10,25,40))
    The RiskCompound counts as one input, not three, so it simplifies your tornado graphs. Using a different discrete distribution in RiskCompound models risks that may occur multiple times, as explained in Combining Probability and Impact (Frequency and Severity).

  • Do you have some other formula where you want the tornado chart to use the formula result, not the individual distributions? In that case, wrap the formula in a RiskMakeInput, like this:
    =RiskMakeInput( formula, RiskName(inputname))
    See Combining Inputs in a Sensitivity Tornado.

last edited: 2016-12-16

4.11. Tornado Graph Is Missing an Input

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

My tornado graph doesn't show a particular input, even though I can see from the formulas that it is a precedent of this output. Why?

There are several possible reasons this could happen.

Are other, more significant inputs crowding out this one? Tornado graphs can only show a limited number of bars, and naturally they show the inputs with the greatest effect on this output (or the greatest correlation to it). See Tornado Graph — How to Set Defaults to find out how to increase the number of bars. If you're already at the maximum, see Placing Change in Output Statistics in Worksheet or Regression Coefficients in Your Worksheet to compute the sensitivity numbers in worksheet functions.

Is the input not being collected? In Simulation Settings, on the Sampling tab, have you set Collect Distribution Samples to Inputs Marked with Collect? In that case, only the inputs that you have marked for collection in the Model Window, or with a RiskCollect property function, can appear in any tornado chart.

Is a RiskMakeInput function excluding this input? When you wrap a formula in a RiskMakeInput function, then all tornado charts exclude any inputs in that formula, as well as all cells referenced in that formula, and all precedents of those cells. Please see Excluding an Input from the Sensitivity Tornado and Combining Inputs in a Sensitivity Tornado for more about how RiskMakeInput works.

Last edited: 2016-06-21

4.12. Convergence by Standard Deviation: Always Same Number of Iterations

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

When I select "auto" for number of iterations, and my test for convergence is on standard deviation, no matter the characteristics of my model it always converges at 2200 iterations. Even if it's just a uniform distribution designated as an output, converging on the standard deviation still takes 2200 iterations. Why is that?

If I enable multiple CPU, the convergence generally takes a few hundred iterations longer. Why?

Surprising though it may be, this result is correct. It has to do with the interaction of the confidence interval for the standard deviation with @RISK's method of testing convergence.

How does @RISK test convergence? The default is to test every 100 iterations for a 95% confidence level on a tolerance of ±3%, so let's work with that. Every 100 iterations, @RISK takes the current simulated statistic — mean, standard deviation, or percentile, whichever one you chose — subtracts 3% from it to get L, adds 3% to it to get U, and then figures the cumulative probability between L and U. If

cumulative probability between L and U ≥ 95%

then you are at least 95% confident that the true value is between L and U. In other words, your mean, standard deviation, or percentile has converged at the 95% confidence level.

But how does @RISK find the cumulative probability when testing for convergence of the standard deviation? A confidence interval for standard deviation is computed from a confidence interval for variance, which uses the χ² distribution. Therefore, to test convergence of the simulated standard deviation, @RISK actually tests convergence of the variance. After n iterations, the current simulated standard deviation is s and the simulated variance is s². The bounds for variance are therefore

L = (0.97s)² = 0.9409s²    and    U = (1.03s)² = 1.0609s²

But here's the surprise: to place a value on the χ² curve, you divide (n-1)s² by that value. Recall the requirement for convergence: the cumulative probability between L and U must be ≥ 95%. Using the χ² distribution, that translates to

cum. prob. of χ² with df=n−1 between (n-1)s²/1.0609s² and (n-1)s²/0.9409s²   ≥   95%

(L and U have traded places, because 1/1.0609 is smaller than 1/0.9409.)  The s² in the fractions cancel out:

cum. prob. of χ² with df=n−1 between (n−1)/1.0609 and (n−1)/0.9409   ≥   95%

This is an inequality in just one variable: n, the number of iterations. It's completely independent of the estimated standard deviation and of the underlying distribution you're simulating. (The tolerance comes into the .9409 and 1.0609 coefficients, and the confidence level is the number on the right-hand side of the inequality.)

Solving the inequality gives n ≥ 2140: to converge to within ±3% with 95% confidence takes 2140 iterations. You can do similar calculations for any other convergence tolerance or confidence level.

Why 2200 iterations, then? The default is to test for convergence every 100 iterations, and the first multiple of 100 iterations ≥ 2140 is 2200.

Why are more iterations needed with multiple CPUs? The master CPU does the convergence testing, based on iteration values it gets from the worker CPUs. If the workers are doing 1000-iteration blocks, for example, then convergence can't be tested more often than every 1000 iterations, and @RISK will report convergence at 3330 iterations.

Why doesn't this happen when means and percentiles are tested for convergence? Because the confidence intervals for means and percentiles don't involve the χ² distribution, and therefore convergence does depend on the progressive estimates of the mean or percentile. It(#rsq#)s only for standard deviation or variance that convergence depends purely on number of iterations.

If you have versions of @RISK 6 before 6.2, you will find that convergence to 3% tolerance with 95% confidence takes 8547 iterations, not 2140. Those versions of @RISK were testing for a ±3% tolerance in variance, not standard deviation. The actual tolerance for standard deviation was about 1.5%, which needed more iterations. You may want to upgrade your software to the current version if you have an earlier version.

Last edited: 2015-10-14

4.13. Missing Results Graph

Applies to: @RISK 7.5.1, possibly some earlier releases also

After a simulation, I don't get a results graph. Instead, the graph area is full of a gray rectangle, with a white rectangle in the upper left.

Or:

The results graph appears, but I can't move the delimiters or change the percentages at the top.

Or:

The results graph appears, but there's no statistics grid and the drop-down arrow to let me select the grid does not appear at the upper right of the window.

Or:

The Define Distributions window freezes when I select a distribution.

These symptoms all have the same underlying cause: @RISK is trying to access a .NET 2 file that does not exist but is still registered. The cure is to re-register your .NET  4, by following these steps:

  1. Close all open copies of Excel.

  2. Open an administrative command prompt—here are directions in case you need them.

  3. You'll need to copy/paste two commands to the administrative command prompt, one command at a time. To copy a command, highlight the entire command with your mouse and press Ctrl+C. To paste the command, right-click into the administrative command prompt, select Paste with the mouse, and press the Enter key on your keyboard.

    • If you have 64-bit Windows, with either 32-bit Excel or 64-bit Excel, copy/paste this command:
      C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe "c:\Program Files (x86)\Palisade\System\Palisade.DecisionTools.Graphing7.dll" /u

      Then copy/paste this command:
      C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe "c:\Program Files (x86)\Palisade\System\Palisade.DecisionTools.Graphing7.dll" /codebase /tlb

    • If you have 32-bit Windows, copy/paste this command:
      C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe "c:\Program Files\Palisade\System\Palisade.DecisionTools.Graphing7.dll" /u

      Then copy/paste this command:
      C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe "c:\Program Files\Palisade\System\Palisade.DecisionTools.Graphing7.dll" /codebase /tlb

  4. The command prompt window will show some output, which should include "Types registered successfully" and "type library was registered successfully". Take a screen shot of the output, to be sent to us if you don't see those messages in the output, or if the fix doesn't work.

  5. Run @RISK, and you should see that the original problem has been resolved.

  6. If @RISK still does not run correctly, verify that .NET Framework 4 is enabled. In Windows XP through 7, Control Panel » Programs and Features; in Windows 8 and 10, Control Panel » Programs and Features » Turn Windows Features On or Off.

  7. If @RISK still does not run correctly, run the Microsoft .NET Framework Repair Tool.

Last edited: 2017-04-22

4.14. Can't Move Delimiters or Change Percentages

Applies to: @RISK 7.5.1, possibly some earlier releases also

The delimiters divide my graph into three regions based on percentages that are shown above the graph. I want to change the percentages, but nothing happens when I click on the numbers or when I try to move the delimiters with my mouse.

There is a problem with your registration of .NET 4. Please follow the procedure in Missing Results Graph to fix this.

Last edited: 2017-03-31

4.15. Restoring Theoretical Distribution in a Results Graph

Applies to: @RISK 6.x/7.x

After my simulation, I was looking at an input distribution in Browse Results.  It showed the theoretical distribution curve as an overlay on the histogram of simulated data.  In Graph Options » Curves, I clicked the theoretical distribution and clicked Remove Curve to work with just the sample data for a while.  How can I recover that theoretical curve as an overlay?

Click the Edit and Export icon at the bottom of the Browse Results window, and then Reset Graph to Defaults.  All customizations will be removed.  You will need to redo any other customizations you did on this graph, but you will have both the sample data and the theoretical curve.

Reset Graph to Defaults menu selection

Additional keywords: Bring back a deleted curv

Last edited: 2015-10-14

4.16. Sum of Percentiles Differs from Percentile of the Sum

Applies to: @RISK, all releases

In my model, I have a set of inputs. I strike a sum, and that is my output. But I also compute the 95th percentiles of the inputs and the 95th percentile of the output using RiskPercentile( ) or RiskPtoX( ). Why does a percentile of the output not equal the sum of that percentile of the inputs?

This is normal behavior. Unless your inputs are correlated with a coefficient of 1, they won't all be at a given percentile in the same iteration. In most iterations, some inputs will be above any particular percentile and some will be below. When you add them all up, the highs and lows tend to balance out, so the 95th percentile of the sum will be closer to the mean than the sum of the 95th percentiles of the inputs.

It's not just percentiles — any statistic will have a similar issue. This is a statistical feature of combining probability distributions, and not any kind of problem in @RISK or in your model.

For a related issue, see Static Value of Output Differs from Simulated Mean.

Additional keywords: Maximum of sum doesn't equal sum of maximums; Minimum of sum doesn't equal sum of minimums

Last edited: 2015-07-22

4.17. "Error!" or #QNAN for Distributions in an IF( ) Function

Applies to: @RISK For Excel 3.5 and newer

In Simulation Data, for some distributions "Error!" is displayed instead of a value. These distributions are used in Excel IF( ) functions, where the distribution functions are sampled or not based on whether the condition is true or false.

The Simulation Data window or report shows the values of the distributions, not the value of the complete cell formula.

"Error!" Is reported for the iterations in which the distribution function was not sampled because the condition that would have triggered its sampling did not occur. The Error! reported for the input pertains only to the separate @RISK distribution function itself. It does not pertain to the entire contents of the cell containing the IF formula. If you want to see the results of calculations from the entire cell, wrap the formula in a RiskMakeInput( ) function if you have @RISK 5.0 or later, or select the cell as an @RISK output.

If you want to see the results of the distribution function separately, but don't want to see any errors reported, you can place the distribution functions in cells all by themselves, and then use cell references to refer to them in the IF( ) functions. But be aware that doing so can throw off the results of a sensitivity analysis, because then you have @RISK distribution functions that are always sampled, but which don't really figure into the calculation of the entire model in those iterations when condition in the IF statement does not call them.

If your objective is merely to hide the "errors", you can set the Collect Distribution Samples option to None, or set it to Inputs Marked with Collect and then don't mark those particular distribution functions for collection, or filter on errors.

Last edited: 2012-11-12

4.18. Reports Do Not Appear after Simulation

Applies to: @RISK, release 6.1.2 only

After a simulation, I can't get Simulation Data or Detailed Statistics reports to appear in Excel.

Please check your simulation settings. On the Sampling tab, do you have Collect Distribution Samples set to None? Or do you have it set to Inputs Marked with Collect, but you haven't actually marked any inputs or collection? Or does your simulation not actually contain any @RISK input distributions?

Under any of those circumstances, an error in @RISK 6.1.2 prevented it from producing certain reports. The problem was fixed in @RISK 6.2.0. If you are eligible, upgrade your @RISK to the current release. If you can't upgrade, you can work around the problem by ensuring that you have at least one input distribution and setting Collect Distribution Samples to All.

Last edited: 2017-02-17

4.19. Delimiter Setting Ignored by RiskResultsGraph( )

Applies to: @RISK 5.0 and newer

I have a RiskResultsGraph( ) function set up as follows, because I want to set the left delimiter at 20%:

=RiskResultsGraph(F26,H6:Q25,13,FALSE,20)

But after a simulation, the graph still has the left delimiter at 5%.

RiskResultsGraph( ) is applying the defaults that are in your Application Settings, because the function parameters are not complete.

With RiskResultsGraph( ), you must specify both delimiters if you want to change either one. If you want 20% at the left and 5% at the right, use this form of the function:

=RiskResultsGraph(F26,H6:Q25,13,FALSE,20,5)

Last edited: 2015-09-16

4.20. Min or Max Setting Ignored by RiskResultsGraph( )

Applies to: @RISK 5.0 and newer

I have a RiskResultsGraph( ) function set up as follows, because I want to set the left edge of the graph at –10:

=RiskResultsGraph(A1,B4:M30,0,,5,90,-10)

But after a simulation, the graph still shows same x axis as before.

With RiskResultsGraph( ), you must specify both Min and Max, or neither. Supply a Max value in addition to your Min value, and the graph will appear as you wish.

Last edited: 2015-09-18

4.21. Template Report Contains Formulas in Place of Numbers

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

I have template reports defined. After a simulation, I expect the generated reports to contain fixed numbers, but instead they contain formulas.

This situation can arise when you have filters defined in your template. The problem comes from a limitation of Excel's copy/paste, which @RISK uses: When @RISK tries to copy/paste a sheet that contains filters, Excel raises an error to the effect that the source and target aren't the same size.

Here are some possible workarounds:

  • If you don't need the filter, remove it.
  • Let the report be created as it is now. Then, select the actual data area of the report (not the template), press Ctrl+C for Copy, then Edit » Paste Special » Values into an empty sheet. Excel won't paste the filtered-out rows.
  • You might try automating the Advanced selection in Excel filters by using its option, "copy to another location".

Last edited: 2015-08-07

4.22. Unwanted Results Summary Window Appears

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

In Simulation Settings » View, I have selected None. But when I start a simulation, the Results Summary window appears anyway.

Do you have convergence monitoring enabled? (This is on the Convergence tab of Simulation Settings.) By design, when convergence monitoring is enabled, @RISK displays the Results Summary window during simulation so that you can monitor the progress of the simulation toward convergence. Please see Status Column of Output Results Summary Report to interpret the status column.

Last edited: 2015-10-14

4.23. Simulation Used to Run, Now Crashes Excel

Applies to: @RISK 6.1, 6.2, 6.3, 7.0 in 32-bit Excel 2013 or 2016

My simulation used to run okay, but now the same file crashes Excel during simulation.

If you're running 64-bit Excel, or Excel 2010 or earlier, this article does not apply to you. (Which Version of Excel Am I Running? guides you to find your Excel version and whether it's 32-bit or 64-bit; the same screen should show you the build number.)

In June 2016, Microsoft updated 32-bit Excel 2013 and 2016 to make them "large address aware". (For more about the update, see the starred note at the end of Should I Install 64-bit Excel?) @RISK 7.0 and earlier cannot run large simulations correctly with this update in place.

To see if you have the update, check your Excel build number. If your build number in Excel 2013 is 15.0.4833.1000 or higher, or your build number in Excel 2016 is 16.0.4390.1000 or higher, then you have the update. In that case you should upgrade your @RISK or DecisionTools Suite to our latest version, which has new programming to accommodate this change by Microsoft. If you have a lower build than those, then something else is the cause; see "Out of Memory" for a starting point.

Last edited: 2016-08-12

4.24. "An exception of unknown type has occurred."

Applies to: @RISK for Excel

When I try to run a simulation, I get the message

An exception of unknown type has occurred.

What is wrong, and how do I fix it?

There are several possible problems, so let's start with the most likely ones before we look at more complicated possibilities.

First, does this happen with only one particular workbook? For example, can you simulate one of our examples successfully? (Click Help »  Example Spreadsheets.) If it's only a particular workbook, please email it to us at support@palisade.com and we'll have a look.

On the other hand, if you also get the error with other workbooks then it is likely to be a configuration problem.

You should not manually add any of our libraries or toolbars to Excel. If you have done that, please remove them, close Excel, and then run @RISK in the recommended way: click the Windows Start button, then Programs or All Programs, then Palisade DecisionTools, then @RISK for Excel.

You may have some other add-ins that are incompatible, or you may have macro files or template files that are incompatible. Please see the appropriate article for help in diagnosing startup conflicts:
Find and Fix Startup Conflicts (Excel 2007–2016)
Find and Fix Startup Conflicts (Excel 2003 and Earlier)

Last edited: 2015-01-05

4.25. "Authorization failure" When Simulating

Applies to:
@RISK 4.5 For Excel with Excel 2003 or earlier

Problem:
When I click on @RISK's simulate button, it returns the error message "Authorization Failure". What is wrong?

Response:
This occurs if you add the @RISK and/or DecisionTools Suite toolbar(s) with Excel's View » Toolbars instead of launching the program. All toolbar buttons seem to operate except for the simulate button which will return the "Authorization Failure" message when clicked. The reason is that adding the toolbar under the view menu does not initialize @RISK properly.

To correct the problem, always start @RISK from the start menu: click the Windows Start button, then Programs or All Programs, then Palisade DecisionTools, then @RISK 4.5 for Excel. (Excel will start automatically if it's not already running.) This is our recommended procedure.

We do not recommend manually adding our toolbars or add-ins to Excel.

last edited: 2012-12-07

4.26. "Exception of type PalPipeError"

Applies to: @RISK 6.0.1

When I run a larger simulation with multiple CPU enabled, @RISK uses only one CPU. Performance Monitor shows the master CPU as green, but the worker(s) as red with a status of "Exception of type PalPipeError in method ParallelSimMsgPipe::Transact". What is wrong?

The copies of @RISK 6.0.1 and The DecisionTools Suite 6.0.1 that were available for download between 15 Oct and 24 Oct 2012 contained an error in the way the worker CPUs are controlled. If you downloaded the software before 15 Oct or after 24 Oct 2012, your copy is not affected.  No other release numbers are affected.

To solve this problem, download and install a fresh copy of @RISK or The DecisionTools Suite. If you need a download link, please contact Technical Support and include your serial number or Activation ID.

Install the downloaded program right over the existing copy of @RISK or The DecisionTools Suite (requires full administrative rights). If the installer prompts you for permission to perform an upgrade, click Yes.

Last edited: 2013-04-25

4.27. "Exception of type PalSystemError" (@RISK 5.0)

Applies to:
@RISK and The DecisionTools Suite, Industrial Edition 5.0 only

Problem:
I have multiple CPU support enabled in @RISK 5.0, but only one CPU is used and the Performance Monitor shows "Exception of type PalSystemError in me.." for the other CPUs.

Response:
@RISK is having a problem starting the additional CPUs This problem has been corrected in later releases of the software.

Please contact your Palisade sales manager to obtain the latest release. If your maintenance is current, the latest release is available to you at no charge.

last edited: 2012-07-25

4.28. "The formula ... could not be correctly parsed"

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

At the start of simulation, I get the error message "The formula formula could not be correctly parsed", or "The formula formula, from cellreference, could not be correctly parsed."

@RISK 5.0 introduced a feature called Smart Sensitivity Analysis, also known as precedent checking.

As @RISK traces back from your @RISK outputs to your distribution functions, along the way it may find an Excel formula that it doesn't know how to interpret, such as one containing an Excel INDIRECT( ) function. (See Precedent Checking (Smart Sensitivity Analysis) for the complete list of formulas that Smart Sensitivity Analysis cannot handle.)

You can disable Smart Sensitivity Analysis for this model and revert to the @RISK 4.5 style of sensitivity analysis so that the simulation will proceed. To do this, click the Simulation Settings icon, select the Sampling tab, and change Smart Sensitivity Analysis to Disabled. Click OK and save the workbook.

The choice of enabling or disabling Smart Sensitivity Analysis can be made for each workbook, and you can also set it in Application Settings to apply to new models. These settings are available in @RISK 5.0.1 and above and in all releases of @RISK in The DecisionTools Suite 5.x. If you do not have this choice, please click Help » About @RISK to verify that you have @RISK 5.0.0, and in that case please visit palisade.com/Updates to request an update to our current version.

Last edited: 2015-10-14

4.29. "Found invalid formula ... Continue without detecting RiskMakeInput precedents properly?"

Applies to: @RISK 6.x/7.x

When I click Start Simulation, I get the message

Found invalid formula "..." in "...". Continue without detecting RiskMakeInput precedents properly?

Or,

The reference "..." in "..." has an OFFSET or INDIRECT, whose precedents cannot be traced. Continue without detecting RiskMakeInput precedents properly?

What is wrong, and how do I fix it?

This is a similar issue to the message "Found invalid formula ... Continue without Smart Sensitivity Analysis?", but it is detected at a different point.

The RiskMakeInput( ) function lets you make any formula behave like an @RISK input. Then in sensitivity analysis the tornado diagrams show sensitivity of the outputs to the value of this formula as a whole, not to any components of the formula and not to any precedents of the formula. At the start of a simulation, @RISK catalogs all distributions that are used only as precedents or components of a RiskMakeInput( ), so that it will know to exclude them from sensitivity analysis after the simulation. If @RISK can't interpret a formula, it won't be able to detect those precedents properly.

The cure is to change the referenced formula to one that @RISK can interpret; see the list and hints in the article referenced above. There is no @RISK setting to ignore RiskMakeInput( ) precedent checking, as there is with Smart Sensitivity Analysis. If you can't change the formula, you'll need to click Yes each time you run a simulation.

Last edited: 2015-10-14

4.30. "Found invalid formula ... Continue without Smart Sensitivity Analysis?"

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

When I start a simulation, I get the error message

Found invalid formula ... Continue without Smart Sensitivity Analysis?

Or,

The reference '...' in '...' has an OFFSET or INDIRECT, whose precedents cannot be traced.
Continue without Smart Sensitivity Analysis?

Smart Sensitivity Analysis was introduced in @RISK 5.0. It's described in the article Precedent Checking.

As @RISK traces back from your @RISK outputs to your distribution functions, along the way it may find an invalid Excel formula. You should fix the formula, using Excel's Find feature to locate it if necessary, and re-run your simulation.  (Instead of Find, you can use the location given just before "has an OFFSET".  That will be either a cell reference or a defined name; you can access defined names in Excel through Formulas » Name Manager (in Excel 2003 and below, Insert » Name » Define).

Certain formulas are correct Excel formulas, but Smart Sensitivity Analysis cannot work with them. Please see Precedent Checking (Smart Sensitivity Analysis) for the list.  If the message identifies one of these formulas, either change the formula (if possible) or disable Smart Sensitivity Analysis on the Sampling tab of Simulation Settings.  If the formula is actually correct, and does not fall in any of those categories, please contact Technical Support at support@palisade.com.

The choice of enabling or disabling Smart Sensitivity Analysis can be made for each workbook, and you can also set it in Application Settings to apply to new models.

These settings are available in @RISK 5.0.1 and above and in all releases of @RISK in The DecisionTools Suite 5.x. If you have @RISK 5.0.0, Smart Sensitivity Analysis is always enabled. You can upgrade to the currentr version to gain many other features as well as the ability to control Smart Sensitivity Analysis. Please visit http://www.palisade.com/Updates/ or contact your Palisade sales manager to request an update to the latest version of @RISK.

See also:
The RiskMakeInput function is treated as a special case, and the above technique will not work for it.  See "Found invalid formula ... Continue without detecting RiskMakeInput precedents properly?"

Last edited: 2017-02-17

4.31. "GetPassword cannot be found."

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

When I try to run a simulation with multiple CPUs, this message pops up:

The macro "...!GetPassword" cannot be found.

with my workbook name in the double quotes. What is GetPassword?

When your workbook has a password, the extra CPUs don't know the password and therefore they can't open the workbook to perform their assigned iterations. They look for a macro called GetPassword to tell them the password.

To solve the problem:

  1. Press Alt-F11 to open the Visual Basic editor.

  2. Press Ctrl-R to open the Project Browser. (If it's already open, the screen won't change when you press Ctrl-R.)

  3. Find your workbook name, such as "VBA Project (PhoneLog.xls)" and expand it by clicking the plus signs at the left till you get to Modules. If you have a Modules entry, click the plus sign if necessary to show the names of the individual modules, then jump to step 5.

  4. If you don't have a Modules entry, right-click on the VBAProject line item for your workbook and then select Insert » Module.

  5. Double-click on Module 1 (or any module name) and you should see a code window with (General) and (Declarations) or similar at the top. Click into the code window, scroll down to the bottom if necessary, insert a blank line and then paste this code:

        Function GetPassword() As String
            GetPassword = "I am the password for this workbook"
        End Function
  6. Change "I am the password for this workbook" to the actual password, keeping the double quotes.

  7. Click any other line in the same window, then in the menu click Debug » Compile Project to make sure that your code was inserted correctly.

  8. Close the VBA window and save your workbook.

In @RISK 5.5.1, make sure that the name of the workbook file (.XLS or .XLSM file) does not contain spaces or special characters such as parentheses. @RISK 5.5.1 will not be able to find the GetPassword macro if the name of the workbook contains these characters.

Last edited: 2015-10-15

4.32. "Method '~' of object '~' failed" (in Simulation)

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

During a simulation, I get a crash with the message

Method '~' of object '~' failed

What is wrong, and how do I fix it?

If this happens with a large model but not with our examples, you may not have enough memory to run your simulation. Try running it in 64-bit Excel, and see if it works. You can also try the techniques in Memory Used by @RISK Simulations to determine about how much memory the model requires.

This can also be caused by inappropriate COM type library registrations. See Removing Outdated References to Office from the System Registry for instructions on removing the references.

See also:

Last edited: 2016-05-13

4.33. "No inputs found that affect this output."

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

I run a simulation and everything seems fine. But when I look at Quick Reports, or when I do Browse Results and ask for a tornado, I see only this message:

No inputs found that affect this output.

Is your output actually varying, or does it have the same value in every iteration?

If your output is varying, but @RISK finds no inputs that influence it, you may have told @RISK to discard input data. In Simulation Settings » Sampling, look at Collect Distribution Samples. If it's set to None or Inputs Marked with Collect, change it to All and rerun your simulation.

If your output has precedents that include Excel volatile functions like RAND( ), it will vary but @RISK won't find any inputs. @RISK considers only @RISK distributions to be inputs. Replace RAND( ) with RiskUniform(0,1).

On the other hand, if your output isn't actually varying, then you need to take a look at the logic of your model. Maybe you started from a deterministic model, and you haven't yet changed the constants to @RISK inputs (probability distributions). Use Excel precedent tracing, on the Formulas tab, to find the precedents of your output.

Here's a good technique for testing your model when you're not getting the kind of variation you expect. Activate the Random/Static icon (the "rolling dice" icon), then press F9 repeatedly to have @RISK draw new random numbers for all distribution. If a cell isn't varying the way you think it should, look at that cell and its precedents to check the logic of your model.

Last edited: 2015-09-11

4.34. "No values to graph" Message / All Errors in Simulation Data

Applies to: @RISK for Excel 5.5.0 and newer

When I run my model, Browse Results shows "There are no data values to graph" for my outputs. If I look in the Simulation Data window, it shows "Error" in every row. What is wrong?

There could be two causes. If this is a legacy model from @RISK 5.0 or later, see My model worked just fine in @RISK 5.0 (or 4.5), below.

If you created this model for @RISK 5.5 or later, it's more likely that you have a logic error in your model. You can use "shoeprint mode" or "footprint mode" to find the error. Open the Simulation Data window (small x-subscript-i icon in the Results section of the ribbon), and then proceed as in the article Some Iterations Show Error in Data Window. What Can I Do?

My situation is similar, but Simulation Data shows "Filtered" on every row, not "Error".

You have a filter defined, and its specifications cause every value of this output to be screened out.

Look at the Define Filters button, near the middle of the @RISK ribbon. If a filter is active, the button has a colored background. Click the button, and if you wish you can edit the filter settings or simply remove the check mark from the box next to Enable Filters for Simulation Results.

If you're editing filters, you may wonder about the Type column. A Standard filter affects only that particular input or output. An Iteration filter uses the values or percentiles of that input or output as a criterion, but when the Iteration filter rules out any particular iteration of this input or output, @RISK also rules out the same iteration of all other inputs and outputs.

My model worked just fine in @RISK 5.0 (or 4.5). But when I run it in 5.5 or later, I get "There are no data values to graph" for my outputs, or the Simulation Data window shows "Error" in every row. What is wrong?

Are you using RiskPercentile, RiskMean, or other statistic functions? These behave differently in 5.5 and later from how they behaved in 5.0 and earlier (including 4.5).

In the earlier versions, @RISK statistic functions like RiskMean and RiskPercentile were evaluated during every iteration. This created three problems. First, for iterations 1 through N-1, the values were wrong because they were computed only on the iterations available so far. Second, and related, the values changed as each additional iteration was run, which was generally not what users wanted or expected. Third, computing all these extra values slowed down the simulation.

Beginning with 5.5, by default the statistic functions are computed only once, at the end of the simulation. This can make a dramatic speed improvement, and it also makes logical sense because the means and percentiles and such aren't known until all iterations have been computed. However, in a few models this reveals a problem that existed all along, but that users were unaware of: trying to use a value (such as a simulated percentile or mean) before the final value was available.

If your model relies on the old behavior, and you actually want to recompute the statistics in each iteration, you can make @RISK behave like the older versions. In Simulation Settings, on the Sampling tab, change "Update Statistic Functions" from "at the end of each simulation" to "each iteration". If you make that change, so that @RISK 5.5,–7.x behaves like 4.5 and 5.0, please bear in mind that this may let your model run at the expense of papering over a real problem. Any formula that refers to a percentile, a mean or another simulated statistic function would get a different value at each iteration. Especially in the earlier iterations, it would be quite volatile.

To get statistics of input distributions, the better method is to use RiskTheoPercentile or RiskTheoMean or similar, rather than RiskPercentile or RiskMean. If you're interested in statistics of an input distribution, a better procedure is to use the "Theo" functions. See Statistics for an Input Distribution. But if you're taking percentiles or means of an output, they cannot be known in advance and your solution is either to change Simulation Settings as mentioned above, or to re-examine the logic of your model.

Last edited: 2017-02-23

4.35. "Non-modal forms cannot be displayed in this host application from an ActiveX DLL, ActiveX control, or Property Page."

Applies to: @RISK 7.x

When I click Start Simulation, I get this message:

Non-modal forms cannot be displayed in this host application from an ActiveX DLL, ActiveX control, or Property Page.

You have an active add-in that is incompatible with @RISK. There may be multiple add-ins that cause this problem, but so far we have seen only one.

The Laserfiche client software component called "Laserfiche Office Integration 8.3" is known to be incompatible with @RISK. It contains Office plugins that prevent @RISK from bringing up some windows. Those plugins can't be disabled from within Excel, but that component must be uninstalled by using the Laserfiche installer.

Other add-ins, or other versions of Laserfiche, may also have this issue; only Laserfiche 8.3 is confirmed at this time.

Last edited: 2017-05-03

4.36. "Not enough memory to run simulation"

Applies to: @RISK 5.x and newer

With multiple CPU enabled, when I run a simulation the Performance Monitor displays the error message "Not enough memory to run simulation". What is wrong, and how can I fix it?

The simulation is not able to allocate the memory it needs to run the simulation. This is probably not a problem with physical RAM, but with virtual memory. Please see Virtual Memory Settings for guidelines, and instructions on changing the settings.

Here are some additional possibilities:

  • Disk free space — Virtual memory uses the free space on your hard drive, so make sure that is not constrained. You may want to use the CLEANMGR program (part of Windows) to remove temporary files: click Start » Run, type CLEANMGR and click OK. If you clear out files manually, remember to empty the Recycle Bin.

  • Smart Sensitivity Analysis — If your Excel file is many megabytes in size, precedent tracing (Smart Sensitivity Analysis) may actually exceed the available memory. Try turning off Smart Sensitivity Analysis on the Sampling tab of Simulation Settings.

  • 64-bit Excel — For most people, 32-bit Excel is just fine. But 32-bit Excel is limited to a 2 GB memory space, regardless of how much physical RAM you have. If you have a really large simulation, you may need 64-bit Excel. One symptom would be a simulation that runs with a modest number of iterations but gets "Not enough memory to run simulation" when you specify a large number of iterations. See also: Should I Install 64-bit Excel?

See also: "Out of memory" gives more suggestions for reducing memory use.

Last edited: 2015-02-27

4.37. "Object initialized twice" When Launching Palisade Software

Applies to: All releases of Palisade's Excel add-ins

The software runs just fine in one instance of Excel, and I can open multiple workbooks in that instance. But when I open a second instance of Excel, I get this message:

Object initialized twice.

This happens either right when Excel opens, or when the second Excel is already open and I try to launch Palisade software.

Palisade software is not designed to run simultaneously in multiple instances of Excel. This is true whether they're the same product or different products, whether they're the same release or different releases. And it doesn't matter whether you use the desktop icon or Start Menu to launch the software, or open the XLA-type add-in file manually. You can run multiple products of the same release in the same instance of Excel.)

If you launch @RISK a second time from the icon or Start Menu, you should get "@RISK is already running", and similarly for the other products, but the already-running copy should not be affected.

But all I did was launch a second instance of Excel, and I got "Object initialized twice."

Most likely you have one or more Palisade add-ins listed as active add-ins in Excel, which means that they load every time Excel loads. This is a conflict situation, and may result in data loss.

  1. Close both instances of Excel. If you've done any edits in the first-opened one, consider saving that workbook under a different name so that you can check it later.

  2. Open one instance of Excel, with a blank workbook. In Excel 2010 or 2013, 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. Remove the check marks from all Palisade add-ins. Click OK, and close Excel.

For the future, use the desktop icons (if present) or the Start Menu's program group called Palisade DecisionTools to open Palisade software. You can do this before or after opening Excel.

See also: Opening Palisade Software Automatically Whenever Excel Opens

Last edited: 2015-01-29

4.38. "Object initialized twice" at End of Simulation

Applies to: @RISK 6.0 and @RISK 6.1 Preview in 64-bit Excel

At the end of simulation, I see a pop-up with the message

Object initialized twice

Or, Excel seems to freeze at the end of simulation, but I see in the Windows taskbar that there are multiple instances of Excel open, and when I move the main Excel window I see that one or more "Object initialized twice" errors were hidden behind Excel.

This is the same problem in 64-bit Excel as the "Type mismatch" at End of Simulation in 32-bit Excel. Please follow the directions in that article to prevent the error.

Last edited: 2013-01-25

4.39. "Open method of Workbooks class failed"

Applies to:
@RISK 5.x under Excel 2007

Problem:
I have multiple CPUs enabled. When I try to run a simulation, the @RISK Performance Monitor crashes with the message "Open method of Workbooks class failed". What is wrong?

Response:
Sometimes there are problems with the XML format introduced in Microsoft Excel 2007. First, make sure you are up to date on your Microsoft Office service packs. (As of this writing, SP3 is the latest for Office 2007.)

If you still have trouble, try clicking the Office button, then Save As and select Excel Binary Format (.xlsb). Then close Excel, reopen @RISK, and open the binary file.

last edited: 2012-11-12

4.40. "Out of Memory"

Disponível em português: Sem memória

Applies to:
@RISK 5.x–7.x
@RISK for Excel 4.x
@RISK for Project 4.x
All other products (temp folder, virtual memory, and Windows desktop heap tips)

When I perform some operation, I get an "out of memory" error. What causes this, and what can I do about it?

Running programs often need more memory than you have in your computer. To meet this need, Windows uses disk space dynamically as "virtual memory", also called the "paging file". Many applications, including @RISK, also write files to your hard drive during operation. For instance, @RISK stores all simulation data in a temporary file for use when generating reports.

"Out of memory" can indicate an actual out of memory condition, or running out of resources such as disk space. Windows and your applications run better when your disk has elbow room — you can get "out of memory" long before you're down to the last megabyte of free disk space. "Out of memory" can also indicate that one or more worksheets in the workbook are protected.

The following apply only to @RISK. For instance, "Out of Memory" might appear when you open a simulation data window after a large simulation, or do something else that takes significant system resources.

Special note: Even if you're not getting the "out of memory" error, you may be able to speed up your @RISK simulation with the techniques in this article.

  • Collecting Input Distributions

    The @RISK default is to collect all inputs. If you don't actually need to record the value of every input, go into Simulation Settings and on the Sampling tab, in the section titled Collect Distribution Samples, change "All" to "Inputs Marked With Collect". Then go to the @RISK Model window (List of Outputs and Inputs) and check (tick) the inputs that you want to collect.

    You should be aware of an important limitation: @RISK shows only collected inputs in tornado graphs and other sensitivity outputs. If you're not sure which inputs to collect, you might run a small pilot simulation while collecting all inputs, to help you identify the ones with the greatest impact on your outputs. Then you will know which inputs to mark for collection in the full-scale simulation.

  • Outputs and Statistic Functions

    @RISK must store the value of each output at each iteration. If you have many outputs that you don't need, remove the RiskOutput part of the formula in Excel's formula bar, or use the Model Window to remove them as outputs.

    When you have a statistic function such as RiskMean or RiskPercentile pointing to a cell, @RISK must store the value of that cell at every iteration. If the cell is a @RISK output, @RISK is storing its values anyway. But if it's an input that's not being collected, or if it's neither an input nor an output, then it's an additional cell for which @RISK needs to store values. Take a look at your statistic functions and eliminate any that aren't needed.

  • Number of Iterations

    Are you performing more iterations than necessary? Consider letting @RISK test for convergence. A pilot run will give you an idea of the number of iterations necessary, and then you can use that or a few more as your fixed number of iterations.

  • Number of Simulations

    Do you have the number of simulations set greater than 1? There is seldom a reason to do this unless you are using RiskSimtable functions. See also Iterations versus Simulations.

  • Protected Sheets

    Protected sheets are not an issue for @RISK 6.0 and later. But if you have one or more protected sheets in your workbook, @RISK 4.x and 5.x may not be able to perform a simulation. Try unprotecting all the sheets (including any hidden sheets that you created) and starting a simulation.

See also:

Last edited: 2017-02-15

4.41. "Out of stack space"

Applies to:
@RISK 5.x

Problem: When I start a simulation, nothing happens for a while (Excel seems frozen), and if I wait long enough I get an error "Out of stack space".

Response:
@RISK 5.0 introduced a feature called Smart Sensitivity Analysis, also known as precedent checking.

Depending on the size or complexity of your model, this precedent checking may finish in a short or long time, or may fail to finish at all. The simplest workaround is to disable Smart Sensitivity Analysis for this model and revert to the @RISK 4.5 style of sensitivity analysis. To do this, click the Simulation Settings icon, select the Sampling tab, and change Smart Sensitivity Analysis to Disabled. Click OK and save the workbook.

The choice of enabling or disabling Smart Sensitivity Analysis can be made for each workbook, and you can also set it in Application Settings to apply to new models. These settings are available in @RISK 5.0.1 and above and in all releases of @RISK in The DecisionTools Suite 5.x. If you do not have this choice, please click Help » About @RISK to verify that you have @RISK 5.0.0, and in that case please visit palisade.com/Updates/ to request an update to our current version.

last edited: 2010-03-15

4.42. "PalFlexServer6 Application has encountered a problem and needs to close"

Applies to: @RISK 6.1.1

When I run a simulation with Multiple CPU set to Enabled, sometimes the worker CPUs do not shut down properly, and I get this error message:

PalFlexServer6 Application has encountered a problem and needs to close

This bug affected a minority of users, and it was fixed in release 6.1.2.  If you are affected by this, upgrading to 6.1.2 or any later release will fix the problem.

Last edited: 2013-06-18

4.43. "Protected Workbook: This operation cannot be performed ..."

Applies to: @RISK 6.x/7.x

When I click Start Simulation or try other operations that involve a simulation, I get this message from @RISK:

Protected Workbook

This operation cannot be performed because worksheet 'name' is protected. However, if you provide the password to the worksheet, it can proceed. After the operation is complete, the worksheet will be reprotected.

This password is stored securely and will be used automatically in the future.

Below the message is a box for entering a password.

For technical reasons, during a simulation @RISK replaces all @RISK functions in your workbook with helper functions, and then swaps them back at the end of the simulation. It cannot do this if a worksheet that contains @RISK functions is protected against writing and is passworded, and therefore the simulation cannot proceed. You have several options:

  • If you want to protect the worksheet simply to avoid accidentally changing something, just protect it without a password. @RISK can work with protected worksheets if they are not passworded.

  • If you need to protect the sheet with a password, supply the password in the input box. You will not need to do it again, because the password will be stored in a hidden sheet in the workbook. (It's stored in encrypted form.)

  • The message appears only if a password-protected worksheet contains @RISK functions. If you would rather not tell @RISK the password, simply move the @RISK functions to cells in an unprotected sheet, and in the protected sheet refer to the cells that contain the @RISK functions.

Last edited: 2015-10-15

4.44. "The cell ... is part of an array formula."

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

When I run my simulation, a message pops up saying

The cell ... is part of an array formula. @RISK outputs cannot be part of array formulas.

Or

The cell ... is part of an array formula. @RISK distributions cannot be part of array formulas.

When I click OK, the simulation is abandoned. What is wrong, and how can I fix it?

To speed up the calculations, at start of simulation @RISK replaces formulas that include RiskOutput( ) and other @RISK functions with special formulas; then at the end of simulation is resets them to the formulas that you entered. @RISK can't do this replacement with an array formula, and therefore you get this message.

Exceptions: RiskData( ) can be used effectively in array formulas; see Placing Iteration Data in Worksheet with RiskData( ). Also, @RISK's Time Series Fit and Batch Fit commands create the time series distributions as array formulas.

There are two workarounds:

  • Maybe you don't actually need an array formula. For example, many array formulas are best replaced by Excel's SUMPRODUCT( ) function, which will also execute faster. Multiple Condition Tests by Bob Phillips specifically addresses the use of SUMPRODUCT( ) to replace filtering conditions like SUMIF( ) and COUNTIF( ).

  • If you do need an array formula, move the RiskOutput or to a new cell. For example, suppose that your cell AA17 contains

    ={RiskOutput()+formula}

    Remove the "RiskOutput()+" part, and then close the formula by pressing Ctrl-Shift-Enter. Cell AA17 will now contain

    ={formula}

    In a blank cell, place this formula:

    =RiskOutput()+AA17

    This is a regular non-array formula that references the cell that contains the array formula. Thus @RISK will still capture all the numbers for your output value, and you avoid the message.

  • If you have created an array formula that involves an @RISK distribution or statistics function other than RiskData( ), again you will need to pull the @RISK function out of the array formula. The exact change will depend on the logic of your worksheet.

Last edited: 2015-10-15

4.45. "The correlation matrix ... has multiple inputs assigned to the same matrix position."

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

When I run my simulation, I get the following message:

The correlation matrix ... has multiple inputs assigned to the same matrix position. Instances can be used to correlate multiple sets of inputs with the same matrix. Continue the simulation anyway?

What is wrong, and how do I fix it?

Correlation is specified by RiskCorrmat property functions within the @RISK distributions.  If you have two or more groups of inputs to be correlated using the same matrix, then your RiskCorrmat functions need a third argument, called an instance.  We recommend you click No and edit your workbook. Please see this article for more on instances and how to create them: Same Correlation Coefficients for Several Groups of Inputs.

However, if you're really trying to use this form of correlation to create a correlated time series, please see the help topic "Correlation of Time Series" in @RISK 6.0 and above.  (You need the Industrial Edition of @RISK 6.0 and above to use time series.)

What happens if I just click Yes and let the simulation proceed?

Please download the example SameMatrixPosition.xls (below).

Suppose you specified the same 2×2 matrix to correlate A16:A17 to each other and B16:B17 to each other, without specifying instances.  Then @RISK will indeed use that matrix to correlate A16 with A17, and to correlate B16 with B17.  But to accomplish this, since you correlated those two groups using the same matrix without instances, @RISK will actually use the same underlying random numbers for A16 and B16, giving them a correlation coefficient of 1 with each other. And the same is true of A17 and B17. These correlations between the groups are probably not what you want.

In the same example, D16:D17 and E16:E17 are correlated with instances, avoiding unwanted between-group correlations.

Last edited: 2015-10-15

4.46. "The correlation matrix at ... is not self-consistent."

Applies to: @RISK 4 and later

When my simulation starts, I get this message:

Warning
The correlation matrix at ... is not self-consistent. @RISK can generate the closest self-consistent matrix. OK generates a corrected matrix and continues, Cancel stops the simulation.

It's tempting to click OK, but that may not generate the matrix that best represents your correlations.

If you have @RISK 5.5 or later, please see How @RISK Adjusts an Invalid Correlation Matrix for information on using an adjustment weight matrix.

If you have @RISK 5.0 or earlier, or you just want to adjust the matrix yourself, see How @RISK Tests a Correlation Matrix for Validity.

Last edited: 2015-03-12

4.47. "The correlation matrix at .... specifies an invalid column."

Applies to: @RISK for Excel 3.5 and newer

When I try to run my model, which contains the @RISK correlation matrix created through the Model window, upon clicking the Run Simulation button, I get this message:

The correlation matrix at '[workbook]worksheet'!range specifies an invalid column (0).

There is a RiskCorrmat( ) function somewhere in the Excel model that specifies the invalid column. The error is in the RiskCorrmat( ), not in the matrix referenced in the error message. Look through the RiskCorrmat( ) functions for one or more that specify a zero, a reference to an empty cell, etc. for the matrix column (the second argument to RiskCorrmat).

Another cause (in @RISK 3.5 and 4.x) is having a correlation matrix named Corrmat, which causes a name conflict within the model.

Last edited: 2012-01-18

4.48. "The Excel name "..." has a character not in the current code page."

Applies to: @RISK 5.0–7.0 only

When I try to run a simulation, I get the error message

The Excel name "..." has a character not in the current code page.

with some name shown within the quotes.

You have one or more Excel names that are not in the character set for your Windows regional settings. For example, you'll get this message if you have any of the Western European regional settings, and an Excel name contains Asian or Greek letters.

Your best solution, if you have a current maintenance contract, is to upgrade to the latest version. Starting with 7.5.0, @RISK has improved Unicode support so that code pages are no longer a concern. However, if you don't have a maintenance contract and don't want to purchase an upgrade, you can use one of the following solutions.

Suggestion 1: If you have any workbooks open that are not part of your simulation, close them and try the simulation again. If the message doesn't appear again, then the problem names were in the unneeded workbooks that you closed. (In a simulation, @RISK simulates all open workbooks.)

Suggestion 2: You could change the Windows Region and Language settings to match those of the person who sent the workbook to you. If you don't want to do that, or don't have privilege, then you will need to edit the workbook so that all the names use only valid characters for your regional settings.

Note: The message tells you which Excel name is a problem, but not which workbook it's in. Therefore, if you have multiple workbooks open, you'll need to follow these suggestions for each open workbook.

Suggestion 3: If you have Excel 2007 or later, try converting the workbook to XLSB format. This worked for one customer, and it's easier than the suggestions below, so you may want to give it a try. (As a bonus, you may find that large files open faster, according to When should the xlsm or xlsb formats be used? at StackOverflow.com.

  1. Click File » Save As. Change "Save As type" to Excel Binary Workbook, and also change the name if you wish.
  2. Close Excel. (You must close Excel, not just the workbooks.)
  3. Reopen @RISK, open the saved XLSB workbook, and try a simulation.

Suggestion 4: Inspect the names in Name Manager, as follows:

  1. Get into Excel's Name Manager:

    • Excel 2000 to 2003: Click Insert » Name » Define.
    • Excel 2007 to 2016: click Formulas » Defined Names » Name Manager.
  2. Scan the list for any non-Roman characters. They sort alphabetically after the Roman letters, so any name that seems to be out of alphabetical sequence is worth a closer look. (You want to scan the whole list, because if there's one problem name there may well be others. If you miss any, you'll get the message again when you try a simulation.)

  3. Change any problem names to all Western European characters, and make the corresponding changes in your formulas.

  4. Save your workbook, probably under a new name so that you can go back to the original if you need to.

Suggestion 5: If you can't find the problem name, it might be hidden. Here are three alternative ways to find and remove hidden names. Use caution in deleting names. If the logic of the workbook depends on the name, then it will not work correctly if the name is deleted.

  • This macro makes all hidden names visible and all visible names hidden. Run it once, delete or edit any of the formerly-hidden names that are a problem, and run it again.

    Sub SwitchNamesVisibility()
    Dim n As Name, lVis As Long, lHid As Long
    For Each n In ActiveWorkbook.Names
        If n.Visible Then lVis = 1 + lVis Else lHid = 1 + lHid
        n.Visible = Not n.Visible
    Next n
    MsgBox ActiveWorkbook.Names.Count & " name(s) processed." & Chr(13) & Chr(10) & _
        "I hid " & lVis & " visible names and made " & lHid & " hidden names visible."
    End Sub
  • Microsoft has a Knowledge Base article, Macro to Remove Hidden Names in Active Workbook. It will step through all the names in the workbook, tell you whether each one is visible or hidden, and give you the option to delete it.

  • If you have a lot of defined names, that can be tedious. Here is a macro that asks you for a name. If the name exists, the macro gives you information about the name and makes it visible. The macro then gives you the option to delete the name.

    Sub FindName()
    Dim ans, sName, oName
    sName = InputBox("Which name are you trying to find?", "Name locator")
    On Error Resume Next
    Set oName = ActiveWorkbook.Names(sName)
    If Err <> 0 Then
        MsgBox "The name '" & sName & "' doesn't exist in the active workbook."
        Exit Sub
    End If
    On Error GoTo 0
    With ActiveWorkbook.Names(sName)
        ans = MsgBox("Parent's name: " & .Parent.Name & Chr$(10) & "Visible? " & .Visible & _
            Chr$(10) & "Refers to: " & .RefersTo & _
            Chr$(10) & Chr$(10) & "Shall I delete the name from this workbook?", _
            vbYesNo + vbQuestion + vbDefaultButton2, "About the name '" & sName & "'")
        .Visible = True
        If ans = vbYes Then
            .Delete
            MsgBox "Name deleted.  Remember to save the workbook!"
        End If
    End With
    End Sub
    

Last edited: 2017-05-08

4.49. "The Excel name "..." refers to "...", which has a character not in the current code page."

Applies to:  @RISK 5.0–7.0 only

When I try to run a simulation, I get the error message

The Excel name "..." refers to "...", which has a character not in the current code page.

with some name and some text shown within the quotes.

You have one or more Excel names that are defined as an expression that is not in the character set for your Windows regional settings. For example, you'll get this message if you have any of the Western European regional settings, and an Excel name's definition contains Asian letters.

The solution is the same as for the similar message The Excel name "..." has a character not in the current code page.

Last edited: 2016-06-29

4.50. "The exception unknown software exception (0xe06d7363) occurred ..."

Applies to: @RISK 5.5 and later

At the end of simulation, I get a popup with

Excel.exe - Application Error

The exception unknown software exception (0xe06d7363) occurred in the application at location 0x7c812a5b

(The location may vary.)

Your workbook's Visual Basic code contains a reference to an old version of the @RISK VBA library. To correct it, press Alt-F11 to open the Visual Basic editor, then follow the procedure in Setting References in Visual Basic.

Last edited: 2014-01-14

4.51. "The RiskMakeInput distribution ... may not be correlated."

Applies to: @RISK 6.3.0 and newer

I have a model that I developed in an earlier version of @RISK, and it simulated without incident. After upgrading, when I click Start Simulation I get the message

The RiskMakeInput distribution in cell location may not be correlated.

Or,

The RiskCompound distribution in cell location may not be correlated.

This worked before — why doesn't it work in the newer version?

It is true that the message is new in @RISK 6.3.0. However, it was always an error to try to correlate these functions; the only thing that's new is that now @RISK diagnoses the error.

Why can't special functions like RiskCompound, RiskSplice, and RiskMakeInput be correlated? When you click Start Simulation, if there are correlated distributions, @RISK draws all values for all correlated inputs up front, rearranges them appropriately to give the desired correlations, and then stores them for use during the sequential iterations of the simulation. (For details, see How @RISK Correlates Inputs.) That process breaks down with these three distributions. For example, @RISK can't predict what values a RiskMakeInput will take on during a simulation — in general, those values can't be known until the simulation is run. So @RISK has no way to reorder the values of a RiskMakeInput to produce the desired correlation.

Last edited: 2014-08-07

4.52. "The worksheet name '...' has a character not in the current code page."

Applies to: @RISK 5.0–7.0 only

When I try to run a simulation, I get the error message

"The worksheet name '...' has a character not in the current code page."

with some name or strange characters shown within the quotes.

It looks like one or more Excel worksheets (tabs) were created by somebody with different regional settings from yours, and not Western Europe or North America.

Your best solution, if you have a current maintenance contract, is to upgrade to the latest version. Starting with 7.5.0, @RISK has improved Unicode support so that code pages are no longer a concern. However, if you don't have a maintenance contract and don't want to purchase an upgrade, you can use one of the following options.

Option A: Locate the workbook that contains the worksheet named in the error message. If you don't need that workbook in your simulation, close it. If you do need it, choose one of the options below.

Option B: Rename the worksheet in question to something in your character set. Here's how:

  1. Click Utilities » Unload @RISK Add-in.
  2. Rename any worksheet tabs that have characters that aren't part of your local character set. (If any formulas in this workbook refer to that worksheet name, Excel will adjust them automatically.)
  3. Save the workbook — probably you want to save under a new name.
  4. Relaunch @RISK.

Option C: Save the workbook in XLSB format, close Excel, reopen @RISK, and open the XLSB workbook.
If any formulas in other workbooks refer to this workbook by name, you will need to update those formulas. Before you do that, verify that your workbook in XLSB format doesn't have the problem. (We do have one confirmed case where this solution worked, but because we did not have access to the workbook we aren't sure whether the success was related to some characteristic of that particular file.)

Option D: Close Excel, change your Windows regional settings to match those of the person who created the workbook, and then run @RISK.

Last edited: 2016-07-12

4.53. "Type mismatch" at End of Simulation

Applies to: @RISK 6.0 and @RISK 6.1 Preview

At the end of simulation, I see a pop-up with the message

Type mismatch

Or, Excel seems to freeze at the end of simulation, but I see in the Windows taskbar that there are multiple instances of Excel open, and when I move the main Excel window I see that one or more "Type mismatch" errors were hidden behind Excel.

In 64-bit Excel, the message is

Object initialized twice

but the symptoms are the same otherwise.

What is wrong?

A problem occurs if you perform a simulation that uses multiple CPUs while @RISK or TopRank is an add-in in Excel's active add-ins list.

The problem is fixed in 6.1.1, with respect to the @RISK add-in. If you have current maintenance, see Upgrading Palisade Software.

To solve the immediate problem, press Ctrl-Shift-Esc to open Task Manager.  Click the Processes tab, and click the column heading Image Name in the table. Select each instance of Excel.exe and click End Process.  (You need to kill all Excel processes before running @RISK again.)

To prevent it from happening again, the best solution is to upgrade to the current version.  If you cannot do that, remove @RISK and TopRank from Excel's add-ins list. (You can still run them through the desktp icons, if available, or via Start » Programs » Palisade DecisionTools.)

To remove add-ins from the active list:

  1. Open the Excel Add-Ins dialog:

    • In Excel 2010, 2013, and 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 or below, Click Tools » Add-Ins.
  2. Find @RISK for Excel 6.0 in the list and clear the box to its left. Repeat for TopRank 6.0 or similar.

  3. Click OK and close Excel.

For @RISK 6.0, we don't recommend making @RISK an active add-in in Excel's list. (@RISK will run just fine if it is not listed as an active add-in.) The problem was fixed in 6.1.1, so beginning with that release there should be no problem having @RISK start automatically when Excel starts if you prefer that.

Last edited: 2015-10-15

5. @RISK for Excel: Optimization (RISKOptimizer)

5.1. Where's RISKOptimizer 6.x/7.x?

Applies to: @RISK 6.x/7.x

I upgraded from 4.x or 5.x, and I don't see RISKOptimizer in the desktop icons or the Start menu group Palisade DecisionTools. Where did it go?

Beginning with 6.0, RISKOptimizer is integrated within @RISK. This allows for smoother operation. For instance, you no longer have two sets of simulation settings to contend with.

To launch RISKOptimizer from within @RISK:

  • In Excel 2007 and above, click the RISKOptimizer icon in the Tools group in the @RISK tab on the Excel ribbon.
  • In Excel 2003, click the Optimizer icon (seventh from the end of the long toolbar), or in the menu click @RISK » RISKOptimizer.

RISKOptimizer is included with @RISK Industrial Edition only. If you have @RISK Professional or Standard and you want to do optimizations, your Palisade sales manager will be happy to arrange the upgrade.

Last edited: 2015-08-04

5.2. RISKOptimizer Not in @RISK Tab of Ribbon

Applies to: @RISK 6.x/7.x

In the "Tools" section of the @RISK ribbon, I see Advanced Analyses, Project, and the @RISK Library, but no RISKOptimizer. What's wrong?

RISKOptimizer is part of @RISK Industrial, and is not included in @RISK Standard or @RISK Professional.

You'll need an @RISK Industrial or DecisionTools Suite Industrial license to run RISKOptimizer. Click Help » License Manager » Select License to see if you have an Industrial license available to you. If not, please contact your Palisade sales office for a quote on upgrading to the Industrial Edition of @RISK or the DecisionTools Suite.

Last edited: 2015-10-15

5.3. "Subscript out of range" with Efficient Frontier Optimization

Applies to: @RISK 7.5.0 only, Industrial Edition

I set up my optimization with Efficient Frontier, and clicked Start. Immediately I got the error message

Subbscript out of range

This is unfortunately a bug in @RISK 7.5.0. The error occurs only when (a) you are using Efficient Frontier (b) with constraints in addition to the special "Efficient Frontier" constraint, the one with multiple constraint boundaries, and (c) you have Simulation Settings » General » Multiple CPU Support set to either Enabled or Automatic. (The default is Automatic.)

The error has been fixed in release 7.5.1. If you still have @RISK 7.5.0, click Help » Check for Software Updates.

Last edited: 2016-10-25

5.4. "Unable to run macro tool during optimization."

Applies to: @RISK 7.5, Industrial Edition

When I click Start in RISKOptimizer, this message pops up:

"Unable to run macro tool during optimization."

What is the "macro tool" that the message refers to? How can I run my optimization?

The "macro tool" of the message refers to the Excel Tool selection in Simulation Settings (not RISKOptimizer Settings), on the Macros tab. In a simulation, that selection is a shortcut to running Excel Solver, Excel Goal Seek, or Palisade Evolver in every iteration of your simulation. But in an optimization, that selection is not allowed, because of technical problems with running Evolver inside RISKOptimizer.

Future releases of @RISK may relax that restriction and let you use the shortcut method to run Excel Goal Seek or Solver within every iteration of every simulation of an optimization. But for now, the workaround is to select Simulation Settings » Macros » VBA Macros and have your macro run Solver or Excel Goal Seek. On that same Macros tab, in the last section, select Fixed Samples, not Different Samples Each Recalculation. See "Solution (beginning with @RISK 6.2)" in Solver and Other Excel Recalculations within Your Macros. The example attached to that article shows you some sample VBA code.

Last edited: 2017-02-27

5.5. Where's the RISKOptimizer Tab (5.x)?

Applies to:
Excel 2007 and later, @RISKOptimizer 5.5.1 and 5.7
(If you have @RISK 6.x, see Where's RISKOptimizer 6.x?)

Problem:
I started RISKOptimizer in Excel 2007 or 2010 and its tab appeared on the ribbon, but when I started @RISK the RISKOptimizer tab disappeared.

or,

I started @RISK in Excel 2007 or 2010 and the @RISK tab appeared on the ribbon. Then I started @RISKOptimizer and there's no tab for it.

Response:
In 5.5.1, 5.7.0, and 5.7.1, when you run @RISK and RISKOptimizer at the same time in Excel 2007 or later, the RISKOptimizer commands are integrated into the @RISK tab. Look at the Start Simulation icon, then look two icons to the right for RISKOptimizer.

last edited: 2013-01-03

5.6. NA in Status Bar at Start of Optimization

Applies to:
RISKOptimizer 1.0, 5.x

Problem:
RISKOptimizer must not be working properly. All of the values I start out with in my spreadsheet are valid, and meet all the constraints I set. However, as soon as I click the Run Optimization button, the status bar says "NA". So apparently it doesn't even recognize the initial solution in the spreadsheet as being valid.

Response:
This happens because if you specify a simulation statistic, such as Mean or Standard Deviation, as the target of your optimization. Since these statistics are calculated based on an entire simulation, at least one simulation must be completed before the "NA" will change to indicate that a valid solution has been found. If you have set conditions calling for convergence or other conditions that take longer, you may have to wait a while to see this happen.

last edited: 2012-01-17

5.7. Correlations Ignored (RISKOptimizer 5.5.0)

Applies to:
RISKOptimizer 5.5.0 only

Problem:
I want to see the simulated correlation of two distributions in my optimization, but the RiskCorrel( ) function does not work.

Response:
Unfortunately, there was a bug in RISKOptimizer 5.5.0. This bug was fixed in 5.5.1, and it did not affect any release of @RISK.

If you are eligible for an upgrade to a later release, you should obtain it from your Palisade sales manager.

If you are unable to upgrade, we do have a partial workaround:

To have RiskCorrel cells return values for the best simulation, after the RISKOptimizer optimization you should choose to put the best solution in the adjustable cells, and then run a simulation in @RISK. To obtain the exact same statistics in @RISK as those in RISKOptimizer, use the same random-number generator, fixed number of iterations, and fixed seed in both programs.

Random-number generator:

  • @RISK: Simulation Settings » Sampling » Generator » Mersenne Twister
    (Mersenne Twister is always used by RISKOptimizer, and is the default for @RISK.)

Fixed number of iterations:

  • RISKOptimizer: Settings » Runtime » Simulation Runtime » Iterations » number
  • @RISK: Simulation Settings » General » Number of Iterations » same number

Fixed seed:

  • RISKOptimizer: Settings » Random Number Generator Seed » seed value
  • @RISK: Simulation Settings » Sampling » Initial Seed » Fixed » same seed value

last edited: 2012-11-22

6. @RISK with Projects

6.1. @RISK 6.x/7.x Doesn't Appear in Microsoft Project

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

I installed @RISK Professional or Industrial, but when I launch Microsoft Project there is no @RISK on the ribbon or in the menu. What's wrong?

@RISK was designed as an Excel add-in, not a Project add-in. (This is a change from version 4 of @RISK.) @RISK running in Excel sends messages to MS-Project via COM, but @RISK runs within Excel only, not within Project.

You do everything having to do with @RISK in the Excel workbook, but you can also change values of Project fields in the MPP file. At simulation time, or if you click Project » Sync Now in @RISK, @RISK updates your Excel workbook to account for any changes you made in the MPP, and vice versa.

Where does the MPP file come from, then? Do I have to create both the MPP file and the Excel workbook?

You create only the MPP file, and then you open @RISK with the default blank workbook. To import the MPP file into @RISK, click @RISK's Project button and then Import MPP File. @RISK creates an Excel workbook and links it to the MPP file. In future sessions of @RISK, you will open only the Excel workbook. @RISK will sense that there is a linked project, and it will open MS-Project and the MPP file. If you click Help » Example Spreadsheets » Simulation with Microsoft Project, you can see how @RISK launches Project and Project loads the MPP file.

We have a helpful video that illustrates this. In @RISK, click Help » Videos » Guided Tours » @RISK Guided Tour. When the Guided Tour opens, you can scroll the menu at the left to select PROJECT, which is near the end.

Last edited: 2015-05-21

6.2. Missing Project Icon in @RISK 6.x/7.x

Applies to: @RISK 6.x/7.x

I launch @RISK and there is no icon for @RISK for Project. What is wrong? Why is the @RISK Project feature not available?

There is no separate desktop icon or Start Menu shortcut for using @RISK 6 with projects. Instead, a Project button appears in the Tools section, near the end of the @RISK tab in Excel's ribbon.
full-sized ribbon

If your Excel window is not wide enough to display the whole tab, only a Tools button will appear. You can click the drop-down arrow to make Project and the other tools available.
shorter ribbon

If you don't have a Project icon in @RISK, please find the problem and solution in this list:

  • Is your computer missing Microsoft Project, or is your version of Project incompatible with your version of @RISK?  For compatible versions, depending on your version of @RISK, please see Windows and Office Versions Supported by Palisade. If you install a compatible version of Project after installing @RISK, @RISK will recognize it. There is no need to reinstall @RISK.

  • Do you have @RISK Standard?  The Project icon does not appear in @RISK Standard Edition, because Project integration requires @RISK Professional Edition, @RISK Industrial Edition, or the DecisionTools Suite. If you have @RISK Standard Edition, please contact your Palisade sales office for information on upgrading.

  • Did the Project icon previously appear in @RISK, but disappear after you upgraded to a later version of Microsoft Project? @RISK may still be looking for the old version of Project, which is no longer on your computer. Please perform the System Registry edit described in Which Version of Project is Opened by @RISK?

  • Are .MPP files not associated with Microsoft Project? With Project and Excel closed, double-click an .MPP file — it must be an .MPP file specifically, not any other type of Project file. If Project does not open, you need to tell Windows that .MPP files are Project files. Right-click the .MPP file and select Open With. (If a subdialog appears, choose Choose default program.) Select Microsoft Project, ensure that the box Always use the selected program is ticked, and click OK.

  • In some rare cases, even though Microsoft Project opens when you double-click an MPP file, the file association may not be set correctly. Here's how to fix it:

    1. In Control Panel, select Default Programs. (If you have the group view of Control Panel, it's in the Programs group.)
    2. Click Associate a file type or protocol with a program. Wait for the list to display, then find .MPP. (You can click once on an entry under Extensions, then quickly type .mpp including the dot.)
    3. If the associated program is not Microsoft Project, or the Project icon doesn't appear at the upper left, click Change Program. Browse to C:\Program Files\Microsoft Office or C:\Program Files\Microsoft Office. Select the Office12, Office14, Office15, or Office16 subfolder for Office 2007, 2010, 2013, or 2016; and in that subfolder select Winproj.exe.
    4. Close the dialog box and Control Panel. If you did have to change the association, try @RISK again and the Project button should now appear.

Last edited: 2015-10-15

6.3. Project Not Linked in @RISK 6.x/7.x

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

I moved or renamed my Excel or Project file. Now, when I open it in @RISK doesn't link to the .MPP file automatically.  I tried to restore the link in Project Settings, but I can't open that dialog because I don't have a project open.  What can I do?

You can re-establish the link by creating a name RISKMPPPath in the Excel workbook.

In Excel 2007 or newer:

  1. Click Formulas » Name Manager.
  2. Look for RiskMPPPath (three consecutive P's).  If it's there, highlight it and click Edit.  If it's not there, click New and create it.
  3. In Refers to, enter the full path and file name of the MPP file, such as
    ="C:\Users\Sanjay\Desktop\Simple Risk Register.mpp"
  4. Click OK and then Close.
  5. Save, close, and reopen the workbook.  (You don't need to shut down Excel.)

If the RiskMPPPath name exists but the Edit button is grayed out, the current sheet may be protected. Right-click on the tab for this sheet and select Unprotect Sheet. If Unprotect Sheet doesn't appear, the sheet is not protected but the workbook may be. Verify that it is not read only and not protected from editing.

In Excel 2003:

  1. Click Insert » Name » Define.
  2. Look for RiskMPPPath (three consecutive P's).  If it's there, highlight it.  If it's not there, click Add and create it.
  3. In Refers to, enter the full path and file name of the MPP file, such as
    ="C:\Users\Sanjay\Desktop\Simple Risk Register.mpp"
  4. Click OK and then Close.
  5. Save, close, and reopen the workbook.  (You don't need to shut down Excel.)

If the RiskMPPPath name exists but Excel won't let you edit the reference, the current sheet may be protected. Click Tools » Protection » Unprotect Sheet. If Unprotect Sheet doesn't appear, the sheet is not protected but the workbook may be. Verify that it is not read only and not protected from editing.

Last edited: 2015-10-15

6.4. After Importing Project, Excel Workbook Isn't Created

Applies to:
@RISK 6.x–7.5.0, Professional and Industrial Editions

I selected Project » Import MPP File in @RISK. Everything apparently went okay, but when I saved the workbook, no Excel file was created on disk.

Do you have a personal macro workbook, Personal.xlsb? If so, that workbook is automatically opened when you or @RISK launches Excel, but you may not be aware of it because it's usually hidden. (You can make it visible by clicking Unhide on the View tab in Excel.) If a Personal.xlsb file is open, @RISK release 7.5.0 or older will write the imported project to that file, instead of to the active workbook or a new workbook, as you selected.

This problem is resolved in @RISK 7.5.1.

  • If you have @RISK 7.5.0, regardless of maintenance status, click Help » Check for Software Updates to obtain the new release.
  • If you have @RISK 7.0.0 or 7.0.1 with current maintenance, click Help » Check for Software Updates to obtain the new release.
  • If you have @RISK 6 with current maintenance, please contact your Palisade sales office to request the new release.

Last edited: 2016-10-25

6.5. Filter Button Gray in Excel

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

I'm using @RISK to simulate a project. I want to filter tasks, but Excel's filter button is grayed out.

To filter tasks in a project, set your filter in MS Project, not in Excel. Please see Filtering Tasks in Projects.

If your purpose in filtering is just to select a group of tasks for similar treatment, you may need risk categories or a parameter entry table. See Parameter Entry Table versus Risk Categories.

Last edited: 2016-06-02

6.6. Standard Engine Used, but "Check Engine" Says OK for Accelerated

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

As advised in For Faster Simulations, I'm trying to use the accelerated engine for simulation, but when I click Start Simulation the status line in Excel tells me that @RISK is using the standard engine.

I clicked Project » Project Settings » Simulation » Check Engine, and the result was "Project OK for accelerated simulation." Why is @RISK still using the standard engine?

Click Simulation Settings » View. You probably have Demo Mode selected, or Show Excel Recalculations. Updating the display to show every recalculation is typically not done when you want the fastest simulations.

Turn off those settings, and @RISK will use the accelerated engine. (The other settings, including Update Windows During Simulation, do not prevent @RISK from using the accelerated engine.)

Last edited: 2015-10-15

6.7. Finish Date Unexpectedly Skewed

Applies to:
@RISK 6.x/7.x, Professional and Standard Editions
@RISK for Project 4.x

The main segments of my project are represented by normal distributions, or other distributions that are symmetric or nearly symmetric. But the finish date of the last task, which is supposed to sum up all of these segments, has a rather large right skew. What is wrong?

Take a closer look at your project to see how predecessor or successor links are affecting the outcome. One way to do this is to insert Predecessor and Successor columns in the Project sheet.

For example, if Task A must finish before its successor, Task B, can begin, then any @RISK distribution on the start time of Task B will be effectively truncated from the left during the simulation, because Task B can never begin before the finish date of its predecessor Task A.

See also: Summary Task Doesn't Sum the Durations of Subtasks.

Last edited: 2015-12-24

6.8. Finish Dates off by 100 Years

Applies to: @RISK 6x/7.x, Professional and Industrial Editions

I have a project that is scheduled for years ahead. I noticed that the dates are okay up to 2029, but I have tasks starting in 2029 and finishing in 1930 instead of 2030, and so on. Later years have a similar problem.

A customer reported this problem to us, and kindly shared the solution as well. Before importing your project, make certain that Microsoft Project is using a four-digit format for dates. Then all the dates will import correctly.

To change the date format in Project 2010 and later, click File » Options » General, and look in the right-hand panel for Date format.

Last edited: 2016-03-03

6.9. Continuous Output Data Graphed as Discrete

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

In @RISK with a project, the histograms for some outputs are displayed as Discrete Probability, and others as Probability Density. (In Application Settings I have preferred distribution format set to Automatic.)

The Discrete probability graph looks very strange at first sight, and whereas it can easily be changed, I was wondering why this behavior occurs —I have not seen this happening with @RISK in pure Excel models.

Project data have many date values, which means it's likely that many iterations will come up with duplicate values.  But when the preferred distribution format is automatic, @RISK looks at the number of duplicates in each distribution to decide whether to graph it as continuous or discrete. If there are no duplicate values in the distribution, or not too many, @RISK graphs it as continuous. If there are too many duplicate values, @RISK graphs the distribution as discrete.

If @RISK doesn't do what you want for a particular distribution, you can tell @RISK how to treat it by using the RiskIsDiscrete( ) property function. RiskIsDiscrete(TRUE) tells @RISK to treat the distribution as discrete, and RiskIsDiscrete(FALSE) tells @RISK to treat it as continuous.

For output distributions, click on the desired cell.  Then click Add Output, enter a name if you wish, and click the fx icon.  You can then set data type to Automatic, Discrete, or Continuous.  You can set the data type in this way when you first define an output or if you have already defined the cell as an output.

If you prefer, you can add a RiskIsDiscrete( ) function manually as the fourth argument:

=RiskOutput("MyOutput",,,RiskIsDiscrete(TRUE)) + ...

or

=RiskOutput("MyOutput",,,RiskIsDiscrete(TRUE)) + ...

You can also apply the RiskIsDiscrete( ) property function to inputs, as in this example:

=RiskResample(1,B1:B100, RiskIsDiscrete(FALSE))

@RISK will graph this function as continuous, regardless of duplicate values or the lack of them.

Last edited: 2015-10-15

6.10. Summary Task Doesn't Sum the Durations of Subtasks

Applies to:
@RISK 6.x/7.x, Pprofessional and Industrial Editions
@RISK for project 4.x

The duration of my summary task doesn't equal the total of the subtask durations. What is wrong?

The summary task doesn't just add up the durations of the subtasks. Rather, the duration of the summary task is the time interval from the start of the earliest subtask to the finish of the latest subtask. This is usually less than the total of the subtask durations, because typically the schedule lets some tasks can be worked on at the same time.

See also: Finish Date Unexpectedly Skewed.

Last edited: 2015-12-24

6.11. Tasks Not Linked in Gantt Chart

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

I opened my project in @RISK. It has predecessor-successor relationships, and the links show in Project, but the Gantt chart in Excel doesn't show any links between tasks. How do I make them appear?

There's a check box in the Gantt chart settings for @RISK.

  1. In @RISK, click Project » Charts and Reports » Standard Gantt to open the dialog.
  2. Tick (check) the box Display Links/Connectors Between Tasks.
  3. Click OK, and the connections will be drawn.

Last edited: 2015-10-15

6.12. Tasks and Resources Blank in Excel after Importing project

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

I imported my project, and the import seemed to go okay, but no data show up in Excel on the Tasks and Resources worksheets.

You may not have a valid Gantt view in this project because a table on which it is based has been deleted, or the project file is corrupted.  The solution:

  1. Open Project (not @RISK).
  2. Use the Organizer to copy over the default Gantt Chart from the Global.MPT file to your project. If Project says that your file already has a Gantt chart, go ahead and overwrite it.
  3. Then resave the project file.

Possibly the .MPP file itself is corrupted.  To fix it, open the file in Project, with @RISK not running.  Export it to XML format and close it.  Then open the XMP file and save it in .MPP format.

Last edited: 2015-10-15

6.13. Milestone Tasks Overlooked by Schedule Audit

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

Although some of my milestone tasks were lacking predecessor or successor tasks, the Schedule Audit did not report them. The Schedule Audit also missed positive lags (fixed durations) between milestones.

Milestones are tasks with a duration of zero. By default, the Schedule Audit does not report issues with them, but you can change this. In the Schedule Audit window, which @RISK displays after performing the audit, click the Options button. Then, near the bottom of the Schedule Audit Options dialog, remove the tick mark from the box labeled "Filter Out Tasks with Duration <=".

Note: @RISK 6.2.0 and earlier failed to report issues with milestones even if that box was empty. This bug was fixed in @RISK 6.2.1; if you have an earlier version you will want to upgrade your copy of @RISK.

Last edited: 2015-10-15

6.14. Tasks Start before Project Start Date

Applies to:
@RISK 6.x/7.x, Professional and Industrial Editions

When I run my simulation, tasks are starting before the project start date. How can this be?

Are you scheduling from the start date of the project, or from the finish date? If you have Microsoft Project set to schedule from the finish date, it keeps the project finish date fixed while varying the tasks so that the project ends on the finish date. While there are some valid reasons to schedule from the finish date, probably you want to change your project to schedule from the start date.

See also: How Project schedules tasks: Behind the scenes — specifically, under How does the project start date affect the schedule?

Last edited: 2016-09-15

6.15. "@RISK's Project commands require a copy of Microsoft Project."

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

When I try to import a project, I get the error message

@RISK's Project commands require a copy of Microsoft Project. This is not available on this system.

But I do have Project installed!

Please double-click an .MPP file.  Does it open in Microsoft Project?  If not, right-click the file, select Open with » Choose default program, and browse to Microsoft Project (program name: Winproj).

If an .MPP file opens in Project when you double-click it, verify that you have Microsoft Project installed on this computer, as opposed to a network share.  Also, deployment of Microsoft Office as Web Apps, On Demand, or some varieties of Office 365 and Click-to-Run may be a problem. See Click-to-Run and Office 365 with Palisade Software for more information.

Verify that your version of Project is compatible with your version of @RISK.  Please see Windows and Office Versions Supported by Palisade.

If all of the above check out correctly, it's possible that somehow the connection between @RISK and Project has been broken.  You can re-establish it by using the technique in Which Version of Project is Opened by @RISK?

Last edited: 2015-10-15

6.16. "An error has occurred linking the selected project ..."

Applies to: @RISK 6.1, Professional and Industrial Editions

I have an Excel workbook that was linked to a project in @RISK. When I try to open the project, I get this error message:

An error has occurred linking the selected project to the opened workbook in Excel. The newly opened workbook will be closed.

I click OK, and the workbook does close.  How can I get access to my project and workbook?

This unfortunately was a program error that affected certain projects when opened in @RISK 6.1.

It was repaired in @RISK 6.2.0.  If you have a current maintenance contract, please visit our upgrades page, or contact your Palisade sales office to request an upgrade to the latest version.

If you don't have a current maintenance contract, or your company policy will not let you install the upgrade, follow this procedure:

  1. Re-import the project and save the resulting workbook under a new name.

  2. Close @RISK.

  3. Open Excel (not @RISK) and copy your input distributions and your outputs from the old workbook to the new one.  The formulas that involve @RISK functions will display #NAME or other error codes, but you can still copy/paste them in Excel.

Last edited: 2015-10-15

6.17. "Can't create Gantt chart using the specified date format in Project."

Applies to: @RISK 6.x/7.x

When importing my MPP file into @RISK, I get this error message:

Can't create Gantt chart using the specified date format in Project. Switch to include hours and minutes in the displayed Project dates.

This message is displayed when one or more tasks have durations that are too short for @RISK's Gantt chart; thus the date format in Project is changed to higher precision. It usually comes up when there are defined tasks with a duration not greater than 1 day.

But this is not actually a fatal error. The Gantt chart in Excel is only visual, and does not affect the simulation in any way because all tasks are still simulated in MS Project.

Last edited: 2015-06-23

6.18. "Error in loading DLL" (when importing .MPP)

Applies to: @RISK 6.x/7.x Professional and Industrial Editions

@RISK seems to run fine in other respects, but when I try to import an MPP file I get this error message:

Run-time error '48':
Error in loading DLL

Your System Registry contains a reference to a version of Microsoft Excel or Project that isn't actually installed, or it lacks a necessary reference to the installed version of Microsoft Project. Please follow the procedure in Removing Outdated References to Project from the System Registry.

Last edited: 2016-03-14

6.19. "Error linking the opened workbook with the associated .MPP file."

Applies to: @RISK 6.0.0, 6.0.1, 6.1.0, Professional and Industrial Editions

When I open my .XLSX file in @RISK 6, I get the error message:

Error linking the opened workbook with the associated .MPP file. Check that the file can be properly opened in Microsoft Project.

What is wrong?

There is a conflict between the name of one of your fits and an internal name in @RISK. To remove the conflict, please follow this procedure:

  1. Launch @RISK and then open your .xlsx file. When "Error linking the opened workbook..." appears, click OK to dismiss it.

  2. On the @RISK tab of the Excel ribbon, click Distribution Fitting » Fit Manager. Delete the fits shown.

  3. Press Alt-F11 to open the Visual Basic Editor. If the code window doesn't open automatically, press F7.

  4. The fit names are invisible, so you're going to flip all names between visible and invisible, delete the now-visible fit names, and then flip all names back to their original visibility. To begin, paste the following macro code into the code window:

    Sub SwitchNamesVisibility( )
    Dim n as Name
    For Each n In ActiveWorkbook.Names
        n.Visible = Not n.Visible
    Next n
    MsgBox ActiveWorkbook.Names.Count & " name(s) processed."
    End Sub
  5. Run the macro.

  6. Click back into your Excel sheet and press Ctrl-F3. Look for the Fit names and delete them. (You may need to unprotect the Tasks spreadsheet first.)

  7. Back in Visual Basic Editor, run SwitchNamesVisibility again, to put all the remaining macro names back as they were.

  8. Delete the macro, if you wish.

  9. Save the workbook and close Excel. When you reopen the workbook in @RISK, everything should be fine.

This problem was fixed in 6.1.1. To avoid this problem in the future, upgrade to the current version if possible; see Upgrading Palisade Software. If you cannot upgrade, assign names not beginning with RPJ to your fits.

Last edited: 2013-10-17

6.20. "Error opening the selected project"

Applies to: @RISK 6.x/7.x, Professional and Industrial Editions

When I try to import any of my projects, I get

Error opening the selected project

But I don't have a problem importing Palisade's examples.

Here are several known causes for this error message, with their cures:

  • Your Global.mpt file may be corrupt. Delete it (or move it to another location) and let Project re-create it.
    Where is Global.mpt? See Microsoft's article "Cannot save to Global.mpt" when exiting Microsoft Project. Don't be put off by the mention of Office 2003 at the top; at the bottom it says that it applies to all versions through 2013.

  • Check your Microsoft Project options, while @RISK is not running. If you have the default project path set to a nonexistent location, it can cause this error. Correct the default project path, close Project, and launch @RISK again.

  • You may have bad COM type library registrations, particularly if you previously had another versoon of Project. Follow the procedure in Removing Outdated References to Project from the System Registry to fix this.

Last edited: 2016-06-29

6.21. "The file was created by a newer version of Microsoft Office Project"

Applies to: @RISK 7.0 only

I have Microsoft Project 2007. In @RISK, as soon as I click "Import MPP File", I get this message:

The file was created by a newer version of Microsoft Office Project and a converter is needed to open it. Do you want to download the converter from the Microsoft Office Web site?

If I click No, I can't import the file. If I click Yes, I get "Sorry, the page you're looking for can't be found."

You need to replace an @RISK file in the Program Files or Program Files (x86) folder tree. Recent versions of Windows may not let you do this in a download, so please follow this procedure:

  1. Verify that Excel and Project are not running.

  2. Download the attached file to your desktop or another convenient location. To verify it, right-click and select Properties. The size should be exactly 270,848 bytes.

  3. Open the folder C:\Program Files (x86)\Palisade\RISK7 or C:\Program Files\Palisade\RISK7 folder, whichever one exists.

  4. Click and drag the downloaded file into that folder. You may have to give permission twice, once to overwrite the older copy of the file and once to put the file into the Program Files tree.

Last edited: 2016-05-03

6.22. Error in Outputs with RiskBranch Function (@RISK 4.x)

Applies to:
@RISK for Project 4.x

Problem:
I looked at the data from my @RISK for Project simulation, which has probabilistic branching. Some of my outputs show "Error" for some iterations instead of giving a data point for that iteration. What is wrong?

Response:
This is an intentional part of the design.

In each iteration, the branching function chooses one of the possible branches. A branch that is not chosen is symbolically removed from the project by "zeroing out" the affected tasks and their descendants. When a task is zeroed out, any outputs related to that task will return "Error" instead of a value. This prevents the values in zeroed-out branches from skewing the summary statistics for that task.

For example, imagine that task A branches with 50% probability to task B1 and 50% probability to B2. If we have outputs on the finish date of B1 and the finish date of B2, and if we run 100 iterations, we would expect the output for B1 to have 50 errors and the output for B2 to have 50 errors. The remaining, non-error samples give us a picture of how the output behaves when the task is included in the project.

last edited: 2012-11-22

6.23. Regression Coefficients Incorrect in Quick Reports (@RISK 4.x)

Applies to: @RISK for Project 4.1.4

In my Quick Reports, inputs with regression coefficients of zero should be ranked by correlation coefficient, but this isn't happening.
Or:
I have a large model with many iterations and inputs, and all regression coefficients are showing as zero instead of their actual values.

A patch is available to fix both of these problems. Please click Help » About in @RISK to verify that you have release 4.1.4, and then contact Palisade Technical Support with your serial number and a reference to this article.  (Your serial number should be visible on the same Help » About screen.)

If you have current maintenance, you might prefer a no-charge upgrade to @RISK 7.x, our current version. The 7.x versions integrate Excel and Project and offer many new features compared to @RISK 4.1.4. Your Palisade sales manager can assist you with the upgrade.

Last edited: 2015-08-07

6.24. Tutorial Does Not Run (@RISK 4.x)

Applies to:
@RISK for Project 4.1
(Tutorials for 6.x and 5.x versions of all products are on the Palisade Web site under Support » Videos » Quick Start.)

Problem:
When I try to run the tutorials, I get a black box with no audio or video.

Solution:
Here are several things to try, in order.

  1. If Microsoft Internet Explorer is not your default browser, please see Tutorial Does Not Run in Firefox, Opera, ...

  2. Check the top of the Internet Explorer window carefully. If you see a thin beige strip with some text about blocked content, click the strip and then follow the instructions to unblock the content.

  3. If you get the message "Error on page", please see "Error on page".

  4. If you get audio but no video, please see Tutorial Has Audio, No Video.

  5. If you are running the tutorial through the Internet, please run the copy that is installed on your computer. Click the Windows Start button, then Programs or All Programs, then Palisade DecisionTools, then Tutorials, then @RISK for Project.

  6. The menu selection (preceding item) is a front end to the actual Windows Media Player files in the tutorial. You can access the media files directly, as follows.

    Open Computer or My Computer and navigate to the directory where you installed Palisade software. The default location is C:\Program Files\Palisade, or C:\DTools for older versions. Then open the subfolders RISKPJ41 » Tutorial » riskproj_wmvs. Open the Overview file and then the rest of the files in numerical order.

    If that doesn't work, please try the .wmv format on our Web site at @RISK for Project Tutorial Movies.

  7. The tutorial uses Windows Media Player files, and you may need to download a codec to play the files. For instance, one user reported that he needed to download the ACELP.NET (130) codec from VoiceAge http://www.voiceage.com/codecs.php to play the @RISK tutorial in Vista. Your IT department can help you download any missing codecs.

last edited: 2012-11-23

6.25. Tutorial Does Not Run in Firefox, Opera, ... (@RISK 4.x)

Applies to:
@RISK for Project 4.1

Problem:
I try to launch the Palisade tutorial, which has a Firefox (Opera, Netscape, ...) icon on its shortcut. Although I do have Windows Media Player installed, the tutorial returns an error message and will not run.

Response:
Tutorials based on Windows Media Player must be played in Internet Explorer. The tutorials will not run in Firefox or other non-Microsoft browsers. However, if Firefox, Opera, Netscape, etc. is your default browser, you can still run the tutorial as follows:

  1. Make sure Internet Explorer is installed on your computer. (If you have a Windows computer, Internet Explorer is most likely present on it even if it's not your default browser.)
  2. Open Internet Explorer.
  3. From the menu in Internet Explorer, choose File>Open. The Open dialog appears.
  4. Click the Browse button in the dialog. The file navigation dialog appears.
  5. Use the dialog to navigate to the tutorial file (or its shortcut).
  6. Click the Open button. The file path to the tutorial appears in the Open dialog.
  7. Click the OK button. The tutorial is now ready to run.

last edited: 2012-11-23

6.26. Tutorial Has Audio, No Video (@RISK 4.x)

Applies to:
@RISK for Project 4.x

Problem:
When the tutorial is launched, the tutorial begins to play. The audio can be heard but the video cannot be seen.

Solution:

  1. Launch Windows Media Player.
  2. Select Tools » Options » Performance.
  3. Decrease the amount of video acceleration by moving the slide in the "Video Acceleration" section to the left.
  4. Click Apply.
  5. Try launching the Palisade tutorial again.
  6. If the video portion of the Palisade tutorial still isn't displayed, return to step 3 and decrease the video acceleration further.

last edited: 2012-11-23

6.27. "All text fields are used in this project!" (@RISK 4.x)

Applies to:
@RISK for Project 4.x

Problem:
When I open my project in @RISK, I get the message

All text fields are used in this project! @RISK requires an empty text field to store data. Please clear a text field and re-try.

But the thing is, I do have text fields that are available.

Response:
There are several possible causes. Before you do too much work troubleshooting, you may wish to upgrade to the current release of @RISK, if you are eligible. This problem does not occur in @RISK 6.0.0 and newer, and these releases have many new features. If you have current maintenance, you can upgrade to the current release of @RISK at no charge; just contact your Palisade sales office.

To solve the problem if you're using @RISK 4, we suggest that you work through these steps in order:

  1. @RISK 4.x knows about only Text1 through Text20. If all those are in use, you will get this message even though higher-numbered text fields are available.

  2. By default, @RISK wants to use field Text1. If Text1 isn't clear, find an available field and follow the procedure in Designating Columns for @RISK for Project 4.x Functions.

  3. If you still get the message, close this project and then open one of our examples. (They're in the RISKPJ41\Examples or RISKPJ40\Examples folder under the folder where you installed your Palisade software.) If you get the same message, look for what else in your environment may be creating a problem, such as another add-in to Project or a template that starts automatically.

  4. If our file opens normally, then it's something in your particular .MPP file that is the problem. Does it contain links to other files or external resources? Perhaps those files are using all the text fields.

  5. Click Tools » Organizer » Fields (in Project 2010, File » Info » Organizer) and look for available custom fields. If Text1 through Text20 are listed there, it means that they are considered "in use" by @RISK and can't be used for the @RISK functions column. (A customer found that this occurred when an .MPP file created in Project 2007 was converted to Project 2003 format.) The solution then is to create a new .MPP file and manually copy everything to it, taking care that everything is duplicated except those custom fields. Then you'll be able to open your rebuilt .MPP file in @RISK.

last edited: 2017-02-17

6.28. "Can't graph ... single calculated value" (@RISK 4.x)

Applies to:
@RISK 4.x For Project

Problem:
After running a simulation in @RISK for Project, all the statistics and graphs are reporting that the output had no variability. The error, "Can't Graph... Single calculated value", also occurs when drawing the histogram. There are @RISK input distributions assigned to the output's predecessor tasks. Thus, the input functions should be causing variability in the output being analyzed.

Response:
Typically this problem occurs when constraints have been added to tasks in such a way that they prevent the output in question from varying.

With Palisade's @RISK for Project, we recommend that all task constraints be set to "As soon as possible" for forward scheduling projects and "As late as possible" for backward scheduling projects. Task constraints such as "Start no earlier than", "Finish no later than", "Must start on", or "Must finish on", may have a significant impact on Monte Carlo simulations and may result in single value output errors. Constraints are always honored when @RISK performs random recalculations during the simulation and the use of constraints that fix the start or finish dates must always be carefully considered before adding them to the schedule network.

Different constraints will have varying impacts on a project. For example, "Start no earlier than" cuts off early task completions and will make a project schedule longer. "Finish no later than" cuts off late finishes and will make a project schedule shorter. A project plan with multiple "Start no earlier than" and "Finish no later than" constraints will likely be constraint bound and might need to be modified for Monte Carlo simulation.

For more on using constraints in Microsoft Project, we recommend Dynamic Scheduling with Microsoft Office Project by Eric Uyttewaal.

last edited: 2005-07-01

6.29. "Error defining output ...Please check the RiskOutput functions" (@RISK 4.x)

Applies to:
@RISK for Project 4.x

Problem:
When I start a simulation, I get the message

Error defining output ...Please check the RiskOutput functions in this range and retry!
Simulation RDK4_DefineOutput 92

Response:

Text fields in Microsoft Project are limited to 255 characters.   If you have a long task name, and one of the fields of that task is an @RISK output, the output name may exceed the limit.  @RISK adds some information to the task name to create the default output name, so you probably want to keep your task names under about 200 characters. 

As an alternative, if you want to keep a long task name, you can specify a non-default output name by editing the RiskOutput function in the @RISK Functions column for that output: change Fieldname=RiskOutput() to Fieldname=RiskOutput("your short name for the output").

last edited: 2012-08-08

6.30. "Error on page" (@RISK 4.x)

Applies To:
@RISK for Project 4.1
Evolver Developer's Kit (EDK)
@RISK Developer's Kit (RDK)

Problem:
When I load RISKPJ41\Tutorial\rp4Tutorial.html (or another tutorial mentioned above) and press any of the PLAY buttons, there is just the little message in the lower left hand corner "Error on page" and nothing happens.

The same thing happens when I attempt to run the tutorial from your Web site.

Response:
Installing an updated version of Windows Media Player (7.0 or higher), or Internet Explorer (6.0 or higher), or both, should cure this problem. These free downloads are available from Microsoft.

Note: If you are running Windows 95 or Windows NT, you will be unable to upgrade your Windows Media Player to the required version. You will need to either install a more up-to-date operating system or run the tutorial from a different computer that has a more recent operating system installed.

last edited: 2012-11-23

6.31. "File not found" (@RISK 4.x)

Applies to:
@RISK for Project 4.x

Problem:
When I open my project, I get one or more "file not found" messages. It doesn't tell me which file it's looking for.

Response:
Please try our examples, which are in folder RISKPJ41\Examples or RISKPJ40\Examples under your Palisade installation directory. If those projects run, your particular project file may be corrupt.

To fix a corrupt project file:

  1. Open Microsoft Project (not @RISK) and open the project.
  2. Do File » Save As and select the type XML.
  3. Close the original project.
  4. Open the XML project, making a note of any error messages.
  5. Save the XML project as an MPP project under a new name, then fix whatever problems the messages revealed.

We found this solution by a Web search, leading to the article "How to troubleshoot damaged projects in Microsoft Project" (accessed 2009-08-29). It is no longer in its original location, but this archived copy is still available.

last edited: 2012-11-22

6.32. "Object library invalid or contains references ..." (@RISK 4.x)

Applies to:
@RISK for Project 4.1, released 2008 or earlier

Problem:
When I try to start @RISK, I get the message

Object library invalid or contains references to object definitions that could not be found

Solution:
This is related to a problem with a Microsoft Windows security update of 2008-12-09: MS08-070: Vulnerabilities in Visual Basic 6.0 Runtime Extended Files (ActiveX Controls) could allow remote code execution (accessed 2012-11-16).

The error message will appear in a new installation of @RISK for Project if the Windows update has already been applied to your system. It can also appear in a previously working installation of @RISK, if you apply the Windows update or it's applied automatically.

In January 2009 we released @RISK for Project 4.1.4r2, which is compatible with that Windows security update. If you have an earlier version of @RISK for Project—4.1.3 or earlier, or 4.1.4 without an "r" number—you should upgrade to a later version to resolve this problem. Your Palisade sales manager can assist you with the upgrade.

To determine your @RISK for Project version, open Computer or My Computer and select C: » Program Files (x86) or Program Files » Palisade » RISKPJ41 » Version History. If you have @RISK 4.1.4r2 or later and you got this error message, the cause is something other than the Windows security update; please contact Palisade Technical Support for assistance.

last edited: 2012-11-16

6.33. "The argument value is not valid." (@RISK 4.x)

Applies to:
@RISK for Project 4.1

Problem:
When I try to show Risk Categories, I get the error message

Runtime error 1101. The argument value is not valid.

What is wrong?

Response:
This is actually a problem in Project rather than in @RISK: You do not have a valid Gantt view in this project because a table on which it is based has been deleted, or the project file is corrupted.

The solution:

  1. Open Project (not @RISK).
  2. Use the Organizer to copy over the default Gantt Chart from the Global.MPT to your project. If Project says that your file already has a Gantt chart, go ahead and overwrite it.
  3. Then resave the project file.

last edited: 2013-06-19

7. @RISK for Excel: Library

7.1. Library Can't Find Any Servers on My Computer

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

I try the Connect or Create button in @RISK Library, but it can't find any servers except my own machine.

It may be a firewall or permissions issues. Please follow this procedure to check that possibility:

  1. Click Start » Programs » Microsoft SQL Server 2005 » SQL Server Management Studio Express. (If it's not there, please visit http://www.microsoft.com/downloads/en/default.aspx and enter

    management studio express

    in the search window. You want Microsoft SQL Server Management Studio Express, which should be the first hit. Download and install it, then run it.)

  2. The server name should be pre-populated with the local server. Click the down arrow and select Browse for more.

  3. In the Browse for Servers dialog, select the Network Servers tab. You will see "Retrieving", then eventually "Database Engine". Click the + sign to expand it, and you should see all the networked machines.

If you do see the networked machines, please let us know and we will assist you. If you don't see the networked machines, this is an issue in your local network and you should get your IT department to establish the necessary permissions and adjust the firewall if appropriate.

Last edited: 2015-10-15

7.2. Library Can't Connect to Networked Database

Applies to: @RISK Professional and Industrial Editions, 6.2 and newer

I'm trying to follow the procedure in SQL for @RISK Library on Another Computer, but I can't get a list of databases.
OR
: Nothing happens when I try to create a database.

First, verify that you have SQL Native Client or SQL Server installed (for @RISK 6.1 and earlier, it must be SQL Server). See SQL Versions and Installation.

Then, try making a dummy connection.  This is a way to resolve problems with connectivity, user names, and passwords outside of the @RISK context.

Setting up SQL as a data source:

This procedure is for Windows 7, but it should be similar for other versions of Windows. If you get any errors or things do not go as expected, the trouble is not @RISK related. Your IT person can help you resolve it.  Your IT person will also verify that you do have a Windows login on the remote computer, and an SQL login on the remote computer.

  1. Open Control Panel » Administrative Tools » Data Sources (ODBC).

  2. On the ODBC Data Source Administrator screen, click Add, select SQL Server, and click Finish.

  3. Type a dummy name and description, pick your remote SQL server from the list, and click Next.

  4. On the next screen, check (tick) "Connect to SQL Server to obtain default settings".  Enter your login information. (You probably want Microsoft Authentication, but your IT person can tell you which authentication to use.) Click Next.

  5. On the next screen, check (tick) "Change the default database to", and select one from the list.  Clear the "Attach database filename" box. Click Next.

  6. Click Finish.

You don't need to keep this dummy data source permanently. Once you've used this technique to verify your network connectivity and your authentication, use the same authentication on the @RISK Library screens. You can then remove this dummy data source on the ODBC Data Source Administrator screen.

Last edited: 2015-03-25

7.3. "Error opening parent key"

Applies to:
@RISK 5.x for Excel

Problem:
When I open @RISK, I get the error message "Risk Library – Error opening parent key".

Response:
This is most likely a problem in your System Registry, either insufficient permission or a corrupted key. You can either diagnose and correct the root cause, or if you don't need the @RISK Library feature you can simply disable it to avoid the problem.

(A) Disabling the @RISK Library
If you have no need for the @RISK library feature, the easiest thing is to turn it off. In @RISK | Utilities | Application Settings, change the fourth item, @RISK Library, to Disabled. Close Excel and reopen @RISK, and verify that the setting is still Disabled.

If you are unable to save Application Settings owing to System Registry issues, you can still disable the @RISK Library by renaming its executable file. With Excel not running, please open My Computer and navigate to the RISK5 folder under your Palisade installation folder. In that RISK5 folder, please rename RiskLibrary.exe to RiskLibrary.xxx. Windows will most likely give you a message about making files unusable, and that's exactly what you want to do.

(B) Checking for System Registry Problems
You may have a problem in your System Registry. To determine whether that's the case:

  1. Close Excel if it is open.
  2. Click the Windows Start button, then Run, and enter the command
          regedit
    Then click OK.
  3. Navigate to the key
          HKEY_LOCAL_MACHINE\Software\Palisade
    or, in 64-bit Windows,
          HKEY_LOCAL_MACHINE\Software\WOW6432Node\Palisade
  4. Under that key, right-click on RiskLibrary and select Rename. Rename the key to RiskLibraryZZZ.
  5. Look carefully at the Regedit window. Is RiskLibrary still there? If it is, then you have insufficient permission or your System Registry is corrupted; please ask your IT department to help you. If the rename operation was successful and RiskLibrary is gone, rename RiskLibraryZZZ back to RiskLibrary and close the System Registry editor; this part of your System registry is fine and you have sufficient permission.

last edited: 2012-11-11

7.4. "The @RISK Library has been disabled."

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

When I click on the library icon and select either Add Results to Library or Show Library, a pop-up box is displayed with the message

"The @RISK Library has been disabled".

Click @RISK » Utilities » Application Settings. In the first group, change @RISK Library from Disabled to Enabled, and click OK.

Last edited: 2015-10-15

7.5. "The @RISK Library has not finished loading."

Applies to:
@RISK for Excel 5.x

Problem:
I have loaded SQL 2005 Express according to the instructions at http://www.palisade.com/support/sql92847.asp. I tried Show @RISK Library, but I got a message saying

The @RISK Library has not finished loading. Try again later.

Solution:
The most likely cause for this message is a problem with the SQL installed on your computer. Please make sure you install using an account with full Administrator permissions.

You should also verify that you can launch and work with the SQL tool directly. Sometimes the @RISK message above is displayed when SQL is being run for the first time, which requires 30 seconds or more of initialization time.

Please see this article for additional possible causes and their cures: "The @RISK Library is not available because a connection ..."

last edited: 2012-11-13

7.6. "The @RISK Library is not available because a connection ..."

Applies to:
@RISK 5.x, Professional and Industrial Editions

Problem:
I downloaded and installed SQL according to your instructions. I have the @RISK Library set to Enabled in my Application Settings. But when I try to use the Library, I get this message:

The @RISK Library is not available because a connection to an SQL Server could not be established.

Solution:
First, do you actually have SQL Server 2005 Express installed? Please check in your Windows Start Menu. If it's not there, please follow the directions at http://www.palisade.com/support/sql92847.asp to install it.

If you do have the right version of SQL installed, then for some reason @RISK is timing out in its attempt to reach the SQL server. The solution is to increase the timeout interval. This article explains how to do that, either by editing the System Registry directly or by running a Registry update file. (Use either method, not both.)

Method A: Edit the System Registry

  1. Click Start » Run, type Regedit, and click OK.
  2. Navigate to HKEY_CURRENT_USER\Software\Palisade\RiskLibrary\5.0\Settings
  3. In the right-hand panel, right-click on an empty space and select New » DWORD.
  4. Rename the new item to ConnectionTimeoutCustom (capitalization as shown, and no spaces).
  5. Double-click ConnectionTimeoutCustom and enter the value 25.
  6. Close Regedit and run @RISK.

Method B: Registry Update File

  1. Download the attached file to your desktop.
  2. Rename the saved file to LibraryTiming.reg.
  3. Double-click the LibraryTiming.reg file. When asked "Are you sure", answer Yes.

last edited: 2010-07-23

7.7. "Unable to initialize RiskLibrary object."

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

During startup, @RISK shows the message

Unable to initialize RiskLibrary object.

This is caused by outdated references to other versions of Microsoft Office. To clear them, please see Removing Outdated References to Office from the System Registry.

Last edited: 2015-09-11

8. @RISK for Excel: Other Issues

8.1. Results Not as Expected (Debugging Tips)

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

Contents:
"Errors" that really aren't?
Error message appears?
Output has just one value?
No values to graph?
Calculations seem wrong
Visual Basic errors?

My simulation results in @RISK don't seem right. Can you recommend any techniques for finding my mistakes in my model?

Consider the possibility that your model is actually behaving correctly. We're frequently asked about these "errors", but they make sense when they're explained:

If an error message appears, there's probably an explanation and a fix in the Troubleshooting section of this Knowledge Base. Type a few key words in the search window at the bottom of this page.

One common problem is an output graph showing just a vertical line, and the statistics showing minimum = mean = maximum. In other words, this output has the same value in every iteration. Most likely, that means none of your input distributions are precedents of this output.

  • To test this, click the "rolling dice" Random/Static icon, below the number of simulations, and then repeatedly tap the F9 key. You will see which cells change and which don't, and that will help you find where the chain of dependents is interrupted.

  • For pure Excel models, as opposed to projects with associated MPP files, you can trace precedent-dependent relationships directly by using tools in Excel. To find the precedents of an output, click the output cell and then, on Excel's Formulas tab, click Trace Precedents repeatedly. Each click will add arrows for one further level of precedents. If there are too many arrows, you can click Remove Arrows, then click on one particular precedent, and then Trace Precedents back from that point.

    In a similar way, you can click on an input cell and then use Trace Dependents to find the cells that depend on that input cell.

  • For project models with associated MPP files, Schedule Audit will tell you of tasks that have no predecessors or no successors. This can help you trace where the logic of your project needs correction.

Maybe you have an output where the graph window shows that there were no values to graph. In this case, look at the number of errors in the statistics, and you'll probably see that it equals the number of iterations. Or maybe the statistics grid shows a number of errors above 0, and you don't know why @RISK is finding errors during some iterations. Either way, here are some tools:

  • In Simulation Settings, on the View tab, tick the box labeled Pause on Output Errors, then run a simulation. @RISK will pause at the first occurrence of an output error, and display a list of precedent inputs. You can also look around in your worksheet, because it contains the input values for this iteration, and calculations derived from those values.

  • You can also use "shoeprint mode" to find the errors; see Some Iterations Show Error in Data Window. What Can I Do?

  • If you're running a simulation with multiple CPU, and you have errors in blocks of consecutive iterations but numbers in other blocks of consecutive iterations, you probably have the problem described in Multiple CPU — Blocks of Errors in Simulated Outputs. That article explains what to look for.

If you have calculations that seem wrong, or aren't working as expected, here are some suggestions. (Save the workbook under a new name before you make debugging-type edits.)

  • Use the Simulation Data window to show all iterations. But first, reduce the number of iterations to about 3 and run a new simulation, so that you don't have an overwhelming mass of data to deal with.

  • Break up complicated formulas. For example, if you have IF(A, B, C), and A, B, and C are complicated formulas, try putting them in separate cells and then use cell references in the =IF formula.

  • Consider adding some cells as outputs, just so that you can see their values in every iteration. This can be a great way to narrow down a calculation error.

  • Force one or more inputs to bad values. For example, if you have a RiskNormal(5,5), and you suspect that a negative value may create error conditions, change it to RiskNormal(–2,0). That will cause every iteration to get a –2 from this input.

I think my worksheets are okay, but my VBA code isn't working right.

Debugging Visual Basic for Applications code can be tricky. Here are some hints:

  • Misspelled variable names are a potential problem. To find them, put Option Explicit before the first sub or function in your module, and then click Debug » Compile. If there are multiple errors, the compiler shows you only the first, so after you fix each error you need to click Debug » Compile again.

  • Try setting breakpoints, and then stepping through the code execution. That will tell you pretty closely where the error is coming from. You can then use the Immediate Window (Ctrl+G) to display values of variables and diagnose the problem.

  • Another technique is to use MsgBox functions to pop up progress messages. As an alternative, the Debug.Print method will write anything you like to the Immediate Window, so that you won't have to deal with pop-ups but still can monitor progress.

Can you look at my model and tell me what's wrong?

We're sorry, but the scope of free Tech Support services doesn't include debugging customer models. If you have a question about how a particular @RISK feature works, we'll gladly answer it for you.

Last edited: 2017-05-16

8.2. Footprint Button Grayed Out

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

After my simulation ran, I opened the Data window, intending to use the Iteration Step feature to place iteration data in my workbook. But the shoeprint icon at the bottom of the window was grayed out, even though the data were displayed.

This can arise from several causes:

  • If you've changed the workbook since running the simulation, Iteration Step mode is unavailable, and you'll see an error in the Data Window's title bar. Run a new simulation.

  • If Collect Distribution Samples (on the Sampling tab of Simulation Settings) has any value other than All, the simulation does not collect all the data needed to run Iteration Step mode, and you will see an error message in the window's title bar. Change Collect Distribution Samples to All and run a simulation. (This will increase the amount of memory used, so you may also want to reduce the number of iterations temporarily.)

  • If you have two distributions in the same cell, Iteration Step mode is unavailable. The solution: move all but one of them to different cells and use cell references in the original formula. For example, suppose a cell contains a formula like

    =IF(something, RiskNormal(something), RiskPert(something))

    Move the RiskPert function to another cell, say AH47, and change the original formula to

    =IF(something, RiskNormal(something), AH47)

    (Having more than one distribution function in a cell is not an error as such. If your model is naturally designed that way, and you don't need Iteration Step mode, there's no reason to break up your formulas.)

Additional keywords: Shoeprint Mode, Footprint Mode

Last edited: 2015-02-02

8.3. Excel Files with @RISK Grow Too Large

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

My Excel workbook containing my @RISK model takes a long time to open, and Excel seems to be unstable because of the large file size. My model was not nearly this large originally, but grew much larger when I ran a simulation and then saved the Excel workbook. What can I do?

When you run a simulation, @RISK can save simulation results in the Excel workbook or in a separate .RSK5 file, or neither. It sounds like you have @RISK set to save results in the Excel workbook, or you had @RISK set that way in the past. To clear those results and reduce the size of this workbook, follow this procedure:

  1. In @RISK's Utilities menu, select Clear @RISK Data.

  2. The Clear @RISK Data dialog box appears. Select "Simulation Results" and clear any marks that appear for the other options. Click OK and answer the confirming prompt.

  3. Save your workbook.

How can you prevent your workbook from growing again with future simulations? Either save results in an external .RSK5 file, or don't save them at all. (If you want to save selected results, use the @RISK Library, which is available in the Professional and Industrial Editions of @RISK.)

Here's how to register your preference with @RISK:

  1. In @RISK's Utilities menu, open Application Settings.

  2. In the General group, in the left column, locate "Save Results". If that is set to "Automatically Save in Workbook", change it to "Prompt on Save", "Save to External File", or "Never Save Results". Click OK.

If you chose "Save to External File", then whenever you save your workbook after running a simulation, @RISK will open a Save @RISK Results dialog showing the default external file name and the size of the results. Click Yes to save results to that file, No to skip saving results, or the Options button (Save Options icon in @RISK 5.x/6.x) to choose a different file name and location.

"Prompt on Save" is a variation on "Save to External File". If you chose "Prompt on Save", then whenever you save your workbook after running a simulation, you get the same Save @RISK Results dialog telling you how large the results are. However, the default in this case is to save results in the same workbook. Click Yes to accept this choice, click No to skip saving results, or click the Options button or the Save Options icon to save results to an external file. With "Prompt on Save", if you run additional simulations in this session, the default save location will remain as the .RSK5 file. But if you close @RISK and restart it, the default save location will change to "workbook". When answering the Save @RISK Results dialog, always check the save location and, if necessary, click the Save Options icon to select the external .RSK5 file.

Beginning with @RISK 7.5, you have another alternative available, to save results when you want to and only then, without being prompted. Select "Never Save Results" in Application Settings. Whenever you reach a point where you'd like to save results, click Utilities » Save Simulation File. You'll be prompted to choose a folder and a file name.

How do I get access to those results when I reopen my Excel file in a later session?

@RISK should pop up a dialog box:

Open Saved @RISK Results from file location?

If the results file was moved or renamed, @RISK won't be able to find it and won't display that dialog. Click Utilities » Open Simulation File... to select the RSK5 file that contains your results.

If your simulation results file is very large, and you have 32-bit Excel, @RISK may not be able to open it. Try closing other programs, and if that's not enough you may need to switch to 64-bit Excel.

Last edited: 2016-07-12

8.4. #NAME Errors in Place of Distribution Functions

Applies to:
@RISK for Excel 5.x and 4.5
RISKOptimizer 5.x and 1.0

In @RISK or RISKOptimizer, I open a workbook that contains distribution functions. Instead of numeric values I see #NAME errors.

Sometimes a saved workbook will not have correct connections to @RISK. One or more of the following three methods will fix the problem. After fixing the problem, save the workbook and it should be fine the next time you open it.

  1. Set Excel calculation to Automatic:

    • In Excel 2007 or newer, click Formulas » Calculation Options » Automatic.
    • In Excel 2003 or earlier, click Tools » Options » Calculation » Automatic.
  2. Press Ctrl-Alt-F9 to force all cells to recalculate.

  3. If that didn't work, run a simulation with one iteration.

  4. If that also didn't work, change "=" to "=", forcing all formulas to recalculate:

    1. Open the Edit–Replace dialog (Alt-E, then E).
    2. Click Options.
    3. Find what: =
      Replace with: =
      Within: Sheet
      Look in: Formulas
      "Match entire cell contents" NOT checked
    4. Click Find All, then click Replace All.

Once you have resolved the #NAME errors, save your workbook.

Last edited: 2012-11-16

8.5. #NAME Errors in Place of Capital IQ Functions

Applies to:
@RISK 6.0.0 through 6.2.0

Problem:
When I run @RISK and Capital IQ together, my CIQ functions show as #NAME errors.

Or, when I open Excel, one of these errors pops up:

'/A .xlsx' could not be found. Check the spelling of the file name, and verify that the file location is correct.

'C:\Users\...\Microsoft\AddIns\ciqfunctions.udf"' could not be found. Check the spelling of the file name, and verify that the file location is correct.

(The file location in the second message will vary.)

Is @RISK incompatible with Capital IQ?

Response:
@RISK 6, through release 6.2.0, unfortunately was incompatible with Capital IQ. In some instances there were even Excel crashes when both add-ins were loaded together. The recent release of @RISK 6.2.1 fixed those problems, so your best bet is to upgrade your copy of @RISK or The DecisionTools Suite.

We are grateful to the people at S&P Capital IQ for their help in finding the problem, and for confirming that the new release of @RISK fixed it.

last edited: 2014-04-04

8.6. #VALUE Errors in Corrected Correlation Matrix

Applies to: @RISK 5.5–7.x

I entered a RiskCorrectCorrmat( ) function as an array formula, to store my adjusted matrix in my worksheet. But all the cells show #VALUE. What is wrong?

If your original correlation matrix, or your adjustment weights matrix, has values above and below the diagonal, then it must be symmetric. If there are values both above and below the diagonal, and the matrix is not symmetric, then the RiskCorrectCorrmat( ) array function will return #VALUE in all cells.

To avoid this problem, especially with larger matrices, it's best for both the original correlation matrix and the adjustment weights matrix to have values only on one side of the diagonal. For this reason, when you create a correlation matrix in @RISK's Define Correlations dialog and tell @RISK to write the matrix to Excel, @RISK doesn't write any values above the diagonal.

See also: How @RISK Adjusts an Invalid Correlation Matrix

Last edited: 2016-03-30

8.7. @RISK Functions Don't Reappear after Swapping Out

Applies to:
@RISK 5.0

Problem:
I have an Excel workbook where the @RISK functions were swapped out before it was saved. I reopened it and then opened @RISK, but I can't get the functions to swap back in. Have I lost all my functions?

Response:
Your functions are still safe.

If @RISK is open when you open a workbook with swapped-out functions, it will swap them back in automatically. The recommended sequence is:

  1. Open @RISK and let it open Excel for you, or open @RISK while Excel is open.
  2. Open the workbook, and @RISK will swap in the functions automatically.

But if you open the workbook first and then open @RISK, the functions are not swapped in and you can't swap them in with the icon. The solution, if you already have a workbook open when you open @RISK, is:

  1. Close the workbook, leaving @RISK and Excel open.
  2. Reopen the workbook. The functions will swap in automatically.

last edited: 2013-02-24

8.8. Toolbar Appears, But Every Button Does Nothing

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

When I launch Excel, the @RISK or TopRank ribbon appears and seems normal. However, none of the buttons do anything. When I click them, dialog boxes and windows don't appear as expected.

This is probably caused by adding the @RISK or TopRank ribbon as an add-in, which you should never do. For more about this, including a repair procedure, please see "Object variable or With block variable not set".

If some of the buttons are active and some are not, see the next few articles by clicking the links at the bottom right of this page.

Last edited: 2016-06-24

8.9. Define Distributions and Browse Results Do Nothing

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

A simulation seems to run normally, but when I click Browse Results nothing happens. Nothing happens when I click Define Distributions. When I try Fit Distributions, the initial fit dialog comes up, but when I click the Fit button on the dialog box I get this error:

Non-modal forms cannot be displayed in this host application from an ActiveX DLL, ActiveX Control, or Property Page.

First, determine whether you need a different article:

This problem has several possible causes, so you may have to try more than one solution.

Solution 1: Verify your installation of the Visual Basic 6 Runtime, and install the latest if yours is missing or out of date.

Solution 2: You may have an active add-in that is incompatible with @RISK.  We list two we know of that give this result, but there could be others that we don't know about. So for a first pass, we recommend disabling all add-ins except those that are part of Excel.

  • The Laserfiche client software component called "Laserfiche Office Integration 8.3": A customer discovered that this contains Office plugins that prevent @RISK from bringing up some windows. Those plugins can't be disabled from within Excel, but that component must be uninstalled by using the Laserfiche installer. Other versions may or may not have this issue; only 8.3 is confirmed.

  • Morningstar Commodity: At least some versions appear to prevent the Define Distribution and Browse Results buttons from opening their windows.

(To list your active add-ins, click File » Options » Add-Ins. The active add-ins are the first list in the right-hand panel. Inactive add-ins, the second list, don't matter. To deactivate an add-in, without uninstalling it, notice the last column, which tells you whether it's an Excel add-in or a COM add-in. Then at the bottom, select that type in the drop-down box after the word "Manage", and click the Go button. After deactivating all add-ins, close and reopen Excel.)

Solution 3: A clean Uninstall and Reinstall of Palisade Software solves the problem in some cases.

Last edited: 2017-04-18

8.10. Define Distributions, Add Output, and Define Correlations Do Nothing

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

When I click Define Distributions, Add Output, or Define Correlations, the background of that button in the ribbon changes color, but no window comes up. I can run a simulation, but there's no Simulation progress window, and Broswe Results doesn't open a window.

First, determine whether you need a different article:

Your RiskModel.dll component is unregistered or misregistered. To fix this, you need full administrative rights. Please follow this procedure:

  1. Open Computer, My Computer, or This PC and navigate to C:\Program Files (x86)\Palisade or C:\Program Files\Palisade. Double-click the RISK7, RISK6, or RISK5 folder. In that folder, Shift-right-click the RiskModel.dll file, and select Copy as path.

  2. Open a command prompt as administrator.

  3. Type regsvr32 /u and a space, but don't press Enter. Right-click in the command window, select Paste, then press Enter. You may get a success or failure message. You can disregard a failure message unless the code is 0x80004005. That code means that the command window does not have full administrative rights. Close it, then open a command prompt as administrator and repeat step 3.

  4. Type regsvr32 and a space (no /u), but don't press Enter. Right-click in the window, select Paste, then press Enter. If you get a success message, close the command prompt and the RISK folder window; @RISK should now bring up all windows correctly. If you get any failure message at all, then something else is wrong.

Last edited: 2016-11-30

8.11. Define Distributions Does Nothing, Results Graph Stuck at "Simulation Starting"

Applies to: @RISK 7.5.0 only

My Define Distributions button doesn't do anything. I can enter distributions through Insert Function, but when I click Start Simulation the results graph window just shows "Simulation is starting. No data to graph."

Before you conclude that something is wrong, check the Excel status line while the simulation is starting up. If you see a succession of status messages, you probably don't have the problem discussed in this article. You may not have any problem at all. Particularly if your simulation is large, or if you have lots of correlations or many iterations, it can take some time before the first iteration begins, and then a bit more time till you start seeing a results graph. If you have a Progress Window, you definitely do not have the problem in this article.

This problem is resolved in @RISK 7.5.1.

  • If you have @RISK 7.5.0 with current maintenance, click Help » Check for Software Updates to obtain the new release.
  • If you have @RISK 7.5.0 without a current maintenance contract, contact your Palisade sales office to get a quote for an upgrade to the current release.

See also:

Last edited: 2017-02-27

8.12. Define Distributions Freezes When I Select a Distribution

Applies to: @RISK 7.5.1, possibly some earlier releases also

In the first Define Distributions dialog, I select a distribution, and the screen freezes instead of showing the parameters and the graph. I can still click into the Excel workbook and edit cells, and I can close the frozen Define Distributions screen by clicking the red X at upper right.

There is a problem with your registration of .NET 4. Please follow the procedure in Missing Results Graph to fix this.

Last edited: 2017-03-31

8.13. No Distributions in Define Distributions Dialog

Applies to: @RISK 6.x/7.x

When I click Define Distributions, the top part of the dialog is normal, and I can see the names of the tabs. But the tabs themselves are empty — there are no pictures of distributions.

Do you see a little orange circle with a question mark, or is the bottom half of Define Distribution completely blank? If you see the orange circle, the solution is to upgrade to the current version of @RISK. If you don't have that circle and question mark, please proceed with the troubleshooting in this article.

Your SharpGrid control is not functioning properly. It may simply be misregistered or missing, or it could be corrupted, or you may have a Windows setting that prevents it from running. (This same root cause has other symptoms, such as missing statistics grids in Browse Results, crashes in StatTools dialogs, and "invalid access to memory location" when starting @RISK.)

Here is the procedure to fix it. (This requires full administrative rights, so you may need to ask your IT department to perform these steps for you.)

  1. Close Excel and Project if they are open.
  2. Open an administrative command prompt.
  3. Enter the command
    cd "C:\Program Files (x86)\Common Files\Data Dynamics\Sharpgrid" && dir c:sg20*
    If you get "cannot find the path" or similar, enter the command
    cd "C:\Program Files\Common Files\Data Dynamics\Sharpgrid" && dir c:sg20*
    If both commands got "cannot find the path", or if file sg20u.ocx does not appear, repair your Palisade software and test @RISK to see if that fixed the problem.
  4. But if sg20u.ocx is there, it may be misregistered. Type this command to re-register it:
    regsvr32 sg20u.ocx
    You should get a pop-up message "DllRegisterServer in sg20u.ocx succeeded." If you do, test @RISK to see if the problem has been solved.
    • If the command did not succeed, something is wrong in your installation of Windows, and you will need to get assistance from your IT department.
    • If the command succeeded but @RISK is still not working correctly, the problem may be your settings for Data Execution Prevention (DEP). SharpGrid cannot run under DEP. To check and correct your DEP settings, see our article Data Execution Prevention.

Last edited: 2016-12-30

8.14. Color Cells Not Working

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

I selected Color Cells in the @RISK tab of the Excel ribbon, but my inputs and outputs aren't colored. What's wrong?

Color Cells are implemented using Excel's conditional formatting feature, so anything that interferes with conditional formatting will interfere with Color Cells. There are also some issues relating only to Color Cells.

  • Make sure to enable Color Cells by clicking the Color Cells button in the @RISK tab of the ribbon. The background of the Color Cells icon will change to let you know that it's active.

  • By design, Color Cells don't work in a workbook that is programmatically created (such as our report workbooks, or any workbook created by program code). Color Cells work in workbooks you open interactively by clicking File » New or File » Open in Excel, by double-clicking a workbook on your desktop or in a folder, and so forth..

  • There is an upper limit of approximately 10,000 cells that can be colored. After that, @RISK will turn off the feature, and a message will appear in the Excel status bar.

  • Conditional formatting rules for @RISK inputs, outputs, and statistic functions may become corrupted by the other existing rules in your workbook or may simply conflict with rules you created yourself. If this happens, please select the affected range and delete all the Conditional Formatting rules that affect it: Home » Conditional Formatting » Clear Rules » Clear Rules from Selected Cells. Turn on Color Cells to apply the changes.

  • @RISK cannot apply conditional formatting rules to protected spreadsheets. When this is an issue, @RISK shows the message "Input/output cells were protected and could not be formatted as specified in Application Settings." Unprotect your worksheet before enabling Color Cells again.

  • When you're using @RISK with Excel 2010 and Project, cell formatting for @RISK functions is only available in saved workbooks. @RISK shows a message in this situation. Save your project .XLSX file, close and restart @RISK, and reopen the file to use formatting.

  • In @RISK 6.3.0, Color Cells don't work correctly in Excel 2013. Upgrade to the current version of @RISK to solve this.

Last edited: 2017-02-17

8.15. No Statistics Table in Browse Results

Applies to:  @RISK 6.x/7.x

I ran a simulation and clicked Browse Results. The graph seems normal, but the statistics table is missing.

Do you see a little drop-down arrow at the upper right corner of the Browse Results window? If so, you have the display choice set to None. Click the arrow and select the display you want to see.

On the other hand, if you just see a big white space where the grid should be, then your SharpGrid control is probably not working correctly. To remedy this, you may need to perform one or both of these procedures:

Last edited: 2017-03-31

8.16. @RISK Mini-Toolbar Does Not Appear

Applies to: @RISK 6.x

When I right-click on a cell, the @RISK mini-toolbar does not appear.

Do you have @RISK 7.0 or newer? With the release of @RISK 7.0.0, the mini-toolbar was replaced by two entries, @RISK–Results and @RISK–Model, in the right-click menu for cells. @RISK–Model always appears; @RISK–Results appears if you have run a simulation.

If you have @RISK 6.x, look in the first section of Application Settings and verify that the mini-toolbar is enabled. The mini-toolbar was introduced in @RISK 6.0, and to bring it up you could right-click a cell or hold the down left mouse button while pointing into a cell. Holding down the left mouse button could interfere with selecting a block of cells, so that behavior was removed from @RISK. In @RISK 6.1–6.3, the only way to bring up the mini-toolbar was to right-click in a cell.

If the toolbar is enabled, the problem may be your screen resolution or display mode. Aero is the Windows higher resolution "Aero-glass" mode that the mini-toolbar was designed for. "Classic" non-Aero modes, like those used in Windows XP or available as a "basic" theme in Windows 7, don't allow the mini toolbar to function correctly. In Windows 7, switch to a higher resolution Aero theme to allow the mini toolbar to work. If you have release 6.1.1–6.2.0, see Mini-Toolbar and Context Menu Missing.

Additional keywords: minitoolbar, mini toolbar

Last edited: 2015-07-16

8.17. Mini-Toolbar and Context Menu Missing

Applies to:
@RISK 6.1.1, 6.1.2, and 6.2.0
(For other releases, see @RISK Mini-Toolbar Does Not Appear.)

Problem:
When I right-click a cell in @RISK, the right-click menu (context menu) does show @RISK.  But the mini-toolbar doesn't appear correctly with its icons; instead there is just a vague ghostly rectangular shape. And if I click on @RISK in the initial right-click menu, the secondary menu with selections like "Define Distributions...", "Add Output...", and "Fit Distributions to data..." does not appear.

A screen shot is attached.

Response:
This is unfortunately a bug in these releases of @RISK.  If you have Aero mode disabled in Windows, or if you're using Windows XP or another Windows version that doesn't have Aero available, the toolbar does not appear.

@RISK displays either the mini-toolbar or the secondary context menu, not both. If the mini-toolbar is enabled in the first section of Application Settings, but your Windows is not in Aero mode, the bug prevents the mini-toolbar from appearing, but the application setting suppresses the secondary context menu.

This bug was fixed in release 6.2.1.  We recommend that you upgrade your software (if eligible).  You can take either of these actions if you're unable to upgrade:

  • Turn on Aero mode, if your version of Windows supports it, and select one of the Aero Themes. The mini-toolbar will appear. 

  • If you prefer not to use Aero, or if your version of Windows doesn't support Aero, you can just disable the mini-toolbar in Application Settings and then you'll have the traditional right-click context menu.

If you've taken those actions and the mini-toolbar still does not appear, see @RISK Mini-Toolbar Does Not Appear

Additional keywords: minitoolbar, mini toolbar

last edited: 2014-03-31

8.18. RiskCorrmat Ignored in F9 Recalculation

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

I've set up an @RISK model with a correlation matrix using the RiskCorrmat function. I've set @RISK's standard recalc mode to random. Why is there no correlation between the correlated input variables when I press the F9 key to recalculate the Excel spreadsheet?

This is by design. F9 key sampling is not controlled by the correlation matrix, because the RiskCorrmat( ) functions only become active during the actual @RISK simulation.

See also:
How @RISK Correlates Inputs

Additional keywords: Corrmat

Last edited: 2015-10-15

8.19. @RISK Changes Simulation Settings When Non-@RISK Workbook Is Opened

Applies to: @RISK 6.3.0 and 6.3.1 only

I opened a workbook that had no @RISK settings or functions in it, and my simulation settings changed. What happened?

If you open a workbook and change any @RISK settings, then open a second workbook without closing the first, @RISK is supposed to ask you whether to change simulation settings for the first workbook to match the new one". In fact, if the new workbook has any @RISK settings in it, all releases of @RISK do just that.

If the second workbook contains no @RISK settings, effectively its settings are the simulation defaults. @RISK 6.0.0 through 6.2.1 still prompt you in that case. But @RISK 6.3.0 and 6.3.1 have a bug: when your second workbook has no settings, @RISK simply applies the default simulation settings to both workbooks without asking you.

This is fixed in @RISK 7.0.0, and we recommend that you upgrade to the new version.

Last edited: 2015-08-07

8.20. @RISK Changes Worksheet Formulas

Applies to: @RISK for Excel 4.x–7.x

During a simulation, I noticed that @RISK changes any formula that involves an @RISK distribution.  Why is that?

Suppose you have two or more distributions in a cell.  During a simulation, when Excel calls on @RISK to recalculate a distribution, @RISK needs to know which distribution Excel wants recalculated at the moment. Therefore, before the simulation @RISK rewrites the formula into a form that will make this identification possible. But even when a cell formula contains only one distribution, @RISK rewrites, so that distributions are treated in the same way whether they occur alone or in a larger formula. The rewrite also lets @RISK calculate some distributions more efficiently.

At the end of a simulation, @RISK changes all the cell formulas back to their original form.

After an Excel crash, in the recovered workbook the formulas were not changed back.  Instead they all began with RiskSDS.  How can I get my formulas back without having to re-create them all?

In this situation, simply run a simulation and the formulas will be changed back at the end.  To make the process go more quickly, change the number of iterations to 2 or 3 before simulating, and then change it back afterward, before saving your workbook.

Additional keywords: Replacing formulas, formulas replaced, formulas changed

Last edited: 2015-10-15

8.21. Chart in Excel Graphs Only 200 Data Points

Applies to:
@RISK for Excel 3.5 and newer
@RISK for Project 3.5 and newer

There are thousands of data points in my @RISK input or output distribution, but when I use the Chart in Excel command (Graph in Excel for @RISK 3.x/4.x), only 200 points (or even fewer) are listed in Excel, and it appears that only these points have been graphed.

Keep in mind that to graph a distribution of data, it must first be binned. The points that you see in Excel are the positions and heights of the histogram bars, not the actual data points. @RISK decides how many bars to use, based on the number of data points (number of iterations), but the number of bins is never more than 200.

Last edited: 2012-01-18

8.22. Detailed Statistics Report in Excel is Pivoted

Applies to: @RISK 5 and newer

I opened the Detailed Statistics window after my simulation, and it looked normal, with one column for each output or input. But when I clicked the icon at the bottom for "Report in Excel", the report was transposed, with one row per output or input and each statistic in a column.

This is by design. There is an internal limit of 256 columns for this report in Excel, even Excel 2007 and later, so if you have more than that many outputs and inputs @RISK pivots (transposes) the report.

If you have under 256 outputs and you don't actually need inputs collected — if you're not planning to do sensitivity analysis — then you can get around this. Open Simulation Settings, and on the Sampling tab change "Collect Distribution Samples" to None.

Last edited: 2015-03-24

8.23. Pasted Graph Loses Some Details

Applies to:  @RISK 6.x

From my graph, I clicked the Edit and Export icon at the bottom and selected Copy Graph or Copy Graph and Grid, then pasted it into my image editor. Some grid lines were lost, or some text was lost. The same thing happens if I paste the graph into an Excel worksheet and then print it as a PDF.

The issue is with image formats in Windows. When you copy an image to the clipboard from Excel or @RISK, it's in Windows metafile format. If you paste it into a program that understands metafiles, such as Excel, it's still right. But if you paste it into an image editor that doesn't understand metafiles, it has to be converted and some detail may be lost in the conversion. Exactly what is lost depends on the graph itself and the program you're pasting into.

If you paste into Excel, everything should look fine. But the image is still a metafile, so if you save the worksheet or image as a PDF then it has to be converted, and again details may be lost.

In @RISK 7.x, the copy command uses a combined format that will paste correctly in these situations. If you're eligible for the upgrade, that is the best solution.

The solution for @RISK 6.x: Don't copy to the clipboard. Instead, from the Edit and Export menu select Save Image File, and choose any format except metafile. The conversion will be done by Excel and should be accurate. You can then open it in your image editor, convert it to PDF, etc.

Additional keywords:  Copy and paste image

Last edited: 2015-08-07

8.24. Advanced Sensitivity Analysis Shows no Variation

Applies to:
@RISK version 5.0 and 5.5.0

Problem:
It seems like the Advanced Sensitivity Analysis just pulls the same values over and over, with no variation between iterations. I have some of the new RiskStatic( ) functions in my model.

Response:
This was a known problem with @RISK 5.0 and 5.5.0, and was fixed in 5.5.1. If you have current maintenance, please upgrade to the latest product.

If you're running an Advanced Sensitivity Analysis on any model that contains RiskStatic( ) functions, all of the sampled values for those functions will be the static value, so it looks like the sensitivity analysis is not working. With an older file where the model was already defined, this wasn't an issue. But when you define new distributions for cells which already contain values, the model will most likely contain RiskStatic( ) values, and those cells will not vary. If you're unable to upgrade to @RSK 5.5.1 or later, the workaround is to remove the RiskStatic( ) functions from those cells, and then run Advanced Sensitivity Analysis.

last edited: 2011-01-24

8.25. Macro Doesn't Store Values to Workbook

Applies to: @RISK for Excel, all releases

I have set @RISK to run a macro at every iteration, and my macro code makes changes to the workbook.  It seems that these changes do get made for some groups of iterations, but not for others.  Why isn't my macro running for all iterations?

Do you have multiple CPU set to Enabled in Simulation Settings?  In a multiple-CPU simulation, each CPU has its own copy of the workbook.  The master CPU (the one with a visible Excel window) parcels out the work to the worker CPUs, and they send back random numbers for @RISK distributions in their assigned blocks of iterations.  At the end of simulation, the worker copies of Excel are shut down, and if your VBA code made any changes they are lost.  

If you need to generate numbers with VBA code during a simulation, and have them available after the simulation, here are some possibilities:

  • If the simulation is not too large, change Multiple CPU to Disabled.  Then there won't be any extra copies of your workbook, and any changes your macros make will go into the only copy of the workbook.

  • If you need to generate values in VBA, change the macro to a user-defined function and call it from a formula in your workbook.  You can then make that cell an @RISK output.  You could use RiskData( ) functions to store all iteration values in the workbook, or create a Simulation Data report after the simulation.

Last edited: 2013-03-29

8.26. GraphDistribution Method in VBA Fails

Applies to: @RISK 7.5.1 only

My VBA code worked fine in 7.5.0, but when I updated to 7.5.1 it started failing in the GraphDistribution method. My error message is

Invalid argument.
Argument: Simulation

or

Method 'GraphDistribution' of object '_RiskSimResultCollection' failed

This is a bug unfortunately introduced in @RISK 7.5.1. It affects GraphDistribution or any other method whose first argument is a variant for identifying the result and whose second argument is an optional simulation number. If you supply the simulation number all is well, but if you leave it out then @RISK displays one of the above errors.

This bug will be fixed in our next release, but we already have a patch available so that you don't have to change any of your VBA code. Download the attached AtRiskOL.dll file to a convenient location, such as your desktop. Then, open the folder C:\Program Files (x86)\Palisade\RISK7 in 64-bit Windows, or C:\Program Files\Palisade\RISK7 in 32-bit Windows, and drag the downloaded AtRiskOL.dll file into that folder. Windows will probably ask you for permission to access the folder and also to overwrite the existing file.

Last edited: 2016-11-04

8.27. "A DecisionTools error occurred."

Applies to: @RISK 6.x/7.x with 32-bit Excel

Previously, I saved my simulation results in an @RISK results file (RSK file). Now, when I open my Excel workbook and try to open the results file, I get

A DecisionTools error occurred.

If the results file is very large, you may be exceeding the available resources in your 32-bit Excel. You may be able to get around this by closing other applications that use significant memory, or you may need to switch to 64-bit Excel.

Last edited: 2016-03-01

8.28. "Cannot run the macro 'AdvTools5.xla!TBGoalSeekMain'."

Applies to:
@RISK for Excel 5.x

Problem:
When I try to run Goal Seek or another advanced analysis, I get this error message:

An error has occurred in @RISK for Excel.

Cannot run the macro 'AdvTools5.xla!TBGoalSeekMain'. The macro may not be available in this workbook or all macros may be disabled.

Response:
This is actually an Excel problem. Either you have some corrupted .EXD-type files, or your RefEdit control has become corrupted somehow. More about the problem of corrupted .EXD files can be found in Lessan Vaezi's Delete EXD files to fix "Object library invalid" error, although the symptom mentioned there is different.

To fix the problem:

  1. Close Excel.
  2. Do a search on your system for any files whose names end in .EXD and delete them. We have confirmation from multiple Office 2010 users that this solution cleared the above error message for them.
  3. Try your advanced analysis in @RISK again. If it works, you can skip the rest of this procedure.
  4. If you still have the problem, the RefEdit control in Excel is the culprit. Please proceed as in "The macro 'AdvTools5.xla!TBSenseMain' cannot be found."

last edited: 2012-11-16

8.29. "Could not read data from file ...tmp."

Applies to: @RISK 7.0.0 only

When I open a particular file in @RISK, I get an error message similar to this one:

Could not read data from file C:\Users\Fred\Appdata\Local\Temp\Pal765.tmp.

Most files are okay; it's just this one that has a problem.

Was your file created in @RISK 5 or 6, and do you have simulation results saved? By design, @RISK 7 can read @RISK 5 and @RISK 6 simulation results, whether saved in the Excel workbook or in an external file. However, there's one exception. If the stored results were filtered with @RISK 5 or 6's Define Filter command, @RISK 7 can't read them correctly, and various kinds of problems may result, such as the above error message, or Excel crashing or hanging. If the results were not filtered, there's no problem reading them.

This exception was corrected in release 7.0.1. If you still have 7.0.0, and you have simulation results stored in an external RSK5 file, just move or delete it before opening the Excel workbook, so that @RISK doesn't find the results and try to read them. If results are stored in the Excel workbook, follow this procedure:

  1. Open the workbook in Excel, not @RISK. Save the workbook under a different name.
  2. Right-click on any worksheet tab, and select Unhide. Unhide the hidden sheets and delete them. (Excel only lets you unhide sheets one at a time.)
  3. Save the file and close Excel. Launch @RISK 7 and you'll be able to open the file.

Last edited: 2016-08-17

8.30. "Error calling the macro ..."

Applies to:
@RISK, all releases
Evolver, all releases

On the Macros tab of my model settings, I list one or more macros to be called during a simulation or optimization. But I get this popup after I click Start:

Error calling the macro "..."

I've checked carefully, and the macro name is spelled correctly in the settings dialog. What is wrong?

This is probably a matter of scoping in Excel.

When @RISK calls a macro by name, Excel looks for it in several places. Depending on just where you placed the macro, its name alone may not be enough for Excel to locate it. Please follow these simple rules for best results:

  • In Visual Basic Editor, put your code in a module, not inside a worksheet object. If you need to create a module, right-click on the workbook name and select Insert » Module.

  • On the Macros tab of the model settings, fully qualify the macro name, using the workbookname!macroname form, such as 'My Own Workbook.xlsm'!MyMacro. It's usually not necessary to fully qualify the name, but it never hurts, and sometimes it is required.

Only a Sub can be set to be called automatically by @RISK or Evolver, not a Function.

Last edited: 2015-12-03

8.31. "Invalid matrix location" when Defining Correlations

In @RISK, I click Define Correlations, add my inputs, set my coefficients, set the matrix location, and click OK. I get the error message

Invalid matrix location

The location I picked is all empty cells, and the address range is valid. What's the problem?

In Excel, click Formulas » Name Manager. You probably have one or more names pointing to #REF. This can happen when you define a correlation matrix in @RISK and then delete it in Excel, or in some scenarios when you delete worksheets or move worksheets between workbooks.

To solve the problem, delete all the names that point to #REF. You will then be able to define your correlation matrix.

To prevent the problem from recurring, don't delete correlation matrices in Excel. Instead, use the Delete Matrix button in the Define Correlations dialog. That will not only delete the matrix, but also delete the name in Name Manager and remove the references to the matrix from the @RISK distributions.

Last edited: 2016-08-26

8.32. "Method '~' of object '~' failed" (Quick Reports)

Applies to: @RISK 6.0 and 6.1

My simulation runs fine, but an attempt to generate Quick Reports fails with the message

Method '~' of object '~' failed

This is fixed in @RISK 6.1.2. If you have 6.0.0, 6.0.1, or 6.1.1, and you have current maintenance, please upgrade to the current release.

See also: There are other possible causes for this message. See All Articles about "Method '~' of object '~' failed".

Last edited: 2017-02-17

8.33. "Method 'Initialize' of object '_RiskOL' failed"

Applies to: @RISK 6.x/7.x

When I launch @RISK, I get this error message:

"Method 'Initialize' of object '_RiskOL' failed"

This could have several causes. The procedure below runs roughly from fastest to slowest. If you try @RISK after a given step and it now works, you can ignore the others.

  1. Please check your Excel add-ins: File » Options » Add-Ins in Excel 2007 and newer, Tools » Options in Excel 2003. @RISK may or may not be listed as an active add-in; it will work fine either way. But if any other @RISK components, such as RISKOptimizer, are listed as active add-ins then please make them inactive. (In Excel 2007 or newer, click the round Go button at the bottom of the right-hand panel to bring up the list of add-ins and remove the appropriate check marks.) After making any add-ins inactive, close Excel and try @RISK again.

  2. If you're running Excel 2013 or Excel 2016, click File » Options » General and remove the check mark from the last option, "Show the Start screen when this application starts." Click OK and close Excel.

  3. Temporarily deactivate all add-ins except those that come with Excel. Close Excel and re-launch @RISK to test it. If @RISK now works, you can add them add-ins back one at a time to find the culprit. There might even be more than one culprit, though this is not very likely.

    If @RISK still doesn't work, leave the other add-ins inactive while you continue with this procedure. It's possible that the problem is one or more add-ins plus one of the causes below. You can add them back when you have @RISK working again.

  4. Follow the procedure in Removing Outdated References to Office from the System Registry to check for outdated references, and remove them if they exist.

  5. Repair Microsoft Office.

  6. Repair @RISK, and if that doesn't work do a clean uninstall and reinstall. (You might wish to skip the repair and just do the clean install. We suggest a repair only because it's a lot simpler and a has a good chance of solving the problem.)

Last edited: 2016-03-29

8.34. "Object not initialized"

Applies to: @RISK 5.x–7.x, Professional and Industrial Editions

My VBA code referencing @RISK fails with "Object not initialized", "Object required", or another error message.

You need to create a reference to the proper @RISK object library in your VBA. Please see Setting References in Visual Basic for the necessary references and how to set them.

These references vary by version of @RISK. If you have macro code that fails now but worked in a previous version of @RISK, probably all you need to do is remove the reference to the old version and add the proper reference or references to the current version.

Last edited: 2015-10-15

8.35. "Object variable or With block variable not set"

Applies to:
@RISK for Excel 5.x–7.x
TopRank 5.7–7.x

When I click on an @RISK icon in the toolbar or ribbon, I get the error message

Object variable or With block variable not set

Or else, none of the ribbon buttons do anything, not even an error message.

This can be caused by manually adding the @RISK or TopRank toolbars. Never do that; instead, you should let our software manage them. Please run Excel and remove the toolbars that you manually added. The instructions vary according to your version of Excel:

  • In Excel 2007 or newer, click File » Options » Add-ins (or the round Office button and then Options » Add-ins). Look at only the active add-ins at the top of the page. If you see any "RiskExcel12" or "TopRankExcel12" add-in in the list, click Go at the bottom of the page, remove the check mark from that add-in, click OK, and close Excel.
    If no such add-in is in the active list, or if the problem persists after you remove the check mark, right-click into the toolbar and click Remove custom toolbar. You may have to try clicking different places in the toolbar until the right-click menu offers that option.

  • In Excel 2003 or older, click View » Toolbars, uncheck the @RISK and TopRank toolbars, then click into your worksheet to make the menu go away. Close Excel.

To prevent this problem in the future, always launch our software through the desktop icon, if available, or through the Windows start menu. Click the Windows Start button, then Programs or All Programs » Palisade DecisionTools and select the application you want. You can do this whether Excel is already running or not; our application will launch Excel for you if it's not already running.

See also: There are other possible causes for this message. See All Articles about "Object variable or With block variable not set".

Last edited: 2016-06-24

8.36. "The data in the workbook ... is invalid"

Applies to:
@RISK 5.x for Excel

Problem:
When I open my workbook in @RISK, I get the message

"The data in the workbook workbookname is invalid."

Response:
Most likely, your data from a previous simulation, stored in this workbook, are corrupt. To clear the error, please follow these steps:

  1. In @RISK's Utilities menu, select Clear @RISK Data.
  2. The Clear @RISK Data dialog box appears. Select "Simulation Results" and clear any marks that appear for the other options. Click OK and answer the confirming prompt.
  3. Save your workbook.

Did you actually intend to store simulation results in the workbook? There are certainly valid reasons to do that, but the tradeoff is that your workbook grows larger and that can slow down your simulations. For other ways to store your simulation results, please see Excel Files with @RISK Grow Too Large.

last edited: 2010-05-20

8.37. "The function DtoolsVersion did not register properly."

Applies to:
@RISK 5.5.1 only

Problem:
While @RISK is shutting down, I get these three error messages:

The function DtoolsVersion did not register properly. Probably an argument description is too long.

The function WorkerThread did not register properly. Probably an argument description is too long.

The function ExtractLibraryDataToWorksheet did not register properly. Probably an argument description is too long.

What is wrong?

Response:
If these messages appear during the shutdown sequence of @RISK, just click OK on them. There is no cause for concern; this is diagnostic reporting that was not intended to be visible but does appear in a few rare configurations.

The messages do not appear in @RISK 5.7 and later.

last edited: 2011-01-05

8.38. "The macro 'AdvTools5.xla!TBSenseMain' cannot be found."

Applies to:
@RISK for Excel 5.0 and 5.5 only

Problem:
When I try to launch advanced sensitivity analysis, I get the error message

The macro 'AdvTools5.xla!TBSenseMain' cannot be found.

or a similar message. (Some users get "System error &H80004005 (-2147467259). Unspecified error" before that message.)

Solution:
Somehow your RefEdit control has become corrupt. This control is part of Microsoft Office, not part of @RISK. (Excel's Conditional Sum Wizard uses it, among others.)

If you are eligible to upgrade to the current version of @RISK, this is the simplest solution. Although this is not a bug in @RISK, it happens that @RISK 5.7 and later no longer use the RefEdit control, so by upgrading you avoid the problem.

If you are not eligible to upgrade, the workaround is to take a copy of RefEdit.dll from the same version of Excel on a known good computer, one where Advanced Sensitivity Analysis launches successfully:

  1. On your computer, close Excel if it is open.
  2. Open My Computer and navigate to C:\Program Files (x86)\Microsoft Office or C:\Program Files\Microsoft Office.
  3. Open the OFFICEnn folder under the Microsoft Office folder (OFFICE14 folder for Office 2010, OFFICE12 for Office 2007, OFFICE11 for Office 2003, and so on).
  4. Rename the existing RefEdit.dll to RefEdit_dll.bak, just in case you need to recover it.
  5. Put the copy of RefEdit.dll from the known good computer into the folder.
  6. Do a search on the C: drive for RefEdit.exd and delete all copies or rename them to RedEfit_exd.bak.
  7. Run a repair of Office by following the procedure in this article.

last edited: 2011-03-22

8.39. "The standard edition of RISK may not be automated."

Applies to: @RISK 5.x–7.x, Standard Edition

When I execute a macro or user-defined function involving the 'Risk' object, I get this popup:

Run-time error '-21472211485 (80040013)':
The standard edition of RISK may not be automated.

What is wrong? 

Automation features (using the Risk object in VBA) are supported in @RISK Industrial and Professional Editions, but not in @RISK Standard Edition.  If you would like to use the automation features of @RISK, please contact your Palisade sales manager for assistance in upgrading your license.

Additional keywords: XDK

Last edited: 2015-10-15

8.40. "The workbook ... has @RISK simulation settings stored in it. ...

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

When I open certain Excel files, I get the message

The workbook workbookname has @RISK simulation settings stored in it. Do you want to change the current @RISK settings to match those stored in this workbook?

What does this mean? How can I avoid the message?

The message is telling you that the workbook you're about to open has simulation settings inconsistent with the currently open workbook. (If you have only a blank workbook open, then the settings in the new workbook are inconsistent with your simulation defaults in Application Settings.) @RISK wants you to decide which set of settings should be in effect for both workbooks, since all open workbooks must have the same settings.

In general, you don't want to have multiple workbooks open in @RISK unless they are all needed for the same simulation. Therefore, the best practice is usually to close workbook A before you open workbook B. If you have workbook A open with @RISK settings, and you're opening workbook B with different @RISK settings, you probably want to answer Yes, then close workbook A without saving it. If you have made changes in workbook A that you don't want to lose, say No and close workbook B without saving (so that its simulation settings won't change); then save and close workbook A and reopen workbook B.

You may be able to eliminate or at least reduce these warnings by adjusting your Application Settings, if you always make the same choices for all models. That is the simplest and safest approach. For more information, please see Avoiding "Do you want to change the current @RISK settings to match those stored?"

Last edited: 2015-10-15

8.41. "These simulation results cannot be opened."

Applies to: @RISK 6.x/7.x

When I try to open an Excel workbook with saved simulation results, I get the error message

These simulation results cannot be opened. They appear to have been saved in another language version of Microsoft Excel or with different Microsoft Windows Regional Settings.

My colleague has no problem opening the same file. Why won't it work for me?

To open saved simulation results, you need to have your Excel and Windows regional settings the same as the person who ran the simulation and saved the results.

If you need those specific results, you will need to change your regional settings (Control Panel » Region and Language) before opening @RISK. If you don't need those specific results, just click OK and run a new simulation.

Last edited: 2015-10-15

8.42. "Type mismatch" Prevents Distribution Fitting

Applies to: @RISK 7.0.0–7.5.0, Professional and Industrial Editions

I'm trying to fit distributions to my data, but as soon as I click Distribution Fitting » Fit, I get this error popup:

Type mismatch

The dialog box never appears.

This is a known problem with the @RISK releases mentioned above, but it's rare: only two customers have reported it as of 2017-02-13, when this article as written.

The issue is that somehow—we don't know how—the list of distributions to fit in the System Registry has been changed to the eight characters <<NULL>>. The fitting dialog reads this invalid value and doesn't know what to do with it. This problem was first reported after 7.5.0 was released, and was corrected in 7.5.1.

To resolve the problem, do any one of the following:

  • Solution 1: If you have current maintenance, upgrade to the current version of @RISK or the DecisionTools Suite.

  • Solution 2: With @RISK not running, open REGEDIT and navigate to this key:
    HKEY_CURRENT_USER\Software\Palisade\@RISK for Excel\7.0\Application Settings\Fitting Defaults
    In the right-hand panel, double-click Distributions and change it to the string
    {Default}
    Include the curly braces around the word Default. Close REGEDIT and run @RISK.

  • Solution 3: In the GUI of @RISK, click Utilities » Application Settings » Fitting Defaults. To the right of Distributions to Fit, you'll see the word Custom. Click on that word and tap the Delete key; Custom will change to Automatic. Click OK, answer the confirming prompt if there is one, and either close Excel or shut down @RISK. (Application settings aren't written to the Registry until @RISK shuts down.)

Last edited: 2017-02-13

9. BigPicture

9.1. BigPicture Doesn't Show in Ribbon, or Gets Error 53

Applies to: BigPicture 1.x or 7.x

I start BigPicture normally (double click on the desktop icon, or via the Start menu) and it seems that it loads. But I can't find a BigPicture tab on the Excel ribbon.

Or, when I try to launch BigPicture I get this error message:

Run-time error '53':
File not found: BigPicture1_x64.xll

or

Run-time error '53':
File not found: BigPicture1_x86.xll

The other tools in the DecisionTools Suite work just fine.

If our other tools have the same problem, please see @RISK Initializes, But No Tab Appears in Ribbon.

If the other tools launch successfully, and this problem is specific to BigPicture, did you have a beta of BigPicture or the DecisionTools Suite before installing the final release?  If you did not install a beta before the final release, please contact Palisade Technical Support for assistance.

If the problem affects only BigPicture, and you did have a beta version before installing the final release, then it's possible the BigPicture or DecisionTools Suite installer couldn't update some entries for BigPicture created in your System Registry by a previous install. To solve this issue, upgrade to the current version of BigPicture or the DecisionTools Suite. If you can't upgrade, or if you have upgraded and the problem remains, follow this procedure:

  1. Make sure you are logged in to Windows with a full administrator account.

  2. Click the Windows Start button and type regedit but don't press the Enter key. In the search results above, right-click Regedit or Regedit.exe and select Run As Administrator.

  3. Navigate to HKEY_LOCAL_MACHINE\Software\WOW6432Node\Palisade (in 32-bit Windows, HKEY_LOCAL_MACHINE\Software\Palisade) and if necessary click the triangle or + sign to expand it.

  4. You will need to take control of BigPicture and each of its subkeys. To begin, click the triangle or + sign at the left of BigPicture to expand it, and repeat until you have expanded all subkeys.

  5. Right-click BigPicture and select Permissions.

    In Windows 8 and newer:

    1. In the Group or user names box, your Windows user name or group name should be showing. If it's not, click Add » Advanced » Find Now, pick your account or group name from the list, and click OK twice.
    2. Click once on your user name or group name under Group or user names. Then, under Permissions for that name, put a check mark under Allow on the Full Control row.
    3. Click the Advanced button to bring up the Advanced Security Settings dialog. If you see an Enable inheritance button near the bottom left, click it.
    4. Still on Advanced Security Settings, the owner is shown above the tabs. If it's you or SYSTEM, continue at step e below. Otherwise, click Change next to the name and select your account or group. If your account or group isn't in the list, click Advanced » Find Now, pick your account or group, and click OK twice.
    5. Save changes by clicking OK on the Advanced Security Settings dialog, and again on the Permissions dialog.
    6. Press the F5 key to refresh the display, and continue at step 6 below.

    In Windows 7 and older:

    1. In the Group or user names box, your Windows user name or group name should be showing. If it's not, click Add » Advanced » Find Now, pick your account or group name from the list, and click OK twice.
    2. Click once on your user name or group name under Group or user names. Then, under Permissions for that name, put a check mark under Allow on the Full Control row.
    3. Click the Advanced button to bring up the Advanced Security Settings dialog. Near the bottom, there should be a check mark for Include inheritable permissions from this object's parent. If necessary, click to set that option.
    4. Click the Owner tab. If the current owner is you or SYSTEM, continue at step e below. Otherwise, select your account or group. If your account or group isn't in the list, click Advanced » Find Now, pick your account or group, and click OK twice.
    5. Save changes by clicking OK on the Advanced Security Settings dialog, and again on the Permissions dialog.
    6. Press the F5 key to refresh the display.
  6. Right-click the first subkey under BigPicture and select Permissions. Repeat steps a through f to take control of that subkey. Continue until you have performed steps a through e on every subkey under BigPicture.

  7. If there is a 6.0 subkey under BigPicture, delete 6.0 and all of its subkeys.

Everything should now work as expected.

If you don't feel comfortable editing your System Registry, please ask your IT department to follow these instructions for you.

If you have no IT department, and if you have current maintenance, you can phone Palisade Technical Support at +1 607 277-8000, menu 5, to join a GotoAssist session where we will perform these edits for you. Before phoning us, please ascertain that:

  • Your organization allows you to participate in remote support sessions such as GotoAssist.
  • You are at your computer and logged in with full administrative rights.
  • You have your BigPicture or DecisionTools Suite serial number available. With the DecisionTools Suite, run one of the tools other than BigPicture, click Help » About, and note your serial number (S/N). With BigPicture alone, please get your serial number from the email you received when you bought the software.

Last edited: 2016-07-13

9.2. "Initialization Error: Localization.ProductLanguage"

Applies to: BigPicture 1.0 and 2016

When I try to launch BigPicture, I get the message

Initialization Error: Localization.ProductLanguage
Contact Palisade Technical Support for more information.

For some reason, a particular registry key was not set correctly, possibly because of interference from an old beta version. You can easily fix it, as follows:

  1. Close all instances of Excel.
  2. Launch REGEDIT (requires admin rights).
  3. Navigate to HKEY_CURRENT_USER\Software\Palisade\BigPicture\1.0.
  4. In the right-hand panel, in the first column (under Name), look for Language and double-click it.  In the edit box that opens, change the value data from Default to English.

Last edited: 2017-03-01

10. Evolver and RISKOptimizer

10.1. Evolver or RISKOptimizer Doesn't Find Best Solution

Applies to:
Evolver, all releases
RISKOptimizer or @RISK Industrial Edition, all releases

When I run Evolver or RISKOptimizer, it runs for a long time but doesn't come up with a good solution. (Or, it doesn't come up with any solution.)

It's possible that your model is very complex and will take a long time. For best results, have a look at For Faster Optimizations for some suggestions. Also, in Optimization Settings (release 6.0 and newer), make sure that the engine is set to Automatic.

We have seen a very few models make better progress when the optimization is stopped and re-started from that point.

The rest of this article applies only to optimizations that use the Generic Algorithm. With 6.x and newer, the Genetic Algorithm is available — it's used instead of OptQuest if you specify it, or if you leave the Engine set to Automatic and the optimizer decides that the Genetic Algorithm will be more efficient. With releases 1.0–5.7, the Genetic Algorithm is always used.

With the Genetic Algorithm, the initial values of adjustable cells can be crucial. One common mistake is starting off with a constraint violation. Details:

In Evolver and RISKOptimizer you set up constraints. As the program tries each new set of adjustable variables, it checks to see if the constraints are met, and if they're not then it backs up to values that do meet the constraints. For a nice picture of this, open the Evolver or RISKOptimizer Help file, click the Search tab, search for backtrack, and in the results select Constraints.

If you start the program off with the adjustable variables not meeting constraints, then the program has no valid trial to back up to. It spends a lot of time blundering around till it gets lucky and hits on a valid solution. For example, you might have a constraint that a range of cells must be between 1 and 100, but then you start with 0 in all the cells, figuring that the program will make the adjustment. It will, eventually. But solution is a lot more efficient—a LOT more—if you start the program off with all constraints met.

In Evolver and RISKOptimizer releases 5.5 and later, you can use Constraint Solver to help you find an initial feasible solution.

During optimization, try adjusting the operators, crossover, or mutation. The advantage of the Genetic Algorithm over LP/NLP (such as used in Solver) is that it can find a global as opposed to a local optimum. But if the program makes initial progress and then seems stuck, you may need to re-run the optimization with more operators selected and perhaps change the mutation rate to "auto". With mutation set to "auto", you can watch the rate change in the Watcher Summary tab: it gets increased if the optimization is not making progress, and once it starts making progress it gets decreased again.

See also:

Last edited: 2015-10-15

10.2. Optimization Makes Faster Progress if I Stop and Restart It

Applies to:
Evolver 6.x/7.x
@RISK Industrial Edition 6.x/7.x

My model seems to make progress faster if I stop and restart it periodically than if I just let it run.

Specifically, the progress window shows the value of the target cell improving rapidly at first, then improvement becomes progressively slower.  If I stop the optimization, saving best values to the workbook, then restart it, progress is rapid again but after a while it again slows down.  If I don't stop and restart the optimization, but just let it run, progress just gets slower and slower.

This is related to your particular model and is not expected behavior for most models.

You've observed that restarting the optimization accelerates the optimization process.  (We say "accelerates", because for all we know it would eventually get to the optimal solution with a single optimization.)  Whether we're talking about the Genetic Algorithm or OptQuest, the optimization algorithm has to make guesses that certain regions of the solution space are not worth pursuing (or not worth pursuing too often).  Apparently in the case of this problem these guesses are often wrong, and it helps to throw them away every now and then.

So why doesn't it restart itself internally, to make the optimization faster?  Because it doesn't know that it would help in this particular problem.  And for most problems such restarts would be counterproductive, losing the memory of largely correct guesses that the algorithm has made so far.

To accommodate this particular problem, you can write a macro using the Evolver or RISKOptimizer XDK (Visual Basic interface) to keep restarting the optimization.  Here is some sample code for Evolver; RISKOptimizer code would be similar.  Please see Setting References in Visual Basic for the appropriate references and how to set them.

Public Sub MultipleOptimizations()
   Dim i As Long
   For i = 1 To 5
      Evolver.Optimize
   Next i
End Sub

Last edited: 2015-10-15

10.3. Efficient Frontier Doesn't Allow an '=' Constraint

Applies to:
Evolver 7.x
@RISK 7.x Industrial Edition

When I've selected Efficient Frontier and try to edit my constraints, I can select an "=" constraint, but the software changes it to <=.

This is a limitation of the underlying algorithms in the OptQuest engine. You can have a <= or >= constraint, but no = constraint for a value or list of values. (Efficient Frontier runs in OptQuest only, not in the Genetic Algorithm.)

This limitation apples only to the Efficient Frontier analysis type.  With the Standard analysis type, all five constraint types <, <=, =, >=, and > are available, in both the OptQuest engine and the Genetic Algorithm.

Last edited: 2017-05-30

10.4. "Error in loading DLL" (at Start of Optimization)

Applies to: Evolver 6.x/7.x

Evolver appears to start fine, and I'm able to create my model and settings. But when I click the button to start optimization, I get this message:

Error in loading DLL

This is a System Registry problem that also prevents @RISK and PrecisionTree from loading at all. For the solution, please see "Error in loading DLL" (at Startup).

Last edited: 2015-10-15

10.5. "Specified optimization settings are not supported with OptQuest."

Applies to:
Evolver 6.x/7.x
@RISK Industrial Edition 6.x/7.x

When I click the Start button, I get this popup message:

Specified optimization settings are not supported with OptQuest.

Which of my settings does OptQuest have a problem with?

It's not actually optimization settings, but your model definition. There are two possibilities:

  • The Grouping method is selected and All Groups Must Be Used is checked (ticked).

  • The Order method is selected for two or more adjustable cell groups, meaning that the optimization requires two or more separate permutations.

In both of these cases, if you have selected Settings » Engine » Manual » OptQuest you'll see this message, and the optimization will not proceed. If you have selected Settings » Engine » Automatic, which is the default, the optimization will use the Genetic Algorithm and you won't see this message.

Last edited: 2015-10-16

10.6. "With integer adjustable cells, the OptQuest optimization engine requires ..."

Applies to:
Evolver 6.x/7.x
@RISK Industrial Edition 6.x/7.x

When I click the start button for my optimization, this message pops up in 7.x:

With integer adjustable cells, the OptQuest optimization engine requires at least two integer values within the range of minimum to maximum (inclusive). Either change the adjustable cell definitions or try the Genetic optimization engine.

In 6.x, it's this message:

With integer adjustable cells, the OptQuest optimization engine requires at least two integer variables in the range of permitted values. It may be possible to use the Genetic optimization engine with the current adjustable cell definitions.

What is wrong, and how do I fix it?

The message is trying to tell you that some or all of your adjustable cells are constrained to be integers, and one or more of those integer adjustable cells have minimum and maximum too close together. For example, if minimum is 0 and maximum is 0, the only possible value that meets constraints is 0.  Similarly, if minimum is 0.5 and maximum is 1.5, the only possible integer value that meets constraints is 1.  But a cell with only one possible value can't really be called an "adjustable" cell, and OptQuest won't allow this. You can apply either of two solutions.

Solution 1:
For the cells where minimum and maximum are too close together, either remove them from the list of adjustable cells or change the definition so that the range [minimum;maximum] includes at least two integer values.  Examples: 0 to 1 (includes integers 0 and 1), or 0.5 to 2.5 (includes integers 1 and 2).

Solution 2:
The Genetic algorithm will usually run with your existing model definition, ignoring the cells where minimum equals maximum and varying the other adjustable cells. (It may take more or less time than OptQuest and may reach a different solution, depending on your model.) To select the Genetic algorithm in Evolver or Optimizer, click Settings » Engine » Manual and if necessary select Genetic.

Last edited: 2015-10-15

11. NeuralTools

11.1. Different Results from Training Same Data

Applies to: NeuralTools 5.x–7.x

I trained a net and saved the training report. Then I experimented with changing settings and retraining, but I didn't like the results. So I changed the settings back to the original and retrained, but the training got different results even though the data were exactly the same.

By default, the testing subset is selected differently during each training session, so the results will not be the same. The fewer cases you have, the more variation in results you should expect, all else being equal. See Recommended Amount of Data.

You can freeze the selection of the testing subset by using the setting "Select Same Cases as Long as This Number is the Same" in the middle of the Train tab on the Training dialog.

Last edited: 2015-10-15

11.2. "This key is already associated with an element of this collection"

Applies to:
NeuralTools 6.x/7.x
StatTools 6.x/7.x

When I try to run Data Set Manager or train my network, I get the error message

This key is already associated with an element of this collection

There are a number of hidden worksheets in your workbook, and they are confusing NeuralTools. To resolve this, make the worksheets visible and delete them:

  1. Right-click on any worksheet tab at the bottom of the Excel window, and select Unhide. Choose any worksheet in the list that appears.
  2. When that worksheet becomes visible, right-click its tab, select Delete, and answer Delete to the confirming prompt.
  3. Repeat until there are no more hidden worksheets.
  4. Save the file under a new name. Close Excel, reopen NeuralTools or StatTools, and open the newly saved file.

You can then open Data Set Manager, re-establish the data set, and perform your training or analysis.

Last edited: 2017-02-15

12. PrecisionTree

12.1. Context Menu Wrong in PrecisionTree 6.x and 7.x

Applies to: PrecisionTree 6.x/7.x

When I right-click on a node, the Excel menu opens, not the PrecisionTree menu. It looks like somehow all the nodes have just become Excel shapes.

PrecisionTree uses a hidden name to keep track of the tree objects. It seems you copied a worksheet from another PrecisionTree workbook, after creating the tree in this workbook. When you did that, Excel recognized that there was a conflict of these hidden names. It should have asked you whether to replace one with the other, or keep both. If you answered to keep both, then they're both in the workbook. PrecisionTree uses the first one it finds, which happens to be the wrong one; hence PrecisionTree doesn't know that your tree is a tree.

To solve the problem, follow these steps:

  1. Delete the sheet that was copied from the other workbook.
  2. Save the workbook and close Excel.
  3. Reopen the workbook in PrecisionTree.
  4. Either rebuild the deleted sheet from scratch, or insert a blank sheet and then copy the contents of the sheet from the other workbook without copying the actual sheet.

Last edited: 2015-10-19

12.2. Context Menu Wrong in PrecisionTree 5.5

Applies to: PrecisionTree 5.5 with Excel 2007
(For later PrecisionTree versions, see Context Menu Wrong in PrecisionTree 6.x and 7.x.)

When I right-click on a node, I get the Excel menu instead of the PrecisionTree menu. What is wrong? If I left-click the node, the expected PrecisionTree dialog comes up, so I know PrecisionTree is running.

Have you split the window pane? There is a bug in Excel 2007, triggered by the split pane. If you go to the View tab of the ribbon and remove the split, the right-click menus for PrecisionTree return.

This bug affects PrecisionTree 5.5.0 and 5.5.1; it was fixed in 5.7. It occurs only in Excel 2007, not in Excel 2003 or 2010.

Last edited: 2012-11-20

12.3. #VALUE in Tree with Utility Function

Applies to: PrecisionTree 5.x and newer

My tree seems okay when I'm just doing regular calculations. but when I switch to using a utility function, some of the branches' values change to #VALUE.

This depends on the tree, your utility function, and your R value, but basically one or more of your branch values leads to a forbidden mathematical operation. The attached workbook shows two simple trees with this problem. To see what's going on with each tree, you may find it helpful to open Model Settings, select the Utility Function tab, and change display to Expected Utility.

Depending on your utility function, here are some hints on what to look for.

Suppose you are using the built-in Exponential utility function,

U = 1 − exp(−$/R)

You won't have a problem displaying Expected Values, but you may have a problem with Certainty Equivalents. For greater and greater positive branch values, this function gets closer and closer to 1. If the Expected Utility of any node displays as 1, it isn't actually 1, but the difference between the utility and 1 is too small to be represented in double precision arithmetic. Thus the utility function treats the utility of any sufficiently large branch value (relative to R) as equal to 1. But what happens if you try to compute the Certainty Equivalent? That's the inverse of the utility function, namely

$ = −R ln(1 − U)

If the utility is indistinguishable from 1, then you're trying to take the logarithm of 0, which can't be done, so you get #VALUE. Essentially you're saying that your risk tolerance is greater than any of the possible negative outcomes on this branch of the tree. Mathematically, a larger R would resolve the #VALUE error, but it way not be a good representation of your risk tolerance. (For example, an R of 3000 would prevent #VALUE errors in the attached example.)

Next, consider the built-in Logarithmic utility function:

U = ln($ + R)

Since the argument to the logarithm function must be positive, all branch values must be > −R. For example, if R is 100 then no branch values can be −100 or lower (more negative). If you display Expected Values and all probabilities are #VALUE, you have this problem. If you can't locate the problems, change display to Expected Utility and then look for #VALUE among the branch values. Either change them or change the R value, as appropriate. (#VALUE for probabilities should resolve themselves when you fix the branch values.)

If you've written a custom utility function, look at the computations involved in that function and its inverse, and make sure that none of your branch values lead to any forbidden mathematical operations. Consider adding some code to these functions to display a specific message if a problem value is encountered.

See also: Utility Functions.

Last edited: 2015-11-24

12.4. "Decision Tree ... exceeds the size limit of the professional edition."

Applies to: PrecisionTree 5.x–7.x, Professional Edition

When I open my tree, I get this message in Excel's status bar:

PrecisionTree: Decision tree 'name' exceeds the size limit of the professional edition of PrecisionTree. [ALT+F10]-Goto [ALT+F12]-Error Dialog

Pressing Alt+F10 takes me to the root of the tree, and Alt+F12 displays the same message in a dialog box.

In the Professional Edition of PrecisionTree, the size of any one tree is limited to 1000 nodes. If you're not sure how many nodes you have, an easy way to check (if you haven't inserted rows through Excel's Insert command) is to take the last Excel row number in the tree, subtract the first row number in the tree, add 1, and divide by 2. For example, if your tree uses Excel rows 15 through 2744, you have 2744–15+1 = 2730 rows in your tree, and 2730/2 = 1365 nodes.

You can simplify repetitive branches of decision trees by replacing them with reference nodes that point to a single subtree. This will probably make your tree more easy to understand and maintain, but it won't evade the 1000-node limit. The number of nodes in a subtree counts against the limit for each point where the subtree is attached to the main tree or referenced in a reference node.

If you need to work with trees larger than 1000 nodes, please contact your Palisade sales manager to upgrade your DecisionTools Suite or PrecisionTree license to the Industrial Edition, which has no limit on tree sizes.

But my message is

Influence Diagram 'name' exceeds the size limit of the professional edition of PrecisionTree.

My influence diagram has well under 1000 nodes.

The 1000-node limit applies to the number of nodes that would exist in a decision tree created from that influence diagram. A decision tree can be much, much larger than the influence diagram it was created from, because the number of nodes in the decision tree increases roughly as a power of the size of the influence diagram. (Looking at it another way, an influence diagram is very compressed, and the corresponding decision tree is much larger because every possibility is spelled out in a unique path.) Thus, even an influence diagram of a dozen nodes could exceed the decision-tree limit.

Contact your Palisade sales manager to upgrade to the Industrial Edition, which has no limits on the size of influence diagrams or decision trees.

Last edited: 2016-09-19

12.5. "Object variable or With block variable not set" (PrecisionTree 1.0)

Applies to: PrecisionTree 1.0 only

When I try to edit a node, I get the message

Run-time error '91':
Object variable or With block variable not set

This comes from editing the tree using Excel edits, such as Ctrl-C and Ctrl-V. It's important to edit a tree using only PrecisionTree facilities.

Unfortunately, once the tree reaches this state of corruption it can't be repaired. The only way to fix the error is to close Excel, reopen PrecisionTree, and build up the tree in a fresh workbook.

See also: There are other possible causes for this message. See All Articles about "Object variable or With block variable not set".

Last edited: 2016-02-23

12.6. "PrecisionTree has detected ... a workbook saved in Excel 2000-2003 format"

Applies to: PrecisionTree 5.7 and newer in Excel 2010 or newer

I have Excel 2010, 2013, or 2016, and I opened a PrecisionTree model that is in .XLS format. I get this message:

PrecisionTree has detected that you have opened a workbook saved in Excel 2000-2003 format which is not 100% compatible with the current version of Excel. PrecisionTree can automatically correct this problem by shutting down and reopening the workbook a second time. Choose 'Yes' to allow this operation. (If you resave this model in the current Excel format, you will not see this message again.)

Why is this message appearing, and what should I do about it?

In Excel's Advanced options there is a setting "Cut, copy, and sort inserted objects with their parent cells". PrecisionTree turns that property off, so that you can perform certain types of edits without corrupting the model. Unfortunately, if you open an .XLS workbook in Excel 2010 while that property is turned off, shapes are liable to be corrupted anyway. This is purely an Excel 2010 issue, which can occur even when PrecisionTree is not loaded.

To work around the problem, PrecisionTree simply needs to reopen the workbook while that property is turned on, then turn the property off again. Why does it display the prompt, rather than just silently do that? Because if your workbook is passworded, you will get another prompt for the password. Or, if you have macros set to perform certain actions when the workbook is opened, they will get performed a second time; and so on.

How do you prevent the prompt? This issue occurs only when opening .XLS files in Excel 2010. Therefore, if you simply save your file in .XLSX format (or .XLSM if it contains macros), and then use the new format instead of the .XLS format, you will never see the warning again.

Last edited: 2015-10-19

12.7. "This would cause the model to exceed the maximum of 5000 nodes. ..."

Applies to: PrecisionTree 6.x/7.x

When I try to paste a subtree or add a node, I get this message:

This would cause the model to exceed the maximum of 5000 nodes in a single decision tree.

You can bypass this limit by using subtrees and reference nodes. Please see Size Limits in PrecisionTree.

Last edited: 2015-10-20

12.8. "Type mismatch" when Chance Node Probabilities Don't Total 100%

Applies to: PrecisionTree 7.5.0 only

I'm using the "Chance Probabilities Must Total 100%" calculation method in my decision tree. When I click on a chance node and set probabilities that don't total 100%, I get the error message

Type mismatch

After that, subsequent operations fail with "Object variable or With block variable not set", "ActiveX component can't create object", or similar messages. I have to close Excel and reopen PrecisionTree.

This is unfortunately a bug in PrecisionTree 7.5.0. It has been fixed in PrecisionTree 7.5.1. f you still have 7.5.0, click Help » Check for Software Updates to obtain the current release.

Last edited: 2016-10-25

12.9. "Type mismatch" with Linked Node (PrecisionTree)

Applies to: PrecisionTree 7.5.0 only

I'm using the linked calculation method in my decision tree. When I click on a node and attempt to select a cell to link to, I get the error message

Type mismatch

This is unfortunately a bug in PrecisionTree 7.5.0. It has been fixed in PrecisionTree 7.5.1. f you still have 7.5.0, click Help » Check for Software Updates to obtain the current release.

Last edited: 2016-10-25

13. StatTools

13.1. Kurtosis Different from Excel's Computation

Applies to:
StatTools, all releases
@RISK, all releases

StatTools calculated a kurtosis of 3.72 for my data set, but Excel's KURT( ) function calculated 0.72. Is StatTools wrong, or Excel?

They're both right, because they're measuring slightly different things. The standard computation of kurtosis gives a value of 3 for a normal distribution, and StatTools follows that computation. But you may want to know how your distribution's kurtosis compares to a normal distribution. Subtract 3, the kurtosis of a normal distribution, from the kurtosis of your distribution, and you have the excess kurtosis.

(excess kurtosis) = (kurtosis) – 3

If your distribution has a kurtosis of less than 3, it has a negative excess kurtosis and is called platykurtic; if your distribution has a kurtosis greater than 3, it has a positive excess kurtosis and is called leptokurtic.

Excel's KURT( ) function computes the excess kurtosis, not the kurtosis, and so it will always return a value 3 less than the StatTools value.

The above also applies to iteration data in @RISK. @RISK reports kurtosis for inputs and outputs. If you apply Excel's KURT( ) function to the iteration data for an input or output, you'll get a value 3 less than 2hat @RISK reported, because @RISK computes kurtosis and Excel computes excess kurtosis.

Last edited: 2016-03-17

13.2. Regression Dialog Too Large for Screen

Applies to: StatTools 6.2.1 and older

When I try to do a regression in StatTools, the dialog box is too large for the screen, and I can't get to the OK button.

This is a known problem with low-resolution screens, those with height 600 pixels or less.  If you can, increase your screen resolution.

If you can't increase the screen resolution, or you prefer not to, you can use the StatTools keyboard shortcuts to fill in fields you can't see and to activate the OK button. The shortcut keys are the underlined letters.

Please refer to the attached snapshot of the StatTools 6 regression dialog. (The snapshot has been resized to fit better in this article; if you want to see it full size, right-click it and select "new window".)

For example, "Residuals vs X-Values" has the letter V underlined. To place or remove a check mark in that box, press Alt-V. "Confidence Level" has the letter O underlined. To set the confidence level, press Alt-O and enter the desired level with per cent sign (%), and press the Tab key, not Enter.

When you are ready to "click" the OK button, press the Enter key.

Last edited: 2014-04-15

13.3. StatTools Crashes On Most Menu Selections

Applies to:  StatTools 6.x/7.x

The StatTools ribbon looks normal, but when I click on Data Set Manager the program crashes with "Microsoft Excel has stopped working". I can click the drop-down arrows to display sub-menus, but when I select any of those items the same thing happens. However, the Chi-square test under Statistical Inference works fine.

Most StatTools dialogs use the SharpGrid control, and your SharpGrid control is probably not working correctly. To remedy this, see No Distributions in Define Distributions Dialog.

Last edited: 2015-10-20

13.4. Data Set Manager Shows No Variables

Applies to:
StatTools 6.x/7.x

I click into my data and then click Data Set Manager. A prompt asks if I want to create a new data set, and I click Yes. But Data Set Manager shows no variables, just a gray background where the list of variables should be. If I open Data Set Manager in a file that already has a data set, it also fails to display the variables.

You may have a non-default value for Data Execution Prevention (DEP). Please follow the WMIC and BCDEDIT instructions in Part A of this article.

Last edited: 2016-12-30

13.5. "Must have at least two more data points than independent variables."

Applies to: StatTools 6.x/7.x

When I click OK in the Regression dialog, I get the message

Must have at least two more data points than independent variables.

That doesn't make sense to me. If I have m independent variables and m+1 points, why doesn't the regression just solve m+1 equations in m+1 unknowns to find the coefficients of the m variables plus the constant term?

Let's define
m = number of independent variables
p = number of data points

Yes, if p = m+1 you can directly solve for the constant term and the m coefficients of independent variables, but that's not really a regression analysis. If you just compute a direct solution in this case, you have a perfect fit for those m+1 points, but you don't know anything at all about how that equation would work with any other values of the independent variables.

StatTools regression is a statistical procedure to find the best set of m coefficients plus constant term, so that the resulting equation does the best possible job of predicting the dependent variable for all values of the independent variables. This works better with a large set of points — one rule of thumb is p ≥ 10·m. (Princeton University suggests p ≥ 20·m ideally, but no lower than 5·m.) The fewer data points you have, the larger the standard errors for the coefficients and the poorer your equation will do at predicting values of the dependent variable. Mathematically, the absolute minimum number of data points is p = 2+m, because the number of degrees of freedom in ANOVA is df = pm−1, and df must be greater than zero. (See the help topic "Regression Command" in StatTools for more about how StatTools does a regression.)

Last edited: 2016-07-29

13.6. Data Set for Predictions Can't Be the Data Set for Regression

Applies to: StatTools 6.x/7.x

I'm doing a regression in StatTools. On the Options tab, I tick the box Include Prediction for Data Set, and click OK. This message pops up:

The data set where the predictions will be made cannot be the data set used to perform the regression.

What is wrong?

As the message says, if you want to use the results of the regression to do predictions, then you need two data sets.

You specify the regression data set on the Variables tab of the Regression dialog, or on the second screen of the wizard. The regression data set contains your independent and dependent variable data.

If you want to use that regression to predict values of the dependent variable for sets of values of the independent variables, you specify the prediction data set on the Options tab of the Regression dialog. The prediction data set must be a second data set; it can't be the same as the regression data set.  The prediction data set must contain the same independent and dependent variables that you're using in the regression. After computing the regression, StatTools will use the regression equation to predict dependent variable values for the independent variable values in the prediction data set.

Last edited: 2017-03-29

13.7. "This action cannot be performed because the Transition Formula Evaluation option is selected ..."

Applies to: StatTools 5.x–7.x

When I select Summary Graphs » Scatterplot I get the error message

This action cannot be performed because the Transition Formula Evaluation option is selected for worksheet name in workbook name

The Transition Formula Evaluation option is not a general Excel option, but one that can be set for individual workbooks. To reset that Excel option in this workbook, follow this procedure.

  1. Open the file, if it's not already open. (It doesn't mater whether StatTools is open or not.)

  2. Navigate to the Lotus Compatibility Settings.

    • Excel 2010, 2013, 2016: Click File » Options » Advanced. Scroll to Lotus Compatibility Settings.
    • Excel 2007: Click the round Office button, then Excel Options » Advanced. Scroll to Lotus Compatibility Settings.
    • Excel 2003: Click Tools » Options » Transition and look at the Sheet Options section.
  3. (Excel 2007 and newer) Next to "Lotus Compatibility Settings for", select the worksheet mentioned in the error message.

  4. Remove the check mark at "Transition formula evaluation".

  5. Click OK.

  6. Save the file.

You will now be able to create your scattergram.

Last edited: 2015-10-19

14. TopRank

14.1. "No outputs or inputs to display"

Applies to:
TopRank 5.x

Problem:
When I open my Model Window, I get the message

No outputs or inputs to display

Response:
You have some characters in your Excel names that are not in the Western European (ISO-8859-1) character set, such as Greek letters. This bug has been noted for fixing in a future release.

Here is the workaround:

In Excel 2000 to 2003, click Insert » Name » Define; in Excel 2007 or 2010 click Formulas » Defined Names » Name Manager. Scan the list for any non-Roman characters. (They sort alphabetically after the Roman letters, so any name that seems to be out of alphabetical sequence is worth a look.) Change the names to all Western European characters, and make the corresponding changes in your formulas.

last edited: 2012-11-22

14.2. "Risk.xla cannot be found"

Applies to: TopRank 5.x–7.x

When I do certain operations in TopRank, such as What-If Analysis, I get this error message:

'...\Risk.xla' cannot be found. Check your spelling, or try a different path.

I notice that the location in the error message, shown before Risk.xla, is an explicit network location with a leading \\ or else a mapped network drive.

You have Excel's default file location set to a network folder, and that confuses TopRank when it tries to load some AutoVary functions that it needs from @RISK. There are several alternative solutions, and you can choose A, B, or C:

A. Change Excel's default file location:

  • In Excel 2013 and 2016, click File » Options » Save, and change Default local file location to a local folder on the same computer as TopRank.
  • In Excel 2010, click File » Options » Save, and change Default file location to a local folder on the same computer as TopRank.
  • In Excel 2007, click the round Office button, then Excel Options » Save, and change Default file location to a local folder on the same computer as TopRank.
  • In Excel 2003, click Tools » Options » General, and change Default file location to a local folder on the same computer as TopRank.

B. Open @RISK each time you open TopRank. You can do this either from the @RISK desktop icon or through TopRank itself: TopRank » Utilities » Load DecisionTools Add-In » @RISK. Or you can start @RISK from the desktop icon and then start TopRank through the similar menu selection in RISK.

C. Set Excel to start @RISK automatically whenever Excel starts, by following the directions in Opening Palisade Software Automatically Whenever Excel Opens. (Yes, we did mean @RISK in that sentence. If Excel opens @RISK automatically, TopRank won't need to open Risk.xla.)

Last edited: 2015-10-19

15. @RISK Developer Kit (RDK)

15.1. "RDK authorization invalid"

This article relates to discontinued products, but is retained for the benefit of our customers with existing licenses. For current information, please see Support Policy for RDK, BDK, EDK, and RODK.

Applies to:
@RISK Developer's Kit (RDK) 4.0 and 4.1

Problem:
While running a simulation from my RDK application, I get this error message:

Error in RDKX module when calling a method of the DLL interface of the RDK or BDK, error number: 73, error description: RDK authorization invalid

Response:
You are running too many users at once.

This could be because there are actually too many users, or because of a bug in your application code.  If you look at RDK code examples, you'll see that RDKApplication.Initialize calls are followed by matching RDKApplication.Free calls.  If you make a number of "Initialize" calls without making the corresponding "Free" calls, that will be treated like multiple users running simulations at the same time.  If you have a license for 1 concurrent user, making two RDKApplication.Initialize calls is not possible if the RDKApplication.Free call is not made.

You may have some process on your server or computer that no longer shows any windows, but is holding on to an RDK license "token".  If you can reboot the machine, that should take care of the problem, but of course you'll also need to add the necessary RDKApplication.Free call to your application code. 

last edited: 2014-01-22

15.2. "Retrieving the COM class factory ... error: 80040154."

This article relates to discontinued products, but is retained for the benefit of our customers with existing licenses. For current information, please see Support Policy for RDK, BDK, EDK, and RODK.

Applies to: @RISK Developer's Kit (RDK) 4.1

When I try to run a simulation, I get this error:

Retrieving the COM class factory for component with CLSID {9A5B23A6-6CA7-11D5-92DE-000102610604} failed due to the following error: 80040154.

or some other error containing 9A5B23A6-6CA7-11D5-92DE-000102610604.

First and foremost, has the RDK been installed? If it has, you'll see "@RISK Developer's Kit 4.1" in the programs list in Control Panel. If not, install it.

Was the application working previously, on this same computer and in this same installation of Windows? If you've begun getting this error after the application used to work, try reinstalling the RDK and the application, and that should solve the problem. (You will not need to reauthorize the RDK if it is already authorized.)

Are you running the RDK in a 64-bit process? The RDK must run in a 32-bit process. Please see 64-bit Versions of Developer Kits? for how to run the RDK with 64-bit applications.

Is there a problem in your .NET deployment of the RDK, such as policy files and PIA file missing or misregistered? See Developer's Kit Redistribution for .NET. It will tell you how to register the files. If you are running the RDK End-User Edition and you received the application as a packaged installer from a vendor, please refer them to that article for tips on creating their application installer.

Last edited: 2015-02-27

15.3. "The network quota has been reached."

This article relates to discontinued products, but is retained for the benefit of our customers with existing licenses. For current information, please see Support Policy for RDK, BDK, EDK, and RODK.

Applies to: @RISK Developer's Kit (RDK) 4.0 and 4.1

While running my RDK application, I get this error message:

error number: 85, the network quota has been reached

This copy of the RDK or BDK has not been authorized, or its authorization was time limited and has expired. It's also possible, though less likely, that some hardware change after authorization has made this look like a new computer to the licensing software and has invalidated the license.

If you have never authorized the software on this computer, authorize it. If you have authorized it on this computer, and you have a current maintenance contract, please contact Technical Support for assistance. Please include your serial number and key code in the message. (Your key code was sent to you with your serial number. It is a string of letters and digits that does not include hyphens. The codes that include hyphens are your request code, ID code, and authorization code, and these will not help Technical Support diagnose your issue.)

Last edited: 2016-01-05

15.4. "Too many outputs"

This article relates to discontinued products, but is retained for the benefit of our customers with existing licenses. For current information, please see Support Policy for RDK, BDK, EDK, and RODK.

Applies to:
@RISK Developer Kit releases 4.x

Question:
I got the error message "Too many outputs" when adding outputs to a range. Is there a limitation in the RDK?

Response:
The number of outputs is not limited, but the number of outputs in any one range is limited to 100. If you don't need more than 100 outputs in a single summary trend graph, then simply add the outputs as individual outputs and the RDK will accept them.

The purpose of an output range is to let you prepare a summary graph for all outputs in the range. As you add more and more outputs in a single graph, it becomes progressively harder to see any meaningful comparisons between them. Even as many as 100 outputs in a single range is quite unusual.

If you truly need summary graphs for more than 100 outputs, then you need to generate the graphs yourself, possibly using some third-party graphing engine. Otherwise, simply add the outputs as individual outputs, or group them in ranges of no more than 100.

last edited: 2010-01-18

16. Evolver Developer Kit (EDK)

16.1. "Nonstandard extension used: '_huge' "

This article relates to discontinued products, but is retained for the benefit of our customers with existing licenses. For current information, please see Support Policy for RDK, BDK, EDK, and RODK.

Applies to:
Evolver Developer Kit (EDK)

Problem:
With the Evolver Developer's Kit, I can successfully run your examples. I am now trying to include Evload.cpp and your header file (Evolver_types.h, Evolver_funcs.h) into my program, written in Visual C++ Studio 6.0. Unfortunately, when I attempt to compile my program, I get:

ERROR C4226. Nonstandard extension used: '_huge' is an obsolete keyword in Evolver_TYPES.H.

How can I eliminate this error and compile my code?

Response:
The "_huge" keyword is obsolete in the 32-bit platform Visual Studio 6.0. The C++ compiler is supposed to just ignore it, and it does ignore it when compiling the examples. However, if the keyword does not get ignored and causes errors during compilation, you can just delete it from lines 6 and 7 in Evolver_types.h.

last edited: 2006-10-16

17. Issues while Uninstalling

17.1. "Another program is being installed."

Applies to: All product uninstallers

While trying to uninstall one of your products, I got the message

Another program is being installed. Please wait until that installation is complete.

I'm not actually installing anything. What can I do?

When one of our employees had this problem, the following worked:

  1. Start » Run » services.msc
  2. Find the Windows Installer service.
  3. If it's running, right-click and stop it.
  4. If it's set to Automatic, right-click, select Properties, and change it to Manual.

You might also try Microsoft's "Fix Problems with Programs" tool, mentioned in "Another version of this product is already installed. Installation of this version cannot continue.".

Last edited: 2015-10-19

17.2. "Another version of this product is already installed. Installation of this version cannot continue."

Applies to: All products, versions 5.x–7.x uninstallers

In Programs and Features (or Add or Remove Programs, or using msiexec /x), I tried to uninstall my Palisade software. But a window popped up with the title "Windows Installer" and this message:

Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

How can I uninstall the product?

Some pointers are incorrect in the database of installed programs. This can happen, according to CNet, if "your computer's registry becomes corrupted; you or someone else inadvertently changes a registry setting used by the Windows Installer, resulting in a problem; the installation of a program that uses Windows Installer ... is interrupted; or there are multiple instances of Setup running simultaneously, or an instance of Setup is blocked".

Microsoft offers a tool to repair this type of problem; please see Microsoft's article Fix Problems with Programs That Can't Be Installed or Uninstalled.

(For future reference: a repair of our software is almost always a better option than uninstalling and reinstalling. It preserves the license, it's faster, and it's less disruptive in general. Very seldom is a full uninstall/reinstall necessary. For directions, see Repair of Palisade Software.)

Last edited: 2016-11-15

17.3. "Error: Failed to load ... FnpCommsSoap.dll"

Applies to:
@RISK 5.0 uninstall

Problem:
When I try to uninstall @RISK, I get a series of messages like

Error: Failed to load C:\Program Files\Palisade\\SystemFnpCommsSoap.dll

Solution:
Two entries in the System Registry are incorrect and can be corrected as follows. (You need administrative rights to edit the Registry.)

    1. Click Start » Run and enter the command
      REGEDIT
      then click OK.

    2. In the left pane, navigate to HKEY_LOCAL_MACHINE\Software\Palisade, or HKEY_LOCAL_MACHINE\Software\WOW6432Node\Palisade in 64-bit Windows. Click once on Palisade.

    3. In the right-pane, double-click on System Directory. In the edit window, you will see two backslashes \\ before the word SYSTEM or System. Remove one of the backslashes, and if the string doesn't end with a backslash then append one. The string will now look something like
      C:\Program Files\Palisade\System\
      (The first part may vary, depending on where the software is installed, but the last part will be as shown.) Click OK.

    4. Double-click on Main Directory. If there are two backslashes at the end, remove one; if there are no backslashes at the end, add one. Click OK.

    5. Close the Registry Editor by clicking the menu item File » Exit.

You will now be able to uninstall @RISK.

last edited: 2010-02-11

18. Network Server Issues

18.1. "Cannot find license file"

Applies to: Palisade Server Manager, all releases

After I install Server Manager and get my license file, the license service shows as stopped, and clicking Start doesn't start it. There is no error message.

I clicked the magnifying glass in Server Manager, and then the View button.  In the debug-log section at the end I see the message "license manager: can't initialize: Cannot find license file."  I did choose a non-default location to install Server Manager, but that shouldn't be a problem.

In general, you're free to choose non-default locations.  But if you have an @ sign in your path, for instance if you install to C:\@RISK, Windows can get confused by the file path.  It's best to avoid special characters like @, *, and ? in file paths.

If that's not the explanation, please contact Palisade Technical Support for assistance, and include your serial number in your trouble report.

Last edited: 2013-11-11

18.2. "Component 'Codejock.Controls.Unicode.v17.1.0.ocx' ... not correctly registered"

Applies to: Palisade Server Manager 7.5.0

When I launch Server Manager, I get the message

"Component 'Codejock.Controls.Unicode.v17.1.0.ocx' or one of its dependencies not correctly registered: a file is missing or invalid"

When I click OK, Server Manager does not run.

This unfortunately happens if you (a) upgrade Server Manager from 7.0.1 to 7.5.0 (b) on a server that doesn't have any client software installed. Thus, Citrix servers and other forms of Terminal Services should not experience this problem.

We have issued a new Server Manager installer for 7.5.1, which you can obtain from Palisade Technical Support.(Please include your software serial number in your email.)

Installing that version will solve the problem.

Last edited: 2016-10-25

18.3. "Feature ... does not support borrowing ..."

Applies to: Palisade network server software 6.x/7.x

In Server Manager, in Advanced Options, I clicked the View button (or in LMTools, on the Config Services tab, I clicked View Log). Near the end of the output I see this message

Feature @RISK60_Professional does not support borrowing, MAX_BORROW_HOURS ignored

or a similar message naming another Palisade product. What is wrong?

This message from the FLEXnet software can be ignored.

Details:
In FLEXnet, there are two forms of Concurrent Network license, activatable and certificate. Technically, the activatable Concurrent Network license does not have borrowing, but it has another feature that serves the same purpose. MAX_BORROW_HOURS is a FLEXnet option for the older certificate form of license.

To keep things simple and consistent, Palisade 6.x and newer network software always uses the term borrowing. Our software presents a single interface to end users and server administrators, whether the underlying Concurrent Network license is the activatable type or the certificate type. When you enable or disable borrowing or change the borrowing limit in Server Manager » Options, for either type of Concurrent Network license, the software updates the MAX_BORROW_HOURS option line. If the license is the more common activatable type, the FLEXnet software does not understand the MAX_BORROW_HOURS line, and it issues a warning message. However, there are no other consequences in the Palisade licensing environment.

Palisade recommends you do not edit the MAX_BORROW_HOURS line in the options file. Depending on the exact sequence of events, it's possible that such an edit could cause borrowing to malfunction, or to be available when you did not want it to be available. Always use the Options dialog in Server Manager to set borrowing options for Palisade Concurrent Network software.

Last edited: 2015-10-19

18.4. "Invalid MAX_BORROW_HOURS value specified"

Applies to: Palisade network server software 6.x/7.x

In Server Manager, in Advanced Options, I clicked the View button (or in LMTools, on the Config Services tab, I clicked View Log). The message

Invalid MAX_BORROW_HOURS value specified

appears near the end of the output. What is wrong?

This message from the FLEXnet software can be ignored. For further explanations, please see "Feature ... does not support borrowing ..."

Last edited: 2015-10-19

18.5. "Path/File access error"

Applies to: Palisade Server Manager 6.x

When I launch Server Manager, I get this error message:

Palisade Server Manager
Path/File access error

This is most likely a privilege issue.

First, make certain that you have logged on with full administrative rights. If not, please log off Windows and log in as a full administrator.

A less common problem is insufficient permissions on files or folders. You need read, write, and delete access (or Full Control) in the folder where Server Manager is installed, and also in the Windows temporary folder.  By default, Server Manager is installed in C:\Program Files (x86)\Palisade\NetServer or C:\Program Files\Palisade\NetServer. To find the Windows temporary folder, click Start » Run and enter the command %TMP% including the percent signs.

If you have full administrative rights, and full control of both folders, but you still see the message, Server Manager may not be getting elevated privilege.  Try starting it this way:  Click Start » Programs » Palisade Network Server, then RIGHT-click Server Manager and select Run As Administrator.

Server Manager 7.0.0 and newer diagnose the problem correctly and tell you that administrative rights are required. To obtain the latest Server Manager, please see Upgrading Palisade Software.

Last edited: 2015-10-19

18.6. "The license server manager (lmgrd) is already serving all vendors, exiting."

Applies to:
Palisade Server Manager, releases 6.0 and newer
LMTools, distributed with Palisade network software releases 5.x

Clients can't get a license, and the Palisade license service shuts itself down as soon as I start it. At the end of the debug log file, I see this message:

The license server manager (lmgrd) is already serving all vendors, exiting.

(The debug log file is displayed in Server Manager by clicking the View button on the Advanced Options screen, or in LMTools by clicking View Log on the Config Services tab.)

FLEXnet offers two ways to handle multiple vendors' licenses on one server.

The method that we support uses each vendor's lmgrd.exe file. Palisade installs to its own folder, so there is no conflict with FLEXnet files from other vendors. (The only potential conflict is with port numbers. To avoid that problem, either specify a unique lmgrd port number for each vendor, or leave all port numbers unspecified.)

The other method, which we don't support, has a single lmgrd.exe file handle licenses from all vendors, by dispatching each license request to the appropriate vendor daemon. Why don't we support this? Most Palisade Concurrent Network licenses, and all Enterprise Network licenses, are of the activatable or "trusted storage" type. This method, having a single lmgrd.exe for all vendors, doesn't work with activatable licenses, because there is no license certificate for lmgrd to read. Consequently, if you chose this method, you will most likely have the problem described above. Palisade Server Manager shows the license normally, because it knows there's no license file, but LMTools Server Status doesn't know about the license and can't display it.

To solve this:

  1. Remove the Palisade licenses from the common license directory or common license file. Or, if you're passing a license list to lmgrd on the command line, remove the Palisade license from the command line.

  2. Stop and restart the service for that copy of lmgrd.

  3. Launch the Windows program Services.msc. If lmadmin is running as a service, stop it and disable the service.

  4. Verify that Palisade License Service is set to Automatic and FLEXnet Licensing Service is set to Manual. In Palisade Server Manager, start the service and you should see that its status changes to Running.

Last edited: 2015-05-26

18.7. "The license you just activated is not usable ..."

Applies to: Server Manager 6.0.1

I've just activated my network license, and I get a popup telling me that activation was successful. Then after Server Manager refreshes its display, it pops up this error:

The license you just activated is not usable, most likely because it has already expired.

The license does show in the Network Licenses Installed box. Is something wrong?

If the license shows in Network Licenses Installed, then it is almost certainly good. This message can come about if you type or paste a space before or after the Activation ID when you enter it. Server Manager removes the extra space but mistakenly displays the message after activation.  (This error occurs only in early builds of 6.0.1, distributed in October 2012, and does not occur in later builds of 6.0.1 or in releases 6.1 and above.  Please upgrade to avoid the problem; see Upgrading Palisade Software.)

If the license does not show in Network Licenses Installed, then something else happened and the license is not usable. Please click the magnifying glass and then View. Save the resulting file and attach it to an email to Palisade Technical Support. Please include your Activation ID in the email.

Last edited: 2012-12-28

18.8. "Unable to clear temp file at ... PalServerStatus.txt"

Applies to: Palisade Server Manager

in Palisade Server Manager, when I click the Status button, I get the error message

Unable to clear temp file at
C:\Users\mylogin\AppData\local\Temp\PalServerStatus.txt

(The path may be different, but the file name matches.)

Close Server Manager, open the indicated folder, and delete the file.  Always be sure to run Server Manager as administrator, though recent versions will request elevation if they need it.

If Windows won't let you delete the file because it's open in another process, open Windows Task Manager (Ctrl+Shift+Esc), locate lmutil.exe on the Details or Processes tab, and click to end the task. This will not affect any license service that is running.

Last edited: 2017-02-28

18.9. "Unable to load PalNetSvrUtil7_x86.dll"

Applies to: Palisade Server Manager 7.x

When I launch Server Manager, I get this error:

Operation Failed
Details:
Unable to load PalNetSvrUtil7_x86.dll

Did you install Server Manager with full administrative rights? If you didn't, or if you're not sure, please repeat the install, but this time right-click the installer and select Run as Administrator.

Another possibility is missing or corrupted Visual C++ runtimes. If Server Manager used to be working, and is now getting this error, that points to this cause. But it could also occur right after install, if the runtimes were present but corrupted. In either case, please install the Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 from item 2 of Microsoft Components Required for Palisade 7.x Software Install; there's no need to reinstall Server Manager after doing this.

Last edited: 2016-08-17

18.10. "You must have full administrative privileges to run this program."

Applies to: Palisade Server Manager 6.x/7.x

When I try to launch Server Manager, I get this error popup:

You must have full administrative privileges to run this program.

But I am an administrator. What's wrong?

Server Manager doesn't directly test whether you're an administrator, because some "administrators" don't actually have full privileges. Instead, it makes these tests:

  • Is the Palisade NetServer folder writable? Specifically, can Server Manager create and then delete a text file? It needs to write to this folder so that it can update the Server.lic folder. If you're an administrator, ensure that the folder itself and the four files Server.lic, Palisade.opt, PalisadeNetwork.lic, and PalisadeService.log are all writable.

  • Do you have full control for the System Registry key Palisade\NetServer under HKLM\Software (32-bit Windows)or HKLM\Wow6432\Software (64-bit Windows)? Server Manager tries to write a string value under that key, read it, and delete it. If any of those fail, it concludes that you don't have administrative rights.

    If you're an administrator, try this yourself: select the key, right-click in the right-hand panel, select New » String Value, and name it TestKey. Give it any text, and verify that you see that text in the right-hand panel after clicking OK. Finally, delete it and verify that it's gone.

    It occasionally happens that the System Registry is corrupted. If that happens, delete the NetServer key and then reinstall Server Manager. (In one case, it was necessary to delete the entire Palisade key and reinstall Server Manager. If you're in a Citrix or similar environment, and you delete the Palisade registry key, you will need to reinstall the client software also, so that's definitely a last resort.)

Last edited: 2015-10-20

18.11. LMTOOLS Crashes When Displaying System Settings

Applies to: All Palisade products 4.x and 5.x licensed with FLEXlm or FLEXnet

I start the FLEX administrative tools (LMTools).  Most functions work fine, but when I click on the "System Settings" tab the program crashes.

We have seen this problem when Data Execution Prevention (DEP) is turned ON on a PC with Execute Disable Bit (EDP) technology. LMTools crashes when attempting to look for a dongle ID from the "System Settings" tab.

To avoid this problem, exclude LMTools from the list of applications supporting this option.  Follow this procedure:

  1. Open Control Panel » System. (Alternative procedure: right-click on My Computer and select Properties.)

  2. On the Advanced tab, in the Performance section, click Settings.

  3. Select the Data Execution Prevention tab.

  4. Select "Turn on DEP for all programs and services except those I select".

  5. Click the "Add..." button, and in the window that opens navigate to LMTools.exe.  (By default, it's in a subfolder under C:\Program Files\FLEXnet\Palisade or C:\Program Files (x86)\FLEXnet\Palisade.  Your serial number is the name of the subfolder.) Click Open.

  6. Click OK to close the Performance Settings dialog, and OK to close the System Settings dialog.

Last edited: 2012-09-28

18.12. FLEXlm License Manager Times Out (Error -15,570)

Applies to: All products with a Concurrent Network license

We have a FLEXlm license on our VPN or other wide area network, but our users are getting error -15,570 or "Unable to reach a network server" when they try to launch the software.

The default FLEXlm License Manager timeout is 0.1 second. If there are a lot of Internet "hops" between the user and the FLEXlm license server, that may not be enough time for the required handshaking to authorize the user.  Likewise, if the client is connecting to the server through a VPN and network performance is slow, the license request may time out.  You can increase this timeout value by setting a system environment variable.

(Note:  The procedure in this article may not be effective if you have specified an Lmgrd port number below 27000 or above 27009.  The FLEXnet 11.10 License Administration Guide says that this procedure "Sets the timeout value a FlexEnabled application uses when attempting to connect to a license server port in the range 27000–27009.")

Please follow this procedure on each user's computer that experiences the problem:

  1. Right click on the My Computer icon and select Properties. (In Windows 7 and 8, click Advanced System Settings when the System window appears.)

  2. On the Advanced tab, click the Environment Variables button.

  3. Click anywhere in the System Variables area and click New. (If the System variables section is greyed out, you don't have administrator rights. Log in to Windows as an administrator to perform this procedure.)

  4. Enter the variable name FLEXLM_TIMEOUT and the new timeout value in microseconds. We recommend 1000000 (a one and six zeroes), meaning 1 second. Don't use separators when entering the value -- 1000000, not 1,000,000 or 1.000.000 or 1 000 000.

  5. Click OK to close the New System Variable window, OK to close Environment Variables, and OK to close System Properties.

The new system variable is permanent; you will not need to create it again when you reboot the system.

If one second (1000000 µs) is insufficient, you can try a higher value; but consider the possibility that something else may be wrong.  See "FAILURE: Unable to reach a network server." for possible causes and cures.

Last edited: 2013-11-05

18.13. FLEXnet Error: "Exiting due to signal 27"

Applies to: All Palisade network products licensed with FLEXlm or FLEXnet

Server Status says that the vendor daemon is not running. When I look at the debug log file, I see this error:

EXITING DUE TO SIGNAL 27

This means that the vendor daemon (Palisade.exe) can't find any valid licenses, or there is a conflict between two or more vendor daemons.

Finding and fixing port-number conflicts on the server:

If you also have FLEXnet licenses from other vendors, check that they are not using the same port number. The port number is found on the SERVER line of the license file, as an optional argument after the Ethernet address. (If "ANY" appears on that line, it refers to any Ethernet address, not any port number.) If some specify a port and some do not, there could be a conflict if an lmgrd with a specified port happens to load after an lmgrd with an unspecified (dynamic) port. If any vendor's license file, including Palisade's, specifies an lmgrd port number on the SERVER line, then every license file must specify a unique port number on the SERVER line. (The more robust solution is not to specify an lmgrd port in any license file.)

If there is a conflict, change the port number in one of the license files, and make a matching change on the clients.

If you specify both lmgrd port number on the SERVER line and vendor-daemon port number on the VENDOR line, they must be different.

Finding and fixing multiple-daemon conflicts:

The Palisade vendor daemon, palisade.exe, can run only one copy at a time. Open Task Manager to see whether you have multiple copies running. If you do:

  1. Shut down all the palisade.exe processes. Also shut down their associated lmgrd.exe processes.
  2. If you have multiple Palisade services defined in LMTools, remove all but one of them.
  3. Restart the Palisade license service in Server Manager (if available) or LMTools.

Finding and fixing license issues:

Perhaps you installed a license but it has expired, or you never installed your license, or maybe you simply need to have the license process reread your licenses.

If you have Palisade Server Manager, which comes with 6.0 and later network software, run it and look at the list of licenses. If no licenses are shown, click the "Unavailable Licenses" button, if it appears, to see unavailable licenses including expired licenses. This should tell you what's wrong, but feel free to contact Palisade Technical Support for assistance.

If you don't have Palisade Server Manager, and your license is a certificate type:

  1. Look in the license file (certificate), on the INCREMENT line, for the expiration date. If the certificate has expired, contact Palisade Technical Support to obtain an updated license file. Please attach your expired license file to your request.
  2. If your certificate has not expired, open LMTools and on the Config Services tab verify that the second box points to the correct license file. Change it if necessary, and click Save Service, then go to Start/Stop/Reread and click Start Server. Close and reopen LMTools, and check Server Status.

If you don't have Palisade Server Manager, and your license is a trusted storage type ("activatable", downloaded with TransferLicenses.bat or Request.bat):

  1. Open a command prompt, navigate to the folder whose name is your serial number, and type this command:
    palserveractutil -view
  2. If the command fails with "ERROR: Activation library initialization failed", you have a port-number conflict; see above.
  3. If you see "No fulfillment records in Trusted Storage", you have not yet downloaded your license. Please follow the procedure in Server Steps 2 through 4 in the network Readme file.
  4. If you see some fulfillment records, look on each INCREMENT line for an expiration date. If every license has expired, please contact Palisade Technical Support for assistance and attach a copy of the output. If you have a permanent license or it has not yet expired, open LMTools and on the Start/Stop/Reread tab click Stop Server, then Start Server. Close and reopen LMTools, and check Server Status.

Last edited: 2016-06-09

18.14. "Exiting due to signal 28"

Applies to: Palisade network products, on license server

When I start the service, it stops itself. The log shows these lines:

(palisade) tcp_s is bad!!! Exiting
(palisade) EXITING DUE TO SIGNAL 28 Exit reason 5
(lmgrd) palisade exited with status 28 (Communications error)

The vendor daemon is trying to use the same port as lmgrd.  Either set them both to dynamic (or unspecified), or change one of them to a different specific number. 

It is simpler to change the vendor daemon port number, because that change affects only the server and does not require reconfiguring the client software.

See also:

Last edited: 2015-10-19

18.15. FLEXnet Error: "Exiting due to signal 32"

Applies to: All Palisade products 4.x and 5.x licensed with FLEXlm or FLEXnet

The Palisade.exe vendor daemon terminates with the message

Exiting due to signal 32

We have not seen this problem here at Palisade, but some users have reported it.  For them, the issue turned out to be that they had installed the licensing software under the custom folder C:\FLEXlm\... on the server.  The solution was to rename the folder to something else, such as C:\LMFlex\... .

The default install location is C:\Program Files\FLEXnet\Palisade... or C:\Program Files (x86)\FLEXnet\Palisade..., and no one with the software installed in the default location has ever reported this problem.

Last edited: 2012-09-28

18.16. FLEXnet error: "exited with status 58"

Applies to: Palisade network software 5.x–7.x, license server

The license server shuts itself down, and the relevant message in the debug log file is "exited with status 58".

We have seen two causes for this error:

  • Port number conflict. Make sure that you don't have two Palisade license services running, not even for two different releases of our software. Also make sure that you have not specified an LMGRD port or vendor daemon port for the Palisade license service that is in use by the FLEXnet license service from another vendor.

  • Data Execution Prevention (DEP). On older versions of windows, set lmgrd.exe and Palisade.exe as running without DEP.

Last edited: 2015-10-19

18.17. Two Copies of LMGRD Running

Applies to:
Palisade network software releases 5.0 and later, including all 6.x/7.x network releases
(FLEXnet 11.4 and later)

After I click Start Service in Server Manager, or Start Server in LMTools, in Windows Task Manager I can see that two instances of LMGRD are running.  Why is this, and how do I fix this problem?

This is by design.  Flexera made a change in how FLEXnet works, between FLEXnet 10.1 (in our 1.x/4.x products) and FLEXnet 11.4 (in our 5.x products).  Now, when lmgrd is run as a service, it launches a second lmgrd process.  Although it looks a bit odd, it's not a problem because the performance impact is negligible.

I have FLEXnet products from multiple vendors.  How can I tell which instances of lmgrd are serving licenses for which end-user software?

In later versions of Windows, right-click an instance of lmgrd in Task Manager and select Properties.  The location will tell you which copy of lmgrd this is.  (By default, "Palisade" will be in the install path for lmgrd used with both 5.x and 6.x versions of our software.)

In earlier versions of Windows, such as Windows XP, you may need a separate utility to obtain that information.  Process Explorer from Sysinternals (now part of Microsoft) is generally well regarded.

Last edited: 2015-10-19

18.18. Server install (5.7): "A network error occurred while attempting to read from the file ..."

Applies to: All concurrent network server installs, releases 5.7
(For this error with 6.x/7.x, please see "A network error occurred" in a 6.x/7.x install.)

I purchased an upgrade or an additional product for my concurrent network license. I'm trying to run the server setup as instructed, but during the server install I get the error message

Error 1316. A network error occurred while attempting to read from the file ...

Palisade apologizes for this problem.  There is an error in the installer, causing it to fail with Error 1316 when another Palisade network server install has already been done.

If you're adding a second product, please follow the procedure in Two or More 5.x Network Products on Same Server.

If you're upgrading an existing product to a later release, please contact Palisade Technical Support at tech-support@palisade.com for customized instructions.  When you contact us, please include both the old and new serial numbers and mention that you're getting an Error 1316 during a second network server install.

Last edited: 2012-11-17