|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
haregtyp unable to register WMQ |
« View previous topic :: View next topic » |
Author |
Message
|
longhorn |
Posted: Fri Jul 10, 2015 6:49 am Post subject: haregtyp unable to register WMQ |
|
|
Novice
Joined: 22 May 2014 Posts: 14
|
Hi,
Just wondering if anyone else has come across this error.
OS: windows Server 2008 Enterprise R2 64 bit
WMQ 7.0.1.12
I have 2 windows 2008 64 bit VMs configured. They are part of a domain and they can ping each other ok etc.
I have installed MQ 7.0.1.12 (I know it's going out of support in September...) on both nodes and have run the full validate cluster configuration task against both nodes and it passed. So I know that IPs/network, shared storage, disk arbitration etc is all fine.
When I try to run haregtyp /r to register WebSphere MQ as an MSCS resource type, I keep on getting the error:
Code: |
C:\Windows\system32>haregtyp /r
An unexpected error occurred whilst registering the IBM WebSphere MQ MSCS resour
ce library with MSCS.
Usage: haregtyp /r | /u
|
I have rebooted the server (a few times) but still can't get rid of that error. There's no entry in the registry to contradict the error that I see. The userid I'm using is a member of mqm and the mqm group itself is a member of the domain mqm group.
Has anyone come across this?
Incidentally a couple of days prior to this, I was able to run the haregtyp cmd successfully and complete the configuration on 2 other nodes but these were 32 bit nodes. Is there something extra/different that is required in order to run the haregtyp command on a 64 bit setup? I wouldn't have thought so.....
Thanks, |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Jul 10, 2015 8:03 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
I believe you need to be a local administrator on the box to run haregtyp.
You will need to have rights to the registry. Talk to your windows administrator...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
longhorn |
Posted: Fri Jul 10, 2015 12:47 pm Post subject: |
|
|
Novice
Joined: 22 May 2014 Posts: 14
|
Thanks for taking the time to respond. I was using a local admin account.
For others who might come across this, the simple solution is that the command must not be run until after the MSCS cluster has been created! |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|