Visual SourceSafe 2005

[CTSstuart]

Is SOS 4 compatible with VSS 2005?

[lbauer]

Yes. SOS 4.1.2 supports VSS 2005.

We have not tested VSS 2005 with earlier versions of SOS.

[kmenningen]

Hello,

I uninstalled VSS 6.0d and then installed VSS 2005 on the SOS 4.1.2 server. I am able to connect but every file list request gets "Operation failed." Here's the log:

29.4.2006 16:45:32 - 1: 'Kevin' connected to database \\yuma\source\SN\srcsafe.ini
29.4.2006 16:45:34 - Exception during PinStatus: QI for IEnumVARIANT failed on the unmanaged server.
29.4.2006 16:45:34 - 29.4.2006 16:45:34 - Server Exception (400): OPERATION_FAILED
29.4.2006 16:45:34 - 1: Server Error: 400
29.4.2006 16:45:39 - Exception during PinStatus: QI for IEnumVARIANT failed on the unmanaged server.
29.4.2006 16:45:39 - 29.4.2006 16:45:39 - Server Exception (400): OPERATION_FAILED
29.4.2006 16:45:39 - 1: Server Error: 400
29.4.2006 16:49:12 - Exception during PinStatus: QI for IEnumVARIANT failed on the unmanaged server.
29.4.2006 16:49:12 - 29.4.2006 16:49:12 - Server Exception (400): OPERATION_FAILED
29.4.2006 16:49:12 - 1: Server Error: 400
29.4.2006 16:49:21 - 1: Exception: Index was outside the bounds of the array.

Then I rebooted even though the VSS 2005 installer didn't say I had to, and tested again. Same result.

I checked and the VSS 2005 client appeared to work fine with the source code database (files were listed). I then rolled back to VSS 6.0d and everything is now working fine. Can you help me get VSS 2005 working? Thanks!

--Kevin

[lbauer]

There are couple of possibilities -- the SourceSafe automation component may not have been properly registered or you may not be using an official release build of VSS 2005.

Earlier pre-release builds of the VSS 2005 automation component did not work with SOS.

Check the version of the VSS 2005 ssapi.dll file. It will be in the Microsoft Visual SourceSafe directory. Right click on the file and select the Version tab. We know that version 8.0.50727.42 works with SOS.

[kmenningen]

Hi Linda,

Thanks for your very prompt response! It is also useful information for everyone to know the exact version you tested. I took a look at the install files directory (I rolled back to VSS 6.0d so I'm just looking at the VSS 2005 installer) and all the DLLs on the install disk are at 8.0.50727.42 including ssapi.dll.

Should we install again and re-register ssapi.dll? Is the VSS 6.0d threading issue repaired in VSS 2005?

Regarding the log (BTW I have 'medium' logging on, not verbose, would switching to verbose help?) entry:

>Exception during PinStatus: QI for IEnumVARIANT failed on the unmanaged server

Do you know the file name of the 'unmanaged server'? Perhaps we can see if it was not properly registered either (if it isn't ssapi.dll).

Thanks and best regards,

--Kevin

[lbauer]

Exception during PinStatus: QI for IEnumVARIANT failed on the unmanaged server

This is the first report we've had of this error and we're not sure how it relates to SourceSafe/SOS. Based on an Internet search, it's a .NET error. Are you using the English language version of VS 2005 or a different version?

You could try re-registering the automation component, to make sure the SOS Server is using the right one. Instructions here:

http://support.sourcegear.com/viewtopic.php?t=255

Reinstalling first might be good idea, too.

[kmenningen]

Hi Linda,

I'll try your suggestion. It is the English version of VSS 2005, but it is being installed on a machine with a language (non-English) version of Win XP, I believe. Since it's a .NET error, I'll also pursue any patches to the .NET 2.0 Framework that may be necessary. I'll post the results.

Best regards,