And "C:\Program Files\PATH\TO\FILE.xml" exists when the action is about to take place? Are you sure that file was written by your install? What do the log entries around that file being written say? Is it possible that the component placing that file somehow doesn't work when you include that action?
/l*v log-file is the same as the "voicewarmup" (the * includes every letter except v and x) when passed using the command-line. The key being referred to is described here: http://msdn.microsoft.com/en-us/library/aa369776(VS.85).aspx. The values can be determined by following links on that page. -----Original Message----- From: Castro, Edwin G. (Hillsboro) [mailto:[email protected]] Sent: Wednesday, July 29, 2009 4:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] (no subject) I'm using a command line like 'msiexec /i package.msi /l*v package.msi.log' to get my log file. How does the "voicewarmup" regkey work? The files to be modified are to be installed by the package. When I tested the package without the XmlConfig elements the files got installed properly. Here's a little more context from the log file: MSI (s) (A0:AC) [16:09:04:530]: Executing op: ActionStart(Name=WriteMetabaseChanges,Description=Installing Metabase Keys and Values,) MSI (s) (A0:AC) [16:09:04:530]: Executing op: CustomActionSchedule(Action=WriteMetabaseChanges,ActionType=11265,Source=BinaryData,Target=**********,CustomActionData=**********) MSI (s) (A0:00) [16:09:04:530]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI5EA3.tmp, Entrypoint: WriteMetabaseChanges WriteMetabaseChanges: Creating Metabase Key: /W3SVC/AppPools/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9028 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9021 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7501 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7502 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/AppPools/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9028 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9021 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7501 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7502 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/AppPools/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9028 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9021 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7501 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7502 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/AppPools/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9028 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9021 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7501 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7502 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/AppPools/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9028 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 9021 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7501 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/AppPools/********/ ID: 7502 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/1/Root/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6005 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 3001 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6000 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6020 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6021 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6022 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6006 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6043 WriteMetabaseChanges: Creating ASP App: /LM/W3SVC/1/Root/******** WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 2102 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 9101 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/1/Root/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6005 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 3001 WriteMetabaseChanges: Creating ASP App: /LM/W3SVC/1/Root/******** WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 2102 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 9101 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/1/Root/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6005 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 3001 WriteMetabaseChanges: Creating ASP App: /LM/W3SVC/1/Root/******** WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 2102 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 9101 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/1/Root/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6005 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 3001 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6000 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6020 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6021 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6022 WriteMetabaseChanges: Creating ASP App: /LM/W3SVC/1/Root/******** WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 2102 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 9101 WriteMetabaseChanges: Creating Metabase Key: /W3SVC/1/Root/********/ WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 1002 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6005 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 3001 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6000 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6020 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6021 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 6022 WriteMetabaseChanges: Creating ASP App: /LM/W3SVC/1/Root/******** WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 2102 WriteMetabaseChanges: Writing Metabase Value Under Key: /LM/W3SVC/1/Root/********/ ID: 9101 MSI (s) (A0:AC) [16:09:04:827]: Executing op: ActionStart(Name=ExecXmlConfig,,) MSI (s) (A0:AC) [16:09:04:827]: Executing op: CustomActionSchedule(Action=ExecXmlConfig,ActionType=3073,Source=BinaryData,Target=ExecXmlConfig,CustomActionData=********) MSI (s) (A0:AC) [16:09:04:843]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI5EA4.tmp, Entrypoint: ExecXmlConfig ExecXmlConfig: Found Wow64 API, but unable to link to Wow64DisableWow64FsRedirection function in kernel32.dll ExecXmlConfig: Found Wow64 API, but unable to link to Wow64RevertWow64FsRedirection function in kernel32.dll ExecXmlConfig: Configuring Xml File: C:\Program Files\PATH\TO\FILE.xml Action ended 16:09:05: InstallFinalize. Return value 3. MSI (s) (A0:AC) [16:09:05:327]: User policy value 'DisableRollback' is 0 MSI (s) (A0:AC) [16:09:05:327]: Machine policy value 'DisableRollback' is 0 MSI (s) (A0:AC) [16:09:05:359]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=989692157,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1) MSI (s) (A0:AC) [16:09:05:359]: Executing op: DialogInfo(Type=0,Argument=1033) MSI (s) (A0:AC) [16:09:05:359]: Executing op: DialogInfo(Type=1,Argument=********) MSI (s) (A0:AC) [16:09:05:359]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1]) MSI (s) (A0:AC) [16:09:05:359]: Executing op: ActionStart(Name=ExecXmlConfig,,) MSI (s) (A0:AC) [16:09:05:359]: Executing op: ProductInfo(ProductKey=********,ProductName=********,PackageName=package.msi,Language=1033,Version=50528256,Assignment=1,ObsoleteArg=0,,,PackageCode=********,,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3) MSI (s) (A0:AC) [16:09:05:359]: Executing op: ActionStart(Name=WriteMetabaseChanges,Description=Installing Metabase Keys and Values,) MSI (s) (A0:AC) [16:09:05:359]: Executing op: ActionStart(Name=ConfigureIIsExec,,) 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: Mike Carlson (DEV DIV) [mailto:[email protected]] > Sent: Wednesday, July 29, 2009 4:31 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] (no subject) > > Is verbose logging enabled (set "voicewarmup" regkey, preferably)? The > log messages here could probably be clearer that they aren't errors, > but this isn't actually failing the install, these are just info > messages saying that the WOW64 API isn't available on the machine. > > What version of the toolset are you using? Have you checked if the XML > file it's trying to modify exists, etc.? > > Thanks, > Mike Carlson > > -----Original Message----- > From: Castro, Edwin G. (Hillsboro) [mailto:[email protected]] > Sent: Wednesday, July 29, 2009 4:17 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] (no subject) > > My installer is rolling back immediately after these entries in the log > file: > > MSI (s) (A0:AC) [16:09:04:827]: Executing op: > ActionStart(Name=ExecXmlConfig,,) > MSI (s) (A0:AC) [16:09:04:827]: Executing op: > CustomActionSchedule(Action=ExecXmlConfig,ActionType=3073,Source=Binary > Data,Target=ExecXmlConfig,CustomActionData=********) > MSI (s) (A0:AC) [16:09:04:843]: Invoking remote custom action. DLL: > C:\WINDOWS\Installer\MSI5EA4.tmp, Entrypoint: ExecXmlConfig > ExecXmlConfig: Found Wow64 API, but unable to link to > Wow64DisableWow64FsRedirection function in kernel32.dll > ExecXmlConfig: Found Wow64 API, but unable to link to > Wow64RevertWow64FsRedirection function in kernel32.dll > ExecXmlConfig: Configuring Xml File: C:\Program Files\PATH\TO\FILE.xml > Action ended 16:09:05: InstallFinalize. Return value 3. > > This suggests that ExecXmlConfig is failing but I don't know why. In > particular, what does the Wox64 API stuff mean? I'm running a 32-bit > installer on 32-bit Windows XP. > > Edwin G. Castro > Software Developer - Staff > Electronic Banking Services > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com<http://www.fiserv.com/> > P Please consider the environment before printing this e-mail > > ----------------------------------------------------------------------- > ------- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > WiX-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ----------------------------------------------------------------------- > ------- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > WiX-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
