VigilEnt Security Manager 4.x
Data access errors occur when attempting to log into VigilEnt Security Manager from a remote GUI.
Error Code 3149: A data access error occurred.
Error: ' [Microsoft] [ODBC SQL Server Driver] [SQL Server] [Login failed for user '(null)'. Reason: Not associated with a trusted SQL server connection'
Error is as follows:
A data access error occurred (Error code 3149).
Error Source: Microsoft OLE DB Provider for ODBC Drivers
Error information: [Microsoft] [ODBC SQL Server Driver] [SQL Server] [Login failed for user '(null)'. Reason: Not associated with a trusted SQL server connection.
This occurs when the remote machine is located in a separate domain than the VigilEnt Security Manager Server ( VSM ). This error can occur despite the fact that there is a trust established between the two domains.
To resolve the above error message, three items need to be implemented. Please follow the steps below to enable SQL authentication within your environment.
Enable SQL Authentication on the VSM server:
- Click Start | Programs | Vigilent | Vigilent Security Server to launch the Configuration Utility on the VSM server.
- Select the Database tab.
- Change the Enable SQL Authentication setting to True.
- Click Apply.
- Restart the Vigilent Security Server service on the VSM server for the change to take effect. Please reference the following link if needing assistance on restarting the service: NETIQKB25651
Confirm that SQL authentication is enabled, in mixed mode, on the SQL server where the VigilEnt database is located.
- Launch the 'SQL Enterprise Manager' from the SQL server.
- Right-click the SQL server located under the 'SQL Server Group' node and select Properties.
- Click the Security tab.
- Under Authentication, verify that it is set to SQL Server and Windows.
Enable SQL Authentication on the client side GUI.
- Launch the VSM GUI.
- Click Configure from the logon box.
- Select the Enable SQL Authentication checkbox and click OK.
- Logon to VSM.