Thanks Bruce.

I looked at the CBS.log file to get some further information. And I
believe this is the reason why the reboot is occurring. This even happens
if I run the installation process 'As Administrator'. What are .rbf files,
and why can't they be deleted?

Thanks in advance.

--------

MSI (s) (80:AC) [18:19:11:101]: Executing op:
End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=280011368)
MSI (s) (80:AC) [18:19:15:953]: PROPERTY CHANGE: Adding ReplacedInUseFiles
property. Its value is '1'.
MSI (s) (80:AC) [18:19:15:984]: User policy value 'DisableRollback' is 0
MSI (s) (80:AC) [18:19:15:984]: Machine policy value 'DisableRollback' is 0
MSI (s) (80:AC) [18:19:16:046]: Note: 1: 1321 2: C:\Config.Msi\146435.rbf
3: 5
MSI (s) (80:AC) [18:19:16:046]: Verifying accessibility of file: 146435.rbf
Info 1903. Scheduling reboot operation: Deleting file
C:\Config.Msi\146435.rbf. Must reboot to complete operation.
MSI (s) (80:AC) [18:19:16:062]: Note: 1: 1321 2: C:\Config.Msi\146437.rbf
3: 5
MSI (s) (80:AC) [18:19:16:062]: Verifying accessibility of file: 146437.rbf
Info 1903. Scheduling reboot operation: Deleting file
C:\Config.Msi\146437.rbf. Must reboot to complete operation.
MSI (s) (80:AC) [18:19:16:436]: Note: 1: 1321 2: C:\Config.Msi\14643d.rbf
3: 5
MSI (s) (80:AC) [18:19:16:436]: Verifying accessibility of file: 14643d.rbf
Info 1903. Scheduling reboot operation: Deleting file
C:\Config.Msi\14643d.rbf. Must reboot to complete operation.
MSI (s) (80:AC) [18:19:16:436]: Note: 1: 1321 2: C:\Config.Msi\14643e.rbf
3: 5
MSI (s) (80:AC) [18:19:16:436]: Verifying accessibility of file: 14643e.rbf
Info 1903. Scheduling reboot operation: Deleting file
C:\Config.Msi\14643e.rbf. Must reboot to complete operation.
MSI (s) (80:AC) [18:19:16:436]: Note: 1: 1321 2: C:\Config.Msi\14643f.rbf
3: 5
MSI (s) (80:AC) [18:19:16:436]: Verifying accessibility of file: 14643f.rbf
Info 1903. Scheduling reboot operation: Deleting file
C:\Config.Msi\14643f.rbf. Must reboot to complete operation.
MSI (s) (80:AC) [18:19:16:436]: Note: 1: 1321 2: C:\Config.Msi\146440.rbf
3: 5
MSI (s) (80:AC) [18:19:16:436]: Verifying accessibility of file: 146440.rbf
MSI (s) (80:AC) [18:19:16:452]: Note: 1: 2318 2:
MSI (s) (80:AC) [18:19:16:592]: Note: 1: 2318 2:
Info 1903. Scheduling reboot operation: Deleting file
C:\Config.Msi\146440.rbf. Must reboot to complete operation.
MSI (s) (80:AC) [18:19:16:592]: No System Restore sequence number for this
installation.


- Chris.




On 31/07/12 4:41 PM, "Bruce Cran" <br...@cran.org.uk> wrote:

>On 30/07/2012 23:59, Chris Dahl wrote:
>> My question then is how can I using Wix set the <merge> entry to *not*
>>try to install the VC10 merge module if it already exists on the system?
>>The problem we are having is that our installer is trying to install it,
>>but it's in use currently by another process. And that process isn't
>>responding to the Restart Manager messaging correctly, which forces a
>>reboot.
>
>I'd guess you have version 10.0.40219.1 on the system and it's trying to
>install the version with KB2565063, which updates the files to
>10.0.40219.325 - the "Visual C++ 2010 SP1 x64" redistributable available
>via the Microsoft Download Center and Visual Studio 2012 RC both contain
>the old version so it's not unlikely you'll be updating to the newer
>version.
>
>-- 
>Bruce Cran


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to