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

New files are not getting install when re-install the patch


Best Answer Stefan Krueger , 05 September 2013 - 12:53

Installed: Advertise

That's a problem. Windows Installer believes that this feature isn't actually install but only advertised. Therefore there's no need to copy the files.

Do you get any SELMGR erros in any of the logs?

Go to the full post


12 replies to this topic

Mayank

Mayank
  • Full Members
  • 16 posts

Posted 23 August 2013 - 10:11

I’m seeing some strange behavior with a minor upgrade.

1.       I added around 15 new files in a minor update to existing features.

2.       When I do install all new files are installed and when I remove all the new files are removed properly, as expected.

3.       But, when I am doing re-install, in few directories new files are not getting installed. Reinstall is copying new files only in few locations but not all files.

 

I checked the install logs from reinstall, SELMGR is detecting new files properly, no error reported.

Log traces for one of such file.

 

MSI © (6C:6C) [15:25:10:102]: SELMGR: New components have been added to feature 'CLIENT'

MSI © (6C:6C) [15:25:10:102]: SELMGR: Component 'DWFPreviewHandler1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'

.

.

MSI (s) (3C:34) [15:25:16:649]: File = DWFPreviewHandler1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B: Final State = Install

.

MSI (s) (3C:34) [15:25:16:962]: {E332DF6E-FD87-4477-971B-7C6145333F1E} File: DWFPreviewHandler1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B ValData: 1.1.0.0 0 33280

.

.

MSI (s) (3C:34) [15:25:32:618]: The file represented by File table key 'DWFPreviewHandler1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' has no eligible binary patches

Till now everything is fine, there should be installfiles entry to overwrite this file which is not present.

 

However, in the first install log the file entry is present under function InstallFiles but during reinstall there is nothing

 

Below is Log entry from first install

MSI (s) (3C:58) [15:11:34:398]: Executing op:

FileCopy(SourceName=DWFPH1.dll|DWFPreviewHandler.dll,SourceCabKey=DWFPreviewHandler1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B,DestName=DWFPreviewHandler.dll,Attributes=4608,FileSize=33280,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,Version=1.1.0.0,Language=0,InstallMode=59768832,,,,,,,)

InstallFiles: File: DWFPreviewHandler.dll

 

 

I’ve searched complete registry for files and components under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components and other places but no footprint left after removal.

 

Any help would be appreciated.

 

Thanks,

Mayank



Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 26 August 2013 - 15:40

It's not quite clear to me what you are doing, please explain step by step:

1. You install the base version msi

2. you install a minor update. Is it a msi or a msp?

3. You remove what? Only the msp from step 2 or the whole product?

4. You install again the base msi in a different folder? Or you install again the msp? Or you run the setup in maintenance mode "reinistall" (REINSTALL=ALL)?



Mayank

Mayank
  • Full Members
  • 16 posts

Posted 30 August 2013 - 11:50

Hi Steafan,

 

The minor update is msp.

 

1. Installed RTM (base version MSI).

2. Installed minor update (msp): All the existing files are patched and new files are installed properly.

3. Removed the minor update which was installed in step#2: all patched files restored back to RTM and new files removed.

 

till here everything works well.

 

4. when i try to install the same minor update again on the same machine. it's not patching all existing and not installing new files.

 

in my further investigation,

I did comparison of system before install of minor update (msp) and after removal, both are identical except windows installer patch cache and patch entries in the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components. under every component the patch entries left as it is.

 

If I restore the registries HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components to before install (before minor update) state then re-install works well. initially I was thinking registry entries are not removed that’s why windows installer is assuming files are already present hence not overwriting. But, it’s not the case, I checked with other minor updates where there is no issue, usually a patch uninstall does not remove file cache and registries from ..\S-1-5-18\Components not sure why.

 

 -Mayank



Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 02 September 2013 - 16:09

Sounds strange. Did you generate logs of all steps to see if there are any problems reported? What differences do you see between the patch install logs of the first and the second time you install the update?



Mayank

Mayank
  • Full Members
  • 16 posts

Posted 03 September 2013 - 11:11

I see during the installvalidate components states, request and action everything is changing to null, no clue why. Obviously, it's being set as expected in first time install.

 

New files which are not copied in msp re-install

Entry1->               MSI (s) (70:7C) [14:02:58:199]: Component: WFPreviewHandler1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B; Installed: Absent;   Request: Null;   Action: Null;   Client State: Unknown

Entry2->               MSI (s) (70:7C) [14:02:58:215]: Component: __WFPreviewHandler1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B65; Installed: Null;   Request: Null;   Action: Null;   Client State: Null

 

Existing file which is not patched in msp re-install

