About 96,700 results
Open links in new tab
  1. Error : System.IO.IOException: the network path was not found

    The fact that this exception is happening on a move next operation (see stack trace) implies that the code was reading through the list when it attempted to read an entry that was not there. …

  2. Powershell error message: Failure | The network path was not found

    Aug 22, 2024 · If F: is actually a network drive (I hope not as that's where you're restoring to), then that drive will not exist for the Service Account; mapped drives are specific to users. Use …

  3. New-PSDrive "The network path was not found" - Stack Overflow

    Nov 26, 2021 · When i try to map a New-PSDrive -Root $patch with a $path using an array, the cmd does not map the drive but give me an error : "The network Path was not found".

  4. Cannot connect to SQL Server (The Network path was not found)

    The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: …

  5. SqlException - The network path was not found - Stack Overflow

    Exception Details: System.ComponentModel.Win32Exception: The network path was not found Source Error: An unhandled exception was generated during the execution of the current web …

  6. Need help on Powershell Copy-Item from network drives

    If you run Get-ChildItem -Path "\\machine1\abc\123" does it display an entry for log 1.zip or does it display an error? Also, is log 1.zip a hidden file?

  7. Resolving SQL "The network path was not found" error

    Jun 10, 2013 · The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named …

  8. Windows Machine File Copy - DevOps task and IP address

    Jun 21, 2019 · Failed to Create PSDrive with Destination: '\\11.11.11.11\C$\TargetDirectory', ErrorMessage: 'The network path was not found' The network path was not found I also tried …

  9. Powershell remoting error - network path not found

    Jul 30, 2012 · Using the FQDN worked for me. Chris N is right: The network path was not found. This is clearly a DNS resolution error; especially if the IP address is working. I would venture …

  10. How do I fix the error 'Named Pipes Provider, error 40 - Could not …

    Mar 30, 2012 · I can't seem to connect to my database from a site. I get this error: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server I tried using the local IP …