SEPM intermittently unresponsive

[fred2k]

I upgraded to SEPM version 14.0.2349.0100 earlier this week. Since then I'm getting frequent episodes of unresponsiveness where the SEPM GUI does not respond to anything I click on. If I run Task Manager during this period I can see two Processes called "SemSvc" running without any reported issues, the system performance is ok (plenty of CPU usage available, and 1.2GB available RAM) and I can even minimize the SEPM Window and move it around so it's not like it's completey bombed out like you usually see with Windows applicaitons hanging.  I've found that if I wait it out, I will usually get control back again, sometimes after a couple of minutes, other times I may have to wait half an hour. Inbetween these episodes, SEPM runs perfectly well, no slow down at all.

System details: Windows Server 2008 R2 64-bit SP1 running on a Dell Power Edge 1950 server (Intel Xeon E5320 1.86GHz, 4 GB RAM).

I have run the Symantec Diagnostic Tool during one of these unresponsive periods. It did report a couple of things as per screen shot below, but since there are still resources available I don't believe this is the cause.

Needless to say, this is making it extremely difficult to use.  Any ideas?

 

 

[ℬrίαη]

Seems to be more of an issue with the remote console. Are you accessing from the SEPM or remotely?

Have you tried bumping up the memory to 8 GB to see if that "fixes" it?

Any errors in the scm-server-0.log?

[fred2k]

I'm accessing SEPM directly, but remotely connecting to the server (that shouldn't make any difference right?)

Do you mean physical RAM or virtaul/file paging RAM?

scm-server-0.log has a couple of warnings:

2017-06-09 11:58:56.777 THREAD 46 SEVERE: Your hard disk  space is less than <10,240>MB and impacts the performance of Symantec Endpoint Protection Manager. You should delete some files to free up space. Symantec recommends that you have a minimum of 10GB of free disk space.

2017-06-09 11:19:28.906 THREAD 50 WARNING: Log table switched to: AGENT_TRAFFIC_LOG_1, old table estimated row count: 50019, to add row count in new table: 100, last switch time: 2017-06-08 13:57:55

Do you think either of these could be the cause?  I will be migrating to a new server later this year, but will have to stick with this one for a few months at least.

[ℬrίαη]

Physical RAM to meet the recommended 8 GB.

Low disk space will have an impact. Are you limited to the current HD size or is this a virtual and you can increase it?

[fred2k]

Won't be able to upgrade physical RAM for now, will have to wait for a new system.

Should be able to free up some disk space, will try that later and see if it helps - will report back.

Thank you for your suggestions.

[Manipillai]

Hi, Seems issue fixed in MP2 SEP 14 MP1 causes random hangs on servers and desktops FIX ID: 4071163, 4071509, 4075683, 4079555, 4080313, 4082812, 4083960, 4085244 Symptom: Servers and desktop computers lock up or hang after they upgrade to Symantec Endpoint Protection 14 MP1. During this hang, you cannot connect remotely to the systems using programs such as Remote Desktop Connection. This issue also occurs with virtualized servers and desktop computers hosted on VMware and Hyper-V. You do not get a log on screen, nor can you access anything on the computers while they are in this state, though the affected systems may respond to pings. This issue appears to occur at random. A restart allows the affected computers to work again, but the issue may return. Solution: Changed the Auto-Protect code so that it does not encounter deadlocks under certain circumstances. Ref link: https://support.symantec.com/en_US/article.INFO4375.html

[fred2k]

Hi Manipillai,

Thanks for letting me know.  My timing really sucked here... I think MP2 was released like 1 day after I did this lol