Feature states; Installed: Advertise; Request: Null; Action: Null
Hi,
I have got a scenario which I am really struggling to understand, it happens during updates and I think I have pinpointed the issue down to the feature states, here is what happens ( this only happens to around 1% of user base):
Users Point of view:
A user is happily running the software and an update is available, the update completes and the user pressumes the update has applied, a few moments late the auto update runs and again tries to update.
Technical Point of view:
The log states installation was completed successfully, however the version was not incremented, the log file states:
MSI (s) (7C:38) [20:32:57:703]: Feature: Base; Installed: Advertise; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: CreateFolder; Installed: Absent; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: ServiceControl; Installed: Absent; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: RemoveFile; Installed: Absent; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: unknown.png; Installed: Absent; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: ntdll.dll; Installed: Absent; Request: Null; Action: Null
....
As you can see the request and action is "null" so nothing is being installed, what is interesting is the Installed stae is set to "Advertise", now I am not too hot on advertisement as non of the components are advertised and the feature state for the "Base" feature is set to "Favor Local" and Advertising is set to "none". (BTW i use WISE installation studio 7)
Also, the MigrateFeatureStates CA seems to fail:
MSI (s) (7C:38) [20:32:57:687]: Doing action: MigrateFeatureStates
Action ended 20:32:57: SetODBCFolders. Return value 1.
MSI (s) (7C:38) [20:32:57:687]: Skipping MigrateFeatureStates action: not run in maintenance mode
Action start 20:32:57: MigrateFeatureStates.
MSI (s) (7C:38) [20:32:57:687]: Doing action: SetARPINSTALLLOCATION
Action ended 20:32:57: MigrateFeatureStates. Return value 0.
I really cannot understand how the installation got into this state, if anyone knows please let me know as i'm pulling my hair out over this one!
Regards
Paul
I have got a scenario which I am really struggling to understand, it happens during updates and I think I have pinpointed the issue down to the feature states, here is what happens ( this only happens to around 1% of user base):
Users Point of view:
A user is happily running the software and an update is available, the update completes and the user pressumes the update has applied, a few moments late the auto update runs and again tries to update.
Technical Point of view:
The log states installation was completed successfully, however the version was not incremented, the log file states:
MSI (s) (7C:38) [20:32:57:703]: Component: CreateFolder; Installed: Absent; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: ServiceControl; Installed: Absent; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: RemoveFile; Installed: Absent; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: unknown.png; Installed: Absent; Request: Null; Action: Null
MSI (s) (7C:38) [20:32:57:703]: Component: ntdll.dll; Installed: Absent; Request: Null; Action: Null
....
As you can see the request and action is "null" so nothing is being installed, what is interesting is the Installed stae is set to "Advertise", now I am not too hot on advertisement as non of the components are advertised and the feature state for the "Base" feature is set to "Favor Local" and Advertising is set to "none". (BTW i use WISE installation studio 7)
Also, the MigrateFeatureStates CA seems to fail:
Action ended 20:32:57: SetODBCFolders. Return value 1.
MSI (s) (7C:38) [20:32:57:687]: Skipping MigrateFeatureStates action: not run in maintenance mode
Action start 20:32:57: MigrateFeatureStates.
MSI (s) (7C:38) [20:32:57:687]: Doing action: SetARPINSTALLLOCATION
Action ended 20:32:57: MigrateFeatureStates. Return value 0.
I really cannot understand how the installation got into this state, if anyone knows please let me know as i'm pulling my hair out over this one!
Regards
Paul
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
FrankSpierings
16 years ago
Paul,
I think we need more information (at least I can't say anything usefull about this issue).
- What is the application. Is it a native MSI (I guess so...)?
- What sort of updates are we talking about? Patches? MSI's?
Please give us the information so we can be of better service to you.
I think we need more information (at least I can't say anything usefull about this issue).
- What is the application. Is it a native MSI (I guess so...)?
- What sort of updates are we talking about? Patches? MSI's?
Please give us the information so we can be of better service to you.
Posted by:
jmcfadyen
16 years ago
there could be custom actions running which are using SetFeatureState api calls. search teh feature name in the logs to see if this is being changed as the result of a CA.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.