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 status 404” error when you access free-busy information for mailboxes on a recently recovered Exchange Server 2013 Mailbox server

"HTTP status 404” error when you access free-busy information for mailboxes on a recently recovered Exchange Server 2013 Mailbox server

View products that this article applies to.

Symptoms

Mailboxes on a recently recovered multirole (Client Access and Mailbox) server that is running Microsoft Exchange Server 2013 cannot access the free/busy service.

When this problem occurs, the following errors are logged.

Outlook logs (Outlook.etl files):

Recipient: user@contoso.com
Exception: Proxy web request failed. , inner exception: The request failed with HTTP status 404: Not Found.
Server Name: < problematic server>
Exception Type: ProxyWebRequestProcessingException
Response Code: ErrorProxyRequestProcessingFailed

IIS Logs on the problematic server:

POST /ews/exchange.asmx - 443 – <Client-IP> ExchangeInternalEwsClient-AuditLog - 404 0 0 15
POST /ews/exchange.asmx - 443 - <Client-IP> ExchangeInternalEwsClient-AuditLog - 404 0 0 15
POST /ews/exchange.asmx - 443 - <Client-IP> ASProxy/CrossSite/Directory/EXCH/15.00.0847.030 - 404 0 0 0
POST /ews/exchange.asmx - 443 - <Client-IP> ASProxy/CrossSite/Directory/EXCH/15.00.0847.030 - 404 0 0 0

↑ Back to the top

Cause

This problem occurs because the InternalNLBBypassUrl value is changed incorrectly after a disaster recovery operation is done on this Exchange 2013 multirole server.

↑ Back to the top

Resolution

To fix this problem, correct the InternalNLBBypassUrl value for Exchange Web Services (EWS) on the problematic server. The correct InternalNLBBypassUrl value should be the following:
https://<problematic server's fqdn>:444/ews/exchange.asmx

To do this, use one of the following methods.

Method 1

Use ADSIEdit to change the InternalNLBBypassUrl value for EWS for this problematic server. Then, recycle the MSExchangeServicesAppPool application pool in IIS. After you recycle the application pool, EWS should work as expected.

Method 2

Use Windows PowerShell to change these settings.

Note Window PowerShell returns a “not within a valid server write scope” error message.
  1. Start Windows PowerShell.
  2. Add the Exchange snap-in. To do this, run the following command:

    Add-PSSnapin *exchange*
  3. Run the following command:
    Set-WebServicesVirtualDirectory -Identity "<problematic server>\EWS (Exchange Back End)" -InternalNLBBypassUrl https://<FQDN of the problematic server>:444/ews/exchange.asmx

↑ Back to the top

Keywords: kbsurveynew, kbtshoot, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3128167
Revision : 1
Created on : 1/7/2017
Published on : 1/11/2016
Exists online : False
Views : 246