|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Error starting WebSphere MQ 3.5 CSD07 on WinXP (resolved) |
« View previous topic :: View next topic » |
Author |
Message
|
yortch |
Posted: Sun Oct 03, 2004 4:59 am Post subject: Error starting WebSphere MQ 3.5 CSD07 on WinXP (resolved) |
|
|
Apprentice
Joined: 30 Aug 2004 Posts: 34
|
I have been working with WBI Message Broker 5 for the past few weeks. I stopped using it for a couple of weeks, this morning I tried to start the broker's Queue Manager (I have it set up for manual startup), I'm getting the following error:
Code: |
Error code 71 starting WBRK_QM/Queue Manager WebSphere MQ service.
The service was unable to start WBRK_QM/Queue Manager. The error message reported was as follows: Purchased processor allowance not set (use setmqcap).
AMQ5615: Default objects cannot be created: CompCode = 0 Reason = 0.
Use WebSphere MQ Services to investigate why the service could not begin. If recovery for this service is active, MQ will attempt to recover. |
I already tried running the command setmqcap and setting it to 1, and returns with no error (I've never had to do this before), but I'm still getting the same error.
The only change I've made on my machine between the time it was working and now, is that I installed WebSphere Studio Application Developer Integration Edition, and I chose not to install the Embedded MQ client, although I believe WSADIE needs to install its own for internal use.
I also already tried creating a new queue manager and I'm getting the following error:
Code: |
Unable to create queue manager TEST_QM.
Queue manager TEST_QM could not be created. WebSphere MQ returned error 25: CRTMQM -ld"C:\Program Files\IBM\WebSphere MQ\log" TEST_QM
AMQ7019: An error occurred while creating the directory structure for the new
queue manager.
Check the error and application event logs to investigate the reason for the the returned error and suggested responses to take to rectify the fault. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.
|
When I go into the event log I found messages that point me to an error file that is not being created on my machine:
C:\Program Files\IBM\WebSphere MQ\errors\AMQ01840.19.FDC.
Any help will be greatly appreciated.
Regards,
Jorge
Last edited by yortch on Mon Oct 04, 2004 5:31 pm; edited 1 time in total |
|
Back to top |
|
 |
csmith28 |
Posted: Sun Oct 03, 2004 5:30 am Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
run dspmqcap and make sure the number of "processor allowance" value is the same as the "number of processors in this machine"
If not like the error output says, use setmqcap to correct your processor allowance.
Check your disk space and make sure you have enough room to create an MQManager. Also check the local and Doamin permissions/groups/authority on user ID that you are trying to create the MQManager with.
My best guess is that this is a permissions issue since MQ Attempted to create a .FDC file in it's own file system and failed.
Also note that if the ID you are logged on under is pooched up in regards to security your setmqcap command may be failing too. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
yortch |
Posted: Sun Oct 03, 2004 10:57 am Post subject: |
|
|
Apprentice
Joined: 30 Aug 2004 Posts: 34
|
I just found out that the service wasn’t really starting… the login was incorrect, I set it to use the MUSR_MQADMIN, but the password was incorrect, since I couldn’t remember it, I had to reset it, and the I wasn’t able to browse the queue manager in the MQ Explorer, I found out I had to reset the password in the Components Services, so my issue is resolved, thanks for your help.
Jorge |
|
Back to top |
|
 |
csmith28 |
Posted: Sun Oct 03, 2004 6:42 pm Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
Yeah, when I was young and stupid I couldn't figure out why I could create an MQManager on my Local W2K Workstation, but then after having done so I didn't have the authority to access it.
Weird stuff.
Logged on with my DOMAIN account I could crtmqm -u SYSTEM.DEAD.LETTER.QUEUE -m LONDON and everyting was fine. The MQManager was created but runmqsc LONDON would fail with some forgotten AUTHORIZATION return code.
Much has changed since then. I am older now. =]
It's kinda sick really. I don't believe I will ever be able to forgive Bill Gates for what he has done but what he has done has contributed greatly to my job security.
MMMMMMMMMMBUWAHahahahahahahahahahahaaaaaaaaaaaaaaaa..........
Holds extended pinky to cheak.
MMMMMMMMMMBUWAHahahahahahahahahahahaaaaaaaaaaaaaaaa..........
MMMMMMMMMMBUWAHahahahahahahahahahahaaaaaaaaaaaaaaaa.......... _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
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
|
|
|
|