CLIENT CONFIG REQUESTS CCR SQL ERROR

Question

Hi,
Since 1 months now, our SMS_Client _Config_Manager is in critical state. This is caused by a lot of errors (100/day):
Microsoft SQL Server reported SQL message 8672, severity 16: [42000][8672][Microsoft][SQL Server Native Client 11.0][SQL Server]The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than
one source row. A MERGE statement cannot UPDATE/DELETE the
This error occurs when the query sp_CP_checkNewAssignedMachine is executed. (See log below)
We migrated all our site from 2007 to 2012 beginning of the year. During migration, we enabled Client Push installation and from time to time, the nodes with "Client No" where deleted from SCCM to be rediscoverd by AD discovery. Now we have
still around 1000 clients that for some or other reason cannot be installed.
I could also see that in the ccrretry.box, there are around 1000 (EMPTY) files to be processed.
CCM.log
Execute query exec [sp_CP_SetPushRequestMachineStatus] 16787434, 1 SMS_CLIENT_CONFIG_MANAGER 2/04/2014 11:20:12 6720 (0x1A40)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 2/04/2014 11:20:12 6720 (0x1A40)
Getting a new request from queue "Retry" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 2/04/2014 11:20:12 6720 (0x1A40)
Found CCR "16787435.ccr" in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 2/04/2014 11:20:12 6720 (0x1A40)
*** exec [sp_CP_CheckNewAssignedMachine] N'P01', 1 SMS_CLIENT_CONFIG_MANAGER 2/04/2014 11:20:12 3584 (0x0E00)
*** [42000][8672][Microsoft][SQL Server Native Client 11.0][SQL Server]The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row. A MERGE statement cannot UPDATE/DELETE the
same row of the target table multiple times. Refine the ON clause to ensure a target row matches at most one source row, or use the GROUP BY clause to group the source rows. : sp_CP_CheckNewAssignedMachine SMS_CLIENT_CONFIG_MANAGER 2/04/2014 11:20:12 3584
(0x0E00)
CCCRT::RunSQLStoredProc - Failed to execute SQL cmd exec [sp_CP_CheckNewAssignedMachine] N'P01', 1 SMS_CLIENT_CONFIG_MANAGER 2/04/2014 11:20:12 3584 (0x0E00)
CCRQueueRequest::GetRequestFromQueue - Failed to execute SQL cmd sp_CP_CheckNewAssignedMachine SMS_CLIENT_CONFIG_MANAGER 2/04/2014 11:20:12 3584 (0x0E00)
Does someone know how to solve this? Are there duplicate records?
Is enabling client push best practice when migration is done? On new machines, the SCCM client is installed via OSD.
Thanks,
WiM

Answer 1

I get the above issue and the one below at a client site; the error started with the error below then changed to the one reported above and back to the one below. Everything is working as it should but the issues started when one of the admins at the data-centre
incorrectly applied a gpo which affected a number of service accounts (sccm inclusive) and they expired....hence reporting in sccm got broke as well as this error in the ccm.log file appeared.
Remote client install still works but I believe this error affects new client discovered by sccm, so in other words devices discovered by sccm do not get the client installed automatically....but if all access and permissions are in place...pushing out the
client to the new discovered system works, it just not done automatically, which kinda defeats one the reasons for using sccm.
I have searched the breadth of the tinternet and I can only find two technet reference to the same error  - one says to edit the stored procedure on the sql server which I don't think should be done... Like Jason said and I concur....its bad joo joos.
The second suggestion, said you should select all the options in the Client Push Installation properties, I have tried this but hasn't solved the problem.
I am planning to upgrade the site to the R2 CU3 before the end of the year but I would like to resolve this error before the upgrade.
The site is currently sccm 2012 sp1 
Any idea?> Resolution? sil vous plait!
Merci