Add a file to a project doesn't work in SOS but does in VSS

epsobolik · Post by **epsobolik** » Mon Jan 07, 2008 10:23 am

We have SOS 4 and VSS 6. Some one tried to add a file to an existing project using SOS and got an 'Invalid parameter' error. He then emailed the files to work and added the files to VSS successfully. Any ideas?

Phil Sobolik

Beth · Post by **Beth** » Mon Jan 07, 2008 11:42 am

You will want to check your SOS log (log.txt) located on the SOS server to see what it says for around the time that the user added the file. There may be more detailed errors listed there. I don't have enough information to know what could have happened.

epsobolik · Post by **epsobolik** » Tue Jan 08, 2008 1:42 pm

Here's the log file for the weekend (when he first had the error) and Monday (when he tried from the office). Connection 17 is him on Monday 1/7. He said he did something else at 10:10, which was right after he had the trouble. So it should have been between 9:52 and 10:10 on 1/7. There doesn't seem to be any activity. Note the wierd error about connection 17 immediately after connection 18 is established. It's almost as if the 17 in the log entry should have been 18.

Phil

1/5/2008 7:20:16 AM - Connection accepted from 71.184.255.9:2822 on local address 146.115.10.14:8888, session id is 6.
1/5/2008 7:29:44 AM - 6: Exception: An existing connection was forcibly closed by the remote host
1/5/2008 7:34:41 AM - Connection accepted from 71.184.255.9:3197 on local address 146.115.10.14:8888, session id is 7.
1/5/2008 7:42:09 AM - Connection accepted from 71.184.255.9:3395 on local address 146.115.10.14:8888, session id is 8.
1/5/2008 8:53:09 AM - Connection accepted from 209.6.134.100:1336 on local address 146.115.10.14:8888, session id is 9.
1/5/2008 9:07:09 AM - 9: Exception: An existing connection was forcibly closed by the remote host
1/5/2008 10:52:39 AM - Connection accepted from 209.6.134.100:1429 on local address 146.115.10.14:8888, session id is 10.
1/6/2008 12:50:19 PM - Connection accepted from 70.185.212.100:2405 on local address 146.115.10.14:8888, session id is 11.
1/6/2008 12:50:36 PM - Connection accepted from 70.185.212.100:2414 on local address 146.115.10.14:8888, session id is 12.
1/6/2008 2:32:28 PM - Connection accepted from 146.115.10.148:2558 on local address 146.115.10.14:8888, session id is 13.
1/6/2008 2:32:28 PM - 1/6/2008 2:32:28 PM - Server Exception (411): UNAUTHORIZED_USER
1/6/2008 2:32:29 PM - 13: Exception during Login: UNAUTHORIZED_USER
1/6/2008 2:32:29 PM - 13: Login Server Error - 411
1/6/2008 5:14:50 PM - Connection accepted from 71.184.255.9:2576 on local address 146.115.10.14:8888, session id is 14.
1/6/2008 5:20:25 PM - 14: Exception: An existing connection was forcibly closed by the remote host
1/7/2008 8:21:13 AM - Connection accepted from 209.6.134.100:1765 on local address 146.115.10.14:8888, session id is 15.
1/7/2008 8:29:23 AM - Connection accepted from 209.6.134.100:1767 on local address 146.115.10.14:8888, session id is 16.
1/7/2008 9:52:58 AM - Connection accepted from 146.115.10.177:1122 on local address 146.115.10.14:8888, session id is 17.
1/7/2008 10:40:49 AM - Killing disconnected or idle client host177.wrightsoft.w.subnet.rcn.com - (146.115.10.177)
1/7/2008 10:40:49 AM - Connection accepted from 146.115.10.159:60627 on local address 146.115.10.14:8888, session id is 18.
1/7/2008 10:40:49 AM - 17: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall
1/7/2008 10:40:49 AM - Killing disconnected or idle client host159.wrightsoft.w.subnet.rcn.com - (146.115.10.159)
1/7/2008 10:40:49 AM - 18: Exception processing messages: A blocking operation was interrupted by a call to WSACancelBlockingCall
1/7/2008 10:41:59 AM - Connection accepted from 146.115.10.159:60647 on local address 146.115.10.14:8888, session id is 19.
1/7/2008 10:42:35 AM - Connection accepted from 146.115.10.159:60657 on local address 146.115.10.14:8888, session id is 20.
1/7/2008 10:42:38 AM - 20: Exception during Login: Invalid password
1/7/2008 10:42:38 AM - 20: Invalid password
1/7/2008 10:42:42 AM - Connection accepted from 146.115.10.159:60659 on local address 146.115.10.14:8888, session id is 21.

Beth · Post by **Beth** » Tue Jan 08, 2008 2:29 pm

The first thing I think would be to check if you are on SOS 4.2. If you are on some other version of 4.x, then it will be a free upgrade to 4.2.

Can you tell me the exact automation component version that is being used? You will want to use these instructions for determining that: Automation Component Version

Most of the automation components work best when the threading is set to 'both' rather than 'apartment.' You can find instructions on how to make that change here: Automation Component threading change

epsobolik · Post by **epsobolik** » Tue Jan 08, 2008 3:00 pm

We were at 4.1.2. I installed the update to 4.2. The version of ssapi.dll that is being used is 6.0.81.69. Threading was set to 'both'. He will try to duplicate his problem.

epsobolik · Post by **epsobolik** » Tue Jan 08, 2008 3:15 pm

Well, a little progress. He was getting the 'Bad parameter' error when he clicked on the 'Add files to the current project' button on the toolbar. He can now click that button and get a dialog. However, the list of local drives and the folders are garbage - the proverbial DOS graphics files.

Beth · Post by **Beth** » Tue Jan 08, 2008 3:36 pm

Where is the VSS server in relation to the SOS server?

Could you load an SOS client right onto the SOS server, then open it and connect using localhost. Then try loading files from there. This will take some of the network components out of the equation to help narrow this down.

Can you post a screenshot of what you are currently seeing?

epsobolik · Post by **epsobolik** » Tue Jan 08, 2008 4:49 pm

The SOS and VSS servers are on the same Win2003 Server machine.

Computers inside the network can add files to the same project with SOS.

Beth · Post by **Beth** » Tue Jan 08, 2008 5:08 pm

Often firewalls and routers can cut off connections, so that will be one area you will want to check.

In SOS Tools - Options, there is a setting for a Keep Alive Signal. Try setting that to see if it helps prevent the closed connections.

Are all other operations working fine? You can check out a file with the GUI, edit it, and check it back in?

How large are the files that you are checking in?

Can you increase the logging level on the server to verbose? Instructions on how to do that can be found here: Debug and Method Logging

epsobolik · Post by **epsobolik** » Wed Jan 09, 2008 9:09 am

So, you're saying that the garbage characters in the drive and folder of the 'add files to project' is due to the connection being lost? It seems like very little has been done between the server and client at this point. It's just collecting which files to add. It seems like the problem would be on the client side.

Phil

Beth · Post by **Beth** » Wed Jan 09, 2008 1:33 pm

Sorry, I meant the disconnects could be why he's not able to add. I had asked for a screenshot of where the garbage characters showed up. I would suggest doing the other things suggested in this post first though.

I looked up your component version and it appears there were some issues with the automation component version you are using. If you want, we have a different version that we know has good results posted here: VSS 6.0c fix.

If you use our download link on that page (the 2nd one) it will have instructions included with it.

Another version that works well is 6.0d (6.0.98.48).

SourceGear Support

Add a file to a project doesn't work in SOS but does in VSS

Add a file to a project doesn't work in SOS but does in VSS

Log file