SCCM Task Sequence failed due to package associated to the task sequence cannot be found

sccm

If you get an issue when trying to load a task sequence and you get the message that a package associated to the task sequence cannot be found, even when it looks like all packages are fully distributed, then you need to check out the SMSTSLog.log file that is on the machine that you are trying to deploy the task sequence to.

To do this, you must have the command prompt via F8 turned on.

Go into a command prompt by pressing F8 and then go in the root of your X: drive. From here type:

  • Cd %temp% and press enter
  • Then go into the SMSTSLog folder by typing;
  • Cd SMSTSLog and press enter

You can then see the SMSTSLog.log file, however, you want to be able to open it up in trace32.exe so that you can view the errors. For me, the best way is to map a network drive to a share, then copy the file to that share on then open an another machine that has trace32.exe installed, from here, you should be able to find the package ID that has the problem, update the distribution of this package and then your task sequence should run without issues.

Newsletter

If you want to be notified when we post more quality guides like this one, sign up to our newsletter and you will receive an email when a new post is live.

Join 92 other subscribers

No need to worry, we will not be filling your inbox with spam and you can unsubscribe anytime you like.

About A.J. Armstrong

Founder of TechyGeeksHome and Head Editor for over eight years! IT expert in multiple areas for over 20 years. Sharing experience and knowledge whenever possible! Making IT Happen.

View all posts by A.J. Armstrong

Leave us a message...

This site uses Akismet to reduce spam. Learn how your comment data is processed.