---
title: "XA Server Stops Responding to Client Requests"
slug: "xa-server-stops-responding-to-client-requests"
description: "In some older versions of the XA server (4.1.3 and older), the XA Credential Provider enabled on XA Server can eat up memory over time, causing errors upon client requests. This troubleshooting article addresses how to resolve this issue."
updated: 2022-06-02T15:56:15Z
published: 2022-06-02T15:56:15Z
canonical: "healthcare.rapididentity.com/xa-server-stops-responding-to-client-requests"
---

> ## 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.

# XA Server Stops Responding to Client Requests

## XA Server Stops Responding to Client Requests

### PROBLEM/NEED

The XA Server service stops responding to client requests.

### POSSIBLE CAUSE 1: The XA Credential Provider is eating up memory on the server

In some older versions of the XA server (4.1.3 and older), having the XA Credential Provider enabled on the XA server eats up memory over time (each time a user authenticates using remote authentication). In this case, you may see errors similar to the ones below:

**Faulting application name:** svchost.exe_Schedule, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1

**Faulting module name:** eXactaccessCredentialManager.dll, version: 4.5.0.860, time stamp: 0x00000000

**Exception code:** 0xc0000005

**Fault offset:** 0x0000000000032480

**Faulting process id:** 0x1310

**Faulting application start time:** 0x01ce8eb2d87e43b0

**Faulting application path:** C:\Windows\system32\svchost.exe

**Faulting module path:** C:\Program Files (x86)\HealthCast\eXactACCESS\bin\eXactaccessCredentialManager.dll

**Report Id:** 5813990f-fae6-11e2-a9e6-68b599cac784

### RESOLUTION 1:

1. Disable the XA Credential Manager on the XA Server.  
***NOTE:*** *Removing the credential provider removes the ability for Connectors to make use of the user's AD username and password, but **ONLY ON THE XA SERVER**, where it should never be needed.*

#### STEPS FOR DISABLING THE XA CREDENTIAL PROVIDER ON AN XA SERVER

1. Open **Regedit.**
2. Browse to **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order]**
  1. Remove **eXactACCESSCredentialManager** (and comma) from the **ProviderOrder** setting
    1. Before
      1. **ProviderOrder**="SnacNp,RDPNP,LanmanWorkstation,eXactACCESSCredentialManager"
    2. After
      1. **ProviderOrder**="SnacNp,RDPNP,LanmanWorkstation"
3. Browse to **HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder]**
  1. Remove eXactACCESSCredentialManager from the **ProviderOrder** setting
    1. Before
      1. **ProviderOrder**="SnacNp,RDPNP,LanmanWorkstation,eXactACCESSCredentialManager"
    2. After
      1. **ProviderOrder**="SnacNp,RDPNP,LanmanWorkstation"