Agents not running

All sheduled agents in a particular database are hybernating. 2-3 developers work on them and no one is sure if someone has *done* anything. Its been 3 days now and none of the agents scheduled to run daily have bothered to run.

We have tried restarting the Agent Manager. A service or the server restart, however, we haven't attempted yet. Could it be due to corruption? As of now I plan to restart the server and run fixup on databases. What other things are to be checked? I would like to keep the downtime minimum.

Thanks for your time.
LVL 19
Who is Participating?
HemanthaKumarConnect With a Mentor Commented:
Refer to this technote for troubleshooting scheduled agents ..

Sometimes restarting AMGR task would fix this issue...AMGR is heavily loaded and consumes most of the server resources...If you have checked my solutions... I mostly discourage scheduled agent idea for that reason. Keep it to low and amgr is your best buddy

Sjef BosmanConnect With a Mentor Groupware ConsultantCommented:
Did you try
    Tell Amgr Schedule
    Tell Amgr Status

And nobody touched the server's clock? It is only one database? You don't have to restart the server then, when you want to fixup the database?

Is there one agent that consumes all time, which got restarted and still consumes all?

madheeswarConnect With a Mentor Commented:
Try to run manually in a test environment.

And try to resave the schedule agents and also try to save as another name and schedule.
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

Sjef BosmanGroupware ConsultantCommented:
What says the Agent Log of the agents?
p_parthaConnect With a Mentor Commented:
Check whether the agent is scheduled to run on that 'server'

RanjeetRainAuthor Commented:
Ah.. sorry to be so late in getting back. We have sorted it out. Actually the claim, that no one has done nothing, was wrong. Some kind soul had signed the database with an ID which didn't have the permission to run agents on the server. Initially no one noticed that agents were not running. A user reported and we saw a strom rushing to us. Luckily for us, we figured it before it became a major issue.

Thanks for all your suggestions.
Sjef BosmanGroupware ConsultantCommented:
That's up to Madheeswar, I think he was closest:
> "... try to resave the schedule agents ..."
RanjeetRainAuthor Commented:
Its okay. No sweat.
RanjeetRainAuthor Commented:
When you are in trouble you look around for hope all around. Any suggestion is worth a million. Any of these suggestions could have saved me a lot of time. And that's worth several tousand EE points. In that case I'm afarid I couldn't have given anybody nopthing other than a thank you.

Points don't matter to me as much. I dont want a refund. Let people find spending time here worthwhile.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.