I've recently created a replica of our production datawarehouse on our new development server. All databases, DTS packages and agent jobs are identical. Production runs perfectly however on development I'm experiencing an interesting phenomenon which is causing some headaches

SOME - not all - of the scheduled jobs just don't run. No errors, no failures - just nothing

The status of these is 'Not Running', the Last Run Status is ''Unknown' and the Next Run Date is last night - ie when they should have run. I tried kicking a couple of them off manually yesterday and they successfully however the scheduled run for later that night still did not take place - so the Next Run Date is still last night. I've run a couple manually this morning and the Next Run Date is for tonight but as per yesterday's manual attempt I'm sure they won't run tonight

I've confirmed that these jobs are enabled, runnable and scheduled. The schedule is enabled and the current date/time according to the job properties on the schedule tab is correct

The jobs are targeting the correct server (local) and are sourced from the correct server. They are running under the same profile as the jobs which did run

So at this point I'm stumped! Any ideas???

TI

Kristen

Yep and as per my expectations again they didn't run. Just nothing. The Next Run Date still says last night.

Do you have warnings, errors in the SQL Agent log?

-Sue

On Thu, 13 May 2004 16:11:04 -0700, "Kristen"
<khodges_nosp (AT) m_csr (DOT) com.au> wrote:

Well there were no errors however you question prompted me to look beyond errors and display all messages in the log and guess what? I found an Information message that contains the answer but I have no idea how to fix it

[396] An idle CPU condition has not been defined. OnIdle job schedules will have no effect

Hunted around in BOL and in Microsoft KB but there was no mention of anything with that error number or with that message. Any ideas?

That doesn't really matter if you jobs are scheduled to run
at specific times.
You can schedule jobs to run when the CPU becomes idle -
those jobs need the threshold of what you define as an Idle
CPU condition. You can set the idle cpu settings on the
advanced tab of SQL Agent properties.

-Sue

On Fri, 14 May 2004 01:21:03 -0700, "Kristen"
<khodges_nosp (AT) m_csr (DOT) com.au> wrote:

So I guess, if that isn't it then I'm still stuck with schedules that just never run.... is anyone aware of any ideas or experienced similar problem?

The solution, if anyone is interested, was that the Windows Event Log was full and the jobs had the 'Write to Windows Event Log' option enabled

So simple and yet so obscure!

Thanks for posting what ended up being the cause of the
problems!

-Sue

On Wed, 19 May 2004 23:31:02 -0700, "Kristen"
<anonymous (AT) discussions (DOT) microsoft.com> wrote: