Knowledgebase Support HMRC Useful links
Knowledgebase home
Tax Return Production
Accounts Production
Client Hub
Practice Management
VAT Filer
Anti-Money Laundering
Support home
Hot Topics
SimpleStep Guides
Release Notes
Known Issues

HMRC Status
Useful Links
Accountancy Practices
and Tax Advisors
Individuals, Businesses, Trusts
and Partnerships
Client Hub
Accounts Production
Tax Return Production
VAT Filer
Company Incorporator
Companies House Forms
Companies House Integration
GDPR Centre
eSign Centre

AML Identity Checking
Limited Company

VAT Filer for Business

Database connection details not found (Cannot connect to database)

Article ID: 1246
Last updated: 05 Jul, 2018

If TaxCalc loses contact with, or has never been able to connect to a database, you will receive the following error message (The wording in the top panel may differ slightly).

This means that your additional machine cannot ‘see’ the server machine – the one on which the database is installed. You can fix this by creating a connection file, as follows.

Step 1: On the server machine

  1. On the machine on which the database is installed, click on the Windows Start button.
  2. Select All Programs and then the TaxCalc Hub folder.
  3. Click on the Discovery Response Editor program. The following window will open.

  1. Click on Create Database Connection File....
  2. Save the database connection file (ASP_DB_Connection.txt) somewhere that can be accessed from the additional machine.

Step 2: On the additional machine

Click on the drag and drop message at the bottom of the error window, and you will see the drag and drop window. Find the database connection file you created in Step 1 and drag and drop it onto the error message box (pictured below).

You should now be able to log in as usual.

Please Note; This information is only applicable to Additional machines not the one acting as the TaxCalc server. If you have issues on the Server computer itself. It is likely that the PostgreSQL service is not started. See Postgres does not always start when the "server" machine is rebooted for more information.

Firewall problems

If you still can't log in, you may be presented with the same messaging as per the first screenshot in this article.

This most likely means that there's an issue with the firewall settings on one or both machines.

To fix this, you need to open the following ports through your firewall:

  • 5433 or 5432 (PostgreSQL could be using either port depending on your configuration, If in doubt add both ports)
  • 3838
  • 6178.

Firewall test

Before opening the firewall ports, you can try temporarily disabling the firewall completely. However, this test is entirely at your discretion as disabling a firewall always carries a risk.

If the database connection can be made while the firewall is disabled, the problem is definitely with the firewall.

Re-enable the firewall and open the ports listed above correctly, using the guidance for your specific firewall. This should solve the connection problem.

If you need more help with firewalls, read the following:

Article ID: 1246
Last updated: 05 Jul, 2018
Revision: 18
Views: 16822
This article was:  

Also read
item Postgres does not always start when the "server" machine is rebooted