Microsoft KB Archive/311389

From BetaArchive Wiki
Knowledge Base


No Auditing Performed When Event 2044 Is Submitted to the Event Viewer

Article ID: 311389

Article Last Modified on 2/22/2007



APPLIES TO

  • Microsoft Message Queuing 2.0



This article was previously published under Q311389

SYMPTOMS

When you submit security auditing event 2044 to Event Viewer, the Queue Manager may not perform any auditing.

CAUSE

In certain situations, the Queue Manager attempts to initialize auditing in the context of the calling process, but the Queue Manager does not have sufficient permissions to do this.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical 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 fix should have the following file attributes or later:

   Date           Time   Version       Size    File name     
   -------------------------------------------------------
   Aug-09-2001   14:12   5.0.0.720   278,800   Mq1repl.dll
   May-29-2001   15:22   5.0.0.720    14,096   Mq1sync.exe
   May-29-2001   15:22   5.0.0.735    71,120   Mqac.sys
   Aug-09-2001   14:12   5.0.0.735   214,288   Mqads.dll
   May-29-2001   15:23   5.0.0.720    21,776   Mqbkup.exe
   Aug-09-2001   14:12   5.0.0.720    29,456   Mqcertui.dll
   Aug-09-2001   14:12   5.0.0.720    49,424   Mqclus.dll
   Aug-09-2001   14:12   5.0.0.720    29,968   Mqdbodbc.dll
   Aug-09-2001   14:12   5.0.0.720    75,536   Mqdscli.dll
   Aug-09-2001   14:12   5.0.0.735    41,744   Mqdssrv.dll
   May-29-2001   15:23   5.0.0.720    98,064   Mqmig.exe
   Aug-09-2001   14:12   5.0.0.720   263,952   Mqmigrat.dll
   Aug-09-2001   14:12   5.0.0.720   223,504   Mqoa.dll
   Aug-09-2001   14:12   5.0.0.720     7,952   Mqperf.dll
   Aug-09-2001   14:12   5.0.0.739   418,576   Mqqm.dll
   Aug-09-2001   14:12   5.0.0.720     8,464   Mqrperf.dll
   Aug-09-2001   14:12   5.0.0.738    91,920   Mqrt.dll
   Aug-09-2001   14:12   5.0.0.738    70,416   Mqsec.dll
   Aug-09-2001   14:12   5.0.0.720   400,144   Mqsnap.dll
   May-29-2001   15:23   5.0.0.720    14,096   Mqsvc.exe
   Aug-09-2001   14:12   5.0.0.720    24,336   Mqupgrd.dll
   Aug-09-2001   14:12   5.0.0.738   108,304   Mqutil.dll
   Aug-09-2001   14:12   5.0.0.720    64,784   Msmq.cpl
   Aug-09-2001   14:12   5.0.0.720   159,504   Msmqocm.dll
                



STATUS

Microsoft has confirmed that this is a problem in Microsoft Message Queuing 2.0.


Additional query words: MSMQ

Keywords: kbprb kbqfe KB311389