We have a build task on our build server, which runs a script to generate MSP files via command line version of AI.
The windows service hosting the build task runs as "network service" user. Currently the build gets stuck at this step, when generating th pcp database:
msiexec.exe /a "path to.msi" /qb TARGETDIR="path to updated" REBOOT="ReallySuppress"
At this step the build as to be canceled, as it would sit there forever.
The problem is "/qb" for headless machines, as this triggers a progress dialog.
My question: Is there a way to change this call to use "/qn" instead?
We use AI 11.0 enterprise.
Suggested Articles
Re: MSP can't be built on headless server
Hello,
I'm not sure why this happens. The "/qb" (basic UI) switch should be silent enough so it doesn't generate a service error. Please give us some time to investigate deeper this scenario and we'll get back to you as soon as we have an conclusive answer.
Thank you for your patience and understanding.
All the best,
Daniel
I'm not sure why this happens. The "/qb" (basic UI) switch should be silent enough so it doesn't generate a service error. Please give us some time to investigate deeper this scenario and we'll get back to you as soon as we have an conclusive answer.
Thank you for your patience and understanding.
All the best,
Daniel
Re: MSP can't be built on headless server
In the meantime we found out, that this is an issue with user rights, not with headless machines or windows service restrictions.
When we ran the msiexec command in a cmd which was started using "runas Network Service" (how to do this) we got this error message:
"The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance."
Running the command with /qn didn't succeed, either.
The real problem is, the Network Service user is not allowed to do installations. We changed the user which runs the windows service and were able to run the build successfully.
It's not necessary to do further investigations.
When we ran the msiexec command in a cmd which was started using "runas Network Service" (how to do this) we got this error message:
"The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance."
Running the command with /qn didn't succeed, either.
The real problem is, the Network Service user is not allowed to do installations. We changed the user which runs the windows service and were able to run the build successfully.
It's not necessary to do further investigations.