Isolate the cause of dataldr error "attempt to update non-existent row. Invalid command: exec pWorkstationStatus_DATA"
ConfigMgr SP1 with R2... all XP SP2 and SP3 advanced clients. We're collecting a few custom classes, and while monitoring the dataldr.log we're regularly seeing "rollbacks" with the error "attempt to update non-existent row" so I'm interested in narrowing the cause for this error.
In that case a given delta gets rejected and moved to badmifs folder, we inspect the serial number (Last Report Version) and the Last Hardware Scan (date/time) in the badmif and compare to the client record that’s in the database. 90% of the time, the last report version (serial number) and the last hardware scan date/time of the badmif are in sequence and logically follows what’s in the database (in other words, it seems that no inventory was missed).The reason I ask is that *most* of the rejected delta MIFs have little more than Workstation_Status getting updated. The client is clearly in the database and an active client. Anyone have an idea on what’s causing the reject/rollback in this scenario? thank you, Al
