000033469 - Cannot connect to the database/cannot get database version information in RSA ECAT

Document created by RSA Customer Support Employee on Aug 2, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000033469
Applies ToRSA Product Set: ECAT
RSA Version/Condition: 4.1.1, 4.1.2
Platform: Windows
O/S Version: 2008 Server R2 Enterprise (64 bit), 2012 Server
Product Name: RSA Netwitness Endpoint.
IssueLogin attempts fail on ECAT 4.1.1 and 4.1.2 with error messages like those shown below:
User-added image
User-added image
CauseThis is due to the current SQL user lacking the right permissions to access the console from within the database permissions.
ResolutionThere are several checks necessary to confirm what the root cause is. Normally, this is caused by SQL users, either created manually or added through the UI, not having the right permissions.
  1. First step is always to confirm the Server Authentication setting for the SQL Server instance is set to the right security posture:
    1. Open SQL Studio Management
    2. Right-click on the name on the name of the instance at the very top of the list and select Properties.
    3. Under the Server Properties window, click on Security
    4. Verify the Server Authentication setting is set to SQL Server and Windows Authentication mode
User-added image
  1. Retry logging in to the UI or using the connection setting under Configure>Connection> Test to verify if this worked. If not, continue to the next steps.
  2. Verify the username has security privileges enabled in the ECAT database. Go to the SQL studio management interface and open the ECAT database, default name is ECAT$PRIMARY
  3. Expand the database, then expand the Security folder. Expand the Users folder.
  4. Right-click on the user in question and select Properties
  5. In Database User window, select Membership. The following window will appear. Note that this is the minimum permission needed to at least access the UI, other users will have more options within the UI at higher levels:
User-added image
  1. Retest and the application should work now without errors. Normally it is not necessary to add sysadmin role if all the user is required to do is access the UI.

Attachments

    Outcomes