Package not installing - WaitingDependency

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Noro - 08 Oct 2008 09:30 GMT

Hi,

can anyone explain me what exactly mean the "WaitingDependency" state change
for execution request (in execmgr.log)? I have troubles deploying software on
some of my clients, where the state change is going from WaitingDependency to
WaitingDependency. It lasts for 5 days now. I'm not able to find solution for
this problem, normally the state change is going from WaitingDependency to
WaitingContent...

server: SCCM2007 SP1
client: windows xp sp2

Thanks

Reply to this Message

Sherry Kissinger [MVP-SMS] - 09 Oct 2008 14:16 GMT

It essentially means it's waiting for either another application to finish
successfully (i.e., you used "run another program first"), or it's waiting
for a dependent condition, like "only when no user is logged in".

Sometimes the other dependent program did finish successfully, but because
of a reboot condition set incorrectly, it's still waiting for a reboot.

Signature

Standardize. Simplify. Automate.

> Hi,
>
[quoted text clipped - 9 lines]
>
> Thanks

Reply to this Message

Noro - 09 Oct 2008 14:39 GMT

Is there a log file, where i can see what is the dependency the execution is
waiting for?

> It essentially means it's waiting for either another application to finish
> successfully (i.e., you used "run another program first"), or it's waiting
[quoted text clipped - 16 lines]
> >
> > Thanks

Reply to this Message