| Author |
Message
|
| mqceries |
 Posted: Mon Dec 12, 2011 9:05 pm Post subject: Error creating Broker |
 |
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
I managed to install wmb6.1 broker, 6.1.9 toolkit and MQ7. Also installed oracle software but getting following error for createbroker command, can you please help me with this error. I made sure that passwords are correct, database is running, and also DSN is working.
| Quote: |
C:\Windows\system32>mqsicreatebroker BRK1 -i MB -a admin -q QM1 -n ORA -u SYSMAN
-p admin
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. T
he ODBC return code was '-1'. See the following messages for information obtaine
d from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely t
o be such things as incorrect datasource or table names. Then correct either the
database or message broker configuration.
BIP2322E: Database error: SQL State ''IM014''; Native Error Code '0'; Error Text
''[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture m
ismatch between the Driver and Application''.
The error has the following diagnostic information: SQL State ''
IM014'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][OD
BC Driver Manager] The specified DSN contains an architecture mismatch between t
he Driver and Application''
This message may be accompanied by other messages describing the effect on the m
essage broker itself. Use the reason identified in this message with the accomp
anying messages to determine the cause of the error.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the userid and password that were specified
with the broker.
- Check that the database is running.
- On Windows check that an ODBC connection has been created.
- On systems which use $ODBCINI check that the file pointed to by $ODBCINI has
been correctly updated.
- Check that the userid and password pair specified for ODBC connect on the mqs
icreate or mqsichangebroker command are capable of being used to connect to the
database using an ODBC connection.
- Check that the database has a adequate number of database connections availab
le for use.
|
|
|
| Back to top |
|
 |
