|Applies To||RSA Product Set: ECAT|
RSA Version/Condition: 4.x
Platform: Windows, MS SQL Server
|Issue||After moving the ECAT database files (for example ECAT$PRIMARY.mdf and ECAT$PRIMARY_log.ldf) and re-attaching to the ECAT SQL Server database, the RSA ECAT Console Server service now stops immediately when trying to start it.|
The ConsoleServer-Error.log file shows an error message like:
4/06/2015 10:13:49 AM
|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 ECAT database or when restoring the ECAT database from a backup.
Alternative 1: Enable the Broker service via the GUI
Enable the SQL Server Broker service on the ECAT 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,
ALTER DATABASE [DBNAME] SET ENABLE_BROKER WITH ROLLBACK IMMEDIATE
Where [DBNAME] = ECAT$PRIMARY, or ECAT$SECONDARY.
|Notes||If enabling the Broker service fails due to a "GUID does not match" error then see KB# RSA ECAT SQL Server is unable to enable SQL Server Broker service, GUID does not match|