SOS Client Hangs - SOS Server Service Locks Up On .VDPROJ

[paulc]

I installed a demo version of SOS 4.2 to work with our SS 2005 repository. We had been using VS 2005 integrated in with SS 2005 which worked fine. SOS 4.2 and SS 2005 repository have been installed on the same machine, a server running Windows 2003 (all updates installed).

On my client I opened VS 2005 and in my options changed my Source Control provider from SS 2005 to SOS 4.2. I then exited VS 2005 and restarted it.

From within Visual Studio I select Open - Source Control - Open From Source Control and attempt to open an setup project (vdproj).

The Visual Studio client locks up, and if I look at the Source Off Site service running on my server, it has locked up using 98% of the CPU. I've left it running for over an hour, and nothing has happened. VS 2005 on my client seems to be waiting, doing nothing.

The log file on the SOS server shows nothing indicating any activity when the service is locked up.

I've tried this multiple times, rebooting both the server and client machines, and the results are always the same - the SOS service on the server machine always locks up.

Any ideas - we were hoping to upgrade from Source Safe 2005 to using SOS but its not looking too promising

I'm using SSAPI.DLL Version: 8.0.50727.42

Log file (showing no output after CPU goes to 98% and service is locked) is attached. I stopped the service after about 4 minutes of it being locked up to flush the output to the log file.

[paulc]

I turned on method logging as well and got the additional lines of log output, telling me that the SOS service was locked up in your PinStatus() method

Is there any way to fix this?

14/11/2006 2:37:54 PM - 3: Exit GetFileList(): $/WorkPlace/MPStudio/V3.0/MSSetup
14/11/2006 2:37:54 PM - 3: Time to execute: 0 minutes, 0 seconds, 46 milliseconds.
14/11/2006 2:37:54 PM - 3: Received message number 102.
14/11/2006 2:37:54 PM - 3: Enter GetFileList()
14/11/2006 2:37:54 PM - 3: Ignore remote dates = True
14/11/2006 2:37:54 PM - 3: GetFileList project:
14/11/2006 2:37:54 PM - Enter PinStatus()

[lbauer]

Let's see if we can narrow things down.

Did you use a new working directory or clear all the project files from you local drive when you did the Open from Source Control? (This includes and virtual directories)>

Are any of the files in the project pinned?

Is this problem specific to the machine or the project? For instance, can another user open the project from Source Control on their machine?

Can you open a different project successfully?

[paulc]

Did you use a new working directory or clear all the project files from you local drive when you did the Open from Source Control? (This includes and virtual directories)>

We used the existing working directory both with and without clearing all project files from the local drive.

Are any of the files in the project pinned?

No

Is this problem specific to the machine or the project? For instance, can another user open the project from Source Control on their machine?

We have tried this with different users and machines. The service on the SOS server locks up in all cases. We have also attempted this many times, with reboots of client and server machines in between, and in every case the results were the same.

Can you open a different project successfully?

Yes - the problem only exists with this VDPROJ file, all of the CSPROJ files in our solution work fine.

Note that using Visual Studio with the Source Safe 2005 provider works fine with this VDPROJ file.

[lbauer]

We'll create a similar project and try to reproduce the problem here. We'll let you know the results.

[lbauer]

We weren't able to reproduce similar errors with a VDPROJ file.

Is there a possibility we could get a copy of your VSS database to try to reproduce it on the actual project? We can sign an NDA.

Email support@sourcegear.com ATTN: Linda if this is an option, and I'll provide instructions for getting it to us.