You still receive unexpected error messages when you run the Test-OwaConnectivity command or the Test-ActiveSyncConnectivity command after you apply hotfix KB954213 on an Exchange 2007 Service Pack 1-based server

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
You apply the hotfix that is described in Microsoft Knowledge Base (KB) article 954213 on a computer that is running Exchange Server 2007 Service Pack 1 (SP1). Then, when you run the Test-OwaConnectivity command or theTest-ActiveSyncConnectivity command in Exchange Management Shell, you still receive unexpected error messages.

For example, if you run the following command:
Test-OwaConnectivity -MailboxServer <servername> -AllowUnsecureAccess:$true -ClientAccessServer <servername>  | fl 
You receive the following error message:

WARNING: The test was unable to log on to Outlook Web Access because of an authentication failure. WARNING: The test for URL '<OWA URL>' failed. AuthenticationMethod   : FBA ClientAccessServer     : <servername> Scenario               : Logon ScenarioDescription    : Log on to Outlook Web Access and verify the response page. PerformanceCounterName : Logon Latency Result                 : Skipped MailboxServer          : <servername>StartTime              : <Date, Time>Latency                : <Time>SecureAccess           : True Error                  : The test was unable to log on to Outlook Web Access because of an authentication failure. UserName               : <username> VirtualDirectoryName   : owa (Default Web Site) Url                    : <owa URL>UrlType                : Internal EventType              : Warning Port                   : 0 ConnectionType         : Plaintext


If you run the following command:
Test-ActiveSyncConnectivity -MailboxServer <servername> -TrustAnySSLCertificate:$true   | fl
You receive the following error message:

ClientAccessServer     : <servername>Scenario               : Options ScenarioDescription    : To retrieve the Exchange ActiveSync protocol version, issue an HTTP OPTIONS command. PerformanceCounterName : DirectPush Latency Result                 : Failure MailboxServer          : <servername>StartTime              : <Date, Time>Latency                : <time>SecureAccess           : True Error                  : [System.Net.WebException]: The remote server returned an error: (401) Unauthorized.......
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
954213 All Test commands that are related to the Client Access Server fail when you run the commands on an Exchange 2007 server in a disjoint namespace
CAUSE
This problem occurs when a test user is automatically created after you run the Test-OwaConnectivity command or the Test-ActiveSyncConnectivity command on the Client Access server. When the user is created, the UserPrincipalName property is set with the domain name of the mailbox server. Typically, the Exchange server assumes that the mailbox server's domain name is always an Active Directory directory service domain name and uses the UserPrincipalName property in the "domain\user" format. However, the Active Directory domain name does not apply in a disjoint namespace scenario.
RESOLUTION
To resolve this problem, install Update Rollup 9 for Exchange 2007 Service Pack 1. For more information about Update Rollup 9 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic: For more information about how to install the latest Exchange service pack or update rollup, see the following Exchange Help topic:
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/library/bb676377(EXCHG.80).aspx
Properties

Article ID: 968224 - Last Review: 01/16/2015 03:05:10 - Revision: 1.1

  • Microsoft Exchange Server 2007 Service Pack 1
  • kbnosurvey kbarchive kbsurveynew kbfix kbexpertiseinter kbqfe KB968224
Feedback