Sounds like the account used to install was not the account used to execute the 
software in the perUser case. If that really was the case then the keys in HKCU 
would not be available to the executing process.

Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail

> -----Original Message-----
> From: Jan Bilek [mailto:bil...@gmail.com]
> Sent: Thursday, March 25, 2010 11:39 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Unreadable Registry values created with WiX
> installer
> 
> Hello,
> Thanks for your care, but i solved the puzzle myself (as usual after i
> go public with my problem).
> Here's the solution:
> We were trying to create keys under HKEY_CLASSES_ROOT and these
> attempts
> are forwarded to HKCU or HKLM
> (http://wix.sourceforge.net/manual-wix2/wix_xsd_registry.htm),
> depending
> on package install scope. When the scope was perUser then keys from
> HKCU
> were unreadable (still don't know why). We simply had to switch scope
> to
> perMachine to make it work. Fortunately we were able make this score
> switch without any harm to other installation parts.
> 
> Regards,
> Jan
> 
> 
> Pally Sandher wrote:
> > 1 - post your WiX code for creating the Registry Entries otherwise
> we're
> > all just guessing at the problem. Also extracts from a verbose log
> when
> > the registry entries are created on the machine with the problem may
> > also help.
> >
> > 2 - Which other systems have you tested? Is it fine on x64 Vista?
> What
> > about x86 & x64 versions of Server 2008 & Windows 7?
> >
> > 3 - final release of WiX 3.0 is v3.0.5419.0. You probably want to
> update
> > your compiler to that version as it's been out since July 2009.
> >
> > Palbinder Sandher
> > Software Deployment & IT Administrator
> > T: +44 (0) 141 945 8500
> > F: +44 (0) 141 945 8501
> >
> > http://www.iesve.com
> > **Design, Simulate + Innovate with the <Virtual Environment>**
> > Integrated Environmental Solutions Limited. Registered in Scotland
> No.
> > SC151456
> > Registered Office - Helix Building, West Of Scotland Science Park,
> > Glasgow G20 0SP
> > Email Disclaimer
> >
> > -----Original Message-----
> > From: Jan Bilek [mailto:bil...@gmail.com]
> > Sent: 25 March 2010 00:35
> > To: General discussion for Windows Installer XML toolset.
> > Subject: [WiX-users] Unreadable Registry values created with WiX
> > installer
> >
> > Hello,
> > I have found a very strange problem.
> > In my installer i'm creating several registry keys and values (COM
> > assembly registration). They are all created without any issues, they
> > are fully accessible using registry editor, they have sufficient
> > permissions to be accessed by any local user, but when i try to open
> the
> > keys and query values from my application, then some keys cannot be
> open
> > and values read.
> > When i delete the registry keys and create them manually (using reg
> > file), then it works flawlessly. This problem occurs only on one
> testing
> > machine (32bit Vista). After several days of struggle i'm starting to
> > think, that there must a problem in Wix (3.0.5217.0).
> >
> > Does anyone have an idea what could be a cause of this strange
> problem?
> > Wix? MSI? Malfunctioning testing system?
> >
> > Thanks for any reply.
> >
> > Jan
> >
> > ---------------------------------------------------------------------
> ---
> > ------
> > Download Intel&#174; 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
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> >
> > ---------------------------------------------------------------------
> ---------
> > Download Intel&#174; 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
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> 
> 
> -----------------------------------------------------------------------
> -------
> Download Intel&#174; 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
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Download Intel&#174; 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
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to