DOC: MTS Debugging Requires Windows NT 4.0 SP4

ID: Q199226

The information in this article applies to:
  • Microsoft Visual J++, version 6.0

SUMMARY

Visual J++ 6.0 has several features that rely on functionality shipping in Windows NT 4.0 Service Pack 4 (SP4). This Windows NT Service Pack was not available at the time that Visual J++ 6.0 shipped. Most of the features that are required from Windows NT 4.0 SP4 are related to MTS Java classes and MTS bug fixes for the Visual J++ debugger.


MORE INFORMATION

Windows NT 4.0 SP4 fixes the following Visual J++ problems or issues:

  • ComFailException in Java, or "Class does not support Automation" errors in Visual Basic. These occur when calling methods of an MTS Java component from the Options command on the Tools menu, and click Debugger and Java, and select Attach to running programs.


  • Various errors when trying to Debug an MTS Java object, including Dr. Watson errors or IDE crashes.


  • NoClassDefFoundError on com.ms.mtx.AppServer when trying to use the MTS Context Java class.


  • Remote attaching to Mtx.exe hosting Java may result in server busy dialog box.


Windows NT 4.0 SP4 also ships the latest version of MTS and its Java COM Wrapper classes.

Information on the availability of Windows NT 4.0 SP4 will be published on the Windows Downloads page.

© Microsoft Corporation 1999, All Rights Reserved.
Contributions by Steve Horne, Microsoft Corporation



Additional query words:

Keywords : kbdocfix kbDebug kbJIT kbMTS kbNTOS400 kbVJ600 kbNTOS400sp4fix kbGrpJava kbVJ600FAQ
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type :


Last Reviewed: November 10, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.