04-19-2011 05:44 AM
Hi all,
We have a clustered instance of EV9 on windows 2008 r2 x64 Under VSFW HA 5.1SP2, The EV configuration wizards were used to create the service group. Post configuration we have two issues.
1. MSMQ log states that the MSMQ Storage Path is not configured (Selected the mount points for MSMQ Data and registry replication during configuration) which are G:\MointPoints\EV_MSMQ, and G:\MointPoints\EV_RegRep. However the MSMQ storage path in the VCS resource is empty (Checked the clustered MSMQ Instance within App Manager and can see that the paths are correct) we have tried all path combinations with no luck.
2. The mount point associated with MSMQ cannot unmount when VCS attempts to offline, even if we stop HAD and use VEA to remove the mount point this fails (Handle shows no open handles to the Volume/mount)
Does anybody have any experience with EV MSMQ configuration? and more importantly what the best practice/configuration steps are to ensure the clustered MSMQ (Created by the wizard) is used and not the local message queueing service?
Many thanks guys.
Regards
Lee
Solved! Go to Solution.
06-15-2011 04:50 PM
Hi guys,
This was resolved by moving MSMQ to its own Mount Point, in this case (H:) Once that was doen the wizard had no problem and the service group creation completed without issue.
So to summarise, If the MSMQ mount is under the same parent folder as the EV volumes the wizard fails and/or after manual service group creation, the MSMQ MountV will fail to offline. Once MSMQ is moved to its own MountV all works as expected.
MAIN.CF (section)
MSMQ S-EVC001P-SG-MSMQ (
IPResName = S-EVC001P-SG-IP
LanmanResName = S-EVC001P-SG-Lanman
MountResName = S-EVC001P-SG-MountV-H
StoragePath = "\\EV_MSMQ"
)
MountV S-EVC001P-SG-MountV-H (
MountPath = "H:"
VolumeName = EV_MSMQ
VMDGResName = S-EVC001P-SG-VMDg
)
Regards
Lee
04-19-2011 01:35 PM
Hi Lee,
It sounds like the wizard may have had problems configuring the service group. You can check the %vcs_home\log\ folder for the EV Wizard log to see if it has any errors.
From there you might try running the EV wizard again and select modify for the EV group that you have configured. Or you can simply change the MSMQ resource's path attribute manually.
As for the MountV not going offline, the MountV_A.txt log might have some more details on why. But if you think it is an open handle then you can change the ForceUnmount attribute to "ALL" and set the AutoFSClean attribute to True. This will make the MountV agent try to break all handles that are on the volume and clean the filesystem if there are any problems.
Other than that, it is a matter of determining what is touching the volume. MountV has the ListApplications attribute that might help but it might not. You can try shutting down all unneeded services until you find what is touching the drive then stop it or put it under cluster control.
Thanks,
Wally
04-19-2011 09:14 PM
Hi Wally,
This is what is shown in the EV Wizard log with regards to MSMQ.
04-19-2011 09:17 PM
Hi Wally, many thanks for the feedback, I have tried all of that and have included some of the log outputs below
MountV-A
04-21-2011 07:54 AM
Hi Lee,
From the MountV log the code [2:5] is access denided. I'm not sure exactly why we are getting access denied when trying to offline the MountV.
The MSMQ error of 1058 is a standard windows error:
C:\>net helpmsg 1058
The service cannot be started, either because it is disabled or because it has n
o enabled devices associated with it.
The EV wizard does show the MSMQ path as G:\MountPoints\EV_MSMQ.
It is not uncommon for handle.exe to not show what has a open handle on the drive. There are sometimes handles that are very transitive in nature and handle.exe pooling interval does not always grab these handles.
I would recommend opening a case with Symantec Technical Support to continue working this issue.
Thanks,
Wally
06-15-2011 04:50 PM
Hi guys,
This was resolved by moving MSMQ to its own Mount Point, in this case (H:) Once that was doen the wizard had no problem and the service group creation completed without issue.
So to summarise, If the MSMQ mount is under the same parent folder as the EV volumes the wizard fails and/or after manual service group creation, the MSMQ MountV will fail to offline. Once MSMQ is moved to its own MountV all works as expected.
MAIN.CF (section)
MSMQ S-EVC001P-SG-MSMQ (
IPResName = S-EVC001P-SG-IP
LanmanResName = S-EVC001P-SG-Lanman
MountResName = S-EVC001P-SG-MountV-H
StoragePath = "\\EV_MSMQ"
)
MountV S-EVC001P-SG-MountV-H (
MountPath = "H:"
VolumeName = EV_MSMQ
VMDGResName = S-EVC001P-SG-VMDg
)
Regards
Lee