Home Sales Crystal KB Contact Us  
RDP Support  


Connect to Support with WebEx
RDPWin KB IRM.Net RDPWin3 & PCI Compliance Search

Correcting a Stat 94 - Editing IRM Bridge 
Server SAT Entries

Revised 9/8/2005 - Article ID#: KI0009

Note:  If the solutions below do not work, install the Pervasive 9.1 client and on the IRM Bridge Server.  See "Installation of Current Pervasive Client on the IRM Server".

Pervasive uses a "SAT" entry in the Registry to store important information about the connection between the Pervasive Client (the IRM or workstation) and the Pervasive Server (the RDP Data Server).   When the IRM or workstation client first connects to the RDP data server running Pervasive, these SAT entries are created in the registry.  If they are created incorrectly the RDP product may not start.  Common errors are "Stat 94" and "Stat 171" when starting RDPDOS, IRM, or RDPWIN.  

This article is specific to the problem of a Stat 94 when connecting RDP's IRM to a Data Server.  The SAT entries can also cause other problems - See "Pervasive Links" below.

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

Upgrading to Pervasive version 10 can be done without calling RDP support.  Customers using a Windows 2008 server must run Pervasive version 10, since Pervasive version 9 does not work on 2008 servers.

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 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.

    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.

  3. 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). 
  4. Click File then Save As, and navigate to the RDPNT/RDP/Pervasive folder and save the document as PervasiveLicenseKey.txt.
  5. Follow all steps listed in Install Pervasive Server Version 10.  Be sure to reboot when the steps indicate to insure the old version is removed correctly.

  6. Create ODBC connection for RDP.  Pervasive's website offers the following link for Error 1918. Error Installing ODBC driver.

  7. 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.


  8. 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:

Verify Permissions and Sharing on RDPNT and Sub-Folders 11/7/2006

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 - Stat 94 on IRM Connecting to Data Server (Security Violation)

Use the following steps to potentially fix a Stat 94 on the IRM bridge server when connecting to the Data Server.

  1. Sit at the IRM Server.  If using Terminal services to connect to the IRM server, you must perform the steps in K000163.htm first to allow terminal services access.  This is critical.
  2. Verify the version of Pervasive on the data server and the IRM client.  The Stat 94 problem on the IRM usually only occurs when the Data Server is running Pervasive Version 7.94.  If a Stat 94 occurs with Pervasive Version 8.x or higher, the problem is usually not SAT entries, but "normal" security issue, such as passwords, rights to folders, etc.  The version of Pervasive on the Server can be determine by using Windows Explorer to find the file \PVSW\BIN\NTBTRV.EXE on the data server.  Right click on this file, left click properties, then click the "Version" tab.  Or See - K000017 for more information on Pervasive Versions.
  3. If the Data server is running Pervasive 7.94, you must then verify that the "hot fixes" have been installed, which were released after the last service pack (SP4).  To verify, look for the file C:\PVSW\BIN\W3NSL22E.DLL on the data server.  If this file does not exist, it is critical to perform all the steps in "Updating Pervasive Data Server and IRM Client to Version 7.94 Hot Fixes".  
  4. If the Pervasive Server is less than 7.94, you must update the data server and the IRM client to Pervasive 7.94 or higher.  Even if the data server is already at version 7.94, you must verify the existence of the file "W3NSL22E.DLL" in the C:\PVSW\PIN folder on the IRM.   After the data server is on Version 7.94, the file W3NSL22E.DLL can be copied from the  C:\PVSW\BIN folder on the data server to the C:\PVSW\BIN folder on the IRM.  See Updating IRM Client to Version 7.94.  
  5. Access the Registry editor with  Start | Run | Regedit.  Go to the following key, which is used by the IRM to find the data server:
    Version 7.94

    HKEY_Users | Default | Software | Pervasive Software | Communications Requester | Version 7 | Settings.  
    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.  

     

  6. Delete the "NumSatEntries" key, as well as SatEntry0, and SatEntry1 (or 2, 3) if they exist. 
  7. Exit Regedit and reboot the IRM server.  You must Reboot for to have the keys reset properly.
  8. After the IRM reboots, start IRMTOOLS.HTM to test the IRM.  This should create the correct SAT entries.  If the entries are created incorrectly it usually means that DNS is not set up correctly (see "setting up DNS" below).  If using terminal services to start the IRM, make sure you have performed all the steps in K000163 first.  See:K000163.htm. The problem may also be you did not copy the file W3NSL22E.DLL properly (see Updating to Version 7.94)
  9. Restart the Registry editor and go to the same key to verify it is correct.  A correct setting appears as follows:

