- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Configuration file error
I am helping a friend with a QuickBooks problem. This error comes up randomly when she is doing random things in the program.
//This is a QuickBooks configuration file It exists while users are connected.//
Do not delete the file yourself QuickBooks may not // open correctly if you manually delete this file
Full screenshot of error attached
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
Let’s go through some troubleshooting steps to get past the configuration file error message to allow QuickBooks Desktop to access a company file in a network or multi-user environment, Cjmartel1976.
We appreciate you providing us with a screenshot of the error message for us to better address the issue. The QuickBooks configuration file described is the Network Data (.ND) file. This file is crucial for QuickBooks Desktop to function in a multi-user or network environment. The warning you quoted—"Do not delete this file yourself. QuickBooks may not open correctly if you manually delete this file,” is due to its vital role in network connectivity.
To resolve issues with .ND files, follow the steps below:
- Search for *.ND in the computer containing the company files.
Note: If .ND files don't exist; open a QuickBooks company file on the computer where the file resides to create it. - Delete or rename the files (.NDOLD).
- Use the Database Server Manager to rescan the folders. This will create new files.
If the same thing happens, we can run the QuickBooks Tool Hub to fix this QuickBooks Desktop error. Just follow the steps and details in this article: Fix common problems and errors with the QuickBooks Desktop Tool Hub.
Revisit this post if you have more questions about accessing company files in a network or QuickBooks-related concerns.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Other questions
Open the company file, create a backup file and restore it with a new name. Did you encounter the same problem?