Can you check this link.

Installing a Symantec Endpoint Protection client to a cluster server

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008120113202748

Hi, we will try that out tonight and i will let ya know of the results.

Thanks for the Info

Michael

I have the same problem in my costumer.

Could anyone help us?

Thank you very much,

Hi Cormac,

Did you succeed after following this procedure?
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008120113202748

Thanks

I have the same issue.  Did Symantec acknowledge the issue yet?

Getting exactly the same error as shown in the first post.

Does anyone have a fix for this??

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. :-)

Symantec,

I have been dealing with your shoddy products full time for the past few months. This problem has been reported back in October '09, and there is still no fix for the customer affected? I hardly consider downgrading to an older version of Endpoint a solution, especially since this version has issues of it's own.

When is this going to be fixed?

Symantec,

Please update this if this issue has been resolved already and put the solution in this Forum.

Thanks,

We just ran into this issue too.   Can someone from Symantec at least confirm that this will be fixed in RU6?

We just ran into this issue too.   Can someone from Symantec at least confirm that this will be fixed in RU6?

Hello,

Is it the same issue with VCS 5.0 / Windows 2003 cluster ?

Jean-Louis.

The KB article that Thomas refers to above says that it is now fixed in RU6.

I havent tested this yet though, i just set our services to disabled for now and need to look at the upgrade now....

sigh... thanks symantec :(

its been fixed, however use the Micorosofthandle.exe in case you come across this error :-(

Anyone know if this is fixed in MR6 MP1?

Curtiplas - yes this has been fixed in MR6 MP1, we have it running on our cluster nodes now without issue.