Application Error Printing to a Banyan Vines Network Printer (184748)

SYMPTOMS

When you try to print from Internet Explorer version 4.01 to a Banyan Vines network printer, you may receive the following error message:

Microsoft Windows NT 4.0

Dr. Watson for Windows NT
An application error has occurred and an application error log is being generated.
explorer.exe Exception access violation (0x00000005), Address:
0x5f60169c.

Microsoft Windows 95

iexplore.exe - Application Error
The instruction at "0x5f60169c" referenced memory at "0xfffc1e7d".
The memory could not be "read".
Click on OK to terminate the application
Click on CANCEL to debug the application

RESOLUTION

To work around this problem, the Banyan Vines administrator must assign a Banyan Vines print queue in your Banyan Vines user profile to an available LPT port, and then install a local printer on your Windows NT client workstation that uses the same LPT port that is assigned in the Banyan Vines user profile. For information about how to do this, refer to the Banyan Vines documentation for your software revision.

This issue is resolved by the following updated file:

Internet Explorer for Windows NT 4.0

   Mshtml.dll  version 4.72.3002.2  dated 2/3/98   2,399,232 bytes

Internet Explorer for Windows 95

   Mshtml.dll  version 4.72.3002.2  dated 2/3/98   2,388,480 bytes

NOTE: After you apply this fix, printing functionality should be restored, but when you quit Internet Explorer, you may receive a type "505" error message for each time you sent a print job to your printer. This error message does not impact the functionality of your printing, and can be ignored. Note that this error is caused by an issue with the Banyan Vines software, and is therefore not an issue that Microsoft supports.

STATUS

Microsoft has confirmed this to be a problem in Internet Explorer version 4.01. An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.