I've never seen this error before when publishing my Word target (Word 2003 still) using Flare 6.1:
Checking Word version:
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)).
The build just stops right away. I can compile WebHelp just fine. Has anyone seen this and have any suggestions?
Word build has error loading library/DLL
Word build has error loading library/DLL
Larisa Dukes
Re: Word build has error loading library/DLL
Hi
I just experienced this error myself. Flare and Word 2010 had been working happily together until recently. I had installed parts of Office 2003 and Office 2007 and then uninstalled them. (The reason was to test out some unrelated software that plugs in to various versions Word and Powerpoint.)
Anyway after uninstalling Office 2003 and 2007 I experienced the same problem as you did.
I ran setup.exe on my Office 2010 disk and chose Repair. This fixed it.
Perhaps the uninstalls deleted an important dll or deleted or modified an important registry entry.
Hope this works for you too.

I just experienced this error myself. Flare and Word 2010 had been working happily together until recently. I had installed parts of Office 2003 and Office 2007 and then uninstalled them. (The reason was to test out some unrelated software that plugs in to various versions Word and Powerpoint.)
Anyway after uninstalling Office 2003 and 2007 I experienced the same problem as you did.
I ran setup.exe on my Office 2010 disk and chose Repair. This fixed it.
Perhaps the uninstalls deleted an important dll or deleted or modified an important registry entry.
Hope this works for you too.
James Willoughby
Re: Word build has error loading library/DLL
Thanks, James. I recently moved to Office 2010 with a fresh install. So far, I haven't seen this error crop up again. I appreciate the tip in case it does.
Larisa Dukes