| Author |
Message
|
| Carl_P |
 Posted: Tue Apr 15, 2003 2:15 am Post subject: Problems starting broker/exection group |
 |
|
Novice
Joined: 15 Apr 2003
Posts: 11
|
Hi,
For the last few days I've been having touble getting a broker set up. I'm at the stage now where I have the broker configured with 2 execution groups, a few message sets and at present a single message flow. The diagram (Domain Topology) shown in the Assignments view looks as I'd expect but when I deploy the Operations diagram never shows anything but the broker.
I've looked at both the control center logs and the system events and I'm unsure how to move forward. Intermittently I get BIP2066E and BIP2087E messages when I deploy, but not always.
I have MQSI and the MQ queue manager located on the same server (Win2k), MQSI is v2.1 5724-D07.
Any suggestions on how I should investigate this and what I could do to resolve the issues? |
|
| Back to top |
|
 |
| Empeterson |
| Posted: Tue Apr 15, 2003 5:20 am Post subject: |
|
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
| I believe this may be the same issue we ran into not to long ago ourselves. Check your MQ log sizes, they may not be big enough. The log sizes default to 1 MB and that might not be enough for MQ to write an entire transaction to the logs. Even if you use circular logging, MQ needs to be able to write out a complete transaction to the logs at one time, and if that transaction is larger than 1 MB, it cant write it. On that note, you may also want to check your channels and system queues and make sure the max message length is high enough to accept large messages. Some of these internal configuration messages can get quite large. We had to greatly increase the max message length of our channels and queues i order to successfully deploy a mesage flow to an AIX broker. |
|
| Back to top |
|
|
| lillo |
| Posted: Tue Apr 15, 2003 5:22 am Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
A few questions,
Are your configuration manager and broker on the same machine?
Are they using the same queue manager?
If you have more than one queue manager, how are the channel which communicate both queue managers?
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| Carl_P |
| Posted: Tue Apr 15, 2003 8:07 am Post subject: |
|
|
Novice
Joined: 15 Apr 2003
Posts: 11
|
| Quote: |
| Are your configuration manager and broker on the same machine? |
Yes
| Quote: |
| Are they using the same queue manager? |
Yes |
|
| Back to top |
|
|
| Carl_P |
| Posted: Tue Apr 29, 2003 7:27 am Post subject: |
|
|
Novice
Joined: 15 Apr 2003
Posts: 11
|
| Been away from this problem for a while but yesterday I managed to resolve it. In the MQ logs I found some authoristation type errors and after looking those up on the forum found that user MUSR_MQADMIN was not a member of the administrators group. Once I corrected this and restarted everything the broker and all execution groups started as expected. |
|
| Back to top |
|
|
| Carl_P |
| Posted: Tue Apr 29, 2003 7:51 am Post subject: |
|
|
Novice
Joined: 15 Apr 2003
Posts: 11
|
Just a little more info. The messages I saw in the MQ log were as follows ...
04/28/03 11:16:02
AMQ6119: An internal MQSeries error has occurred (WinNT error 1352 from
LookupAccountSid.)
EXPLANATION:
MQSeries detected an unexpected error when calling the operating system. The
MQSeries error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
04/28/03 11:16:03
AMQ6183: An internal MQSeries error has occurred.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 1236.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
04/28/03 11:16:04
AMQ6119: An internal MQSeries error has occurred (WinNT error 2226 from
NetLocalGroupGetInfo.)
EXPLANATION:
MQSeries detected an unexpected error when calling the operating system. The
MQSeries error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
04/28/03 11:16:04
AMQ6183: An internal MQSeries error has occurred.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 1236.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
04/28/03 11:16:04
AMQ6118: An internal MQSeries error has occurred (0)
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
04/28/03 11:16:05
AMQ6183: An internal MQSeries error has occurred.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 1236.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
------------------------------------------------------------------------------- |
|
| Back to top |
|
|
| ourtown |
| Posted: Wed May 28, 2003 3:06 pm Post subject: |
|
|
Acolyte
Joined: 05 Feb 2002
Posts: 67
Location: Somerset, NJ
|
I know that it is late but
WinNT error 2226 from NetLocalGroupGetInfo means that "the specified NT Server is not the Primary Domain Controller and the action failed."
So your domain environment must have changed since you installed MQ and the NT server that MQ is querying is no longer valid
I don't know how you would get around this other than by reinstalling MQ
_________________
Brian S. Crabtree
WBI Consultant |
|
| Back to top |
|
|
|
|
