Operation Failed

rnettles · Post by **rnettles** » Thu Oct 19, 2006 8:15 am

I recently moved our Source Code from a Windows NT server to a Windows server 2003 SP1. The old server used VSS 6.0, while the new server uses VSS 2005. The SOS server version is 3.5.1.

I am able to use the SOS client to view the source directory structure and even get the latest version of code. However, it appears that certain write processes, such as 'Check Out', will produce the error 'Operation failed'. However, I am able to successfully 'Label' files with the client.

The H: Drive is a local disk. The SourceOffSite Server service is running under the SYSTEM account, which has Full Control rights to the H: disk.

Server Log File Begin -------------------------------
SourceOffSite Server 3.5.1
Professional Edition (Export Permitted)

Operating System: Windows NT 5.2

Java VM: Microsoft Corp. Version 1.1.4

Pin Support enabled.

Debugging output enabled.

VSS DLL synchronization disabled.

Number of licenses configured: 65

SourceSafe Initialization file(s) located at:
H:\TNP\Desktop\Lean\srcsafe.ini
H:\TNP\Desktop\Lean1\srcsafe.ini
H:\TNP\Desktop\DBLAB\srcsafe.ini
H:\TNP\Desktop\Universal Softphone\srcsafe.ini

Listening for connections on secure port 8890
Listening for connections on unsecure port 8888

Thu Oct 19 09:58:39 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - Connection Established
Thu Oct 19 09:58:41 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - "rnettles" connected to database: H:\TNP\Desktop\Lean\srcsafe.ini
Thu Oct 19 09:58:42 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - Begin Get File List Operation: $/_CCF Lean 08_23_04/Client/Ccf/BankOfAmerica.Ccf.UI
Thu Oct 19 09:58:42 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - Thread Thread-3 is now the alpha thread
Thu Oct 19 09:58:42 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - Getting version information
Thu Oct 19 09:58:42 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - Version information obtained

...

(171.164.140.26) - Getting version information
Thu Oct 19 09:59:14 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - Version information obtained
Thu Oct 19 09:59:14 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - End Get File Operation: MainForm.cs
Thu Oct 19 09:59:14 EDT 2006 - B000F1FB6AE18.nc.bankofamerica.com (171.164.140.26) - Begin Checkout Operation: MainForm.cs
Server Log File End ---------------------------------

I saw in another customer's post that registering the correct ssapi.dll for VSS 2005 fixed their problem. I'm wondering if I need to do the same, and how to obtain the file if necessary.

Please help as this is urgent.

lbauer · Post by **lbauer** » Thu Oct 19, 2006 11:54 am

We haven't tested SOS 3.5 with VSS 2005. It is fully supported with SOS 4.1.2 and later.

We might be able to sort out whether this is just a regular configuration issue or an incompatibility issue.

What is the path to the ssapi.dll listed in this registry key:

HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32

Is it pointed to your VSS 2005 client location?

rnettles · Post by **rnettles** » Thu Oct 19, 2006 12:17 pm

The path in the registry is set to: D:\Apps\Microsoft Visual SourceSafe\ssapi.dll

There are 3 ssapi.dll files located on the server:
D:\Apps\Microsoft Visual SourceSafe
D:\Apps\Microsoft Visual Studio\VSS\win32
D:\Apps\Microsoft Visual Studio\VSS\netsetup.x86\VSS\win32

It appears that the client exe and the server exe are both located in the same directory of D:\Apps\Microsoft Visual SourceSafe. I could be mistaken.

Is this helpful, or anything else we can check?

lbauer · Post by **lbauer** » Thu Oct 19, 2006 1:27 pm

This looks like the registered ssapi.dll (VSS Automation Component) may be for for VSS 2005. (VSS 2005 has no win32 directory.)

What is the version of the ssapi.dll file in D:\Apps\Microsoft Visual SourceSafe? (Right-click, Properties->Version)

What is the version of the ssapi.dll file in D:\Apps\Microsoft Visual Studio\VSS\win32

I would not suggest manually registering the ssapi.dll at this point. First of all, it already seems to be registered, secondly registering the VSS 2005 ssapi.dll seems to cause registry changes that make it nearly impossible to go back to using the VSS 6.0 automation component.

rnettles · Post by **rnettles** » Thu Oct 19, 2006 1:40 pm

D:\Apps\Microsoft Visual SourceSafe\ssapi.dll = 8.0.50727.4 (RTM.050727-4200)
D:\Apps\Microsoft Visual Studio\VSS\win32\ssapi.dll = 06.00.9350

I am assuming you'd want me to point
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32]
to D:\Apps\Microsoft Visual Studio\VSS\win32\ssapi.dll

???

lbauer · Post by **lbauer** » Thu Oct 19, 2006 3:54 pm

I just tested SOS 3.5.3 with the VSS 2005 automation component and got an error connecting to the database, plus this in the log:
Thu Oct 19 16:30:46 CDT 2006 - tower.ad.sourcegear.com (65.161.114.170) - (0x80029c4a) Error loading type library/DLL. I couldn't even log in.

I think this confirms that SOS 3.5.3 does not support VSS 2005.

You could point the path in the registry to:
D:\Apps\Microsoft Visual Studio\VSS\win32\ssapi.dll = 06.00.9350

This is VSS 6.0c, which works with SOS 3.5.3.

Restart the SOS Server after changing the path.

NOTE: We haven't tested the scenario of what happens if some users have VSS 2005 clients and others are using SOS with the VSS 6 automation component against the same VSS databases.

For best results VSS client version and VSS automation component version used by SOS should match.