Hi All,
I have had Symantec Support to debug our problem and it appears to be a known issue internally in Symantec??????? Wonder why this is not made public yet???
As to Symantec, this problem should
only excist on Windows 2003 Cluster (MSCS) running RU5.
They are planning a fix, but it might not be implemented until RU6!!!!!
This seems mad, as this is supposed to be an enterprise product....Why is this patch not a priority to Symantec???
But conclusion on Windows 2003 cluster-nodes is: Downgrade to MR4 MP2 and then it all works perfectly again.
If you want to make sure that you have the exact same symptoms, then try running the sysinternals tool: handle.exe with the "-p" option and pipe it to a text file.
Search for Q: (in my case the Quorum drive) and if you see that the smc pid has an -RW lock on the drive, then you know this is the same problem.
Good luck with the next version of SEP. :-)