PDS Med
Technical Support
1600 N. Lorraine 1-800-283-7543
Hutchinson, KS
PDS/Pervasive Version 8.1 Configuration and Troubleshooting
Revised 10-06-2004
Disclaimer:
Professional Data Services does not support or guarantee compatibility with third-party software or hardware, even if Professional Data Services has recommended such products.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, AND IS SUBJECT TO CHANGE WITHOUT PRIOR NOTICE. PROFESSIONAL DATA SERVICES, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL PROFESSIONAL DATA SERVICES OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF PROFESSIONAL DATA SERVICES OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY.
Most problems running PDS are related to the Pervasive or PDS configuration or Networking problems.
PDS Configuration 2
Pervasive Configuration 2
Pervasive.SQL V8 Workgroup (Peer to Peer Network) 2
Pervasive Server Configuration (Peer to Peer) 3
Pervasive Workstation Configuration (Peer to Peer) 4
Pervasive.SQL V8 Server (Client Server Network) 5
Pervasive Server Configuration (Client Server) 5
Pervasive Workstation Configuration (Client Server) 6
Pervasive System Analyzer 7
Testing Pervasive 7
Uninstalling Pervasive 7
Common Errors 9
3012: Local engine is not accessible to the MicroKernel router 9
3014: The MicroKernel router cannot find an engine 9
3105: No available transport protocol for the Pervasive Network Services Layer 9
116: The file is owned by another Microkernel engine acting as a Gateway 10
94: The application encountered a permission error 10
161: The maximum number of user count licenses has been reached 10
PDS Configuration
PDS should not be installed on the server, or main computer, off of the root drive. The PDS folder, TTG has to be under the APPS folder on the server, shared as APPS, with Full Control to All Users. Also Security on the folder and subfolders must be set to Full Control for All Users.
Example: C:\APPS\TTG
The network must be in good working condition. You should be able to ping the Server from any Workstation, by name. Pervasive must be able to resolve the Server name to its IP address. Using an external source for Name Resolution (such as DSL) usually causes problems. The Server should have a static (non-changing) IP address.
Windows 2000, NT, and XP Pro workstations should have local administrative rights in order for PDS to function correctly.
On all PCs (including the server) there should be a mapped network drive to the APPS share on the server. Double click on my computer and find the mapped network drive (usually P:). It should look like “apps on server office”. Double click on the network drive (P:). You should be able to see a TTG folder. IF YOU RECEIVE ANY ERRORS ACCESSING THIS NETWORK DRIVE THEN THERE IS A CONNECTION PROBLEM BETWEEN THIS WORKSTATION AND THE SERVER
The PDS install (\TTG\wssetup.exe) should be run through the mapped drive. Example: P:\TTG\wssetup (P: is mapped to APPS) This will install PDS on the PC with the correct paths. The Start in Path on the PDS shortcut should NOT be a UNC path (example \\server\apps\ttg). It should be driveletter:\ttg. (example P:\ttg)
PDS and Pervasive should always be installed via Add\Remove Programs on any server running Terminal Services. Otherwise it will not run properly.
Pervasive Configuration
There are two versions of Pervasive used by PDS. The Workgroup Engine is used in a Peer-to-Peer network. The Server Engine is used on a Windows 2000/2003 or NT server. The Workgroup Engine supports a maximum of five concurrent users. Any systems with more than 5 users running PDS require the Server Engine version.
Pervasive.SQL V8 Workgroup (Peer to Peer Network)
The Pervasive.SQL V8 Workgroup is installed on all PCs. It must be installed from the Pervasive Installation CD. The PC with the PDS data is referred to as the “server” or “main computer”. Pervasive must be installed to C:\PVSW.
Pervasive Server Configuration (Peer to Peer)
1. Click Start4Programs4Pervasive.SQL V84Control Center.
2. Expand Pervasive.SQL V8 Engines and expand the appropriate PC.
3. Expand Configuration, then expand Server, and click on Communication Buffer Size
4. In the right hand frame, double-click on Communication Buffer Size, change the Current value to 65153, and click OK.
5. In the right hand frame, double-click on MKDE Communication Buffer Size, change the Current value to 65153, and click OK.
6. In the left hand frame click on Communications Protocols.
7. In the right hand frame, double-click on Supported protocols
8. In the right hand frame (Selected:) remove all items except for Microsoft TCP/IP. Left click on an item and then click the second arrow ( ................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.