| Author |
Message
|
| arun57 |
 Posted: Mon Jan 14, 2008 4:49 am Post subject: Error while creating configuration manager |
 |
|
Novice
Joined: 14 Jan 2008
Posts: 21
|
hi,
I have installed on my computer (Windows XP) IBM MQ v6 and IBM Message Broker 6.
I am trying to create default configuration manager and I am getting the error below when the ConfigManager is being created. User "157116" is what I use when I log into my machine. How can I work around this problem?
I am new to this software so detailed instructions would be great.
D:\Program Files\IBM\MessageBrokersToolkit\6.0>CALL mqsicreatedb DEFBKDB6 -i 157116 -a **********
BIP9824I: Creating the DatabaseInstanceMgr Service Component.
BIP9832I: Starting the DatabaseInstanceMgr Service Component.
BIP9828I: Connecting to the Cloudscape Network Server on port 1527.
BIP9809I: Creating Derby Database 'DEFBKDB6', this may take a while.
BIP9829I: Cataloging the Derby Database 'DEFBKDB6'.
BIP9818I: IBM Cloudscape/Apache Derby was used to create the 'DEFBKDB6' database.
BIP8071I: Successful command completion.
D:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Mon Jan 14 17:45:40 IST 2008]
Creating the Configuration Manager. [WBRK6_DEFAULT_CONFIGURATION_MANAGER]
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the Configuration Manager.
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\Program Files\IBM\MQSI\6.0
D:\Program Files\IBM\MessageBrokersToolkit\6.0>mqsicreateconfigmgr -i 157116 -a ********** -q WBRK6_DEFAULT_QUEUE_MANAGER WBRK6_DEFAULT_CONFIGURATION_MANAGER
BIP8134E: Unable to alter WebSphere MQ Queue Manager 'WBRK6_DEFAULT_QUEUE_MANAGER'.
This command attempts to alter a WebSphere MQ Queue Manager, the Queue Manager could not be altered.
Locate and resolve the problem and retry the command. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jan 14, 2008 4:54 am Post subject: Re: Error while creating configuration manager |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| arun57 wrote: |
D:\Program Files\IBM\MessageBrokersToolkit\6.0>mqsicreateconfigmgr -i 157116 -a ********** -q WBRK6_DEFAULT_QUEUE_MANAGER WBRK6_DEFAULT_CONFIGURATION_MANAGER
BIP8134E: Unable to alter WebSphere MQ Queue Manager 'WBRK6_DEFAULT_QUEUE_MANAGER'.
This command attempts to alter a WebSphere MQ Queue Manager, the Queue Manager could not be altered.
Locate and resolve the problem and retry the command. |
Going out on a limb, I'd say that the user 157116 is unable to alter the queue manager "WBRK6_DEFAULT_QUEUE_MANAGER"; just a guess you understand. 
I'd check the queue manager logs to locate & resolve the problem. After you've checked that user id has the correct rights with the queue manager... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| arun57 |
| Posted: Mon Jan 14, 2008 5:06 am Post subject: |
|
|
Novice
Joined: 14 Jan 2008
Posts: 21
|
| i checked user accounts. 157116 has the mqm as well as mqbrkrs rights. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 14, 2008 5:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| arun57 wrote: |
| i checked user accounts. 157116 has the mqm as well as mqbrkrs rights. |
Ok, not an authorisation problem, so it's not the most likely cause. Oh well. 
What do the logs say?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| arun57 |
| Posted: Mon Jan 14, 2008 5:12 am Post subject: log files.. |
|
|
Novice
Joined: 14 Jan 2008
Posts: 21
|
D:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: []
+++++++++++++++++++++++++++++++++++ task trace +++++++++++++++++++++++++++++++++++++++++++++
TIMESTAMP [Mon Jan 14 18:32:13 IST 2008]
Creating the Configuration Manager. [WBRK6_DEFAULT_CONFIGURATION_MANAGER]
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the Configuration Manager.
Collected output from task >
Stdout: [MQSI 6.0.0.1
C:\Program Files\IBM\MQSI\6.0
D:\Program Files\IBM\MessageBrokersToolkit\6.0>mqsicreateconfigmgr -i 157116 -a ********** -q WBRK6_DEFAULT_QUEUE_MANAGER WBRK6_DEFAULT_CONFIGURATION_MANAGER
BIP8134E: Unable to alter WebSphere MQ Queue Manager 'WBRK6_DEFAULT_QUEUE_MANAGER'.
This command attempts to alter a WebSphere MQ Queue Manager, the Queue Manager could not be altered.
Locate and resolve the problem and retry the command.
D:\Program Files\IBM\MessageBrokersToolkit\6.0>exit]
Stderr: [WebSphere MQ queue manager created.
Creating or replacing default objects for WBRK6_DEFAULT_QUEUE_MANAGER.
Default objects statistics : 43 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
WebSphere MQ queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' starting.
5 log records accessed on queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' during the log replay phase.
Log replay for queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' complete.
Transaction manager state recovered for queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER'.
WebSphere MQ queue manager 'WBRK6_DEFAULT_QUEUE_MANAGER' started.] null |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 14, 2008 5:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Sorry, I should have been more specific. I'm not saying the queue manager's not started, I meant what error messages did the alter attempt generate in the queue manager log?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| arun57 |
| Posted: Mon Jan 14, 2008 5:31 am Post subject: |
|
|
Novice
Joined: 14 Jan 2008
Posts: 21
|
EXPLANATION:
WebSphere MQ, running with the authority of user 'musr_mqadmin@pc007939', was
unable to retrieve group membership information for the specified user.
ACTION:
Ensure Active Directory access permissions allow user 'musr_mqadmin@pc007939'
to read group memberships for user '157116@cts'. To retrieve group membership
information for a domain user, MQ must run with the authority of a domain user.
----- amqzfubn.c : 3582 -------------------------------------------------------
1/14/2008 18:58:55 - Process(2076.106) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
AMQ8079: Access was denied when attempting to retrieve group membership
information for user '157116@cts'. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 14, 2008 5:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Ah - the old "domain user" gag! 
If you search this forum you'll find reams of posts discussing the joys and pitfalls of using WMQ in a Windoze Domain environment. The problem, as you've undoubtably deduced from the error, is that MQ is unable to obtain the information it needs to authenticate actions & prove group membership. Do the search and you'll find loads of information on strategies, workrounds and fixes.
It's more an issue with Windoze than MQ - my personal view (and I offer it as nothing more than that) is that MQ works best running as a local user with local admin rights. Add other users to the local setup as you need.
Happy searching and good luck!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| arun57 |
| Posted: Mon Jan 14, 2008 5:46 am Post subject: |
|
|
Novice
Joined: 14 Jan 2008
Posts: 21
|
thanks a lot..  |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 14, 2008 8:16 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| Vitor wrote: |
| It's more an issue with Windoze than MQ - my personal view (and I offer it as nothing more than that) is that MQ works best running as a local user with local admin rights. Add other users to the local setup as you need. |
If you are only going to need to authenticate local user IDs then this works just fine and is preferred in my opinion as well.
As soon as you need to authenticate domain IDs, then you must run MQ under a domain account in a particular domain group (details in the Windows MQ Quick Beginnings manual). Note that if you are running on a Microsoft Hardware Cluster you have to deal with authenticating a domain ID even if you hard code an MCAUSER on the channel(s). This is because the SIDs will be different for the User1 ID (for example) if you define "User1" on each server in the MSFT hardware cluster. The MQ Authorities are actually applied to the SID and not the friendly name on Windows.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| arun57 |
| Posted: Wed Jan 16, 2008 2:04 am Post subject: |
|
|
Novice
Joined: 14 Jan 2008
Posts: 21
|
BIP8134E: Unable to alter WebSphere MQ Queue Manager 'WBRK6_DEFAULT_QUEUE_MANAGER'.
This command attempts to alter a WebSphere MQ Queue Manager, the Queue Manager could not be altered.
Locate and resolve the problem and retry the command.
this is the exact error i am getting. Is this because of difference between domain id and local id. how can i solve it? please help. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 16, 2008 2:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| arun57 wrote: |
| Is this because of difference between domain id and local id. how can i solve it? please help. |
Yes. Have you reconfigured as sugested in this thread, or used one of the other posted methods?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
