topic QV Server unable to connect to database from QMC in QlikView

QV Server unable to connect to database from QMC

Mon, 26 Jan 2026 18:19:17 GMT

Hi,

I am facing an issue, when I am executing a qvw from Qlikview Desktop it's getting executed succesfully, but when I am executing it from QMC it is failing by showing an error as:
ODBC CONNECT32*XUserId*XPassword*
Error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
General Script Error

Strange thing is that sometime it gets executed from QMC but fails more often.

I have configured System DSN by the service account and I am using ODBC CONNECT32 to connect to database.

Has anyone faced this before?? Any solution for this??

Thank in advance.

Regards,

Sakir

Re: QV Server unable to connect to database from QMC

Fri, 11 Jul 2014 06:37:18 GMT

Hi.

I have already had this problem. You have to add drivers for the connections. You can fix that from System DSN. See the attached pic.

Re: QV Server unable to connect to database from QMC

vardhancse — Fri, 11 Jul 2014 06:40:33 GMT

for qlikview server(QMC) will have some service account.

we should give access to those service accounts for the db what ever we are using.

with out that we can not reload the data in QMC directly from DB

Re: QV Server unable to connect to database from QMC

vardhancse — Fri, 11 Jul 2014 06:41:44 GMT

it is the process will in our local system.

but from server if we want to do, we need to give access to the server account to the DB

Re: QV Server unable to connect to database from QMC

Mon, 14 Jul 2014 02:16:30 GMT

Hi Dimitrov,

Driver is already been configured. I can execute qvws from QMC, but most of the time it is failing stating above mentioned error. Had there been problem with the DSN, none of the tasks would have have got executed successfully.

Re: QV Server unable to connect to database from QMC

Chris_Rice — Tue, 15 Jul 2014 21:10:47 GMT

Hi Sakir,

In the case that the job sometimes completes successfully, and sometimes does not, the fault usually is on the DB or driver side. If the driver were not setup, or you had incorrect permissions, the job would never complete. With that being said, I would look at the logs for the DB and see if anything stands out there. Also, you can try using an OLEDB connect instead of ODBC to see if there are any differences.

When a script is ran through QV Developer and connects to a DB, the DB sees the user coming in as a "User". When that same script is ran through the QMC, that same user will be seen as a "Service". Services usually have a different set of permissions and a lower priority than users in the DB, therefore the different results.