XADM: Event Log Reports 1025 (EcGetRestriction)

Last reviewed: March 16, 1998
Article ID: Q175597
The information in this article applies to:
  • Microsoft Exchange Server, versions 4.0, 5.0, 5.5

SYMPTOMS

The information store may report the following error in the event log:

   Event ID: 1025
   Source: MExchangeIS Private
   Type: Warning
   Category: None

   Description:
   An error occurred.
   Function name or description of problem: EcGetRestriction
   Error: 1402

CAUSE

EcGetRestriction is a function that continually performs "self checks" and makes additional calls to a number of sub-functions. If the self-check function or one of these sub-functions returns an invalid or "false" answer, EcGetRestriction will generate the event 1025. This is usually caused by an invalid pointer in the information store.

Because the EcGetRestriction function continuously performs these self checks, the 1025 may appear frequently in the event log.

WORKAROUND

The misdirected pointer needs to be realigned within the information store. It can be repaired by performing an ISINTEG -FIX -PRI, ISINTEG -FIX -PUB, or both.

For more information about running ISINTEG on Exchange Server version 5.5, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: 177885
   TITLE: XADM: ISINTEG -FIX With -PUB or -PRI No Longer Works in 5.5
Keywords          : XADM
Version           : winnt:4.0,5.0
Platform          : winnt
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: March 16, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.