Everyone --

We are still working through the issue with Microsoft and EMC. The most current is that we have been to single out a node in our cluster to be our guinea pig. As of this morning...

- We have found out that we had outdated HBA drivers for our HBA to our EMC SAN. There is also a mandatory (says EMC) patch from Microsoft required for the HBA. It should be in place now too.

- We have also put in some Server Service/LanMan reg pokes microsoft suggested.

One of the new things they found was related to this:

"The errors we’ve been getting indicate that the Server service is unable to keep up with the demand for network work items that are queued by the network layer of the input/output (IO) stream.

There are many causes some of which only cause brief logging of error conditions (but may not cause failover) and these may be addressed by tuning the server service.

Disk subsystem not being able to keep up is the most common cause of the accumulation of work items in the server service. "

He then went on to suggest this reg poke:

To increase the capacity of the server service to handle incoming IO request please set the following registry settings (Hexadecimal values) using regedit.exe:

HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

"MaxFreeConnections"=dword:00000064

"MinFreeConnections"=dword:00000020

"MaxRawWorkItems"=dword:00000200

"MaxWorkItems"=dword:00002000

--- We'll see where this takes us... I am also collecting additional information for him as well... will keep you posted.

-- Mike