XADM: IS Stops in _mapises\notifysrv.cxx During Shutdown

 Last reviewed: February 12, 1998
Article ID: Q179013
The information in this article applies to:
  • Microsoft Exchange Server version 5.0

SYMPTOMS

The Microsoft Exchange Server Information Store crashes during shutdown. The call stack is similar to the following: 

   FramePtr  RetAddr   Param1   Param2   Param3   Function Name
   0179ffa0  0046d831  00000000 0110f680 0179ffec
   STORE!ScanForOutstandingNotifications+0xe3
   (FPO: [ebp 00000005] [0,2,4]) [ notifsrv.cxx @ 713 ]

CAUSE

The Microsoft Information Store has freed the shared block of memory and set the global pointer for it to NULL (allocated for use with the NT Performance Monitor data) before this notification thread has been shutdown. Once this thread attempts to access this block of memory using the NULL pointer, an access violation occurs.

RESOLUTION

To resolve this problem:

  • Release the memory and free the pointer only after the notification thread has completely shutdown.

NOTE: Service Pack 1 must be applied to Microsoft Exchange Server 5.0 prior to applying this fix.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server, version 5.0.

This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

Additional query words:
Keywords : kbbug5.00 kbfix5.00.sp2 XADM kbusage
Version : 5.0
Issue type : kbbug
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.