SMS_Inventory_Data_Loader error

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi all,

I recently edited the sms_def.mof file to include hardware information from
our clients. Using mofcomp.exe the mof file checked fine and was parsed fine
by a test client. However, I am now getting an error in the Component Status:
"Severity Type Site code Date / Time System Component Message ID Description
Error Milestone BRQ 4/11/2008 11:31:11
AM USDBRQSCA1MS004 SMS_INVENTORY_DATA_LOADER 620 Microsoft SQL Server
reported SQL message 547, severity 16: [23000][547][Microsoft][ODBC SQL
Server Driver][SQL Server]DELETE statement conflicted with TABLE REFERENCE
constraint 'DataItemContext_2_FK'. The conflict occurred in database
'SMS_BRQ', table 'DataItemContext'. Please refer to your SMS
documentation, SQL documentation, or the Microsoft Knowledge Base for further
troubleshooting information."

I searched the Knowledge Base to no avail. Does anyone have idea how to
resolve this?

--
Thank you in advance,
Eddie
.

Relevant Pages

  • Re: SMS_Inventory_Data_Loader error
    ... I recently edited the sms_def.moffile to include hardware information from ... by a test client. ... documentation, SQL documentation, or the Microsoft Knowledge Base for further ... I searched the Knowledge Base to no avail. ...
    (microsoft.public.sms.inventory)
  • RE: Norton Antivirus Client
    ... was copy the extracted defs into the incoming dir on the clients side. ... repointing the clients update path, but requires reg hacks on every client. ... Subject: Norton Antivirus Client ... Simple question I cannot confirm on Symantec's "knowledge base". ...
    (Security-Basics)
  • Re: Filemaker 9 Server, 2003 Server Problem
    ... I downloaded and installed the 9.0v2 and now no clients are listed in the client view, but clients are logged in to the server. ... Sometimes restarting the server fixes it but other times I have to stop the Service and restart the service. ... I have search their Knowledge base and do not find anything in regards to this issue. ...
    (comp.databases.filemaker)