Symantec Endpoint Protection Manager Unexpected Server Error & Embedded Database Service Fails to Start

So I am in mid-swing of a Windows Server 2012 upgrade which involves migrating my Symantec Endpoint Protection Manager installation to this new server.  All is going well until I go to the server configuration wizard and get this lovely little error message:

SEPMerror

As always, while scouring the Internet, there are plenty of different solutions out there.  Which is great and painful all at once, because obviously none of them work until you find one that does.  Which also involves making a change, testing it and then if it doesn’t work, switching back.  Now, cutting to the chase, here is my situation and solution:

Issue:

  1. When launching Symantec Endpoint Protection Manager (SEPM), a console error dialog box is displayed that reads “Unexpected server error.”
  2. When looking at the services tool in administrative tools on the server, the Symantec Embedded Database service is not started, starts and stops or fails to start.

Solution:

  1. Check the SID of the service
    1. On the computer where SEPM is installed, click Start > Run (unless it is server 2012, the begin with step 2 below).
    2. Type CMD or COMMAND and click OK (in server 2012, you will have to click or highlight the resulting search item).
    3. At the command prompt, type:  sc qsidtype SQLANYs_sem5
    4. You should see the following (hopefully, if you are experiencing my same error):
          [SC] QueryServiceConfig2 SUCCESS
          SERVICE_NAME: SQLANYs_sem5
          SERVICE_SID_TYPE: RESTRICTED
  2. Change the SID type of the SQLANYs_sem5 service to UNRESTRICTED
    1. On the computer where SEPM is installed, click Start > Run (unless it is server 2012, the begin with step 2 below).
    2. Type CMD or COMMAND and click OK (in server 2012, you will have to click or highlight the resulting search item).
    3. Type: cd “<Drive>:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin”
    4. Type:  ServiceUtil.exe -changeservicesidtype 1 -servicename “SQLANYs_sem5”
  3. Verify that the SID type has no changed to UNRESTRICTED by following the steps outlined in item 1 above.

I sincerely hope this helps you or someone else – it worked for me!  Twice for that matter since I accidentally uninstalled it after having gone through this mess!  So I had to search for the answer twice!  Now I’m documenting it here in case I ever need to find it again!

, ,

No comments yet.

Powered by WordPress. Designed by Woo Themes