Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

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.

Minor Upgrade does not reinstall components

Started by daniela , Nov 17 2004 05:03

4 replies to this topic

daniela

Members
3 posts

Posted 17 November 2004 - 05:03

Hello friends, I have seen similar topics this particular problem posted all over the internet, but none of the suggestions seem to work for me.

I have created a Minor Upgrade to replace a few executables (they are each individual components) with newer versions of the same files. When i run the setup.exe, it says it performs the upgrade... but the old files are not replaced with the new ones! The product version has successfully been updated, according to Support Information in Add/Remove Programs. Looking at the log file, there are no SELMGR entries, and i haven't added or removed any components in the project. My two features indicate a local action, but all of the components have NULL actions., which is why nothing upgrades.

CODE

MSI (s) (F8:54): Feature: NVR_VWR; Installed: Local; Request: Local; Action: Local
MSI (s) (F8:54): Feature: NVR_SS; Installed: Local; Request: Local; Action: Local
MSI (s) (F8:54): Component: htdocs; Installed: Local; Request: Null; Action: Null
MSI (s) (F8:54): Component: websrvr; Installed: Local; Request: Null; Action: Null
...

Puzzled at why the components do not update, i created a nearly blank, basic upgrade that works fine. The correctly operating test programs's log file reports that "Request: Reinstall; Action: Reinstall" are present for the features, and the component requests and actions are local. I would like to have this same reinstall behavior in my main project, but can't figure out how to force reinstall mode on.
I have tried:
Set Reinstall to ALL on Next button click
Custom Action setting REINSTALL to ALL
Add Reinstall and REINSTALL properties to the property table
Pass REINSTALL=ALL on the commandline to msiexec using /V switch of setup.exe
No matter what i try, Request and Action are always Local for the feautures, and always Null for the components.

I do not wish to move to a major upgrade. Please, oh please please please tell me how to reinstall my files. I've attached to log file for your perusal.

Attached Files

nvr_inst.zip 24.5KB 79 downloads

daniela

Members
3 posts

Posted 18 November 2004 - 02:13

Also tried:

Not using setup.exe, as in
msiexec /i myinstallname.msi REINSTALLMODE=vomus REINSTALL=ALL /L*v logfile.txt

Setting default maintenance mode to reinstall using _IsMaintenanceMode = Reinstall in the properties table as a default.

Recreated the upgrade item, pointed to previous version msi, and ran the update validation wizard. This reported no errors or problems.

Verified that there are no conditions on any of the components.

Still no change, everything has a Null action!

Stefan Krueger

InstallSite.org

Administrators
13,269 posts

Posted 18 November 2004 - 08:49

In your log, find the information about whether it will install/overwrite components and files, or not, and why (e.g. file with newer version already exists, and the like) This should give you some hint why Windows Installer doesn't overwrite the files.

Stefan Krüger
InstallSite.org twitter facebook

HOWTO: Logging an MSI installation

Read this before sending me e-mail or private messages

daniela

Members
3 posts

Posted 19 November 2004 - 01:32

Hello Stefan,
Thanks for the advice. I searched the log file for overwrite and came up with a lone section of interest:

CODE

MSI (c) (4C:E0): Disallowing installation of component: {997FA962-E067-11D1-9396-00A0C90F27F9} since the same component with higher versioned keyfile exists
MSI (c) (4C:E0): Disallowing installation of component: {474F61F1-7342-11D2-A199-00A0C90AB50F} since the same component with higher versioned keyfile exists
MSI (c) (4C:E0): Disallowing installation of component: {10048713-2C96-11D2-9A97-006097C4E452} since the same component with higher versioned keyfile exists
MSI (c) (4C:E0): Disallowing installation of component: {74991043-85B9-4462-93E1-AFBA4139477F} since the keyfile exists and the component is marked to never overwrite existing installations
MSI (c) (4C:E0): Disallowing installation of component: {49E71CBB-3C4D-4FD5-A01F-7F81BB43FCD3} since the keyfile exists and the component is marked to never overwrite existing installations

