Clsidvw.exe OLE/Createable Objects Registry Diagnostic

ID: q176562

The information in this article applies to:

ActiveX Data Objects (ADO), versions 1.5, 2.0
Remote Data Service for ADO versions 1.0, 1.1, 1.5, 2.0

SUMMARY

CLSIDVW.exe is a self-extracting file that contains a setup file for installing the CLSIDView utility.

CLSIDView provides a simple, non-hierarchical view of registered components. CLSIDView allows you to check the properties of Microsoft Data Access Components (MDAC) components without having to cross-reference the ProgIds and Clsids in Regedit.exe. In addition to displaying information about your component, you can register, unregister, mark safe, or correct all related keys for your component. You can also use CLSIDView to correctly register Remote Data Service (RDS) Business objects on a server for HTTP, HTTPS, or distributed component object model (DCOM) protocols.

MORE INFORMATION

The following file is available for download from the Microsoft Software Library:

Clsidvw.exe

Release Date: Nov-19-1997

For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base:

Q119591 How to Obtain Microsoft Support Files from Online Services

CLSIDView is for use by individuals familiar with building Component Object Model (COM) components using MDAC technologies (ODBC, OLE DB, ActiveX Data Objects (ADO), Remote Data Service ([RDS] ). It can be easily extended, though, to manage other component technologies by modification of the Clsidvw.ini file. CLSIDView is designed for use by someone that is familiar with building COM components in Visual Basic, Visual C++, and so forth.

Up and Running Quickly

To install CLSIDView, run the Setup.exe file. After you run the Setup.exe file, the CLSIDView icon will be on the Start menu under Program Files. CLSIDView defaults to looking for all MDAC 2.0 run-time files installed by the MDAC 2.0 Typical Redistribution. CLSIDView lists all of the registered and unregistered components. If any of the .dlls are missing you will see a [NOT FOUND] entry in the list (you may have to change the View menu from Summary to Detail, though). If the .dll exists and is a COM component, but is not registered, you will see [WARNING!-COM COMPONENT NOT REGISTERED] in the ClsId column. In the drop-down text area next to "Find" on the toolbar you can select a different group of components to look for, or you can just type in the name of one COM .dll, .exe, or .ocx server, or multiple servers separated by commas.

Using CLSIDView to Register Remote Data Service (RDS) Business Objects

In the Find combo box you can change to a different set of MDAC components (1.5, 1.1, 1.0, and so on), or you can enter the name of your RDS Business objects (or other automation servers). CLSIDView searches your computer for those objects and gives you information about them. Right-clicking a given .dll in the detail view also gives you the option of performing the registration required by RDS for business objects.

Miscellaneous Usage Tips

Clicking a column header changes the sort order.

You can type in the names of multiple components separated by commas in the Find combo box.

CLSIDView saves the names of the components you type in if it finds at least one of them.

You can edit the ClsidVw.ini file and add your own component sections.

Right-clicking selected components opens the Options context menu.

A [NOT FOUND] message indicates a component you are looking for could not be located on disk.

Some components may exist, but do not need to be registered and is indicated by [NON-REGISTERED COMPONENT].

"Compare to HTML" lets you select an .asp/.htm file to search for createable objects.

If you see the same ProgId listed twice, this means an older version of your component was never unregistered.

To unregister a component that no longer exists from Options, choose Remove, "All related entries...".

"Refresh" re-reads information from the registry.

The toolbar items each have a ToolTip.

If you clear the "Use Find Filter" check box, all registry entries will be listed and the Find combo is ignored.

You can use the "Remote Server..." option to connect to a DCOM server running CIS_DCOM.exe.

You do not need to use Dcomcnfg on the client if you provide a server name under "Remote Server...".

If "Silent registration" is cleared you get the Regsvr32.exe dialog box for each component.

Remove, Server from File System fails if any of the selected servers are in use.

RDS options can be viewed by scrolling to the far right in the Listview control.

The RDS options will be reversed for each of the selected components.

[WARNING!-COM COMPONENT NOT REGISTERED] is displayed if a COM .dll file exists but is not registered.

CLSIDView does a GetProcAddress of DLLRegisterServer on each .dll file to determine if it can be registered.

CLSIDView uses the InprocServer32 or LocalServer key to find a server and get its version information.

CLSIDView searches Windows, Windows\System, and the path of the other servers to find non-registered servers.

If a server you specify cannot be found [NOT FOUND] displays.

Setup Specifics

After running the Setup.exe, five main files exist on your local hard drive The five files are listed in the following table:


   File Name      Description
   ----------------------------------------------------------------------

   ClsidVw.exe    The main .exe file that contains the user interface (UI),
                  which gets all its info from the ClsidSrv.dll file.

   ClsidSrv.dll   Provides high level interfaces for the ClsidView.exe
                  file.

   Registry.dll   Provides registry specific interfaces wrapping the
                  registry API.

   CIS_DCOM.exe   Contains no logic, just implements the ClsidSrv .dlls
                  and interfaces in a distributed component object model
                  (DCOM) .exe server.

   ClsidVw.ini    Contains section information about groups of
                  components.

The three component object model (COM) components can be used outside of the ClsidVw.exe, but they are not well documented or are unsupported.

The Registry.dll file would save a programmer from having to learn the registry API.

Additional query words: Registry Clsid HKEY_CLASSES_ROOT register diagnosis kbfile adoall adoMisc rdsGenInfo rdsall kbdse kbrds100 kbrds150 kbrds200 kbmdac kbsweepnext


Keywords          : kbfile kbADO kbADO150 kbADO200 kbMDAC kbRDS kbRDS100 kbRDS150 kbRDS200 
Version           : WINDOWS:1.0,1.1,1.5,2.0
Platform          : WINDOWS 
Issue type        : kbinfo