For quite a while on one of the SCCM servers (SP2 R2 native mode on W2k8 sp2) regularly the task sequence failed at package validation stage - complaining one of the packages not found - in fact it is there. Strangely, once this happens a restart of SMS_EXECUTIVE service and SMS Agent Host service will fix the problem. However, it doesn't last long - the problem repeated almost daily. Just do not know what can be wrong. Why restart those two services can get the TS go through? Any hints?

Any errors in logs? Zulqarnain Ali | MCTS, MCSA | Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

For quite a while on one of the SCCM servers (SP2 R2 native mode on W2k8 sp2) regularly the task sequence failed at package validation stage - complaining one of the packages not found Any hints? Did u check the package was correctly distributed to DP ? what does smsts.log says ? are there any network issues ?//Eswar Koneti @ www.eskonr.com

I've faced this similar issue and because of that issue MP used to stopped working for us regularly. And we had noticed that whenever this issue happened, CCM namespace was getting disappeared from WMI (wmimgmt.msc) and atlast the issue turned out to be antivirus scan on WMI repository. Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

And for a sanity check, what service pack are you on? Do you have any hotfixes installed?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Take a look at the package version. In the SMSTSLog.txt it will tell you the package ID it is failing on and the package version will follow it. (ie. VPR0001B.214 packageID.version). Compare this to your DP. If they are different, then either the machine is not receiving an updated policy from the MP or the MP is unaware of the new package version from the DP. For the later, sometimes removing the DP from the package and re-adding it will fix the problem. If its the former, you'll need to take a look at the MP logs for any errors.Allen Anderson Systems Analyst Arizona State University - OKED Knowledge Informatics