> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/unable-to-connect-to-the-workspace.md).

# Unable to connect to the workspace

Fix the SQL Server pre-login handshake error in Remote Desktop Manager by trusting the self-signed certificate or adding it to your store.

When trying to connect to a Microsoft SQL Server workspace in Remote Desktop Manager, you may encounter this error message:

`A connection was successfully established with the server, but then an error occurred during the pre-login handshake.`

Chances are your SQL Server is configured with a self-signed certificate that you do not have in your certificate store.

### Solution

Either add the certificate to your store or configure Remote Desktop Manager to trust the certificate. Follow the steps below for the Remote Desktop Manager configuration:

1. Select your workspace in the ***navigation pane***.
2. Go to ***File – Workspaces***, then click on ***Edit workspace***.
3. In the ***Advanced*** tab, click on ***More Settings***.
4. Scroll down to the ***TrustServerCertificate*** setting and set its ***Value*** to "true".
5. Click ***OK*** in all the windows to save your changes, then try to connect again.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/unable-to-connect-to-the-workspace.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.