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......./App
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.
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......./App
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.
ASKER
I did, but it didn't make any difference..
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.
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.
ASKER
you mean i should remove all the drives I added?
ASKER
SMS_Distribution_Manager is showing a status of Critical......
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
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?
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
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
ASKER
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?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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?
Have you checked the Site Status logs for the Distribution Point/s?
I have had DPs run out of storage space previously and throw up such errors. Might want to check that.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
ASKER
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.
The logs for the DPs will shed light on that issue, have you checked these yet?
ASKER
there are few of them, which one is the right one to check?
ASKER
smsdpmon.log this was last logged in 2014
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.
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.
ASKER
That does shows errors, but the steps I have taken to solve it, it doesn't work :-(
What are the errors shown and what steps have you attempted?
After suffering the same issue myself I figured out the fix: Revision history.
Open X:\windows\logs\smstslog\smsts.log
In there it will have the ID of the app - e.g. BAFF61AEB/2. The important bit is the revision at the end. In my case the app was a Rev 6 but the OSD was looking/using Rev 1.
The fix: delete the revisions. I deleted all except current one and it fixed it immediately.
Redistributing/validating does not work because the App is definitely on the DP. I can even deploy it. It's the TS is stuck at the wrong Revision.
Open X:\windows\logs\smstslog\smsts.log
In there it will have the ID of the app - e.g. BAFF61AEB/2. The important bit is the revision at the end. In my case the app was a Rev 6 but the OSD was looking/using Rev 1.
The fix: delete the revisions. I deleted all except current one and it fixed it immediately.
Redistributing/validating does not work because the App is definitely on the DP. I can even deploy it. It's the TS is stuck at the wrong Revision.
You can refresh the packages and try.