The Backup Exec Management Service does not start after upgrading to Backup Exec 2012
|Article:TECH179970|||||Created: 2012-01-26|||||Updated: 2012-06-13|||||Article URL http://www.symantec.com/docs/TECH179970|
If the IIS Admin Service cannot be started on the server Backup Exec 2012 is installed on, then the Backup Exec Management Service will not start. The Backup Exec Management Service will try to start the IIS Admin Service and if it fails to start, the Backup Exec Management Service will also fail to start. Entries similar to the following may also show in the Event Viewer:
* Starting Management service
* Starting IIS Admin service
* IIS Admin service failed to start
* Management service cannot be started
Windows 2003 Std Server SP2 64 bit server
Attempt to manually start the IIS Admin Service. If the service starts up properly, then start the Backup Exec Management Service. If the IIS Admin Service fails to start manually, contact Microsoft's Support to resolve this issue.
*If the IIS Admin service is started and still the BE management service doesnt start check out for event logs in the windows event viewer.
Event Type: Error
Event Source: Backup Exec Management
Event ID: 0
An exception occured starting remoting services for Backup Exec Management Service:
System.ServiceModel.CommunicationException: The tracking (workstation) service is not running. This often indicates that a service that HTTP.SYS depends upon (such as httpfilter) is not started. ---> System.Net.HttpListenerException: The tracking (workstation) service is not running
--- End of inner exception stack trace ---
HTTP SSL : This service implements the secure hypertext transfer protocol (HTTPS) for the HTTP service, using the Secure Socket Layer (SSL). If this service is disabled, any services that explicitly depend on it will fail to start.
Check whether the HTTP SSL service is disabled.
Set it to manual and run the command "net start httpfilter" or start the HTTP SSL service.
Article URL http://www.symantec.com/docs/TECH179970