Home > IT Blogs > SBS 2003 and beyond >

SBS 2003 and beyond:

HP Servers

Apr 5 2009   7:13PM GMT

Microsoft Server 2003 and Reading Bluescreen Memory Dumps



Posted by: Roger Crawford
Windows Server 2003, HP Servers, Blue Screen, Storport.sys

This week I was on-site at a customers and I had a server as I was watching it blue screen. You know those feelings when this happens but the server came back up OK. So I got to digging and found that this was happening when the server was under a load or doing a shadow copy. So ok what is going on here and I was not really finding anything giving me a clue why. So I dug some more and found the memory.dmp file that the server dumped so ok now what to do. I emailed one of the techs that if anybody had a tool for reading this file he would. Ok his statement was send it to MS it is faster. Now that is fine but they want money so why do that. I went to my friend Google and search for some tools and found the MS Windbg tool and also got the symbols for a 2003 Server. I followed the help for reading the file a dn defined the Symbol File folder and right away when I ran this I seen what was going on. It was a problem with the Storport.sys causing the Blue Screen so I did some searching and found that on some HP Servers running with SAS drives this was a issue and there was a hotfix and I applied this.

But that did not help it did this again so I dug some more and found that some of the HP Management drivers will cause this to happen. The server was one I moved from old hardware to new after the old hardware had died so there could have been some left overs from that so I completely removed the HP Management agents and this straighted this out. Now to find a resolution to get this updated with the HP Stuff and not have this happen. More on that later.

Til Later just Roger

AddThis Social Bookmark Button     0 Comments     RSS Feed     Email a friend

Apr 5 2009   6:55PM GMT

HP Servers and Windows Updates



Posted by: Roger Crawford
HP Servers, Windows Updates, HP NIC Teaming

There are days you just wish you had not got up early. Wednesday morning I had a site that needed updated with Windows updates so I was around about 2:30 and started updating all the servers. This was the only time of day we could do this so I got them all done by 5:30 or so and I checked OWA and the TS Gateway and the different programs and it all looked good. So I thought anyway about 8 we got the call that users could not access their email or user files. I popped in and looked around and it looked good from the server perspective anyways.

So they sent someone on-site and they couldn’t find anything so they started a Server down call with MS and worked on this much of the day and into the night. I got a email from the tech on-site about 9 wondering if I could relieve him at midnight if nothing had changed. I checked and nothing had changed so I headed on-site and got their a little after midnight and the MS guy was dwelling on the networking of the server and I watched for while and I could see one of the NICs was showing as failed which when I looked more it was actually the Network Team that was broken. We got the HP updates and updated the server with the latest and greatest updates and then rebooted the server still no go so I suggested removing the team which the MS guy thought would be a good deal. We removed this and then set the right IP on one of the adapters and disabled the other rebooted the server and life was good. We got the virtual servers back online and everything working. Moral to the story is make sure you ahve your HP Server updated with the newest updates as some of the MS Updates are not compatible with older drivers and firmware and such.

Til later just Roger

AddThis Social Bookmark Button     0 Comments     RSS Feed     Email a friend