Is there a solution? "Error 1918.Error installing ODBC driver Pervasive ODBC Engine Interface, ODBC error 0: ."

Last post 08-08-2011 11:02 AM by InstallGuy. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 08-05-2011 9:44 AM

    Is there a solution? "Error 1918.Error installing ODBC driver Pervasive ODBC Engine Interface, ODBC error 0: ."

    I'm encountering this error message when attempting to re-install Pervasive 10.3. Reason for the re-install is a program (Acer edata security) was causing a conflict with a client's business applications but instead of uninstalling the application, they rolled the OS back to the last restore point. I have read the information here but have not been successful implementing the suggested solutions (thanks Bill): Check your ODBC definitions to make sure all the paths specified are correct for your new install. Check in the registry in HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Pervasive ODBC Client Interface HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Pervasive ODBC Engine Interface Keep in mind that for 64-bit systems these keys are found under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node Bill Bach Goldstar Software Inc. www.goldstarsoftware.com In fact I have fully uninstalled pervasive from his computer, removed the above pervasive registry entries and all other pervasive entries in the registry, then re-installed with admin rights. = no success. Rinse, wash, repeat = no success. Can someone provide more insight to get them back up and running? Computer : Windows Vista x86, running BusinessVision and BVEssentials. Thank you, Stephen Lake
  • 08-05-2011 11:02 AM In reply to

    Re: Is there a solution? "Error 1918.Error installing ODBC driver Pervasive ODBC Engine Interface, ODBC error 0: ."

    To completely remove PSQL:

    First, the best way to uninstall PSQL v10.0 and higher is to use the entry in Add/Remove Programs [ARP, aka "Programs and Features"] so check in ARP to see if "Pervasive PSQL" is still listed and attempt to uninstall if it is.  If the uninstall fails for any reason then the PSQL configuration has been corrupted somehow and you should first attempt to "repair" the current installation using the "Change" or "Modify" option in ARP (note that you may need access to the original installation source location or media) before attempting to uninstall it using ARP.  For a 'Repair', once you are presented with the "Program Maintenance" dialog select the 'Repair' option and complete the maintenance installation to repair PSQL.  After a successful repair, then attempt to uninstall PSQL using ARP.  After this, if you still see a "Pervasive PSQL" entry in ARP [rare] then this would indicate a more serious problem involving a corrupt PSQL product registration with the Windows Installer service on that system, which would require the use of 3rd party tools to properly clean up.

    If there are no PSQL entries listed in Add/Remove Programs then it should be OK to manually cleanup any remaining PSQL registry and/or program files from the system (see below).  Just make sure you backup/copy any of your PSQL data files before attempting to manually make changes to the system registry or before deleting PSQL program files.

    To manually cleanup the system after an unsuccessful PSQL uninstall:

    1) Make sure any running Pervasive services or applications are stopped.

    Open the Services Control Panel (start-->run-->services.msc) and stop any running "Pervasive" services.

    If you have PSQL Workgroup Engine installed then make sure the Workgroup Engine is stopped ("Stop Workgroup Engine" shortcut in Pervasive program menu folder).

    2) Make sure the ODBC driver settings are in fact cleaned up in the system registry: 

    NOTE: You may need to manually re-create Pervasive ODBC DSNs (or re-install any 3rd party software using PSQL) after cleanup.

    Before you do this make sure you export and save the HKLM\SOFTWARE\[Wow6432Node\]ODBC\ key(s). The "Wow6432Node" location will only be present on 64-bit systems.

    Open the ODBC Administrator and check the System DSN tab.  If you want to install from scratch, delete any DSNs using the "Pervasive ODBC Engine [or Client] Interface" driver. Then check the Drivers tab and delete any "Pervasive ODBC Engine [or Client] Interface" drivers. If your system is running a 64-bit OS note that there are two separate ODBC Administrators and you will need to duplicate this step using both the 32-bit version (%windir%\SysWOW64\odbcad32.exe) and the 64-bit version (%windir%\system32\odbcad32.exe).

    3) Make sure the actual PSQL ODBC driver files (DLLs) are removed from all locations on the disk.

    Search all locations on all disks for any of the following files: w3odbcci.dll, w3odbccs.dll, w3odbcei.dll, w3odbces.dll (for anyone using v11 out there also check for w64odbcei.dll, odbcci64.dll, and odbccs64.dll).

    Make a backup of the files and then delete them.

    Lastly, re-install PSQL.

  • 08-05-2011 6:19 PM In reply to

    Re: Is there a solution? "Error 1918.Error installing ODBC driver Pervasive ODBC Engine Interface, ODBC error 0: ."

    Unfortunately, it is again unsuccessful. Result = Error 1918. See below for steps taken and results.

    Before Pervasive was un-installed, the 'Repair' option was attempted without success. Same 1918 Error.

    1) Checked all Services.msc and did not find any services with the name Pervasive. Check.

    2) Opened ODBC Administrator and found 3 PSQL (Pervasive) entries. Attempted to configure and received the following messages

    - "The routines for Pervasive ODBC Engine interface driver could not be found. Please re-install component not found in registry."

    - Same message given when attempting to "Remove" non-functional DSN's.

    - Removed DSN's by deleting them from HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI, then again deleted all keys that reference PERVASIVE.

    3) Searched computer for all files named w3odbcci.dll, w3odbccs.dll, w3odbcei.dll or w3odbces.dll. Finding none, I rebooted machine.

    Installed program via command prompt as administrator - Error 1918 Urrrggghh!

    What else could be causing PSQL v 10.3 to fault during the install? There must be a way to allow pervasive to install, right?

  • 08-08-2011 11:02 AM In reply to

    Re: Is there a solution? "Error 1918.Error installing ODBC driver Pervasive ODBC Engine Interface, ODBC error 0: ."

    The fact that you can't run the uninstall from Add/Remove Programs and that none of the PSQL ODBC DLLs exist on the system sounds like you tried to remove PSQL from the system without actually using the uninstall in Add/Remove Programs, resulting in a severly corrupt PSQL "configuration" where the PSQL information in the system registry does not match what is actually installed on the system (including the issue with the product registration with Windows Installer mentioned in my previous response).

    In other words, now you have a bogus PSQL product registration with the Windows Installer service as well as bogus PSQL entries in the system registry that reference files that are not actually on the system. This is why you can't run any PSQL install action correctly - because the install is detecting the ODBC entries in the registry and then failing to find the referenced files on the hard drive.

    IF YOU WILL BE RE-INSTALLING THE EXACT SAME VERSION OF PSQL that is currently listed in Add/Remove Programs (v10 SP3 / 10.3 in your case), you don't need to fix the bogus PSQL product registration with the Windows Installer service as re-installing later will fix that problem.  If you are installing a different version (including later service packs for the same major version) then you will need to contact Pervasive support for assistance in cleaning up the bogus MSI entry.

    To clean up the system registry issues, search the registry locations below for any keys that have values which reference files in the PSQL "bin" folder where the referenced file does not actually exist in that location on the hard drive. Export those registry keys to a file to back them up and then delete the key or key values described below:

    On 32-bit and 64-bit systems:
    HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<key_for_psql_dsn_name>\  [delete the key, this will usually have a "Driver=<path_to_psql_odbc_dll>" value entry]
    HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources\   [delete the key, this will usually have a "<key_for_psql_dsn_name>=Pervasive ODBC Engline/Client Interface" value entry]
    HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers\  [delete only the value(s) named "Pervasive ODBC Engline/Client" - leave all other values]
    HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Pervasive ODBC Client Interface\  [delete the key]
    HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Pervasive ODBC Engine Interface\  [delete the key]
    HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Pervasive Software OEM to ANSI\  [delete the key]

    64-bit systems only:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\<key_for_psql_dsn_name>\  [delete the key, this will usually have a "Driver=<path_to_psql_odbc_dll>" value entry]
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources\   [delete the key, this will usually have a "<key_for_psql_dsn_name>=Pervasive ODBC Engline/Client Interface" value entry]
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers\  [delete only the value(s) named "Pervasive ODBC Engline/Client" - leave all other values]
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Pervasive ODBC Client Interface\  [delete the key]
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Pervasive ODBC Engine Interface\  [delete the key]
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Pervasive Software OEM to ANSI\  [delete the key]


    Next, export and delete the main PSQL registry key and any of the service keys listed below that exist (not all of them will):

    On 32-bit and 64-bit systems:
    HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\psqlCE\
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\psqlWGE\
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Pervasive.SQL (relational)\
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Pervasive.SQL (transactional)\
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\xiocache
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\xiodf
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\xiofsf

    64-bit systems only:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pervasive Software\

    As long as all of the entries above are manually cleaned up then you should be able to re-install PSQL v10 SP3 using the original installation media without getting the ODBC error message.  You will not be able to use the bogus entry in Add/Remove Programs to re-install PSQL until you have actually run the setup EXE from the original installation source (which will re-register the PSQL product with Windows Installer using the correct configuration information).

     

Page 1 of 1 (4 items)