Problem configuring MSMQ. CS ERROR V-16-10041-17025 MSMQ:INSTANCENAME-MSMQ:monitor:Failed to validate storage configuration. Error 2

Article:TECH160579  |  Created: 2011-05-22  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH160579
Article Type
Technical Solution


Environment

Issue



Cluster resource MSMQ  fails to probe and fails to come online. MSMQ log shows entry as


VCS ERROR V-16-10041-17025 MSMQ:INSTANCENAME-MSMQ:monitor:Failed to validate storage configuration. Error 2
 


Error



VCS ERROR V-16-10041-17025 MSMQ:INSTANCENAME-MSMQ:monitor:Failed to validate storage configuration. Error 2

This error translates to :

  ERROR_FILE_NOT_FOUND   # The system cannot find the file specified.
 


Environment



Windows 2008 R2 Server

Storage Foundation-HA for Windows v.5.1 SP2
Enterprise Vault v.9.1

Microsoft Queuing (MSMQ)


Cause



MSMQ  Instance name in the registry, didnt match the one specified in VCS  Service Group


Solution




Please check the following

1) Ensure that VCS is started on all systems.

2) Ensure that all the required resources are online.

3) Ensure that the volume or LUN for the MSMQ data is mounted or connected on the node on which you are configuring the MSMQ resource.

4) Confirm and verify the MSMQ  name in Veritas Cluster. For example EVault-MSMQ

5) Check and confirm that the MSMQ preconfiguration file exists. Default location is   c:\windows\system32\drivers\InstanceName-MSMQ.sys. For example c:\windows\system32\drivers\EVault-MSMQ.sys

If does not exist then run the following command:

C:\>msmqconfig -c -n EVault-MSMQ -s S1 S2 -m X:\MSMQ\Storage

In above example, the MSMQ resource name is EVault-MSMQ, nodes in the system
list are S1 and S2, and the storage path created is X:\MSMQ\Storage.

6) Check and verify the instance name in the registry. Example shows synatax if the instance is EVault-MSMQ

HKLM\Software\Microsoft\MSMQ\Clustered QMs\MSMQ$EVault-MSMQ

7) Check and verify that the MSMQ resource name  naming convention is correct. If the resource name is EVault-MSMQ, then the (VCS) MSMQ Monitor will be looking for it in the registry, at the following default Microsoft location.
 
HKLM\SOFTWARE\Microsoft\MSMQ\Clustered QMs\Evault-MSMQ\Parameters

The instance name (Evault-MSMQ in the above example) must match the MSMQ Instance name that has been defined. If not, then export the registry key for backup reasons and modify it appropriately to match the instance name.


8) If all above fails then, delete the service group which contains the MSMQ resource, delete all entries of MSMQ from the registry and from the data volumes (e.g. G:\MSMQ); and re-create the whole service group again following the step-by-step instructions on P.330 of the Veritas Cluster Administrators Guide, in the section titled "Configuring the MSMQ resource"


 





Article URL http://www.symantec.com/docs/TECH160579


Terms of use for this information are found in Legal Notices