Windows 2003 Cluster will not roll over due to the Symantec PBX Service Group refusing to failover.
Sharing a few knowledgebase articles with the CommandCentral Community. Please respond to this forum if you find these useful.
----------------------------------------------
Document ID: 307696
http://support.veritas.com/docs/307696 Exact Error Message
"PBX cluster service is refusing to failover"
Details:
Remove the Symantec PBX Service Group.
note: The Symantec PBX Service Group is a shared service. Removing the PBX Service Group will deny it's use to all Symantec products installed.
1. Stop all the CCS services including PBX. <If other products that use PBX (like NBU) are installed, stop them as well>
A) Stopping of the processes using the Services Control Manager.
B) Also stop the Adaptive Server Anywhere service.

2. Open a command prompt and cd into the directory where PBX is installed. By default the path should be C:\Program Files\VERITAS\VxPBX\bin
3. Execute this command on the prompt "MSCS-cluster-pbx.bat -delete"

4. Check if the resources are been removed using the MSCS Admin console.

5. Start PBX and all other CCS services <also services of other products if stopped earlier>. Verify that all the process and Explorers are running.
a) cd C:\Program Files\VERITAS\CommandCentral Storage\HAL\bin
b) halagentcfg.exe" list-processes -a

--------------------------------------------------------------------------------
Products Applied:
CommandCentral Storage 5.0 DCAP, 5.0 MP1, 5.0 MP1 RP1, 5.0 MP1 RP2, 5.0 MP1 RP3
Last Updated: December 12 2008 08:00 PM GMT
Expires on: 08-20-2009
Subjects:
CommandCentral Storage
Performance: Network
Languages:
English (US)
Operating Systems:
Windows Server 2003
DataCenter, DataCenter (IA64), DataCenter (x64), DataCenter SP1, DataCenter SP1(IA64), DataCenter SP1(x64), DataCenter SP2, Datacenter SP2(x64), Enterprise (IA64), Enterprise (x64), Enterprise SP1(IA64), Enterprise SP1(x64), Enterprise SP2, Enterprise SP2(x64), Enterprise Server, Enterprise ServerSP1, R2, Standard Server, Standard Server SP1, Standard Server SP1 (x64), Standard Server SP2, Standard Server SP2 (x64), Standard Server(x64), Storage Server, Storage Server SP1, Storage Server SP2, Web Server, Web Server SP1, Web Server SP2
Comments
That's for sharing. I never
That's for sharing. I never knew about that actual batch file! (I just simply deleted it from cluadmin before)
This technote actually applies to other products such as SFW 5.0 where we created a PBX group for each node.
But later this has been removed in SFW 5.1 as it wasn't needed to specifically monitor the PBX service within the cluster.
Hence deleting this PBX cluster group in MSCS doesn't hurt at all for any product I believe. (As long as it remains started in SCM)
Please mark my post as solution to help others also if it resolved your issue.
Would you like to reply?
Login or Register to post your comment.