Troubleshooting
Errors
If you experience errors, verify that:
You can connect to SQL Server using the login that you created.
You can verify the connection using the SQL Server Command Line Tool.
If the login uses SQL Server authentication:
sqlcmd.exe -S <server name>\<instance> -U <login ID> -P <password>
If the login uses Windows authentication, and the current Windows user is the same as the SQL Server login:
sqlcmd.exe -S <server name>\<instance>
Your system meets the recommended installation requirements.
For example, 1 GB RAM is recommended (512 MB is the minimum) for Microsoft SQL Server.
If you continue to experience errors with Microsoft SQL Server :
Ensure that the server is set up to allow remote connections.
If you are connecting to a named instance, try specifying the TCP port number along with the server and instance name: < servername > \ < instance >, < port >.
For example, using sqlcmd.exe:
sqlcmd.exe -S sqlserver\mycorp2,1433 -U sa -P letmein!
If you continue to experience errors with Microsoft SQL Server , try the following:
Start the SQL Server Configuration Manager (Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools)
Select SQL Server Network Configuration > Protocols for < SQLServer instance > and enable Shared Memory, TCP/IP, and Named Pipes protocols.
Select SQL Native Client Configuration > Client Protocols and enable protocols with the following order:
Shared Memory 1
TCP/IP 2
Named Pipes 3
Restart the server to apply your settings.
User mapping
Check if user mapping is correct and places the DBUser login in the context of the application database. In SSMS or sqlcmd execute:
select count(1) from sesslog_full;
You need to fix user mapping if you get "no such table" or zero rows. For example in SSMS:
Click Server > Security > Logins.
Right-click the DBUser then select Properties> User mapping.
Ensure that the correct Login is mapped to the database schema and user, and has correct privileges granted, as in Step 6.
Verify or update current backend database connection settings
Use the iddbadm utility to verify or update current backend database connection settings.
You can see and change the details of the application connection to its database, in the Windows registry (HKLM\SOFTWARE\Bravura Security\Bravura Security Fabric\<instance>\MSSQL)
Any change to that key's values can be made directly, other than the password, which is encrypted and requires running iddbadm to be changed (showconfig will not expose its plaintext value).
Services
Under certain circumstances, Bravura Security Fabric services may fail to start after a server reboot. This problem may occur if the database is unavailable, or the database services and/or other dependent services have not started completely when the Bravura Security Fabric services attempt to start. There are two methods for resolving this problem.
Method 1: Manually start the services
If Bravura Security Fabric services fail to start, you can manually start all required services. To do this:
Before you begin, ensure the database is available.
Log on to the affected server.
On the Start menu, click Run , type
services.msc, Click OK.In the results pane, find the Bravura Security Logging Service.
Right-click the service, then select Restart.
In the results pane, find the Bravura Security Database Service .
Right-click the Service, then select Start.
Repeat steps 6 and 7 for all Bravura Security services that did not start.
Method 2: Set Bravura Security Fabric services to Automatic (Delayed Start)
To ensure that the database and all required services have started completely before the Bravura Security Fabric services have started, you can set them to Automatic (Delayed Start). To do this:
Log on to the affected server.
On the Start menu, click Run, type
services.msc, Click OK.In the results pane, find the Bravura Security services.
Right-click the service, then select Properties….
Change the Startup Type to Automatic (Delayed Start).
Click Apply , then click OK.
Repeat steps 4-6 for all Bravura Security services that are installed.
Restart the server.