Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Failed to run task sequence (0x80004005)

  • Thread starter Thread starter ronvanloo
  • Start date Start date
  • Replies Replies 3
  • Views Views 16K
Status
Not open for further replies.

ronvanloo

Member
Messages
7
Reaction score
1
Points
3
Hello

Since last Friday we can't provide any image to our devices anymore.
The error occurs when I do a PXE boot and when I select the desired task sequence I see a screen (for 30 seconds) Resolving selected taks sequence dependencies.....
After this I got the error screen.

All tasks sequences have this error. I also created a new one with no actions in it, same error.
Error 0x80004005 can occur on many errors as I can find on the internet.
I also checked the certificate and there is 1 certificate blocked but this one already expired in 2014.
I examined the smsts.log and this is the error:
Failed to download policy {d4b89af7-b174-45bc-ad9b-c457ad2a22d9} (Code 0x80004005).
Before this error I first got 5 messages: BOM not found on policy reply

Is here someone who had an idea?

Regards,

Ron
 
Hereby I send you the log file.
I also pressed F8 when the error occurs. When I do a ipconfig I get the correct IP settings.
There is also a NetSetp.log file on the device and in this file I can see the MININT..... name and that this is attacht to the workgroup: WORKGROUP

Regards,
Ron
 

Attachments

I solved the problem.
I deleted the policy that is mentioned in the SMSTS.LOG that could not been found. The policy can be found in 3 tables of the MSSQL database:
  • policy
  • policyassignment
  • deppolicyassignment

Before this action I first made a snapshot of the SCCM VMware server in case of.....
After I deleted the policy i tried a new installation of a machine and the TS reported no error. After a while the machine was ready and there were no errors in the logging.
The only strange thing is that the deleted policy returned in all 3 tables. But we installed a couple of machines after I noticed this but the TS starts and ends without any problem.
I think this is a case for Mulder and Scully because I don't have a clue what was causing this problem.
Thanks for all your relpies and ideas.
Regards,
Ron
 
Status
Not open for further replies.

Forum statistics

Threads
7,165
Messages
27,965
Members
18,264
Latest member
markmumford

Trending content

Back
Top