XADM: Upgrade to Exchange 5.5 Fails If Virus Software Is Enabled (178302)

Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.
Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
Note An antivirus program is designed to help protect your computer from viruses. You must not download or open files from sources that you do not trust, visit Web sites that you do not trust, or open e-mail attachments when your antivirus program is disabled.

For additional information about computer viruses, click the following article number to view the article in the Microsoft Knowledge Base:

129972Computer viruses: description, prevention, and recovery

SYMPTOMS

When you attempt to upgrade Microsoft Exchange Server versions 4.0 or 5.0 to Microsoft Exchange Server version 5.5, errors may occur and you receive one of the following error messages:

Microsoft Exchange Server Setup
An internal initialization error occurred in the database
upgrade process.
Microsoft Exchange Server Setup
ID: no. c1032bfc
<OK>

Microsoft Exchange Server Setup
ERROR: Your upgrade did not complete successfully. Please restart your
Microsoft Exchange Services and your system will behave as it did before
the upgrade was attempted.
Please contact Microsoft Product Support Services for more information.
Microsoft Exchange Server Setup
ID: no. c1032c07
<OK>

CAUSE

When certain virus checking programs are installed, they add various File System Filters as devices. These devices are enabled automatically (or when the server is started) and prevent JET 97 (ESE), the Microsoft Exchange Server 5.5 database, from installing and functioning correctly.

WORKAROUND

The workaround that is presented below will allow the setup program complete the upgrade to Microsoft Exchange Server version 5.5. However, to ensure that Microsoft Exchange Server database utilities will function properly, you should obtain and install a post-Service Pack 3 hotfix for Windows NT 4.0 before you restart any virus software programs on a Microsoft Exchange 5.5 Server computer.

Disable the anti-virus software. Double-click the Services icon in Control Panel to set the appropriate services to Disabled.
Disable the system devices. Double-click the Devices icon in Control Panel. Set the appropriate system devices to Disabled.
Stop all Microsoft Exchange Server Services and set them to Manual startup.
Restart the server and then proceed with the upgrade.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows NT Server version 4.0 Service Pack 3. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem.

http://www.microsoft.com/ntserver/nts/downloads/archive/NT4y2kpostSP3/default.asp

NOTE: Review the Readme.txt file in that directory before you attempt to install the hotfixes.

For additional information, please see the following article in the Microsoft Knowledge Base:

174748 XADM: ESEUTIL /g Returns Error -1022