SCCM Failed to Run Task Sequence Error

Hi,

Sccm was running fine for me, but I imported some drivers and after that whenever I run an image, it fails on the first step. i.e. "Failed to Run Task Sequence. This task sequence cannot be run because the program files for ScopeID_DE68FC0......./Application_BAFF61AEB............cannot be located on distribution point "

When I clicked on Distribution Point Configuration Status.....out from 3 sites....2 of them failed....one of them is showing an exclamation mark sign....is that related?

Thanks.
LVL 8
LeoAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
I guess it is related.

You can refresh the packages and try.
0
LeoAuthor Commented:
I did, but it didn't make any difference..
0
deanomacCommented:
I would try going to the System Status node and checking both Site Status and Component Status nodes for errors.  You will likely find the cause here.

Either way, removing the offending package/application from all distribution points, then re-adding may solve it.  You might also want to check that the source path for the app/package is still valid and can be navigated to by SCCM.
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

LeoAuthor Commented:
you mean i should remove all the drives I added?
0
LeoAuthor Commented:
SMS_Distribution_Manager is showing a status of Critical......
0
deanomacCommented:
Well that means that either it has errors (which is likely given the information you have provided already) or it has exceeded its quota of Warning messages.

Open up the log and limit it to a week of messages. Let it show all messages, as you may find more information on the issues if you display more than just the error messages.  Each message, if an error, should provide you with a couple of options to rectify it.
0
Mike TLeading EngineerCommented:
Hi,

You can look in the system status log for the distribution manager (right-click show all) and it will show all the errors related, which I suspect is the driver package. It will give the package ID, so then investigate those packages are indeed valid. You can go to the DP role within admin and go to the content tab and validate and redistribute them there.

To find the offending thing in the TS go to the task-sequence and pull the bottom window up to see more. Then right-click the column header and add Object ID. Look for ScopeID_DE68FC0......./Application_BAFF61AEB and see what it is in English! Validate and redistribute the package and test. If it still fails just delete that package - if it's the driver package you will still have the drivers so all's not lost. Then create a brand new package and distribute.

Another tool I found very useful is the Content Library Explorer which comes with the CM12 Toolkit.

Mike
0
LeoAuthor Commented:
Hi, mike, can you please clarify what you mean by DP role? (sorry i just started working on SCCM)
and now when i right click on task sequence and try to edit it, it gives an error, i cant edit any of the task sequences.....

also previously when i created task sequence and distributed the content to all unknown computers group (i believe that what we have to do) under completion tab, it shows 0%, why?
0
Mike TLeading EngineerCommented:
DP role is Distribution Point role in Admin "Servers and Site system roes" - the bottom window will list the roles you have installed. If you only have one server then it's simpler to find.

To do what I was talking about you just select a TS. so no need to edit it.

If you're beginning in CM I would not use unknown computers to prevent accidents. You never know who is visiting and might somehow hit F12...

As for being unable to edit any TS at all, that's a whole other story. If you create a new one from scratch can you edit that?

It's a good habit to export TS regularly - it's only a tiny XML file, but untick the boxes in the wizard. If you want to export everything, that's good too but will be much bigger and take a lot longer. It creates a zip file of all content.

Mike
0
LeoAuthor Commented:
ok, when i distribute content of a task sequence, which group should i target, also how can i make sure its viewable when i start to image it on a computer?
0
deanomacCommented:
DP Role = Distribution Point Role

Administration > Site Configuration > Servers and Site System Roles

Click on whichever server has the Distribution Point Role, right click the Distribution Point role from the lower window and select Properties.

I would suggest that one of the APPLICATIONS inside your task sequence is not distributed to one or more of the Distribution Points.  Check your Distribution Point logs.  Your first error message you posted stated exactly what the issue was, you need to check your apps are properly distributed, otherwise the device attempting to run the Task Sequence will not be able to locate a source for the applications you are attempting to deploy to it.
0
deanomacCommented:
Taking a step back a second. Perhaps the issue is not the un-distributed applications, but the inability of the selected Distribution Point to receive the associated files.

Have you checked the Site Status logs for the Distribution Point/s?
0
deanomacCommented:
I have had DPs run out of storage space previously and throw up such errors.  Might want to check that.
0
Mike TLeading EngineerCommented:
To target the task-sequence create a new collection. Set the Limiting collection to All desktops and server clients. Then add one machine (your test box) to the collection as a DIRECT member. Your machine will need to be known to CM before this will work but it's better as it reduces risk. CM is a powerful tool and it's a bit like operating a 30 ft crane - you can do a lot of damage.

Before adding the drivers, was your task-sequence quite simple - just apply OS and a few apps? I'm wondering what's gone wrong and if you have other packages that distributing too, or as Dean mentions your DP is struggling. And yes, disk space is always at risk of running out with lots of software installs. The final thing is avoid putting content on the C: drive. That's just a bad idea. If it's already there then leave it for now.
0
deanomacCommented:
Bit like learning to juggle, but instead of three balls, you have been given 45......and instead of balls, you have been given nuclear warheads.......and instead of juggling, you are being asked to throw them at the ground and hope they don't go off... ;-)

Welcome to the perilous world of OSD in SCCM! haha.
Here's some gentle bedtime reading on the above juggling... http://myitforum.com/myitforumwp/2012/08/06/sccm-task-sequence-blew-up-australias-commbank/
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
deanomacCommented:
On a side note - If you do deploy the OSD Task Sequence to unknown computers, ensure you have a PXE password set.  That would go most of the way to stopping unwanted devices being imaged with the corporate build.
0
LeoAuthor Commented:
Apologies for late reply, I have been trying to diagnose the issue,I created a new task sequence, but it kept showing compliance 0%, I guess there is something wrong with the distribution points in general, means yesterday I was trying to advertise a package for drivers, so I created a driver package advertised it to the site which required it, it failed. So no matter what I advertise the compliance status is 0 percent.
0
deanomacCommented:
The logs for the DPs will shed light on that issue, have you checked these yet?
0
LeoAuthor Commented:
there are few of them, which one is the right one to check?
0
LeoAuthor Commented:
smsdpmon.log this was last logged in 2014
0
deanomacCommented:
Monitoring > System Status > Site Status > (Look for Distribution Points then right click and show messages)
Monitoring > System Status > Component Status > (Look for SMS_DISTRIBUTION_MANAGER, right click and show messages)

These two are a good place to start your checks.
0
LeoAuthor Commented:
That does shows errors, but the steps I have taken to solve it, it doesn't work :-(
0
deanomacCommented:
What are the errors shown and what steps have you attempted?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.