For the Data Access service: Microsoft.Mom.Sdk.ServiceHost.exe.config. For the Management Configuration service: Microsoft.Mom.ConfigServiceHost.exe.config (in Service Manager) orcshost.exe.config (in Operations Manager) To disable CRL checking, add the following line in the <runtime> section:

Symptoms. The Microsoft Exchange Service Host service (Microsoft.Exchange.ServiceHost.exe) on a computer that is running Microsoft Exchange Server 2013 crashes after you enable United States Federal Information Processing Standard (FIPS) compliant algorithms for encryption, hashing, and signing.

Symptoms. After you install the Microsoft Exchange Server March 2022 security update, the Exchange Service Host service (MSExchangeServiceHost) fails repeatedly and logs Event ID 7031 in the system log and Event ID 4999 in the application log:

Launch the Xbox app for PC. Click your Profile picture. Click on Support. Click on Gaming Services Repair Tool. Click on Start Troubleshooting.

The Microsoft Exchange Service Host service (Microsoft.Exchange.ServiceHost.exe) on a Microsoft Exchange Server 2010 server crashes intermittently. Additionally, the following event is logged in the Application log: Cause.

Symptoms. The Microsoft Exchange Service Host service (Microsoft.Exchange.ServiceHost.exe) on a computer that is running Microsoft Exchange Server 2013 crashes after you enable United States Federal Information Processing Standard (FIPS) compliant algorithms for encryption, hashing, and signing.

Resolution. We recommend that you set the latencyThresholdInMSec element to 8000 and the minCongestionWindowSize element to 64. To do this, update or add the following elements under the <microsoft.identityServer.proxy> section in the Microsoft.IdentityServer.Servicehost.exe.config file:<congestionControl latencyThresholdInMSec="8000 ...

The Monitoringhost.exe process may consume all the CPU resources when a large amount of performance data is created by using a managed data source module in System Center Operations Manager 2007 - Microsoft Support. Symptoms. Consider the following scenario:

Svchost.exe process that hosts a Group Policy client service crashes on a Windows 8 or Windows Server 2012-based computer - Microsoft Support. Windows 8 Windows Server 2012 Standard More... Symptoms. Consider the following scenario: Direct Access is configured on a computer that is running Windows 8 or Windows Server 2012.

When you are using a computer that is running Windows 7 or Windows Server 2008 R2, the Svchost.exe process that hosts the network location awareness service crashes intermittently. Cause. This issue occurs because a handle leak occurs in the Wldap32.dll file. Resolution. This hotfix is also available at Microsoft Update Catalog. Hotfix information.