I have a new server, ML570 G4 Proliant, that has been chugging along fine for the last few months. However, just recently - probably within the last several weeks - I've been noticing in the event log, at seemingly random times, "The previous system shutdown at <time> on <date> was unexpected" EVENT ID 6008. The only thing I can think of that has change is Retrospect Enterprise Server 7.6 was installed to back up files to a network share (one folder in the backup que is 720k files); however, retrospect will say in it's internal log "backup script <name> ran successfully on <time>" so I don't think it's due to teh backup software. Yet then it will say "execution terminated unexpectedly possibly due to power failure or system crash" I've include two screen shots of the event viewer errors
nic agent error
shut down error
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I noticed this information snippet in the event viewer - the file that it says to look at is over 2GB and will not open with notepad as there is not enough memory to view it (8GB of ram installed currently)...not sure if this is important or not..
bugdump
We have 5 ML 570 servers that randomly reboot with event ID 6008. I am trying AGAIN to get to the bottom of this and came across your post.
One of these servers that we have was running Server 2000 we got Microsoft to look at the issue and it needed a hotfix that we could not get from them because we had not taken out a Microsoft extended hotfix agreement in 2005 but as Windows 2000 is no longer supported we cannot purchase one of these agreements or get the necessary hotfix.
Apparently there is a problem with Windows 2000 running on this server. This can happen on a computer that is using an Intel Dual-Core Xeon 7100 series CPU. However, the problem could also occur with other dual-core processors that use an L3 cache.
We installed Server 2003 and the server has now only rebooted once since (In about 6 months). It is just the other 4 servers running server 2003 we now have to stop rebooting randomly.
If it helps we our servers are in an air conditioned server room with no temperature issues, three of the servers are SAN attached but the two that are not also reboot randomly. We have noticed that they reboot at a similar time so it is possible that it could be a backup job. It does not happen on our ML 570 G4 that is running ESX 3.5 so I believe that the issue might be a microsoft issue.
This was what would happen before we upgraded to 2003 then it turned into the crash eventid 6008
http://support.microsoft.c
This is to do with a fault in one of the HP agents
http://h20000.www2.hp.com/
Business Accounts
Answer for Membership
by: CPAsAdminPosted on 2008-10-14 at 09:14:56ID: 22712774
I would be checking the UPS for problems. Weak batteries, excessive load. Move the server to a different UPS or to the Wall. Did the problem follow the server?