You are currently offline, waiting for your internet to reconnect

Your browser is out-of-date

You need to update your browser to use the site.

Update to the latest version of Internet Explorer

A "0x0000008E" Stop error occurs when you set the message storage limit for a Message Queuing queue to be larger than 4 GB in a 32-bit version of Windows Server 2003

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.
Symptoms
Consider the following scenario:
  • You run Message Queuing (also known as MSMQ) 3.0 on a computer that is running a 32-bit version of Windows Server 2003.
  • You set the message storage limit for a queue to be larger than 4 gigabytes (GB). For example, you set the message storage limit to 16 GB.
In this scenario, you receive a Stop error message that resembles the following:
STOP 0x0000008E ( parameter1 , parameter2 , parameter3 , parameter4 )
KERNEL_MODE_EXCEPTION_NOT_HANDLED
Notes
  • The parameters in this Stop error message may vary, depending on the configuration of the computer.
  • Not all "0x0000008E" Stop error messages are caused by this problem.
Cause
This issue occurs because an access violation may occur if the following conditions are true:
  • The memory storage limit is set to a high value.
  • The Message Queuing queue contains lots of messages.
Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2003 Service Pack 2 (SP2). For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2003 file information notes
  • In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2003
File nameFile versionFile sizeDateTimePlatform
Mqac.sys5.2.2008.4819102,40017-Jan-201112:58x86
Update.exe6.3.4.1743,21607-Jul-201015:19x86
Update.verNot applicable10817-Jan-201112:51Not applicable
Workaround
To work around this issue, set the message storage limit to 4 GB or to less than 4 GB.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about Message Queuing message storage, visit the following Microsoft website: For more information about how to set the message storage size for queues, visit the following Microsoft website: For more information about software update terminology, 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
Properties

Article ID: 2494629 - Last Review: 10/09/2014 12:16:00 - Revision: 3.0

  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Message Queuing 3.0
  • kbmdd kbqfe kbhotfixserver kbfix kbexpertiseinter kbsurveynew kbexpertiseadvanced KB2494629
Feedback