Skip to content

VSS Plugin – Jenkins

October 21, 2011

Was trying to use Jenkins to enable CI for a product which uses VSS as the source code control tool.

Installed the VSS plugin for Jenkins and encountered the following error.

[history] Unable to open database C:\\srcsafe.ini
hudson.util.IOException2: com4j.ComException: 80040154 CoCreateInstance failed : Class not registered : .\com4j.cpp:135
at scm.vss.VSSSCM.getHistoryEntries(VSSSCM.java:304)
at scm.vss.VSSSCM.getHistoryEntries(VSSSCM.java:266)
at scm.vss.VSSSCM.checkout(VSSSCM.java:200)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1193)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:566)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:454)
at hudson.model.Run.run(Run.java:1376)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:230)
Caused by: com4j.ExecutionException: com4j.ComException: 80040154 CoCreateInstance failed : Class not registered : .\com4j.cpp:135
at com4j.ComThread.execute(ComThread.java:189)
at com4j.Task.execute(Task.java:23)
at com4j.COM4J.createInstance(COM4J.java:89)
at com4j.COM4J.createInstance(COM4J.java:67)
at vss.ClassFactory.createVSSDatabase(ClassFactory.java:13)
at scm.vss.VSSSCM.getHistoryEntries(VSSSCM.java:298)
… 9 more
Caused by: com4j.ComException: 80040154 CoCreateInstance failed : Class not registered : .\com4j.cpp:135
at com4j.Native.createInstance(Native Method)
at com4j.COM4J$CreateInstanceTask.call(COM4J.java:105)
at com4j.COM4J$CreateInstanceTask.call(COM4J.java:92)
at com4j.Task.invoke(Task.java:44)
at com4j.ComThread.run0(ComThread.java:149)
at com4j.ComThread.run(ComThread.java:125)
Archiving artifacts
Finished: FAILURE

Took some time to identify the problem.

The problems were

  • The VSS client was not installed into the system, rather it was copied
  • Due to the copying of VSS client, the SSAPI.dll was not registered.

How to solve the problem?

Register the SSAPI.dll which will be available in the WIN32 folder of VSS client

regsvr32 c:\\VSS\\WIN32\SSAPI.dll

and now we are set to have CI……

Advertisements
No comments yet

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: