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.
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.BIP2322E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''.The error has the following diagnostic information: SQL State ''IM002'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompnying 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 specifiedwhen the broker was created.Check that the database is running, that an ODBC connection has been created andthat the userid and password pair specified for ODBC connect on the mqsicreatecommand are capable of being used to connect to the database using an ODBC connection. Also ensure that the database has a adequate number of database connections available for use.
Check that the database is running, that an ODBC connection has been created andthat the userid and password pair specified for ODBC connect on the mqsicreatecommand are capable of being used to connect to the database using an ODBC connection. Also ensure that the database has a adequate number of database connections available for use.
Have you performed all these checks? What was the outcome? _________________ Honesty is the best policy.
Insanity is the best defence.
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