SQL##f - SqlState: S1000, ErrorCode: 0, ErrorMsg: [DataDirect][ODBC Progress OpenEdge Wire Protocol driver] Insufficient information to connect to the data source.

[Anonymous]

Extracting data from a Progress Database using an ODBC connection I get the following error:

SQL##f - SqlState: S1000, ErrorCode: 0, ErrorMsg: [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]Insufficient information to connect to the data source.

The driver (pgoe1023.dll) and has been installed and tested, and works!   I can connect to the database and preview the table content in the Qlikview connection wizard.  I simply can't reload/extract the data.

I can use the ODBC connection with Excel MS Query and extract data from tables.  The user is the owner of the database, so security, or permission to read the database should not be the issue.

After having established the connection to the database in Qlikview, the logon prompt continues to appear when making a selection on the tables.

It appears to be an issue with the Qlikview connection string as it doesn't store the password (which is in fact "blank").

ODBC CONNECT32 TO STYLEman (XUserId is QbMHOZdNPDdUM);

However, modifying the connection statement and using "ODBC CONNECT32 TO STYLEman (UserId is abcd, Password is )" does not solve the problem!

Does anyone have experience in configuring the ODBC for Progress so that the User ID and Password are passed through. 

[fosuzuki]

Have you tried to setup the connection string using the "Connect" button from the Edit Script window? It should include the encrypted userid and password...

[Anonymous]

The ODBC connection was created with the "Connect" button, but the "Scramble Connect User Credentials" was not ticked, so the User ID and Password were not encrypted in order to eliminate that as a potential issue.

I have solved the problem now by using an OLE DB connection.  It is worth commenting that the Wizard does not create a connect statement and returns an error:

I have had to build the OLE DB statment and modify the "Extended Properties" connection string to include the Password and the Catalog.

OLEDB CONNECT32 TO [Provider=MSDASQL.1;Persist Security Info=True;Extended Properties="DSN=STYLEman;HOST=1xx.1xx.1.1x;PORT=3000;DB=STYLEman; UID=ABCD;PWD=";Initial Catalog=STYLEMAN];

[rustyfishbones]

Hi Nick,

Did you ever get a fix for this? I am getting the following message

SQL##f - SqlState: S1000, ErrorCode: 4294947068, ErrorMsg: [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Access denied(Authorisation failed)

ODBC CONNECT32 TO [gal-pws]

I can connect to the Database and see all the tables but when I try to extract I get the above message

[Anonymous · Accepted solution]

Hi Alan

The error is slightly different

SQL##f - SqlState: S1000, ErrorCode: 4294947068, ErrorMsg: [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Access denied(Authorisation failed)

ODBC CONNECT32 TO [gal-pws]

It's not my area of expertise, but in my project experience the following have been asked / suggested:

1. Did you install the driver as an Administrator? OR
2. Can you use the ODBC connection to extract data through Excel with the same permissions (user / password)?

The first is obviously database "permissions" the second is related to the "connection".

I had adequate database permissions, but found that the "connection" was problematic.  This appeared to be a Qlikview  ODBC connection issue. I solved this by (as above) putting the ODBC connection in an OLE wapper.

Let me know  how  you get on.

[rustyfishbones]

Hi Nick,

It's not my area of expertise either

I have had connected to PROGRESS Databases numerous times without any issues.

We have a Database Administrator here, just waiting for him to help me!

I will let you know when I have it solved

Thanks

Alan

[#7]

i am getting the following error:

SQL##f - SqlState: S1000, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream

SQL SELECT *

FROM "INRS-NAV-LIVE-DB".dbo."R STAHL Go Live$Sales Header"

Can anyone pls help???

[Anonymous]

Did you find a solution for this problem?? We experience exactly the same errors.

rgrds Anita

[ThornOfCrowns]

Looking at his profile, I doubt Nick Scott is monitoring this thread, especially as it's the best part of two years old.

[Anonymous]

Hi

Yes.  As I stated above, I solved the problem by putting the ODBC connection into an OLE DB Wrapper.

What are the specifics of your problem and what steps have you taken to to resolve them?