ODBC - Call Failed

[muzadzim]

We are running Voiceguide 5.1.7.001 on Windows 2000 Workstation with SP4

 

We have a Progress V8 database. We have installed and tested ODBC drivers to the database from other programs and we where successsfull. However with Voiceguide we are getting the following error in the log trace

 

->ODBC mode used

->Error 5.1.7001 OpenDatabase [3146:ODBC - Call failed]

 

Please assist.

 

Regards Martin

[SupportTeam]

Sounds like the ODBC's "CONNECT" string is incorrect.

What is the Connect string you are using now with VoiceGuide to connect to your database and have you tried any other alternative Connect strings?

[muzadzim]

The name of the system DSN created in control panel is -- members

 

the connect string we are using is

Database -- members

Connect String -- ODBC;DSN=members;

 

Regards

 

Martin

[SupportTeam]

Can you connect to your database using MS Query?

 

Which ODBC drivers are you using for your database, from http://www.openlinksw.com/ or some others?

 

Here is some info on getting ODBC drivers for Progress running - maybe something there can help:

http://www.innov8cs.com/downloads/ProgressODBCFAQ.pdf

 

maybe this will help as well:

http://www.progress.com/progress/products/...l92/odr/odr.pdf

[muzadzim]

Yes we can connect with MS Query.

 

We are using Openlink Lite (Largefor Progress 8.2a).

[SupportTeam]

We're not experts on the connect strings needed to connect to a Progress database.

 

To test ODBC connectivity from VoiceGuide you can try setting up a MS Access database as an ODBC source (as per examples in VoiceGuide help file) and see if this works. This should verify if the ODBC layer works at all on your system.

 

Then I'd try a few other variants of the Connect string that seem plausible. Usually the connect string contains the database username and password as well...

[muzadzim]

I seem to be connecting to the database , however I still can not get any data out. Below is an extract from the trace log,

 

 

 

114904.70 0 [sayWelcome] Playing (C:\Program Files\VoiceGuide\data\tts0.wav)

114904.78 0 PlaySoundStart ok [C:\Program Files\VoiceGuide\data\tts0.wav]

114904.78 0 RunModule PLAY end

114909.70 0 Play End line[0] (id=237406)

114909.72 0 LsPlayMsg EV_PLAY_FINISHED

114909.72 0 LsPlayMsgFinished EV_TIMEOUT_GOTOMODULE

114909.73 0 [DbPractitioner] DB Query

114909.73 0 ODBC mode used

114914.98 0 About to execute Retrieve Operation [sELECT benefit FROM benefit WHERE membership=249711]

114917.41 0 ERROR 5.1.7001 OpenRecordset: 3146:ODBC--call failed.

114917.78 0 [sayFailure] Playing

114917.78 0 tts generate start[Failure Failure Failure]

114917.83 0 tts generate end

114917.84 0 [sayFailure] Playing (C:\Program Files\VoiceGuide\data\tts0.wav

[SupportTeam]

Please update to v5.2.2 of VG and post the trace from that version - that version has a few extra debugging messages which may be useful here...

[Guest Guest_muzadzim]

We are querying the database but the query returns no data. When we use the same query in MS SQL we are retrieving data. Below is the trace after upgrading to 5.2.2

 

110028.75 0 ScriptEventCode 9002 iLineState=1101

110028.75 0 LsPlayMsgFinished EV_TIMEOUT_GOTOMODULE

110028.77 0 TimeoutClear

110028.77 0 [DbPractitioner] DB Query

110028.78 0 db ODBC mode used

110031.77 0 db About to execute a Retrieve type operation [select * from fund]

110034.17 0 db [DbPractitioner] row count=0

110034.17 0 rv add [DbPractitioner_RowCount]{0}

110034.50 0 TimeoutClear

110034.50 0 [sayFailure] Playing

110034.52 0 tts generate start[Failure Failure Failure]

110034.53 0 tts generate wait

[SupportTeam]

If there was an error running the SQL query the error would have been reported in the trace. As we see:

 

110034.17 0 db [DbPractitioner] row count=0

 

this suggests that the ODBC driver did not report any errors when processing the query, but has returned to VoiceGuide the result that 'no records could be found'.

 

Have you done this test?:

To test ODBC connectivity from VoiceGuide you can try setting up a MS Access database as an ODBC source (as per examples in VoiceGuide help file) and see if this works. This should verify if the ODBC layer works at all on your system.

 

I'd also try to see if you can set up a local MS Access table that links to your Progress database and see if you can retrieve data that way.

 

After better establishing what does work and hat does not work on your system you may have a better idea of where the problem lies.