Explore, isolate the problem via a process of elimination. In every problem you encounter there are always a few things that could be a prime reason for it.

We tried almost anything!Īfter some hard Googling, I came up with information that indicate that the anti-virus program is my 'smoking gun.' I turned to ESET again and, to my surprise, they said I should try a older version of Exchange server anti-virus software. THey sent me patches for HP hardware and nothing seemed to help. So, for almost two weeks, the HP server division support tried to fix the problem. I had ESET version 4 on the server, so I contacted the ESET support and they suggested to put an Exchange-related version of the anti-virus because it was an Exchange server. Īnother suggestion related to the anti-virus version on the server. So we changed the offload setting of the network card and some HP errors were cleared, but the server was still freezing. One of the suggestions was that it might be a misconfiguration of the network card. So after a week with no success, they replaced the motherboard but it didn't solve the problem. The HP log showed up with ASR error that implies a motherboard error or driver error.

We started to examine the HP report and found some errors.

The error was still there and the server was still freezing. They sent me a driver for updating the ILO to a newer version, but it didn't work. I applied the error to the HP support team for assistance. The log did not show any unusual error except from ILO error regarding the HP ilo2 network card. The only way to get it back on track was to physically power it off and back on. I wasn't able to ping the server nor connect it via RDP, but the server was still powered on. The problem was that my Exchange server was freezing up once or twice a day. I have an HP D元50 with Windows Server 2008 Standard Edition sp2 and Exchange 2007 sp2. My needle was an anti-virus version causing problems with my Exchange server. Every system administrator encounters once in while in a problem where the solution seems to be a needle in haystack.

Eset nod32 server edition