Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "Http 500" error message when you use Exchange Troubleshooting Assistant on an Exchange Server 2007 Client Access server to diagnose issues

"Http 500" error message when you use Exchange Troubleshooting Assistant on an Exchange Server 2007 Client Access server to diagnose issues

View products that this article applies to.

Symptoms

You can use Microsoft Exchange Troubleshooting Assistant on a Microsoft Exchange Server 2007 server to diagnose issues. If you enable the AllResponses trace tag of the MSExchangeWebServices component and then configure the mailbox trace filtering option for one or more mailboxes, this tracing encounters an exception in the w3wp.exe process. Additionally, you find that the IIS trace log on the Exchange Server 2007 Client Access server includes the following error message:
<IIS_Log_filename>:<number>:<date_time> W3SVC1 <ip-address> POST /ews/Exchange.asmx SoapAction=xxxxxxxxxx xxx x xxxx 500 0 0

This problem always occurs when you troubleshoot an Exchange Web Services (EWS) application. In this situation, the EWS application might also throw an exception with the following call stack information:

Encountered unhandled exception: System.Web.Services.Protocols.SoapException: Server was unable to process request. System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Exchange.Services.ServiceExtensionManager.TraceMessage(Stream stream, Trace tracer)
at Microsoft.Exchange.Services.ResponseLogger.AfterSerializeResponse(SoapMessage message)
at Microsoft.Exchange.Services.ServiceExtensionManager.DoAfterSerializeResponse(SoapMessage message)
at Microsoft.Exchange.Services.ServiceExtensionManager.<>c__DisplayClass1.<ProcessMessage>b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
at Microsoft.Exchange.Diagnostics.ExWatson.SendReportOnUnhandledException(MethodDelegate methodDelegate, IsExceptionInteresting exceptionInteresting, Boolean terminating)
at Microsoft.Exchange.Services.Core.ServiceDiagnostics.TraceErrorOnUnhandledException(MethodDelegate methodDelegate)
at System.Web.Services.Protocols.SoapMessage.RunExtensions(SoapExtension[] extensions, Boolean throwOnException)

↑ Back to the top

Resolution

To resolve this problem, install the following update rollup:
2279665� Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: KB983540, kbexpertiseinter, kbhotfixrollup, kbsurveynew, kbqfe, kbfix

↑ Back to the top

Article Info
Article ID : 983540
Revision : 2
Created on : 9/9/2010
Published on : 9/9/2010
Exists online : False
Views : 458