A 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 the 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 'DPIORANTESTSPATIAL$'.
This means that a user named DPI (on server ORANTESTSPATIAL) could not log in 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.
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 log in 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.