ODBC connection suddenly doesn't work - Qlik Community

Report Inappropriate Content · ‎2016-09-13

Hi,

i have a QVD generator that through a ODBC connection reads from a database and stores in to r-.qvds. This has been working for a year, now suddenly it doesn't?

see attached for the error message: Invalid object name thats just crazy when it's been working everyday for the past half year.

Anyway to debug or find what's been going wrong here?

stabben23 · ‎2016-09-13

Hi,

have there been some password changes for the user who read from SQL?

Can you Connect or Select from Your script to the database?

tracysmart · ‎2016-09-13

It might sound like an obvious question but have you checked the database to make sure that the table hasn't been renamed/deleted and ruled that out first?

Report Inappropriate Content · ‎2016-09-13

Staffan, Actually now that you ar ementioning this. I have changed my AD password upon automatic request from our system. But qlikview is running on an external server which has its own log ins.

Report Inappropriate Content · ‎2016-09-13

Yes ofcourse. Nothing like that

miguelbraga · ‎2016-09-13

Hey there,

Try creating another QVW and try to access your database from the new app. There might be a possibility that your database have become corrupt and/or changed the location by another user. Please let us know what is happening...

Regards,

MB

rupamjyotidas · ‎2016-09-13

Hope the database is not upgraded to 64 bit and your connector to database is 32 bit.

krishnacbe · ‎2016-09-13

To check the access stuffs you can connect to SQL server using the functional ID or if you do not have SQL server try to connect through OLEDB.

If connection is fine and only issue with table you need to contact the SQL administrator.

stabben23 · ‎2016-09-14

Ok, check Your connectionstring and see so its not Your user thats Connect to the database. Also check the user on qlikview server, make sure that this account have password never expired.

Anonymous · ‎2017-01-30

Hi Niklas!

I had the same prbolem , and i tell you how i solved it.

Well my problem was with the connection ODBC in oracle

i just selected OLE DB and i checked the "Forced 32 Bit" chek box. And then it worked .. wierd but its how it work for me.

Cheers.