Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

WSAD not connecting to ClearCase

19 views
Skip to first unread message

Kelly Han

unread,
Jul 14, 2003, 9:52:45 AM7/14/03
to
WSAD (version 5.0.1) was connecting to ClearCase fine till one day it
suddenly stopped. I installed WAS 5.0.1 a few days before that happened.

WSAD configuration detail says,
com.rational.resourcemanagement.cmframework.CMConnectException: Cannot find
Source Control tool information on this machine.

at
com.rational.resourcemanagement.cmframework.ProviderMgr.attach(ProviderMgr.j
ava:109)

at com.rational.clearcase.RSCMService.initialize(RSCMService.java:1230)

........

Anyone know why it is doing that? Thank you!

Kelly


Juan Manuel Martinez

unread,
Jul 14, 2003, 11:27:25 AM7/14/03
to
In article <beucji$aahg$1...@news.boulder.ibm.com>, kell...@s1.com says...

> Anyone know why it is doing that? Thank you!
>
>
After updating WSAD, did you also update Clearcase plugin? It is available through Update
Manager too.
--
Juanma Martinez

Kelly Han

unread,
Jul 14, 2003, 2:12:12 PM7/14/03
to
Thanks Juanma, I managed to install the clearcase plugin, it didn't make any
difference. I have been using WASD 5.0.1 all along, it was connecting to
ClearCase till one day it decides not to...

Kelly

"Juan Manuel Martinez" <juanma_...@es.ibm.com> wrote in message
news:MPG.197cea479...@news.software.ibm.com...

Stefan Schurman

unread,
Aug 6, 2003, 11:04:03 AM8/6/03
to
Hi Kelly,

This error is displayed when the SCC provider is not properly being
presented by the Operating System (I'm not sure why this would have changed
though).

1.) Confirm the presence of the following registry key:
\HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\
with a string of:
ProviderRegKey = Software\Atria\ClearCase

2.) Confirm the presence of the following registry key[s]:
\HKEY_LOCAL_MACHINE\SOFTWARE\Atria\ClearCase
with strings of:
SCCServerName = ClearCase
SCCServerPath = ccscc.dll

Setting the above keys properly should resolve the problem.

Regards,
Stef


"Kelly Han" <kell...@s1.com> wrote in message
news:beurq3$8v72$1...@news.boulder.ibm.com...

0 new messages