MS07-040 Issues

  • Article

We have seen a number of issues in regards to the security update MS07-040 This is not meant to be an inclusive list of issues, but these are some of the problems we have seen and what the resolution was for each.

Problem 1

Getting an exception after updating to MS07-040 when using SSL (TLS)

 Unhandled Exception: System.Net.WebException: The underlying
connection was closed: Could not establish secure channel for
 SSL/TLS. ---> System.ComponentModel. 
Win32Exception: The message received was unexpected or
 badly formatted 
--- End of inner exception stack trace --- 
at System.Net.HttpWebRequest.CheckFinalStatus() 
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) 
at System.Net.HttpWebRequest.GetResponse()

Root Cause:

The reason for the client to have worked all the while before applying the security update, was because by default, the .Net 1.1 framework only supported the SSL v3 protocol. The TLS protocol is disabled in the .Net 1.1 framework. After applying the above patch, the .Net framework 1.1, enabled the TLS protocol and since it is the latest SSL protocol specification, you suddenly faced the above error.

The error you faced was because the SSL Accelerator card was only configured to handle SSLv3 traffic. You needed to explicitly enable the TLS specification on the Accelerator card to make it compatible with the Client request.

Resolution:

Enable the TLS specification on the accelerator card to make it compatible with the TLS Client. If this is not done, the card responds back with a Fatal Error indicating that it cannot understand the TLS protocol.

Problem 2

Getting unprintable characters in client-side script after installing the patch

Resolution:

https://support.microsoft.com/default.aspx?scid=kb;EN-US;940521

Problem 3

Getting the following event log from perfmon:

 Event Type: Error
Event Source: Perflib
Event Category: None
Event ID: 1008
Date:  7/11/2007
Time:  1:03:15 PM
User:  N/A
Computer: NJPSUS0002
Description:
The Open Procedure for service "ASP.NET" in DLL "
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_perf.dll" 
failed.  Performance data for this service will not be 
available. Status code returned is data DWORD 0. 
Data:
0000: 05 40 00 80

Resolution:

https://support.microsoft.com/default.aspx?scid=kb;EN-US;944746

Problem 4

Receive the following error on Windows 2000 SP4 after installing:

 Error 127: the specified procedure could not be found.

Resolution:

https://support.microsoft.com/default.aspx?scid=kb;EN-US;816542

Problem 5

Receive 500 errors with the following event in the event log:

 Event Type:     Warning
Event Source:   ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID:       1309
Date:           12/07/2007
Time:           10:24:38
User:           N/A
Computer:       VSTest
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 12/07/2007 10:24:38
Event time (UTC): 12/07/2007 8:24:38
Event ID: aa58f4d35bc547aeafd7c417967bdd8d
Event sequence: 8 Event occurrence: 1 Event detail code: 0

Application information:
    Application domain: /LM/W3SVC/1/Root/Test-1-128287022723281250
    Trust level: Full
    Application Virtual Path: /Test
    Application Path: C:\Inetput\Test
    Machine name: VSTest

Process information:
    Process ID: 412
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
    Exception type: EndPointException
    Exception message: An error occured in the IIS HTTP handler. 
 The error is: Type 'System.Web.HttpHeaderCollection' in Assembly 
'System.Web, Version=2.0.0.0, Culture=neutral, 
PublicKeyToken=b03f5f7f11d50a3a' is not marked as serializable.

Resolution:

https://support.microsoft.com/default.aspx?scid=kb;EN-US;941386

Problem 6

When you use the <any ... /> tag to extend a WSDL with complex types, after installing this patch the WSDL is no longer parsed correctly.

Resolution:

https://support.microsoft.com/default.aspx?scid=kb;EN-US;940959

Problem 7

Receive a System.NullReferenceException from System.Web.SessionState.SessionStateModule.PollLockedSessionCallback:

 Event Id : 5000:
EventType clr20r3, P1 aspnet_wp.exe, P2 2.0.50727.832, P3 461ef1db,
 P4 system.web, P5 2.0.0.0, P6 461ef1d2, P7 297c, P8 8d, P9 system.nullreferenceexception, P10 NIL. 
Event id: 1000
aspnet_wp.exe (PID: 5240) stopped unexpectedly.

System.NullReferenceException
Object reference not set to an instance of an object

at System.Web.SessionState.SessionStateModule.PollLockedSessionCallback(Object state)
at System.Threading._TimerCallback.TimerCallback_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._TimerCallback.PerformTimerCallback(Object state).

Resolution:

https://support.microsoft.com/default.aspx?scid=kb;EN-US;942086

Problem 8

When you try to serialize an ObjRef object in an application that is built on the Microsoft .NET Framework 1.1 between the client computer and the server computer, you may receive the following exception error message:

 System.Runtime.Serialization.SerializationException: Type missing
for member of type Object '_ContextID'.

Resolution:

https://support.microsoft.com/default.aspx?scid=kb;EN-US;944925