Endpoint Protection Manager logs show "Invalid object name" when querying SQL
Last Updated May 17, 2019
The Symantec Endpoint Protection Manager (SEPM) is unable to start properly, or has missing information in one or more pages, reports, or logs. Errors are seen in SEPM logs under ...\tomcat\logs.
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Invalid object name 'CONNECTION_TEST'.)
java.sql.SQLException: Invalid object name 'sem5.dbo.SEM_AGENT'.
Scenario A: Permissions are incorrect for the SQL login.
Scenario B: The default database schema for the configured database user does not match the schema name for one or more database objects (tables, views, procedures, etc...).
Scenario A Test and correct permissions for the SQL login and the database user. Logging in with the SEPM SQL login using SQL Management Studio can help with this. Note: The database user should have the db_owner role for the SEPM's database. Also Note: If the SQL login had sysadmin (SA) privilege added for any reason (e.g. migration to 14.x), please remove this privilege once the installation or migration has completed. This privilege will override the default schema assigned to the user and may interfere with normal SEPM functionality.
Scenario B Step 1: SEPM 12.1 and 14.x use the default schema name 'dbo'. Please ensure the database user (default: 'sem5') has the 'dbo' schema, or your appropriate custom schema configured as the default in the user properties. Example: If you use a custom schema name of 'dbouser', the tables would be listed in SQL Management Studio under the SEPM database as dbouser.tablename (e.g. in the sem5 database the tables appear like dbouser.SEM_AGENT). The default schema in the database user properties in this case should also be 'dbouser' to match this custom schema example.
Step 2: If Step 1 does not resolve the issue, or if partial data is shown in the SEPM (e.g. unable to see clients, no data in logs/reports, etc...), it will be necessary to identify objects with the incorrect schema, and transfer them to the correct schema. Confirm the database user schema as above prior to completing the schema transfer. Please contact technical support if you are not familiar with this procedure. Caution: Ensure that necessary SQL backups are present before making any changes.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe