| Author |
Message
|
| Blobtastic |
 Posted: Wed Dec 03, 2003 2:13 am Post subject: Problem deploying default config in WBIMB v5 |
 |
|
Apprentice
Joined: 03 Nov 2003
Posts: 34
Location: uk
|
Hi all,
I'm trying to install a local version of WBIMB v5.0 for evaluation, and I've selected 'create a default configuration', just so that I can have a 'play' with the product.
I've installed MQ5.3 CSD 5 and DB2 8.1 fixpack 2, all without any apparent problems.
The script seemd to run a long way through - creates and connects to databases, creates QM,broker, configmgr, starts them etc, but then fails with BIP0915E Message brokers toolkit is unable to communicate withe the configuration manager.
the detail reason of:-
'Could not connect to MQ Queue Manager WBRK_QM (reason code = 2009)'
Has anyone seen this before, or can anyone offer any help ? I've tried rebooting and rerunning, but get the same problem. |
|
| Back to top |
|
 |
| Boolean |
| Posted: Wed Dec 03, 2003 3:17 am Post subject: |
|
|
Acolyte
Joined: 05 Jun 2003
Posts: 56
Location: Sweden
|
Unless you use WBIMB v5.0 with CSD02 you can expect these kind of problems.
And I think that you will need DB2 8.1 fixpack 3 with the above.
_________________
/ Boolean |
|
| Back to top |
|
|
| Blobtastic |
| Posted: Wed Dec 03, 2003 3:20 am Post subject: |
|
|
Apprentice
Joined: 03 Nov 2003
Posts: 34
Location: uk
|
Thanks Anders.
I'll update to those two levels and try again - I may be back later!
many thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 03, 2003 6:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Blobtastic wrote: |
Thanks Anders.
I'll update to those two levels and try again - I may be back later!
many thanks |
The other thing is NEVER try running WMBIMB v5 without applying CSD01 AT LEAST.
CSD01 is required. The GA version is DOA.   
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Blobtastic |
| Posted: Wed Dec 03, 2003 8:49 am Post subject: |
|
|
Apprentice
Joined: 03 Nov 2003
Posts: 34
Location: uk
|
Bad news guys,
I've applied the latest CSD's and fixpacks available, and get exactly the same error.
That was having done a restart on the PC, so I'll try a proper reboot overnight and see how it looks in the morning.
Failing that, any more ideas? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 03, 2003 9:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you even started the GA version Toolkit, without installing CSD01 first, you will have to uninstall everything and reinstall.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Blobtastic |
| Posted: Tue Dec 09, 2003 3:43 am Post subject: |
|
|
Apprentice
Joined: 03 Nov 2003
Posts: 34
Location: uk
|
Hmm, bad news.
Uninstalled WBIMB and reinstalled with CSD02 before doing anything, but still got exactly the same problem.
I'm quite happy to uninstall everything (DB2, MQSeries and WBIMB) and reinstall if someone can tell me a) is that necessary and b) what the correct order of install is!
With DB2, if I install fixpack 2 on 8.1, it all looks ok, but if I add fixpack 3 on top it tells me I've got fixpack 0! That being the case, it may be safer with fixpack 2?
I've also got MQSeries 5.3, CSD 5, and WBIMB v5.0, CSD 2
As always, any advice or assistance gratefully received. |
|
| Back to top |
|
|
| akmlau |
| Posted: Wed Dec 10, 2003 11:17 am Post subject: |
|
|
Novice
Joined: 10 Dec 2003
Posts: 12
|
I would recommend going with DB2 8.1 fixpack 4.
But that shouldn't really help with your current problem. What is showing up in your EventViewer (Control Panel --> Administrative Tools --> EventViewer)? It should be logging some warnings/errors that should help diagnose what is wrong.
Also, maybe delete the broker and configmgr using the command line tools before trying the to recreate them again via the Getting started wizard. |
|
| Back to top |
|
|
| jkuehn |
| Posted: Wed Dec 17, 2003 5:48 am Post subject: |
|
|
Newbie
Joined: 17 Dec 2003
Posts: 4
Location: Halifax, Nova Scotia, Canada
|
Hi All:
I recently installed V5 in our environment. I had the exact same symptoms. I called IBM support and the suggested some things to try. However in the end, I found out what was wrong...
When MQI installs, it creates the Config Mgr service and all Broker services as MANUAL, and not Automatic. As such, when you reboot the server, the services are not started. The 2009 error you received, I also received for several days until I noticed the services were stopped. I started the services and could immediately connect. Kink of embarrassing at the time. I remembered afterward encountering this feature of the install during training several years ago with this product.
Good luck.
_________________
John Kuehn
Senior Software Product Analyst
ITOS Systems Enablement
Maritime Life Assurance Co.
(902) 453-7307
jkuehn@maritimelife.ca |
|
| Back to top |
|
|
| nahsay |
| Posted: Tue Feb 17, 2004 1:08 pm Post subject: Re: Problem deploying default config in WBIMB v5 |
|
|
Novice
Joined: 13 Feb 2003
Posts: 15
|
| Blobtastic wrote: |
I'm trying to install a local version of WBIMB v5.0 for evaluation, and I've selected 'create a default configuration', just so that I can have a 'play' with the product.
I've installed MQ5.3 CSD 5 and DB2 8.1 fixpack 2, all without any apparent problems.
The script seemd to run a long way through - creates and connects to databases, creates QM,broker, configmgr, starts them etc, but then fails with BIP0915E Message brokers toolkit is unable to communicate withe the configuration manager.
the detail reason of:-
'Could not connect to MQ Queue Manager WBRK_QM (reason code = 2009)'
Has anyone seen this before, or can anyone offer any help ? I've tried rebooting and rerunning, but get the same problem. |
My search led me to this thread because I am experiencing similar problems.
My error message is different than the OP, mine says:
| Quote: |
Could not connect to MQ Queue Manager "WBRK_QM" (reason code=2195)
|
I know for a fact that the queue manager in question is running. I also have the latest CSD and fixpacks installed for DB2, WBIMB and MQ. I even checked to see that the appropriate services are running as suggested by jkuehn.
I can provide more information or logs upon request. Any ideas because I am now stuck. Thanks.  |
|
| Back to top |
|
|
| apsy |
| Posted: Wed Feb 18, 2004 6:22 am Post subject: |
|
|
Novice
Joined: 10 Feb 2004
Posts: 24
|
This is what I got on iBM's MQ manuals regarding error code 2195
2195 X'0893' MQRC_UNEXPECTED_ERROR
The call was rejected because an unexpected error occurred.
Corrective action: Check the application's parameter list to ensure, for example, that the correct number of parameters was passed, and that data pointers and storage keys are valid. If the problem cannot be resolved, contact your system programmer.
On z/OS, check whether any information has been displayed on the console. If this error occurs on an MQCONN or MQCONNX call, check that the subsystem named is an active WebSphere MQ subsystem. In particular, check that it is not a DB2 subsystem. If the problem cannot be resolved, rerun the application with a CSQSNAP DD card (if you have not already got a dump) and send the resulting dump to IBM.
On OS/2 and OS/400, consult the FFST record to obtain more detail about the problem.
On Compaq OpenVMS Alpha, Compaq NonStop Kernel, and UNIX systems, consult the FDC file to obtain more detail about the problem. |
|
| Back to top |
|
|
| nahsay |
| Posted: Wed Feb 18, 2004 7:48 am Post subject: |
|
|
Novice
Joined: 13 Feb 2003
Posts: 15
|
| Thanks for the information from the manual but what do I do on a Win2k Pro box? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 18, 2004 8:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| yashan wrote: |
| Thanks for the information from the manual but what do I do on a Win2k Pro box? |
Check your Application log in Event Viewer for more information.
Post the top portion of any FDC files here, or search www.software.ibm.com for the probe ID.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jkuehn |
| Posted: Mon Feb 23, 2004 9:44 am Post subject: Connect error 2009 is an MQ error, not MQI |
|
|
Newbie
Joined: 17 Dec 2003
Posts: 4
Location: Halifax, Nova Scotia, Canada
|
Several things to try...
1) Verify that the Queue Mgr port number (Default 1414) you setup WBRK_QM on is the same one you are trying to connect Broker toolkit to.
2) Ensure that MQSeries, and Config Mgr are both started. Config Mgr service is set to manual on install so will not start at reboot until set to Automatic.
3) Ensure the account you are using is in MQM local group. You will have to reboot to make group change effective.
4) User MQSeries First Steps and exercise the API to ensure you can open the QM yourself.
_________________
John Kuehn
Senior Software Product Analyst
ITOS Systems Enablement
Maritime Life Assurance Co.
(902) 453-7307
jkuehn@maritimelife.ca |
|
| Back to top |
|
|
| nahsay |
| Posted: Mon Feb 23, 2004 10:58 am Post subject: |
|
|
Novice
Joined: 13 Feb 2003
Posts: 15
|
| jefflowrey wrote: |
Post the top portion of any FDC files here, or search www.software.ibm.com for the probe ID. |
Can you please elaborate? I do not understand what you want me to post or what the probe ID is. Thanks. |
|
| Back to top |
|
|
|
|
