|Applies To||RSA Product Set: RSA NetWitness Endpoint|
RSA Version/Condition: 4.x
Platform: Windows, MS SQL Server
|Issue||After moving the RSA NetWitness Endpoint database files (for example ECAT$PRIMARY.mdf and ECAT$PRIMARY_log.ldf) and re-attaching to the RSA NetWitness Endpoint SQL Server database, the RSA RSA NetWitness Endpoint Console Server service now stops immediately when trying to start it.|
The ConsoleServer-Error.log file shows an error message like:
|Cause||The Microsoft SQL Server Broker Service provides messaging and queuing functions between instances.|
This functionality helps in sending messages to remote databases on different servers, and in processing messages within a single database. In order to send messages between instances, the Service Broker uses TCP/IP.
The Microsoft SQL Server Broker Service is required in the ECAT$PRIMARY and ECAT$SECONDARY databases.
The Microsoft SQL Server Broker Service is automatically disabled when moving the RSA NetWitness Endpoint database or when restoring the RSA NetWitness Endpoint database from a backup.
Alternative 1: Enable the Broker service via the GUI
Enable the SQL Server Broker service on the RSA NetWitness Endpoint primary server for the database ECAT$PRIMARY, and if it exists, the ECAT Secondary Server database ECAT$SECONDARY.
Alternative 2: Enable the Broker service via SQL
Another option is to create a SQL query to enable the Broker Service with the following SQL command,
Where [DBNAME] = ECAT$PRIMARY, or ECAT$SECONDARY.
|Notes||If enabling the Broker service fails due to a "GUID does not match" error, see article RSA ECAT 4.x SQL Server is unable to enable SQL Server Broker service, GUID does not match.|