Microsoft KB Archive/299764

= Visual J++ compatibility problem requires Microsoft VM upgrade on Windows XP and Windows Server 2003 =

Article ID: 299764

Article Last Modified on 10/26/2007

-

APPLIES TO

 Microsoft Visual J++ 6.0 Standard Edition, when used with:  Microsoft Windows XP Professional

 Microsoft Windows Server 2003, Standard Edition (32-bit x86) 

-



This article was previously published under Q299764





Beta Information
This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location from which you downloaded the release.



SYMPTOMS
When you install Visual J++ on a computer running a fresh installation of Windows Server 2003 or Windows XP, or when you upgrade to Windows XP on a computer that is running Windows 95, Windows 98, Windows NT, or Windows 2000, you may have to update the Microsoft virtual machine (Microsoft VM) to version 5.00.3200 or later. When you start to install the program, you may experience one of the following problems:  On a new install of Windows Server 2003 or Windows XP

You may receive the following error message:

Microsoft Visual J++ has a known compatibility issue described in Microsoft Knowledge Base article Q299764. Microsoft Visual J++ customers must correct this issue before using Visual J++.

Windows blocks the Visual J++ install program until you install or update the Microsoft VM.</li> On an upgrade install of Windows XP

When you upgrade to Windows XP on a Windows-based computer that already has Visual J++ installed, Windows XP Setup detects that Visual J++ is installed, and then adds the following error message to the Windows XP upgrade report:

Microsoft Visual J++ has a known compatibility issue described in Microsoft Knowledge Base article Q299764. Microsoft Visual J++ customers must correct this issue before using Visual J++.

In this scenario, you may experience problems when you run Visual J++ until you upgrade to a current version of Microsoft VM.</li></ul>

<div class="cause_section">

CAUSE
The Windows Server 2003 and Windows XP Application Compatibility Technologies block the installation of Visual J++ on Windows Server 2003 or Windows XP if Microsoft VM is not installed or if the version of Microsoft VM is older than version 5.00.3200. This occurs because the security and encryption dynamic-link libraries (DLLs) that are installed with older versions of Microsoft VM (such as the version that is distributed with Visual J++) are not compatible with the newer DLL versions that Windows Server 2003 and Windows XP use.

By default, on a new installation of Windows Server 2003 or Windows XP, Microsoft VM is not installed with the operating system. When you try to install Visual J++, and the Microsoft VM does not exist on the computer or is older than the version that is provided with Visual J++, Visual J++ tries to install the Microsoft VM that is included with the Visual J++ distribution. However, because the Microsoft VM that is included with Visual J++ is an older version of the Microsoft VM, and its security and encryption DLLs are not compatible with the operating system, the Application Compatibility Technologies blocks the install of Microsoft Visual J++ on the computer until you install a compatible version of the Microsoft VM.

<div class="resolution_section">

RESOLUTION
To resolve this problem, install the Microsoft virtual machine from the Visual J++ CD-ROM, and then visit the Windows Update Web site to install the security fixes. To install the Microsoft virtual machine from the Visual J++ CD-ROM, follow these steps:
 * 1) On the CD-ROM install media, open the IE4 subfolder.
 * 2) Locate and then double-click Msjavx86.exe to run the executable file.
 * 3) Click Start, point to All Programs, and then click Windows Update. Install any fixes for the Microsoft VM that Windows Update detects.

<div class="references_section">