Follow

Interop error when creating documents

When trying to create a document for a case in TurboLaw, you receive an error message which says:

Unable to cast COM object of type 'Microsoft.Office.Interop.Word.ApplicationClass' to interface type 'Microsoft.Office.Interop.Word._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00020970-0000-0000-C000-000000000046}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

After clicking "OK" to this message, your document will not appear.

This problem is caused by an error with Microsoft Office, specifically with Microsoft Office's internal settings being incorrect.

To resolve this problem, you can have Microsoft Office "repair" itself. To do this, follow these steps:

  1. Click on your Start menu and open the Control Panel
  2. Click on Uninstall a Program (or Add/Remove programs in Windows XP)
  3. Locate the entry for Microsoft Office and click on it. After you click on it, you should see a button labeled Change appear either next to it, or at the top of the list (depending on what version of Windows you have). Click this Change button.
  4. Once Microsoft Office setup appears, choose the Repair option and click Next to have Microsoft Office repair itself. You may need to reboot your computer once this process is complete; Microsoft Office setup will tell you if you need to do this once it is done.

Once you have performed these steps, TurboLaw should be able to open documents normally without the error.

Advanced Troubleshooting

This problem is caused by incorrect COM Interop settings in the Windows registry. This can be caused by installing a newer version of Microsoft Office, and then removing it and installing an older version instead. (For example: you get a new computer which comes pre-installed with a trial version of Microsoft Office, but you remove this trial and install the older version which you own.)

As the source of this problem is in the Windows registry, it is best to use the method described above to resolve the problem.

However in some cases the method described above may not resolve the problem. In this case, it will be necessary to edit the Windows registry directly to correct the problem.

Note: Editing the Windows registry can cause serious, potentially unrecoverable problems with your computer. If you are not familiar with how to back up and restore your Windows registry, do not attempt any of these steps and instead contact a qualified computer technician. If you follow these steps on your own, you do so at your own risk. 

To begin with, it is necessary to locate the correct registry entries for your particular version of Microsoft Office. In the error message you receive, there will be an IID mentioned (in the example given above, this is: {00020970-0000-0000-C000-000000000046}). This is the CLSID for Microsoft Word (or Excel, if you are receiving this message when opening an Excel-based form, such as a financial or HUD form).

Once you have the CLSID, open the Windows registry (using regedit) and browse to HKEY_CLASSES_ROOT\Interface\[the CLSID from the error message]\TypeLib.

In this TypeLib key, look for the (Default) value - this will be another, slightly different ID number - this is the TypeLib ID. Also, make note of the Version value.

Now, browse to the registry key HKEY_CLASSES_ROOT\TypeLib\[the TypeLib ID you just found].

In this key, there should only be 1 subkey, and it should be the same as the Version value you found previously. If there are any other subkeys with different versions, they will need to be removed - these other subkeys are what is causing the issue with COM Interop.

Once the offending keys have been removed so that only the 1 subkey remains (with the same version you found previously), you can close the Registry Editor.

You should now be able to create documents with TurboLaw without receiving this error - you do not need to restart the computer.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk