Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Files not copied after a patch installation


3 replies to this topic

kirann_hegde

kirann_hegde
  • Full Members
  • 93 posts

Posted 16 June 2013 - 16:58

Hello,

 

I am facing a strange issue where the files are not copied after a patch installation.

Up until now, we were delivering updated versions of our product using .msi(major upgrades). However, now we want to ship our updates using  .msp files.

 

There are around 5 files in 5 different components. Each of these files are unversioned and are the key files for the respective components.

Somewhere during the product lifecycle, someone introduced entries for these files in the RemoveFile table, so that the latest version of the files is always copied during the upgrade process. I am not sure as to why this was requiered, as  the File hashing for unversioned files should have allowed upgrading of these files, without requiring an explicit removal(using RemoveFile table) and installation using the InstallFiles . This was  done when the upgrades were delivered using msi files.

All was working.

 

Now , we have decided to release updates to our product using a  msp(patch ) file. However, it's surprising that the files are not  re-installed during apatch.

i.e the remove file table deletes these files and the InstallFiles standard action does not restore them. I would have expected these to be restored as they are they key files for the respective components and missing key files to be restored.

The windows installer log files indicates that the corresponding components are  marked for installation.

 

I also see the following snipped in the log file:

Allowing installation of component: {199327E3-7FBE-4D9F-8DED-38DBDEDEEC03} even though a modified unversioned keyfile exists and file versioning rules would disable the component

 

Is it because windows installer detected that the existing file on the disk was modified and decided not to replace it-atleast thats what the log message indicates.However, the Removefiles action goes ahead and cleans it whereas the InstallFiles does not do anything as the decision not to install the file was already taken earlier on in the Execute sequence.

 

Could someone explain to me as to why this behavior?

 

Regards,

Kiran Hegde

 


kirann_hegde

kirann_hegde
  • Full Members
  • 93 posts

Posted 18 June 2013 - 06:59

Could somone kindly provide me with some answers?

 

Thanks,

Kiran Hegde



VBScab

VBScab
  • Full Members
  • 436 posts

Posted 18 June 2013 - 16:48

[normal VBScab Sarcasm Mode off]

Why not ask the person/team who decided that using patches was the way to deliver updates? Clearly, he/she/they must have tested every installation scenario before coming to that decision, right?

Having never really dabbled with creating patches in the past, I would have to do some in-depth reading on MSDN to determine whether or not what you're seeing is expected behaviour but it seems likely that it is.


- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.

Mayank

Mayank
  • Full Members
  • 16 posts

Posted 28 June 2013 - 03:38

Search log file with <file name>, it must log why it's not overwriting.