Qv app refreshes at local but not in QV Server

[krishna20]

Hi Folks,

We are using Informix DB for our projects.

QV loader is running successfully at local but it's getting failed in QV server, specifying that  Error: ErrorSource: Microsoft OLE DB Provider for ODBC Drivers, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified .

We are able to connect database and can fetch the data.

We were using driver client 4.90... and yesterday we downgraded to 2.90, still issue not resolved.

I googled for this issue at we have less discussions on informix db issues.

We are having special characters in our password,is it the issue?? but in one of our projects this scenario is working fine.

what could be the issue is?

Can anyone light up on this issue.

marcowedel  stalwar1 Gysbert Wassenaar   Avinash R marcus_sommer

[avinashelite]

1.Your using OLEDB or ODBC connection ?

if its ODBC then you have to add the DSN in server with the name your using in connection

2.Check whether required drivers are installed in the QV server for informix DB

[krishna20]

Hi,

It's OLEDB connection.

Drivers are installed and test connection succeeded. 

[michael123]

Are you using same AD-user in both instances? Has account running QVS access rights to database?

[krishna20]

Yes all settings has been given correctly.But don't know why the application is failing in QV server.

[avinashelite]

Did you checked in the server , whether the connection is working fine or not ? if you have server access login to server and check the connection

[krishna20]

Hi Avinash,

Connection getting successful.

[avinashelite]

you tried this in the server ?

[Colin-Albert]

Your connection is using ODBC (OLEDB for ODBC), so have you added the ODBC datasource on the server with exactly the same name as on the machine where the app was created?

Do you have QV Desktop installed on the server?

If so, logon to the server using the account running the QDS service, and try loading the app manually on the server, this should show you the error.

Have you enabled the document log? If so, the log file will also show the cause of the error.

[krishna20]

I am working in server only and  above screenshot is from server.