Technical Support 1600 N. Lorraine

Transcription

1 Technical Support 1600 N. Lorraine Hutchinson, KS PDS Cortex/Pervasive Version 9 Configuration and Troubleshooting Revised 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. Table of Contents Supported Operating Systems 2 PDS Configuration 3 Pervasive Configuration 4 Pervasive.SQL V9 Workgroup (Peer to Peer Network) 5 Pervasive Server Configuration (Peer to Peer) 5 Pervasive Workstation Configuration (Peer to Peer) 7 Pervasive.SQL V9 Server (Client-Server Network) 8 Pervasive Server Configuration (Client Server) 8 Pervasive Workstation Configuration (Client Server) 9 Pervasive System Analyzer 10 Testing Pervasive 10 Uninstalling Pervasive 10 Common Errors 12 94: The application encountered a permission error : The maximum number of user count licenses has been reached 13 -Page 1 PDS & Pervasive Configuration and Troubleshooting -

2 Supported Operating Systems Server Operating Systems supported by PDS Cortex are Windows 2000 Server and Windows 2003 Server. Any previous Windows Operating Systems are not supported. Windows Small Business Server is NOT supported. Workstation Operating Systems supported by PDS Cortex are Windows 2000 Professional (SP3 or higher) and Windows XP Professional. All other versions of Windows are NOT supported. PDS Cortex does NOT support any Windows 64bit Operating System. PDS only supports 64bit processors when a Windows 32bit operating system is installed. See s.pdf for specific requirements. -Page 2 PDS & Pervasive Configuration and Troubleshooting -

