When starting the RSA ECAT Console Server, the service is able to connect to the ECAT$PRIMARY database, but the ECAT ServerOutput shows the warning "The Bit9 GSR database was not found".
The issue may be caused due to one of the reasons below.
The optional Bit9 database may not be loaded on the ECAT SQL Server, or it may not be attached.
Sometimes when the Bit9 database is created it is given a different database name, and therefore by default it mounts with the incorrect name.
1. Ensure the Bit9 database is mounted.
On the ECAT SQL Server database machine run the SQL Server Management Studio program, and login to the SQL Server database. Open the list of mounted Databases, and confirm the Bit9 database is showing.
If the Bit9 database is not mounted, then as mentioned in the RSA ECAT Installation Guide, the Bit9 database is optional. Ensure you have downloaded the compressed Bit9 database files from Download Central, and have extracted the files (Bit9GSRBase.mdf and Bit9GSRBase_log.ldf) to the ECAT SQL Server machine.
Follow the instructions in the RSA ECAT Installation Guide to attach the Bit9 database.
a. Go to Start > All Programs > Microsoft SQL Server 2012 > SQL Server Management Studio. b. Right-click Databases and select Attach…. c. In the Attach Databases dialog box, click Add…. d. Navigate to the folder with the Bit9 database. e. Double-click the Bit9GSRBase.mdf file, or select it and click OK.
2. Ensure the Bit9 database is mounted as the database name "Bit9GSRBase".
When attaching the Bit9GSRBase.mdf file if it incorrectly shows an "Attach As" name that is not "Bit9GSRBase", then click into this field and correct the name.
3. Restart the RSA ECAT Console Server service.
Confirm the ECAT ServerOutput no longer shows the warning "The Bit9 GSR database was not found".