How can I fix QuickBooks Cannot Communicate with the Company File error

QuickBooks Cannot Communicate with the Company File [SOLVED]

Company file errors have been on rise in recent times in QuickBooks Desktop. One such error major issues is when QuickBooks Cannot Communicate with the Company file. This technical problem can be attributed to different factors, of which the most common issue is Windows firewall issue. Other factors include issues with QB database server manager,  DNS configuration issues, restricted permissions, including other factors. This blog shall list all the causes, and shall explain the methods to fix QuickBooks Cannot communicate with Company file error

Main factors that contribute to QuickBooks Cannot Communicate with Company File Error

The primary causes of this Company file error are:

  • Windows Firewall related issues.
  • QuickBooks database server manager is facing technical errors and the service related to this program is not running properly.
  • DNS settings are not configured properly.
  • QuickBooks Desktop is not updated.
  • Restricted permissions to share the Company file folder.

Solutions to fix QuickBooks Cannot Communicate with Company File Error

Users should perform the below given solutions to effectively resolve this issue. 

Solution 1: Making Firewall Configurations

Firewall configurations include the following steps:

  • Click on Start menu and then search for Windows Firewall.
  • Therein, go to Advanced Settings.
  • Right-click on Inbound Rules.
  • After that, click on New Rule.
  • Hit on Port, and then click on Next.
  • Select TCP and provide the correct ports corresponding to the QuickBooks version.
  • After that, click on Next.
  • Allow the connection and following that click on Next.
  • Select all the profiles and then hit on Next.
  • Go for the creation of a rule and then type in a name.
  • Hit on Finish.

Solution 2: Update QuickBooks 

Updating QuickBooks can go a long way in fixing different types of technical issues in QuickBooks. The steps are:

  • Launch QuickBooks first and then go to Help.
  • After that, click on Update QuickBooks.
  • Then, mark Reset Updates box and click on Get Updates.
  • Finally, click on Update Now.
  • Now, run QuickBooks and check if the Company file connection error is still existing.

Solution 3: Verify QBDBMgrN.exe Process

  • The first step is to open the Task Manager.
  • There, click on QBDBMgrN.exe in Processes.
  • If it is not available, then allow admin rights for the service “QBDataServiceUser”. The procedure is:
  • Close QuickBooks and all the background programs.
  • Open the Control Panel.
  • Then go for User Accounts and click on Manage another account.
  • Double-click QBDataServiceUser.
  • Hit on Change Account Type.
  • Choose the Administrator option and change the account type. 
  • Now, run QuickBooks. The error should be sorted out.

Solution 4: Run QuickBooks Doctor File tool

QB File Doctor is a useful tool in QuickBooks Tool Hub. It can be used for fixing diversified Company file issues including the issue when QuickBooks cannot communicate with the Company file. The steps are:

  • Set up QuickBooks Tool Hub at first. Make sure to download it from Intuit website.
  • Now, run the Tool hub.
  • Click on Company File Issues and then run QuickBooks File Doctor Tool.
  • Browse for the Company file and choose it.
  • Then hit Next.

Solution 5: Run the QuickBooks Database Server Manager

  • Run QB Tool Hub and then click on Network Issues.
  • Click on QuickBooks Database Server Manager.
  • Install the tool and run it. Browse for the company file folder and select it.
  • Click on Start Scan.
  • The process may take a while. Wait for it to get fixed.


This blog demonstrated all the workable solutions to help you fix QuickBooks cannot communicate with the company file error. If you are still facing the issue, or need any other technical help, straightaway call our QuickBooks experts at the helpline +1800-615-2347.

Leave a Reply

Your email address will not be published. Required fields are marked *