Event ID 3, Event ID 1309 and Event ID 108 are logged on an Exchange Server 2010 Client Access server

Article translations Article translations
Article ID: 2249852 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You use Outlook Web App (OWA) to log on to a Microsoft Exchange Server 2010 mailbox.
  • You try to perform one of the following operations:
    • Delete an email message.
    • Mark an email message as read or unread.
    • Right-click a folder, and then click Empty Folder.
    • Upload an attachment.
In this scenario, you may receive one of the following error messages:
  • Error message 1:

    An unexpected error occurred and your request couldn't be handled.
  • Error message 2:

    The action you tried to perform couldn't be completed because there's a configuration problem on the server. If the problem continues, contact your helpdesk.
Additionally, the following events are logged in the Application log on the Client Access server:

Log Name: Application
Source: System.ServiceModel 3.0.0.0
Event ID: 3
Task Category: WebHost
Level: Error
Keywords: Classic
User: SYSTEM
Description:
WebHost failed to process a request.
Sender Information: System.ServiceModel.Activation.HostedHttpRequestAsyncResult/63835064
Exception: System.UriFormatException: The protocol binding '[::1]:80:' does not conform to the syntax for 'http'. The following is an example of valid 'http' protocol bindings: ':80:'.
at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result)
Process Name: w3wp
Process ID: <process id>


Log Name: Application
Source: ASP.NET 2.0.50727.0
Event ID: 1309
Task Category: Web Event
Level: Warning
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: <date & time>
Event time (UTC): <date & time>
Event ID: b6b2b454c918491fa3eabb8f681e0ce0
Event sequence: <xx>
Event occurrence: <xx>
Event detail code: <xx>

Application information:
Application domain: /LM/W3SVC/1/ROOT/EWS-1-129210142826415583
Trust level: Full
Application Virtual Path: /EWS
Application Path: <drive>:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\
Machine name: <machine name>

Process information:
Process ID: <process id>
Process name: w3wp.exe
Account name: <account name>

Exception information:
Exception type: UriFormatException
Exception message: The protocol binding '[::1]:80:' does not conform to the syntax for 'http'. The following is an example of valid 'http' protocol bindings: ':80:'.

Request information:
Request URL: https://127.0.0.1:443/ews/exchange.asmx
Request path: /ews/exchange.asmx
User host address: 127.0.0.1
User: <user>
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\SYSTEM

Thread information:
Thread ID: 3
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False

Stack trace: at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result)
at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)


Log Name: Application
Source: MSExchange OWA
Event ID: 108
Task Category: Configuration
Level: Error
Description:
Outlook Web App couldn't connect Exchange Web Services due to a configuration error. Response code = "500".

CAUSE

The issue occurs when the Internet Information Services (IIS) website that hosts the Exchange Web Services (EWS) virtual directory contains a site binding that binds to an IPv6 address.

Note
 It is a known issue that this configuration may cause an exception .

RESOLUTION

To resolve this issue, install the hotfix that is described in Knowledge Base (KB) article 981667. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981667 FIX: An exception occurs when a WCF client sends a request to a .NET Framework 3.5-based WCF service that uses an IPv6 address for the binding

STATUS

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

MORE INFORMATION

For more information about EWS, visit the following Microsoft website:
General information about EWS

Properties

Article ID: 2249852 - Last Review: December 28, 2010 - Revision: 1.0
APPLIES TO
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseinter KB2249852

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com