Unable to connect to SourceOffSite

[ACC.GAID]

SourceOffSite version 4.0.2

Once I have entered credentials, the SOS program just displays the message "Logging on.." but nothing further occurs.
The connection is never successful and the Folders and files are never displayed.

Attached a screenshot taken.

[lbauer]

Is this a new problem? Was it working before?

Do other users have problems logging in to the SOS Server?

I see you are using the secure port. Have you imported an encryption key?

What operating system is the SOS Client installed on?

We'd like to see a copy of the SOS Server log. The SOS Server log is called log.txt and is in the SOS Server directory on the SOS Server machine. Reproduce the problem, then send the log to support at sourcegear.com, Attn: Linda. Please include a link to this forum post and let me know what your username is and what time in the log you were trying to connect to SOS.

[ACC.GAID]

Hi,

It is a new problem, but it not continuos, sometimes people can log into the SOS server and another not.
The operating system is Windows Server 2003 Service Pack 1.
I attach the log file from the server.

Thanks & Regards.

[lbauer]

The log does seem to indicate connectivity issues:

1/18/2010 9:52:32 PM - 1: Exception: An existing connection was forcibly closed by the remote host
1/18/2010 9:52:36 PM - Connection accepted from 10.18.208.39:52338 on local address 10.114.104.48:8890, session id is 2.
1/18/2010 9:53:44 PM - 2: Exception: An existing connection was forcibly closed by the remote host
1/18/2010 9:56:34 PM - Connection accepted from 10.18.208.39:52379 on local address 10.114.104.48:8890, session id is 3.
1/18/2010 9:56:50 PM - 3: Exception: Index was outside the bounds of the array.
1/18/2010 9:56:53 PM - Connection accepted from 10.18.208.39:52381 on local address 10.114.104.48:8890, session id is 4.


This could be due to network issues or a problem with the SourceSafe automation component which SourceOffSite uses to connect to the VSS database.

To determine which version of the SourceSafe Automation Component (ssapi.dll) is 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.

What version is your SOS server using?

[ACC.GAID]

Hi,

The version of the SSAPI.DLL is 6.0.98.48

Thanks for your help.

[lbauer]

See if this registry fix helps:

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

[ACC.GAID]

The ThreadingModel was just set to Both. So, that´s not the problem.

[ACC.GAID]

We are still with the problem, is there anything else we can do in order to solve the problem?
Regards

[lbauer]

These errors are hard to troubleshoot, as they are often network related. You also have a lot of databases and users, which could be putting a load on the SOS server.

Are there any firewalls, proxies, anti-virus software that could be closing the connection?

Is there any pattern as to when the connections get closed -- when the client sits idle, or during a long recursive operation, for instance?

If a firewall or other device is closing the connection after a certain amount of time when no data is moving between client and server, you could try enabling the Keep Alive signal in the Vault GUI Client under Tools->Options->General.

We have re-written much of the network part in the SOS Server version 5.0. You could try installing the 5.0 server as a test. You 4.x clients should be able to connect. An SOS 5 server can be installed alongside an SOS 4 server. Let me know if you're interested in pursuing this option.

[peymoore]

We are having exactly the same issue. Remote users can connect OK (and even recently), but periodically when the connect it just appears to hang. The server is running on Win2K3 64bit and this issue didn't occur until after updating from SOS 4.x to 5.0.1 earlier this month.

When the symptom occurs you can't restart the SOS server through Services, but if you kill the SOS process through task manager and then restart, all is good and the same user can immediately connect and get their correct information displayed.

I verified that we have the noted version of ssapi.dll, but we don't have the CLSID referenced to check the threading model.

The last entry written into the sos log on the server simply shows a connection was made, but nothing else.

Any other suggestions or information you might want to know?