1. Reboot the failing node.
2. Verify that no failed providers exist for this node. This can be verified by opening up VEA and going to Properties of the connected host (default is Localhost). At the bottom, it will show failed providers. If there are failed providers, look to PATH statement being too long as the culprit to this.
3. Try to reinstall MSCS option by deselecting it and then reselecting it again.
4. Try TN 269703 that is linked below to re-register. You may get an error on step 2 as the resource already exists so this would be expected.
5. Make sure that "vxres.dll" exists in the Cluster folder (%systemroot%\Cluster) and that logged on account has full control permission to this folder.
6. *****Before doing step 6 - Please be sure to backup the registry in case something goes wrong. This value should not cause any problems, but if you are concerned about this please contact Microsoft regarding assistance with this*****
If the issue is related to not being able to get the node as a Possible Owner - you can stop the cluster service on both nodes and edit the registry by going to: HKLM\Cluster\ResourceTypes\Volume Manager Disk Group\PossibleNodes. If you double click this key you will see if it is not registering properly that it will just show a 1 in there. If you go to the other Resource Types that are working, you will see that they look like this:
So, you can edit this value to match exactly like them and do this for all nodes in the cluster and then reboot the boxes. If you do not reboot, you will more than likely receive other errors so this is important.
If you are still experiencing problems after doing this, please contact Symantec Support to determine if this is a Microsoft issue or a Symantec issue.
The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.
Rate this Article