MS11-028 may cause issues with SQL, Exchange and PowerShell
Published Jan 15 2019 01:48 PM 191 Views
First published on MSDN on Apr 21, 2011

A .NET Security Update (MS11-028) may end up causing issues with applications that make use of the .NET Framework, mostly resulting in applications being unable to launch, or loss of functionality within Native Applications that make use of .NET. In some cases, it could lead to an application crash. For this issue to occur, the updates have to be laid down in a specific order.

For this issue to occur, KB 979744 would have had to be installed prior to 2449742 or 2446709 (part of security bulletin MS11-028).  NOTE: 979744 is a prerequisite for Exchange 2010 SP1.

You may experience the following:

· Reporting Services service fails to start.

· SQL Server Profiler tool cannot be launched on the server machine.

· SQL Server Management Studio cannot be launched on the server machine.

· Database Mail and CLR functions may be broken.

· Event Viewer cannot be launched on the server machine.

· PowerShell cannot be started.

This issue only affects the following Operating Systems:

Vista SP2
Windows 2008 SP2
Win 7 RTM
Windows 2008 R2

Win7 SP1 and Windows 2008 R2 SP1 are NOT affected!

We have since reissued KB 979744 to avoid the problem.  The Exchange team has posted a blog about this as well here .

KB 2540222 describes how you can detect if you have the original version of KB 979744 installed and offers steps to correct the issue.

EDIT (4/25/11):

From an RS Perspective, we saw the following from a startup crash.  In the RS Log we had the following:

rshost!rshost!fd0!04/19/2011-11:42:38:: e ERROR: Generating a dump and exiting the process due to fatal runtime error.

In the Event Log we saw the following:

Windows could not start the SQL Server Reporting Services (MSSQLSERVER) service on Local Computer.
Error 1067: The process terminated unexpectedly.

Unfortunately, this doesn’t tell us much outside of the fact that RS Crashed from a .NET issue.  In this case, having just the info above, I would guess an Access Violation (AV).  Because you see the messages above, doesn’t mean you hit this issue though.  You would still need to validate the versions of the binaries in place to see where you sit.

Adam W. Saxton | Microsoft SQL Server Escalation Services

Version history
Last update:
‎Jan 15 2019 01:48 PM
Updated by: