Exception during Login: Invalid OLEVERB structure (Exception

[jfallot]

Hi,

I am currently testing SOS 5.0.3.

The client is unable to connect to the server.

The server log file contains the following error:
2011-03-31 19:13:09,336 - Connection accepted from 10.1.12.27:2890 on local address 10.1.28.137:8080, session id is 3.
2011-03-31 19:13:12,680 - 3: Exception during Login: Invalid OLEVERB structure (Exception from HRESULT: 0x80040000 (OLE_E_OLEVERB))
2011-03-31 19:13:12,680 - 3: Invalid OLEVERB structure (Exception from HRESULT: 0x80040000 (OLE_E_OLEVERB))
2011-03-31 19:13:12,680 - 3: VSS database closed for the session id 3.

The contents of the srcsafe.ini is the following:
Data_Path = \\TERRE\SOFTWARE\VSS\DB.SOLUTIONS
since I need to select a specific Database of a VSS respository hosting several databases
(such kind of redirect was working fine with SOS version 3.5)

The database can be correctly opened with a regular VSS client (2005 version).

What can I do to get a better idea of the source of the issue?

Thank you.

[lbauer]

This looks like a VSS database/VSS automation component issue.

Which version of the VSS Automation Component is the SOS Server using?

To determine the SourceSafe Automation Component (ssapi.dll) version used by SOS Server, look under this registry key:

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

The value will have the path to the specific ssapi.dll file used by SOS Server. For the version information, locate the ssapi.dll file. Right click on the ssapi.dll file, choose Properties->Version.

[jfallot]

Hi Linda,

The registry contents for that key are:

[HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32]
@="C:\\Program Files\\Microsoft Visual SourceSafe\\ssapi.dll"
"ThreadingModel"="Apartment"
"Class"="Microsoft.VisualStudio.SourceSafe.Interop.VSSDatabaseClass"
"Assembly"="Microsoft.VisualStudio.SourceSafe.Interop, Version=5.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
"RuntimeVersion"="v1.1.4322"

[HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32\5.2.0.0]
"Class"="Microsoft.VisualStudio.SourceSafe.Interop.VSSDatabaseClass"
"Assembly"="Microsoft.VisualStudio.SourceSafe.Interop, Version=5.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
"RuntimeVersion"="v1.1.4322"

And the version found is ssapi.dll is: 8.0.50727.42

Regards,
JF

[Beth]

Here's a few things to try.

1) Switch your threading model from Apartment to Both.

2) Install the VSS sp 1 on the SOS Server: http://www.microsoft.com/downloads/en/d ... laylang=en

3) Run analyze against your VSS database when no users are connected. You can get the analyzer to fix as it goes along by running the following command-line command. Replace C:\VSS\Data with the path to your VSS database data folder.

Code: Select all

analyze -C -D -F -V4 C:\VSS\Data