Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

LUA 2.x Schedule does not run.

Created: 15 Oct 2012 | 7 comments

Issue:

In LiveUpdate Administrator (LUA) 2.x  a “schedule” will not run. Usually it has been running, but now, for no obvious reason,  when scheduled to run, it just fails.

In the LUA interface,  under Events,  look for an error message similar to: “Execution for schedule <schedule_name> is skipped because already running request found for this schedule.” [sic]  The Activity Monitor shows no such schedule is running.

Cause:

This error message indicates that a scheduled task never closed properly,  and is preventing the next scheduled run from being able to start.  The hung task is not visible.

The hanging schedule can be either a Distribution task or a Download task.

Solution:

Log off the LUA interface and restart the LUA host server.  

Additional:

If you have email alerts configured, you may receive an email like this after the restart:

-----Original Message-----
From: <LUA sending name>   
Sent: Monday, April 23, 2012
To: Administrator

Subject: Distribution task 528 'Distribution A' has failed to complete

 Total size of files in request: 7026 MB.  Percentage Complete: 1%.

 Elapsed: 32 hour(s),56 minute(s),31 seconds

Started: 4/22/12 5:00:01 AM CDT

Ended: 4/23/12 1:56:32 PM CDT

 Further detail on the failures is provided below.

---------------------------------------------------------------

Distribution location: Default Production Distribution Center.

Failed file transfers: 246

Successful file transfers: 58

Reason for failure:  File(s) could not be transferred

---------------------------------------------------------------

HTH

John

Comments 7 CommentsJump to latest comment

.Brian's picture

You should also post as an article for better visibility.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

John Cooperfield's picture

Thanks!  I thought it was too short and simple for an article, but I think I will do that soon. May incorporate from folk's comments.

John Santana's picture

Hm... I also face this issue as well, but sadly that rebooting the server is not making any progress at all :-|

but thanks for the clarification and sharing here mate !

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

John Cooperfield's picture

John Santana,

Would you please describe the issues a little more, and are you having the error message in the first post above?

Thanks

Mick2009's picture

Many thanks, John!  Especially for posting a solution.

You may wish to cast a vote in support of the following proposed "Idea":

Email Alerts for Lengthy LiveUpdate Administrator 2.x Tasks
https://www-secure.symantec.com/connect/ideas/email-alerts-lengthy-liveupdate-administrator-2x-tasks

If that goes into effect, the intention is that admins will receive a mail earlier than the 32 hours. 

With thanks and best regards,

Mick

John Cooperfield's picture

Thank you,   and I Voted up   [Edit:] the article you cited:

Email Alerts for Lengthy LiveUpdate Administrator 2.x Tasks
https://www-secure.symantec.com/connect/ideas/email-alerts-lengthy-liveupdate-administrator-2x-tasks

John Santana's picture

Yes I have voted for your suggestion mate !

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.