Error Messages from PCC
You may receive several different messages when attempting to create or connect to databases in PCC. This section explains the likely causes for some of the most common error messages:
•
Can’t retrieve database names. You don’t have access rights for the operation
•
Unable to connect to the specified remote server. Verify that all of the communication components are loaded on the remote server and that there are available sessions and try again
•
An error was encountered while connecting to the server
•
Unknown configuration properties
Can’t retrieve database names. You don’t have access rights for the operation
This error may occur when you are attempting to create a new database on the server. The most likely cause is that you are logged in as an operating system user that has neither administrative rights in the server operating system, nor membership in the Pervasive_Admin group on the server. Another likely cause is that you forgot to enter a user name and password.
Solution: Be sure to enter a user name and password for the remote operating system. You must have administrative rights on the server or be a member of the Pervasive_Admin group in order to create a new database on the server. Granting Administrative Rights for the Database Engine explains how to set up the Pervasive_Admin group.
For Windows 32-bit platforms, be sure that you are set up as a local user on the system, not a network user. Network users have a domain name and a back slash preceding the user name, such as BOSTON\GILBERT. Be sure that the user who is a member of the Administrators group or Pervasive_Admin group is a local user.
If you have checked permissions and your user login does in fact meet one of the criteria above, then you should also check to make sure that you are logged into the correct network. You can verify whether you are logged into the correct network by attempting to read or write to a server that you are certain uses the target operating system.
Unable to connect to the specified remote server. Verify that all of the communication components are loaded on the remote server and that there are available sessions and try again
You may receive this error when attempting to register a new remote server in PCC. There are several reasons you may receive this error:
1
You mis-typed the server name. The database client tried to connect to a server that does not exist.
Solution: Double-check the name of the server, and make sure you can see it in your Network Neighborhood, spelled exactly how you entered it.
If you know the server exists but you can’t see it in your Network Neighborhood, make sure that you are logged into the correct network. Ask your network administrator for help.
2
The server user count has expired. If you have been using a temporary license, you will get this message for connection attempts after the license has expired.
Solution: Run License Administrator to check the status of licenses installed on the server. In the window that appears, you can see detailed status information on each license that has been applied to your server. If your license has expired, purchase a permanent license from your reseller or from Actian Corporation.
3
There are no available sessions on the server. If you have a heavy load of users on the server, or if you have configured the server with a small number of sessions, you may receive this error.
Solution: Run Monitor to check the usage of sessions available on the server. Check MicroKernel Communication Statistics. For Total Remote Sessions, if the Peak value and the Maximum value are the same, then it is likely that you have run out of sessions.
4
The remote database server is not running.
Solution: Make sure that the remote database engine is running, or ask your network administrator to do so.
5
The remote database server is not accepting client requests.
Solution: Set the properties to ensure that the remote database engine is configured to accept remote requests. You must have administrative permission on the server (or membership in the Pervasive_Admin group) in order to do so. In PCC, right-click on the server name in PSQL Explorer, then click Properties. Click Access and ensure that the Accept Remote Request option is selected.
An error was encountered while connecting to the server
The most likely cause of this error is using the wrong operating system user name or password in an attempt to connect to the server.
Other possible causes include:
•
The operating system may be expecting the user to change his/her password on the first logon. This situation occurs if, in the User Manager, you have selected the User Must Change Password at Next Logon checkbox.
•
If the user is a member of another group with lesser permissions, the lesser permissions will override the greater permissions. A user always has the most restrictive permissions of any group to which the user belongs.
Solution: Double-check the spelling of the user name and the password. Make sure the user and password have been set up on the remote server operating system.
Inspect the user’s account information on the server. Make sure the operating system is not expecting the user’s password to be changed at the next logon. Make sure the user is not also a member of a group that has restricted permissions.
For Windows 32-bit platforms, be sure that the user is set up as a local user on the system, not a network user. Network users have a domain name and a back slash preceding the user name, such as BOSTON\GILBERT. Be sure that the user who is a member of the Administrators group or Pervasive_Admin group is a local user.
Unknown configuration properties
It is possible, but unlikely, that PCC may retrieve configuration properties from the database engine that are invalid. Please contact PSQL Customer Support to report such error conditions.