I logged into my exchange server a few days ago and launched the Exchange Management Shell (EMS). It immediately crashed after opening. I then tried to open a powershell prompt. It also immediately crashed. I then logged into a couple of other servers and workstations and tried launching powershell and found that the issue was common amongst most of the computers in our domain. Almost all computers had powershell crash immediately after it was opened. A handful of computers worked as expected with powershell remaining open after launch.
I use powershell to send email notifications from workstations and computers when certain Windows events are logged in the Event Viewer. I looked back at my notification history and found that most of the affect computers quit sending notifications as of 11/13/14. Because of this, I thought the issue may be related to the MS updates on 11/12/14 as there have been multiple reports of issues after installing these security updates.
Here's what I've tried so far on one of the servers that is experiencing the issue (without success):
- Uninstalled all updates since 10/31/14
- Ran SFC /scannow
- Ran ngen update for both 32 and 64 bit versions of .NET Framework 2.0
- Ran the .NET Repair Tool
All of the servers and workstations that are experiencing this issue are logging the following 2 errors in the event log every few seconds:
Error #1 (.NET)
Log Name: Application
Source: .NET Runtime
Date: 12/3/2014 9:27:55 AM
Event ID: 1023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HONEYDEW.mtefcu.org
Description:
.NET Runtime version 2.0.50727.5485 - CLR: Fatal Execution Engine Error (000007FEF84B600A) (80131506)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1023</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-12-03T14:27:55.000000000Z" />
<EventRecordID>5021127</EventRecordID>
<Channel>Application</Channel>
<Computer>HONEYDEW.mtefcu.org</Computer>
<Security />
</System>
<EventData>
<Data>.NET Runtime version 2.0.50727.5485 - CLR: Fatal Execution Engine Error (000007FEF84B600A) (80131506)</Data>
</EventData>
</Event>
Error #2 (PowerShell)
Log Name: Application
Source: Application Error
Date: 12/3/2014 9:27:53 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: HONEYDEW.mtefcu.org
Description:
Faulting application name: powershell.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc7f3
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
Exception code: 0xc0000005
Fault offset: 0x0000000000018e5d
Faulting process id: 0x3024
Faulting application start time: 0x01d00f0552aef630
Faulting application path: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9083f894-7af8-11e4-a74f-000c29db4eea
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-12-03T14:27:53.000000000Z" />
<EventRecordID>5021126</EventRecordID>
<Channel>Application</Channel>
<Computer>HONEYDEW.mtefcu.org</Computer>
<Security />
</System>
<EventData>
<Data>powershell.exe</Data>
<Data>6.1.7600.16385</Data>
<Data>4a5bc7f3</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.18247</Data>
<Data>521eaf24</Data>
<Data>c0000005</Data>
<Data>0000000000018e5d</Data>
<Data>3024</Data>
<Data>01d00f0552aef630</Data>
<Data>C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>9083f894-7af8-11e4-a74f-000c29db4eea</Data>
</EventData>
</Event>