Prev | Getting Started with Pervasive.SQL (Server edition) | Next |
Issues After Uninstalling Pervasive.SQL on Windows
When you uninstall Pervasive.SQL using the Add/Remove Programs mechanism in Windows, you should not have any database engine files remaining on your system. However, some actions such as installing multiple times to the same machine or restoring archived components can cause a significant number of files to be left on your system. This is a side effect of how the installation process works with the Windows operating system and can be corrected using Pervasive System Analyzer (PSA).
In the situations described previously, the files are left because Windows has the files marked with usage counts that indicate that they are being used by more than one program, and therefore the uninstallation program does not remove them from your system. This is expected behavior, but it may lead you to conclude that the Pervasive.SQL uninstall program is not functioning correctly.
In order to correct this condition, run the PSA Delete function and remove all Pervasive components from your system. PSA deletes the files and the Windows registry entries that caused the files to remain on your system. At that point, you should have a system that is free of Pervasive.SQL components, and the next installation of Pervasive.SQL will have correct usage counts.
For information on how to use the PSA Delete function, see Pervasive System Analyzer (PSA) in Pervasive.SQL User's Guide.
Prev Obtaining File, Client, and Engine Version Number |
Contents Up Check for Revisions | Next Engine and Client Version Conflicts |