XADM: Access Violation Occurs in the System Attendant When You Run Mailbox Manager

Article translations Article translations
Article ID: 320263 - View products that this article applies to.
This article was previously published under Q320263
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

In Exchange 2000, the Mailbox Manager service runs as part of the Exchange 2000 System Attendant. If you run Mailbox Manager in an Exchange 2000 Active/Active cluster configuration, an access violation may occur in the System Attendant process (Mad.exe).

The stack dump file that is created by the access violation is similar to the following:
00 0f34cad0 77e8830e 0f34cb18 00000001 0f34cb18 KERNEL32!CompareStringW+0x100
01 0f34caf4 0043bbab 0f34cb18 00000002 00452344 KERNEL32!lstrcmpiW+0x1d
02 0f34cb00 00452344 00000002 00000000 0f34cbcc mad!CStr::strcmpi+0xd
03 0f34cb9c 004517a8 0d97365c 00000000 00401ee8 mad!CMBCleanConfig::FSelectCurrentPolicy+0x60
04 0f34cbb4 00451b31 0f34cbcc 0d956d38 0d984650 mad!CJanitorInfo::FSelectCleanPolicyGoverningMailbox+0x22
05 0f34cbf0 0044be80 0d984650 00000001 0d956d38 mad!CJanitorInfo::FSelectCleanPolicyGoverningMailbox+0x51
06 0f34f928 0044c28a 0d984650 0f34fc60 0f34fc50 mad!CMailboxCleanImpl::ScProcessRecipient+0x123
07 0f34fc84 0044c39f 00000000 0d96b330 0d956d38 mad!CMailboxCleanImpl::ScWalkUsersOnStore+0x1fd
08 0f34ff4c 0044c450 0d956d38 0d919960 00000000 mad!CMailboxCleanImpl::ScWalkStoresOnServer+0x107
09 0f34ff74 0041110e 0d919968 0d919960 00000001 mad!CMailboxCleanImpl::ScCleanMailboxes+0xa0
0a 0f34ff8c 004111c4 0d919960 0d919960 00000000 mad!CMBCleanTask::ScCleanMailboxes+0x7a
0b 0f34ffa0 0040f3e6 0017f248 0000000f 0040fb08 mad!CMBCleanTask::Work+0x3b
0c 0f34ffac 0040fb08 0000000f 77e8758a 0d919960 mad!CTimerTask::DwLoop+0x17
0d 0f34ffb4 77e8758a 0d919960 0017f248 0000000f mad!CTimerTask::DwLoopStatic+0x1d
0e 0f34fff0 0040faea 0d919960 00000000 00000000 KERNEL32!BaseThreadStart+0x52

CAUSE

When Mailbox Manager runs, it retrieves the string in the msExchPoliciesIncluded attribute on a user object. This string is usually two Globally Unique Identifiers (GUIDs) that are separated by a comma. If that comma is missing, the access violation that is described in the "Symptoms" section occurs.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: System Attendant

Collapse this tableExpand this table
File nameVersion
Mad.exe6.0.5770.80
Davex.dll6.0.5770.80
Dsaccess.exe6.0.5770.80
Dscmsg.dll6.0.5770.80
Excdo.dll6.0.5770.80
Exmgmt.exe6.0.5770.80
Exoledb.dll6.0.5770.80
Exprox.dll6.0.5770.80
Exres.dll6.0.5770.80
Exsp.dll6.0.5770.80
Exwmi.dll6.0.5770.80
Jcb.dll6.0.5770.80
Mdbmsg.dll6.0.5770.80
Mdbsz.dll6.0.5770.80
Phatcat.dll6.0.5770.80
Store.exe6.0.5770.80

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

Properties

Article ID: 320263 - Last Review: October 24, 2013 - Revision: 3.3
APPLIES TO
  • Microsoft Exchange 2000 Server Service Pack 2
  • Microsoft Exchange Server 2000 Service Pack 1
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB320263

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com