MQSeries.net :: View topic - ODBC Driver not found

mqdev · Posted: Tue Oct 09, 2007 3:48 pm Post subject:

Hello,
We are having an issue with a Message Flow which accesses an SQL Server. The Message Flow was migrated from v2.1 to v6.0 (platform is Win2003). The ODBC Data Source Name is configured identically on both v2.1 and v6.0 boxes - however the flow works fine on the v2.1 box but not on v6.0.

Has anyone faced this issue? When I search for this on mqseries.net, I find a lot of hits but none seems to offer a solution which works in our scenario - I have checked the Driver level ( it is at 3.86 while IBM prescribes 3.60 or later). An insight into this issue esp from folks who have faced and solved it would be appreaciated. Below is the error text from Event Viewer App logs when the flow executes.

Thanks
-mqdev

Event Type: Error
Event Source: WebSphere Broker v6003
Event Category: None
Event ID: 2322
Date: 10/9/2007
Time: 1:33:04 PM
User: N/A
Computer: VMWMQD1
Description:
( BKMQSINTD1.EAGLE.GENERAL ) 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.

Event Type: Error
Event Source: WebSphere Broker v6003
Event Category: None
Event ID: 2321
Date: 10/9/2007
Time: 1:33:04 PM
User: N/A
Computer: VMWMQD1
Description:
( BKMQSINTD1.EAGLE.GENERAL ) 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.