Reset Password · PC & Mac Help and Assistance

Welcome Guest! To enable all features please Login or Register

Posted by: Lemonde - 12 July 2017 07:09:10
We are seeing that the server is still referencing the old OAB server even though it has been decommissioned. Where do we remove the reference? Log Name: Application Source: MSExchange Front End HTTP Proxy Date: 12/07/2017 07:00:30 Event ID: 3005 Task Category: Core Level: Warning Keywords: Classic User: N/A Computer: server.domain,suffix Description: [Oab] Marking ClientAccess 2010 server OABserver.domain,suffix (https://OABserver.domain,suffix/OAB) as unhealthy due to 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 192.168.144.14:443 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) 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.GetResponse() at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url) Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange Front End HTTP Proxy" /> <EventID Qualifiers="32768">3005</EventID> <Level>3</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-07-12T06:00:30.000000000Z" /> <EventRecordID>3998681</EventRecordID> <Channel>Application</Channel> <Computer>server.domain,suffix</Computer> <Security /> </System> <EventData> <Data>Oab</Data> <Data>OABserver.domain,suffix</Data> <Data>https://OABserver.domain,suffix/OAB</Data> <Data>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 192.168.144.14:443 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) 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.GetResponse() at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data> </EventData> </Event>[/code]

Posted by: Lemonde - 12 July 2017 07:09:10

We are seeing that the server is still referencing the old OAB server even though it has been decommissioned. Where do we remove the reference? Log Name: Application Source: MSExchange Front End HTTP Proxy Date: 12/07/2017 07:00:30 Event ID: 3005 Task Category: Core Level: Warning Keywords: Classic User: N/A Computer: server.domain,suffix Description: [Oab] Marking ClientAccess 2010 server OABserver.domain,suffix (https://OABserver.domain,suffix/OAB) as unhealthy due to 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 192.168.144.14:443 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) 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.GetResponse() at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url) Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange Front End HTTP Proxy" /> <EventID Qualifiers="32768">3005</EventID> <Level>3</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-07-12T06:00:30.000000000Z" /> <EventRecordID>3998681</EventRecordID> <Channel>Application</Channel> <Computer>server.domain,suffix</Computer> <Security /> </System> <EventData> <Data>Oab</Data> <Data>OABserver.domain,suffix</Data> <Data>https://OABserver.domain,suffix/OAB</Data> <Data>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 192.168.144.14:443 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) 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.GetResponse() at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data> </EventData> </Event>[/code]

Posted by: sirclesadmin - 31 August 2017 13:15:37
Also seeing: Log Name: Application Source: MSExchangeApplicationLogic Date: 31/08/2017 10:56:31 Event ID: 3054 Task Category: Extension Level: Error Keywords: Classic User: N/A Computer: servername.domain.suffix Description: Scenario: ProcessOrgExtensions. The organization mailbox for emaildomain.suffix could not be retrieved. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchangeApplicationLogic" /> <EventID Qualifiers="49156">3054</EventID> <Level>2</Level> <Task>3</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-08-31T09:56:31.000000000Z" /> <EventRecordID>4564150</EventRecordID> <Channel>Application</Channel> <Computer>servername.domain.suffix</Computer> <Security /> </System> <EventData> <Data>ProcessOrgExtensions</Data> <Data>emaildomain.suffix</Data> </EventData> </Event>[/code]

Posted by: sirclesadmin - 31 August 2017 13:15:37

Also seeing: Log Name: Application Source: MSExchangeApplicationLogic Date: 31/08/2017 10:56:31 Event ID: 3054 Task Category: Extension Level: Error Keywords: Classic User: N/A Computer: servername.domain.suffix Description: Scenario: ProcessOrgExtensions. The organization mailbox for emaildomain.suffix could not be retrieved. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchangeApplicationLogic" /> <EventID Qualifiers="49156">3054</EventID> <Level>2</Level> <Task>3</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-08-31T09:56:31.000000000Z" /> <EventRecordID>4564150</EventRecordID> <Channel>Application</Channel> <Computer>servername.domain.suffix</Computer> <Security /> </System> <EventData> <Data>ProcessOrgExtensions</Data> <Data>emaildomain.suffix</Data> </EventData> </Event>[/code]

Posted by: Lemonde - 24 April 2020 14:29:35
Check that all of the old servers have been removed in ADSIEdit Under services>microsoft exchange>Organisation name>Administrative Groups>Exchange administrative group>servers Just be sure you do not delete any servers that are live, so check version numbers etc before taking any action. DO NOT DELETE THE WRONG SERVER, YOU HAVE BEEN WARNED!!! Because then you will have to restore an authoritative domain restore onto a DC to get email working again.

Posted by: Lemonde - 24 April 2020 14:29:35

Check that all of the old servers have been removed in ADSIEdit Under services>microsoft exchange>Organisation name>Administrative Groups>Exchange administrative group>servers Just be sure you do not delete any servers that are live, so check version numbers etc before taking any action. DO NOT DELETE THE WRONG SERVER, YOU HAVE BEEN WARNED!!! Because then you will have to restore an authoritative domain restore onto a DC to get email working again.

Important Information: