51364 Pervasive Control Center (PCC) may not display menu items or nodes pertaining to DataExchange or Backup Agent after installation of DataExchange or Backup Agent
Workaround: Start PCC by running the following command, which clears a memory cache used by PCC: pcc –clean.
If you want to clean the cache without starting PCC, for example, from your custom install, run the following command: pcc -application com.pervasive.core.RCPNullApplication -clean -nosplash
51403 Fetches with variable length bookmarks in SQLFetchScroll() not working correctly
51779 The Pervasive System Analyzer (PSA) registry key remains after uninstall completes
51981 Line number and ruler options have no effect in Pervasive Control Center (PCC) text editor
52229 Canceling a client install removes PSCORE.DLL or PSCL.DLL from Windows system32 folder
52267 In DDF Builder, cannot add a new column to existing tables using the Create button
52268 In DDF Builder, changes made in SQL Definition editor are retained after closing the editor without saving changes
52447 On SuSE Linux, installation of Pervasive PSQL puts the daemon startup and shutdown scripts in wrong location
52834 DDF Builder does not return an error when creating a table structure for a Btrieve file with overlapping keys
52905 Repair option from Add/Remove Programs does not work for a Workgroup installation repair
Workaround: Uninstall the Workgroup product then reinstall it.
52953 Installation does not request a reboot if a locked files is placed in the Easy Updates folder
52973 After a Linux uninstall, the Pervasive PSQL startup and shutdown scripts are not removed
53087 License Administrator applies a temporary license if an invalid license key is entered twice
53135 Silent install reads ptksetup.ini only from where the install is invoked
Workaround: To have a silent install read an edited ptksetup.ini, copy the install to a writeable location, edit the ptksetup.ini file, and then invoke the silent install
53208 Pervasive Control Center (PCC) may return "Unknown error -19" when you view table properties.
One source of this error is if the SQL indexes created do not match the underlying indexes in the Btrieve file.
53220 After uninstalling Pervasive PSQL and Pervasive System Analyzer on Windows, some documentation files remain under Program Files\Common File\Pervasive Software Shared\Doc
Workaround: Delete the remaining files manually from the operating system
53233 Pervasive System Analyzer (PSA) network test fails when Pervasive V8.1 (or prior versions) is upgraded to Pervasive PSQL v9 SP2 then V8.1 restored from the archive
Workaround: Use the PSA provided with its version of Pervasive PSQL to diagnose network connectivity. For example, use the PSA provided with Pervasive PSQL v9 SP2 to test connectivity for Pervasive PSQL v9 SP2 and the PSA provided with V8.1 to test connectivity for Pervasive.SQL V8.1.
53243 The uninstall program fails to identify some utilities that are open, such as Maintenance, Function Executor and Rebuild, but still performs the uninstall
53376 On Linux, uninstall of Pervasive PSQL Server leaves symbolic links in /usr/local/psql/lib
53407 In Pervasive System Analyzer, “supported protocols” links from the troubleshooting suggestions fails to open the appropriate help page
53507 Pervasive Control Center (PCC) exits with error code 1 after opening files through the File --> Open menus (the File dialog)
This problem can occur if more than one Java Runtime Environment (JRE) is installed on the same machine. This problem may also occur when adding an external tool to PCC.
Workaround1: Specify a JRE version equal to or greater than JRE 1.5.0 when you start PCC. For example, the following command specifies JRE 1.5.0 and involves an instance of Java without a console window:
The -vm parameter is required if you specify the JRE. The full path to javaw.exe must be enclosed by double quotes if the path contains spaces.
Workaround2: If you use a version of the configuration management software CM Synergy prior to 6.4, you may also experience this problem if you right-click in the File dialog. The workaround is to unregister CMExplorer.dll, which allows you to perform check-in, check-outs, and so forth fom the Windows File Explorer. Once unregistered, perform your CM Syngery check-ins, check-outs, and so from from the CM Synergy GUI rather than from File Explorer.
53603 You cannot install the Pervasive PSQL client using Group Policy's Software Installation
53684 An SQL query with nested scalar functions (such as STUFF, REPLACE, REPLICATE, POSITION) in the SELECT list may cause a general protection fault
Workaround: Contact Pervasive Support for field test fix (FTF)
53698 Btrieve status code 26 (“the number of keys specified is invalid”) may result if a UNION view contains more than 59 nullable columns in the SELECT list with FORWARD-ONLY cursor
The database engine only allows 119 key segments on a file so a UNION query is likely to run into this limit if a SELECT list contains more than 119 not nullable columns or 59 nullable columns because the database engine is trying to generate a temporary file that has segment indexes on all columns.
Workaround: Contact Pervasive Support for field test fix (FTF)
53759 CREATE TABLE IN DICTIONARY always creates a table in legacy mode (not supporting TRUE NULLs) even when SET TRUENULLCREATE = ON
Workaround: Contact Pervasive Support for field test fix (FTF)
53801 Window 98 and ME cannot connect through the relational interface with the SPX protocol
53802 SQL query may return error “Filter comparisons are limited to 256 bytes for LONG character data” if leading segment column is STRING data type and IN list is empty
Example: Column c1 is the leading segment column. SELECT * FROM
WHERE c1 IN (“)
Workaround: Contact Pervasive Support for field test fix (FTF)
53803 Increase in number of index segments for the Pervasive PSQL v9 SP2 (9.5) file format is available only for the transactional interface (number of segments remains 119 for SQL access)
53815 Scalar functions NOW() and NEWID() cannot be used in default value assignments with CREATE TABLE or ALTER TABLE
Workaround: Create or alter the table without a default value then execute an UPDATE statement to set the column value to NOW() or NEWID().
