Connection to SQL Server Database failed: TS-DB001 KB - OpenLM Software License Management
Israel +972 4 6308447         USA +1 619 831 0029              JAPAN +81 505 893 6263 担当:萩原

Connection to SQL Server Database failed: TS-DB001 KB

You are here:
< All Topics


Customer reported failure to connect to the SQL Server. The “Check” button worked in the “OpenLM Database Configuration” dialog box but EasyAdmin couldn’t connect to the SQL Server.



1. The customer defined the OpenLM Server (in the “OpenLM Database Configuration” dialog box) to work with SQL server using “Windows Authentication”. This means that logging to the SQL Server was done using Windows credentials.
2. The customer clicked “Check” on the “OpenLM Database Configuration” dialog box, and it worked because the process worked fine with the provided Windows credentials.
3. Then he started the OpenLM Server. It didn’t work because it had other credentials.

The customer sent a log containing these lines:

FATAL 2011-09-26 12:11:14,276 [thread 11]  SessionProducer CreateFactory - Can't map nhibernate domains
System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'DPI\ORANTESTSPATIAL$'.

This means that a user named DPI (on server ORANTESTSPATIAL) could not login to the SQL Server, hence the system halts (FATAL error means that the application could not recover).


1. The “Database credentials” dialog box may be configured the wrong way, e.g.: check the “Embedded” check box in the window for Databases that are located on local drives.

2. OpenLM Service credentials: In the “Windows Services” window, select the “OpenLM Server” item. The “OpenLM Server Properties” dialog window opens. Select the “Log On” tab.

Log On tab on the Services window for OpenLM Server

Here you can see under what credentials the service runs. By default it is configured to log on as “Local System Account” but some users change it.

We suggest doing one of the following:

1. Change the OpenLM Service credentials to that of a user who has both administrative permissions and permission to login to the SQL server.

2. Another option is to use “SQL Server Authentication” instead of “Windows Authentication” when using the OpenLM Server DB Configuration Tool.

Title #02.001 Connection to SQL Server DB failed.
Category Data Base
Date Sep 26, 2011
Handled by Rachel.
Relevant Links (link to mantis item, docs, customer correspondence etc.)
Applies to license managers FLEXlm, FLEXera FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer reported failure to connect to a new SQL Server through EasyAdmin. Succeeded in connecting it via the Configuration form “Check” button. Customer succeeded in connecting to old FB Server through EasyAdmin.
Observed during investigation Log contained fatal error:
Login failed for user ‘DPI\ORANTESTSPATIAL$’
Trouble shoot process Credentials issue
Solution Found (Options: Found/Pending/Known Issue)
Previous Connection to FlexLM license server failed: TS-OLMSRV002 KB
Next DB has reached a critical size: TS-DB004 KB
Table of Contents