Hi Guys , back with a new blog on how to get your OSD rocking . Recently i had a request from one of my clients that Task sequences are failing to run and the moment we select any task sequence it fails with the following error :

Now looking at the error and logically thinking we see that failure is happening while downloading a certain policy . The issue appears to have been caused by problematic references to the policy in the DepPolicyAssignment and PolicyAssignment tables of the site database. So we need to find the culprit policy. We can run few SQL queries to get the data.
Run the following query to find PADBIDs related to the policy in question
select * from PolicyAssignment where PolicyID like ‘%DDA01EA1-098A-42CB-8EA7-C3A7E99D714E%’
You will get a PADBID information as example number : ‘102488517’
Then we run the following query to delete the above PADBID:
delete from PolicyAssignment where PADBID = 102488517
When we run the delete command we get the following error stating that there is a conflict in the database and we cannot delete the policy as of now.
DELETE statement conflicted with the REFERENCE constraint “DepPolicyAssignment_1_FK”. The conflict occurred in database “CM_XYZ”, table “dbo.DepPolicyAssignment”, column ‘PADBID’
Please run the following queries to check for the same policy and PADBID in table DepPolicyAssignment:
select * from DepPolicyAssignment where PolicyID like ‘%DDA01EA1-098A-42CB-8EA7-C3A7E99D714E%’
select * from DepPolicyAssignment where PADBID = ‘102488517’
You should find the PADBID related to the policy in the DepPolicyAssignment table, and then run the following queries to delete the PADBID from the DepPolicyAssignment and PolicyAssignment tables:
delete from DepPolicyAssignment where PADBID = 102488517
delete from PolicyAssignment where PADBID = 102488517
Then we run the following queries to confirm that the PADBIDs have been removed:
select * from PolicyAssignment where PolicyID like ‘%DDA01EA1-098A-42CB-8EA7-C3A7E99D714E%’
select * from DepPolicyAssignment where PolicyID like ‘%DDA01EA1-098A-42CB-8EA7-C3A7E99D714E%’
We then test the task sequence again and it runs without any issue. I hope it will help you fix the issue going further if you come across any such problem.
This was very helpful, thanks for taking the time to post.
LikeLiked by 1 person
Thanks a lot Matt
LikeLike
Hi And thanx for posting this. You saved my SCCM 🙂
In our case ( sccm 2111 + hotfix from 11-1-2022 ) we had a double entry of the troublesome policy; one was version 1 , the 2nd was version 20
I deleted the version 1 and all was fine again. I couldn’t have figured this one out without this post; so thanx again.
LikeLike