How to avoid that error 1704 causes issues when running an wrapper that installs multiple msis
When running a setup.exe installer (which runs a numer of msi's in the background of SQL Server Management Studio) I ran into an error 1704. I finished the current user repair of this product and I could then run the installation wrapper.
How can I avoid that this error causes issues when this package goes to production.
A reboot before and after the installation ?
Are there any other options ?
How can I avoid that this error causes issues when this package goes to production.
A reboot before and after the installation ?
Are there any other options ?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
AngelD
12 years ago
Does the previous MSI require a reboot before continueing with the rest of the MSIs?
(check a verbose log)
Does the below registry key exist after your get the error?
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\InProgress
(check a verbose log)
Does the below registry key exist after your get the error?
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\InProgress
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
