Re: Unexpected shutdown



From the list of events your system is rebooting. what happens in the event
logs prior to "previous sysytem shutdown..."

Are any dumps written?
Any stop codes? With these you can check on Technet for causes.
Do a search for files written around that time this may give a clue to what
the system was doing prior to the reboot.

Do you have any manufacturer diagnostics for the server? If the server is HP
or IBM etc then you will be able to download idag programs that will test
memory, processor etc.




"Marco Roberto Gonçalves Junior" <marco.roberto@xxxxxxxxxx> wrote in message
news:OTmW%23aLhGHA.3296@xxxxxxxxxxxxxxxxxxxxxxx
Phill,

first of all tks for your fast reply.
There is nothing running at this time (scheduled tasks) and the problem
does not happen everyday. Today, for instance, did not occur.

The list of event is the following

1 - The previous system shutdown at 6:57:16 AM on 5/30/2006 was
unexpected.
2 - Microsoft (R) Windows (R) 5.02. 3790 Service Pack 1 Multiprocessor
Free.
3 - The Event log service was started.
4 - The COM sub system is suppressing duplicate event log entries for a
duration of 86400 seconds. The suppression timeout can be controlled by a
REG_DWORD value named SuppressDuplicateDuration under the following
registry key: HKLM\Software\Microsoft\Ole\EventLog.
5 - HP NC7761 Gigabit Server: Driver initialized successfully.
6 - HP NC7761 Gigabit Server: Network controller configured for 1Gb
full-duplex link.
7 - The IPSec Driver is starting in Bypass mode. No IPSec security is
being applied while this computer starts up. IPSec policies, if they have
been assigned, will be applied to this computer after the IPSec
services start.
8 - The Exchange IFS driver loaded successfully.
9 - The Application Experience Lookup service started successfully.
10 - DFS has finished building all namespaces.
11 - DFS server has finished initializing.
12 - The IPSec driver has entered Secure mode. IPSec policies, if they
have been configured, are now being applied to this computer.
13 - The Server Agents service version 7.20.0.0 has started.
14 - The Storage Agents service version 7.20.0.0 has started.

Best Regards,

Marco


"Phill" <ps22@xxxxxxxxxxxxxxxxxx> wrote in message
news:2c2dnQKujNr2CeDZRVnyrA@xxxxxxxxxxxx
Your system is rebooting and you should have additional messages after
this about restarting windows (similar but not the same as this is from
my XP pc)

Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Uniprocessor Free.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


and about services starting.
the first one is usually the event log.service.

If it is the same time each day that your system is rebooting then what
are you running at 6:50 onwards.
Backups?
Exchange utils?
Is anything scheduled at that time within scheduler?


"Marco Roberto Gonçalves Junior" <marco.roberto@xxxxxxxxxx> wrote in
message news:OI%23ZQd%23gGHA.4080@xxxxxxxxxxxxxxxxxxxxxxx
Hi everyone,

a few days ago I started receiving in the event log the following
message:
======================================================
Event Type: Error
Event Source: EventLog
Event Category: None
Event ID: 6008
Date: 5/30/2006
Time: 7:00:37 AM
User: N/A
Computer: PATSRVEX01
Description:
The previous system shutdown at 6:57:16 AM on 5/30/2006 was unexpected.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d6 07 05 00 02 00 1e 00 Ö.......
0008: 06 00 39 00 10 00 e4 01 ..9...ä.
0010: d6 07 05 00 02 00 1e 00 Ö.......
0018: 09 00 39 00 10 00 e4 01 ..9...ä.
======================================================

It always happens at the same time, but I cannot figure out what is
going on.
This is a DC with Windows 2003 SE, Exchange 2003 and Norman Antivirus.
I configured the server to perform a complete memory dump, but the file
was not written.
I fact, I noticed that it could be a false message because it is an
Exchange Server (installed in a DC) and if I restart this server it
takes more than 10 minutes to be ready again.
I have some events in the security event log at 6:59 AM, 7:00 AM, and so
on. If you see the message above it was written at 7:00:37 AM and it
says that the shutdown was at 6:57:16. It sounds strange!!!
Does anybody know what could be the problem?


Best Regards,


Marco







.



Relevant Pages

  • Re: SBS Server keeps shutting down
    ... as we have had a few power cuts recently and the server kept chugging along. ... I have no idea what IPSec is ... multiple reboot mentioned above and some other troubleshooting steps ...
    (microsoft.public.windows.server.sbs)
  • Re: Unexpected shutdown
    ... Do you have any manufacturer diagnostics for the server? ... - The Event log service was started. ... - The IPSec Driver is starting in Bypass mode. ... - The Exchange IFS driver loaded successfully. ...
    (microsoft.public.windows.server.general)
  • Re: L2TP/IPSec Verbindung läuft mit XP SP2 nicht mehr
    ... In XPSP2 the IPsec driver needs a registry setting when either the ... server or workstation are behind a NAT gateway. ... 1- Client initiates to a server that is behind the NAT ... > Peer Private Addr ...
    (microsoft.public.de.german.windowsxp.networking)
  • Re: Should I install Certificate Authority to solve these problems ?
    ... You can use IPsec with or without certs from your PKI. ... negotiations to your AD machines or those trusting the ... > In the item 1 below, the tool in use is a HP server management tool (type ... >>> Management is pushing to get Certificate Authority ...
    (microsoft.public.win2000.security)
  • VPN zu Exchange Server
    ... Ich moechte mich in unser Firmennetz einloggen (Exchange Server) und habe ... dazu eine VPN Software (IPSEC) die den Tunnel zur Gegenstelle bereitstellt. ... EXCHANGE kontaktieren und auch synchronisieren, ... bekomme ich eine "Netzwerkfehler - Server nicht ...
    (microsoft.public.de.exchange)

Loading