Sorry I didn't follow up (on my own post none-the-less! for shame!) The error code was "0x8013141A". I was completely thrown by this, because everything I read related to signed code...I wasn't signing any of my code, and as far as I could tell, the assembly was a Microsoft (.net) assembly (Microsoft.Deployment.WindowsInstaller). It then occurred to me though that I was working in a wix-development environment (built some custom extensions to votive and the pre-processo), having compiled wix from the source code (p.i.t.a.). One of the articles I'd read talked about how the Wix team signs the assemblies with their own private key...
Long story short, Microsoft.Deployment.WindowsInstaller is NOT part of the .NET framework, and is an assembly created by the Wix team. The one being used in my installer was not signed with their private key, and so wouldn't get loaded at install time (on any other machine). I rolled back my dev environment, installed the pre-compiled binaries and badda bing: we're good to go. Sorry for the total lack of communication, my bad. Stryder On Sun, Mar 21, 2010 at 8:46 AM, dB. <[email protected]> wrote: > I couldn't get elevation to happen programmatically, but my installers run > in a bootstrapper, so I got the bootstrapper to elevate (dotnetinstaller, > http://dotnetinstaller.codeplex.com supports a custom manifest). It seems > like this is the only easy option, because from my understanding elevation > is per process. Maybe someone can implement an elevated server piece, do the > checks and come back with the result? > > If you don't want to reinvent the wheel, http://msiext.codeplex.com has > all this stuff nicely implemented in a wix UI extension. The CAs are C++. > Screenshots: > http://msiext.codeplex.com/wikipage?title=Common%20UI%20Wix%20Extension > > Hope this helps, > dB. > > > dB. @ dblock.org > Moscow|Geneva|Seattle|New York > > > -----Original Message----- > From: Stryder Crown [mailto:[email protected]] > Sent: Friday, March 19, 2010 2:04 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] UAC, InstallService, verify user account... > > Getting all three to work together isn't...well, working. Hoping somebody > might have a suggestion as to how this could work better... > > I've got a complete handle on the actual service installation and start up > (and tear down) and can even have the user enter account information to run > the service as via an install dialog. > > But, if the account information isn't correct, when the service is > installed > (and started) I get the 'insufficient privileges' dialog box with only > 'retry' and 'cancel' buttons. The user has no opportunity (at that point) > to re-enter the account information (user name and password). > > So, I thought I'd be clever and execute a custom action that uses > SSPI/Logon > to validate the users information at the installer dialog, before the > service is installed. And this works too! Except under UAC conditions > (Vista/windows 7). If I have UAC disabled, I have no problems. So, this > means I have to elevate the custom action...but since we're talking UAC, I > have to defer it to InstallInitialize/InstallFinalize...At which point > there's no dialog entry available. And at that point, I can't even get a > dialog going from the Custom Action (via winforms/WPF) from which I > would've > set the verified and set the Properties being used by the ServiceInstall > element. > > So, any ideas? Did any of that make sense? Anybody else out there try to > tackle User Authentication/Impersonation during an install? I'm about to > see if I can't push the custom action back to the end of the installation > process, and update the service at that point, but I'm not feeling too > confident (or proud) of this sort of hackery. > > Stryder > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
