After restoring a SQL backup of the Symantec Endpoint Protection Manager (SEPM) database or moving the database to a new server, the SEPM no longer functions.
Attempting to run the Management Server Configuration Wizard to reconnect the SEPM to the database results in the following error:
"Failed to add server"
This issue results in the following errors in the tomcat logs:
2011-04-13 13:00:30.987 SEVERE: Unexpected server error. in: com.sygate.scm.server.servlet.StartupServlet
com.sygate.scm.server.metadata.MetadataException: Invalid object name 'CONNECTION_TEST'.
"java.sql.SQLException: Invalid object name 'LOCAL_METADATA'."
A specific user or custom schema was assigned to the database when it was created or later after it was installed. The SEPM is able to connect to the SQL server but can't find the tables in the database because the user currently assigned to the database was not specified when the Management Server Configuration Wizard was run.
In the SQL Management Studio when you expand the database to show the tables or stored procedures, you see a schema (or user) name prefixed to all table names. For example dbuser1.CONNECTION_TEST.
Run the Management Server Configuration Wizard again. When prompted for the database user, specify the same username that is prefixed to the tables.
If you encountered this issue during the upgrade of Symantec Endpoint Protection Manager, then you will need to follow up with re-running "upgrade.bat", which is typically located in the SEPM bin folder: