| Author |
Message
|
| sashi1977 |
 Posted: Sun Nov 07, 2004 11:15 pm Post subject: WBIMB Getting Started error |
 |
|
Novice
Joined: 31 Aug 2004
Posts: 16
|
Hi, I've just installed WBIMB 5 on a Win XP Pro SP2, and also installed Fix Pack 4 on top of it too. I also followed some of the advice on the Fix Pack 4 readme file, before running the Getting Started wizard.
(I'd also installed WebSphere MQ 5.3 CSD08, DB2 8.2 Enterprise Server Edition, JRE 1.5, and MDAC 2.7 SP1 Refresh).
Initially I had a problem connecting to the Configuration Manager, but after reading the error log, I discovered that the IBM MQSeries Broker ConfigMgr service was disabled (found it under Control Panel --> Administrative Tools --> Services). I enabled it, and then ran the wizard again, but this time I got another error i.e.
| Code: |
| Unable to connect to WBRK_QM (Error: 2009) |
I've looked through the posts on this forum regarding this problem (and there's quite a few of 'em) but I've been unable to find a concrete solution for it.
Would really appreciate any assistance provided. Thank you! |
|
| Back to top |
|
 |
| kirani |
| Posted: Sun Nov 07, 2004 11:24 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Is your queue manager running? 2009 error code means MQRC_CONNECTION_BROKEN.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| sashi1977 |
| Posted: Sun Nov 07, 2004 11:54 pm Post subject: |
|
|
Novice
Joined: 31 Aug 2004
Posts: 16
|
| kirani wrote: |
| Is your queue manager running? 2009 error code means MQRC_CONNECTION_BROKEN. |
Yup. WBRK_QM is running. I also allowed remote administration. (I don't know if it has anything to do with the error, but I thought I'd give it a go anyway).
A more complete error message is (from my notes):
Error BIP0915E Unable to communicate with the Configuration Manager. WBRK_QM cannot be reached.
A runtime error occurred during java.lang.reflect.InvocationTargetException while Adding broker [WBRK_DOMAIN] to domain in workspace. |
|
| Back to top |
|
|
| sashi1977 |
| Posted: Mon Nov 08, 2004 1:40 am Post subject: |
|
|
Novice
Joined: 31 Aug 2004
Posts: 16
|
OK, this just got crazy. I've been talking to a support guy from IBM about my problem, and after running through every permutation of solutions we could think of, he finally suggested that I stop using the Getting Started wizard, and uninstall and re-install everything, and finally configure everything manually.
His reason? Apparently, the wizard doesn't work most of the time.
 |
|
| Back to top |
|
|
| nathanw |
| Posted: Mon Nov 08, 2004 3:43 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
check your install paths
this can cause problems
basically every time I isntall WBIMB i change the path to something like
*:\IBM\WBIMB
i use this principle for all websphere products and never have probs with connection etc |
|
| Back to top |
|
|
| chenulu |
| Posted: Tue Nov 09, 2004 9:16 am Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
| There are issues with the Getting started wizard (never worked). Creating the objects manually works all the time. |
|
| Back to top |
|
|
| jdlennon |
| Posted: Tue Nov 09, 2004 11:43 am Post subject: |
|
|
Novice
Joined: 07 Oct 2004
Posts: 19
Location: The Villages, FL
|
This may be dumb question but when you installed MQ, did you include the Java stuff? If not - it can't connect to the QM.
_________________
Jill D Lennon |
|
| Back to top |
|
|
| chenulu |
| Posted: Tue Nov 09, 2004 12:16 pm Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
| I don't think it has anything to do with MQ Java. Otherwise the manual creation of objects would also fail. In this case the wizard creates the objects that it needs but fails while connecting to the ConfigMgr. |
|
| Back to top |
|
|
| jdlennon |
| Posted: Tue Nov 09, 2004 5:17 pm Post subject: |
|
|
Novice
Joined: 07 Oct 2004
Posts: 19
Location: The Villages, FL
|
Well, as I said, it is a long shot but that is the type of error the Tookit gives if you have not installed MQ Java stuff because it tries to connect as a Java Client. But - as I said, probably not in this case.
_________________
Jill D Lennon |
|
| Back to top |
|
|
| sashi1977 |
| Posted: Tue Nov 09, 2004 10:48 pm Post subject: |
|
|
Novice
Joined: 31 Aug 2004
Posts: 16
|
It turned out to be something very simple, after all.
When I did the default configuration for WebSphere MQ, it created a default queue manager that had port 1414 assigned to it.
Of course, after having installed WMQ and ran the First Steps and all, I completely forgot about it and when running the WBIMB Getting Started wizard, I entered 1414 for the port for WBRK_QM.
That was why WBIMB couldn't connect. Removing all the queue managers in WMQ, and restarting the Getting Started wizard, sorted it out.
Like I said, it was something simple, after all.  |
|
| Back to top |
|
|
|
|
