Help with MSI 1636
Answers (1)
Got this error when deploying an msp to another package I made to 300+ Blade computers. The error did not appeared during QA (tested 4~8 times on my own) nor during UAT (got 6 different UAT testers applying the patch before rolling it out). Out of the 300+, 94 blades presented the error. Running it again some of the failed ones didn't help, only solution was to re-run the original msi (which uninstalls itself then reinstalls) and then apply the patch. Both the patch and the msi were done in Wise, and both had a wrapper handling the command line and external logging. The patch only replaced a dll in %INSTALLDIR%, and was built by removing the dll and its component, then creating an entry into removefilestable to remove the old dll, then adding the new dll with a component built into a new feature marked as required. Not sure what went wrong, tomorrow will take a look to some of those equips.
so that the conversation will remain readable.