QMC ODBC connetion to Access DB fails

[nikita42]

Hi,

My QVW is pulling in data from an Access DB using a Forced 32 ODBC connection. The exact connection statement is:

ODBC CONNECT32 TO [Microsoft Access DB;DBQ=Y:\SourceFile.accdb];

The reload works fine on my local machine, but fails on QMC.

I've made sure that the DB name and folder location are correct. I'm using a System DSN for the connection. The ID used by QlikView has full permissions to read/write the folder where the DB is located. On the DB properties as well the ID has full access.

For some reason, whenever I try to run the app on QMC, I get an error saying:

Error: SQL##f - sqlstate: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Is there a way to force QMC to use the right driver or something else I can do to make this work?

[krishnacbe]

Hi,

Did you created System DSN in the Server? If so did the ODBC connection test succeeded during creation in server?

[nikita42]

No, I can't find anything on creating a DSN on the server. Could you tell me how to do this?

[krishnacbe]

Same steps you created in you machine, you need to create in the server.

[krishnacbe]

If you do not have access to login to server, ask your system administrator to create the System DSN.

[Peter_Cammaert]

Also, do NOT refer to your MDB files using Drive Mappings (e.g. Y:) as those mappings may not exist for the account running the QlikView services. Use UNC paths instead.

BTW QMC has nothing to do with this. It's a desktop-like process called QVB.exe that tries to reload your document by executing the load script almost exactly like the QV Desktop engine. Only without User Interface and using a different (service) account.

Best,

Peter.

[nikita42]

This seems to work. I spoke to the server admins and they told me to switch to an OLEDB connection instead to avoid the ned for DSN creation.

But now I have another problem. The reload with the OLEDB hangs in QMC. Im able to reload the app on my local and distribute it to access point, but reload on QMC goes on for hours. In the logfile, I can see that there's an issue with the DB password:

OLEDB CONNECT32*Provider*

*Password*

*Password*

*

But I've set my Database Password = "" in the connection string and it's a simple Access DB on my local environment so there aren't any password protections anyway.

Any ideas?

[sdmech81]

HI You need to cerate connection from publisher how u did it on ur machine.

I mean connection on machine from where u want them to be run.

Sachin

[sdmech81]

Check with DB admin team,as peter said its nt QMC issue.

Sachin