2014-01-16 11:42:58:817 1172 d2c Handler : WARNING: Command line install completed. Return code = 0x00000002
Any ideas why this install is failing via Patch Manager?
The key here is why the installer is returning an Exit Code of 0x2.
First objective would be to obtain a list of Exit Codes for Notepad++. It's a lot more fun flying with an idea of a destination. :-)
Since this occured when upgrading both 6.5.1 and 6.5.2, and I know we tested the 6.5.2->6.5.3 path (and we should have tested the 6.5.1->6.5.2 path), I do have to hesitate before considering it an issue with the package. So, for the moment, my working presumption here is that this is an environmental situation. On the other hand, since you're able to do the upgrade interactively with no issue, and it only fails when using the WUAgent, that could also be relevant.
But also, keep in mind... Patch Manager really has nothing at all to do with this event. In the end, the sequence of things goes like this:
1. Patch Manager tells the Windows Update Agent to install Notepad++ 6.5.3.
2. The Windows Update Agent launches Notepad++ 6.5.3.
3. Notepad++ 6.5.3 installer runs and either succeeds, or not. But at this point, truly, neither the WUAgent, nor WSUS, nor Patch Manager have any bearing at all on what the installer does.
What MAY be relevant is the environment in which the installer is running. A couple of notable differences between an interactive install and a WUAgent-based install:
- An interactive install is... well... interactive. It has UI. It has a user.
- A WUAgent install is silent, and does not have access to user-based resources.
One other note... the Patch Manager Notepad++ 6.5.3 package uses PackageBoot to ensure that Notepad++ is not running before the installation is launched. If PackageBoot is unable to terminate a running instance of Notepad++ on the target system, the installation of the update WILL fail.