BUG: Oleview Hangs with Incorrect Typelib Viewer Registration

Article translations Article translations
Article ID: 176938
Expand all | Collapse all

Symptoms

When attempting to view a type library, Oleview appears to hang and does not respond to user interaction. In addition, Task Manager shows that the Oleview.exe and Rpcss.exe processes combined are taking up nearly 100% of CPU time.

Cause

This problem is caused by an incorrect registration of the Iviewers.dll in- process server. Iviewers.dll contains the type library interface viewer object used by Oleview to parse the type library. The problem happens when the InProcServer32 entry for this object (under HKCR\CLSID\{57EFBF49-4A8B- 11CE-870B-0800368D2302}) points to an incorrect path. This exposes a bug in Oleview that causes it to try to load the viewer object in an infinite loop.

Resolution

To resolve this problem, re-register Iviewers.dll. This DLL is supplied along with Oleview.exe as a part of either the platform SDK or the Visual C++ compiler. Locate the DLL on the machine, and register its objects by issuing the following command:
Regsvr32 iviewers.dll

Status

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

Properties

Article ID: 176938 - Last Review: June 22, 2014 - Revision: 3.0
Keywords: 
kbbug KB176938

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com