Video Screencast Help

SBS 2011 server is practically unusable after installing SEP 12.1 SBE

Created: 13 Mar 2012 • Updated: 14 Mar 2012 | 2 comments
Chuck Lavin's picture

Hi --

I have a newly installed Windows SBS 2011 Standard server running on dual four-way Xeon 3 GHz processors and 16 GB of RAM. For the past two and a half weeks since the server went online, it has been humming along running at most with a 10% CPU load (usually far lower than that). This server services file/print and Exchange for a four-user office; in this capacity, there is no reason for it to be at any type of continual load. In fact, the EIST subsystem has been throttling back the CPUs' frequencies to save power, since the CPUs were doing practically nothing all day.

Earlier today, we installed SEP 12.1 SBE on this server. After installing the SEP Manager and the SEP client for the server and just one of the PCs, operations have come practically to a standstill. The server now "idles" with a 70-80% CPU load. Ask the server to actually do something, and the eight processor instances all max out at 100%.

It's really difficult to tell what's going on, since CPU utilization numbers change wildly every time the Task Manager refreshes. But most of the processes that repeatedly pop in at the top of the CPU utilization list are dbsrv11.exe *32, SemSvc.exe *32, one or both of the ccSvcHst.exe *32, and several sym* *32 processes that dart in and out of view too quickly.

I obviously can't run the server like this ... I cannot understand how simply installing an antivirus solution would cause an eight-way server to go from <10% CPU utilization to 80-100%, and this obviously needs to be corrected. I also can't understand why all the services and processes associated with SEP on this machine seem to be 32-bit.

What's going on, and how do I fix it (before I just uninstall the whole thing)?


Comments 2 CommentsJump to latest comment

NRaj's picture

This does not look like an expected behaviour.

On a 64 bit platform, the SEP processes will be seen with a *32 suffix. This is by design.

As for the CPU usage. I recommend that you create a case with the tech support to get this clarified.

QuickStart Guide - Create and Manage Support Cases in SymWISE

How to update a support case and upload diagnostic files with MySupport

Create and Manage Support Cases

Contact Business Support

Griffinite's picture

Agree with Chuck SEP 12.1 on SBS 2011 is a stinker!

Not only does it consume CPU, appears to have memory leaks, but causes all sorts of issues with SMB shares.

I've removed it. Problems solved. I won't be logging a support case. If adequate testing had been completed, this would have been evident. I am not spending my time doing R&D for Symantec.