Fix 0x80070035 Error on a Windows PC
By Russell Winters
What is Error 0x80070035?
Error 0x80070035 or "Network path not found" error occurs whenever a user tries to open
a company file on a Windows Vista workstation. Since Microsoft has ended offering support for
Windows XP, users operating on this OS may experience the error while accessing a company file
from a Windows XP host machine. Whenever, the device is unable to find the location of a particular
file that a user wishes to open, he may get the following message:
"Error 0x80070035: Unable to open company file, network path not found."
What are the Causes of the Error?
One of the possible causes of the error is a network configuration issue. Users may also
confront the error if the Link-Layer Topology Discovery (LLTD) Responder component isn't installed
in the Windows Vista workstation⁄server.
What are the Possible Solutions to Fix Error 0x80070035?
Solution 1: Ensure QBCF Monitor Service is Running
Firstly, you will need to ensure while fixing the "Network path not found" error is to
confirm that the QBCF Monitor service is running on both Windows workstations.
Follow the tips to confirm the same:
1. Click "Start" button and go to Search field
2. Type "Services.msc" and press Enter
3. Right-click on "QBCFMonitor Services" option and click "Properties"
4. Select the "Automatic" in the "Startup Type" from the drop-down menu and
click the "Start" button
5. Click "OK" to bring the changes into effect.
Solution 2: Check for Network Configuration Problems
If you've confirmed that the QBCF Monitor service is running on both the systems, you
will need to check your network configuration to resolve the error. Browse to the installing
and configuring QuickBooks for a multi-user section or simply check the network environment
to verify that everything has been setup correctly.
Solution 3: Install Link-Layer Topology Discovery (LLTD) Responder component
If nothing helps, visit Microsoft's official website and look for the Link-Layer Topology
Discovery (LLTD) file. Since you must have tried all the possible ways to fix the error, installing
the Link-Layer Topology Discovery (LLTD) is the only thing you can do now to remove the error
from your device.
Follow these tips to install the solution from Microsoft's official website:
1. Visit Microsoft's official website and proceed towards the Microsoft Download Center
2. Download the Link Layer Topology Discovery (LLTD) Responder package
3. Scan the file for security purposes and then run the file on your system to fix the issue
4. You must restart your device after applying the package to ensure that the problem gets fixed.
You can also use the hotfix package to install the LLTD Responder component on Windows
XP-based computers. Undoubtedly, you may need to take help from an online computer support
firm if you're unable to fix your PC problems by following the tips mentioned above. To prevent
serious damages, ensure that you conduct regular PC maintenance sessions and install the latest
updates from Microsoft's website. Sometimes, the tech solutions provided by technicians aren't
capable of fixing the issue so take your device to the nearest computer service centre to get it fixed.
Russell Winters is an ardent technician associated with
Qresolve online computer support
with wide experience of fixing issues with PCs, laptops, tablets and smartphone. With a strong
track record of devising effective ways of
online tech support and system security,
she has so far helped thousands of users across the globe.
More Windows Troubleshooting Articles:
• Troubleshoot Windows 7 with Problem Steps Recorder
• Is Your Laptop Overheating? - 12 Tips To Prevent Overheating
• How to Fix Aclui Errors
• First Stop When Troubleshooting Windows 7 - Control Panel
• Free Tool to Recover Files From Damaged Disc
• Video - How to Use Memtest86+ to Test Your PC's Memory Subsystem
• Wireless Router Problems and Solutions
• How to Troubleshoot, Dissemble, and Repair a Laptop Display
• PC Technician's Guide to EMI (Electromagnetic Interference)
• How to Fix Sqmapi.dll Error