Sign in
Microsoft.com
 
System Center Configuration Manager TechCenter
 
 
 
System Center Configuration Manager TechCenter > System Center Configuration Manager Forums > Configuration Manager General > Critical Warnings being logged after deleting a collection
Ask a questionAsk a question
Search Forums:
 

AnswerCritical Warnings being logged after deleting a collection

  • Thursday, November 05, 2009 3:23 PMStevyb69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi All,
    I deleted a collection today, nothing that I don't usually do, but since then I'm getting inundated with the following messages being logged against the SMS_COLLECTION_EVALUATOR component:

    Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][ODBC SQL Server Driver][SQL Server]The DELETE statement conflicted with the REFERENCE constraint "Update_DeploymentSummary_Collections_FK". The conflict occurred in database "SCCM_SC1", table "dbo.Update_DeploymentSummary", column

    Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.

    The collection did have an updates deployment assigned to it, but was moved to a different collection before I deleted it.

    Any ideas anyone?

    Cheers,
    SB
    Closest I can find to this error is here:
    http://social.technet.microsoft.com/forums/en-US/configmgrgeneral/thread/fe6d305b-284f-45a0-96ea-c1fa9e36d76d
    http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/c73e6dd3-ebc4-4da7-9267-6635fc1996f7/

    http://www.microsoft.com/technet/security/Bulletin/MS08-067.mspx If you don't ever patch anything, for god sake make sure this patch is on.......
     

Answers

  • Friday, November 06, 2009 3:21 PMStevyb69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Now for the fun bit...... it's fixed itself.

    No idea why, it logged errors every 30 mins over night until 6:31 this morning, then it's logged nothing since!

    Self healing SCCM, that's what I like to see :)
    http://www.microsoft.com/technet/security/Bulletin/MS08-067.mspx If you don't ever patch anything, for god sake make sure this patch is on.......
    • Marked As Answer byStevyb69 Friday, November 06, 2009 3:21 PM
    •  
     

All Replies

  • Friday, November 06, 2009 3:21 PMStevyb69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Now for the fun bit...... it's fixed itself.

    No idea why, it logged errors every 30 mins over night until 6:31 this morning, then it's logged nothing since!

    Self healing SCCM, that's what I like to see :)
    http://www.microsoft.com/technet/security/Bulletin/MS08-067.mspx If you don't ever patch anything, for god sake make sure this patch is on.......
    • Marked As Answer byStevyb69 Friday, November 06, 2009 3:21 PM
    •