VS 2k3 "Unable to decrypt user key"

Jason · Post by **Jason** » Thu Aug 26, 2004 7:51 am

Hi --

I'm using SOS 3.5.3 with VS 2k3 and get this particular error whenever I try to use any source controlled files:

Unable to decrypt user key

The weird thing is, SOS works fine on its own. The client logs in and functions properly. Only when using SOS through VS does this error appear. I saw this post: http://support.sourcegear.com/viewtopic.php?t=125 but it doesn't address the difference in the way that the integrated SOS versus standalone SOS treates user keys.

Thanks,
Jason

corey · Post by **corey** » Thu Aug 26, 2004 9:15 am

Let's check to be sure the SOS integrated client is located in the same location as your GUI client. Launch regedit.exe and check the value of key:

HKEY_LOCAL_MACHINE\SOFTWARE\SourceOffSite\SourceOffSite\SCCServerPath

The path given should match the exact location where your GUI client resides.

Jason · Post by **Jason** » Thu Aug 26, 2004 9:33 am

The current contents of that key is:

"e:\Program Files\SourceOffSite\SosScc.dll"

Which definitely points to the correct SOS install dir. Does it matter where my current key resides?

Thanks,
Jason

corey · Post by **corey** » Thu Aug 26, 2004 9:39 am

Yes, in SOS 3.5, the key must reside in the same directory as your executable files, sosscc.dll and sos.exe.

Guest · Post by **Guest** » Thu Aug 26, 2004 11:07 am

Hmm, the key is definitely in that same directory along with the exe and dll...

corey · Post by **corey** » Thu Aug 26, 2004 1:10 pm

Strange. If your Registry points to the correct sosscc.dll, and the sos.exe, sosscc.dll, and key file are all located in the same directory, and if you can correctly connect using the GUI Client and are using the same login name and server address when using the IDE Client, then both clients should work.

Guest · Post by **Guest** » Thu Aug 26, 2004 2:35 pm

Agreed! Too bad VS/SOS don't...

I'm just going to try to reinstall the client. I'll let you know what happens. Thanks!

Jason · Post by **Jason** » Fri Aug 27, 2004 7:49 am

Well, make sense or no, that appeared to fix it. Thanks again for your help!