We just started to deploy SCCM into our infrastructure. Currently, I have my Central Site, 3 Primary Sites, and 2 secondary sites build, with no clients as of today. From within the ConfigMgr Console, under Site Status from the Central Console, I just noticed the same errors on all 3 of our primary servers. Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][ODBC SQL Server Driver][SQL Server]The UPDATE statement conflicted with the FOREIGN KEY constraint "LU_SoftwareCode_SoftwareList_FK1". The conflict occurred in database "SMS_SCH", table "dbo.LU_SoftwareList", column 'SoftwareID'. Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. We're just starting to build out our infrastructure and noticed these errors. Any idea where to start with this one? Chris

where you are seeing these error... i mean which log or any componets?Abhishek Joshi | Blog :- www.MicrosoftTechEd.com Personal site : www.AbhishekJoshi.com

I'm seeing these messages from the Site Status from my Central Server. I expand Site Database > I expand System Status, and I see that there are errors in the right hand pane. If I pick a server, then Show Messages > Error I see essentially the same messages on each server, with the exception of the database, which reflects each of the primary site DB's. I also just noticed that there were a few warnings, when I look at all of the warnings for one particular primary site, I see a number of warnings related to SMS_AI_KB_MANAGER I've copied all of the warnings from one server below. Still not sure where to look for this, however, these same 6 warnings appear on the other two primary servers, in addition to the 3 errors posted earlier. (again only the server names are different) Severity Type Site code Date / Time System Component Message ID Description Warning Milestone BUR 5/10/2010 9:43:14 AM CBSBURLSCCM01 SMS_AI_KB_MANAGER 7500 Asset Intelligence KB Manager encountered errors processing file K0IHXCG9.ARV. This file will be retried 100 times in subsequent processing cycles. Warning Milestone BUR 5/10/2010 9:43:14 AM CBSBURLSCCM01 SMS_AI_KB_MANAGER 619 Microsoft SQL Server reported SQL message 50000, severity 15: [42000][50000][Microsoft][ODBC SQL Server Driver][SQL Server]Fatal error inserting into LU_SoftwareCode: [Code]={518930be-7875-4547-b026-20b92f695781} : sp_UpsertSoftwareCatalog Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. Warning Milestone BUR 5/10/2010 9:43:12 AM CBSBURLSCCM01 SMS_AI_KB_MANAGER 7500 Asset Intelligence KB Manager encountered errors processing file 7CXI37QR.ARV. This file will be retried 100 times in subsequent processing cycles. Warning Milestone BUR 5/10/2010 9:43:12 AM CBSBURLSCCM01 SMS_AI_KB_MANAGER 619 Microsoft SQL Server reported SQL message 50000, severity 15: [42000][50000][Microsoft][ODBC SQL Server Driver][SQL Server]Fatal error inserting into LU_SoftwareCode: [Code]=kb975561 : sp_UpsertSoftwareCatalog Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information. Warning Milestone BUR 5/10/2010 9:43:12 AM CBSBURLSCCM01 SMS_AI_KB_MANAGER 7500 Asset Intelligence KB Manager encountered errors processing file 7B6KZ4PK.ARV. This file will be retried 100 times in subsequent processing cycles. Warning Milestone BUR 5/10/2010 9:43:12 AM CBSBURLSCCM01 SMS_AI_KB_MANAGER 619 Microsoft SQL Server reported SQL message 50000, severity 15: [42000][50000][Microsoft][ODBC SQL Server Driver][SQL Server]Fatal error inserting into LU_SoftwareCode: [Code]=shutdown : sp_UpsertSoftwareCatalog Please refer to your SMS documentation, SQL documentation, or the Microsoft Knowledge Base for further troubleshooting information.

have u gone through this post http://social.technet.microsoft.com/Forums/en-US/configmgrai/thread/c4d484ec-7263-4289-b5f7-d6142ac6f758#e71904c6-819d-4819-8efc-c56fef8f0e7bAbhishek Joshi | Blog :- www.MicrosoftTechEd.com Personal site : www.AbhishekJoshi.com

It looks like the errors I was experiencing was due to AI being enabled on the Central site, but not enabled on the primary site servers. Once AI was enabled on the Primary servers, the errors seemed to have gone a way.