Greetings all,

I have two Primary sites that I've noticed are reporting the following error against the SMS_POLICY_PROVIDER component.

All sites running ConfigMgr 2012 R2, Windows Server 2012, and SQL 2012 SP2

Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The INSERT statement conflicted with the FOREIGN KEY constraint "DepPolicyAssignment_1_FK". The conflict occurred in database "CM_X00", table "dbo.PolicyAssignment", column 'PADBID'.

The policypv.log is also reporting various errors "failed to create policy and policy assignment based on pacakge..." and there a couple of hundred .CXX and .RT13 and .RT14 files in the policypv.box, some seem to be a few months old.

There are 10 other Primaries that are all fine and showing no issues.

Database replication is showing all OK from the CAS, so this looks to be very much a issue specific to these two sites.

A search for similar issues only seems to find a few technet forum posts with an answer of "It's all fixed now" and no other detail which really isn't very helpful :(

Does anyone have some suggestions on how to resolve this, or is this going to need a call to Microsoft?

Thanks,

Scott.

• Edited by Scott Williams - IP1 Sunday, May 17, 2015 11:55 PM

I haven't seen that blog post, but it looks like the same thing. I'll see if it helps me identify a fix. Thanks for the pointer.

There are a dozen or so packages that seem to be appearig in the logs, so a call to MS might still be needed.

The fact this has also happened on only two of the Primaries makes me wonder what the initial cause was. I suspect it may be related to some network/server issues we had a while back that may have caused some sync or replication issues between sites.

Looking at our errors it does seem to be task sequence related, but the packages are not a boot images, just packages referenced in the TS. There are two different TS, and multiple different deployments for each one. It's happening on 2 of our 12 primary sites, so I'm thinking it is just a glitch at some point with file/database replication.

Both of the deployments have a name starting with an "_" though, but I don't know if that's supposed to mean something or just co-incidence?

Deleting the deployment is undesirable given the complications around how UEFI deployments work and the need to recreate a whole stack of other deployments.

It looks like it might need to be a call to Microsoft. Hopefully we can get away with doing something like copying a database table from another good server to resolve...