Error 1800: Failed to creat remote working directory.

BatchPatch Forums Home Forums BatchPatch Support Forum Error 1800: Failed to creat remote working directory.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #9287
    houghton
    Participant

    Here is the scoop, I have BatchPatch on two separate computers and they are both offline. I retrieved the wsusscn2.cab file correctly and placed the file on cpu#1 and am now attempting to Actions>Windows update>Retrieve consolidated url list of available updates from cpu#2. I am able to ping cpu#2 from cpu#1 so the connection is there. I am logged into both cpu’s with the same credentials. When I go to complete this process this is the log that comes back;

    Windows Update Messages

    Error 1800: Failed to create remote working directory. Please check permissions on the target computer and verify your working directory path in Tools > Settings. HRESULT -2147024843: The network path was not found.

    – 11:00:42

    Local Agent Log

    ::Begin download – 2016-11-09 11:00:16

    Microsoft Offline Scan File

    1> wsusscn2.cab :: File already exists in cache

    ::End download – 2016-11-09 11:00:16

    Files located in cache: 1

    Files downloaded: 0

    Failures: 0

    ::Begin file copy operation – 2016-11-09 11:00:16

    Error 1800: Failed to create remote working directory.

    ::End file copy operation – 2016-11-09 11:00:42

    All Messages

    Wed-11:00:42> Windows Update: END (Offline mode: Check for available updates and generate consolidated url list)

    Wed-11:00:42> Windows Update: Error 1800: Failed to create remote working directory. Please check permissions on the target computer and verify your working directory path in Tools > Settings. HRESULT -2147024843: The network path was not found.

    Wed-11:00:16> Windows Update: Initializing copy of WsusScn2.cab file from local cache to target working directory…

    Wed-11:00:16> Windows Update: Local download complete (Files located in cache: 1. Files downloaded: 0. Failures: 0)

    Wed-11:00:16> Windows Update: Executing WsusScn2.cab downloader…

    Wed-11:00:16> Windows Update: Queued WsusScn2.cab downloader…

    Wed-11:00:16> Windows Update: BEGIN (Offline mode: Check for available updates and generate consolidated url list)

    Wed-11:00:16> Windows Update: Queued…

    The Remote Working Directory location in cpu#1 says “C:/Program Files/BatchPatch” and that location didn’t exist on cpu#2 at first. I did add the location and this had no effect.

    I don’t know if this matters but both cpus do have a copy of BP, could they be interfering with one another? I do not have BP running when I am attempting to complete this process on cpu#2, but I don’t know I am guessing here.

    Any thoughts?

    #11432
    doug
    Moderator

    Your issue boils down to:

    HRESULT -2147024843: The network path was not found.

    This is the same as:

    0x80070035 The network path was not found

    This is a Windows issue, not a BatchPatch issue.

    1. Make sure target computer firewall is configured properly: Using BatchPatch with Windows Firewall

    2. Make sure no other software such as HIPS is blocking.

    3. Make sure you are using correct computer name and that you can resolve fileshares on the target computer using that same name… so ‘start > run > \targetComputeradmin$ must be accessible, and so must \targetComputerC$Program FilesBatchPatch’

    4. Google search 0x80070035 The network path was not found for more solutions… e.g. https://social.technet.microsoft.com/Forums/office/en-US/028a3d13-f571-49e0-abe7-1ca61fb92082/error-code-0x80070035-the-network-path-was-not-found?forum=w7itpronetworking

    #11434
    houghton
    Participant

    Thank you Doug. I did notice a that the firewall was on cpu#2 and not on on cpu#1. I am going to try what is listed in you first item on the list. For now I turned off the firewalls on both cpus and the process is running.

    Thank you for your time and attention sir.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.