When I run the test-systemhealth cmdlet on either one of my CAS, it breaks RPC over HTTP for Outlook clients. They start receiving message boxes to authenticate against the mailbox server. Hereare the only events showing up in the App log:Information7/8/2009 7:00:11 PMBPA100None Processing for ExBPA is 0% complete.Information7/8/2009 7:00:17 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Application Error Reporting. Product Version: 12.0.6015.5000. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:17 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: System Center Operations Manager 2007 R2 Agent. Product Version: 6.1.7221.0. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:17 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Exchange 2007 Enterprise Anti-spam Signatures. Product Version: 3.3.4604.600. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:17 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Active Directory Management Pack Helper Object. Product Version: 1.1.0. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:17 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Exchange Server. Product Version: 8.1.240.6. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:17 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Forefront Server Security. Product Version: 10.1. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:17 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Time Travel Tracing (x86). Product Version: 2.04. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:17 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Exchange 2007 Enterprise Block List Updates. Product Version: 3.3.4604.001. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:18 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Dell OpenManage Server Administrator. Product Version: 5.3.0. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:18 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Time Travel Tracing (AMD64). Product Version: 2.04. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:18 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Forefront Server Security Deployment Agent 10.5.1241.0. Product Version: 10.5.1241.0. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:18 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Network Monitor 3.1. Product Version: 03.01.0512.0000. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:18 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Forefront Server Security. Product Version: 10.1. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:18 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Exchange 2007 Standard Anti-spam Filter Updates. Product Version: 3.3.4604.600. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:18 PMMsiInstaller1035None Windows Installer reconfigured the product. Product Name: Microsoft Silverlight. Product Version: 1.0.30716.0. Product Language: 1033. Reconfiguration success or error status: 0.Information7/8/2009 7:00:42 PMBPA101None Processing for ExBPA is 100% complete.Information7/8/2009 7:02:41 PMMSExchange ADAccess2080Topology Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1784). Exchange Active Directory Provider has discovered the following servers with the following characteristicsInformation7/8/2009 7:02:41 PMMSExchange ADAccess2095Topology Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1784). The Configuration Domain Controller has been changed from MYSERVER002.SUB.MYDOMAIN.local to MYSERVER001.SUB.MYDOMAIN.local.Information7/8/2009 7:02:42 PMMSExchange Messaging Policies1000Journaling Journal rules were loaded.Information7/8/2009 7:02:42 PMMSExchangeTransport16022Configuration A configuration update has successfully completed.Information7/8/2009 7:02:42 PMMSExchangeTransport16022Configuration A configuration update has successfully completed.Information7/8/2009 7:02:42 PMMSExchangeTransport16002Configuration The new transport server configuration has been read and components have been notified.Information7/8/2009 7:02:42 PMMSExchangeTransport16022Configuration A configuration update has successfully completed.Information7/8/2009 7:03:25 PMMSExchange OWA63ADNotifications The Outlook Web Access configuration settings have been read and updated successfully. Virtual directory: "owa". Web site: "Default Web Site".Information7/8/2009 7:03:25 PMMSExchange OWA63ADNotifications The Outlook Web Access configuration settings have been read and updated successfully. Virtual directory: "owa". Web site: "Default Web Site".Information7/8/2009 7:03:25 PMMSExchange OWA63ADNotifications The Outlook Web Access configuration settings have been read and updated successfully. Virtual directory: "owa". Web site: "Default Web Site".If I perform an IISRESET, the issue resolves itself. I verified all the app pools are running normally before performing the reset. We are running Rollup 2. Anyone have any insight as to what might be causing this? Thanks!

Did you check your IIS Services to verify that those did not stop? What about moving to Rollup 8? What version of Windows and IIS are you using?SF - MCITP:EMA, MCTS

IIS Services are running when the breakdown occurs. We are scheduled toinstall Rollup 8 in three weeks. We are currently running Server 2008 x64 Standard on both CAS with plans to update to SP2 within the next 30-60 days.Thanks!

Hi, I would like to know whether Outlook users are prompted for authentication repeated even they have provided correct credential after running test-systemhealth command. I am not able to find any similar issue in our internal database. Based on the current situation, as the issue solved after resetting IIS, we are hard to identify the root cause of the issue. Nevertheless, I suggest you review the IIS log to check whether we are able to find any clues regarding the problem. In addition, in case the Outlook Anywhere issue occurs again, we can following steps below troubleshoot the issue: 1. Please check whether only external clients encounter the problem. You can configure an Outlook client in internal network and have it connect to Exchange Server through RPC over HTTP. If the issue does not occur in internal network, we do think that the Exchange is configured correctly for Outlook Anywhere to work and you need to focus on the firewall which may affect Outlook Where feature 2. If the internal Outlook client is not able to connect to exchange server either, we do suspect that it is an Exchange related issue. We can use following methods to troubleshoot the issue: a. Access Outlook Anywhere URL (for example: https://outlookanywherename/rpc/rpcproxy.dll). You should get a blank page after authentication. In addition, no certificate related warning is received. In most cases, being repeatedly prompted for credentials is a good indicator that the root certificate for the Certificate Authority is not present in the Trusted Root Certificates Authority store on the client. b. You can use RPCCFG tool to check whether the valid ports registry key is configured correctly on CAS server. You should get result like below: Note: MB is the netbios name of backend mailbox server and the mb.lab.com is the FQDN of the backend mailbox server Server Name Port Settings ------------------------------------------------------------------------------- MB 6001-6002 6004 mb.lab.com 6001-6002 6004 c. You can use RPCDump tool to check whether the 6001, 6002 and 6004 ports are listened by Mailbox Server: a4f1db00-ca47-1067-b31f-00dd010662da represents the Information Store which should listen 6001 port f5cc5a18-4264-101a-8c59-08002b2f8426 represents the Directory Proxy Service which should listen 6004 port 1544f5e0-613c-11d1-93df-00c04fd7bd09 represents the Directory Referral Service which should listen 6002 port d. You can also use RPCPing tool to check whether the issue occurs when client connects to CAS server or the CAS server connects to backend mailbox server: How to use the RPC Ping utility to troubleshoot connectivity issues with the Exchange over the Internet feature in Outlook 2007 and in Outlook 2003 http://support.microsoft.com/kb/831051/en-us In case the above method is not able to help you identify the root cause of the issue, you may need to submit a case to have Support Engineer to further troubleshoot the issue. For more information regarding Outlook Anywhere: How does Outlook Anywhere work (and not work)? http://msexchangeteam.com/archive/2008/06/20/449053.aspx Autodiscover and Outlook Anywhere Issues http://technet.microsoft.com/en-us/library/cc411322.aspx How to Set the NTDS Port on a Global Catalog Server Acting as an Exchange Server 2003 Back-End Server http://technet.microsoft.com/en-us/library/bb124159(EXCHG.65).aspx Mike