Skip to content
Menu
Menu

Knowledge Base

KB050153 | INCORRECT ODBC ENTRY AFTER ELVIS UPDATE

KB050153 | INCORRECT ODBC ENTRY AFTER ELVIS UPDATE

Product: Elvis
Version: 2.7
Booth: 2008-04-23

Symptoms

After the installation of a new Elvis version, it is no longer possible to open a project with the Elvis configuration and the Elvis process server. An error message appears in the configuration that contains a problem with the database (e.g. “Driver’s SQLAllocHandle on SQL_HANDLE_DBC failed.”), this error message is written to the ElvisSvr .log at the process server.

Cause

This is caused by an ODBC entry that was only incompletely updated during the update. Parts of the corresponding registry branch “HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST. INI\Sybase SQL Anywhere 5.0 for Elvis” also point to the old Elvis directory. It is also possible that some of the ODBC files (wod50t.dll, wl50ent.dll, wtr50t.dll) have not been transferred to the new directory.

Solution

We provide a small tool that repairs the ODBC entry. Please proceed as follows:

  • You must be logged in as a Windows administrator to make the correction.
  • Extract FixElvisOdbc.exe from the ZIP file to the current Elvis directory (e.g. C:\Program Files\Elvis 2.7).
  • Run the file by double-clicking.
  • If you encounter any error messages, please contact our support.

Support Area

KB050153 | INCORRECT ODBC ENTRY AFTER ELVIS UPDATE

Knowledge Base

Here you will find answers, solutions to problems and examples of our products.
KB050153 | INCORRECT ODBC ENTRY AFTER ELVIS UPDATE

Case Studies

Successful in use: practical examples of our products and individual developments.
KB050153 | INCORRECT ODBC ENTRY AFTER ELVIS UPDATE

Support

Describe your concern using our support form.
KB050153 | INCORRECT ODBC ENTRY AFTER ELVIS UPDATE

License registration

Register your Elvis license!

IT GmbH · An der Kaufleite 12 · D-90562 Kalchreuth

© Copyright 2024. IT GmbH | Webdesign by Appear Online