Unexpected server error 0x10010000 <site name> <server>

Article:TECH105218  |  Created: 2008-01-25  |  Updated: 2012-06-03  |  Article URL http://www.symantec.com/docs/TECH105218
Article Type
Technical Solution


Issue



Symptoms
Getting a "Unexpected server error 0x10010000 <site name> <server name>" error message in the Symantec Endpoint Protection Manager on the Admin tab.

  • After typing login credentials into the Policy Manager Console error message 0x10010000 displays.
     

Error



Error "Unexpected Server error. ErrorCode 0x10010000."


Environment



-- Server 2003 Standard Edition (32 bit) with SEPM 12.1 installed.


Cause



There are many possible causes for this problem. Be sure to read through all of the possible causes and solutions listed below.

  • After importing the License file (.slf) to the SEP 12.1

Solution



Ensure that all Symantec services are started

  • Check that all database ports are available (1433 for SQL or 2638 for Embedded)
  • Verify ODBC connection
      Verify communication to the embedded (Sybase) database.
      1. Verify that the "Symantec Embedded Database" service is running and that the "dbsrv9.exe" process is listening on TCP port 2638.
      2. Test the ODBC connection.
        1. Click Start> Control Panel
        2. Open Administrator Tools
        3. Double-click Data Sources (ODBC)
        4. Select the System DSN tab
        5. Double-click the SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:
          • Name: SymantecEndpointSecurityDSN
          • Description:
          • Server: Servername\InstanceName (Can be blank as it is localized, otherwise specify default "sem5")
          • Login ID: dba
          • Password: <SEPM Login Password>  
        6. Leave the default settings for the remaining items and click Finish
        7. Click Test Data Source, and verify that it states "Success"
        8. Click OK

      Verify communication to the Remote (SQL) Database.
      1. Verify that you have specified a named instance during installation and configuration. Example: \\\
      2. Verify SQL Server is running and properly configured.
      3. Verify the network connections between Symantec Endpoint Protection Manager and the SQL database.
      4. Test the ODBC connection.
        1. Click Start> Control Panel
        2. Open Administrator Tools
        3. Double-click Data Sources (ODBC)
        4. Select the System DSN tab
        5. Double-click SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:
          • Name: SymantecEndpointSecurityDSN
          • Description:
          • Server: Servername\InstanceName (Only enter the server name or IP address if using the default instance)
          • Login ID: sa
          • Password: <SA Password>  
        6. Leave the defaults for the rest of the items and click Finish
        7. Click Test Data Source on the next page and ensure it states "Success"
        8. Click OK
  • Reboot the machine.


If the still issue persists, perform the Repair on the Symantec Endpoint Protection Manager from Control Panel>>Add/Remove Program..

If the above steps doesnt resolve the issue, examine the scm-server-0.log for possible indications of the cause. By default, this log is located in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs  for both SEP 11 and SEP 12.1
 



Legacy ID



2008062510082748


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


Terms of use for this information are found in Legal Notices