# Distribution Server Troubleshooting

This document outlines common issues related to the Distribution Server (DS), recommended self-healing steps, and support instructions for unresolved problems.

## Table of Contents

1. [Distribution Server Service Stopped](#distribution-server-service-stopped)
2. [Distribution Server Shutdown](#distribution-server-shutdown)
3. [Distribution Server Startup Failure — Port Unavailable](#distribution-server-startup-failure--port-unavailable)
4. [Distribution Server Replication Failure](#distribution-server-replication-failure)
5. [Distribution Server File Server Replication Failure](#distribution-server-file-server-replication-failure)

## Distribution Server Service Stopped

### Problem

The Distribution Server is not functioning as expected because the service was stopped during the replication process.

### Solution

Start the Distribution Server service on the affected machine.

Follow these steps to start the service:

1. Press `Win + R`, type `services.msc`, and press **Enter**.
2. In the **Services** window, locate the **Distribution Server** service.
3. Right-click on the service and select **Start**.
4. Ensure the **Startup Type** is set to **Automatic** to avoid similar issues in the future.

## Distribution Server Shutdown

### Problem

The Distribution Server is currently offline due to a system shutdown.

### Solution

Power on or restart the machine hosting the Distribution Server to resume operations.

## Distribution Server Startup Failure — Port Unavailable

### Problem

The Distribution Server component failed to start, because of the configured port is unavailable.

### Solution

1. Verify the port number in the Remote Office page. By modifying the settings in Remote Office, check if any other services are using the same port. If so, modify the Remote Office configuration to use a different, available port.  
   [![dsportnumber](https://cdn.manageengine.com/products/desktop-central/images/dsportnumber.png)](https://cdn.manageengine.com/products/desktop-central/images/dsportnumber.png)

2. **Open Windows Services:**
   - Press `Win + R` to open the **Run** dialog.
   - Type `services.msc` and press **Enter**.

3. **Check for Services Using the Same Port:**
   - Identify the port configured in the **Remote Office** settings (e.g., `8027`).
   - Open **Command Prompt** as Administrator.
   - Run the following command:

     ```
     netstat -aon | findstr :<port-number>
     ```

     Replace `<port-number>` with the actual port (e.g., `8027`).

4. **Find the Corresponding Service:**
   - Note the **PID** from the command output.
   - In `services.msc`, right-click a column header and enable the **PID** column if not already visible.
   - Match the PID to identify the service using the port.

5. **Resolve Port Conflict:**
   - If another service (e.g., **DS** or third-party app) uses the same port, go to the **Remote Office** page.
   - Modify the port number to an unused one.
   - Save the changes and restart the Remote Office service.

6. Verify the status of the Distribution Server service and attempt a restart.

If Problem Persists, please contact support and provide the following:

- **A. Nginx Configuration Files:**
  - `<Ds_dir>\dsnginx\conf`
  - `<Ds_dir>\replication\ds-data`
- **B. Logs:**
  - Latest DS logs for root cause analysis.

## Distribution Server Replication Failure

### Problem

The Distribution Server is not functioning properly due to replication issues.

### Solution

Check the current status of the DS service and restart it if required.

If Problem Persists, please contact support and provide the following:

- Latest DS logs from the affected machine
- For on-premises deployments: include relevant server logs

## Distribution Server File Server Replication Failure

### Problem

Web Server component is not functioning properly, which may be causing file server replication issues.

### Solution

1. Verify the status of the Distribution Server service and attempt a restart.
2. Check the Distribution Server's communication status using the troubleshooting tool available at:  
   `<DS_Installation_Directory>\ManageEngine\UEMS_DistributionServer\bin\ds_troubleshooting_tool.exe`

If Problem Persists, please contact support and provide the following:

- Latest DS logs
- For on-premises deployments: include relevant server logs