Executing Local File Error – "Deployment: Error: Could not find file"

[ebruddah]

I’m attempting execute a .reg file that is local on the target machine. However it says it can’t find the file. I just created a .reg job a few days ago the same exact way and it’s working fine still. Not sure how to resolve this.

******************************************************
It copies over fine and I’ve confirmed it’s there.
******************************************************

Tue-10:15:06> Copy File/Folder: Complete
Tue-10:15:06> Copy File/Folder: Copying “\\protect2019\msi\dnsfix.reg” to “\\TECH1\C$\” (Overwrite:TRUE)
Tue-10:15:06> Copy File/Folder: Initiating…
Tue-10:15:06> Copy File/Folder: Queued…

******************************************************
However when I run it, it errors out.
******************************************************

Deployment
FileToDeploy:: \\protect2019\msi\dnsfix.reg
CopyEntireFolder:: TRUE
LeaveEntireFolder:: FALSE
RetrieveConsoleOutput:: FALSE
Command:: regedit.exe /s “dnsfix.reg”
Parameters::
All Messages
Tue-10:22:07> Deployment: Error: Could not find file ‘C:\dnsfix.reg’.
Tue-10:22:07> Deployment: Copying file(s) to TECH1 …
Tue-10:22:07> Deployment: Queued file copy operation…
Tue-10:22:07> Deployment: Establishing connection…
Tue-10:22:06> Deployment: ‘DNS – Fix’ queued…

[doug]

Please follow the instructions at this link, which shows how to deploy a single .reg file:

Deploy Registry Keys to Multiple Computers Using BatchPatch

[ebruddah]

I followed those directions originally and have previously created a working .reg deployment a few days ago. But for whatever reason this new one I have created will not run. It says it can’t find the file although it’s there at the path on C:\. I can still run that .reg deployment I created but Like I’m saying the new one does not work.

[doug]

I guess I’m confused. Your original deployment works because you followed the instructions in that link to create it. But the second one does not work because you didn’t follow the instructions in that link. I can’t tell from the log you provided exactly what is going on, but I can see that there are some weirdnesses there. For example… when a deployment is performed there is no need to perform a manual separate file copy operation. The deployment itself handles the file copy. Second, the deployment looks to the deployment staging folder for the file that is being executed, but your log shows that it is looking at C:\dnsfix.reg, which is not in the deployment staging folder. I know you said the file exists at that location, but that’s not my point. My point is that what you have created is not a normal/standard/expected deployment, though I don’t fully understand exactly what you have created without being able to see the actual deployment configuration window. At this point where I’m confused is if you had a successful deployment that you created by following the instructions in the aforementioned link, why would you not follow it again to create a new deployment? Why are you trying to do something differently in the new deployment rather than following the instructions for how a .reg deployment is created in BP? It seems, based on the logs you showed, that you have somehow modified the deployment in a way that won’t work (such as, for example, modifying the actual command to execute instead of using the command to execute that BP automatically creates when you setup the deployment).

If you can provide me with a screenshot of your deployment configuration (I mean the actual window where you create the deployment in BP) I might be able to see where things aren’t setup right. This forum doesn’t allow you to upload images, so you would either have to post the image on imgur or similar and then link to it from here, or you may email us through the contact form on our website for further support.

Thanks,
Doug

[ebruddah]

Awww… Thanks I got it. The confusion was from thinking I had to copy the .reg file to the target machine using a copy job since I could not get it to run from a UNC path.

I found that the previous deployment job I created had the .reg file at the root of C:\ on my server and that’s why it was running. I copied the .reg file to the root of my server and it works now. I have now repointed all my deployment jobs to the local folder where all my .msi, .bat and other install files are and works fine now.

Thanks for helping me get that sorted out.

[doug]

Great, glad you got it figured out

-Doug

[Author]

Posts