Home → Troubleshooting → All Products: Startup → "... 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.
If that System Registry key doesn't exist, creating it may solve the problem. For instructions, see Which Version of Excel Is Opened by Palisade Software?
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:
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-08-31