Look at the "Note" regarding 2720. That is telling you that an API attempting to set a source directory failed. The OS returned error 2 to that API internally. 2 = "The system cannot find the file specified.".
Are you running this MSI from a share? Are drives mapped differently for different users on the box? There are several hits on the internet for 1625 errors, some seem to relate to installed KB stuff. -----Original Message----- From: tob...@gmx.net [mailto:tob...@gmx.net] Sent: Monday, August 16, 2010 12:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] MSI Error 1625 reasons? Hello, this is more an MSI than WiX related issue but I have seen many general MSI question with good answers, so I try this also. I have an msi installation that exits with error 1625, but only on a small number of machines. The same installation file works well on all others. Here is the relevant log file part (sorry for the german, it was a german OS where we have the problem): MSI (s) (48:8C) [11:15:01:985]: Note: 1: 2343 MSI (s) (48:8C) [11:15:01:985]: Entering CMsiConfigurationManager::SetLastUsedSource. MSI (s) (48:8C) [11:15:01:985]: Note: 1: 2720 2: 2 MSI (s) (48:8C) [11:15:02:032]: Note: 1: 1729 MSI (s) (48:8C) [11:15:02:032]: Product: MyProduct -- Configuration failed. MSI (s) (48:8C) [11:15:02:032]: Das Produkt wurde durch Windows Installer neu konfiguriert. Produktname: MyProduct. Produktversion: 1.3.2.5. Produktsprache: 1033. Erfolg- bzw. Fehlerstatus der neuen Konfiguration: 1625. MSI (s) (48:8C) [11:15:02:032]: MainEngineThread is returning 1625 MSI (s) (48:68) [11:15:02:048]: No System Restore sequence number for this installation. Systemrichtlinien verhindern diese Installation. Wenden Sie sich an den Systemadministrator. So the error message is pointing to system policy, but so far we found no cause of the error. We allready searched a lot, and even compared the "local security settings" with a machine were there is no error, but could not find any hint what change or "setting" causes this error. It is also strange that reinstalling the os on a machine that has this error "fixed" the problem. May be someone on the list had similar problems and found a solution for this or could give a pointer to the root cause of this error? Best regards, Tobias -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
