The Setup program stops responding, and event ID 1031 is logged when you try to install or to reinstall Exchange Server 2003 in Disaster Recovery mode

When you try to install or to reinstall Microsoft Exchange Server 2003 in Disaster Recovery mode, you experience the following symptoms:

�	The Exchange Server Setup program stops responding (hangs) when it tries to start the Microsoft Exchange System Attendant (MSExchangeSA) service.
�	An event that resembles the following event is logged in the Application log: Event Source: MSExchangeSA Event Catagory: General Event ID: 1031 Data: date Time: time Type Error User: N/A Computer: ComputerName Description: One of the System Attendant's tasks was blocked. Function: OfflineABScanTack Work

This issue may occur if an antivirus program is running when you install Exchange Server 2003 in Disaster Recovery mode.

To work around this issue, follow these steps.

Important These steps may increase your security risk. These steps may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you decide to implement this process, take any appropriate additional steps to help protect the system. We recommend that you use this process only if you really require this process.

1.	Stop and then temporarily disable the antivirus program.
2.	Restart the computer.
3.	Install Exchange Server 2003 in Disaster Recovery mode.
4.	Re-enable the antivirus program.

For more information about disaster recovery operations in Exchange Server 2003, see the "Exchange 2003 Disaster Recovery Operations Guide." To do this, visit the following Microsoft Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base: