---
title: "Service Fails to Start"
slug: "xa-troubleshooting-audit-monitor-service-fails-to-start"
description: "This is a troubleshooting article that describes how to fix an issue when the Audit Monitor Service fails to start."
tags: ["5000", "FQDN", "Troubleshooting", "Fail", "How-To", "Healthcast", "Audit Monitor Service"]
updated: 2023-09-21T15:16:22Z
published: 2023-09-21T15:16:22Z
canonical: "healthcare.rapididentity.com/xa-troubleshooting-audit-monitor-service-fails-to-start"
---

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

# Service Fails to Start

## Audit Monitor Service Fails to Start

#### Problem

After installing Audit Monitor, the Audit Monitor service fails to start.

An error message is displayed when starting the service:

![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/audit-monitor-service-fails-to-start.doc-image-8ksxekso.png)

Services - The HCI SSO Audit Monitor Service services on the Local Computer that started and then stopped. Some services stop automatically if they are not in use by other services or programs.

The Audit Monitor logs located in “**C:\ProgramData\HealthCast\Audit Monitor\logs**” show an error similar to the one below:

2020-07-16 13:44:49.150 -05:00 [Information] Listening on prefix: https://+:5000/ 2020-07-16 13:44:49.150 -05:00 [Error] Start Microsoft.Net.Http.Server.WebListenerException (0x80004005): The process cannot access the file because it is being used by another process at Microsoft.Net.Http.Server.UrlGroup.RegisterPrefix(String uriPrefix, Int32 contextId) at Microsoft.Net.Http.Server.UrlPrefixCollection.RegisterAllPrefixes(UrlGroup urlGroup) at Microsoft.Net.Http.Server.WebListener.Start()

### POSSIBLE CAUSE 1: The default Audit Monitor port (5000) is being used by another program

To verify whether port 5000 is being used by another program:

1. Open a command window as a local administrator
2. Run the following command
  1. netstat -ab > “c:\netst.txt”
3. Open the generated file (netst.txt)
4. Search for “:5000”
  1. If you find a line that includes port 5000, another program is using that port  
![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/audit-monitor-service-fails-to-start.doc-image-rb6wbs5b.png)

### RESOLUTION 1: Configured Audit Monitor to use a port other than 5000

1. In this example, we will be configuring the Audit Monitor service to use port 6000
2. Verify that the port you are planning to use is not already in use
  1. Open a command window as a local administrator
  2. Run the following command
    1. netstat -ab > “c:\netst.txt”
  3. Open the generated file (netst.txt)
  4. Search for “:6000”
  5. If you do not find “:6000”, port 6000 should be safe to use
3. Open the firewall for the port, reserve the URL prefix, and assign an SSL certificate
  1. ***NOTE:*** *These steps assume you are updating a saved version of the modified SsoAuditMonitorSetup.ps1.*
    1. Run PowerShell ISE as a local administrator
    2. Open the **C:\Program Files (x86)\HealthCast\SSO Audit Monitor\Config\SsoAuditMonitorSetup.ps1** file
    3. Modify the Port value to 6000.  
![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/audit-monitor-service-fails-to-start.doc-image-rjqerd6v.png)
    4. Run the script
4. Update the SSO Audit Monitor JSON File to use port 6000
  1. Open the **C:\Program Files (x86)\HealthCast\SSO Audit Monitor\Config\appsettings.json** file in Notepad (or another text editor)
  2. Modify the “server.urls” setting so that it is using port 6000
  3. ![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/audit-monitor-service-fails-to-start.doc-image-1udh1k0j.png)
  4. Save the file.
5. Try starting the Audit Monitor service.
  1. Unless there are other configuration problems, the service should start and run without generating any errors  
![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/audit-monitor-service-fails-to-start.doc-image-3o6twz3x.png)

### POSSIBLE CAUSE 2: The configured certificate does not have the FQDN of the server

In order for Audit Monitor to work properly, there must be a server certificate installed that has the Fully Qualified Domain Name as the subject field (see [https://hc-admin.idauto.net/en/system-requirements-284247.html](https://hc-admin.idauto.net/en/system-requirements-284247.html)):

![](https://cdn.document360.io/f2567005-8048-43b2-8bfc-3abc2da42bca/Images/Documentation/audit-monitor-service-fails-to-start.doc-image-4s0v5oe4.png)

### RESOLUTION 2: Obtain a certificate that has the FQDN of the server as the Subject

1. Obtain a certificate that has the FQDN of the server as the Subject and configure Audit Monitor to use that certificate.

## Related

- [Reports that Include "In Month X" Do Not Go Higher than 2020](/xa-troubleshooting-audit-monitor-reports-higher-than-2020.md)