Interpretation of a Pervasive SAT Entry

7/22/2005 The following is a copy of an Email from Pervasive Support with respect to SAT entries. The SAT entry on the IRM client will be in a different form depending on what address resolution mechanism was used by the IRM to communicate with the data server.  Ideally the address resolution should be done by DNS.  If an internal DNS server is set up correctly, the IRM almost always works.  When DNS is not set up correctly, the IRM will fail periodically.  See Setting up DNS Correctly below. 

 

Address 
Resolution Type		 Forms of SAT Entry
DNS serverName,nosServerType,addrResolutionType,serverType,addressFamily,npAuthFailed

For example, a valid entry is (RDPDATA, 2, 4, 0, 1, 0).  The paramaters are explained below using variables  (RDPDATA, A, B, C, D, E)
NETBIOS serverName,nosServerType,addrResolutionType,netbiosLana,serverType,addressFamily
Otherwise serverName,nosServerType,addrResolutionType,serverType,addressFamily

Variable Category Values
A

nosServerType

The "A" variable indicates what type of server the client is communicating with.  "nosServerType" stands for " Network Operating System server type", with possible values to the right.

For RDP this should "2" - Windows
Setting Explanation
0 UNKNOWN_SERVER
1 NETWARE_SERVER
2

Windows XP, 2000 or 2003
(this is what we want)
3 LOCAL_DRIVE
4 WINCE_SERVER (Windows CE)
B

addrResolutionType

The "B" variable, addrResolutionType, indicates how the TCP/IP address for the data server was obtained by the client.  

As long as DNS is set up correctly, the "B" variable can be "3" or "4" for RDP.    However, if DNS is not set up correctly there will usually be problems no matter what the "B" variable is.   See Setting up DNS Correctly below. 

Text from Pervasive Article:

3 (Named Pipe) - requires a Microsoft networking client and that the target server be an NT server engine. For Btrieve applications connecting to an NT server engine, this should always be the resolution method used. Note that you would not see this when the target is a Workgroup engine, even if the engine itself is running on a NT machine; 

4 (DNS) - requires TCP/IP; typically you should only see this for NetWare servers, but you also can see it for P.SQL 2000 DSN's that specify an IP address as the server name. 5 (Windows CE) 6 (NetBIOS)

  
Setting Address Resolution Mechanism Used 
0 Unknown Address Resolution
1 Bindery Address Resolution 
2  NDS - (IPX/SPX) - Novell 
3 Named Pipe 
(this is what we want, but 4 ok)
4 DNS using TCP/IP
4 is ok if DNS Setup correctly
5 Windows CE
6 NetBIOS

Warning:  Always set the client - Microkernel Router, Access to:

  • Use Local Microkernel Engine
  • Use Remote MicroKernal Engine
  • The only supported protocol should be TCP/IP on all Clients and the server

 

The "C" variable changes based on the setting of the "B" variable, address resolution type.  Assuming DNS is set up correctly, and the paramater above is a "4", the "C" variable is:

serverType

This parameter should always be "0" for RDP because we communicate with the Btrieve Transactional Engine. 

For RDP this should be a "0" - Btrieve

  
Setting Which Pervasive "Server"  
0 BTRIEVE SERVER
(this is what we want)
1 SCALABLE SQL SERVER
2 UNKNOWN COMM SERVER
3 SIMBA SERVER 
D The "D" variable for a DNS server is the indicates what protocol was used to communicate to the server, and is called:

Address Family

For RDP this should be a "1" - TCPIP

  
Setting Protocol Used  
0 ISPX
1 TCPIP

(this is what we want)
2 NAME_PIPE
3 UNKNOWN_TRANSPORT
4 NETBIOS
E The "E" variable for a DNS is used to determine if a Named Pipe authentication failed previously, and if true, don't try again.   it is called:

npAuthFailed 

For RDP this should be a "0" - False.  If this is set to "1", RDP will often get an error 171.  

  
Setting Indication 
0  False

(this is what we want)
1 True

Note: If this is set to "1", RDPDOS, IRM, and RDPWIN will often not start and product an Error 171.  

For example a good SAT entry for a Windows 2000 or 2003 data server that has the name RDPDATA would be:

 RDPDATA,2,3,0,1,0  or  RDPDATA,2,4,0,1,0

Sat Entry For RDPDOS

