It would be great if you can get us the actual dump. I will be able to pass the dump to the concerned team. Let me know when you have this ready, I will help you to upload it.
Thanks!
Vineeth
The OP is unable to create the dump as I proposed because it does not work with the USB keyboard he feels.
It would be great if you can get us the actual dump. I will be able to pass the dump to the concerned team. Let me know when you have this ready, I will help you to upload it.
Thanks!
Vineeth
Hi, Veneeth,
I was unable to create a dump because on XP, the registry entry that enables BSD on ctrl-scroll lock only works with PS/2 keyboards.
caa100, ccSvcHst shutdown problems are very difficult to reproduce and diagnose. If you're willing to take the effort, there are a few diagnostic steps that you could take to help isolate the problem. The first of which would be, if you boot your system and instantly shut it down, before logging in, does the problem occur? If you wait five minutes without logging in and then shut down, does the problem occur? If you log in and then instantly shut down, does the problem occur? If you log in, do nothing for five minutes, and then shut down, does the problem occur? All of these questions are designed to figure out which instance of ccSvcHst is hanging and whether it is other services or start up items that may be causing the hanging. If the problem doesn't present under any of the preceding scenarios, then try to determine if opening and closing a browser or opening and closing an e-mail reader before shutting down causes the problem.
Reese, thanks for responding. I can answer one of your questions straight off: it HAS occurred when a user logs in, waits a moment, then logs out without launching any programs. (It is intermittent, and sometimes this does not cause a problem.) I will reinstall NIS2010 and get answers to your other questions. Since it is intermittent, I will try each one several times with reboots in between. Thanks, I’ll be back with results when I have them.
cif you boot your system and instantly shut it down, before logging in, does the problem occur? If you wait five minutes without logging in and then shut down, does the problem occur? If you log in and then instantly shut down, does the problem occur? If you log in, do nothing for five minutes, and then shut down, does the problem occur?
Boot up, shut down immediately from Welcome screen:
5 tries, no errors
Boot up, wait 5 minutes without logging in, shut down from welcome screen:
5 tries no errors
Boot up, log in, shut down immediately:
5 tries, 1 error
But up, log in, wait 5 minutes, shut down
5 tries, 1 error
Also of note:
If I run anything after logging on, the odds of getting the error when I log out are greatly increased.
Fore example: Boot log in, Launch NIS, click "help" then "version" , close NIS, shut down: 5 tries, get the error 4 times
If I boot up, log in, log out immediately, log in, and log out again, I usually get the error on the second log out.
Whether you press "End now" or "Cancel", the result is the same -- the logout process continues
The error occurs on logout before the desktop display goes away. Not until after dealing with the dialog error dialog does the sceen clear, at which point you see the usual "Closing Network Connections" then "Saving your settings" then "shutting down"
caa100, thanks for being so diligent and trying these items out. From the symptoms, it appears that the user session instance is getting stuck. You've now mentioned that you have the add-on pack installed. I suspect that that may be the culprit. Can you uninstall it and see if the problem persists?
The fact that you can reproduce the problem four out of five times is promising, if only we could get it to 5 out 5. With the current 4 out of 5, though, we might be able to force a couple of dumps and figure out what's going on from one of them.
caa100, thanks for being so diligent and trying these items out. From the symptoms, it appears that the user session instance is getting stuck. You've now mentioned that you have the add-on pack installed. I suspect that that may be the culprit. Can you uninstall it and see if the problem persists?
The fact that you can reproduce the problem four out of five times is promising, if only we could get it to 5 out 5. With the current 4 out of 5, though, we might be able to force a couple of dumps and figure out what's going on from one of them.
Yep, add on pack seems to be at the heart of the matter:
Removed the add on pack, and the problem seems to be resolved. (Rebooted several times, logged in and out as different users, ran various applications, and did not see the problem.)
Reinstalled the add on pack, and the problem has returned.
We have looked at your dump and recognized a problem. I now have to pass the issue to the responsible team to get a more specific diagnosis. Thank you for your help so far!
FYI, the fix for this issue is currently scheduled to be included in the next release of the add-on pack. No, I can't tell you when it's expected to be released...