FIX: You receive a "System.IO.IOException, 'The handle is invalid'" error message when you use both Visual J# .NET and Visual C# .NET to access the stdout output stream in the same process

This article has been archived. It is offered "as is" and will no longer be updated.
If you unload a Microsoft Visual J# .NET Application Domain (AppDomain) in a Microsoft Visual C# .NET process, the stdout output stream that is associated with the Console object is closed. After this point, if you try to use the Console object from the Visual C# .NET code, you receive the following error message:
System.IO.IOException, "The handle is invalid"
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Visual Studio .NET 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version       Size       File name   ---------------------------------------------------------   09-Oct-2003  20:52  1.1.4322.956  3,743,744  Vjslib.dll   09-Oct-2003  09:13  1.1.4322.956    266,240  Vjsnativ.dll   09-Oct-2003  20:52  1.1.4322.956  3,399,680  Vjswfc.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Steps to reproduce the behavior

  1. In Visual Studio .NET 2003, create a project that contains a Visual C# .NET console program and a Visual J# .NET assembly class library.
  2. Add the following code to the Visual C# .NET console program:
    using System;using JSOut;public class OutputCrash{		public static void Main()	{	Console.WriteLine("Before entering new domain.");	AppDomainSetup domainSetup = new AppDomainSetup();	domainSetup.LoaderOptimization = System.LoaderOptimization.SingleDomain;	AppDomain domain = AppDomain.CreateDomain("tempDomain", null, domainSetup);	// This call generates an AppDomain for the Visual J# output.	domain.DoCallBack(new CrossAppDomainDelegate(JSharpOut.JSharp));	AppDomain.Unload(domain); 	// You receive the System.IO.IOException error message when you write to the stdout 	// because the stdout handle is no longer valid. This failure occurs only after	// the AppDomain that has the Visual J# delegate unloads.	Console.WriteLine("After leaving new domain.");		}}
  3. Add the following code to the Visual J# .NET assembly class library:
    public class JSharpOut { 	public static void JSharp() { 	long l = java.lang.System.identityHashCode(new Object()); 	} } 
  4. Compile and then run the project. The System.IO.IOException error occurs on the last statement:
    Console.WriteLine("After leaving new domain.");

Article ID: 830297 - Last Review: 12/08/2015 05:04:02 - Revision: 1.5

Microsoft Visual J# .NET 2003 Standard Edition, Microsoft .NET Framework 1.1

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbvsnet2003presp1fix kbvsnet2003sp1fix kbqfe kbfix kbbug KB830297