A common thing that people tried to do in the PSQL2000i days was to
leverage a "network installation" for workstations, in order to avoid
having to run new patches on each computer.
However, and we found this the hard way, when you upgrade a system that
had a "Network Installation" in the past, problems can arise. Since
the upgrade software detects the fact that PSQL2000i is on the
workstation, it starts by archiving off all of the old software from
the install directory. In this case, the "install directory" points to
the shared network location -- usually the servers \PVSW\BIN directory.
Thus, the upgrade of the workstation very cleanly strips out all
existing Pervasive components -- from the server.
What we found was one possible solution: Go into RegEdit and remove
the HKLM\Software\Pervasive Software registry key, then rerun the v8.6
installer. This will prevent the installer from knowing about the old
network directory.
BTW, PSQLV8's most current version is v8.7, also known as Service Pack
3. You may also wish to upgrade the engine and clients before you get
too far into the process. Get the patch from www.pervasive.com.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 03/2007 ***
PJ wrote:
Quote:
I have a site that seems to be having a persistant problem with the
Pervasive server software just becoming uninstalled. I have checked
the database for corruption, viruses, worms, etc.....
The removal of only part of the Pervasive software does not seem to
have any kind of pattern as to when it will be removed and it seems
like it just to started to happen when the site was upgraded from
Pervasive 2000i SQL to Pervasive 8.6, any suggestions.
The site is running on a Windows 2000 Server |