Palisade Knowledge Base

HomeTechniques and TipsAll ProductsRunning "Out of Process"

1.14. Running "Out of Process"

Applies to:
@RISK 7.5.2 in 32-bit Excel 2013 or 2016
@RISK 7.6.x in 32-bit Excel 2013, 2016, or 2019
Evolver 7.5.2 in 32-bit Excel 2013 or 2016
Evolver 7.6.x in 32-bit Excel 2013, 2016, or 2019
NeuralTools 7.5.2 in 32-bit Excel 2013 or 2016
NeuralTools 7.6.x in 32-bit Excel 2013, 2016, or 2019
PrecisionTree 7.5.2 in 32-bit Excel 2013 or 2016
PrecisionTree 7.6.x in 32-bit Excel 2013, 2016, or 2019
StatTools 7.5.2 in 32-bit Excel 2013 or 2016
StatTools 7.6.x in 32-bit Excel 2013, 2016, or 2019

Does not apply to:
64-bit Excel, or 32-bit Excel 2010 or 2007

What does it mean to run out of process or in process, and what difference does it make to me?

@RISK and our other add-ins are 32-bit code, and each product has a bridge to 64-bit Excel. Those bridges are called RiskOutOfProcessServer7.exe, EvolverOutOfProcessServer7.exe, NeuralToolsOutOfProcessServer7.exe, PrecisionTreeOutOfProcessServer7.exe, and StatToolsOutOfProcessServer7.exe. We say that @RISK (Evolver, NeuralTools, ...) is running out of process, meaning that it doesn't run directly as part of 64-bit Excel's process, but instead routes communications with Excel through the bridge.

When you're interfacing 32-bit code with 64-bit code, that's normal. However, in 7.5.1 and earlier releases, even with 32-bit Excel 2013 and 2016, @RISK and the other tools ran out of process. With 7.5.2, that changed: when running with 32-bit Excel, the tools listed above now run in process by default. This removes a layer of code and should provide better performance and greater stability, since there's no longer a separate "out of process server" layer.

If your simulations involve Microsoft Project, you'll notice a very significant speedup from running @RISK 7.6 in process.

But there are many builds of Excel 2016 out there, not to mention future Excel updates, and it's not possible to test with all of them. It's possible, though not likely, that your particular build or configuration might experience a problem with running in process, such as flashing windows or windows not appearing at all, or other issues identified by Palisade Technical Support. If this happens, you can set Palisade software to run out of process and avoid the problems.

How do I set the software to run out of process?

These settings are recorded in the current user's profile. If people log in to this computer under different Windows usernames, the others will continue running in process unless they also follow one of these two methods.

Method A: If you can launch the software, and get into Utilities » Application Settings, it's easy. In the Advanced section at the end of Application Settings, change Operating Mode to out-of-process, and click OK.

TIP: If you have the DecisionTools Suite, and some tools are working, change this setting in one of the working tools, and it will offer to change it in the others, working and non-working. Remember to close Excel before re-testing the tool that has problems.

Method B: If you can't launch the software, or the Application Settings dialog won't come up, you can use the attached OutOfProcess Registry file.

  1. Close all open instances of Excel and Project.
  2. Download the attached OutOfProcess file.
  3. Change the extension from TXT to REG. (If you can't see the .TXT extension, see Making File Extensions Visible.)
  4. Double-click the REG file.

The REG file will set Registry keys for the five products listed above. If you don't have the DecisionTools Suite but only one or more individual products, the extra keys will do no harm.

What if I want to go back to running in process?

In Utilities » Application Settings » Advanced, set Operating Mode to in-process, or use the attached InProcess file.

Are there any known issues when running in process?

Here's what we've identified so far:

Last edited: 2018-11-28


This page was: Helpful | Not Helpful