HELP: Cannot connect anymore to server

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
Xavier
Posts: 230
Joined: Tue Mar 01, 2005 5:06 am

HELP: Cannot connect anymore to server

Post by Xavier » Fri May 25, 2007 3:04 am

Hello,

I've installed yesterday Visual Studio 2005 to fix the show diff on pinned file issue. We're now unable to connect to the server !
You will find below the log.
I can connect with Source safe admin, source safe explorer locally on the computer where the sourcegear server is installed. But I cannot remotely.

I've resintalled the VSS2005, Sourcegear 4.2 server locally (on Windows XP); and remotely reinstalled the SourceGear 4.2 client on windows.

Please help...

The error is "invalid handle" as you can see below at the end of the log file.



25/05/2007 10:49:30 - ****************************************************
25/05/2007 10:49:30 - SourceOffSite Server 4.2 Professional - With Cryptography

25/05/2007 10:49:30 - CurrentCulture is fr-FR.

25/05/2007 10:50:32 - Server Information
25/05/2007 10:50:32 - No Operating System information is avaiable
25/05/2007 10:50:32 - Total Physical Memory: 510 MB
25/05/2007 10:50:32 - Time Zone: (GMT+01:00) Brussels, Copenhagen, Madrid, Paris
25/05/2007 10:50:32 -
25/05/2007 10:50:32 - SSAPI.dll Information:
25/05/2007 10:50:32 - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
25/05/2007 10:50:32 - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
25/05/2007 10:50:32 -
25/05/2007 10:50:32 - Started at 25/05/2007 10:50:32

25/05/2007 10:50:32 - General logging level is Error. Method logging is Disabled.

25/05/2007 10:50:32 - Number of licenses configured: 2
25/05/2007 10:50:37 - SourceSafe Initialization file(s) located at:
25/05/2007 10:50:37 - C:\Base Source Safe\cvs\srcsafe.ini

25/05/2007 10:50:37 - INTERNET3 is attempting to listen for connections on secure port 9876


25/05/2007 10:50:38 - Waiting for a connection....secure = True
25/05/2007 10:56:45 - Connection accepted from 192.168.0.54:2672 on local address 84.99.69.48:9876, session id is 1.
25/05/2007 10:56:47 - 1: Exception during Login: The handle is invalid.
25/05/2007 10:56:47 - 1: The handle is invalid.

Xavier
Posts: 230
Joined: Tue Mar 01, 2005 5:06 am

Post by Xavier » Fri May 25, 2007 4:15 am

Some details:
it runs on Windows XP with service pack 2 and patches
it worked with Visual Source Safe 6 sp6 (with the showdiff issue only)
it worked with VSS2005 until a reboot
it works with source 6.0 both remotely and locally
a base check has been done
the v1.0.3705, v1.1.4322 and v2.0.50727 .Net framework are installed

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed May 30, 2007 8:02 am

There is a chance that the automation component you have could be an issue. First, can you provide me the complete version numbers for your automation component? Details on how to do that can be found here: Automation Component Version. It's important to make sure you are going to the one listed in the registry. Some users have multiple automation components on their server.

Xavier
Posts: 230
Joined: Tue Mar 01, 2005 5:06 am

Post by Xavier » Thu May 31, 2007 8:24 am

The file is in C:\Program Files\Microsoft Visual SourceSafe\ssapi.dll

File Version is 8.0.50727.42
In the item name:
8.0.50727.42 (RTM.050727-4200)

Sorry for the delay I was flying back.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Thu May 31, 2007 9:20 am

I believe the version of the ssapi.dll that you have is for VSS 2005. Can you go back to the registry where that path was listed and look for the threading model and set that to 'both'. If it's already set to that, just let me know.

Xavier
Posts: 230
Joined: Tue Mar 01, 2005 5:06 am

Post by Xavier » Thu May 31, 2007 10:36 am

Thanks.It works. :D

May be you should add that to your log file it fails all the time with apartment.

Thanks again. It was a real trouble for us.

Post Reply