If you have completed the steps in the configuration guide and are experiencing problems connecting to the database, please follow the troubleshooting steps below:
|Connection Error||Potential Causes||Resolution|
|Unable to complete network request to host [hostname].||
||Step 1: Click the “Ping” button.
If the result is: “Ping Failed”, then the problem is Cause #1 to the left. Verify the server name or IP Address with your server administrator, and confirm that it is accessible on the network.
Step 2: Click the “TCP/IP Test” button.
If the result is: “No connection could be made because the target machine actively refused it”, then the problem is Cause #2 to the left. Skip the remainder of this section and follow the steps listed for the error message in the next row below.
If the result is: “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [hostname:port], then the problem is Cause #3, or 4 to the left.
Use the troubleshooting steps listed below this table for the specified cause to resolve the problem.
|No connection could be made because the target machine actively refused it.||The Firebird service is not running on the server.||Start the Firebird service in Windows Control Panel –> Administrative Tools –> Services. If the Firebird service is not listed there, install the KZFirebirdServer package as described in the shared database configuration instructions.
If you have run the KZFirebirdServer installer, but the service is not displayed or will not run, an anti-virus software may have interfered with the installation. Temporarily disable any anti-virus software and install KZFirebirdServer again.
|I/O Error for file “Training Manager”
Error while trying to open file
|Your user name and password are not defined. Ask your database administrator to set up a Firebird login.||The value entered in the SYSDBA password field does not match the SYSDBA password on the Firebird server.
Note: The SYSDBA password is used by the database server. It is not the same as the application passwords that have been set up for personnel to login to the client software.
Leave the setting as the default value unless it has been changed on the server.
|If the Firebird administrator has changed the SYSDBA password for the Firebird database, request the password or have the administrator enter the password for you in the SYSDBA Password field.
If the SYSDBA password has not been changed, there may be another instance of Firebird running on the server with a different SYSDBA password. See the multi-instance configuration instructions in the user guide.
|Any other error message not listed above.||Unknown||Check each of the items listed below and then try again. If the problem continues, contact us through the Support page on our website.|
Check the Windows firewall:
The Windows firewall is a frequent cause for not being able to connect to the server. Make sure port 3050 is available for Inbound TCP connections on the server. Here are the steps:
For Windows 2003 and earlier:
Open the Windows Firewall dialog: Start –> Run –> enter “firewall.cpl”, and then click the Ok button.
Go to the Exceptions tab, and then click the Add Port button.
Enter a name such as “Firebird Database”, and then enter the port number 3050, and click Ok.
For Windows 2008 and later:
Open the Windows Firewall With Advanced Security: Start –> Search –> enter “firewall”, and select the program “Windows Firewall With Advanced Security”.
Select “Inbound Rules” in the left pane.
Click “New Rule” in the Actions pane on the right, and create a rule with the following settings:
Rule Type: Port
Specific Port: 3050
Action: Allow the connection.
Profile: As required.
Check the Firebird database process:
If you have already configured the firewall and are still unable to connect, please check to see if the Firebird database process is running on your server.
- Open the Windows Task Manager: Start –> Run –> enter “taskmgr”, and then click the Ok button.
- Go to the processes tab, and make sure the checkbox for show processes for all users is checked.
- Sort the processes by clicking on the Image Name column header and look for a process named fb_inet_server.exe.
- If the process is not there, please install the Firebird Server.
Confirm the database connection setting:
If you have configured the Firewall and the database process is running, confirm that the database connection setting on the client is correct.
- Log in to the Enterprise client, and go to Tools –> Database Connection.
- Confirm that the bottom radio button is selected for a multi-user database. If the top radio button is selected, only a single user will be able to access the database – the database will be locked and an I/O errorwill occur for subsequent connection attempts.
- Confirm that the name of the database server is entered correctly. It should be the name only, no slashes, file paths, etc. To find the name of your database server, log on to the server and then right-click “My Computer”, choose “Properties”, and then select the “Computer Name” tab.
If the problem continues, there may be an anti-virus or other security software blocking the process on the server.
Check the firebird.log file for errors:
Log in to the server, and check the firebird.log file in the Program Files \ Firebird directory for errors.
You may see an error such as the following: “INET/inet_error: select in packet_receive errno = 10038”
–> This error indicates that the Firebird server process cannot operate correctly due to network interference which may be caused by an anti-virus or other security software blocking it. Check your security software and exclude the Firebird process or temporarily disable the security to test the connection again.
inet server err: setting KEEPALIVE socket option or inet server err: setting NODELAY socket option
–> This error may indicate that you need to use the “SuperServer” version of Firebird instead of the “Classic” version. You can download the SuperServer version here.
Backup your database
To set up a nightly backup schedule, see: Schedule Database Backup