When the next process kicked off, we received a "Network Path Not Found" warning.
Ideally this issue occurs when you cannot access the network resources. Any of several different and unrelated technical problems on a network generate this error but mainly it is caused due to Antivirus or Firewall blocking the resources or when the Windows Defender Firewall block system resources. However, the causes may be many, thus we would try to troubleshoot the issue sequentially.
Approach 1: Check if the drive or files which you are using are shared or not. (On File server)
- Right click the drive on the targeted computer that you are to visit and choose Properties. We are using the C drive on a virtual machine as an example.
- Navigate to Sharing tab. If you see that the network path here says Not Shared, then click Advanced Sharing… tab.
- Tick the box for Share this folder and then please make sure the the Share name is correct. Then click Apply and OK to save the change and exit.
- Then press Windows key and R at the same time to open the run command. Type the name of the folder in the search box and hit Enter. You should be able to access to this folder correctly now.
# Approach 2:- Ping IP address of target machine/server (file server) from machine where robot is installed
- It might be possible that while the file/folder is shared correctly, the network channel isn’t connected right. We could test it by pinging the IP address of the target computer from the primary computer.
- Press Win + R to open the Run window on the target computer and type the command cmd and hit Enter to open the Command Prompt window.
Type the command ipconfig/all and hit Enter. It would populate a bunch of information.
- Note the value of the IPv4 address.
- Now, open Command Prompt on the primary computer.
- Type ping and press Enter.
Check if you get 4 confirmation replies or not.
If not, you could try running the Network Adapter troubleshooter. Go to Start > Settings > Updates and Security > Troubleshoot and select the Network Adapter Troubleshooter. Restart the system after running the same.
# Approach 3:- Check if there has been any changes in the Network Security policies on machine/server where robot is installed
- If the above two methods did not help, then you should check whether the problem was on your network connection.
- Hit Start button, then type in the search box secpol.msc and hit Enter.
- Then follow the path: Local Policies > Security Options > Network security: LAN Manager authentication level. Double click the option Network security: LAN Manager authentication level.
# Approach 4:- Reboot all devices.
- You may find value in rebooting all affected devices or the shared devices.
- The host and client computers and the network router.
- It's possible that cached data in one of the links of the networking chain prevents the network transaction from successfully completing.
# Approach 5:- Reset TCP/IP on machine/server where robot is installed
- Opening a Windows command prompt and entering "netsh" commands. For example, the command.
- netsh int ip reset
- Resets TCP/IP on Windows 8 and Windows 8.1. Rebooting the operating system after issuing this command returns Windows to a clean state.
- A misconfigured or misbehaving software firewall running on the initiating Windows device may interfere with local file sharing.
- Temporarily disabling firewalls, either the built-in Windows Firewall or vendor-supplied firewall software will help you figure out if a firewall's preventing your network from sharing properly.