Article ID: 945078 - Last Review: December 4, 2007 - Revision: 1.0 A time-out may occur in Exchange Server 2007 when the SA resource is trying to come onlineOn This PageSYMPTOMSIn Microsoft Exchange Server 2007, you may experience a
time-out problem when you use the System Attendant (SA) resource on a Single
Copy Cluster (SCC) or on a Continuous Copy Cluster (CCR). The time-out occurs
when the SA resource is trying to come online. This problem may occur during
Setup, after a restart, after a failover, or after you move a group by
using the move-clusteredMailboxServer cmdlet. Additionally, the following events may be logged in the System log: Event Type: Error Event Type: Error Event Type: Information Event Type: Information Event Type: Error Event Type:
Information Event Type: Error
Event Type: Error Event Type: Warning Event
Type: Error Event Type: Error Event Type: Warning CAUSEAlthough the System Attendant service starts, the service
times out while it waits for the SA resource. RESOLUTIONTo resolve this problem, use a different time-out
value. The SA resource fails because it is not completing initialization before the 40-second time-out. The cluster pending time-out value for the SA resource is 180 seconds. However, the Exres.dll file uses an internal time-out value of 40 seconds. The Exres.dll file is not honoring the default setting of 180 seconds for the SA resource. However, if you set any other time-out value for the SA resource, the setting is observed. You can set the time-out value by using Cluster Administrator (CluAdmin.exe) or by using a command prompt. To use Cluster Administrator to set a time-out valueOpen the properties of the SA resource, click the Advanced tab, and then change the pending time-out value to 150 seconds.To use the command prompt to set a time-out valueOpan a command prompt, type the following command, and then press ENTER:cluster res “Exchange System Attendant
Instance (CMS Name)” /prop PendingTimeout=150000 MORE INFORMATIONIf an Exchange 2007 cluster is experiencing the problems
that are described in this article, there may be underlying Active Directory
directory service issues. | Article Translations
|
Back to the top
