SMS: Error "Violation of PRIMARY KEY constraint" When Status Manager Writes To Database (215059)
The information in this article applies to:
- Microsoft Systems Management Server 1.2
- Microsoft Systems Management Server 2.0
This article was previously published under Q215059 SYMPTOMS
The following errors may appear in the Statmgr.log:
SQL Err #10007> General SQL Server error: Check messages from the SQL Server.
SQL Msg #2627> Violation of PRIMARY KEY constraint 'StatusMessages_PK'. Cannot insert duplicate key in object 'StatusMessages'.
SQL Msg #3621> The statement has been terminated.
You may also receive the error on constraint 'StatusMessageAttributes_PK'.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Systems Management Server 2.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
236325 SMS: How to Obtain the Latest Systems Management Server 2.0 Service Pack
WORKAROUND
To work around this problem, perform the following steps: - Stop the SMS_STATUS_MANAGER using the Systems Management Server Service Manager.
- Delete the oldest SQL file in the \SMS\Inboxes\statmgr.box\retry directory.
- Restart the SMS_STATUS_MANAGER using the Systems Management Server Service Manager.
- Repeat steps 1-3 until the Statmgr.log file no longer reports the SQL errors.
NOTE: Performing the workaround above may result in the loss of status messages. If losing currently queued status messages is acceptable, then you can simply delete all of the SQL files in step 2 and skip step 4.
STATUSMicrosoft has confirmed that this is a problem in Systems Management Server 2.0. This problem was first corrected in Systems Management Server 2.0 Service Pack Service Pack 1.
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbBug kbDatabase kbfix kbsms200fix kbStatSum KB215059 |
|---|
|