If there are problems with RDPDOS accessing the data server, it may be necessary to delete and recreate the SAT entries in the following key, which is used by RDPDOS to access the DataServer.:

Version 7.94

HKEY_CURRENT_USER | Software | Pervasive Software | Communications Requester | Version 7 | Settings. 

 

Again delete both the "NumSatEntries" key, as well as SatEntry0, and SatEntry1 (or 2, 3) if they exist.  Start RDPDOS to recreate the keys and verify they are correct.

Elimination of Novell IPX/SPX From Supported Protocols

IF the SAT entry indicates a "Novell Server" (for example, 2000Server, 1,4,0), this may cause the IRM to still generate an Stat 94.  This problem may be solved by setting the Pervasive Server and the IRM Bridge Server Pervasive Client to only use the TCP/IP protocol.  The problem can also be caused if the Novell Client software is installed on either the Data Server or IRM bridge.  

  1. Start the Pervasive Control Center from the IRM Bridge 

  2. Expand the Server Name of the IRM and select "Configuration"

  3. Select the "client" configuration and then "Communication Protocols".  

  4. Change the supported protocols to TCP/IP only on all clients and the server.

  5. Delete the SAT entries again

  6. The IRM must be rebooted for the change to take effect.  

  7. Start the IRM again with IRMTOOLS.HTM.   

  8. Recheck the SAT entries - they should no longer indicate a Novell Server (ie, we want  "Servername,2,4,0").  

                  Setting up DNS Correctly

If the IRM Bridge server does not set the SAT Entries correctly it usually means that DNS is not set up correctly on either the IRM Bridge Server or the Data Server.  Test as follows:

  1. From the IRM Bridge command prompt (DOS Prompt), type NSLOOKUP. 

  2. At the ">" prompt, type in the data server name.  This should return the correct IP Address using forward DNS Lookup.

  3. At the ">" prompt, type in the IP Address of the Data Server.  This should return the correct name using Reverse DNS Lookup.

  4. From the Data Server command prompt (DOS Prompt), type NSLOOKUP. 

  5. At the ">" prompt, type in the IRM server name.  This should return the correct IP Address using forward DNS Lookup

  6. At the ">" prompt, type in the IP Address of the IRM.  This should return the correct name, using Reverse DNS Lookup.

  7. If any of the four values above are wrong there is a critical problem with DN and the IRM will never work reliably.  The key is to:

  • Install DNS Correctly on the data server - see:  RDP Data Server Installation

  • The preferred DNS server of both the IRM server and Data Server must be the same, which is usually the IP address of the Data Server. 

Use Pervasive Version 9.xx or higher Client on IRM server

If all else fails, and the customer does not wish to update to Pervasive 9.xx on the server, you can try to put Pervasive 9.xx (or higher) client on the IRM bridge and communiate with the Pervasive 7.94 on the data server.  The Pervasive clients are backwards compatible and this may work.  The Version 9 client doesn't have the same SAT problems as version 7.94.  However, this is not a recommended or supported solution.

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:

Pervasive Support: 800-287-4383
RDP Standard Hours Support 970-845-7108
RDP Support Home Page www.Resortdata.com/customers/Customer/htm

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:

Hyperlink Pervasive Database Topic
Overview Overview of Pervasive Software Including Installation and Upgrade Procedures
Purchase How to Purchase Pervasive.SQL from Resort Data Processing
K000060 Verify the Pervasive Version
KWin0200 Pervasive Workgroup Engine Must Be Installed as a Service on Citrix Server or Windows Terminal Server
K000188 Delete Pervasive Users Without Administrator Rights
KI0009 Correct Stat 94 on the IRM Bridge Server - Change SAT Entries
K000186 Pervasive Versions 7 or Less Do Not Work and Are Not Supported by RDP
K000187 Correct Stat 171 in RDP-DOS, IRM, or RDPWin 
K000163 Install and Configure Pervasive.SQL Using Terminal Services - IRM Server and Data Server
K000057 RDP No Longer Supports Novell Servers (Netware)
K000055 RDP Requires All Workstations use XP Professional with Pervasive
Installation Installing Pervasive on a Windows 2000/2003 Server and on Workstations
K000053 Uninstalling Pervasive from the Data Server, IRM, or Client Workstation
K000189 Stat 46 with RDP000 or RDP910 Using Pervasive Version 9

 
Links to RDP Data Server and Internet Reservation Module (IRM) documents

Support Home  RDPWin3 & PCI Compliance Enhancement Requests Open A Web Support Ticket
Training 3rd Party Interfaces RDP Sales Website Contact Us