Article ID: 221173
Article Last Modified on 6/18/2003
APPLIES TO
- Microsoft Visual Basic 6.0 Learning Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
This article was previously published under Q221173
SYMPTOMS
After creating a Visual Basic application that references remote servers using DCOM and then installing it on a target machine, the application crashes when it tries to call the remote server.
CAUSE
This can occur if you are still using the older version of Clireg32.exe. For additional information on this problem, please see the following article in the Microsoft Knowledge Base:
185193 CLIREG32 Fails to Register TypeLibrary of DCOM server
RESOLUTION
Visual Basic 6.0 ships a newer version of Clireg32.exe that can be found on the Visual Basic 6.0 or Visual Studio 6.0 CDs. However, when you install Visual Basic 6.0 or Visual Studio 6.0, the newer version does not get installed on your machine. Consequently, when you create a distribution package for your Visual Basic 6.0 applications, the Package and Deployment Wizard (PDW) takes the old version of Clireg32.exe from the winnt\system32 directory and includes it in the distribution list. When this happens, you experience the problem described in the above Knowledge Base article.
To solve the problem:
- Check if you have the old version in the winnt\system32 folder. The versions are:
- Old Version: 5.00.3716 Size: 44 kb Date: 1/16/97 12:00
- Old Version: 5.00.3716 Size: 44 kb Date: 1/16/97 12:00
- New Version: 5.00.8168 Size: 42 kb Date: 6/17/98 12:00
- If the old version exists, copy the new version from the Visual Basic 6.0 CD into the Winnt\system32 directory.
- Recreate the distribution files with the PDW.
- Reinstall the client to the workstations.
Keywords: kbdcom kbprb kbwizard KB221173
