Somehow my Servers ASA ODBC Driver is missing, I can still see all the DSN created using ASA ODBC Driver, but cant open them anymore.Its probably due to the InstallUninstall Sybase Persoanl ServerNetwork Server.
Sybase Adaptive Server Anywhere Download And InstallI was googling to find whether theres Sybase ASA ODBC Driver installation package I can download and install, but no success.
Sybase Adaptive Server Anywhere Driver Using Regsvr32Accroding to these articles, we can re-register the driver using regsvr32 or manually change Registry. Article 1 The following error occurs because the ODBC driver settings or registry keys have been removed from the registry. Solution 1 The first solution is to re-register the ODBC driver: At a command prompt, navigate to the Pylon Anywhere installation directory (for example, C:Program FilesSybasePylon AnywhereDB ). Run the following command: regsvr32 dbodbc9.dll Now you should be able to edit the Pylon Anywhere data source from the ODBC Data Source Administrator. ![]() Type Regedit Navigate to the following key: HKEYLOCALMACHINESOFTWAREODBCODBCINST.INI Create a new key under this key called Adaptive Server Anywhere 9.0 Under Adaptive Server Anywhere 9.0, create the three strings shown in the following screenshot: Under the key HKEYLOCALMACHINESOFTWAREODBCODBCINST.INIODBC Drivers, create the string Adaptive Server Anywhere 9.0 with the value Installed Close the registry. You should be able to edit the ODBC data source or add a new data source. Horan Recently, one of our client sites started reporting strange system errors with our software. For days, we tried to recreate the issue in our labs, but were unsuccessful. When we finally opened a remote desktop sharing session to the individual users PC, we noticed that the ODBC driver files for SQL Anywhere were for a much older build of the same version. They had installed another SQL Anywhere-based software product, and that packages setup routine had overwritten our existing ODBC driver files. Since both software packages were written to use the Adaptive Server Anywhere n.n driver, we were essentially sharing that middleware layer. Our solution for avoiding this problem was to isolate our installation of the Adaptive Server Anywhere ODBC driver, and brand it with our company name. That gave us total control over the software, and protected us from getting overwritten by any other software setup routines. ![]() Create a new Registry Key in: HKEYLOCALMACHINESOFTWAREODBCODBCINST.INI that identifies your installed driver name. We called ours VCI Adaptive Server Anywhere Create two string values under this key, DRIVER and SETUP that point to the location of your installed Adaptive Server Anywhere driver files; Create a new string value in: HKEYLOCALMACHINESOFTWAREODBCODBCINST.INIODBC Drivers with the name of your specific driver name (created in step 2 above), and the value Installed; Now, when creating individual ODBC profiles for your application, use your renamed ODBC driver, not the standard Adaptive Server Anywhere n.n driver. Mate thanks You saved my life. Hi, I follow all the steps and i get the following error cant load the install procedures because an error: 193.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |