Since upgrading to NIS 2010 recently, and immediately after having received the 17.5.0.127 update (via LiveUpdate), this old chestnut has returned:
On closing down my computer, this message pops up -
I used to get this some time ago with NIS 2009, then it seemed to have been fixed, but now it's back with NIS 2010 version 17.5.0.127. (Interestingly, I didn't notice the problem with the initial upgrade to NIS 2010, only when I received version 17.5.0.127). I'm running Windows XP SP3.
I'm not the only one who gets this, as many previous posts show. My daughter is also getting this message now on her laptop (also XP SP3) with the same version of NIS 2010. Her laptop is a different make and is running different apps to my 7-year old tower pc, so please don't tell me it's the configuration.
As this issue has come up so many times in the past, does anyone (especially at Symantec, please!) actually know how to fix the problem - or is it like the Ancient Mariner (doomed to roam through cyberspace for evermore)?
1. Exit all the programs. 2. Click Start > Run. 3. In the Run dialog box, type the following text: regedit 4. Click OK. 5. Navigate to the following registry key: HKEY_CURRENT_USER\Control Panel\Desktop 6. In the right pane, right-click AutoEndTasks, and then click Modify. 7. Change the value from 0 to 1 8. Click OK. 9. Exit the Registry Editor.
Thanks Vineeth - it seems to work, but I'll try it for a bit longer just to make sure.
How did you find out about this - is it an official Symantec fix or did you come across it some other way? Also, will the registry change affect anything else?
Vineeth's suggestion simply disables Windows from prompting you about the non-responding application and instead terminates it automatically. This will affect any program that is not responding during shutdown so you could potentially lose any unsaved data if a program were, for some reason, just being slow to save and exit. On the other hand, you would probably click the Close Now button anyhow since you want your machine to shut down and you'd lose that data regardless. You shouldn't be seeing this message at all but Vineeth's solution prevents it from bothering you.
I appreciate that there is a risk of losing data by forcing a program to terminate before it has finished whatever it is doing. What I can't understand is why it's always ccSvcHst that seems to be the culprit.
Is there any reason why it should be slow in terminating? What exactly is ccSvcHst doing at this point that takes so long to complete, and is there a risk of adversely affecting the operation of NIS if Windows forces it to terminate?
It's not exactly a new problem that just affects NIS 2010, as it's been happening to many people who have earlier releases of NIS too. So, bearing in mind it's longish history and repeatability, has Symantec been able to replicate the problem and find a fix for it yet?
I appreciate that there is a risk of losing data by forcing a program to terminate before it has finished whatever it is doing. What I can't understand is why it's always ccSvcHst that seems to be the culprit.
Is there any reason why it should be slow in terminating? What exactly is ccSvcHst doing at this point that takes so long to complete, and is there a risk of adversely affecting the operation of NIS if Windows forces it to terminate?
It's not exactly a new problem that just affects NIS 2010, as it's been happening to many people who have earlier releases of NIS too. So, bearing in mind it's longish history and repeatability, has Symantec been able to replicate the problem and find a fix for it yet?
Many thanks.
There are lots of reasons why it might be slow in terminating. It realistically should never get to the second dialog about not responding during shutdown though. If it takes that long, ccSvcHst is probably hung up somewhere. Shutdown problems can be very difficult to debug though. Forcing a crash and getting a dump file would be the normal proceedure for debugging but during shutdown that can frequently be very difficult to do.
As far as finding a fix is concerned, the answer is yes and no. The two instances of ccSvcHst contain most of your Norton program's functionality. We've found and fixed issues in various different technologies but there obviously is at least one more issue somewhere.
As far as Windows terminating NIS during shutdown, there is a very small risk that it could effect NIS but you're probably safe. Besides, since it isn't shutting down, there's not much more you could do anyhow.
The ccSvcHst shutdown error is one of the symptoms of the NIS-fails-to-load properly v 17.5 bug discussed in other threads in this forum (e.g., http://community.norton.com/t5/Norton-Internet-Security-Norton/Problem-with-NIS-2010-Windows-XP-SP3-17-5-update-Urgent/td-p/193603/page/10). If you are experiencing the shutdown error: When you first startup your PC, make sure you see the NIS icon in your system tray. If you don't, you WILL experience the shutdown error when you shutdown, but the problem is more significant: you're probably not fully protected, and you won't be able to access the main NIS window. (If you DO see the NIS icon in the system tray but still experience the shutdown error, you're probably experiencing something other than the problem I'm referring to.)
The NIS-fails-to-load-properly problem is intermittent--can occur on any reboot. If you experience it, the best thing to do is to reboot again--you might have to do this a couple of times until you see the icon in the system tray. Once you see the icon in your system tray, you're OK until the next reboot.
Symantec is well aware of this issue and working to identify the root cause and develop a fix.
Same problem here -- ccSvcHst not responding when you try to shut down or log off. However, if you press cancel, the system shuts down/logs off. Have not noticed NIS 2010 fail to load, but I have noticed that is seems to be loading Slowly. It used to be among the first things to appear in the tray at login. Latelely it is often much delayed.
I run NIS on three machines (two with XP SP3, one with Win 7). It is only happening on one of them (one of the XP machines.)
Not sure exactly when this started, but I think it has beeen about three weeks now.
I did a complete uninstall using the removal tool, then reinstalled. Thought it was helping, but back to the same today. Wish I had read this thread, first, I probably would have saved my energy. Seems there is a bug in need of squashing. Lookng forward to LiveUpdate fixing this very annoying problem.
A ccSvcHst error on shutdown means that something is causing one of the two ccSvcHst processes to fail to respond properly when requested to quit by Windows. This is a symptom with multiple possible causes. If you're sure the NIS icon has been visible in your system tray during the same session in which you experience the ccSvcHst error on shutdown, you probably have a different problem than the NIS-fails-to-load properly v 17.5 issue that Symantec has recognized and is developing a fix for.
Well, I am now getting this as well and I now notice the NIS2010 tray icon is missing. Also, if I click on NIS2010 on the desktop it does not come up! I assume this is what you are all talking about!
Well I have installed the hotfix, and the problem is not resolved.
About half the time, when someone logs off or shuts down, the error occurrs.
I've used the removal tool and reinstalled. I've removed all software and one driver that was recently installed. I've updated video drivers. Still getting the error.
3) In the end, no files will be sent to Symantec automatically. You will be shown the location of the logs after you complete the form after hitting the "finish" button.
Let me know when you have the logs ready, and I'll send you the location to upload them.
Thanks so much for your instructions on creating debug logs. Unfortunately, the timing was just a little off; I just spent the evening removing 2010 and installing 2009.
i am very sorry that I will not be able to help, at least for now. If I have some time next weekend I will go back to 2010 and then follow your instructions to create a log file.
Again, most sorry. I certainly could have done this today -- our timing just didnt work out.
FYI: Reverting to 2009 seems to have solved the problem.
If you get a chance to reinstall the Norton 2010 product, and if you receive the error message again, please let me know. It would be great if you can provide the log files. Timing may not be a problem. Let me know your time zone, I would be able to come online at your convenient time.
