Hello,
We encounter with error when install Enterpise Library 3.1 - May 2007 for Visual Studio 2008 on Windows Vista SP1 machine.
Error 2769: Custom Action Install5f8cd7ca_0f3c_4ded_8129_e98e6402b46c did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: Install5f8cd7ca_0f3c_4ded_8129_e98e6402b46c, 1,
Verbose log below.
Thank you for any help.
With best regards,
Anton Spitsyn
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.
Error 2769
Started by
AntonS
, Dec 18 2008 15:49
4 replies to this topic
Posted 18 December 2008 - 16:23
Windows Installer reference explains 2769:
The InstallExecuteSequence may have been authored incorrectly. Actions that change the system must be sequenced between the InstallInitialize and InstallFinalize actions. Perform package validation and check for ICE77.
Seems very abstract.
I don't believe that perform package validation for helps in this case
The InstallExecuteSequence may have been authored incorrectly. Actions that change the system must be sequenced between the InstallInitialize and InstallFinalize actions. Perform package validation and check for ICE77.
Seems very abstract.
I don't believe that perform package validation for helps in this case
Posted 18 December 2008 - 17:08
Any time I've encountered this error it's been due to an issue with the Directory table. Either incorrectly resolved directory names, missing backslashes (if properties are used by the CA) and so on.
Validating the package will, in all probability, highlight the exact cause or, at the very least, the directory/property at issue.
Validating the package will, in all probability, highlight the exact cause or, at the very least, the directory/property at issue.
- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.
Posted 04 May 2009 - 22:09
i hav face this problem.but didnt get any solutions.i hav tried lots off things...now i hav a freash copy of windows now its ok..
[signature removed by Administrator]
Posted 13 May 2009 - 04:01
As VBScab has mentioned, this could be a Directory table problem. The Directory table is resolved at runtime so its possible one of the windows defined folders (i.e. programfiles) was set to something windows installer could not resolve. Running with verbose logging might have pointed to a few clues.