| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MB default config Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| prasannanb |
 Posted: Mon Nov 30, 2009 6:37 am Post subject: MB default config Error |
 |
|
Apprentice
Joined: 17 Apr 2009
Posts: 35
|
Hi,
I am very new to message broker and I am trying to setup the MB environment.
I have installed all the necessary sofwares and when I try to run the "Default Configuration wizard" I am getting below error in DefaultConfigurationWizard.log
----------------------------------------------------------------------------------------------------------
C:\Program Files\IBM\WMBT610>mqsistart WBRK61_DEFAULT_CONFIGURATION_MANAGER
BIP8015E: The component cannot be started.
The command cannot start the required component.
The possible causes of this error are: insufficient user ID permissions; lack of system resources (not enough memory); the &mqproduct; environment is not configured correctly for the user who is running the command (for example, the mqm library is missing from the user's path).
----------------------------------------------------------------------------------------------------------
In the windows event viewer -
Timeout (30000 milliseconds) waiting for the IBM WebSphere Message Broker component WBRK61_DEFAULT_CONFIGURATION_MANAGER service to connect.
The IBM WebSphere Message Broker component WBRK61_DEFAULT_CONFIGURATION_MANAGER service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
----------------------------------------------------------------------------------------------------------
The error BIP8015E looks very general and the user id is part of Administrator, DB2ADMNS, mqbrkrs and mqm group.
I am not able to fix this. Could anybody please help me?
Thanks in advance,
Prasanna |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Nov 30, 2009 7:04 am Post subject: Re: MB default config Error |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prasannanb wrote: |
The error BIP8015E looks very general and the user id is part of Administrator, DB2ADMNS, mqbrkrs and mqm group.
|
And yet it contains advice. Have you investigated anything other than authorities?
| prasannanb wrote: |
| I am not able to fix this. Could anybody please help me? |
I'd go with the "environment not configured correctly". As this is Windows, make sure you've restarted a few times. Verify the underlying WMQ set up is working correctly, and look for other event log messages.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| student |
| Posted: Mon Nov 30, 2009 8:09 am Post subject: |
|
|
Apprentice
Joined: 17 Mar 2009
Posts: 31
Location: UK
|
| First verify wether you are able to execute normal commands like dspmq, mqsilist etc.. Does it throws error? Also do you have minimum available memory as recommended by IBM? |
|
| Back to top |
|
|
| agrawalamit166 |
| Posted: Mon Nov 30, 2009 10:52 am Post subject: |
|
|
Voyager
Joined: 17 Aug 2009
Posts: 78
Location: NY, US
|
Please read "WebSphere Message Broker Basics".
There might be a problem due to authorization.
Here are few thing should remember always:
1. The permitted number of characters for the user ID varies according to operating system:
– On Windows, the maximum password length is 12 characters.
– On Linux and UNIX®, the maximum password length is 8 characters.
Databases in the WebSphere Message Broker configuration might also contain additional restrictions, for example, DB2 Universal Database.
2. The case of the user ID should be consistent; use all lowercase or all uppercase letters.
3. On Windows, the Administrator user ID must not be used. Any attempt to use the Administrator user ID with the WebSphere Message Broker run time produces authorization errors.
4. On Windows, the user ID must be a member of the Administrators security group.
It is recommended that user ID and password combinations are valid on all of the operating systems that are involved in your WebSphere Message Broker configuration. |
|
| 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
|
|
|
|
