Re: Reboot command no longer works in Task Scheduler
- From: "Dave Patrick" <DSPatrick@xxxxxxxxxxxxxxxx>
- Date: Mon, 27 Oct 2008 08:51:51 -0600
What errors are present in the system log at the time machine reboots? Do you have a handle on what process is memory leaking?
You can script it.
http://www.microsoft.com/technet/scriptcenter/resources/qanda/aug05/hey0816.mspx
Fixing the memory leak and blue screen stop error makes the best sense to me.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Oliver" wrote:
Hi, for the system log - I've changed this to overwriting events older than 7
days already. So I am hoping this will fix the problem. However, I want to
find out if there is a free faciliy from Microsoft where I can request for an
email notification if a certain ID is triggered. Example, on my Exchange
Server event viewer log file, if there are IDs such as 8250, 8026, 2102, then
I would like a program to notify me via email. Is there such a facility?
The reason for this is that when the domain controller shuts down
unexpectedly, all domain servers are affected, the Exchange Server event
viewer log file generates these ID codes. So if these happens, an email
alert will enable me to respond quickly. Does this make sense?
Oliver
"Dave Patrick" wrote:
What is in the system log at the time machine restarts?
Control Panel|Administrative Tools|Event Viewer|"file"|Action|Properties the
default is to overwrite events older than 7 days and max log file size of
512 kbytes. You can change to "Overwrite Events as needed"
"The shutdown has to work on each Saturday to refresh the server memory."
It would be better to locate and fix the leaking process.
Take a snapshot of Task Manager|Processes just after startup. Then check it
again later to see what process is ballooning. Also take a look at Task
Manager Processes|Mem Delta a consistently positive value usually indicates
a memory leak.
This tool may also help.
http://www.microsoft.com/technet/sysinternals/Utilities/ProcessExplorer.mspx.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Oliver" wrote:
> The following bat script (as a file.bat) which I put on a task > scheduler
> no
> longer works (W2K service pack 4).
>
> Shutdown.exe /L /R /T:120 /C
>
> How can I fix this? The shutdown has to work on each Saturday to > refresh
> the server memory.
>
> Also, as a related solution to the above problem, how I can get the > event
> viewer to email me an alert when it triggers certain ID code?
>
> Our main problem is that the server shutdowns expectedly and I suspect > it
> is
> the event viewer getting full. So I am hoping someone will have the
> solutions.
>
> Oliver
>
>
.
- References:
- Reboot command no longer works in Task Scheduler
- From: Oliver
- Re: Reboot command no longer works in Task Scheduler
- From: Dave Patrick
- Re: Reboot command no longer works in Task Scheduler
- From: Oliver
- Reboot command no longer works in Task Scheduler
- Prev by Date: Re: Reboot command no longer works in Task Scheduler
- Next by Date: Re: AVG killed a file - now W2K says no access
- Previous by thread: Re: Reboot command no longer works in Task Scheduler
- Next by thread: AVG killed a file - now W2K says no access
- Index(es):
Relevant Pages
|
Loading