Proliant DL380p Gen8 2012 standard server randomly hangs
Posted on 2014-01-07
Early last year, I installed a new proliant server to replace our DC. The new server is running server 2012 standard. I am now having an issue where the server hangs randomly for a couple of minutes and then is suddenly fine. While is hangs, users can't access SMB shares or the SpiceWorks helpdesk I have setup.
When I first set this server up, I remember this was happening but I don't remember what I tried to do to fix it. The issue seemed to go away on its own. Here I am now, several months later, and it is suddently happening again. So it either stopped and then started again or it has been happening randomly and I am just now noticing it. I could see it being easy to miss this because sometimes users may not report the issue since it hangs for a couple minutes and then is fine.
I talked with HP and they recommend I install the SPP which I am going to try tomorrow. I confirmed the BIOS is up to date.
I found these in the file service log.
BEDC01 2012 Warning srv System 1/7/2014 1:23:16 PM
While transmitting or receiving data, the server encountered a network error. Occasional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem.
BEDC01 30623 Warning Microsoft-Windows-SMBClient Microsoft-Windows-SMBClient/Operational 1/7/2014 1:22:26 PM
Connection to share \servername\IPC$ was lost. Status 0xC00000B5
BEDC01 30621 Warning Microsoft-Windows-SMBClient Microsoft-Windows-SMBClient/Operational 1/7/2014 1:22:26 PM
Session to server \servername was lost Status 0xC00000B5
I found several of the events below around the time the users reported the issue. They are for all sorts of services. Similar events appear to be in groups together randomly.
Log Name: System
Source: Service Control Manager
Date: 1/7/2014 1:05:16 PM
Event ID: 7011
Task Category: None
A timeout (60000 milliseconds) was reached while waiting for a transaction response from the Spooler service.
I thought the backups might of been an issue since they sometimes go into the day but I just confirmed the issue happened while no backups were happening.
I appreciate any feedback on this.