Changing Pervasive Terminal Services Security

Last Modified 8/23/2004 - Article ID#:  K000163

This document applies to Pervasive Version 7.94 and earlier.  If the solutions below do not work, install the Pervasive 9.1 client and on the workstation or IRM Bridge Server.  Related documents:

• Installation of Current Pervasive Client on the IRM Server
• Correcting a Stat 94 - Editing IRM Bridge  Server SAT Entries
• Pervasive Client Must be installed as a Service on Citrix Server or Windows Terminal Server

Upgrade to Current Pervasive Version

When troubleshooting any problem with the Pervasive Database, the first step is always to verify the version of the Pervasive Engine that is installed on the Data Server and the version of the Pervasive Client on the problem workstation.   If either the engine or client are not current they must be updated.  See "How to determine the Pervasive Version".

Upgrade Steps for Pervasive Version 10 or 11

Upgrading to Pervasive version 10 or 11 can be done without calling RDP support.  Customers using a Windows 2008 server must run Pervasive version 10 or higher, since Pervasive version 9 does not work on 2008 servers and is no longer supported.

Note:  All users must exit RDP during the upgrade, including the IRM and all interface workstations.  Schedule this installation at a time when the system can be down for approximately 4 - 8 hours AND when RDP support is open.  RDP 24-hour support is not available for Pervasive Updates.

1. Hardware Requirements:  Workstations must be Windows XP, Vista or Windows 7 with at least one (1) gigabyte of RAM, and the data server must be Windows 2003 or 2008 with at least two (2) gigabytes.
   
2. To install Pervasive P.SQL for Windows, you must have full administrator-level rights on the machine where it will be installed.  This includes the Server and all workstations (Pervasive Client installations).

Pervasive Server Installation

1. Uninstall prior Pervasive version.  Customers should never install an update over a prior version.  Follow all steps listed in Uninstall Pervasive which uses images from 9.52 as a reference.  Steps to uninstall should be the same regardless of version.  Be sure to reboot when the steps indicate to insure the old version is removed correctly.
   
   
2. Create a Pervasive folder in the RDPNT/RDP directory.  For example, with the F:/RDPNT/RDP folder selected, click File from the main menu and select New/Folder.  Enter Pervasive as the new folder name.



3. Copy the entire Contents from the PSQL installation disk into the new F:/RDPNT/RDP/Pervasive folder.  For example, select D:/ (disk drive) from My Computer, select all files, right-click and select Copy:
   
   Select the F:/RDPNT/RDP/Pervasive folder, right-click and Paste the PSQL disk contents into the newly created Pervasive folder.
   
   
4. From the Start menu, select Run, enter "notepad", and click OK to open a new Notepad document.  Enter the License Key for your Pervasive installation disk (located on the outside of the CD package). 
   
5. Click File then Save As, and navigate to the RDPNT/RDP/Pervasive folder and save the document as PervasiveLicenseKey.txt.
   
6. Follow all steps listed in Install Pervasive Server Version 10 or 11.  Be sure to reboot when the steps indicate to insure the old version is removed correctly.
   
   
7. Create ODBC connection for RDP.  Pervasive's website offers the following link for Error 1918. Error Installing ODBC driver.
   
   
8. Navigate to the following location on your RDP Data server C:\Documents and Settings\All Users\Application Data\Pervasive Software\PSQL\samples.  Select the Samples.btr file and copy into your newly created RDPNT\RDP\Pervasive folder.  Do not copy the Samples.btr file from the disk.
   
   
   
9. Test connections.

Pervasive Client Installation (on all workstations and IRM Server)

1. You cannot install the client remotely.  You must physically sit at each workstation and logon as a user with ADMINISTRATOR RIGHTS to the workstation to install the Pervasive client, or to use RDPWin software.  The Pervasive client software must be installed on all workstations, the IRM server, and all Terminal/Citrix Servers.
    
2. Map a drive from the workstation to the RDPNT folder on the data server
   
   
3. If a previous version of Pervasive Client is on the workstation, uninstall it and then reboot the workstation. 
   
   
4. Install Pervasive Client Version 10 or Workgroup Version 10.
   
   
5. Test connections (using specific Client configuration instructions).
   
   
6. Repeat the uninstall steps for the old version and the installation steps for Version 10 for each server (including the IRM), interface computers, and RDPWin workstations.

NOTE:  The PSQL Workgroup engine is only needed for installations where a single user workstation will be running RDP.  All other machines including the IRM, interface computers and RDPWin workstations can run on the PSQL 10 client (service) installation

See also:

• How to determine the Version of Pervasive
• Upgrade pricing and installation procedures

Modify Key with RegEdit
Pervasive Version 7.94 and 8.xx

Starting with Pervasive Version 7.94, there is a new key in the registry that restricts or allows Terminal Services to have full control from a Pervasive level.  The default for this new key is to allow Terminal Services NO CONTROL.  This new key must be changed on both the IRM Bridge server and the Data Server in order for RDP support to connect to either machine with Terminal Services and have full control.

This key must be changed with the steps below:

1. On the IRM server, select Start-Run and enter REGEDIT.  Expand the following Key:
   
   HKEY_LOCAL_MACHINE | SOFTWARE | Pervasive Software | Utilities Interface | Settings | Restricted Access
   
   Note: If the " Utilities Interface" key does not exist see "Creating the Registry Key" below.
   

2. The value name should appear as "Restricted Access on WTS Client'", with a default value of "1", which means "no access'.  Change the value to "0" and select OK.   The display should appear similar to the one below.  When done, close Regedit.  The server will have to be rebooted for the changes to take effect.  You cannot change any other settings, such as the SAT entries, until you reboot and reconnect with Terminal Services.  

3)  Repeat Steps 1 and 2 for the data server.  It is critical to change this key on both the IRM server and the Data Server to allow RDP Support to have full control with Terminal Services to either machine.

4)   When done, close Regedit.  You must reboot the IRM server for the changes to take effect. Do not try to test the IRM until you Reboot the IRM server.   You cannot change any other settings, such as the SAT entries, until you reboot and reconnect with Terminal Services.   

What to do if the Registry Key Does not Exist

If the registry key for "Restricted Access on WTS client" does not exist, and the Pervasive Version on the server is 7.94, the key can be created as follows: 

Repeat the above steps for the DataServer. The key will also not exist if connected to a server running the Pervasive WORKGROUP engine.

 Re-installation of Pervasive  

If the Pervasive engine is removed from the server or the Pervasive Client is removed from the IRM Bridge server, the steps in this document must be performed again. 

• For details on removing Pervasive, see  " Uninstalling Pervasive Software ".

• For details on re-installation of Pervasive, see "Installation of Pervasive"

Troubleshooting Pervasive.SQL Database

The following links may be useful when troubleshooting problems with Pervasive Software and Resort Data Processing.  The following support phone numbers are also available:

The current version of Pervasive is much faster and more reliable than older versions.  If the solutions below are not helpful, it may be necessary to upgrade to the current version of Pervasive.  Please review the following:

• Installation of v10 Pervasive Client on the IRM Server
• How to Verify the Version of Pervasive Engine on the RDP Data Server 
• Order Pervasive by calling RDP Sales

IRM Troubleshooting Links