Correcting Stat 171 in RDPDOS, IRM, or RDPWin 

Updated 2/12/2007  - Article ID#: K000187

Under some conditions RDPDOS, IRM, and RDPWin cannot open Pervasive files on the data server and will return one of the following errors when starting:

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 11

Upgrading to Pervasive version 11 can be done without calling RDP support.  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 7 or higher with at least one (2) gigabytes of RAM, and the data server must be Windows 2008 or 2012 with at least eight 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 11 or Workgroup Version 10 or 11.
   
   
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

Verify Permissions and Sharing on RDPNT and Sub-Folders 

Verify that the security is set correctly as follows:

1. On the data server, start Windows Explorer
2. Highlight the RDPNT folder and right click properties and click the Security tab
3. Make sure the RDP group is listed as "full control"
4. Click the "Advanced button" and check the check box for "Replace entries on all child objects with entries shown here that apply to child objects" and click OK.  This will force the RDP group to be listed on the RDP folder under RDPNT and all programs and files in the RDP folder and sub-folders
5. Also check the "sharing" tab on RDPNT and make sure that EVERYONE has full control.  Or you can add the RDP group and give it full control

Solution - Change SAT Entry with Regedit

The solution for all products (RDPDOS, IRM, or RDPWIN) is to change the SAT entry with Regedit as follows.  Note, for a more complete explanation of Pervasive SAT entries, see "KI0009 - Correcting a Stat 94 on the IRM Bridge Server - Changing SAT Entries"

1. Start-Run-Regedit.  Browse to the following key:
   

   Version 7.94	Version 7.xx is not supported
   Version 8.xx	HKEY_Local_Machine | Software | Pervasive Software | Communications Requester | Version 8 | Settings.
   Version 9.xx	HKEY_Local_Machine | Software | Pervasive Software | Communications Requester | Version 9 | Settings.

2. Delete the "NumSatEntries" key, as well as SatEntry0, and SatEntry1 (or 2, 3) if they exist.  

3. Close Regedit and restart RDP (RDPDOS, IRM, or RDPWIN).  This should recreate the SAT entry

4. Verify that SatEntry0 appears similar to:  RDPDataz,2,4,0,1,0.  The "0" at the end is the critical problem.  The error 171 occurs because this is a "1".  

   BAD SAT Entry	RDPDataz,2,4,0,1,1
   GOOD SAT Entry  (appears Below)	RDPDataz,2,4,0,1,0
   The Regedit view of a good Pervasive Version 9 SAT entry appears below. For  a more complete explanation of Pervasive SAT entries, see "KI0009 - Correcting a Stat 94 on the IRM Bridge Server - Changing SAT Entries"

For  a more complete explanation of Pervasive SAT entries, see "KI0009 - Correcting a Stat 94 on the IRM Bridge Server - Changing SAT Entries"   If the problem continues, update the client software to Version 9.1 as described below.  

How to determine the Version of Pervasive on the Data Server

• How to determine the Version 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 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