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

unable to patch second version of file


2 replies to this topic

angp

angp
  • Full Members
  • 49 posts

Posted 03 April 2012 - 09:45

Hi All,

I'm having problem patching on a RTM + SP1 based master.
I have the file version of the file incremented, higher than that of the previous SP1.

The patch works perfectly on RTM but not on RTM +SP1.
I cannot find the SELMGR error in the log file.
ProductVersion of the upgradedImage is incremented. ProductCode remain.

I did not see the line, Caching "Component" from "location" for baseline 0 in my RTM + SP1 log.

But for RTM log file, Prior to the caching statement, I see that there is this Action start InstallFiles. for successful patching.

Please advice what could be the problem.
unsure.gif
Thanks,
angp

angp

angp
  • Full Members
  • 49 posts

Posted 16 April 2012 - 08:33

Found the problem. It is the Component's GUID that differs. tongue.gif

angp

angp
  • Full Members
  • 49 posts

Posted 16 April 2012 - 08:52

Had another issue. Not related to my previous issue.
This time round, the situation is, I have additional files to be patched on top of RTM and RTMM + SP1. So my SP2 contains SP1 patched files + its own set of files.I realized that these new files will not be patched.How MSIMSP knows that these files needed patching for SP2? I had these files versioned set to SP2 a higher version than RTM and SP1. But they are not patched.

From MSIMSP log I only see: "Files differ: 'd:\test\SP2\abc.dll', '\\server\RTM\abc.dll'
Patch file created: FTK=abc.dll; temp location=test\08085.HDR."
but

for files that were patched in both SP1 and SP2 I'm able to see:

"Files differ: 'd:\test\SP2\abc.dll', '\\server\RTM\abc.dll'
'\\server\RTM\abc.dll', 'd:\test\SP1\abc.dll'
Patch file created: FTK=abc.dll; temp location=test\08086.HDR."

Anyone encountered such issue???

What should I do to fix this issue?

Thanks,
angp