So I'm having a problem installing an EXE that's an MSI wrapper that requires a configuration file. One key point is on the prior step I'm generating the configuration file via a PowerShell script as per the applications guidelines as the configuration will vary from server to server. Here's the process as I'm running it:
- Create foo.xml with a configuration for the server via ps script and put it in C:\Foo on the local server, this step works as expected.
- With the installer step use the setup line of $(Repository)\FooSoft\132\setup.exe /s /v"/L*V c:\Foo\foo_verb.txt /qr REBOOTPROMPT=REALLYSUPPRESS REBOOT=REALLYSUPPRESS UNATTEND=1 ADMINCONFIGFILE=\"C:\Foo\foo.xml"" as outlined in the applications install document
- The install completes, but not fully as the configuration file wasn't used/found based on the foo_verb.txt verbose log created during install
I have ensured on step 2 above that the "Includes Entire Directory" check box was checked as there are multiple additional files needed, which does copy the files over (as I don't get a missing file error).
In an attempt to fix this I copied my package and replaced the install step with a copy step to copy all the install files to the server, and added a command step run a batch file on the server with the setup.exe line above in it. This also did not work
Also to ensure the command is correct I manually copied over the files to one server, ran the script to create the config file and then ran the setup line via a command prompt and everything worked correctly.
What I'd like to know is why is the setup not seeing my configuration file? Do I need to put it somewhere else?
Please sign in to leave a comment.