Member Avatar for Techdavid

Every 2 hours my server will power down. I just recently installed the 2003 OS. I only used the first disc for the installation. There are no scheduled tasks and the power management settings are fine. Its not a heat issue because it will reboot immediately afterward. I would think this is a software issue, however I am not sure where to start.:(

  • 5 Contributors
  • 4 Replies
  • 493 Views
  • 4 Weeks Discussion Span
  • Latest Post Latest Post by lasitha2005d

Dani AI

Generated

A focused troubleshooting checklist that builds on ’s prompt to check Event Viewer and the SBS angle raised by , and . The two‑hour, immediate‑reboot symptom is most consistent with either a software-initiated shutdown (a process calling the shutdown API) or an external/firmware power cycle that immediately restores power (UPS/BMC/BIOS). The next steps aim to prove which.

First, concentrate on the System and Security event logs around the timestamps. Useful System events to identify the initiator are Event ID 1074 (shutdown initiated — shows the process/user and reason), 6006/6005 (clean stop/start of the event log service) and 6008 (previous shutdown was unexpected). If 1074 is present it will name the process or service that asked Windows to stop; if nothing shows, the cause is likely outside Windows.

If the initiator is not obvious, capture process creation so the offending process can be seen: temporarily enable Audit Process Tracking (Local Security Policy → Local Policies → Audit Policy → Audit process tracking) to record Security Event ID 592 entries for new processes (filter for shutdown.exe or similar). Procmon (Sysinternals) with a filter on Process Create is very effective but keep it filtered to avoid huge logs. Also inspect scheduled tasks and scripts:

schtasks /query /fo LIST /v
dir C:\Windows\Tasks

Check Group Policy startup/shutdown scripts (Computer Configuration → Windows Settings → Scripts) and any domain GPOs if the server is domain‑joined.

If Windows logs show no initiator, inspect external management: UPS software (PowerChute, APC, etc.), chassis management/iLO/DRAC/IMM logs, RAID/backup agents and BIOS power‑restore settings. Avoid ad‑hoc registry hacks or killing services as a long‑term fix; identify the initiating process first. If SBS is in play, verify edition and activation via official documentation rather than applying undocumented “workarounds.”

Recommended Answers

All 4 Replies

Member Avatar for jlego

what software runs on the machine.

after it shuts down, look at the event logs. under application and system. find the error listed and post it here

Member Avatar for ingrammusic

Is it SBS?

Member Avatar for Phlosten

Could it be a licensing issue? I seem to remember SBS shuts itself down if it detects another sbs server on the same network etc

Member Avatar for lasitha2005d

This is definitely an SBS issue. I m 100% sure. If you are using it as a DOMAIN CONTROLLER you have to avoid that. You have to demote and use it as a member server.Or reinstalling it and stopping when you are asked to install DC.
Seems you haven't installed your license properly. If you use a legitimate OS with License, you have to install it properly. Get used to the available tools and you will be able to install cal packs.
However if you have installed Database features or ERP then those will cause problems.
Its better if you have an Enterprise version as a DC since it is the most flexible and feature rich.
If its not legit:
You have to kill the task sbscrexe.exe from hour to hour. That will stop other functions as well.
However have a solution for that. A Registry hack. Inbox me. Last time when I posted that in a public forum I had to face problems :D

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.