| mqceries |
| Posted: Mon Dec 12, 2011 9:18 pm Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
| i am using Win 7 professional 64 bit os, oracle 11gr2 64 bit. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Dec 12, 2011 10:09 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Broker 6.1 runtime DOES not work on Windows 7.
It will work inside 'XP Mode' but this might not be available for your version of Windows 7.
XP Mode is an XP virtual machine. It is a free download from Microsoft for qualifying versions of Windows 7.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqceries |
| Posted: Tue Dec 13, 2011 5:24 am Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
| yes i am using windows xp mode, the only problem is that vpn is not supported by remoted desktops(xpmode)- and i cant connect to office environment.. thats my biggest issue. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Dec 13, 2011 5:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mqceries wrote: |
| yes i am using windows xp mode, the only problem is that vpn is not supported by remoted desktops(xpmode)- and i cant connect to office environment.. thats my biggest issue. |
No.
Your biggest issue is that Broker v6.1 is not supported on Windows 7.
The only environment where you should even be thinking of using it is on a personal workstation for testing and development. |
|
| Back to top |
|
|
| mqceries |
| Posted: Tue Dec 13, 2011 6:00 am Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
| i do understand, but given the things i had no option and trying to get best of these. we had deployments going on parallely and i dont want to disturb those and planning to image the flows in my machine to work parallely. given that error correct me i am wrong it may be talking about 64bit mismatch or so..DB2 was not installing on win 7. Now that my machine is pre built with 7 and manufacturer settings its nt allowing me to install windows xp. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 13, 2011 6:00 am Post subject: Re: Error creating Broker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqceries wrote: |
BIP2322E: Database error: SQL State ''IM014''; Native Error Code '0'; Error Text
''[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture m
ismatch between the Driver and Application''. |
This is completely clear. You have a 64 bit architecture. WMBv6.1 is 32 bit. This is a mismatch. It doesn't work.
It is possible to get this working (though I confess I wasn't using Oracle). Once it was working I took a disc image so I could restore it if the magic went away. But this was on my development workstation and I fully endorse and echo the comments of my most worthy associates. This is an unsupported configuration. When weird things start happening you'll be on your own.
Do not attempt to use this for anything business related.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Dec 13, 2011 6:05 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqceries wrote: |
| i do understand, but given the things i had no option and trying to get best of these. we had deployments going on parallely and i dont want to disturb those and planning to image the flows in my machine to work parallely. given that error correct me i am wrong it may be talking about 64bit mismatch or so..DB2 was not installing on win 7. Now that my machine is pre built with 7 and manufacturer settings its nt allowing me to install windows xp. |
Funny that. Last year bought an Asus laptop with Windows 7 Pro pre installed.
I upgraded (over the network) to Ultimate and can quite happily run XP Mode.
You (ie yourself) do not install XP as a separate operation. The XP Mode software you download from Microsoft does it all for you. The installer also does a WGA check...
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqceries |
| Posted: Tue Dec 13, 2011 6:25 am Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
| smdavies99 wrote: |
| mqceries wrote: |
| i do understand, but given the things i had no option and trying to get best of these. we had deployments going on parallely and i dont want to disturb those and planning to image the flows in my machine to work parallely. given that error correct me i am wrong it may be talking about 64bit mismatch or so..DB2 was not installing on win 7. Now that my machine is pre built with 7 and manufacturer settings its nt allowing me to install windows xp. |
Funny that. Last year bought an Asus laptop with Windows 7 Pro pre installed.
I upgraded (over the network) to Ultimate and can quite happily run XP Mode.
You (ie yourself) do not install XP as a separate operation. The XP Mode software you download from Microsoft does it all for you. The installer also does a WGA check... |
My intention was not to contradict you or some thing, i never said that i have trouble using winxp mode. Mine is professional editon and the problem is that cisco vpn any connect keep saying that it wont support winpxp mode.. i dint tried using all the broker stuff from win7 by pulling it from winxp mode.. |
|
| Back to top |
|
|
| mqceries |
| Posted: Tue Dec 13, 2011 6:27 am Post subject: Re: Error creating Broker |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
| Vitor wrote: |
| mqceries wrote: |
BIP2322E: Database error: SQL State ''IM014''; Native Error Code '0'; Error Text
''[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture m
ismatch between the Driver and Application''. |
This is completely clear. You have a 64 bit architecture. WMBv6.1 is 32 bit. This is a mismatch. It doesn't work.
It is possible to get this working (though I confess I wasn't using Oracle). Once it was working I took a disc image so I could restore it if the magic went away. But this was on my development workstation and I fully endorse and echo the comments of my most worthy associates. This is an unsupported configuration. When weird things start happening you'll be on your own.
Do not attempt to use this for anything business related. |
I really appreciate and thankful if you can help me to fix this, i had trouble in installing oracle 32 bit editions before.. i tried oracle 9i,10g,11g express edition, 11g all had problems and it dint went to creating DSN.. now that i am desperate and feel bad that i cant do any thing..it sucks. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 13, 2011 6:37 am Post subject: Re: Error creating Broker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqceries wrote: |
| i had trouble in installing oracle 32 bit editions before.. i tried oracle 9i,10g,11g express edition, 11g all had problems and it dint went to creating DSN |
Yes, that happened to me too. It's interesting how few 32 bit database products work on 64 bit Windows, or work fully.
I got WMBv6.1 a database on Win 7 by installing a 64 bit version of SQL Server & configuring a 32 bit ODBC to point to it. That simplifies about 2 days of fiddling round including disabling the SQL Server security because none of the user ids would work. Following about 3 days of trying various flavours of DB2.
Interestingly I couldn't use the same driver to access the 32 bit SQL Server that held some business reference data the flows used. Never did get to the bottom of that issue before my interest petered out.
As to exactly what I did, not sure (hence the disc image). I'd tell you how the machine is set up, but on a different site to me now.
| mqceries wrote: |
| .. now that i am desperate and feel bad that i cant do any thing..it sucks. |
Yep, sounds familiar. One thing you can do (which I know works) is to accelerate the migration onto WMBv7. A good way of doing this is to demonstrate how unstable the WMBv61 set up you have on Win 7 is (or at least that worked for me).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqceries |
| Posted: Tue Dec 13, 2011 7:00 am Post subject: Re: Error creating Broker |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
| Vitor wrote: |
| mqceries wrote: |
| i had trouble in installing oracle 32 bit editions before.. i tried oracle 9i,10g,11g express edition, 11g all had problems and it dint went to creating DSN |
Yes, that happened to me too. It's interesting how few 32 bit database products work on 64 bit Windows, or work fully.
I got WMBv6.1 a database on Win 7 by installing a 64 bit version of SQL Server & configuring a 32 bit ODBC to point to it. That simplifies about 2 days of fiddling round including disabling the SQL Server security because none of the user ids would work. Following about 3 days of trying various flavours of DB2.
Interestingly I couldn't use the same driver to access the 32 bit SQL Server that held some business reference data the flows used. Never did get to the bottom of that issue before my interest petered out.
As to exactly what I did, not sure (hence the disc image). I'd tell you how the machine is set up, but on a different site to me now.
| mqceries wrote: |
| .. now that i am desperate and feel bad that i cant do any thing..it sucks. |
Yep, sounds familiar. One thing you can do (which I know works) is to accelerate the migration onto WMBv7. A good way of doing this is to demonstrate how unstable the WMBv61 set up you have on Win 7 is (or at least that worked for me). |
Really appreciate your reply, as it answered many questions. Now that i can feel it not only happened to me or i am doing some thing wrong.. i guess u know the feeling. Given that SQL server i havent tried that one.. will give it a short..  not planning for installing Acess though. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 13, 2011 7:22 am Post subject: Re: Error creating Broker |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqceries wrote: |
| Given that SQL server i havent tried that one.. will give it a short.. |
A short (in the electrical sense) is not that unlikely. 
I don't want you to get the impression this worked - it ran. It was as stable as me on 6 cans of Red Bull, required a certain amount of scripting to get the deploys to work and the debugger lied more than it usually does.
Given that I tend to use scripted deploys (though not this involved) and user trace anyway I could live with it. Until I got the WMBv7 migration done.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqceries |
| Posted: Mon Dec 19, 2011 2:41 pm Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
sorry for being offline for couple of days. I tried couple of new things suggested by vitor and finally able to install SQL Server 2008 R2 on win 7 pro and created a 32 bit dsn for it. I also created broker and cofiguration manager, i am getting the following error on creating a broker no errors while creating configuration manager. But diff errrors while creating a new domain connection. I am using MQ 7.1, Broker 6.1 and tool kit 6.1.9. I followed correctly QM and all..though screenshots says diff queue manager.
Thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Dec 19, 2011 10:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Which user is running this prompt?
What group is it member of?
Before trying to create the broker, can you try and start the config manager?
What errors are being shown in the windows event log?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
