Issue: Exchange 2007 Test-OutlookWebService Part 1 – Test-OutlookWebService

-

 

 

On E2K7
[PS] C:\Documents and Settings\exchadm\Desktop>Test-OutlookWebServices | fl

Id      : 1003
Type    : Information
Message : About to test AutoDiscover with the e-mail address exchadm@msft.com.

Id      : 1007
Type    : Information
Message : Testing server BQT-CA07.msft.corp.com with the published name https:/
          /bqt-ca07.msft.corp.com/EWS/Exchange.asmx & https://oaw.msft.com/ews/
          exchange.asmx.

Id      : 1019
Type    : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover
           URL on this object is https://BQT-CA07.msft.corp.com/Autodiscover/Au
          todiscover.xml.

Id      : 1006
Type    : Information
Message : The Autodiscover service was contacted at https://BQT-CA07.msft.corp.
          com/Autodiscover/Autodiscover.xml.

Id      : 1016
Type    : Success
Message : [EXCH]-Successfully contacted the AS service at https://bqt-ca07.msft
          .corp.com/EWS/Exchange.asmx. The elapsed time was 46 milliseconds.

Id      : 1015
Type    : Information
Message : [EXCH]-The OAB is not configured for this user.

Id      : 1014
Type    : Success
Message : [EXCH]-Successfully contacted the UM service at https://bqt-ca07.msft
          .corp.com/UnifiedMessaging/Service.asmx. The elapsed time was 15 mill
          iseconds.

Id      : 1013
Type    : Error
Message : When contacting https://oaw.msft.com/ews/exchange.asmx received the e
          rror The request failed with HTTP status 401: Unauthorized.

Id      : 1016
Type    : Error
Message : [EXPR]-Error when contacting the AS service at https://oaw.msft.com/e
          ws/exchange.asmx. The elapsed time was 78 milliseconds.

Id      : 1015
Type    : Information
Message : [EXPR]-The OAB is not configured for this user.

Id      : 1014
Type    : Information
Message : [EXPR]-The UM is not configured for this user.

Id      : 1017
Type    : Success
Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://oaw.ben
          q.com/Rpc. The elapsed time was 562 milliseconds.

Id      : 1006
Type    : Success
Message : The Autodiscover service was tested successfully.

Id      : 1021
Type    : Information
Message : The following web services generated errors.
              As in EXPR
          Please use the prior output to diagnose and correct the errors.


 

On E14
[PS] C:\Windows\system32>Test-OutlookWebServices

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1003
Type       : Information
Message    : Autodiscover is about to be tested with the e-mail address MSExchApproval1f05a927-3be2-4fb9-aa03-b59fe3b56f4c@msft.com.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1007
Type       : Information
Message    : Testing server BQT-E14CAS1.msft.corp.com with the published name https://bqt-e14cas1.msft.corp.com/EWS/Exchange.asmx & https://msft.com/ews/exchange.asmx.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1019
Type       : Information
Message    : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://BQT-E14CAS1.msft.corp.com/Autodiscover/Autodiscover.xml.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1006
Type       : Information
Message    : Contacted the Autodiscover service at https://BQT-E14CAS1.msft.corp.com/Autodiscover/Autodiscover.xml.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1013
Type       : Error
Message    : When contacting https://BQT-E14CAS1.msft.corp.com/EWS/Exchange.asmx received the error The operation has timed out

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1016
Type       : Error
Message    : [EXCH]-Error contacting the AS service at https://BQT-E14CAS1.msft.corp.com/EWS/Exchange.asmx. Elapsed time was 884 milliseconds.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1015
Type       : Success
Message    : [EXCH]-Successfully contacted the OAB service at https://BQT-E14CAS1.msft.corp.com/EWS/Exchange.asmx. Theelapsed time was 0 milliseconds.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1014
Type       : Success
Message    : [EXCH]-Successfully contacted the UM service at https://BQT-E14CAS1.msft.corp.com/EWS/UM2007Legacy.asmx. The elapsed time was 934 milliseconds.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1013
Type       : Error
Message    : When contacting https://BQT-E14CAS1.msft.corp.com/ews/exchange.asmx received the error The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1013
Type       : Error
Message    : When contacting https://BQT-E14CAS1.msft.corp.com/ews/exchange.asmx received the error The remote certificate is invalid according to the validation procedure.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1016
Type       : Error
Message    : [EXPR]-Error contacting the AS service at https://BQT-E14CAS1.msft.corp.com/ews/exchange.asmx. Elapsed time was 46 milliseconds.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1015
Type       : Success
Message    : [EXPR]-Successfully contacted the OAB service at https://BQT-E14CAS1.msft.corp.com/ews/exchange.asmx. The elapsed time was 0 milliseconds.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1014
Type       : Success
Message    : [EXPR]-Successfully contacted the UM service at https://BQT-E14CAS1.msft.corp.com/ews/UM2007Legacy.asmx. The elapsed time was 15 milliseconds.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1013
Type       : Error
Message    : When contacting https://oaw.BQT-E14CAS1.msft.corp.com/Rpc received the error The remote name could not be resolved: 'oaw.bqt-e14cas1.msft.corp.com'

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1017
Type       : Error
Message    : [EXPR]-Error contacting the RPC/HTTP service at https://oaw.BQT-E14CAS1.msft.corp.com/Rpc. Elapsed time was 15 milliseconds.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1006
Type       : Success
Message    : Autodiscover was tested successfully.

RunspaceId : 6edf2e57-3ff5-468e-ba99-32ff5c7b3f1f
Id         : 1021
Type       : Information
Message    : The following web services generated errors.
                 As in EXCH
                 As, in EXPR
                 Contacting server in EXPR
             . Use the previous output to diagnose and correct the errors.

 

 

Blog Extended Reading
1. Issue: Exchange 2007 Test-OutlookWebService Part 1 – Test-OutlookWebService
2. Issue: Exchange 2007 Test-OutlookWebService Part 2 - Get-OutlookProvider

More Information & Reference
1. Outlook Anywhere ask for repetitive logon requests
2. 自動探索服務傳回意外的 Outlook 無所不在 Proxy 設定值

 

image

Comments

Post a Comment

Popular posts from this blog

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Secti...
Read more

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c7992...
Read more

REF: Planning Exchange 2010 DAG - Part 1 - Network Requirements

-
Image
  Planning for High Availability and Site Resilience  - Network Requirements (a single MAPI network / one or more Replication networks ) In Exchange 2010, each DAG will have multiple networks: a single MAPI network , which is used by other Exchange 2010 servers to communicate with the Mailbox server in the DAG, and one or more Replication networks , which are used for log shipping and seeding within the DAG. It's important that the DAG networks are configured correctly. (two adapters/ MAPI network failover/ Replication network revert to MAPI Network/ ) Each member of the DAG must have at least two network adapters installed . This configuration provides you with one MAPI network and one Replication network, and the following recovery behaviors: In the event of a failure affecting the MAPI network, a server failover will occur (assuming there are healthy mailbox database copies that can be activated). In the event of a failure affectin...
Read more