HomeTroubleshooting@RISK for Excel: Simulation"Type mismatch" at End of Simulation

4.54. "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

This page was: Helpful | Not Helpful