Server reboot every hour on the hour.

I installed a new server for a customer and the last few days the server is restarting on a hourly basis.
In the event viewer, I noticed the tasks below are the last items before the server restarts.  There are no errors in the event log.  Can I shut down the service, so it won't run?  
------------------------------------------------------------------------------------------------------------------------------
Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------------------------------------------------------------------------------------
Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
vitalev88Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RohitBagchiCommented:
This also sounds like a virus.

Check the RPC service under services and change its properties to "Do Nothing" on error.

I cant remember the name of the virus that does this, but this is the easiest fixit if thats the problem. Once done, the server will stop rebooting and you should try an antivirus to sort out the problem permanently.

Hope this is the problem and it helps.
0
vitalev88Author Commented:
I set the RPC service to Do Nothing on error.  I'll see at 1030am, if you systems stands up.  I'll let you know.
0
RohitBagchiCommented:
Best of luck mate - i know these kind of problems can really make us want to tear our hair out...
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

rindiCommented:
I'd also disable automatic reboots on system error (right click my computer, select properties, advanced, startup and recovery settings), that should then show you a Bluescreen with error code on it which could help diagnosing it. Also look for minidumps and upload a few.
0
vitalev88Author Commented:
No, luck.  The server just restarted even though I did everything you all sent.  Any other ideas?
0
drchristopheCommented:
Have you tried disabling the WMI (Windows Management Instrumentation) service.

It could be Group Policy Processing writing to the WMI database and failing. Be aware if you diable this service the following will also be stopped:

Security Center
Windows Firewall

But I'm sure you can live with that for testing.
0
vitalev88Author Commented:
I shut down the WMI services, I'll let you know at 12:30pm EST.  The server goes down like clock work.
0
vitalev88Author Commented:
No luck.....  The Server rebooted again.  Any other ideas to try?
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
Sorry... but this sounds VERY much like you are running Microsoft Small Business Server but haven't set it up properly.  Small Business Server does this if it is not setup in a domain within the first week or two.  The only exception is that there SHOULD be an event log notice indicating this... Can you confirm you are CERTAIN this was not installed from Small Business Server media?
0
vitalev88Author Commented:
No, it's Server 2003 Standard, not Small Business Server.  I install it myself.  It's been running fine for almost two months, but for the last few days, it's been restarting every hour.  I even changed the time on the server it see if it wouldn't restart, but it did at half past the hour.
0
drchristopheCommented:
I would suggest as you have instaled it for a new customer they may be getting a little bit anoyed by now.

I think you should bite the bullet and perform a repair on the o/s. You won't lose an files or config etc... but may be the quikest way of getting you back up and running again.

here is the process from MS just encase you don't know:

How to Repair Your Installation of Windows
You may be able to repair a damaged Windows Server 2003 installation by running Windows Setup from the Windows CD.

To repair your installation of Windows, follow these steps: 1. Insert the Windows Server 2003 CD in the CD-ROM or DVD-ROM drive.  
2. If the Windows CD displays the What would you like to do? menu, click Exit.  
3. Turn off your computer, wait ten seconds, and then turn your computer back on.  
4. If you are prompted to start your computer from the CD, do so.

Note You must be able to start your computer from the Windows Server 2003 CD-ROM to run Windows Setup. Your CD-ROM or DVD-ROM drive must be configured to do so. For information about how to configure your computer to start from the CD-ROM or DVD-ROM drive, see the documentation that is included with your computer, or contact your computer manufacturer.  
5. After Setup starts, press ENTER to continue the setup process.  
6. Press ENTER to select the option To set up Windows now, press ENTER. Do not select the Recovery Console option.  
7. Press F8 to accept the licensing agreement.

Setup searches for previous installations of Windows. " If Setup does not find a previous installation of Windows Server 2003, you might have a hardware failure.

Hardware failures are beyond the scope of this article. See a computer hardware specialist for more help or try the Hardware troubleshooter. For more information about the Hardware Troubleshooter, see the Windows Server 2003 Help topic "Using Troubleshooters."
" If Setup does find a previous installation of Windows Server 2003, you may receive the following message:
If one of the following Windows Server 2003 installations is damaged, setup can try to repair it. Use the up and down arrows to select an installation. To repair the selected installation, press R. To continue without repairing, press ESC.
Select the appropriate Windows Server 2003 operating system installation, and then press R to try to repair it.
" Follow the on-screen instructions to repair the installation.

Notes" You might have to change the boot drive sequence in your BIOS settings to successfully start your computer from the Windows Server 2003 CD. Contact the manufacturer of your computer, or see your manufacturer's documentation, for more information.
" If you cannot start your computer from the Windows Server 2003 CD, you might have a CD-ROM or DVD-ROM drive failure or other hardware failure.

Hardware failures are beyond the scope of this article. See a computer hardware specialist for more help or try the Hardware troubleshooter. For more information about the Hardware Troubleshooter, see the Windows Server 2003 Help topic "Using Troubleshooters."
" After you repair your Windows Server 2003, you may be required to reactivate your copy of Windows Server 2003.  
 
 
0
vitalev88Author Commented:
I check for virus and the server is clean.  Rebuilding the server is the last thing I will have to try.  Would anyone else have any questions of why the server restarts every hour at 42 minutes after the hour?
0
rindiCommented:
Are there any minidumps you could upload?
0
RohitBagchiCommented:
Stupid thing this - have you tred changing the time to check if its clock related - as in it reboots EXACTLY 42 Mins past the hour.

If you change the time by  afew minutes, does the action happen on schedule?

Disable the network interface before its scheduled for a auto restart, maybe its being shutdown remotely. Turn of remote log ons and try if the restarts happen even if that is the case.

Check if the CPU fan is working - maybe overheating is causing the restarts- then last ditch, plug the HDD into another computer and run it as is and check if the restarts still happen. If they dont check for faulty hardware on the server computer.

Wow, this sounds like a fun experience. Good luck mate.

0
vitalev88Author Commented:
After checking the server, I shutdown Symantec Backup Exec and the server stop rebooting.  I'm working with Symantec to resolve the issue.  Thanks for your help comments and suggestions.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rasheed04Commented:
No Symentic AV on the server. But server restarts every hour. First 3 days worked without any issue. Using another DC in Win 2000 server. But this is win 2003 without domain (workgroup). Seen some answeres in google that due to multiple DC. But didn't connect multiple DC. so what could be? Trend Officescan installed as client from DC win 2000 server.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.