HP VERTICA ODBC DRIVER DOWNLOAD
|Date Added:||1 November 2015|
|File Size:||6.92 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Resources for IT Professionals. Change the database, server name, user name, password, and any other relevant parameters to match the information for your database.
We actually tried that. Sign in to vote.
We actually have 2 users where this error is happening, while we have over 20 users running the same OS version and Office version getting no error and the connection working as expected. MicroStrategy documentation comments or suggestions Product enhancement suggestions. Most users have no problems creating a DSN of either bit, but a few have the problem when trying to define a bit version.
MicroStrategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability. Thanks for the response.
Copy and paste the contents from the odbc. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. Wednesday, November 1, Best regards, Yuki Sun Please remember to mark the replies as answers if they helped.
We also uninstalled those Vertica drivers and installed prior versions, as version 9 is relatively new. I have the exact same issue when trying to use the 32bit driver even though it’s there. This helps narrow down if the issue is because this particular. If you have Office and Office ProPlus Preview version questions, you can still ask about Preview for a limited time: Wednesday, April 11, 9: We have had other users of all 3 versions of the ODBC driver sets from Vertica successfully connect via bit Office.
ODBC Driver for Vertica for Linux
h; Recent installation of Vertica drivers on bit Windows 7 running Office bit. Would greatly appreciate any additional ideas you might have. Note that this issue is only affecting some users. The third-party product s discussed in the procedure below is manufactured by vendors independent of MicroStrategy. Wednesday, November 1, 6: Office Office Exchange Server.
Thanks again, and have a great day! This can often be found along with the driver installation. Open the MicroStrategy odbc. The path to the installation location you choose for the ODBC driver is used later in this procedure as the value for the Driver parameter in the odbc. Ideas on why this error is being thrown for some, and how to resolve it? The specified module could not be found. Tuesday, October 31, For information on veetica available parameters, refer to your third-party Vertica driver documentation.
You should paste the contents of the DSN exactly as they appear in the example file. Hope the above information can be helpful. Vertica by default installs both 32 and 64 bit drivers. Specified driver could not be loaded due to system error