Stopping service results in crash (90% of times)

Jared Sullivan · Post by **Jared Sullivan** » Wed Feb 21, 2007 9:09 pm

This bug report is on XP!!!! Dont ask me for versions cause I just download latest.

[log file]
22/02/2007 2:04:38 PM - Waiting for a connection....secure = False
22/02/2007 2:04:38 PM - Waiting for a connection....secure = True
22/02/2007 2:04:42 PM - Stopping the service.

Thanks Linda or Beth

Beth · Post by **Beth** » Thu Feb 22, 2007 9:47 am

So you're saying that when you stop the SOS service and users are connected that the clients crash rather than giving an error? I'm assuming that when you say the bug is on XP, that your clients are on XP right?

Jared Sullivan · Post by **Jared Sullivan** » Sat Feb 24, 2007 5:27 pm

I never said anything about clients being connecte. I never said anything about service running on clients.

This is a service error and the service is running on XP server.

Beth · Post by **Beth** » Mon Feb 26, 2007 9:18 am

I need a few more details about what's happening.

Stopping service results in crash

Are you manually stopping the service or is it stopping on its own?

Is the entire machine hang when the service is stopped, or just one program, or SOS?

Jared Sullivan · Post by **Jared Sullivan** » Mon Feb 26, 2007 8:15 pm

Hi Beth,

Sorry for late responses all the time but either your notification service is down or my ISP is blocking forum posting notifications.

About the crash:
1. As you can see, it is only a program error - has no bearing on windows 'hanging'.
2. Yes, I am manualling stopping service using services.msc from run menu. Sometimes I just need to reset the server as I use VSS to fairly high capacity.
3. This occurs when no clients are connected also, but I have seen it shutdown correctly sometimes.

Enough questions!

Beth · Post by **Beth** » Tue Feb 27, 2007 11:58 am

What .NET frameworks are installed?

Jared Sullivan · Post by **Jared Sullivan** » Tue Mar 06, 2007 5:36 pm

only 2.0. can confirm with 3.0 as well.

Beth · Post by **Beth** » Wed Mar 07, 2007 9:14 am

Sorry I still have questions because I'm not sure yet what could be causing this. What version of SOS are you using?

Also, if the 3.0 .NET framework is running, that would be helpful to know. We are still testing with the latest Microsoft stuff.

Jared Sullivan · Post by **Jared Sullivan** » Thu Mar 08, 2007 3:43 pm

SOS = 4.1.2.242
NET = 2.0, you should know NET 3.0 is NET 2.0 with crap bolted on. So it doesn't make a difference
VSS = 2005+SP1 on XP

Beth · Post by **Beth** » Fri Mar 09, 2007 11:55 am

Was this the same machine that you had upgraded to Vista and then down graded again?

SOS 4.2 would be a free upgrade for you and that one works better with the 2.0 .NET framework. Previous versions may have issues with it. (See the first point made on our release page: http://sourcegear.com/sos/releaseinfo.html) You may wish to give that a try .

Beth · Post by **Beth** » Fri Mar 09, 2007 1:36 pm

I have recreated this I think. I'll see if I can fix my recreation and will post back.

GlenH · Post by **GlenH** » Wed Mar 21, 2007 1:49 pm

I was having the same problem on a Windows 2003 SP1 server. I added the "everyone" group, Full control, to the temp folder that SOS was using, and performed the fix described in SOS Concurrency Crash and my problem went away.

Jared Sullivan · Post by **Jared Sullivan** » Tue Apr 03, 2007 5:43 pm

And what is the temp directory for SOS Server?

Beth · Post by **Beth** » Thu Apr 05, 2007 2:40 pm

I had recreated the situation and just set the threading model to both and that fixed it.

Jared, does your SOS server start then, or does it not start at all after that error?

rick · Post by **rick** » Sun May 06, 2007 5:53 am

SOS = 4.1.2.242

i have the same problem.
every time manual stop the service , get crashed.

SourceGear Support

Stopping service results in crash (90% of times)

Stopping service results in crash (90% of times)

bug

Bug

bug

bug

Bug