The Symantec Scan Engine 5.2 service fails to start during a Server reboot.

Article:TECH177879  |  Created: 2011-12-28  |  Updated: 2012-01-05  |  Article URL http://www.symantec.com/docs/TECH177879
Article Type
Technical Solution



Issue



When a Server starts up or is rebooted the Symantec Scan Engine 5.2 service fails to start in a timely fashion, and the Scan Engine service has to be manually started again after the Server is up.


Environment



Symantec Scan Engine
Windows Server


Cause



Typically we see this issue occurs in a heavily loaded environment.  Such as a Server that is running several CPU intensive processes, with the Server itself being hosted by a heavily loaded vmware server.


Solution



One solution to help with this is to try increasing the Service Control Manager timeout period.  The default SCM timeout period is 30 seconds, and if a service does not report to the SCM within this timeout period the SCM will terminate that process.  Below is a link with details on how to change the Service Control Manager timeout period,

technet.microsoft.com/en-us/library/cc756351(WS.10).aspx

Please note the parameters value is in milliseconds, and the default value is 30 seconds (30000 milliseconds).




Article URL http://www.symantec.com/docs/TECH177879


Terms of use for this information are found in Legal Notices