| Author |
Message
|
| srailkar |
 Posted: Tue Mar 28, 2006 12:36 pm Post subject: WBIMB 6.0 - Message flow cannot connect to SQL Server 2005 |
 |
|
Apprentice
Joined: 01 Jun 2005
Posts: 37
|
After migrating the message flow which was working fine in version 5 environment, the message flow does not connect to SQL Server 2005 Database. Much appreciate any insights on this issue:
MQ 6.0.0.1
WBIMB 6.0
Platform: Windows Server 2003
ODBC entry for SQLServer - OFACDB
Compute node : Datasource = OFACDB
Code abending on:
INSERT INTO Database.ofac.OFAC_RESPONSES
(el_Client_Element_Transaction_Id,
el_Response_Name,
el_Client_Element_User_Id)
VALUES (OJOURNALID,
OJOURNALID,
OUSERID,
OINVESTIGATORID);
Error :
2006-03-28 12:54:43.834739 3984 UserTrace BIP2231E: Error detected whilst processing a message 'HTTPREQUEST_REPLY.HIT'.
The message broker detected an error whilst processing a message in node 'HTTPREQUEST_REPLY.HIT'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2006-03-28 12:54:43.834739 3984 DatabaseException 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.
2006-03-28 12:54:43.834739 3984 DatabaseException 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 accompanying messages to determine the cause of the error.
2006-03-28 12:54:43.835739 3984 Error BIP2232E: Error detected whilst handling a previous error in node 'HTTPREQUEST_REPLY.HIT.LOG'.
The message broker has detected an error in node 'HTTPREQUEST_REPLY.HIT.LOG' whilst handling a previous error.
See the following messages for details of the exception list associated with the original error. Thereafter messages will be associated with the new error.
2006-03-28 12:54:43.835739 3984 RecoverableException BIP2230E: Error detected whilst processing a message in node 'HTTPREQUEST_REPLY.HIT'.
The message broker detected an error whilst processing a message in node 'HTTPREQUEST_REPLY.HIT'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2006-03-28 12:54:43.835739 3984 DatabaseException 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.
2006-03-28 12:54:43.835739 3984 DatabaseException 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 accompanying messages to determine the cause of the error.
2006-03-28 12:54:43.836738 3984 UserTrace BIP2231E: Error detected whilst processing a message 'HTTPREQUEST_REPLY.ATTUS.IN'.
The message broker detected an error whilst processing a message in node 'HTTPREQUEST_REPLY.ATTUS.IN'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2006-03-28 12:54:43.836738 3984 RecoverableException BIP2230E: Error detected whilst processing a message in node 'HTTPREQUEST_REPLY.HIT.LOG'.
The message broker detected an error whilst processing a message in node 'HTTPREQUEST_REPLY.HIT.LOG'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2006-03-28 12:54:43.836738 3984 MessageException BIP2665E: Output node 'HTTPREQUEST_REPLY.HIT.LOG' expected a distribution list but one did not exist. State = '-1' ''MQW005'' '0' ''''
An MQ output node with the "Destination Mode" property set to "list" received a message but there was no valid distribution list, that is, it did not contain a "Destination" folder in turn containing an "MQ" folder.
Check the message flow to determine whether the message is being built correctly, correct the problem and redeploy the broker. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Mar 28, 2006 12:41 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you specify a datasource name on the HTTPREQUEST_REPLY.HIT.LOG node?
Did you create the ODBC datasource with that datasource name?
Can you establish a connection using that datasource outside of Broker?
Are there errors on the SQLServer side?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| srailkar |
| Posted: Tue Mar 28, 2006 12:58 pm Post subject: |
|
|
Apprentice
Joined: 01 Jun 2005
Posts: 37
|
Did you specify a datasource name on the HTTPREQUEST_REPLY.HIT.LOG node?
YES
Did you create the ODBC datasource with that datasource name?
YES
Can you establish a connection using that datasource outside of Broker?
Tested connection of the Datasource within ODBC setup
Are there errors on the SQLServer side?
No error showing on the SQLServe side, which leads me to believe I am not going that far..... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 28, 2006 1:23 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does it work if you specify a user in the ODBC DSN setup?
Did you specify a user and password for the datasource with mqsisetdbparms?
Did you grant permissions to that user for all the database objects that it needs to access, within the database?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| srailkar |
| Posted: Tue Mar 28, 2006 2:10 pm Post subject: |
|
|
Apprentice
Joined: 01 Jun 2005
Posts: 37
|
Does it work if you specify a user in the ODBC DSN setup?
YES
Did you specify a user and password for the datasource with mqsisetdbparms?
MISSED this one
Did you grant permissions to that user for all the database objects that it needs to access, within the database?
YES |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Mar 28, 2006 2:12 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
Firstly, SQLServer 2005 is not currently supported with any version of message broker.
Having said that, check the following:
The ODBC connection must be made in the SYSTEM panel not the FILE panel.
The best drive to use is the SQLServer 2005 Native ODBC Driver (a seperate install along with the DB).
You must use SQLServer authentication, not Windows authentication.
The username and pwd should be specified with mqsisetdbparms if they are different to the DSN user id and pwd used when creating the broker.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| born2win |
| Posted: Thu Nov 09, 2006 6:39 am Post subject: |
|
|
Novice
Joined: 01 Feb 2006
Posts: 16
|
Platform: Windows Server 2003
ODBC entry for SQLServer - OFACDB
Compute node : Datasource = OFACDB
Code abending on:
INSERT INTO Database.ofac.OFAC_RESPONSES
(el_Client_Element_Transaction_Id,
el_Response_Name,
el_Client_Element_User_Id)
VALUES (OJOURNALID,
OJOURNALID,
OUSERID,
OINVESTIGATORID);
The Datasource is set to OFACDB and he is accessing it as ofac. could this be an issue? |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Nov 09, 2006 11:52 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
Firstly if he was still having a problem, I would be suprised given the time passed  .
Secondly the Datasource name is OFACDB, where as ofac is the schema name, so no, this cannot be the problem.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| mqdev |
| Posted: Tue Oct 09, 2007 6:36 am Post subject: Exact same issue - what is the resolution? |
|
|
Centurion
Joined: 21 Jan 2003
Posts: 136
|
srailker,
We have migrated v2.1 Broker to v6.0. On the new box, we have setup the ODBC SQL Server settings identical to that on v2.1. The message flow works fine on v2.1 but is giving "ODBC Driver not found" error (exact same error messages as yours - to the T!). What was the resolution in your case? We have a PMR open with IBM and are waiting on the same - but any solution here would expediate our project execution - so please speak up.
Thanks
-mqdev |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 09, 2007 7:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
MQDEV
You're likely using the wrong driver in your ODBC data source.
Also, please start a new thread for new problems, even if it LOOKS like the same problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
