asked on

Win2k server shuts itself down every 7 days

We have a fairly new machine running Win 2k Server (SP4), and it's running just one program (ADP Software for payroll). We have Norton Corp Ed on there for security purposes, and that's about it. Every Sunday night, at 6pm, the machine shuts itself down, (EVENT ID 6008). I realize this has been covered before, but I haven't been able to gather an answer from the previous postings. If you need more information from me, please ask.

Thanks,
Bill Mirza

ASKER CERTIFIED SOLUTION

Lee W, MVP

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Zaheer Iqbal

Is it overheating etc... Anything the event log to show..
Plz check the following http://www.eventid.net/display.asp?eventid=6008&eventno=14&source=EventLog&phase=1

bmirza

ASKER

It's an HP/Compaq workstation... used to have WinXP on it, and we decided to use it as our ADP server.

I don't think it's an overheat issue, because it happens at 6pm every sunday. the Automatic updates are off. any other options to explore?

BigC666

howdy,

what does the event viewer record at that time.

bmirza

ASKER

nothing at all for the time of the crash... at the time of restart, you see a log referencing the 6pm crash on sunday.

BigC666

what does the entry say?

bmirza

ASKER

Here's the log for monday morning (when we turned it back on):

Event Type:      Error
Event Source:      EventLog
Event Category:      None
Event ID:      6008
Date:            10/11/2004
Time:            9:14:51 AM
User:            N/A
Computer:      ADP1
Description:
The previous system shutdown at 6:00:38 PM on 10/10/2004 was unexpected.
Data:
0000: 000a07d4 000a0000 00000012 00000026
0010: 000a07d4 000a0000 00000016 00000026

-------------------------------------------------------------------------------------------------
and here's the last warning that we got before that: (3:32 pm on Sunday)
Event Type:      Warning
Event Source:      w32time
Event Category:      None
Event ID:      64
Date:            10/10/2004
Time:            3:32:54 PM
User:            N/A
Computer:      ADP1
Description:
Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute "w32tm /s" from the command line.
Data:
0000: 000003e5

BigC666

is this the machine that does the time sync, the time sync is critical to a win2k network

bmirza

ASKER

I am unfamiliar with "time sync"... so, no I don't believe it does anything with "time sync"... it is actually independent of the entire network. we have one web server, one email server and one adp server. it's only purpose is to be the ADP software server for 2 workstations.

i also forgot to mention that we're running SQL Server v. 7.5.1 on that machine.

BigC666

is it in the domain or a domain by itself

bmirza

ASKER

it's in the domain, i would compare it to a networked workstation that just happens to be serving adp software.

BigC666

iwould suggest that you time sync it to you dc using the net time command, start->run->cmd enter this will get you to the dos prompt type in net time /? to get help

bmirza

ASKER

ok thanks, i will try that out and i guess we'll see on monday.

BigC666

ok, let us know

nihlcat

This has probably already been asked elsewhere, but are there any scheduled tasks? We had an issue with a PC inventory program that flipped out once a week on a W2K server.

nihlcat

Yep, actually leew asked that question long ago...