Exchange Issue
-
Thursday, February 23, 2012 11:19 AMWe are facing an issue with internal mails are not delivering properly to receipient end.
All Replies
-
Thursday, February 23, 2012 11:29 AMWhat happens to mail delivery? Is it delayed delivery or are you getting any NDR?
Gulab Prasad,
MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007
MCITP: Lync Server 2010 | MCITP: Windows Server 2008
My Blog | Z-Hire Employee Provisioning App
-
Thursday, February 23, 2012 11:29 AM
Hi James
You will have to give some more details to assist with troubleshooting. What does "not delivering properly" mean?
Cheers, Steve
-
Thursday, February 23, 2012 11:30 AM
Hi,
can you provide more detail please.
number of server and version ?
all mails or some mails ?
with all client or only some client, is it ok with OWA ?
Are services up ?
Client are connected ?
can you telnet server using 25 port ?
Regards,
Best Regards Don't forget to mark it as answer if it helps
-
Friday, February 24, 2012 9:30 AM
Hi All ,
Sorry for not given the more details about the issue. We are using exchange 2010 with DAG enabled. The internal mail is not receiving to the end user.
when i check the message tracking Error is Failed " The message couldn't be delivered
Any suggesions.. There is nothing in the event viewer. this is not a particular database.
-
Monday, February 27, 2012 12:51 AMModerator
-
Monday, February 27, 2012 5:10 AM
Hi Im getting this error on MY Exchange 2010,
Can anyone help?Thanks.
[PS] C:\Windows\system32>Test-WebServicesConnectivity -MonitoringContext:$true -TrustAnySSLCertificate:$true -LightMode:
$true |fl
RunspaceId : ae612c5a-0cac-4322-abab-7f2f2224e363
LocalSite : Default-First-Site-Name
SecureAccess : True
VirtualDirectoryName :
Url :
UrlType : Unknown
Port : 0
ConnectionType : Plaintext
ClientAccessServerShortName : seaexchange
LocalSiteShortName : Default-First-Site-Name
ClientAccessServer : seaexchange.ships.ad
Scenario : GetFolder
ScenarioDescription : Issue an Exchange Web Services GetFolder call to retrieve a folder.
PerformanceCounterName : CreateItem Latency
Result : Failure
Error : [System.Web.Services.Protocols.SoapException]: Active Directory is unavailable. Try again
later.
UserName : extest_97761bfe28284
StartTime : 2/26/2012 9:01:11 PM
Latency : 00:00:00.0156135
EventType : Error
LatencyInMillisecondsString :
Identity :
IsValid : True
RunspaceId : ae612c5a-0cac-4322-abab-7f2f2224e363
Events : {Source: MSExchange Monitoring WebServicesConnectivity Internal
Id: 1011
Type: Success
Message: The Client Access server configuration check succeeded., Source: MSExchange Monitoring W
ebServicesConnectivity Internal
Id: 1007
Type: Success
Message: Credentials were successfully loaded for all test mailboxes in the local site., Source:
MSExchange Monitoring WebServicesConnectivity Internal
Id: 1006
Type: Success
Message: There were no errors loading credentials for the test mailboxes that exist on mailbox se
rvers in the local site., Source: MSExchange Monitoring WebServicesConnectivity Internal
Id: 1001
Type: Error
Message: Some of the Client Access server connectivity transactions failed. Detailed information:
-------------------------------------
Target: seaexchange.ships.ad|Default-First-Site-Name
Error: [System.Web.Services.Protocols.SoapException]: Active Directory is unavailable. Try again
later.
Details:
The Web Services method failed for the following reason:
Active Directory is unavailable. Try again later.
Call stack
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message
, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] par
ameters)
at Microsoft.Exchange.SoapWebClient.CustomSoapHttpClientProtocol.<>c__DisplayClass4.<Invoke>b_
_3()
at Microsoft.Exchange.SoapWebClient.HttpAuthenticator.NoHttpAuthenticator.AuthenticateAndExecu
te[T](SoapHttpClientProtocol client, AuthenticateAndExecuteHandler`1 handler)
at Microsoft.Exchange.SoapWebClient.SoapHttpClientAuthenticator.AuthenticateAndExecute[T](Soap
HttpClientProtocol client, AuthenticateAndExecuteHandler`1 handler)
at Microsoft.Exchange.SoapWebClient.EWS.ExchangeServiceBinding.ConvertId(ConvertIdType Convert
Id1)
at Microsoft.Exchange.Monitoring.TestWebServicesConnectivity.CallConvertId(WSExecutionContext
context)
at Microsoft.Exchange.Monitoring.TestWebServicesConnectivity.DoConnectivityTest(WSExecutionCon
text context)
Client Access Server Name: seaexchange.ships.ad
Scenario: GetFolder
Scenario Description: Issue an Exchange Web Services GetFolder call to retrieve a folder.
User Name: extest_97761bfe28284
Performance Counter Name: CreateItem Latency
Result: Failure
Site: Default-First-Site-Name
Latency: 00:00:00.0156135
Secure Access: True
ConnectionType: Plaintext
Port: 0
Latency (ms): 15.6135
Virtual Directory Name:
URL: null
URL Type: Unknown
Error:
[System.Web.Services.Protocols.SoapException]: Active Directory is unavailable. Try again later.
-------------------------------------
}
PerformanceCounters : {Object: MSExchange Monitoring WebServicesConnectivity Internal
Counter: CreateItem Latency
Instance: seaexchange.ships.ad|Default-First-Site-Name
Value: -1000}
- Edited by khozhi Monday, February 27, 2012 5:11 AM
-
Monday, February 27, 2012 7:16 AM
Do u have any antivirus,antispam agents in your hub transport server..?- Proposed As Answer by Terence YuMicrosoft Contingent Staff, Moderator Friday, March 02, 2012 8:36 AM

