Alerter Aborts After Deadlocking with Another Process

Last reviewed: April 24, 1997
Article ID: Q153609

The information in this article applies to:

Microsoft Systems Management Server versions 1.0 and 1.1

SYMPTOMS

On a busy site, the Systems Management Server Alerter may become deadlocked with another Systems Management Server process using the Systems Management Server database. This causes the Alerter to abort its cycle and pending alerts will not be executed.

Alerter.log displays error messages similar to the following:

   >>Msg>> Your server command (process id 15) was deadlocked with another
   process and has been chosen as deadlock victim. Re-run your command~~
   $$<SMS_ALERTER>...

RESOLUTION

To correct this problem, upgrade to Systems Management Server 1.2.

STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 1.1. This problem has been corrected in Systems Management Server version 1.2.

Additional query words: prodsms SQL
Keywords : kbbug1.10 kbfix1.20 kbnetwork smsdatabase smsdataloader smsgeneral
Version : 1.0 1.1
Platform : WINDOWS

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: April 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.