Saturday, January 22, 2005
Server Problems
This past week was very hectic for me with my consulting business. The company that my wife works for does "document requisitioning", which basically means they are hired by an attorney, insurance company or someone else to do the "leg work" in getting documents, copying or scanning them, and then make them available to the client either in printed or digital form.
Well something happened with their server last Friday and it crashed. The server would not boot-up but would go to a "blue screen of death" (BSOD) while booting up Windows Server 2003. I was able to get it up, but only by disabling a dozen services and the network cards, would it then boot into the OS. I could then start all the services and enable the network cards, and the system would work.
After a few hours the ASP pages on the server (created by a 3rd party vendor application) would stop working with an error message about "Unable to start new session". Incidentally, the ColdFusion pages for the applications I wrote worked fine. Sometimes restarting the web server services would allow the ASP pages to work again, other times I had to restart the whole server again.
The event log didn't have much for clues and what was worse was that I couldn't narrow down which service was causing the problems as I had commitments each night of the week until Friday and rebooting the server during the day just wasn't a good choice as the companies clients would be using the web site in addition to the staff using it.
So the server hobbled along until Friday night when I was able to examine things and reboot the server a number of times. At first I thought it was bad memory, but after running it through 4 different memory tests, all reported the system RAM was fine.
I believe the problem was two fold. First, I think the 2GB of RAM isn't enough anymore so we ordered another 2GB of RAM to install which will take this server up to 4GB of RAM (running Windows Server Enterprise by the way). Second, the Microsoft Exchange Information Store seemed to be corrupted and leaking memory so I re-applied the service pack 1 for Exchange 2003 which seems to have fixed that problem. I also applied the latest BIOS and RAID firmware updates per the manufactuer.
For now the server seems to be back to it's solid state after the service pack was re-applied. The memory will be here on Tuesday and I'll install it then. I worked on this from 7:00p - 3:00a so I'm heading to bed now.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment