NEW The record for machine PCxxxxx (GUID:xxxxxxxxxx) was not found in the database.

[AhmedLS]

Hi,
i have this repeating error on statesys.log where it is complaining about a PC that doesnt exist anymore. the issue is that the user cloned his pc to a VM due to hardware error which ended by replacing his motherboard then restored the VM to his PC back.

the PCxxxxx is availabe on CM now but with different GUID. all is good but the database holds a record for the old PC and GUID

the questions is that. is it possible to delete the PC from SQL server ? or maybe there is a better solution.
I already tried deleting the current asset PCxxxxx from CM which showed up the next day with the new GUID.
regards to all

 

[Garth]

Deleting the pc from CM will delete the object from SQL at the next maintenance task cycle ~3 days.

If it gets a new GUID what is the problem? Does the VM still exist?

 

[AhmedLS]

Deleting the pc from CM will delete the object from SQL at the next maintenance task cycle ~3 days.

If it gets a new GUID what is the problem? Does the VM still exist?

there is a pc named pc20930 with GUID let say X1 but CM log (in red in the attched photo) shows another PC named PC20930 with GUID2

 

[Garth]

Delete the outdate state message.

 

[AhmedLS]

Delete the outdate state message.

it is not an outdated message. the error is popping up every30 minutes in the log

 

[Garth]

it is not an outdated message. the error is popping up every30 minutes in the log

Please read the log file, you will see that it is retrying an outdate status message.

 

[AhmedLS]

Please read the log file, you will see that it is retrying an outdate status message.

ended up deleteing the CM client form this asset and deleting it from SCCM. it showed up again and i pushed the cm client again to it. thats solved the issue and no more errors showed up