Meanwhile, event ID 4999 for MSExchangeRepl.exe are recorded in the Application log multiple times until the restarted node has completely restarted. While this is occurring, Windows clients may be disconnected. To fix this problem, install Cumulative Update 15 for Exchange Server 2013 or a later cumulative update for Exchange Server 2013.

Windows 7 or Windows Vista. Step 1: Open User Accounts. Click Start , type Control nusrmgr.cpl in the Start Search box, and then press ENTER. Click User Accounts. If you are prompted for an administrator password or for a confirmation, type the password, or provide confirmation. Step 2: Add a new user.

On a computer that is running Windows 7 or Windows Server 2008 R2, the conhost.exe process crashes when an application exits. When the issue occurs, the computer might stop responding. Note The following steps describe the process that leads to the crash: A grandparent process has console handles.

Resolution. To fix this issue, install the April 4, 2017, update (KB3178717) for Microsoft Skype for Business 2016. Fixes an issue in which Skype for Business 2016 can’t be started.

Exit Outlook. Press the Windows logo key + R to open a Run dialog box. Enter Outlook /safe, choose a profile if prompted, and then select OK. If Outlook doesn't crash or hang, continue by selecting File > Options > Add-Ins. At the bottom of the window, select COM Add-ins and then select Go.

After several days, the WMI Provider Host program (Wmiprvse.exe) may crash. After the issue occurs, you can just ignore the report about the crash in the WMI host program because the process will restart with the next request by itself. However, this issue may affect other WMI queries running against the system at the same time that the crash ...

Faulting application path: C:\Windows\system32\lsass.exe Faulting module path: C:\Windows\system32\kerberos.DLL Report Id: 168aa2f9-95d6-11e4-80ec-a0369f05235a Faulting package full name: Faulting package-relative application ID: Event ID 5000: The security package Kerberos generated an exception. The exception information is the data.

When an MSDTC transaction runs on a computer that is running Windows 7 or Windows Server 2008 R2, the Distributed Transaction Coordinator service (Msdtc.exe) may crash if slow network performance occurs. Additionally, the following events are logged: Cause. This issue occurs because MSDTC logs a warning.

On a computer that is running Windows Server 2008 R2 or Windows 7, the Svchost.exe process that hosts Windows Management Instrumentation (WMI) service may crash. Additionally, an event entry that includes the following message is added to the Application log: Also, the following other services that run in the same Svchost.exe process also fail:

When you send a meeting invite that includes a Loop component, Outlook crashes when you click Send. This issue happens after updating to Version 2307 Build 16626.20170. In the Application Event Log the crash event will match the specifics below: Faulting application name: OUTLOOK.EXE, version: 16.0.16626.20170, time stamp: 0x64cc6089.