cjungers
asked on
Veritas VEA Issue - "volume manager disk group" restype not recognized on 1 node of a cluster
I have a Win2k3 EE Sp1 (32bit) 2 node Sql 2005 cluster running 3 sql instances. We are moving from EVA 5000 disk to EMC disk. Using emulex HBA's LP952's, SCSIport drivers version 5.5.30.2, using secure path 4.0. Installed Veritas Storage Foundation 4.3 Mp1 on both nodes to migrate the volumes to dynamic disk and cluster disk resources to Veritas disk groups. On node1 of the cluster the server is not able to recognize the restype "Volume Manager Disk Group", so node 1 is not able to recognize the cluster disk or create new disk resources (Using Volume manager disk groups). On node 2 I am able to create the disk resources just fine. I am getting this error on Node 1
Event ID: 1058
"The Cluster Resource Monitor could not load the DLL vxres.dll for resource type Volume Manager Disk Group."
I have already deleted the retype from node 1 and re-registered the retype as follows
- cluster restype "Volume Manager Disk Group" /Delete /TYPE
Then
- regsvr32 vxresext.dll
- cluster restype "Volume Manager Disk Group" /CREATE /DLL:vxres.dll /TYPE:"Volume Manager Disk Group"
- cluster /regext:vxresext.dll
Still not working, i have completely removed VSFW from node 1 and reinstalled with/without node 2 powered on. I have an open case with Symantec, but have not gotten anywhere yet on this issue. I can provide any more details if any one has run into this issue before. Thanks
Event ID: 1058
"The Cluster Resource Monitor could not load the DLL vxres.dll for resource type Volume Manager Disk Group."
I have already deleted the retype from node 1 and re-registered the retype as follows
- cluster restype "Volume Manager Disk Group" /Delete /TYPE
Then
- regsvr32 vxresext.dll
- cluster restype "Volume Manager Disk Group" /CREATE /DLL:vxres.dll /TYPE:"Volume Manager Disk Group"
- cluster /regext:vxresext.dll
Still not working, i have completely removed VSFW from node 1 and reinstalled with/without node 2 powered on. I have an open case with Symantec, but have not gotten anywhere yet on this issue. I can provide any more details if any one has run into this issue before. Thanks
ASKER
That is the same article I found on this issue as well. After working on this more I have found the answer. It turned out to be that my path statement was too long and vertias was at the end of the path statement. I moved the statement to the front of the path on the server, rebooted and that has fixed the issue. Thanks for the help though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://seer.support.veritas.com/docs/269703.htm