Error: Failed to create working directory

[ligerzerox]

Full error: Failed to create working directory. Please check permissions on the target computer and verify your working directory path in Tools > Settings: The name cannot be found.

I’ve got a VM that I’m using test a software deployment. I tried the suggested troubleshooting from this thread (https://batchpatch.com/forum/topic/error-1605-failed-to-create-remote-working-directory) but no luck.

I added the Host using the “Add hosts from directory” option so BatchPatach can see the machine just fine. It can ping it, it can reboot the machine, and it added a file to the machine in the C:Windows directory that it was supposed it. The account being used to run BatchPatch is a domain admin account. I manually logged into the VM with the account and was able to create the folder without issue, but it’s not able to do it as part of the software install. Any help is appreciated.

[doug]

Sounds like it’s a DNS issue of some kind. I would suggest trying the FQDN instead of just the NetBIOS name. If that doesn’t work, try the IP instead of the name. It might be the case that there’s just an issue with the DNS cache on the BP computer not containing an entry for the target computer. You might be able to simply restart the DNS client service on the BP computer or restart the computer altogether. Or perhaps the issue is that there is simply no entry for the target computer on the DNS server.

[ligerzerox]

I rebooted the BP server, but the install still failed. There was a RDNS entry missing for the test target so I added one, but it still fails with the same error. If it was a DNS issue though, shouldn’t it have also failed at pinging the target machine, rebooting the taregt machine, and copying the file to the C:Windows directory on the target machine?

[doug]

I hear what you’re saying that it seems like it shouldn’t be a DNS issue if those other things work, but I’m not sure that’s definitely the case because DNS is not always used. NetBIOS might be used in some cases, for example. Nevertheless, it’s simple enough to just try the IP address instead of the name, which will answer the question right away.

Let me know how it goes.

Thanks.

[ligerzerox]

Added with the IP address instead and still no dice.

[doug]

That’s peculiar. Thanks for confirming.

I know you wrote the error in your original posting, but can you confirm that is the *exact* message? Is there no error code or HRESULT included? Is the error definitely “The name cannot be found” as opposed to “The network name cannot be found” ?

Also, what is the deployment working directory path that you have set under ‘Actions > Deployment > Target working directory’

Thanks,

Doug

[ligerzerox]

Exact verbiage from my last attempt:

“Tue-14:18:44> Deployment: Error: Failed to create remote working directory. Please check the permissions on the target computer and verify your working directory path in Tools > Settings: The network name cannot be found.”

There’s no error code or HRESULT.

Now this may be the problem as I couldn’t find clear documentation so I made an assumption; in the Deploy settings, the “Target working directory” is E:Batch Deployments. Our PCs don’t have an E: but the server does so I assumed it served as a staging area on the server.

I checked the “Remote Working Directory”, as the error said, under Tools > Settings, and that’s pointing to C:Program FilesBatchPatch.

Should the “Target working directory” also be pointing to C:Program FilesBatchPatch?

[doug]

OK, that’s the problem.

Tools > Settings > Remote working directory default config is C:Program FilesBatchPatch

Actions > Deployment > Target working directory default config is C:Program FilesBatchPatchDeployment

The ‘Target working directory’ is not staging area on the server but rather is the staging area on the target computers, so the drive must exist. This is why you’re experiencing the error.

In the meantime, we will modify the error text so that it explains to look at the ‘Actions > Deployment > Create/modify > Target working directory’ instead of ‘Tools > Settings > Remote working directory.’

Thanks,

Doug

[ligerzerox]

Okay, the tech who set this up must’ve changed it. He’s no longer with us so I assumed that was the default.

When I try to change the “Target working directory” I now see the message saying that it’s for the host; however, when I try to change it and save my deployment, it doesn’t retain the change. I changed the field to C:Program FilesBatchPatchDeployment but after I save the deployment and close the window, it changes back to E:Batch Deployments.

[doug]

Looks like that’s a bug. I’m seeing now that it only saves the field when you “Apply deployment to row” or “Execute now.” We’ll get that fixed. Glad you highlighted it.

Thanks,

Doug

[ligerzerox]

That fixed it!! I saved it, ran Execute Now, and it ran successfully. I went back to double-check and it has retained the new path. Thanks for all your help, Doug! Getting this working in Batch Patch saved me a from having to do a 10-step process that was going to take a couple hours.

[doug]

Excellent. Glad you got it working!

-Doug

[Author]

Posts