Users cannot log on to Outlook Web Access after you apply Exchange 2007 Service Pack 1 in an Exchange 2007 environment

Really :-|

New SP1 KB: http://support.microsoft.com/kb/947168

Microsoft Exchange Server 2007 Service Pack 1 (SP1) was applied to the Internet-facing Client Access Server (CAS). However, Exchange 2007 SP1 was not applied to internal-facing CASs. When a user tries to log on to Microsoft Office Outlook Web Access through a proxy, the user receives the following error message:

Outlook Web Access is not currently available for the user mailbox that you are trying to access. If the problem continues, contact technical support for your organization and tell them the following: The Microsoft Exchange Client Access server that is proxying the Outlook Web Access requests is running an older version of Microsoft Exchange than the Client Access server in the mailbox Active Directory site.

MSExchange ADAccess Event ID 2501 and 2114

I am seeing quite a few of these on my Exchange 2007 RTM SCC Clusters.  We also have the need to recycle the Microsoft Exchange Active Directory Topology Service to get mail flow working :-|  Go on some tell me that SP1 fixes this :-D

Event Type: Error
Event Source: MSExchange ADAccess
Event Category: General
Event ID: 2501
Date:  21/01/2008
Time:  15:22:06
User:  N/A
Description:
Process MSEXCHANGEADTOPOLOGY (PID=2028). The site monitor API was unable to verify the site name for this Exchange computer – Call=DsGetSiteNameW Error code=800703e5. Make sure that Exchange server is correctly registered on the DNS server. 

Event Type: Error
Event Source: MSExchange ADAccess
Event Category: Topology
Event ID: 2114
Date:  21/01/2008
Time:  15:10:03
User:  N/A
Description:
Process STORE.EXE (PID=5936). Topology discovery failed, error 0x8007077f (Local Error). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, “Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.