Entry1->               MSI (s) (70:7C) [14:02:58:184]: Component: com.VPro.exe.171FE5FE_1840_4392_99F5_2A2AC68D829B; Installed: Local;   Request: Null;   Action: Null;   Client State: Local

Entry2->               MSI (s) (70:7C) [14:02:58:215]: Component: __com.VPro.exe.171FE5FE_1840_4392_99F5_2A2AC68D829B65; Installed: Null;   Request: Null;   Action: Null;   Client State: Null

 

Existing file which is patched in msp re-install.

Entry1->               MSI (s) (70:7C) [14:02:58:153]: Component: com.Aloader.exe.49F95744_1841_40EE_90A1_A8D58B610FE4; Installed: Local;   Request: Local;   Action: Local;   Client State: Local

Entry2->               MSI (s) (70:7C) [14:02:58:250]: Component: __com.Aloader.exe.49F95744_1841_40EE_90A1_A8D58B610FE465; Installed: Null;   Request: Local;   Action: Local;   Client State: Null



Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 04 September 2013 - 16:34

Request: Null doesn't look good. Not sure why this happens. What does it say about the Features containing those components?



Mayank

Mayank
  • Full Members
  • 16 posts

Posted 05 September 2013 - 09:09

:( associated feature is set to re-install, I'm not able to understand this behavior of InstallValidate and why only during re-install of msp.

 

MSI (s) (70:7C) [14:02:58:153]: Feature: CLIENT; Installed: Advertise;   Request: Reinstall;   Action: Reinstall



Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 05 September 2013 - 12:53   Best Answer

Installed: Advertise

That's a problem. Windows Installer believes that this feature isn't actually install but only advertised. Therefore there's no need to copy the files.

Do you get any SELMGR erros in any of the logs?



Mayank

Mayank
  • Full Members
  • 16 posts

Posted 06 September 2013 - 10:33

Thanks Stefan,I missed this bit of info. I checked while installing the msp first time the Installed state of that feature is LOCAL

 

First Install -> MSI (s) (70:FC) [13:53:57:845]: Feature: CLIENT; Installed: Local;   Request: Reinstall;   Action: Reinstall

 

In general, how InstallValidate determines the feature's state? Is msp removal changing something.

 

No SELMGR errors, I found entries related to new components, in removal log there is not entry for SELMGR.

Here are the entries from msp re-install log
 
MSI © (B4:64) [14:02:37:467]: SELMGR: New components have been added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'VWFPreviewHandler1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'com.VWFGenerator1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'Com.CSEDMDwfWrapper1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'Com.AxExpressViewerDll1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'Com.ExpressViewerDll1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'Com.Interop.AdCommon1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'com.Interop.DwfComApi1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'com.Interop.ECompositeViewer1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'Com.Interop.EModelViewer1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'Com.EPlotModel1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'Com.Interop.EPlotRenderer1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'Com.Interop.EPlotViewer.dll1.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'com.Request.ProviderConfig_RevitRFA.xml.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'com.FGNServiceHost.EXE.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'com.FGNService1.dll.171FE5FE_1840_4392_99F5_2A2AC68D829B' is a new component added to feature 'CLIENT'
MSI © (B4:64) [14:02:37:467]: SELMGR: Component 'com.DevExpress.XtraWizard.dll.DD74585B_0A75_4BEE_9749_5BE4C1ABEB6C' is a new component added to feature 'CLIENT'
 

 

Thanks,

Mayank



Mayank

Mayank
  • Full Members
  • 16 posts

Posted 10 September 2013 - 11:32

it's because of new file, while removing it, the entire feature is turning to advertise. i think i am close to the exact problem, I'll update this thread once it's fixed



Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 11 September 2013 - 15:56

Removing a component from a feature can have this effect. But this should trigger a SELMGR error. And I didn't expect a patch uninstall to cause this type of problem.



Mayank

Mayank
  • Full Members
  • 16 posts

Posted 13 September 2013 - 10:31

I found the root cause in one of  the merge module we consumed, where a non-install developer had added few components and removed one component, component GUID  was reused from deleted component to a newly added component.

 

There were no SELMGR errors because the component code was reused, windows installer could not realize that a component is removed and it made harder to debug this issue. But while un-installtion of the patch, windows installer changed the state of entire feature to advertise. that's why re-install started skipping the components.

 

I requested developer to bring the component back to the merge module and create new GUID for newly added components. If a file is must to remove then change the attribute to transitive .

After that,  Patch install/un-install/re-install everything started working perfectly.

 

Thanks Stefan for your support, it was really helpful.

 

Regards,

Mayank



Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 17 September 2013 - 19:12

That was tricky. Glad you got it solved.