Palisade Knowledge Base

HomeTroubleshootingAll Products: Startup"Unable to cast COM object"

2.89. "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 and later 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 in Batch File

  1. Open an administrative command prompt. You must run this procedure in an administrative command prompt; even if you have administrative privileges, you cannot run this successfully via a Start » Run window.

  2. Download the attached KB1484_Reregister_AtRiskOL.bat file to a convenient location—save it, don't run it.

  3. Shift-right-click the downloaded file and select Copy as Path.

  4. Click into the administrative command window. Right-click and select Paste, then press the Enter key.

  5. The pop-up message should be "DllRegisterServer ... succeeded". If you get a different message, follow the instructions in the window.

Option B — Repair or Upgrade

Last edited: 2018-07-08


This page was: Helpful | Not Helpful