Re: SMS Package Hangs on client

From: Fender (Fender_at_discussions.microsoft.com)
Date: 08/20/04 

Date: Fri, 20 Aug 2004 13:57:02 -0700

Thanks Shehzas,

Yep, after I set it up to "allow user to interact" it was as clear as day.
The batch file hangs prompting for a password when trying to make a drive
connection. When the batch is run from teh run line at the run line it runs
through just fine with no prompt. Since it is being run with the SMS account
or local machine account it hangs since that share has permissions assigned.
Since the batch was hanging waiting for a prompt, it wouldn't time out in the
12 hour time period and wouldn't return a failure code. This prevented all
subsequent packages from being deployed (they would have the status awaiting
another program to finish). Apparently the only way to clear this hanging
mode is to delete the advertisement and have each of the clients reboot (this
is the big pain!). Any other way you know of to delete the tasks without
having to do the reboot etc? Thanks again for your help.

"Shehzad Khoja [MSFT]" wrote:

> Can you check the program property "Allow user to interact with this
> program" and see if it is showing you a dialog box or any other prompts?
> What is the maximum allowed run time? Have you set it to days? If you don't
> specify anything for maximum allowed runtime then SMS defaults it to 12
> hours (not days). What does program do? Is it possible that program itself
> is taking all that time to run? While SMS is reporting that program is
> running can you check task manager to see if program is really running?
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Fender" <Fender@discussions.microsoft.com> wrote in message
> news:5081BD6C-D226-4773-AE5F-F03A940AA98F@microsoft.com...
> > I have created a package that hangs with the Message State Name of
> "Running"
> > and Message Name of "Program Started" in the Report Log. Nothing more
> happens
> > until it times out (days later). The package can be run with no problem
> from
> > the run line connecting to the same point on the distribution server (no
> user
> > prompts or pauses etc).
> >
> > The execmgr.log shows the last message few messages below:
> >
> > Execution Manager timer has been fired. execmgr 8/19/2004 1:02:24 PM 712
> > (0x02C8)
> >
> > I am running the from SMS 2003 to XP Clients Using admin rights for
> install
> > and as a mandatory package to be run as soon as possible.
> >
> > Any ideas what could be causing this package to hang? Thanks
> >
>
>
>

Relevant Pages

  • Re: SSH login automation, get stuck at the last step.
    ... will get stuck running the batch file. ... and then the prompt. ... When I execute my script on the top, ... Does anybody know about using Expect to do ssh login and then run any ...
    (comp.lang.tcl)
  • Re: Does pirut and yuum really work in FC6
    ... that package might have had a dependency on GNOME ... would have been removed after a prompt. ... If you have the yum log, ...
    (Fedora)
  • Portupgrade Stale Dependency Issue
    ... Just ran pkgdb -F per prompt from the portversion program and got the ... ruby-rdoc-0.9.0 is not required by any other package ... -> Hint: checking for overwritten files... ...
    (freebsd-questions)
  • Re: Should I add this Repo?
    ... Should I add this Repo? ... But it still sounds like a badly-created package. ... don't prompt ... installation. ...
    (Ubuntu)
  • Re: Does pirut and yuum really work in FC6
    ... that package might have had a dependency on GNOME ... would have been removed after a prompt. ... If you have the yum log, ... reproduce it, a bug report would be useful along with the steps and the ...
    (Fedora)