| Author |
Message
|
| Batman |
 Posted: Fri Apr 16, 2004 5:38 am Post subject: WMBI 5 connection error |
 |
|
Newbie
Joined: 16 Apr 2004
Posts: 6
Location: UK
|
hey all
sort of a newbie question but its really bugging me
have installed WMBI 5 and CSD 2on my laptop with XP pro and MQ 5.3 with CSD 5
go to create a default config and it all works creates queue managers brokers databases etc and then when i try to start the ball rolling and get it all sorted i get a connection error with the queue manager
BIP0951E Unable to communicate with the configuration manager
Queue Manager ***** could not be reached
and then in details
Could not connect to MQ Queue Manager '*****' (reason code=2195)
Any ideas folks
is driving me mad
someone told me that CSD 3 should fix this can anyone confirm?
many thanks |
|
| Back to top |
|
 |
| Batman |
| Posted: Fri Apr 16, 2004 10:17 am Post subject: |
|
|
Newbie
Joined: 16 Apr 2004
Posts: 6
Location: UK
|
as a follow on i am also getting this error associated with MQ Series q managers
A communications error for TCP/IP occurred.
An unexpected error occurred in communications.
The return code from the TCP/IP (ioctlsocket) call was 10038 (X'2736'). Record these values and tell the systems administrator.
have searced alot for a solution to this and dug around but for somereason it wont let the WBI connect to the config manager because of the Q manager
can anyone please help
if this was 2.1 i would have a full and up and running system by now with full on message flows etc but this V5 is a pain!!! |
|
| Back to top |
|
|
| fschofer |
| Posted: Fri Apr 16, 2004 12:59 pm Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
|
| Back to top |
|
|
| Batman |
| Posted: Sat Apr 17, 2004 10:40 am Post subject: |
|
|
Newbie
Joined: 16 Apr 2004
Posts: 6
Location: UK
|
yeh have firewall but why should that effect? silly stuff this
tcp/ip seems ok have followed the instructions but doesnt seem to be fixing the problem
am getting rite annoyed with this
wouldnt want to do a complete reinstall again tbh just want to run the damn broker
am tempted to drop the lot and just do 2.1 lol |
|
| Back to top |
|
|
| fschofer |
| Posted: Sat Apr 17, 2004 1:04 pm Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
|
| Back to top |
|
|
| waugh |
| Posted: Mon Apr 19, 2004 4:41 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
This is what i found when i got this problem sometime ago.
if its on windows, go to folder disthub, by default, c:/program files/ibm/disthub/v2, you should see three folders _uninst, classes, lib...if one of these not there.. you got faulty installation..
when you try to connect to Queue Manager, if you look at the event viewer it actually tells you the same.
Solution:
uninstall and reinstall WBIMB 5.0 and apply CSD 02..( do not open toolkit until you apply CSD 02) |
|
| Back to top |
|
|
| HugoB |
| Posted: Tue Apr 20, 2004 12:11 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 67
|
Or even more effective;
Try this environment variable;
MQNOREMPOOL=1
This needs to be a system variable in you win XP.
After this do a reboot.
This will switch you back to some sort of MQ 5.2 functionality related
to TCP/IP things.
This did the trick for me, i had the same config.
Oh fschofer gives you the correct link i presume. |
|
| Back to top |
|
|
| Batman |
| Posted: Sat Apr 24, 2004 6:31 pm Post subject: |
|
|
Newbie
Joined: 16 Apr 2004
Posts: 6
Location: UK
|
ok guys thanks for the help
just as an update i have done all the above and still get the same error
i really dont see what the problem is tbh
one thing i ahve discovered is that when i am creating a broker environment the install / create routine is NOT creating the appropriate queues or channels within mq and therfore it falls over when attempting to connect as the following error occurs
BIPv500
( WBRK_BROKER ) A problem was detected with WebSphere Business Integration while issuing MQOPEN for WebSphere Business Integration queue 'SYSTEM.BROKER.ADMIN.QUEUE', WebSphere Business Integration queue manager 'WBRK_QM'. MQCC=2, MQRC=2085.
The operation on the specified queue or queue manager returned with the indicated WebSphere Business Integration completion and reason code.
Check the WebSphere Business Integration completion and reason codes in the WebSphere Business Integration Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action. If an MQOPEN was unsuccessful because the queue manager or queue did not exist, then define these objects to WebSphere Business Integration. If the problem was because incorrect object names were specified, then the message broker will try to recover, if the problem
and yes i did define the objects manually after, well up to the point i felt like throwing the laptop out of the window 
have used ibm middleware in its various guises for 4 years now (used to be on here a bit but forgot sign in and stuff) and am not a total newbie to wmqi/mq etc
been involved in alot of projects on 2.1 and tbh this has foxed me completely
i have the oppurtunity to have a 2nd hard drive for my laptop with a win2000 install which i am going to use for business involving wmqi5 etc and other stuff and keep my current hard drive for all my other bits and pieces
i reckon its a xp.mq/wmqi communications thing and until i hear of a bona fide solution / upgrade / install package i am going to remove it from my xp system
all i can say is that its a major pain in the ass for this to happen as it means jumping about between systems
if i was a complete newbie with no experience i would probably be on here all the time but with the knowledge i have i dont see what the problem is
ah well at least i remember this sign on lol |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Apr 25, 2004 5:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I am having no problems at all with XPPro, WBIMB v5 FixPack 2 and WMQI FixPack 5.
So it's something you're doing, not the software.
But I also didn't try to build the default configuration.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
