Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Experts,
I get an error for one of the qvw document when loading on a server and on the desktop. This particular document was migrated from one server machine to other and it works fine on the old machine. The Oracle client 32 bits and 64 bits also have been installed but still it doesn't connects.
1. OLEDB CONNECT32*Provider*
Error: ErrorSource: Microsoft OLE DB Provider for ODBC Drivers, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
General Script Error
2. For the other document I get an error as
OLEDB CONNECT32*Provider*Password*Password*
Error: ErrorSource: Microsoft OLE DB Service Components, ErrorMsg: Class not registered
General Script Error
The document uses MS Access as it's database and it runs fine on the older machine but fails on the new machine.
Plesae let me know what needs to be fixed for the above errors.
Thanks.
A OLEDB CONNECT32*Provider*... statement (see your OP, you are saying that it fails with the exact same error) tells the Script Engine to go looking for 32-bit drivers. With just the 64-bit Access drivers installed, there will be no match. Change the CONNECT statement to match your installed drivers.
One thing i can say for the 1st one is you are missing the ODBC DSN Name. Create that from your "ODBC" manager and that will solve the problem.
Not sure about the second one, but i would see if the service account has access to MS Access DB and you were able to go to that file location.
if your using the 64 bit Qlikview and want to connect for the 32bit machine then , check the force 32 bit connection option in the edit script and make sure the TNS file has the data source details and you server has all the drivers installed
If your database is MS Access (and how about Oracle then?), you'll need the appropriate OLEDB/ODBC drivers that are included with MS Office. You can also download them from the Microsoft downloads site. For example, see here:
Best,
Peter
Hi Peter,
I installed the MS Access drivers 64 bits and have put the DSN name but it's still failing with the same error.
A OLEDB CONNECT32*Provider*... statement (see your OP, you are saying that it fails with the exact same error) tells the Script Engine to go looking for 32-bit drivers. With just the 64-bit Access drivers installed, there will be no match. Change the CONNECT statement to match your installed drivers.
Hi Peter,
I uninstalled the 64 bits drivers for MS access and installed the MS access drivers 32 bits and given the DSN name. Then the document ran successfully. Thanks for the support Peter.
Hi,
Please go through this link ,
https://community.qlik.com/blogs/qlikviewdesignblog/2014/02/10/odbc-confusion
May help you.
thanks,
bunny