Testing SoS Client & Server v4.2.x - Hang On

cmf · Post by **cmf** » Tue Jan 09, 2007 4:44 pm

Hi all...

We decide here to test this util to get fast connect via internet.

We notice there is a trouble when refreshing folder using SoS Client.

We now are testing v4.2 both Server and Client, and we use VSS2005.

When open (after successfully validate against VSS database) a folder under the proyect, no refresh is done, and a message in our native language appear saying something this:

"Incorrect parameter"

(sorry about my little english)

in spanish says: "El Parámetro es incorrecto"

so folders under the VSS project are shown fine, but not ther contents.

Here is a copy of what we see in the server error log file:

289aaaa 07:28:45 p.m. - ****************************************************
289aaaa 07:28:45 p.m. - SourceOffSite Server 4.2 Professional - With Cryptography

289aaaa 07:28:45 p.m. - CurrentCulture is es-AR.

289aaaa 07:28:46 p.m. - Server Information
289aaaa 07:28:46 p.m. - Operating System: Microsoft Windows 2000 Server
289aaaa 07:28:46 p.m. - Service Pack: 4.0
289aaaa 07:28:46 p.m. - OS Version: 5.0.2195
289aaaa 07:28:46 p.m. - Locale: Ox0c0a
289aaaa 07:28:46 p.m. - OSLanguage: 3082
289aaaa 07:28:46 p.m. - Total Physical Memory: 494,73 MB
289aaaa 07:28:46 p.m. - Time Zone:
289aaaa 07:28:46 p.m. -
289aaaa 07:28:46 p.m. - SSAPI.dll Information:
289aaaa 07:28:46 p.m. - Location: file:///C:/Archivos de programa/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
289aaaa 07:28:46 p.m. - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
289aaaa 07:28:46 p.m. -
289aaaa 07:28:46 p.m. - Started at 289aaaa 07:28:46 p.m.

289aaaa 07:28:46 p.m. - General logging level is Info. Method logging is Enabled.

289aaaa 07:28:46 p.m. - Number of licenses configured: 10
289aaaa 07:28:46 p.m. - SourceSafe Initialization file(s) located at:
289aaaa 07:28:46 p.m. - C:\Meditar\Proyecto C#\VSS\srcsafe.ini

289aaaa 07:28:46 p.m. - proliant800 is attempting to listen for connections on secure port 8081
289aaaa 07:28:46 p.m. - proliant800 is attempting to listen for connections on unsecure port 8080

289aaaa 07:28:46 p.m. - Waiting for a connection....secure = True
289aaaa 07:28:46 p.m. - Waiting for a connection....secure = False
299aaaa 07:29:22 p.m. - Connection accepted from 192.168.1.7:1604 on local address 192.168.1.1:8080, session id is 1.
299aaaa 07:29:22 p.m. - 1: Enter Authorized()
299aaaa 07:29:22 p.m. - 1: Connection from: celeron-1800-02.rosario.meditar.com (192.168.1.7)
299aaaa 07:29:24 p.m. - 1: Enter Login()
299aaaa 07:29:24 p.m. - 1: User 'carlos' requesting to login to database 'C:\Meditar\Proyecto C#\VSS\srcsafe.ini'
299aaaa 07:29:24 p.m. - 1: Client is speaking protocol version 2.0

299aaaa 07:29:24 p.m. - 1: 'carlos' connected to database C:\Meditar\Proyecto C#\VSS\srcsafe.ini
299aaaa 07:29:24 p.m. - 1: Exit Login()
299aaaa 07:29:24 p.m. - 1: Enter GetProjectTree()
299aaaa 07:29:26 p.m. - 1: Exit GetProjectTree(): $/
299aaaa 07:29:26 p.m. - 1: Enter GetFileList()
299aaaa 07:29:26 p.m. - Enter PinStatus()
299aaaa 07:29:26 p.m. - Exit PinStatus()
299aaaa 07:29:26 p.m. - 1: Exit GetFileList(): $/
299aaaa 07:29:35 p.m. - 1: Enter GetFileList()
299aaaa 07:29:35 p.m. - Enter PinStatus()
299aaaa 07:29:35 p.m. - Exit PinStatus()
299aaaa 07:29:35 p.m. - 1: Exit GetFileList(): $/Proyectos
309aaaa 07:30:00 p.m. - 1: Enter GetFileList()
309aaaa 07:30:00 p.m. - Enter PinStatus()
309aaaa 07:30:00 p.m. - Exit PinStatus()
309aaaa 07:30:00 p.m. - 1: Exit GetFileList(): $/Proyectos/Sistema

and on the client side hour glass is sit forever doing nothing.

We are making some wrong thing?

Thanks in advance...

cmf · Post by **cmf** » Tue Jan 09, 2007 4:53 pm

Further information.

Doing from client side, a "Refresh Project Tree" works fine, while doing "Refresh File List" arise the problem I talked about early.

Seems there is a problem when trying to refresh or get project´s files list.

Thanks once again.

cmf.

lbauer · Post by **lbauer** » Wed Jan 10, 2007 12:43 pm

What version of the VSS Automation Component is SOS Server using? Here's how to find out:http://support.sourcegear.com/viewtopic.php?t=1510

When you check for the version number, also look at Other Version Information->Language.

If you're using a non-English version of the Automation component, this could be causing a problem.

cmf · Post by **cmf** » Wed Jan 10, 2007 1:54 pm

Hi Linda, and thanks for your reply !

I did everything as i can read from this forum, meaning that i knew that kind of questions.

Anyways, here you go:

VSS version on the side where server is running is: VSS2005, so it gives me a ssapi.dll version 8.0.50727.42 with language English US.

Thanks for your reply once again.

PD: we test early version for a while, and no problem reported with same ssapi.dll component and same VSS database.

