---
title: "Troubleshooting Multi-Tenant Environments"
slug: "troubleshooting-multi-tenant-environments"
updated: 2025-06-06T13:38:43Z
published: 2025-06-06T13:38:43Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Multi-Tenant Environments

## Overview

The following document provides information about potential issues that may occur during the installation/use of a [**Multi-Tenant**](https://documentation.decisions.com/v9/docs/about-multi-tenancy) environment. This information is subject to changes based on new [**Minor Releases**](https://documentation.decisions.com/v99/docs/release-process-overview).

---

## If the Control Instance Does Not Start

If the Control Instance's Decisions Server does not start after applying a checkpoint, proceed through the following troubleshooting methods.

### If the Error Stems From Lack of Socket Access Permission

- From **DecisionsServerInstaller.exe** or [**Settings.xml**](https://documentation.decisions.com/v9/docs/system-settings-overview-settings-xml), change the **ServerType**from **Hosted**to **Unmanaged** and back to Hosted.
- Ensure that the Decisions Server is restarted each time the ServerType is changed.

### [If the Server is Self Hosted](https://documentation.decisions.com/v9/docs/installation-guide#self-hosting-)

- Verify that IIS is turned off.
- Note that IIS starts automatically after reapplying at a checkpoint.

### If one of the Instances was Recently Updated

- Verify that the [**Control**](https://documentation.decisions.com/v9/docs/multi-tenancy-setting-up-a-control-instance)****and [**Tenant Instances**](https://documentation.decisions.com/v9/docs/multi-tenancy-adding-and-setting-up-a-tenant-instance)****are the same version.
- If the versions are incompatible, the previously created **Account** will not be able to log in.