The last 2 items are explainable because I have two components which are set to never overwrite. This is the behaviour i would like for those 2 configuration files, and the GUID listed here matches them in the component table.
The first 3 items are puzzling, however. I have done a search of all tables in the project for these GUIDs and they do not appear anywhere. Neither do they appear in the registry before or after the upgrade is attempted.
The 2nd and 3rd GUIDs do not appear anywhere else in the log file. The 1st GUID appears in the log file closer to the end:

CODE

MSI (s) (98:AC): Executing op: ActionStart(Name=RegisterClassInfo,Description=Registering class servers,Template=Class ID: )
Action 15:53:30: RegisterClassInfo. Registering class servers
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={00020420-0000-0000-C000-000000000046},,,Description=PSDispatch,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {00020420-0000-0000-C000-000000000046}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={B196B286-BAB4-101A-B69C-00AA00341D07},,,Description=PSFactoryBuffer,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {B196B286-BAB4-101A-B69C-00AA00341D07}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={0BE35203-8F91-11CE-9DE3-00AA004BB851},ProgId=StdFont,,Description=CLSID_StdFont,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {0BE35203-8F91-11CE-9DE3-00AA004BB851}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={46763EE0-CAB2-11CE-8C20-00AA0051E5D4},ProgId=OldFont,,Description=Obsolete Font,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {46763EE0-CAB2-11CE-8C20-00AA0051E5D4}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={0BE35204-8F91-11CE-9DE3-00AA004BB851},ProgId=StdPicture,,Description=CLSID_StdPict,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {0BE35204-8F91-11CE-9DE3-00AA004BB851}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={00020421-0000-0000-C000-000000000046},,,Description=PSEnumVariant,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {00020421-0000-0000-C000-000000000046}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={00020422-0000-0000-C000-000000000046},,,Description=PSTypeInfo,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {00020422-0000-0000-C000-000000000046}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={00020423-0000-0000-C000-000000000046},,,Description=PSTypeLib,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {00020423-0000-0000-C000-000000000046}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={00020424-0000-0000-C000-000000000046},,,Description=PSOAInterface,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {00020424-0000-0000-C000-000000000046}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={00020425-0000-0000-C000-000000000046},,,Description=PSTypeComp,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {00020425-0000-0000-C000-000000000046}
MSI (s) (98:AC): Executing op: RegClassInfoRegister(Feature=NVR_VWR,Component={997FA962-E067-11D1-9396-00A0C90F27F9},,ClsId={0000002F-0000-0000-C000-000000000046},,,Description=CLSID_RecordInfo,Context=InprocServer32,,,,,,,,,)
RegisterClassInfo: Class ID: {0000002F-0000-0000-C000-000000000046}

However, I do not know what these 11 classes are being registered with this untraceable component GUID.

I have examined the upgrade transformation in Orca and found that version numbers increase on exactly 5 executables (as expected). These executables are in their own components and each marked as a key file. There are no version numbers that decrease, according to this method of examination.

If you can shed some light on the origin of these strange component GUIDs, your help would be appreciated. I do not know why only 5 components have " Disallowing installation of component" entries in the log, yet all 25 or so components have Action: Null.
I suspect the problem has something to do with the feature Action: Local instead of feature Action: Reinstall, but I don't know why this would be the case.

Thanks for your input!

Stefan Krueger

InstallSite.org

Administrators
13,269 posts

Posted 19 November 2004 - 09:42

QUOTE

If you can shed some light on the origin of these strange component GUIDs

Maybe they are from some merge modules? Did you search the InstallShield project file (which won't search in merge modules) or the actual .msi file (using Orca)?

QUOTE

I suspect the problem has something to do with the feature Action: Local instead of feature Action: Reinstall, but I don't know why this would be the case.

Yes, I suspect this also. And I don't know either.

Stefan Krüger
InstallSite.org twitter facebook

HOWTO: Logging an MSI installation

Read this before sending me e-mail or private messages

Back to InstallShield "Basic MSI" Projects