We have a Windows Server running 2003 with SP2 applied. Our environment is completely Terminal Server oriented. (ie. All of our staff connects to the Terminal Server to do their work, nothing saved on locals.)
Periodically we are getting Event 55's on one of the two physical disks. This has been happening for about 16 months now. Originally it was on a "real" server. Then we imaged it and set it up on a VMware server. Still had the issue. We purchased a new server and completely reinstalled the OS and applications. Only thing copied from the old system was the data. The problem has persisted.
I have been researching this issue and the only thing that comes close to what we have going, seems to be addressed in MS KB 932578. http://support.microsoft.com/kb/932578
However, that is for systems with allocation units smaller then 4096. Unless Windows is reporting it wrong, our server has a size of 4096.
Everything else I have found, has been older then what we have already installed.
We don't do anything with double-byte characters either.
It always seems to happen around specific times/days of the month. Though nothing is consistant with the programs running at the time. All that seems consistant is that it is heavier disk io.
So.... my question is (finally)... Is it possible that the fix in KB 932578 could fix this issue, even though my unit size is 4096? And is there any downside from trying this?