SOS and VS2005 Hanging when getting latest version
Moderator: SourceGear
-
- Posts: 7
- Joined: Wed Dec 12, 2007 9:51 am
SOS and VS2005 Hanging when getting latest version
I am running Windows Server 2005, Visual Studio 2005 and SOS 4.2. I have tried getting latest from both SOS and from VS 2005 but it keeps hanging. I've tried delting the solution and restarting but nothing seems to help.
How large of a solution are you getting from?
Can you check your SOS log file on the server for errors or post it? (Or you can send it to support at sourcegear.com [attn: Beth]with a link to this thread.)
What happens if you open up your SOS client and perform a Get on either one file or a small folder that is in that solution?
Can you check your SOS log file on the server for errors or post it? (Or you can send it to support at sourcegear.com [attn: Beth]with a link to this thread.)
What happens if you open up your SOS client and perform a Get on either one file or a small folder that is in that solution?
-
- Posts: 7
- Joined: Wed Dec 12, 2007 9:51 am
-
- Posts: 7
- Joined: Wed Dec 12, 2007 9:51 am
Any chance the log is coming my way?
Was this working previously? I know there was a CTP released, but I'm not sure if that's going to affect this or not. Did you install that?
Hanging often is due to something with the automation component, though it seems odd that it happens on only one file. Can you go into the registry on the SOS server and go to this location: HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32.
Next, find the "ThreadingModel" Key, and set its value to "Both".
It could be that some socket is closing on the network, but I won't really know until I know what the server says.
Was this working previously? I know there was a CTP released, but I'm not sure if that's going to affect this or not. Did you install that?
Hanging often is due to something with the automation component, though it seems odd that it happens on only one file. Can you go into the registry on the SOS server and go to this location: HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32.
Next, find the "ThreadingModel" Key, and set its value to "Both".
It could be that some socket is closing on the network, but I won't really know until I know what the server says.