Visio2000: Microsoft Office XP Upgrade Causes Visio to Stop Responding When Started

If you upgrade Microsoft Office 2000 to Microsoft Office XP, and then start Microsoft Visio 2000, you receive the following message and Visio stops responding when the progress bar is at 80% (percent).

-or-

The Windows Installer displays the following message and Visio never completely starts, because the message box never closes.

This problem occurs when any of the following conditions is true.

Case 1

1. You install Office 2000.
2. You install the non SR-1 version of Visio 2000.
3. You install Office XP and choose to have Office 2000 removed during the Office XP installation.
   
   NOTE: When you click Upgrade Now during the Office XP installation, Office 2000 is automatically removed.

Case 2

1. You install Office 2000.
2. You install Visio 2000 Service Release 1 (SR-1) by using the unattended installation package, Vis2000.msi.
   
   NOTE: Vis2000.msi is only available on Select CDs.
3. You install Office XP and choose to have Office 2000 removed during the Office XP installation.

Case 3

1. You install Office 2000.
2. You install the non SR-1 version of Visio 2000.
3. You install Office XP and choose to keep Office 2000 installed during the Office XP installation.
4. You uninstall Office 2000 at any time after the Office XP installation is finished.

To resolve this problem, use the appropriate methods for your situation.

Method 1: Reinstall Microsoft Visual Basic for Applications

To resolve this issue, reinstall the Windows Installer package for Visual Basic for Applications (VBA6.msi). To do this, follow these steps:

1. Quit all programs that are running on your computer, including any antivirus programs.
2. Open the following folder on your Microsoft Visio CD:
   \Install\Bin\SP\VBA
3. Right-click Vba6.msi, and then click Install on the shortcut menu.
4. Click OK when the installation is finished.

Method 2: Preventative Measure for Corporate Deployment

If you are deploying Office XP across a large number of computers, you can "chain" the installation of the Vba6.msi Windows Installer package onto the Office XP installation. This prevents the behavior from occurring in the first place.

For additional information about how to chain the Vba6.msi package, click the article number below to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.