Home → Troubleshooting → All Products: Other Issues → 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:
This message can result if the software was installed without administrative rights. Solution: Right-click the installer, select Run as Administrator, and then when the installer asks what you want to do select Repair. If you don't get the prompt to repair or modify, the installer will do a full reinstall.
Conflicts with other add-ins can cause this message. Solution: Find and Fix Startup Conflicts.
Try Removing Outdated References to Office from the System Registry, if you get this error without an error number.
Your installation of Excel may have become corrupted. Solution: Repair of Excel.
You may have problematic DEP settings. See Data Execution Prevention for testing and repair procedures.
"Object variable or With block variable not set" (Windows 8) when accompanied by runtime error –2146232576 (80131700)
"Object variable or With block variable not set" (Windows 7 and Vista) when accompanied by runtime error –2147024894 (80070002)
"Object variable or With block variable not set" if you have manually added any toolbars for @RISK, Evolver, etc.
"Object variable or With block variable not set" when Importing MPP File
"Object variable or With block variable not set" (PrecisionTree 1.0) when accompanied by runtime error 91
Additional keywords: Object variable, with block, variable not set
Last edited: 2018-08-03