Hi,

Running Exchange Server 2013 CU3 Standard.

This is an unusual issue which has been bugging me since setting up this system. The event log is frequently producing this error although other log entries imply that MSExchangeApplicationLogic is operational.

Log Name:      Application
Source:        MSExchangeApplicationLogic
Date:          19/02/2014 15:07:31
Event ID:      3018
Task Category: Extension
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.contoso.com
Description:
Scenario: GetConfig.GetConfig. The request failed. Mailbox:  Url: https://o15.officeredir.microsoft.com/r/rlidMktplcWSConfig15 Exception: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 65.55.69.140:443
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at Microsoft.Exchange.Data.ApplicationLogic.Extension.BaseAsyncOmexCommand.<>c__DisplayClass2.<EndGetResponseCallback>b__1()

The other server of a pair is showing no such errors.

Does anyone have any experience of dealing with this?

Cheers, Nick C

• Edited by Nick G Cooper Thursday, February 20, 2014 7:53 AM

Hi Nick,

Lack of resource on "Event ID 3018 MSExchangeApplicationLogic".

According to the error message "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connect host has failed to respond 65.55.69.140:443", it seems an issue on the Network side.

Based on my experience, this issue happens if the machine that is running the program is behind proxy (or firewall) that allows traffic coming only from authenticated users.

By default Azure/IIS configures AppPool to run under "NetworkService". Hence, Proxy does not allow traffic coming from this account.

More details in the following blog:

Azure: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond x.x.x.x:x"

http://blogs.msdn.com/b/narahari/archive/2011/12/21/azure-a-connection-attempt-failed-because-the-connected-party-did-not-properly-respond-after-a-period-of-time-or-established-connection-failed-because-connected-host-has-failed-to-respond-x-x-x-x-x-quot.aspx

 

Please also make sure the 443 port is available.

 

If I have any misunderstand, please correct me.

 

Thanks

Mavis

Hi Nick,

Any update?

 

Thanks

Mavis

Hello Mavis,

I'm having the same issue for our Exchange 2013 (on premises) are trying to connect to microsoft.

do you know why ? and how can we configure it to use outbound connecting via a proxy server

it tries to access the following URL:

https://o15.officeredir.microsoft.com/r/rlidMktplcWSConfig15?CV=15.0.847.32&Client=WAC_Outlook

Regards

Antnio

Hello Mavis, Antonio,

we have the same issue for our Exchange 2013 also on premises. I tries to connect to:

https://o15.officeredir.microsoft.com/r/rlidMktplcWSConfig15?CV=15.0.913.22&Client=WAC_Outlook  Where 15.0.913.22 is the Version of Exchange

Exch2013 CU5. Why does it try to Access, and how can we stop it??

Regards Rudi

Hi,

A bit of an update: The server in question is behind a firewall preventing direct access to the internet. Requests for internet resources such as https://o15.officeredir.microsoft.com/r/rlidMktplcWSConfig15 are blocked so the server never manages to connect to the resource.

The solution we have in place is to ensure that the servers can connect to the internet via a web proxy.

Add the web proxy address and port to the Exchange Server Configuration using the Exchange Management Console.

Set-ExchangeServer -InternetWebProxy internetwebproxy.contoso.com:nnnn where nnnn is the port number if required.

I hope this helps anyone who may still be struggling with this.

Regards,

Nick

• Proposed as answer by SkinniO Thursday, January 22, 2015 8:23 AM

Set-ExchangeServer -InternetWebProxy internetwebproxy.contoso.com:nnnn where nnnn is the port number if required.

Thank you. Just wanted to add that the value needs to be entered in the form of an uri. So for example:

Set-ExchangeServer server01 -InternetWebProxy http://10.3.3.3:80