Menu
▾
▴
wix-users
|
From: Gareth at S. <gm...@se...> - 2007-04-24 10:37:00
|
Hi guys, I have an issue with a package I've built which has a number of merge modules, including that for MDAC2.8. This has some properties set on the client side of the installation that need to be passed to the server side in order for it to install when needed. It is not needed on Vista, of course. The problem is that when I repair the package, some ways of doing so give a UAC prompt and the installation log correctly passes these properties across and everything works. But some methods or repairing do not give a UAC prompt and the merge module gives it's error dialog (trying to install on an unsupported OS) and rolls back the install. Examples of when it works: - Click 'Repair' at the top of the Programs & Features dialog in Vista. Examples of when it doesn't work: - Right-click the program in Programs & Featurs dialog and 'Repair' from context menu. - Double-click the original MSI and select 'Repair' in the UI Sequence. So, how can I insist that the install gets elevated and give the UAC prompt in order to work in all methods of repairing the install? Many thanks, Gareth -- View this message in context: http://www.nabble.com/UAC-Prompt-Required-tf3637831.html#a10158386 Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Bob A. <wi...@bo...> - 2007-04-25 04:49:48
|
Gareth at Serif wrote: > So, how can I insist that the install gets elevated and give the UAC prompt > in order to work in all methods of repairing the install? > Make sure the InstallPrivileges attribute isn't set to 'limited' (i.e., make sure it's 'elevated'). Remember that the UI is never elevated on Vista (with UAC turned on). -- sig://boB http://bobs.org |
|
From: Gareth at S. <gm...@se...> - 2007-04-25 16:50:12
|
The InstallPrivileges attribute is indeed set to "elevated". I never actually figured out what behioural differences there were on the strength of this attribute though... -- View this message in context: http://www.nabble.com/UAC-Prompt-Required-tf3637831.html#a10184850 Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Bob A. <wi...@bo...> - 2007-04-26 03:27:52
|
Gareth at Serif wrote: > The InstallPrivileges attribute is indeed set to "elevated". I never > actually figured out what behioural differences there were on the strength > of this attribute though... > MSI should elevate as soon as it starts the execute sequence. As always, a verbose log is essential in diagnosing odd behavior. Search for "Grabbed execution mutex" to find when MSI starts. -- sig://boB http://bobs.org |
|
From: Gareth at S. <gm...@se...> - 2007-04-26 11:01:48
|
Thanks for your advice. I have done some detailed comparisons between the log of the successful repair (with UAC prompt) and the unsuccesful repair (without UAC prompt) and here are the unique lines for each case... WORKING REPAIR: ============ MSI_LUA: Credential prompt not required, user is an admin Specifed source is not already in a list. Adding new sources is allowed. FAILING REPAIR: ========== MSI_LUA: Credential prompt is not required at this point, product is managed and deployment compliant Specifed source is already in a list. Adding new sources is not allowed. Machine policy value 'EnableUserControl' is 0 PROPERTY CHANGE: Modifying RestrictedUserControl property. Its current value is '0'. Its new value: '1'. There are many Machine Policy lines that are declared in greatly different orders, but are nominally identical, although some are duplicated in the failing repair. Regards, Gareth -- View this message in context: http://www.nabble.com/UAC-Prompt-Required-tf3637831.html#a10198290 Sent from the wix-users mailing list archive at Nabble.com. |
|
From: Mike D. <mi...@di...> - 2007-04-26 18:21:04
|
>From Windows 2000 onwards, MDAC is part of the operating system, under Windows File Protection, and can only be upgraded using an OS update/hotfix-style package or by a service pack. The only supported method of installation is to run MDAC_TYP.EXE. There is no newer version of MDAC for Windows Vista. Any merge module you find is likely to either simply have detection for MDAC, contain custom actions to launch MDAC_TYP.EXE (BAD! - example at http://support.microsoft.com/kb/320788), be an unauthorized repackaging which is unlikely to work, or be an out-of-date version. I'd strongly recommend launching MDAC_TYP.EXE from a bootstrapper application. -- Mike Dimmick -----Original Message----- From: wix...@li... [mailto:wix...@li...] On Behalf Of Bob Arnson Sent: 26 April 2007 15:59 To: Gareth at Serif Cc: wix...@li... Subject: Re: [WiX-users] UAC Prompt Required Gareth at Serif wrote: > MSI_LUA: Credential prompt is not required at this point, product is managed > and deployment compliant > Specifed source is already in a list. > Take a look at http://blogs.msdn.com/rflaming/archive/2006/10/01/uac-in-msi-notes-is-this-i ntentional-if-so-why.aspx: Maintenance mode operations such as repair or feature state changes do not require credential prompts. So that's working as designed. The question is why do the MDAC merge modules require elevation. Do you have them in a single feature? You should be able to then use VersionNT to disable the feature on Vista. -- sig://boB http://bobs.org ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX...@li... https://lists.sourceforge.net/lists/listinfo/wix-users |
|
From: Bob A. <wi...@bo...> - 2007-04-27 06:28:43
|
Mike Dimmick wrote: > >From Windows 2000 onwards, MDAC is part of the operating system, under > Windows File Protection, and can only be upgraded using an OS > update/hotfix-style package or by a service pack. The only supported method > of installation is to run MDAC_TYP.EXE. > D'oh -- totally forgot about that. Thanks. -- sig://boB http://bobs.org |
|
From: Bob A. <wi...@bo...> - 2007-04-26 15:07:52
|
Gareth at Serif wrote: > MSI_LUA: Credential prompt is not required at this point, product is managed > and deployment compliant > Specifed source is already in a list. > Take a look at http://blogs.msdn.com/rflaming/archive/2006/10/01/uac-in-msi-notes-is-this-intentional-if-so-why.aspx: Maintenance mode operations such as repair or feature state changes do not require credential prompts. So that's working as designed. The question is why do the MDAC merge modules require elevation. Do you have them in a single feature? You should be able to then use VersionNT to disable the feature on Vista. -- sig://boB http://bobs.org |
