> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/help-and-support/support-articles/kb000013.md).

# KB000013: Access Manager cannot be installed on Windows Server 2016 with TLS 1.0 disabled

## Summary

If you try to install the Access Manager Service on Windows Server 2016, when policies have been applied to harden TLS and remove support for TLS 1.0 and 1.1, AMS will fail to install.

## Cause

The built-in SQL driver in Windows Server 2016. used by the installer, is unable to use TLS 1.1 or TLS 1.2. This causes the installer to fail as it cannot connect to the database.

This impacts only the installer itself. AMS will operate correctly with only TLS 1.2 enabled.

This issue does not impact Windows Server 2019 or later.

## Resolution

The only workaround available at this stage is to temporary enable TLS 1.0 and TLS 1.1 on the server, perform the installation or upgrade, and then disable TLS 1.0 and 1.1 again.

Note that to install future upgrades, the same process will need to be repeated.


---

# 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.lithnet.io/ams/help-and-support/support-articles/kb000013.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.