SOS 4.0 Connection problem

[Steve D]

Hi, When we try to connect to VSS 4.0 Server via browser to test connection http://servername:8080 we get this error. We cant connect via Browser or VSS 4.0 Client

Any ideas?

Thanks

Steve D

4/8/2004 9:28:57 PM - ****************************************************
4/8/2004 9:28:57 PM - SourceOffSite Server 4.0.0 Professional - With Cryptography

4/8/2004 9:28:57 PM - CurrentCulture is en-US.

4/8/2004 9:28:58 PM - Server Information
4/8/2004 9:28:58 PM - Operating System: Microsoft Windows 2000 Server
4/8/2004 9:28:58 PM - Service Pack: 4.0
4/8/2004 9:28:58 PM - OS Version: 5.0.2195
4/8/2004 9:28:58 PM - Locale: Ox0409
4/8/2004 9:28:58 PM - OSLanguage: 1033
4/8/2004 9:28:58 PM - Total Physical Memory: 255.55 MB
4/8/2004 9:28:58 PM - Time Zone: (GMT-06:00) Central Time (US & Canada)
4/8/2004 9:28:58 PM -
4/8/2004 9:28:58 PM - SSAPI.dll Information:
4/8/2004 9:28:58 PM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
4/8/2004 9:28:58 PM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
4/8/2004 9:28:58 PM -
4/8/2004 9:28:58 PM - Started at 4/8/2004 9:28:58 PM

4/8/2004 9:28:58 PM - General logging level is Error. Method logging is Disabled.

4/8/2004 9:28:58 PM - Number of licenses configured: 1
4/8/2004 9:28:58 PM - SourceSafe Initialization file(s) located at:
4/8/2004 9:28:58 PM - C:\Program Files\Microsoft Visual Studio\Common\VSS\srcsafe.ini

4/8/2004 9:28:58 PM - vels2 (192.168.189.3) is attempting to listen for connections on unsecure port 8080

4/8/2004 9:28:58 PM - Waiting for a connection....secure = False
4/8/2004 9:30:43 PM - Connection accepted from 192.168.189.3:2098, session id is 1.
4/8/2004 9:30:43 PM - 4/8/2004 9:30:43 PM - Server Exception (407): [GET / HTT - Input string was not in a correct format.] - UNRECOGNIZED_MESSAGE
4/8/2004 9:30:43 PM - 1: Failed to start the client instance: UNRECOGNIZED_MESSAGE

[lbauer]

The browser connect test that we used so often in SOS 3.x doesn't work in SOS 4.0.

A better test for 4.0 is telnet. Open a command prompt and type:

telnet <servername or IP> <port>

If the connection is allowed to pass, you should see a message that starts with:

200 Protocol-Version:2.0 Message-ID:00000000 Database Aliases . . .

If you don't see this, something is blocking the connection.

[javamick]

I can telnet to the server on port 8080 and get the response talked about in other posts. I can also see the connection in the log.txt file, but when I try to connect using the program it doesn't do anything and it doesn't log anything in the log.txt file. Any ideas?

Thanks,
Micky

[lbauer]

Where does the client hang, after connecting to the SOS Server or logging in to the VSS database? Can you log in from an SOS Client on another machine?

If you continue to experience problems, try to connect with the SOS Client again and then send me a copy of the log.txt file from the SOS Server directory. Just click on the email link below