Error codes
If any problems should arise, against our expectations, and an error prompt is displayed, it contains an error code. By means of the list below the error codes can help you with the solution of the problem. If a problem occurs regularly, or if you can not solve the problem on your own, please contact the support and name the accordant error code for the diagnosis of the problem.
Error code: 4
Error: "Error at opening the database."
Proposals for solution:
- Check if the databases are configured properly.
- Try to connect the database again.
Error code: 5
Error: "The database is not opened."
Proposals for solution:
- Check if the databases are configured properly.
- Try to connect the database again.
Error code: 6
Error: "The database could not be opened. Check the database path and the password."
Proposals for solution:
- Check the database path and the password.
- Check if the databases are configured properly.
- Try to connect the database again.
Error code: 10
Error: "Error at connecting with the server database."
Proposals for solution:
- Make sure that the server is started.
- Make sure that the database configured at the client is started at the server
Error code: 11
Error: "Error at open/execute."
Proposals for solution:
- Please contact the support
Error code: 12
Error: "No database has been found."
Proposals for solution:
- Check via the Windows Explorer if the database actually exists.
- If the database lies on a network share, make sure that there can be built up a connection with the share.
- Have you got write privileges for the database?
Error code: 13
Error: "Wrong database password."
Proposals for solution:
- Check if the caps lock key is active.
- Make sure that the right password is used. The database password is required, the user password does not work here.
Error code: 14
Error: "KeyFile could not be opened."
Proposals for solution:
- Check via the Windows Explorer if the KeyFile *.pedkey actually exists.
- If the keyfile lies on a network share, make sure that there can be built up a connection with the share.
- Have you got write privileges for the keyfile?
Error code: 15
Error: "Error at opening the database (SQL engine)."
Proposals for solution:
- Please contact the support
Error code: 16
Error: "Wrong password for the network protocol."
Proposals for solution:
- Check if the Caps Lock key is active.
- Make sure that the right password is used. The connection password which is required here is given away at the server installation.
Error code: 17
Error: "The database server does not react."
Proposals for solution:
- Make sure that the server is started.
- Check the settings of the Password Safe firewall
- Are the server ports as well as the service port activated in the network firewall?
- Check your network configuration
Error code: 20
Error: "Execute could not be carried out in the time given."
Proposals for solution:
- Please contact the support
Error code 21:
Error: "The multiuser network file could not be started."
Proposals for solution:
- Check if you have got right privileges on the folder in which the database is.
- If the database folder lies on a network share, make sure that the share is accessible.
Error code: 22
Error: "The multiuser network file can not be opened."
Proposals for solution:
- Check if the file *.ps6n is in the database folder and if you have got right privileges for it.
- If the database folder lies on a network share, make sure that the share is accessible.
Error code: 23
Error: "Access to this database has been denied."
Proposals for solution:
- Check the settings of the Password Safe firewall
Error code: 24
Error: "The maximum number of sessions has been achieved. Connection with the database not possible."
Proposals for solution:
- Wait until another session has been closed.
- Purchase further licenses.
Error code: 25
Error: "The database is already opened and can therefore not be opened again."
Proposals for solution:
- A single user database has been opened by another user and has to be closed by that user first.
Error code: 26
Error: "Error at open/execute."
Proposals for solution:
- This message is sent at a hacking suspicion. Therefore check imperatively if anybody wants to gain access to your data.
- Check the log files of the server.