Comment: The event viewer shows a VolSnap error with a event Id: 33 Then the server shuts down. I don't know why. The hard drive is half full so plenty of space. The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.

Perhaps this fits the bill http://support.microsoft.com/kb/887827 Imagine the power if you knew how to internet search

You cheated wanderer! You used google. Or worse yet, you surfed over to microsoft's knowledge base and ran a search on the error message there..........

Busted! You caught me CurtR! But that's not cheating, that's using the tools available. We aren't cavemen anymore. Well most of us aren't :-) Imagine the power if you knew how to internet search

Yeah guys but I don't think thats not my problem. Why would it shut the server down and then it disables a processor and it won't boot back up. So then I can't remote into it and restart it, I have to drive to the office and enable the processor and reboot and its up?? But the event log shows the error that I posted as the last thing happening before it gos down???

Not sure what you mean by "disable the processor"? To me the phrase "shut the server down" implies it's off, (ie: no power). If that's the case, then you can't remote in to it and restart it because it's off.....period. If the NIC in the server is WOL capable, you could start it that way, but that's a different ball of wax and doesn't address the issue at hand. I didn't read the article through myself. I didn't need to as I'm not the fella with the problem. Honestly, I'm not going to now either. But as my previous sarcastic post implies, by doing groundwork with google and the MS Knowledge Base (ie: using the tools available to repeat what wanderer said) you should be able to find all the info you require if that link wanderer supplied doesn't fix the problem.

Well I am curious as to what you mean by "it disables a processor". What is "it"? "as the last thing happening before it gos down" That doesn't always mean anything. If it crashed, whatever did it, didn't have time to write to the log. "The oldest shadow copy of volume C: was deleted " Um how did you do that? Just delete the file? You might want to use performance monitor and log 'paged pool memory' counter as it seems to relate to problems with VSS. Are you ready for where Microsoft wants you to go today?