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

Last reviewed: March 16, 1998
Article ID: Q178302
The information in this article applies to:
  • Microsoft Exchange Server, versions 4.0 and 5.0

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>

   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. c1032c08
   <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.

  1. Disable the anti-virus software. Double-click the Services icon in Control Panel to set the appropriate services to Disabled.

  2. Disable the system devices. Double-click the Devices icon in Control Panel. Set the appropriate system devices to Disabled.

  3. Stop all Microsoft Exchange Server Services and set them to Manual startup.

  4. Restart the server and then proceed with the upgrade.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows NT Server version 4.0 Service Pack 3. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

This hotfix is included in the Microsoft Windows NT Server version 4.0 post- Service Pack 3 rollup hotfixes which are available at the following FTP site:

   ftp://ftp.microsoft.com/bussys/winnt/winnt-
   public/fixes/usa/nt40/hotfixes-postSP3/roll-up

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:

   ARTICLE-ID: Q174748
   TITLE     : XADM: ESEUTIL /g Returns Error -1022


Additional query words: c1032bfc upgrade 5.5 innoculan
Version : WINDOWS:5.5
Platform : WINDOWS
Issue type : kbbug


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 16, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.