> For the complete documentation index, see [llms.txt](https://docs.soraco.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soraco.co/docs/qlm-license-server/troubleshooting-tips-for-sql-error.md).

# Troubleshooting tips for SQL Error

### Authentication Mode

Verify that SQL Server is configured for "SQL Server and Windows authentication mode". This is done by viewing the properties at the SQL Server level and selecting the Security Node.

 

![mceclip0.png](https://support.soraco.co/hc/article_attachments/360045602451/mceclip0.png)

### Security

1\. Verify that the user configured to access your database as specified in the web.config is configured at 2 levels:

* At the SQL Server / Security / Logins level
* At the Database / Security / Users level

![mceclip1.png](https://support.soraco.co/hc/article_attachments/360045602491/mceclip1.png)

 

![mceclip2.png](https://support.soraco.co/hc/article_attachments/360045483372/mceclip2.png)

 

2\. Verify that the user at the Database level has the appropriate privileges. To do so:

* Start SQL Server Management Studio
* Locate your Database and expand the node
* Locate the Security node and expand it
* Locate the Users node and expand it
* To create a new user (skip this step if the qlmuser is already created): 
  * Right mouse click and select New User
  * Set the user name to: qlmuser
  * Set the Login name to: qlmuser
* Set the following Membership: db\_datareader, db\_datawriter, db\_ddladmin

3\. Verify the credentials in the web.config file

* Locate the license server web.config file, typically located in c:\inetpub\wwwrooot\Qlm\QlmLicenseServer
* Edit the web.config file with a text editor such as notepad
* Locate the connectionstrings section
* Verify that the Data Source setting points to your DB server
* Verify that the name of the database is correct
* Verify that the User/Pwd values to connect to the DB are correct

4\. If you are upgrading from QLM v7 or older to QLM v15 or later, some tables need to be created prior to the upgrade (ServerProperties). Please contact our support team for assistance.

###  

###  SSL / TLS 

If you get the error: \[DBNETLIB]\[ConnectionOpen (SECCreateCredentials()).]SSL Security error, this means that you are using an older version of the OLE  DB Driver for SQL which does not support TLS 1.2. You must :

1\. Install the latest Microsoft OLE DB Driver 18 for SQL Server from: \
<https://www.microsoft.com/en-us/download/details.aspx?id=56730>\
\
2\. Update the connectionStrings in the web.config as shown below (change the values of Server, Database, User and Password as needed)\
\
\<connectionStrings>\
&#x20; \<add name="QlmWebService.Properties.Settings.qlmConnectionString"\
&#x20;     connectionString="Provider=msoledbsql;Server=localhost;Database=qlmdemo;User Id=qlmdemo;Password=qlmweb30;"\
&#x20; />\
&#x20; \<add name="QlmSvcLib.Properties.Settings.qlmConnectionString"\
&#x20;   connectionString="Provider=msoledbsql;Server=localhost;Database=qlmdemo;User Id=qlmdemo;Password=qlmweb30;"\
&#x20;   />\
&#x20; \<add name="aspConnectionString" connectionString="Data Source=localhost;Initial Catalog=qlmdemo;User Id=qlmdemo;Password=qlmweb30;"\
&#x20;   providerName="System.Data.SqlClient" />\
&#x20;\</connectionStrings>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.soraco.co/docs/qlm-license-server/troubleshooting-tips-for-sql-error.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.