BatchPatch Forums Home › Forums › BatchPatch Support Forum › Deploying exe file fails but runs ok manually
- This topic has 4 replies, 2 voices, and was last updated 10 years, 6 months ago by doug.
-
AuthorPosts
-
April 28, 2015 at 5:34 pm #9059nhsitdeptParticipant
I’m trying to deploy Office 365 Pro Plus.
Batchpatch keeps giving an error of deployment code 123
Deployment
“setup.exe /configure c:BatchPatchtemplocalonly64.xml”
All Messages
Tue-13:26:10> Deployment: Exit Code: 123
Tue-13:26:10> Deployment: Executing \JesseTestWin7 -s -w “C:BatchPatchtemp” “C:BatchPatchtempsetup.exe /configure c:BatchPatchtemplocalonly64.xml”
I can run this command in a cmd prompt on the machine and everything works fine.
April 28, 2015 at 6:03 pm #10761dougModeratornhsitdept – It’s not clear to me exactly how you came to this… in particular what looks odd to me is the quotation marks in your command. It should be something more like:
Tue-13:26:10> Deployment: Executing \JesseTestWin7 -s -w “C:BatchPatchtemp” “C:BatchPatchtempsetup.exe” /configure localonly64.xml
Please try to match your deployment to the screenshot below (obviously you might have a different installer path and a different target working directory, but the rest should be the same). Your ‘localonly64.xml’ file should be placed in the same folder as the setup.exe, which should prevent the need from specifying the entire local path to it, though I don’t think that specifying the full path is where the problem occurred. And you should make sure to check the box that says “copy entire directory contents…”
When you then execute the deployment it should have the quotation marks set the way that they are in what I pasted above, not how they are in what you pasted in your posting. Let me know how it goes.
April 28, 2015 at 6:07 pm #10765dougModeratorIf you continue to have problems, please send us an email and we’ll troubleshoot that way instead of in the forum.
-Doug
April 28, 2015 at 8:02 pm #10757nhsitdeptParticipantThanks, this did the trick. I didn’t think to put the quotes around setup.exe
Thanks!
April 28, 2015 at 8:14 pm #10759dougModeratorBatchPatch automatically provides the proper quotation marks, so the “command to execute” need not be manually edited by you at all. When you create the deployment as specified in the screenshot, the “command to execute” is automatically populated as you see in the screenshot. I did *not* manually edit it, nor should you.
Thanks,
Doug
-
AuthorPosts
- You must be logged in to reply to this topic.
