This thread shows you how to identify the program causing the shutdown if you are unsure: 1 Poblano OP bg_vignesh Aug 21, 2013 at 4:10 UTC Hi, Join the community Back I agree Powerful tools you need, all for free. A driver update could have maybe caused the problem with Windows Update. I am checking the server every hour or so, waiting for it to fail, with my luck it will run for 3 weeks now without issue. 0 LVL 38 Overall: news
Can you recall the last thing you did on this server? Googling the event ID mainly points out to heat issue or some sort of memory failure but this server is on a virtualised environment (VmWare esxi 4.1) along with its companion you can use utilities from technet to read your dump file and it will usually show you if any drivers or which ones caused the issue. Creating your account only takes a few minutes. https://social.technet.microsoft.com/Forums/windowsserver/en-US/1c0662ef-2922-4ec1-82db-bdee7ef529cf/event-id-6008-windows-server-2003-server-reboot?forum=winservergen
When we opened the cabinet and checked the server hardware and noticed there was only one power supply we knew we were on the right track. Can you let the fans speedup? I have 4 of these in the same rack and this one is running the hottest of all 150f. According to MS: http://support.microsoft.com/kb/326564 This is an issue with a program that is forcing the system to shut down.
Agree? 0 LVL 13 Overall: Level 13 Windows Server 2003 3 Message Assisted Solution by:Richard_de_groot2008-03-18 There was a remarkable change in behaviour when you put the fans on the MB. At this point, I will head home and watch for the pings to the server to stop as my clue that its gone down. How can I find the reason for the last shutdown in Windows Server 2003. Event Id 6008 Windows Server 2008 R2 Unexpected Shutdown I run Symantec AV 10.2, I did notice that the install was strange (client was not reporting properly) so for the moment it has been removed.
And read this article which listed possible reasons for event 6008: http://www.chicagotech.net/troubleshooting/eventid6008.htm Below are related KBs, also check them: You may experience an abnormal shutdown on a Windows Server 2003-based computer Event Id 6008 Windows Server 2003 R2 Of course this one is near the bottom so I am off to play rack games now. 0 LVL 38 Overall: Level 38 Windows Server 2003 33 Message Accepted Solution First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. https://support.microsoft.com/en-us/kb/950323 Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.
I don't see any obvious signs of problems in the event logs. Event Id 6008 Windows Server 2012 R2 Try Free For 30 Days Join & Write a Comment Already a member? and stopped. 0 LVL 38 Overall: Level 38 Windows Server 2003 33 Message Expert Comment by:ChiefIT2008-03-16 "Question: I changed the server not to reboot on failure but it is, any Is it possible that dust can be the problem for short circuiting the server?
It is running on a UPS so I don't think it lost power. navigate to this website All rights reserved. Could it be that the PSU slowely reducing it's power? As I have an idential server, I could swap out RAM to test. 0 LVL 13 Overall: Level 13 Windows Server 2003 3 Message Expert Comment by:Richard_de_groot2008-03-16 Let's try the Event Id 6008 Windows Server 2008 R2
What can I make out of this event log? The two I found that remove the ""rebooting problem"" are housecall and spybot S&D. So, I am going to take a couple guesses. More about the author Of course since this was an unexpected shutdown, it does not give me much useful information.
We are a small organization too and hence I'll take your idea and see how I go.Thanks. 0 Pimiento OP Taylor9004 Jan 29, 2014 at 4:48 UTC Well, Event Id 41 Windows Server 2008 R2 That said, I think I may head out and continue death watch from home. then you can reference the event id as mentioned to find out any solution.s share|improve this answer answered Jul 2 '09 at 18:16 dasko 82411628 add a comment| up vote 0
Can you take the hood off the case and ventilate th MB area? View → Filter... → Event Id: 1074 and 1076. No user logged during the time betwen the reboots. The Previous System Shutdown Was Unexpected Server 2008 Maybe also with another virusscan tool than you already have. 2.
windows-server-2003 windows-event-log share|improve this question edited Feb 27 '12 at 16:29 voretaq7♦ 69k1397179 asked Jul 2 '09 at 18:02 railmeat 3011410 add a comment| 4 Answers 4 active oldest votes up Connect with top rated Experts 14 Experts available now in Live! That will prevent the services it runs from denying you the ability to remove the spyware application. click site A hotfix is available for this from Microsoft.
Join Now Hi, We've received the below error log occasionally on our servers. I have seen where Windows updates will shut down automatically after downloading the latest updates. If yes, you may be looking at a hardware problem. The machine is a SuperMicro X6DH8.
Richard 0 Message Author Comment by:systemssupply2008-03-15 Thanks for getting back to me, I am sure I changed nothing, have not been there is weeks. But your answer did help. They don't conflict with eachother because spybot is an executable and housecall is a full program. To fix this problem you might want to look at this post and create a domain policy that prevents Windows Updates, or WSUS servers, from rebooting the machine upon installing updates: