Object Replication errors after a ConfigMgr 2012 R2 SP1 upgrade.
After a ConfigMgr 2012 R2 SP1 upgrade, I experienced a lot of Object Replication errors in the SMS_Object_Replication_Manager.
These errors looked like this:
Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The DELETE statement conflicted with the REFERENCE constraint "CI_CurrentRuleDetail_CIID_FK". The conflict occurred in database "CM_***", table "dbo.CI_CurrentRuleDetail", column 'Setting_
Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.
After a Little Google'ing, I found that Henk Hoogendoorn had the same problem, and he had described how he solved this.
Look here:
http://henkhoogendoorn.blogspot.dk/2015/06/object-replication-errors-after.html
01 July 2015
Client version '5.00.8239.1000' is not compatible with the site 'xxx' version '5.00.7958.1000'.
I had just updated my SCCM environment (SCCM 2012 R2 CU4) with SP1 when I stumbled over this error,
making my clients unable to upgrade
ccmsetup.log:
Download Update: Connecting to the server.
Successfully completed BITS download for client deployment files.
Successfully downloaded client files via BITS.
Validated file 'C:\WINDOWS\ccmsetup\CLP1030.msp' hash DCFA14C76F0C1E8FFC487C791F990EE464E79590BF93FA1657F72A1BB7956A7F'
Retrieved client version '5.00.8239.1000' and minimum assignable site version '5.00.8200.1000' from client package
Checking compatibility of site version '5.00.7958.1000', expect newer than '5.00.8200.1000'
Client version '5.00.8239.1000' is not compatible with the site 'xxx' version '5.00.7958.1000'. Client version '5.00.8239.1000' is not compatible with the site 'PS1' version '5.00.7958.1000'. Params to send '5.0.8239.1001 Deployment Error: 0x87d0029d, Client version '5.00.8239.1000' is not compatible with the site 'xxx' version '5.00.7958.1000'.
This was causing grey hair, until I had a little (great) help:
Is the management updated in the system management container?
Open with adsiedit and check the mp version on the registration.
This was not updated.
Making SCCM update this, solved the problem.
ccmsetup.log:
Download Update: Connecting to the server.
Successfully completed BITS download for client deployment files.
Successfully downloaded client files via BITS.
Validated file 'C:\WINDOWS\ccmsetup\CLP1030.msp' hash DCFA14C76F0C1E8FFC487C791F990EE464E79590BF93FA1657F72A1BB7956A7F'
Retrieved client version '5.00.8239.1000' and minimum assignable site version '5.00.8200.1000' from client package
Checking compatibility of site version '5.00.7958.1000', expect newer than '5.00.8200.1000'
Client version '5.00.8239.1000' is not compatible with the site 'xxx' version '5.00.7958.1000'. Client version '5.00.8239.1000' is not compatible with the site 'PS1' version '5.00.7958.1000'. Params to send '5.0.8239.1001 Deployment Error: 0x87d0029d, Client version '5.00.8239.1000' is not compatible with the site 'xxx' version '5.00.7958.1000'.
This was causing grey hair, until I had a little (great) help:
Is the management updated in the system management container?
Open with adsiedit and check the mp version on the registration.
This was not updated.
Making SCCM update this, solved the problem.
Subscribe to:
Posts (Atom)