Migration User. Posted Jul 25, AM. Reply Reply Privately Options Dropdown. Is it absolutely necessary to have this?? RE: What is ccSvcHst. On our XenApp servers we have multiple instances, is this absolutely required?? The above-mentioned link does not work. Hi Tom, I have checked this link are working I have copy and paste In SEP The ccSvcHst.
A few hours ago when I rebooted the machine mentioned in my original post, memory usage had ballooned to over , K. Probably best to work with support so they can get some debug logs. I assume it was fine with Same OS across all machines?
The problem has occurred both on machines with Win 7 and Win The SymDiag tool showed no significant issues. I was using a Win 10 laptop this morning and I noticed the fan noise increase. I immediately ran task manager and could see the noted issue with ccSvcHst.
I checked scan logs and live update logs to see if either had just run with negative results. I am puzzled why no one else has reported this on the forums.
I never noticed this issue with I will look into contacting support. Perhaps this issue has already been addressed for a future release. I've got the same problem.
But sometimes only. On one machine only. I have upgraded 14 from The problem occurred 3 times since then. When it happens I can't start even the program SymCorpUi. Only Cleanwipe helps!!! Then the reinstall After reinstalling it works fine. But in weeks, it happens again Very annoying I am also having the same issue with a few servers, Windows R2 and R2.
CleanWipe and a fresh install works for a week or 2 then the issue comes back. Same with a simple reboot. I do notice that the Symantec icon doesn't show up in the System tray when ccSvcHst. To date, I have not started a support call with Symantec.
I have been observing to see if I could find a pattern. The only thing I have found is in some cases when the problem begins if I try launching Live Update my screen flashes and nothing pops up. Not even a message. Reboot always fixes the issue.
I was hoping someone from Symantec might respond to this issue here on the forums. My history with support has been shaky and I am trying to avoid going that route unless absolutely necessary. Right now I am waiting for the first service pack to see if the issue is corrected. Several other known issues with 14 need resolution as well. A Symantec response in this forum would be appreciated. I have the same problem with SEP I have 4 different physical machines that have experienced this problem.
One has an Intel i5 the rest have i7s. The other one has 16gb of memory. I have noted similar usage numbers during defwatch scans but that usage always drops when the scans are completed. The problem machines stay at these percentages and fan noise increases as the CPU usage heats up the machines. I have left the machines alone for over an hour and the CPU percentage never returns to normal. No scans are running and live update is not running.
Reboot required. I have also noted on a couple of machines a W7 and a W10 that occasionally defwatch scans never show completion in the scan log. I see a defwatch scan right now on the W7 machine that started over 4 hours ago and has NOT completed. No excessive CPU utilization is occurring. The only solution is to reboot as you cannot run another scan. Please open a support case for assistance. The system is business-critical and restarting it is undesirable.
Recommended Download and install the Windows Performance Toolkit. Download SymDiag and start gathering debug logs while the issue is happening using the following steps: Set the timer for 5 minutes instead of Run for 60 seconds while reproducing the issue.
Note: Symdiag debug logging and the Windows Performance recorder trace should be running at the same time for 60 seconds. Avoid running the WPR trace for longer than 5 minutes. After reproducing the issue, click Save on the Windows Performance Recorder trace.
Click OK to terminate the Program. The error usually occurs at system startup and shutdown. A bug in certain versions of Norton products, such as Norton , is said to be the main cause of the ccSvcHst error. In fact, ccsvchst. The most common cause of this problem is an outdated file or application. Additionally, you may suffer from this problem if there are some configuration problems with your Norton antivirus or your computer is infected with some type of malware.
There are many methods to fix ccSvcHst. Some of these are listed below. Perform them in the order given and then test your PC. If the problem persists, proceed to the next step. To do this, first open the Start menu and then select Control Panel.
0コメント