Shorcuts are self repaired even if a shortcut is launched
Shorcuts are self repaired even if a shortcut is launched. The application has four shortcuts. Upon launching the 1st shortcut, it repairs. After doing so, when the 2nd shortcut was launched, it also repairs. Is there anyone of you has an idea on how to solve the issue? Thanks in advance.
FYI: vendor MSI
Regards,
Wilson
FYI: vendor MSI
Regards,
Wilson
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Each triggered repair will be logged in the Event Viewer so open EV, check which component is being repaired (the EV will show the component GUID) and take it from there.
Posted by:
wilson
15 years ago
I already have the component GUID taken from event viewer. What will be the next move?
Posted by:
SHRIRAMVEN
15 years ago
Check whether the component has the keypath set correctly. If not set it.
Posted by:
Inabus
15 years ago
The obvious thing to do is check WHY it self repairs in the first place, use logging to find out and eventvwr will tell you the component causing the selfrepair.
P
P
Posted by:
anonymous_9363
15 years ago
What will be the next move?You need to trace the GUID back to the component itself and then determine why it's being repaired. Did you validate the MSI? Might there by chance be user-level objects (files in the user profile or HKEY_CURRENT_USER registry entries) mixed with machine-level ones?
Are all the shortcuts allocated to one feature?
Posted by:
wilson
15 years ago
ORIGINAL: VBScab
What will be the next move?You need to trace the GUID back to the component itself and then determine why it's being repaired. Did you validate the MSI? Might there by chance be user-level objects (files in the user profile or HKEY_CURRENT_USER registry entries) mixed with machine-level ones?
Are all the shortcuts allocated to one feature?
Yes. I have validated the MSI and there were no ICE57 error (entries in per user registry mixed with per machine).
All shortcuts are allocated in different subfeature.
Posted by:
anonymous_9363
15 years ago
OK, well, that leaves tracing which component is triggering the repair.
It seems odd that all the s/c are triggering a repair...
It seems odd that all the s/c are triggering a repair...
Posted by:
wilson
15 years ago
ORIGINAL: VBScab
OK, well, that leaves tracing which component is triggering the repair.
It seems odd that all the s/c are triggering a repair...
Not all shortcus are triggering a repair. Only two of the shortcuts are triggering a repair, the other two shortcuts are not.
FYI: The two shortcuts that triggering a repair are executable.
Posted by:
AngelD
15 years ago
Could it be due to any temporary file?
The executable is removing files/registry during launch?
Permission problem to repairing a resource?
Giving us more details would help us help you
The executable is removing files/registry during launch?
Permission problem to repairing a resource?
Giving us more details would help us help you
Posted by:
shweta_kar
15 years ago
Hi Wilson,
through prism or picture taker cature the changes done by source as well by your msi and compare.
For e.g Run the picture taker take the intial snapshot and in the second snapshot run your source save the .pwc file.
now repeat the above process and instead of running exe run your msi.
Some resources must be missing due to which it self repairs.
through prism or picture taker cature the changes done by source as well by your msi and compare.
For e.g Run the picture taker take the intial snapshot and in the second snapshot run your source save the .pwc file.
now repeat the above process and instead of running exe run your msi.
Some resources must be missing due to which it self repairs.
Posted by:
anonymous_9363
15 years ago
Not all shortcus are triggering a repair.
In response, I'd say again
OK, well, that leaves tracing which component is triggering the repair.
Posted by:
anonymous_9363
15 years ago
Some resources must be missing due to which it self repairs.Not quite right. The resource may well be present but an indicator to its key path status may be broken/missing, which a new install of the source (if this is a captured MSI) wouldn't correct.
Wilson, you need to check the Event Viewer to get the ID of the component which is being repaired, trace that back in the MSI to the actual component and then work from there.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.