SQL conflict delting collection
I deleted a couple of collections from console this morning. Since doing this getting error message back from 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 "SMS_001", table "dbo.Update_DeploymentSummary", column Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. From colleval.log *** [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 "SMS_001", table "dbo.Update_DeploymentSummary", column 'CollectionID'. CCollectionSource_SQL::DeleteCollection - error in sql cmd delete Collections from Collections where CollectionID = 171 I have seen a couple of threads relating to similar error messages with Asset intellligence but nothing concrete Any thoughtsIan Burnell, London (UK)
May 31st, 2011 5:53am

The only way to solve that would be modifying the database directly as far as I can tell. That's unsupported and might lead to even more severe issues. So the best way to solve that would be calling CSS.Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
May 31st, 2011 6:15am

Well strange one this. I had setup a patch collection as a folder with sub-collections underneath, then created patch deployment to the root folder and sub-collections. I decided to clean this up so deleted one of the collections underneath the "folder" collection. No problem. Then deleted the folder collection iteself and saw the deployment advertised to it, so I amended the deployments to point to a different collection. After deleting the folder collection (successfully from the console) I then got the above error. So simply deleted the deployment completely and then saw the collection removed ok from the SQL table in dataldr.log so all ok now.Ian Burnell, London (UK)
May 31st, 2011 8:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics