Stopping service results in crash (90% of times)
Moderator: SourceGear
-
- Posts: 81
- Joined: Sun Aug 06, 2006 12:51 am
Stopping service results in crash (90% of times)
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
[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
- Attachments
-
- Nice pic of problem
- crash.JPG (27.31 KiB) Viewed 18176 times
-
- Posts: 81
- Joined: Sun Aug 06, 2006 12:51 am
bug
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.
This is a service error and the service is running on XP server.
-
- Posts: 81
- Joined: Sun Aug 06, 2006 12:51 am
Bug
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!
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!
-
- Posts: 81
- Joined: Sun Aug 06, 2006 12:51 am
bug
only 2.0. can confirm with 3.0 as well.
-
- Posts: 81
- Joined: Sun Aug 06, 2006 12:51 am
bug
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
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
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 .
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 .
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.
-
- Posts: 81
- Joined: Sun Aug 06, 2006 12:51 am
Bug
And what is the temp directory for SOS Server?