Class not registered error in Build Machine
 

Hi,
I had some problems in my Build Machine while using VBP 5.7.
I'm using LuntBuild server (http://www.pmease.com/luntbuild/) in order to manage my nightly builds, integration builds.
When LuntBuild runs VisBuildCmd.exe I get the following error message: "Error creating builder component: Class not registered".

If I run VisBuildCmd.exe manually (from a DOS prompt window) this problem does not happen, but sometimes this error shows up
in the GUI interface (in this case, if I restart the vbp gui, the error disappears).

I've read some topics but i didn't found the solution.

(http://www.kinook.com/Forum/showthre...ght=registered)

(http://www.kinook.com/Forum/showthre...ght=registered)

I'd appreciate any suggestions.
Thanks in advance.

By 'using cmd.exe', do you mean using the VBP console app? Both the GUI and console apps use the same method to create the builder component.

That error message is returned from the CoCreateInstance COM API. The error indicates that the lookup of registry information for the builder component is failing (typically because the necessary entries are not found). The pertinent registry keys are

HKEY_CLASSES_ROOT\CLSID\{28DED69C-A541-465C-AA2A-78321E797E83}
HKEY_CLASSES_ROOT\TypeLib\{34DCF8AE-50CB-4D20-A163-D1287F83AA55}
HKEY_CLASSES_ROOT\Interface\{2DA36047-8B60-4333-ACC0-E2D05491DF7A}
HKEY_CLASSES_ROOT\Interface\{6239A18C-E6A1-43C5-99F9-049697FFC325}

The DCOM standard marshaller also gets involved in the creation process (oleaut32.dll, registry key HKEY_CLASSES_ROOT\CLSID\{00020424-0000-0000-C000-000000000046} and others), and if any of that is messed up it can cause issues as well.

But since the problem is sporadic, it sounds more like the registry is corrupt or something is causing registry lookups to sometimes fail. Is the problem specific to a single machine? Can you post the information from Help | About | Install Info? Thanks.

Response
 

Hi,

Yes I use the VBP console app, but sometimes the problem occur in the GUI APP too.


The problem occur only in the Build Machine (I dont have others machines with VBP installed).

Blind the install information:

Visual Build Professional 5.7
Windows Version: 5.1.2600.1.0
Install path: D:\Prog\VisBuildPro
cmax20u.dll version 2.1.0.21
SftTree_IX86_U_45.dll version 4.5a
SftTree_IX86_U_50.dll version 5.01
unins000.exe version 51.15.0.0
VisBuildBld.dll version 5.7.0.0
VisBuildCmd.exe version 5.7.0.0
VisBuildCore.dll version 5.7.0.1
VisBuildDotNET.dll version 5.7.0.0
VisBuildExt.dll version 5.7.0.0
VisBuildLog.dll version 5.7.0.0
VisBuildMisc.dll version 5.7.0.0
VisBuildMS.dll version 5.7.0.0
VisBuildNet.dll version 5.7.0.0
VisBuildPro.exe version 5.7.0.1
VisBuildSvr.dll version 5.7.0.0

Thanks for response.

This was resolved by installing the latest Windows patches via Windows Update.