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

Scheduled tasks fail with this error message:
"[396] An idle CPU condition has not been defined - OnIdle job schedules
will have no effect"
The OS is Windows Server 2003 R2 Std Edition SP2
SQL Server 2005 Developer Edition (9.0.3042)
Analysis Services is running.
Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00
(srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.832
Operating System 5.2.3790
What is the problem and the solution?Hi,
Goto properties of SQL Server Agent --> Advanced --> Check "Idle CPU
condition" and define appropriate values.
HTH,
Dinesh|||Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. what is kind of your job?
2. Does your SQL Server Agent Service account has administrator permission?
If not, what is the result if you use a local administrator as your SQL
Server Agent Services startup account?
3. Does this issue occur always or intermittently?
Also, for further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the SQL error logs which are located in the
folder %ProgramFiles%\Microsoft SQL Server\MSSQL(.n)\LOG by default.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Thank you. That did it.
<dinu_babu@.hotmail.com> wrote in message
news:1185349324.238775.247870@.x40g2000prg.googlegroups.com...
> Hi,
> Goto properties of SQL Server Agent --> Advanced --> Check "Idle CPU
> condition" and define appropriate values.
> HTH,
> Dinesh
>|||I needed to go to properties of SQL Server Agent --> Advanced --> Check
"Idle CPU
condition" and define appropriate values. as described by Dinesh|||Hi,
Thanks for your updating and response.
I am glad to hear that this issue has been fixed by Dinesh's suggestion. If
you have any other questions or concerns, please feel free to let us know.
It is always our pleasure to be of assistance.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================