lbauer · Post by **lbauer** » Wed Jan 10, 2007 5:25 pm

Your configuration looks OK.

Basically, you're not getting the file list, and it's not clear why. The log just stops, with no error.

Was this same SOS installation working properly before? If so, what changed?

Does this happen with any user login, or from any client machine?

Is the user using an SOS 4.2 client?

Try to connect with an SOS Client on the same machine as the SOS server, and use "localhost" for the server name. Does that work?

cmf · Post by **cmf** » Wed Jan 10, 2007 8:13 pm

Was this same SOS installation working properly before? If so, what changed?

Well, before was only used VSS2005 client. And when this error arise, we install previos SOS version on the same server where VSS database is.
It worked fine.

Does this happen with any user login, or from any client machine?
Well, we only test on one client, others in production are using VSS.

Is the user using an SOS 4.2 client?
Yes, both Server and Client are using SOS v4.2.x

Try to connect with an SOS Client on the same machine as the SOS server, and use "localhost" for the server name. Does that work?

Yes, worked fine, with no error. But my scenario was to move the Server component to where Client component is installed. Then configured to point to localhost as you told early. It works great. But we like to move Server component where Server File is. Server File is running Windows 2000 Server Small Bussines.

I hope thats can help.

Sorry about my little english.

And thanks once again for quickly reply.

cmf.

lbauer · Post by **lbauer** » Thu Jan 11, 2007 10:37 am

Let me see if I understand:

If you connect to the SOS Server with an SOS Client on the SOS Server, using localhost, you can get the file list with no problem. Is that correct?

But if you connect to the SOS Server, but the client is on a different machine, you can't get the file list?

cmf · Post by **cmf** » Thu Jan 11, 2007 12:43 pm

Hi Linda...

Yes, You are right !

We prefer SOS Server be installed on the file server wich in turn is running a version of Microsoft Small Bussiness Server 2000 (in disguise Windows 2000).

Further, that machine holds also, the VSS database and has installed a copy of VSS 2005, so SOS Server using SSAPI.DLL, can manage SOS Clients requests. Is that right?

In deeper details, really i "move" (unninstall it and then re-install it), SOS Server to a machine runnig a version of Windows XP Proffesional, wich has also installed the same SOS Client component wich was unable to get the file list in the early scenario.

I hope my english be a bit clear... sorry else.

Thanks once again...

cmf.

lbauer · Post by **lbauer** » Fri Jan 12, 2007 3:23 pm

Further, that machine holds also, the VSS database and has installed a copy of VSS 2005, so SOS Server using SSAPI.DLL, can manage SOS Clients requests. Is that right?

Yes, this *should* work.

If an SOS Client on the same machine as the SOS Server can get the file list, but an SOS Client on a different machine, connecting to the same SOS Server cannot get the file list, then this may be a network issue.

Something is preventing communication between the SOS client and SOS Server when they are on different machines. It could be anti-virus software, a router, something blocking TCP traffic.

cmf · Post by **cmf** » Fri Jan 12, 2007 7:12 pm

I think You are right, but also i think that is hard to debug.

Because the connection with the VSS database, first time the SOS Client goes fine, but when SOS Client try to download or refresh the file list, there is problems are shown.

The only thing i have between the SOS Server and SOS client is both in Client machine and a Server machine a NOD32 version uptodate. But it doesn´t not show nothing about warning and their stuffs.

I will test it from a WAN connection, to see if the problem resides on the LAN side.

I hope it help.

Thanks so much !

cmf.

cmf · Post by **cmf** » Sat Jan 13, 2007 9:17 am

I test it on a WAN link outside the office.

From my house i just installed the SOS Client and try to connect to remote SOS Server but same trouble.

We remember we doesn´t change anything when installed early version of SOS Server and SOS Client.

Earler versions of SOS worked great, without problems. And worked on LAN scenarios as WAN scenarios, like i can verify at this moment.

Perhaps something wrong with SOS Server v4.2.x.

Last, i leave SOS Client 4.2.x and try to connect to SOS Server 3.x via LAN, and connections was fine, and i can retrieve file list, while with SOS Server version 4.2.x i was not able to do that.

If i can contribute to anything more i will. Let´s say to put some more light on this. Once again sorry about my little english.

Thanks in advance as usual...

cmf.

lbauer · Post by **lbauer** » Sun Jan 14, 2007 4:41 pm

What port is SOS 3.5.3 Server using?

What port is SOS 4.2 Server using?

Are they on the same machine?

cmf · Post by **cmf** » Mon Jan 15, 2007 10:48 am

Ports settings was:

Unsecure: 8080
Secure: 8081

in both cases.

But i uninstall one SOS Server version before install the one one.

cmf.

lbauer · Post by **lbauer** » Tue Jan 16, 2007 4:10 pm

Sorry this is taking so long. We don't know what the problem is.

We prefer SOS Server be installed on the file server wich in turn is running a version of Microsoft Small Bussiness Server 2000 (in disguise Windows 2000).

Was SOS 3.5.x working fine on this machine, or was SOS 3.5.x on a different machine?

If SOS has never worked on your file server, we wonder if it is because it has Spanish-language Windows? Sometimes SOS Server does not work properly if the OS is not English.

If we can't determine what the problem is, you might need to install the SOS Server on a different machine on the LAN. It can still communicate with the VSS database, though you need to run the SOS Server Service under a domain account.

cmf · Post by **cmf** » Thu Jan 18, 2007 7:17 am

Linda, no problem.

Yes, SOS Server was worked fine on that machine, we don´t change anything, only install a previous version of SoS, and yes, it worked very fine in the same scenario where version 4.2.x doesn´t.

If see something in the future, please back on this.

I will appreciate it.

Thanks so much.