Pervasive.SQL V8 (V8.6) Service Pack 2 (SP2) Release - July 2004 README.TXT Contents ------------------------------------------------------------------------ This document contains the following topics: * General Information * New Features * Installation Notes * Environments Supported * Documentation Notes * Known Issues * Technical Support * Useful Links * Disclaimer ------------------------------------------------------------------------ General Information Welcome to the Pervasive.SQL V8.6 Service Pack 2 (SP2) Release. If you have previously installed one of the pre-releases of SP2, you must completely remove it from your system prior to installing this final release of SP2. Run Uninstall to remove the pre-release of SP2 from your system, then use the cleanup option in the Pervasive Systems Analyzer to ensure that all registry entries pertaining to the pre-release are removed. This release delivers fixes to all known critical issues in Pervasive.SQL V8. It can be applied over any Pervasive.SQL product. This includes, but is not limited to, the following Pervasive products: Pervasive.SQL 2000i SP4 (v7.94) Pervasive.SQL V8 (initial shipping version V8.0) Pervasive.SQL V8 SP1 (8.10) Pervasive.SQL V8 Security (8.50) Or it can be installed on a machine with no previous Pervasive products installed. User count keys from any previous V8 product apply automatically to SP2. However, if you are running Pervasive.SQL 2000i or earlier, you must purchase an upgrade key from Pervasive sales. This release has separate installations for NetWare Servers, Windows Servers, Linux Servers, and Windows Workgroup Engine. To update your client installations, install the server first. Then install the client at each remote computer by mapping a drive to the server and running setup.exe from the server directory C:\pvsw\clients (or the "clients" directory of your chosen installation location). IMPORTANT FOR USERS OF V8.10 AND EARLIER The Pervasive Security release (v8.50) included major new features and enhancements. These features are included in this service pack. These features have been explained in detail in the What's New document version 8.50. If you are upgrading from an earlier version of Pervasive.SQL other than 8.50, you should read the What's New document in detail before installing. ------------------------------------------------------------------------ New Features This section describes the new features offered in the SP2 release. * A new configuration option has been added. The option can be used by old Btrieve applications that do not want Pervasive.SQL to verify that the key length passed to the client requester is big enough to hold the key. This will prevent a status 21 from being returned. Be aware that if you choose to use this option there is no checking by the Pervasive requester to prevent a potential memory overwrite. The new option can be found in Pervasive Control Center Configuration under Client --> Application Characteristics --> Verify Key Length. * After applying SP2 to a Server installation, the setting for Max MicroKernel Memory Usage will be lowered to 60% if it is above that value. The setting is not lowered if you have previously manually set it to a value below 60%. In that case, the setting retains its current value. The original default value is 90%. You can view this setting in the Pervasive Control Center Configuration under Server --> Performance Tuning --> Max MicroKernel Memory Usage. The reason for this forced change is because you can experience system hangs if the MicroKernel reaches 90% usage and certain other events occur simultaneously on your system. This hang is more likely to occur if you are using SQL to access your data, if you have heavy usage of the Pervasive Monitor utility, or if you are running DataExchange or AuditMaster. To update your Database Engines, you must reboot and restart your server after applying SP2. * A user or administrator cannot change the Btrieve security policy from Database or Mixed if relational security is enabled on the target database. The error "Attempt to modify database flags was rejected" displays if a change is attempted. You can, however, change the policy from Classic to Database or to Mixed even if relational database security is enabled. To change the security policy, an administrator must log in to the target database as the Master user, disable relational security, and then change the Btrieve security policy. Additionally, once relational security is enabled and the Btrieve security policy is set to Database or to Mixed, you cannot delete the Database Name. The error "Error occurred during dropping database" displays if a deletion is attempted with the Drop Database utility. Even though the error occurs, the Drop Database utility does delete the DSN. (The DSN is deleted but not the Database Name.) Use ODBC Administrator if you need to re-create the DSN. Please see What's New in Pervasive.SQL V8.5 for a description of all features in V8 that were new for V8.5, as well as documentation for the use of these features. What's New in Pervasive.SQL V8 is included in your product installation in HTML Help (.CHM) format. Note: Because this is a service pack without extensive new features, the documentation remains as it was for Pervasive.SQL V8.50. All references to 8.50 in the documentation also apply to 8.60. ------------------------------------------------------------------------ Installation Notes After reading these notes, see Getting Started with Pervasive.SQL for installation procedures. Windows Please note the following environmental issues when installing to Windows: * You must have Administrator rights to install this product. * When installing the Client to Windows XP/2000/NT 4, you must reboot after the client install for Win 16-bit access to Btrieve. * If you receive an error during your install concerning the inability to update a component names OLEDB32R.DLL do not be alarmed. This is a Windows component and the error will not impact your ability to run Pervasive.SQL SP2. * You may receive an error during your install on an older version of Windows saying that the installer cannot find isutldll.dll and/or instlic.dll. If you get this error, the only workaround is to reboot and start your install over. It should succeed the second time. * On some older OSs such as Windows NT, the Pervasive System Analyzer may launch even though the system asks you to reboot after the install. Do not run PSA until after you have rebooted. Otherwise, you may receive errors about "invalid entry points" and similar failures. * Windows 95 is not supported. You must have at least Windows 98 SE to install Pervasive.SQL V8.60. * If you are installing a downloaded version of Pervasive.SQL, do not place the setup files in a location that is listed in the PATH environment variables, because this can cause issues with file copying during install. Place the setup files in a location such as the Windows TEMP directory. * You cannot install Pervasive.SQL from a terminal server session. You must be on the console of the server to install. * You need Internet Explorer 4.01 SP2 or later in order to install the product because of a requirement from Windows Installer. You also need Internet Explorer to view the online documentation, and use the Network troubleshooting features of PSA. To determine if your Internet Explorer version is adequate, select Help | About Internet Explorer from a browser window and ensure that the version displayed is 4.72.3612.1713 or higher. * When installing to Windows 98 SE, you may encounter an issue if the PATH environment variable is too long, because the Pervasive.SQL installation program may be unable to modify the PATH to add the Pervasive BIN directory. If you encounter issues after installing to Windows 98 SE even if install reports success, check your PATH statement. If necessary, manually add C:\PVSW\BIN to your PATH. By default, Pervasive.SQL installs to c:\pvsw\bin. If you installed to a drive other than C:, or to a directory other than PVSW, revise the path statement with the path information appropriate for your installation. * A local security policy in Windows XP Professional "Sharing and security model for local accounts" can adversely affect network logins. Under the default policy, all network logins to local accounts are authenticated as Guest, no matter what credentials were supplied. This causes your authorization for databases using Mixed or Database mode not to match your OS credentials and can prevent data access you intended to authorize. To resolve this condition, ensure that your policy for "Sharing and security model for local accounts" is set to Classic, which authenticates users as themselves. Windows 2003 already has a default setting of Classic. Windows XP Professional has a default setting of Guest, and Windows 2000 and earlier releases do not have this security policy. To find this policy in Windows XP, browse to Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options. Note: Windows 2000 Service Pack 4 (SP4) is required for Windows 2000 installations. SP4 is required to run any of the Pervasive.SQL database products—Server Engine, Workgroup Engine, or Client—on Windows 2000. NetWare Please note the following environmental issues when installing to NetWare: * When trying to install the Pervasive.SQL client on Windows 2000 by running the client installation program located on a NetWare file server, you may encounter the following error: "The system can't open the device or file specified." This problem is a known issue in Microsoft Client for NetWare as described on the Microsoft web site: http://support.microsoft.com/default.aspx?scid=kb;en-us;838439 To resolve the issue, follow the instructions provided by Microsoft or install the client from an installation program located on a non-NetWare hard drive volume. * NetWare 6.0 includes Pervasive.SQL 2000i SP4. However, NetWare 6.0 configures Pervasive.SQL 2000i with very minimal resources. These settings in some cases are much lower than the recommended default settings from Pervasive. We highly recommend that you review all of the settings and adjust them based on the expected usage of your applications. In particular, you should reset the MicroKernel cache size to at least 20% of your total physical memory. If you do not change this setting then you can experience NetWare CPU hog time-out errors. * The NetWare install creates shortcuts that link to utilities on the mapped NetWare drive. Running these utilities from the NetWare shortcut can potentially causes a conflict in the pscore component depending on the Pervasive components on the local machine. If you receive such a conflict message using the License Administrator, run the utility locally and connect to the remote engine. * Running the NetWare install from a Windows 2000 (SP4) machine can produce warning messages from Windows such as "Error 1321. The Installer has insufficient privileges to modify the file." Despite the warnings, Install should complete normally. If it does not, install your NetWare server from a machine running an earlier service pack of Windows 2000. * Running the NetWare install from a Windows 2003 machine can produce Windows security warning messages that reference files install is trying to copy. If you receive such dialogs starting with "Some files can harm your computer.", click Open and Install will complete normally. ------------------------------------------------------------------------ Environments Supported This section lists the platforms and environments on which Pervasive.SQL V8.60 has been tested. Server Engine The Pervasive.SQL V8.60 Server was tested on the following: * Windows 2003 Server/Advanced Server with Hotfix KB 823980 * Windows 2000 Corporate SP4 * Windows 2000 Advanced SP4 * Windows 2000 Professional SP4 * Windows NT 4 Server SP6a or higher * Windows NT 4 Workstation SP6a or higher * NetWare 6.5 SP2 * NetWare 6 SP3 * NetWare 5.1 SP6e * NetWare 4.2 SP9 with Unicode support * Microsoft Terminal Server and Citrix MetaFrame 1.8/XP * Linux deployments with a Kernel version 2.4 or higher, Glibc 2.2 or higher, and the PAM libraries. Workgroup Engine The Pervasive.SQL V8.60 Workgroup was tested on the following: * Windows 2003 Server/Advanced Server with Hotfix KB 823980 * Windows XP Professional * Windows XP Home Edition * Windows 2000 Corporate SP4 * Windows 2000 Advanced SP4 * Windows 2000 Professional SP4 * Windows NT 4 Server SP6a or higher * Windows NT 4 Workstation SP6a or higher * Windows ME * Windows 98 SE Tool for Running Workgroup Engine as a Windows Service A tool that installs the Workgroup engine as a service is available on the Pervasive Component Zone web site. The tool is unsupported and available only on an as-is basis. To download the tool, visit the following URL and select the "Toolbox - WGE as an NT Service." link. http://www.pervasive.com/ComponentZone/Component/Lookup.asp?Function=ShowComponents&ID=6&Category=Tools+%2F+Utilities After downloading the file: 1. Place the tool in the BIN directory where your Pervasive files are installed. 2. Shut down your Workgroup engine. 3. Double-click PVSW.EXE to run the tool. 4. From the menu, choose Tools | WGE as a Service. The next screen provides the option to install the Workgroup engine as a service. Before you do so, click Info and follow the instructions provided. Clients The Pervasive.SQL V8.60 client was tested on the following: * Microsoft Client for Windows, 32-bit (Windows 98 SE, ME, NT, 2000, and XP) * Microsoft DOS 6.22 * Microsoft Client for NetWare * NetWare Client for Windows NT (4.9, 4.83 SP1) * NetWare Client for Windows 9X (3.40, 3.32 SP1) * Linux deployments with the following characteristics: o Kernel version 2.4 or higher o Glibc 2.2 or higher o PAM libraries (if PAM is selected for security) ------------------------------------------------------------------------ Documentation Notes This section provides information regarding the documentation included with the Pervasive.SQL V8.60 product. Because this is a service pack without extensive new features, the documentation remains as it was for Pervasive.SQL V8.50. All references to 8.50 in the documentation also apply to 8.60. HTML Help and Internet Explorer This release includes support for Microsoft HTML Help (files with .CHM extension). HTML Help uses components of the Internet Explorer (IE) engine to display help files. A defect in the early versions of IE 5 (and some 5.5 versions) causes display irregularities with modular HTML Help systems. These display conditions may be seen in PVSWDOCS.CHM, the master help file for Pervasive.SQL V8.60 that dynamically loads the other help files. Since this defect affects only the file merging mechanism, you will see no display irregularities when loading individual help files. Some specific symptoms you may encounter are: * The Contents/Index/Search/Favorites pane at the left side of the help window does not display correctly or is slow to repaint when you select a different tab such as Index or Search. * The body pane on the right side of the help window does not display correctly or at all. * The splash screen displayed when first loading the help window does not clear until you click on it. If you encounter any of these display conditions, the solution is to upgrade to IE 5.01 or higher. You may download version 5.01 or higher from Microsoft's web site. You can determine your version by clicking Help | About Internet Explorer from the browser window. If your Internet Explorer version is one of the following, or a later version, then your HTML Help should function correctly. IE Version Description 5.00.2919.6307 Internet Explorer 5.01 5.00.3105.0106 Internet Explorer 5.01 with Service Pack 1 6.00.2800.1106 Internet Explorer 6.00 with Service Pack 1 Windows XP Professional and XP Home includes IE 6.0. Windows 2000 and Windows ME shipped with IE 5.01 so you should not see the display irregularities on those platforms, nor with older IE 4 versions. Contact Pervasive Technical Publications If you have additional questions or comments about documentation, please feel free to post your remarks on DevTalk at the following URL: http://www.pervasive.com/devtalk ------------------------------------------------------------------------ Known Issues So that we can update known issue reports periodically between releases, all Known Issues are published in the Knowledge Base on the Pervasive web site, rather than in this static document. In the Knowledge Base, perform a search in the Knowledge Base on "Known Issues in Pervasive.SQL V8" to get a list of known issues. Click the link below to visit the Knowledge Base: http://support.pervasive.com/eSupport/ ------------------------------------------------------------------------ Technical Support You may obtain technical support from the following Web-based support options: o Pervasive Knowledge Base at http://support.pervasive.com/eSupport o To open a support incident, http://www.pervasive.com/support/index.asp. Click on Open or Check Status of a Support Incident. To report a product defect, see http://www.pervasive.com/support/index.asp and click on Report a product defect. If you require something other than what Web-based support options provide, contact Pervasive Support by phone: o 800-287-4383 option 3 (the Americas) o +800.1212.3434 (Austria, Belgium, Denmark, France, Germany, Italy, Luxembourg, The Netherlands, Spain, Sweden, Switzerland, and the U.K.) o +32.0.23.37.61 (Any other European, Middle Eastern, African or Asian countries, excluding Japan) For technical support and discussions about Pervasive products in general: o Visit the DevTalk forum at http://www.pervasive.com/devtalk. o Visit http://www.pervasive.com/company/contact/index.asp for other contact information. For information on updates and Service Packs: o Visit the updates page at http://www.pervasive.com/support/updates ------------------------------------------------------------------------ Useful Links * For a comprehensive list and details of Pervasive Products, see http://www.pervasive.com/offerings * Discuss all your Pervasive development issues at: http://www.pervasive.com/devtalk * Review information about application development at: http://www.pervasive.com/developerzone * For Technical Papers, see: http://www.pervasive.com/support/techpapers.asp * For Product Manual downloads, see: http://www.pervasive.com/support/technical/online_manuals.asp * For viewing Product Manuals online, see: http://www.pervasive.com/library * For information on our Support programs, see http://www.pervasive.com/support/support_programs.asp * For information on updates and Service Packs, see: http://www.pervasive.com/support/updates ------------------------------------------------------------------------ Disclaimer This application uses the free iODBC Driver Manager as written by Ke Jin , enhanced with local modifications from Pervasive for the NetWare platform. Pervasive will donate their code changes to the current maintainer of the iODBC Driver Manager project, in accordance with the LGPL license agreement of this project. The iODBC Driver Manager home page is located at: http://www.iodbc.org For further information on this project, contact its current maintainer: Patrick van Kleef . PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS. Copyright © 2004 Pervasive Software Inc. All Rights Reserved. ------------------------------------------------------------------------ *** END OF README.TXT ***