Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Features removed during SP


3 replies to this topic

Frank Kish

Frank Kish
  • Full Members
  • 2 posts

Posted 08 May 2007 - 19:55

We create a msp and when we install it removes the features. Looking in Add\Remove programs > change > modify they now all have the "not installed" red X. And the parent feature had a the disk with a yellow "1"...not sure what that means.

Any idea why this is happening or just where to start looking?

Frank

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 09 May 2007 - 12:12

Did you follow the minor update rules and restrictions?
Create a log file of the update and look for SELMGR errors.

Frank Kish

Frank Kish
  • Full Members
  • 2 posts

Posted 10 May 2007 - 01:19

"Did you follow the minor update rules and restrictions?"....well I thought we did but once we searched the log file for SELMGR it pointed us to the error "Removal of a component from a feature is not supported".

This was referring to a DLL that had been updated...not one that was being remove. But tracing things back from there we found that a merge module had been updated and was not point to the correct dll (same name, diff directory). Once we got the old merge module from source control and made sure it pointed to the correct dll the MSP we created installed correctly.

Thanks for the help, don't know if we would had figure that out without your input!

Frank

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 10 May 2007 - 16:23

I'm glad you found the problem.
A few hints for other portential causes of such problems:
You cannot remove a merge module as this would also remove the merge module's components.
And you cannot change the ComponentId GUID of an existing component (typically if you remove a file/component and re-add it a new GUID is automatically assigned to it).
Set the MSIENFORCEUPGRADECOMPONENTRULES property in your package or the EnforceUpgradeComponentRules on the target machine to make sure such problems are reported at install time (cause the update to fail with an error message) instead of silently logging them as SELMGR errors. (requires MSI 3.0 or above)