Troubleshooting Common PSQL Issues
This section outlines problems you may encounter during the installation or when first using the Workgroup product.
I receive Status 7224 or my license is no longer listed in the License Administrator utility.
When the PSQL Workgroup is installed as an application, you may experience this situation. Applications do not automatically inherit the user’s administrative rights. You can stop the engine, run it as administrator, and then run the command line license administrator or GUI License Administrator as administrator to authorize the license. Another alternative is to install Workgroup Engine to run as a service. See Running the Workgroup Engine as a Service.
I fail to see the effects of my configuration changes.
Try stopping and then restarting the database engine. Whenever you make a change to engine configuration components, you must stop and restart the database engine for the changes to take effect. For information on how to start and stop the database engine, see Verifying Database Engine is Running.
Why do I receive Status 7012 when trying to create a new database with the Workgroup Engine using PCC on Windows?
When PCC creates a new database, the new database name is added to dbnames.cfg and an entry is added to the ODBC.INI registry in order to create a corresponding System DSN.
Due to Microsoft operating system constraints on registry access, the Workgroup Engine should be run in an elevated mode, so that the database System DSN can be created.
Once the System DSN is created successfully, any user may start the Workgroup Engine and use the DSN.
*Note: In Windows, standard users may create User DSNs without this restriction.
Why do I (now) receive Status 95, after running my application successfully?
Your application has lost its session with the database engine. This can happen if you make changes to your configuration settings and must restart the database engine, as in the troubleshooting example given above. At the moment the database engine is stopped, any application that is running loses its session with the database engine. You must stop all those utilities and restart them in order to reestablish communication.
See the Status Codes and Messages manual for more cases in which this status code can be returned.
Installing a PSQL application has rendered another application unusable.
If the latest DLLs have been overwritten, it is possible to restore the overwritten DLLs using a backup directory that is automatically created when you install PSQL.
How do I verify that my DOS components are functioning properly?
PSQL provides a DOS version of BUTIL.EXE for purposes of verifying that your DOS components are functioning properly. This file is installed in the PSQL\BIN folder of the PSQL Program Files default installation directory.
Why can’t I restart my application after an improper program exit?
Database engine components may remain in memory if the engine is interrupted improperly.
►
If you cannot restart your program after improperly aborting the application by using Ctrl-C or stopping the process:
1
Shut down and restart your system.
2
Avoid terminating applications in an abnormal manner.
Why isn’t my application using the Workgroup engine?
If you previously installed PSQL requesters and later installed the PSQL v12 Workgroup engine but your application is only using the requesters, you may have an outdated configuration that sets Local Access to Off. The PSQL v12 Workgroup engine’s installation does not overwrite existing settings. To reset Local Access to On, see Using the Server and Workgroup Engines Concurrently.
How Do I Access the PSQL Online Manuals?
►
To access the online documentation:
1
Access Control Center & Documentation from the operating system Start menu or Apps screen.
2
Click the desired manual on the PCC Welcome page. (If the Welcome page has been closed, click Help then Welcome.)
I received an error message during installation that begins: “Setup did not update the PATH statement in autoexec.bat because the new path would be too long for Windows.”
This message appears when the installation program cannot update the PATH environment variable because the resulting PATH definition would be too long (exceeds the environment space). For information on how to increase the environment space defined in config.sys, refer to Microsoft knowledge base articles.
If you get this error message, then a REM statement (a comment) has been added to your autoexec.bat file. The REM statement contains the PATH value that would have been entered. You can change the PATH statement manually.
The best approach, if possible, is to install the product at a location with a shorter installation directory so that the value of PATH does not exceed the environment space.