Are the Components that contain the registration being installed? A verbose
log file will tell all.

On Thu, Jul 7, 2011 at 9:26 AM, Wang, Miaohsi <miaohsi.w...@invensys.com>wrote:

> Hi Rob,
>
> I added the two standard actions into the InstallExecuteSequence as you
> described (without attributes), but the result is the same. Those merge
> module files are still not getting registered when feature Server is not
> selected for installation. It seems the registration of the files is tied to
> feature Server. One more thing, when I examined the final MSI file, I could
> see that the registration data for those merge module files is present in
> the MSI. Any more idea?
>
> Thanks a lot,
> Miaohsi
> -----Original Message-----
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Wednesday, July 06, 2011 10:47 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Merge module files not getting registered
>
> The Merge Modules are supposed to carry the actions they require. If the
> Merge Module is not authored correctly, you can ensure the actions get in
> the final MSI by doing something like:
>
> <InstallExecuteSequence>
>   <RegisterClassInfo/>
>   <WriteRegistryValues/>
> </InstallExecuteSequence>
>
> Or whatever actions you need. Notice there are no attributes on those
> actions. That ensures they get the default location (which is right
> 99.99999% of the time).
>
> On Wed, Jul 6, 2011 at 8:50 AM, Wang, Miaohsi <miaohsi.w...@invensys.com
> >wrote:
>
> > Dear All,
> >
> > We have two features (Client and Server) in an WiX installer and both of
> > them include a merge module, called CFI. Some of the CFI files are
> > self-registering. During the install runtime, if we select both features
> to
> > install, then these CFI files register properly. However, if we select
> only
> > Client to install, the CFI files are still installed but not registered.
> So,
> > I generated a log file in each of the two cases. At the bottom is a
> > difference that I found when comparing the log files.
> >
> > As you can see, in the Client + Server case, there is a lot of
> registration
> > going on in action RegisterClassInfo. In the case of Client-Only install,
> > action RegisterClassInfo does not do much and switches quickly to action
> > WriteRegistryValues. Moreover, take file pv.dll in CFI for instance, when
> > the file is registered it seems associated with feature Server, as you
> can
> > see below.
> >
> > MSI (s) (E4:74) [13:23:12:953]: Executing op:
> >
> RegClassInfoRegister(Feature=Server,Component={D2DDE281-9076-477C-A6A9-105FC4DDF425},FileName=C:\Program
> > Files\Common Files\SIMSCI\SIMSCICFI40\VC090x32\bin\pv.dll,
> >
> > Is there a way to ensure that the merge module files are registered
> > whenever they are installed?
> >
> > Thanks a lot,
> > Miaohsi
> >
> > Client + Server install logging:
> > CreateShortcuts: Shortcut: kfmmh9ri.0|Invensys OPC UA Simulation Server
> 1.0
> > MSI (s) (E4:74) [13:23:12:859]: Note: 1: 1402 2: HKEY_CLASSES_ROOT\.0 3:
> 2
> > MSI (s) (E4:74) [13:23:12:890]: Executing op:
> > ActionStart(Name=RegisterClassInfo,Description=Registering Class
> > servers,Template=Class Id: [1])
> > Action 13:23:12: RegisterClassInfo. Registering Class servers
> > MSI (s) (E4:74) [13:23:12:906]: Executing op:
> >
> RegClassInfoRegister(Feature=SecurityClient,Component={805EA8EE-7E8B-4FE7-B60B-7AC6EBB20186},FileName=C:\SimSci\ROMeo60\Shared\Bin\Sec_DCOMProxy.dll,ClsId={C33BA386-5DC5-4F4B-B90C-A1A29C18A37E},,,Description=PSFactoryBuffer,Context=InprocServer32,,,,,,,,,)
> > RegisterClassInfo: Class Id: {C33BA386-5DC5-4F4B-B90C-A1A29C18A37E}
> > MSI (s) (E4:74) [13:23:12:906]: Executing op:
> >
> RegClassInfoRegister(Feature=ModelAppServer,Component={0E1B4F18-CB9F-4088-9585-E08863050303},FileName=C:\WINDOWS\system32\VFP6R.DLL,ClsId={008B6021-1F3D-11D1-B0C8-00A0C9055D74},ProgId=VisualFoxpro.Runtime.6,VIProgId=VisualFoxpro.Runtime,,Context=InprocServer32,,,,,,,,,)
> > RegisterClassInfo: Class Id: {008B6021-1F3D-11D1-B0C8-00A0C9055D74}
> > MSI (s) (E4:74) [13:23:12:921]: Executing op:
> >
> RegClassInfoRegister(Feature=Server,Component={3207D1B1-80E5-11D2-B95D-006097C4DE24},,ClsId={0002E005-0000-0000-C000-000000000046},,,Description=Component
> > Categories Manager,Context=InprocServer32,,,,,,,,,)
> > RegisterClassInfo: Class Id: {0002E005-0000-0000-C000-000000000046}
> > MSI (s) (E4:74) [13:23:12:921]: Executing op:
> >
> RegClassInfoRegister(Feature=Server,Component={FCD3F2B9-39D6-499E-90C0-0DDBCAF5FAAA},FileName=C:\Program
> >
> Files\SsiFlex\SSIFlex.exe,ClsId={CB12807E-0EA9-4EE0-B82C-550874B354E1},ProgId=SSIFlex.SSIFlexSrv.1,VIProgId=SSIFlex.SSIFlexSrv,Description=SSIFlexSrv
> >
> Class,Context=LocalServer32,,AppID={8F58E37C-F765-4E72-97C3-40D64F61F1BE},,,,,,,)
> > RegisterClassInfo: Class Id: {CB12807E-0EA9-4EE0-B82C-550874B354E1}
> > MSI (s) (E4:74) [13:23:12:937]: Executing op:
> >
> RegAppIdInfoRegister(AppId={8F58E37C-F765-4E72-97C3-40D64F61F1BE},ClsId={CB12807E-0EA9-4EE0-B82C-550874B354E1},,LocalService=SSIFlex,ServiceParameters=-Service,,,)
> > MSI (s) (E4:74) [13:23:12:953]: Executing op:
> >
> RegClassInfoRegister(Feature=Server,Component={2A2009B8-B158-4644-821C-4C3C0C89B97D},FileName=C:\Program
> >
> Files\FlexCell\FlexCell.ocx,ClsId={FB821424-DF64-417D-9064-C2C789D53EC6},ProgId=FlexCell.Grid,,Description=FlexCell.Grid,Context=InprocServer32,,,,,,,,,)
> > RegisterClassInfo: Class Id: {FB821424-DF64-417D-9064-C2C789D53EC6}
> > MSI (s) (E4:74) [13:23:12:953]: Executing op:
> >
> RegClassInfoRegister(Feature=Server,Component={D2DDE281-9076-477C-A6A9-105FC4DDF425},FileName=C:\Program
> > Files\Common
> >
> Files\SIMSCI\SIMSCICFI40\VC090x32\bin\pv.dll,ClsId={258CCBBD-6CB2-11DE-8BF2-444553544200},ProgId=SimSci.PVServerVC90x86.90,VIProgId=SimSci.PVServerVC90x86,Description=SimSci
> > PROvision Server v9.0 (VC 9.0, 32-bit),Context=InprocServer32,,,,,,,,,)
> > RegisterClassInfo: Class Id: {258CCBBD-6CB2-11DE-8BF2-444553544200}
> > MSI (s) (E4:74) [13:23:12:968]: Executing op:
> >
> RegClassInfoRegister(Feature=Server,Component={ADDCA5C6-9F10-4A9F-A714-393C11AF268B},FileName=C:\Program
> > Files\Common
> >
> Files\SIMSCI\SIMSCICFI40\VC090x32\bin\PVChar.ocx,ClsId={4D4A1DDD-6CB2-11DE-8BF2-444553544200},,,Description=SimSci
> > Char Property Page v9.0 (VC 9.0, 32-bit),Context=InprocServer32,,,,,,,,,)
> > RegisterClassInfo: Class Id: {4D4A1DDD-6CB2-11DE-8BF2-444553544200}
> > MSI (s) (E4:74) [13:23:12:984]: Executing op:
> >
> RegClassInfoRegister(Feature=Server,Component={ADDCA5C6-9F10-4A9F-A714-393C11AF268B},FileName=C:\Program
> > Files\Common
> >
> Files\SIMSCI\SIMSCICFI40\VC090x32\bin\PVChar.ocx,ClsId={4D4A1DDC-6CB2-11DE-8BF2-444553544200},ProgId=SimSci.CharCtrlVC90x86.90,,Description=SimSci
> > Char Control v9.0 (VC 9.0, 32-bit),Context=InprocServer32,,,,,,,,,)
> > RegisterClassInfo: Class Id: {4D4A1DDC-6CB2-11DE-8BF2-444553544200}
> > MSI (s) (E4:74) [13:23:12:984]: Executing op:
> >
> RegClassInfoRegister(Feature=Server,Component={D4C62D2E-5898-4D50-97AD-C10ADB5496CA},FileName=C:\Program
> > Files\Common
> >
> Files\SIMSCI\SIMSCICFI40\VC090x32\bin\PVFloat.ocx,ClsId={77C6C5B1-6CB2-11DE-8BF2-444553544200},,,Description=SimSci
> > Float Property Page v9.0 (VC 9.0,
> 32-bit),Context=InprocServer32,,,,,,,,,)
> >
> >
> >
> >
> ---------------------------------------------------------------------------------
> > Client-Only install logging
> > CreateShortcuts: Shortcut: kfmmh9ri.0|Invensys OPC UA Simulation Server
> 1.0
> > MSI (s) (E4:88) [13:14:22:390]: Note: 1: 1402 2: HKEY_CLASSES_ROOT\.0 3:
> 2
> > MSI (s) (E4:88) [13:14:22:390]: Executing op:
> > ActionStart(Name=RegisterClassInfo,Description=Registering Class
> > servers,Template=Class Id: [1])
> > Action 13:14:22: RegisterClassInfo. Registering Class servers
> > MSI (s) (E4:88) [13:14:22:406]: Executing op:
> >
> RegClassInfoRegister(Feature=SecurityClient,Component={805EA8EE-7E8B-4FE7-B60B-7AC6EBB20186},FileName=C:\SimSci\ROMeo60\Shared\Bin\Sec_DCOMProxy.dll,ClsId={C33BA386-5DC5-4F4B-B90C-A1A29C18A37E},,,Description=PSFactoryBuffer,Context=InprocServer32,,,,,,,,,)
> > RegisterClassInfo: Class Id: {C33BA386-5DC5-4F4B-B90C-A1A29C18A37E}
> > MSI (s) (E4:88) [13:14:22:406]: Executing op:
> > ActionStart(Name=WriteRegistryValues,Description=Writing system registry
> > values,Template=Key: [1], Name: [2], Value: [3])
> > Action 13:14:22: WriteRegistryValues. Writing system registry values
> > MSI (s) (E4:88) [13:14:22:406]: Executing op:
> > ProgressTotal(Total=987,Type=1,ByteEquivalent=13200)
> > MSI (s) (E4:88) [13:14:22:421]: Executing op:
> >
> RegOpenKey(,Key=CLSID\{C33BA386-5DC5-4F4B-B90C-A1A29C18A37E}\InProcServer32,,BinaryType=0)
> > MSI (s) (E4:88) [13:14:22:421]: Executing op:
> > RegAddValue(Name=ThreadingModel,Value=Both,)
> >
> >
> > *** Confidentiality Notice: This e-mail, including any associated or
> > attached files, is intended solely for the individual or entity to which
> it
> > is addressed. This e-mail is confidential and may well also be legally
> > privileged. If you have received it in error, you are on notice of its
> > status. Please notify the sender immediately by reply e-mail and then
> delete
> > this message from your system. Please do not copy it or use it for any
> > purposes, or disclose its contents to any other person. This email comes
> > from a division of the Invensys Group, owned by Invensys plc, which is a
> > company registered in England and Wales with its registered office at 3rd
> > Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023).
> For
> > a list of European legal entities within the Invensys Group, please go to
> >
> http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77
> > .
> >
> > You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> > recept...@invensys.com. This e-mail and any attachments thereto may be
> > subject to the terms of any agreements between Invensys (and/or its
> > subsidiaries and affiliates) and the recipient (and/or its subsidiaries
> and
> > affiliates).
> >
> >
> >
> ------------------------------------------------------------------------------
> > All of the data generated in your IT infrastructure is seriously
> valuable.
> > Why? It contains a definitive record of application performance, security
> > threats, fraudulent activity, and more. Splunk takes this data and makes
> > sense of it. IT sense. And common sense.
> > http://p.sf.net/sfu/splunk-d2d-c2
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
>
>
> --
> virtually, Rob Mensching - http://RobMensching.com LLC
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to which it
> is addressed. This e-mail is confidential and may well also be legally
> privileged. If you have received it in error, you are on notice of its
> status. Please notify the sender immediately by reply e-mail and then delete
> this message from your system. Please do not copy it or use it for any
> purposes, or disclose its contents to any other person. This email comes
> from a division of the Invensys Group, owned by Invensys plc, which is a
> company registered in England and Wales with its registered office at 3rd
> Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For
> a list of European legal entities within the Invensys Group, please go to
> http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77
> .
>
> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> recept...@invensys.com. This e-mail and any attachments thereto may be
> subject to the terms of any agreements between Invensys (and/or its
> subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
> affiliates).
>
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to