How to Fix “Could Not Get the Name of the Current QuickBooks Company Data File” Error in Webgility Desktop
This article helps Webgility Desktop users solve error "Post to QuickBooks failed due to Could not get the name of the current QuickBooks Company data file." that occur when Webgility Desktop loses connection with QuickBooks Desktop. Common causes include change in company file name, outdated or invalid QuickBooks connection certificates, or permission issues restricting access to the company file.
Cause of the issue:
This error typically occurs when Webgility loses connection with QuickBooks Desktop, preventing it from retrieving the company data file name. Possible causes include a temporary disconnection between Webgility and QuickBooks, an outdated or invalid QuickBooks certificate, or permission-related issues that restrict access to the company file.
To resolve the error "Post to QuickBooks failed due to Could not get the name of the current QuickBooks Company data file," follow these steps:
1. Verify QuickBooks Connection
At times, QuickBooks may disconnect for various reasons, requiring verification of the connection between Webgility and QuickBooks Desktop.
Please refer to the following article:
Verify QuickBooks Desktop Connection & Company File
2. Regenerate the QuickBooks certificate
If Webgility is unable to connect to QuickBooks, we may need to re-authorize the connection by removing the existing certificate first and then regenerating it with a new connection.
Please refer to the following article:
Regenerate QuickBooks Certificate