I have been seeing the following error message any time I try to import a Word document into Madcap Flare V11:
"System.InvalidCastException occurred at 8/4/2016 9:24:12 AM
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: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY))."
This occurs when I attempt to create a new project via "File > New Project > MS Word Documents", or when I try to import a Word document into an existing project via the "Project > Import" feature. At the time this error started cropping up, I had upgraded the Microsoft .NET Framework on my PC to version 4.6. Not sure if this is the root cause.
Has anyone experienced this error before? Any input about this or how I could resolve it would be very helpful.
System.InvalidCastException When Importing Word Documents
-
- Jr. Propeller Head
- Posts: 5
- Joined: Tue Jun 14, 2016 11:03 am
-
- Propellus Maximus
- Posts: 1238
- Joined: Mon Feb 27, 2006 5:56 am
- Location: Melbourne, Australia
Re: System.InvalidCastException When Importing Word Document
Others have had this problem in the past, and usually running a Repair on Word will fix it - looks like a problem with the system environment. Worth a try.
Installaing .NET probably shouldn't break things, but it does change the system which could cause problems.
Installaing .NET probably shouldn't break things, but it does change the system which could cause problems.
Margaret Hassall - Melbourne
-
- Jr. Propeller Head
- Posts: 5
- Joined: Tue Jun 14, 2016 11:03 am
Re: System.InvalidCastException When Importing Word Document
Thanks for your help....I will give that a try tomorrow.
-
- Jr. Propeller Head
- Posts: 5
- Joined: Tue Jun 14, 2016 11:03 am
Re: System.InvalidCastException When Importing Word Document
This resolved my problem....thanks again!