|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Broker is shown stopped on ISO2 |
« View previous topic :: View next topic » |
Author |
Message
|
KIT_INC |
Posted: Mon May 26, 2008 4:48 am Post subject: Broker is shown stopped on ISO2 |
|
|
Knight
Joined: 25 Aug 2006 Posts: 589
|
I installed ISO2 supportpac on my test system (WINXP WMB V6 csd05). But my broker is shown as stopped.Bit the broker is actually running.
I tried to start it. It come back with an error
"Task: Starting the Broker "BKR1" failed
If you can manually fix the issues that caused this task to fail, do so and then click Yes. If you click Yes, the wizard starts the task again.
If you click No, the wizard rolls back all completed tasks, if roll-back is possible.
To establish why the task failed, examine this wizard's log file which can be found in the workspace
directory [C:\Documents and Settings\kit-inc\Application Data\IBM\MQ Explorer\.metadata].
I excamine the CommandAssistantWizard.log as instructed. But it only says
26 08:44:48 EDT 2008]
Starting the Broker "BKR1"
Status ERROR: com.ibm.etools.wmadmin.broker.runtime code=0 Could not start the broker BKR1 null
Any suggestion ? |
|
Back to top |
|
 |
KIT_INC |
Posted: Mon May 26, 2008 5:30 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006 Posts: 589
|
I have WMB Toolkit running on the same Windows XP. I am able to connect to the borker and configmgr running on the same box. Unless the broker explorer is trying to connect with a different ID than my logon ID, then it may be a security problem. |
|
Back to top |
|
 |
dstorey |
Posted: Tue May 27, 2008 2:47 am Post subject: Reset your Saved State? |
|
|
 Novice
Joined: 25 Mar 2002 Posts: 15 Location: UK
|
Hello,
If you only have local brokers you could try reseting the broker explorers saved state.
Window->Preferences->Broker Explorer -> Remove all Broker Explorer Saved State
We use the PID of the Broker held in the registry to determine if the local broker is stopped or started. A non zero value should display an active broker.
Good Luck,
Dom |
|
Back to top |
|
 |
dstorey |
Posted: Tue May 27, 2008 5:09 am Post subject: |
|
|
 Novice
Joined: 25 Mar 2002 Posts: 15 Location: UK
|
Hello,
Another possibility is that your windows/ linux logon password has recently been changed and you need to change this within the broker and configuration manager.
Use the commands:
mqsichangebroker <BROKERNAME> -i <userid> -a <password>
mqsichangeconfiguration manager <CONFIGURATIONMANAGERNAME> -i <userid> -a <password>
You also may need to change your service logon password.
Good Luck,
Dom |
|
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
|
|
|
|