-1

So I have several MSI packages which we use to deploy to our production environment with an in house application. But recently we started moving to SCCM. This is when the problem started, most of the MSIs tend to have handle leaks. My observations below -

  • Tried manual installation of the MSI - works fine
  • Tired using MSIEXEC with verbose logging - works fine
  • Same MSI being installed thru SCCM fails with mishandle leak errors. All these leaks tend to happen in the custom actions in *.rul files.

Note that this is not specific to a particular MSI or particular server, similar behavior is observed in several MSI packages and in several servers.

Any help would be appreciated.

Suyash Khandwe
  • 386
  • 3
  • 11
  • Did you code the custom actions or are they supplied by InstallShield? Is there any indication in the log that the custom action has crashed (a common cause of leaks)? Are you publishing to the user or the machine (because a per user install and a per system install are very different)? Perhaps post the actual log extract that shows the issue. – PhilDW May 23 '16 at 18:16
  • Custom action is written by us and it works fine outside SCCM. I can't post the logs due to my company's polices, but I can answer your questions for sure. Even the verbose logs don't say anything more. The moment custom action is hit, it leaks MSI handle. The application gets published to the machine. Appreciate your help. – Suyash Khandwe May 23 '16 at 18:21

1 Answers1

0

Usually deployments through SCCM run under the LocalSystem account, maybe that is causing the custom action to behave like this.

You can run the package with PsExec on your local machine and simulate a similar execution, to see if that is the case.

- Debugging custom actions - MSI handle leaks

Bogdan Mitrache
  • 10,536
  • 19
  • 34