3 PDS Cortex Configuration PDS Cortex must NOT be installed on the server, or main computer, off of the root drive. The PDS Cortex folder, TTG has to be under another folder (usually the APPS folder) on the server and the folder must be shared, 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 with C:\APPS shared. The network must be in good working condition. You should be able to ping the Server by name from any workstation. Pervasive must be able to resolve the Server name to its IP address. Using an external source for Name Resolution (such as DSL) may cause problems. The Server should have a static (non-changing) IP address. Any network errors in Windows event viewer on the server or any workstation could cause problems running PDS. Windows 2000 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 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 Cortex install (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 Cortex launches many components that may be blocked by firewall and other security software. For this reason PDS recommends turning off any firewall software. PDS has found that some antivirus software does include a built in firewall and will cause problems running PDS Cortex. Other security software such as script blocking should also be turned off. If PDS Cortex will not start turn off all firewall, antivirus, and security software. PDS Cortex and Pervasive should always be installed via Add\Remove Programs on any server running Terminal Services. Otherwise it will not run properly. -Page 3 PDS & Pervasive Configuration and Troubleshooting -

4 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 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 V9 requires Java Runtime 5.0, version which is included on the installation CD. Other versions of Java may not be compatible with Pervasive. Special Note: When upgrading from Pervasive.SQL 2000 or 2000i (version 7), Pervasive must be uninstalled on the server and every workstation. After Pervasive is uninstalled the Pervasive Cleanup Utility must be run on the server and every workstation. -Page 4 PDS & Pervasive Configuration and Troubleshooting -

5 Pervasive.SQL V9 Workgroup (Peer to Peer Network) The Pervasive.SQL V9 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 on the server as well as each workstation. Notes on the Workgroup Engine The Pervasive Workgroup Engine must be running at all times on the server (main computer). The Workgroup Engine starts as a program so a user will need to be logged in to the server for the Workgroup Engine to start. Make sure that the Pervasive.SQL Workgroup Engine is NOT running on any workstations, it should only be running on the main computer ( server ). o Pervasive.SQL Workgroup Engine should NOT be in the Startup folder on a workstation. (Start/Programs/Startup). o If the Workgroup Engine is in Startup folder it should be deleted. Also check the Windows Sys Tray (by the clock in the lower right). If there is a PC with a green + then right click on it and select Stop Engine and Exit. o The Pervasive.SQL Workgroup Engine should be running at all times on the main computer. It should be in the Startup folder. The Server must be up and running and a user logged in for the Engine to be started. -Page 5 PDS & Pervasive Configuration and Troubleshooting -

6 Pervasive Server Configuration (Peer to Peer) Any settings not listed should be left at the defaults o Go to Start > All Programs > Pervasive > Pervasive.SQL > Pervasive.SQL 9 Control Center Select Configure Microkernel Router and review the following settings: Access o Use Local Microkernel Engine should be checked o Use Remote Microkernel Engine should NOT be checked Communications Protocols o Only TCP/IP should be checked Performance Tuning o Use Cache Engine should NOT be checked Click OK to save any changes Select Configure Local Engine and review the following settings: Access o Accept Remote Request should be checked o Allow Cache Engine Connections should NOT be checked Communications Protocols o Only TCP/IP should be checked Compatibility o Create file version should be 9.0 Memory Usage o System Cache should NOT be checked Performance Tuning o Limit Segment Size to 2GB should NOT be checked o Cache Allocation default should reflect 20% of physical installed memory-up to 32MB. This can be changed to reserve more RAM for Pervasive. Pervasive automatically converts the number to 16KB increments. o Max Microkernel Memory Usage should be set to 60% Click OK to save any changes The workstation engine must be restarted for any changes to take effect. -Page 6 PDS & Pervasive Configuration and Troubleshooting -

7 Pervasive Workstation Configuration (Peer to Peer) Any settings not listed should be left at the defaults o Go to Start > All Programs > Pervasive > Pervasive.SQL > Pervasive.SQL 9 Control Center Select Configure Microkernel Router and review the following settings: Access o Use Local Microkernel Engine should NOT be checked o Use Remote Microkernel Engine should be checked Communications Protocols o Only TCP/IP should be checked Performance Tuning o Use Cache Engine should NOT be checked Click OK to save any changes Local Engine settings do not need to be set on the Client. -Page 7 PDS & Pervasive Configuration and Troubleshooting -

8 Pervasive.SQL V9 Server (Client-Server Network) The Pervasive.SQL V9 Server is installed on the server (Windows 2000 or 2003 Server) Pervasive must be installed to C:\PVSW on the server and this folder needs to be shared, Everyone Full Control in order to test the Pervasive Client. The Pervasive Client is installed on all workstations to C:\PVSW. Pervasive Server Configuration (Client Server) Any settings not listed should be left at the defaults Go to Start > All Programs > Pervasive > Pervasive.SQL > Pervasive.SQL 9 Control Center Select Configure Microkernel Router and review the following settings: Access o Use Local Microkernel Engine should NOT be checked o Use Remote Microkernel Engine should be checked Communications Protocols o Only TCP/IP should be checked Performance Tuning o Use Cache Engine should NOT be checked Select Configure Local Engine and review the following settings: Access o Accept Remote Request should be checked o Allow Cache Engine Connections should NOT be checked Communications Protocols o Only TCP/IP should be checked Compatibility o Create file version should be 9.0 Memory Usage o System Cache should NOT be checked Performance Tuning o Limit Segment Size to 2GB should NOT be checked o Cache Allocation default should reflect 20% of physical installed memory. This can be changed to reserve more RAM for Pervasive. Pervasive automatically converts the number to 16KB increments. o Max Microkernel Memory Usage should be set to 60% Click OK to save any changes The Server Engine must be restarted for any changes to take effect. -Page 8 PDS & Pervasive Configuration and Troubleshooting -

9 Pervasive Workstation Configuration (Client Server) Any settings not listed should be left at the defaults o Go to Start > All Programs > Pervasive > Pervasive.SQL > Pervasive.SQL 9 Control Center Select Configure Microkernel Router and review the following settings: Access o Use Local Microkernel Engine should NOT be checked o Use Remote Microkernel Engine should be checked Communications Protocols o Only TCP/IP should be checked Performance Tuning o Use Cache Engine should NOT be checked Click OK to save any changes Local Engine settings do not need to set on the Client. -Page 9 PDS & Pervasive Configuration and Troubleshooting -

10 Pervasive System Analyzer The Pervasive System Analyzer (PSA) is a utility that can test connectivity between the Pervasive client on a workstation and the Pervasive Engine on the server. It can also be used to uninstall and cleanup Pervasive. Testing Pervasive 1. Go to Start>Programs>Pervasive System Analyzer 2. Click Next on the Welcome screen 3. For Action select Test Active Installation 4. Remove the check from Test Relational Engine 5. The Log File path should be ok 6. Click Next 7. Click the Browse Button ( ) under Target machine and select the server. (Entire Network Microsoft Windows Networks Domain Server) 8. The first test will be the Network Communication test. You should get a screen that indicate: Successfully connected to server via TCP/IP protocol, and Successfully transmitted 75 test messages via TCP/IP protocol during stress test. Any errors or problems will be displayed if any of the tests fail. 9. If the Network Communications test does not complete successfully then PDS will not run on this workstation. 10. If the Network Communications test fails, click back. Enter the IP Address of the server for the Target machine. Click Next to run the tests again. If the Network Communications test passes with the IP Address but not the server name then Name Resolution is not working properly. 11. The next test will be the Transactional Engine test. For the samples directory to test browse to the \\servername\pvsw\samples folder and click ok. 12. Click Next 13. You should see checkmarks next to all 6 tests. Any Xs indicate a failure and should give additional information. 14. Click Next. 15. To view detailed results click View Log File. 16. Click Finish to exit the PSA. Uninstalling Pervasive 1. Go to Start>Programs>Pervasive System Analyzer 2. Click Next on the Welcome screen. 3. For Action select Delete Components or Archives and click Next 4. Select Local Machine and click Next. 5. Select Delete Pervasive SQL components and registry settings to delete the current installation of Pervasive. -Page 10 PDS & Pervasive Configuration and Troubleshooting -

11 6. Select Delete Pervasive archives to delete previous Pervasive installations that have been archived. (Both items may be selected) 7. Click Next. 8. There will be prompt to confirm the deletion-click Yes. 9. Click Finish to exit the PSA. -Page 11 PDS & Pervasive Configuration and Troubleshooting -

12 Common Errors Pervasive s documentation, included as part of the installation often gives good information on specific error messages. Go to Start>All Programs>Pervasive.SQL 9>Documentation>Pervaisve.SQL 9 to open the help document. Also the Pervasive log is located at Start>All Programs>Pervasive.SQL 9 Documentation>PVSW.log. This file is a log of Pervasive errors and messages that have occurred on that workstation\server. This can be helpful in troubleshooting errors. 116: The file is owned by another Microkernel engine acting as a Gateway 3012: Local engine is not accessible to the MicroKernel router 3013: The remote engine is inaccessible to the MicroKernel router because the networking component is not loaded 3014: The MicroKernel router cannot find an engine 3105: No available transport protocol for the Pervasive Network Services Layer 3111: Failure during send to the target server These errors indicate that the Pervasive Client is unable to access the Pervasive Engine. Check and make sure Pervasive is running on the server. Verify that the mapped network drive is accessible. Make sure you can ping the server by name from the workstation. Check the Pervasive Client Configuration. Check Windows Event Viewer on the workstation and the server, any type of network errors could indicate a network problem that keeps PDS from loading or causes intermittent problems in PDS. The Pervasive Client is unable to access the Pervasive Engine, usually because of a Networking problem between the workstation and the server. Make sure you can ping the server by name from the workstation. 1. Right click on the PDS short cut on the desktop and click on Properties. 2. The Start In path should be the Mapped Drive (such as P) \TTG. (Example: P:\TTG). 3. Close the Properties box. 4. Double Click on My Computer. 5. There should be a P: drive listed. It should show up as Apps on Server (P:). 6. If there is no drive letter matching the drive in the Start In path in the PDS Properties than that drive needs to be mapped. 7. If the drive letter is there double click on it. If you receive an error such as Network Drive Not Accessible then there is a problem with the network connection between the server and the workstation. Try rebooting the workstation. 8. If you still get the same error then try checking the Pervasive Client Configuration. -Page 12 PDS & Pervasive Configuration and Troubleshooting -

13 94: The application encountered a permission error Check the permissions on the Share on the server. It should be Everyone Full Control. Also the security on the folder should be Everyone Full Control. 161: The maximum number of user count licenses has been reached 1. Check and make sure there are available Pervasive Licenses. 2. On the Server go to Start>Programs>Pervasive.SQL>Other Utilities\Monitor. 3. Click on MicroKernel and then Resource Usage 4. Check Licenses in Use. The Maximum value is the total number of Licenses allowed on this server. The Current value shows how many users are currently accessing Pervasive. If these numbers match then there are no more licenses available until a user closes PDS. To check licenses on the Pervasive server: 1. Go to Start>Programs>Pervasive.SQL>Other Utilities>License Administrator 2. The License Administrator utility will list the version, type of license, and the user count. Temporary licenses will have an expiration date. 3. One license is required for each concurrent connection, each workstation running PDS requires a Pervasive License -Page 13 PDS & Pervasive Configuration and Troubleshooting -