| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP1539E: Unable to deploy configuration data to broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| sbbdev |
 Posted: Wed Sep 17, 2008 4:07 am Post subject: BIP1539E: Unable to deploy configuration data to broker |
 |
|
Novice
Joined: 03 Sep 2008
Posts: 18
|
Hi there
i'm trying to deploy MQ flows to my MQ server, first i get the following message telling me the initiaion was OK with the server
| Code: |
BIP1520I: Deploy operations successfully initiated.
The Configuration Manager has processed the deploy request and initiated the deploy of configuration data to the following brokers. Active brokers: SBB_BROKER1 . Deleted brokers: .
Open the Event Log Editor to check the outcome of the operations. There will be a separate set of log messages for each broker. |
however, when i open the MQ event log i get the follwoing error:
| Code: |
BIP1539E: Unable to deploy configuration data to broker SBB_BROKER1: broker does not exist on queue manager SBBBK1QM.
An attempt was made to deploy configuration data to broker SBB_BROKER1, but WebSphere MQ could not deliver the deploy request to the broker. The broker was found not to exist on queue manager SBBBK1QM. No configuration data was deployed.
Either the wrong WebSphere MQ queue manager has been specified for the broker, or the broker has not been created using the mqsicreatebroker command, or the broker has been prematurely deleted using the mqsideletebroker command. Note that WebSphere MQ queue manager names are case-sensitive. Depending on the cause, either correct the queue manager name and redeploy, or create the broker using the mqsicreatebroker command and redeploy, or delete the broker from the configuration using the Message Brokers Toolkit and redeploy to remove all traces of the broker from the configuration repository. |
previousely, i had a problem trying to connect to the server. i had a message telling my that i had no permission to connect. i was advised to delete the config manger and the broker and all it's references in IBM DB2 (table named "CBROKER") and recreate them again.
i recreated the broker and manged to connect to the server in the domain pain/IBM Toolkit but i,m getting the above error message now
please help |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Thu Sep 18, 2008 2:36 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
(By you mentioning DB2, I assume you're on WMB v5, which is going out of service soon. I'd recommend starting on the path to WMB v6.1 - you'll find WMB v6.1 a lot easier to manage when encountering problems such as these. Plus it's faster and generally better all-round.)
BIP1539 is thrown when the Config Manager attempts to open the broker's SYSTEM.BROKER.ADMIN.QUEUE to put the deployment message, but MQ threw MQRC_UNKNOWN_OBJECT_NAME.
Either the broker wasn't created correctly (i.e. the MQ resources were not created successfully), or you haven't set MQ up correctly to allow messages to flow from the Config Manager's queue manager to the broker's queue manager. |
|
| Back to top |
|
|
| sbbdev |
| Posted: Thu Sep 18, 2008 3:32 am Post subject: |
|
|
Novice
Joined: 03 Sep 2008
Posts: 18
|
| Quote: |
| or you haven't set MQ up correctly to allow messages to flow from the Config Manager's queue manager to the broker's queue manager. |
thanks for the reply, can you please elaborate more on what you said above?
i thought, according to the error, i did not create the broker successfully although i can see in the services pannel and i can connect to the server and broker in "Domain" pane using the toolkit. so what i did is that i tried deleting the broker in order to re-create it again but i'm getting an error saying i have not authority to connect to the databse!
C:\>mqsideletebroker SBB_BROKER1
BIP8018E: Component running.
This component is running, the command issued cannot be run against a running co
mponent.
Stop the component and reissue the command.
| Code: |
C:\>mqsideletebroker BROKER1
WebSphere MQ queue manager running.
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 '08001'; Native Error Code '-30082'; Error T
ext '[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with se
curity reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001 '.
The error has the following diagnostic information: SQL State '0
8001' SQL Native Error Code '-30082' SQL Error Text '[IBM][CLI Dr
iver] SQL30082N Attempt to establish connection failed with security reason "24
" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001 '
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
when the broker was created.
Check that the database is running, that an ODBC connection has been created and
that the userid and password pair specified for ODBC connect on the mqsicreate
command are capable of being used to connect to the database using an ODBC conne
ction. Also ensure that the database has a adequate number of database connectio
ns available for use. |
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
