When checking the replication status in Admin >> Servers, it indicates Replication Succeeded. However, on the Home Tab it indicates replication failed.
SEPM version 14
SQL Server 2012
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
Secondary Error: java.sql.BatchUpdateException: Cannot insert the value NULL into column 'USER_NAME', table 'master.dbo.SEP_Alert_Log'; column does not allow nulls. INSERT fails.
The SEP_Alert_Log found in the database was confirmed to be a table trigger that is used to pull notifications from our Alerts table into a 3rd party tool used by the customer to take action on specific alerts.
The 'master.dbo.SEP_Alert_Log' is just one example. This could be any name or schema location specified by the customer.
The use of table triggers are not supported by Symantec for the SEPM database. Have the customer's database administrator disable the table trigger to let replication succeed.
Remove the table trigger and suggest the use of external logging to a syslog server and have the customer pull notifications from the syslog server as a supported means of effectively taking action on specific notifications.
Subscribing will provide email updates when this Article is updated. Login is required.