FIX: You may receive a "The memory could not be 'read'" error message, or a COM+ Interop type mismatch exception error occurs when you run .NET Framework applications that use the AS/400 Data Queue ActiveX control (904708)


The information in this article applies to:

  • Microsoft Host Integration Server 2004

SYMPTOMS

When you run Microsoft .NET Framework applications that use the AS/400 Data Queue ActiveX control (Mseigdq.dll) to read from and to write to IBM iSeries (AS/400) data queues, you may experience one or more of the following problems:
  • You receive application error messages that are similar to the following:
    ApplicationName - Application Error
    The instruction at "memory address" referenced memory at "0x00000000". The memory could not be "read".

    Click on OK to terminate the program
    Click on CANCEL to debug the program
  • A Microsoft COM+ Interop type mismatch exception occurs when you try to process a record that is returned when the application calls the DataQueue.GetQueueItem method. This exception only occurs when the application uses managed code. This exception does not occur if the application uses Microsoft Visual Basic 6. The error message that you receive may be similar to the following:
    System.Runtype.InteropServices.SafeArrayTypeMismatchException

CAUSE

You receive a "The memory could not be 'read'" error message because the AS/400 Data Queue ActiveX control tries to read an invalid memory location.

The COM+ Interop type mismatch exception occurs because the AS/400 Data Queue ActiveX control returns record data as a safe array of VT_UI1 data. This data is not Automation compatible. This behavior causes the COM+ Interop layer to return the type mismatch exception because the COM Interop layer does not know how to marshal the VT_UI1 data.

RESOLUTION

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 Host Integration Server 2004 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:

http://support.microsoft.com/contactus/?ws=support

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 file attributes) 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
   ----------------------------------------------------
   29-Sep-2005  19:39  6.0.1988.0  121,344  Mseigdq.dll
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

This hotfix updates the AS/400 Data Queue ActiveX control to fix the problem that causes application error messages when invalid memory is accessed.

This hotfix does not fix the problem in which a COM+ Interop type mismatch exception occurs. However, you can resolve problem by using the .NET Framework 2.0 on any computer that is running a .NET Framework application that calls the AS/400 Data Queue ActiveX control. The .NET Framework 2.0 can correctly marshal unsigned byte arrays such as VT_UI1 data types. Therefore, the type mismatch exception does not occur.
Modification Type:MinorLast Reviewed:7/25/2006
Keywords:kbHotfixServer kbQFE kbHIS2004 kbfix kbbug kbpubtypekc KB904708 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.