While repair package ask for .msi
Hello
I need your advice on the issue which I am facing with some of my packages which I captured through Wise Setup Capture tool.Packages are working fine with install uninstall but when I try to repair package from add remove programs it's gives error "source not found".
I validated the package there is not much problem only two ICE03 errors were there that also not some major.
I keep only single feature install while creating packges.
I want to understand why application not try to search app.msi in c:\windows\installer instead of the location from where it's installed.
I tried installing the msi which was getting copied in c:\windows\Installer folder that's working.
I know somewhere I am going wrong while capturing or editing.
Please suggest,
Thanks in advance
R Ray
I need your advice on the issue which I am facing with some of my packages which I captured through Wise Setup Capture tool.Packages are working fine with install uninstall but when I try to repair package from add remove programs it's gives error "source not found".
I validated the package there is not much problem only two ICE03 errors were there that also not some major.
I keep only single feature install while creating packges.
I want to understand why application not try to search app.msi in c:\windows\installer instead of the location from where it's installed.
I tried installing the msi which was getting copied in c:\windows\Installer folder that's working.
I know somewhere I am going wrong while capturing or editing.
Please suggest,
Thanks in advance
R Ray
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
AngelD
15 years ago
The original source is required if:
file(s) needs to be (re-)installed
unversioned files missing an entry in the MsiFileHash table
the ResolveSource action is used and not conditioned to only run on install
e or a is added to the REINSTALLMODE property
feature set to run-from-source
any custom action set to access the original source
I'm sure I've missed some but these are the regulars
Check the event viewer and verbose log to find out why it requires the source
file(s) needs to be (re-)installed
unversioned files missing an entry in the MsiFileHash table
the ResolveSource action is used and not conditioned to only run on install
e or a is added to the REINSTALLMODE property
feature set to run-from-source
any custom action set to access the original source
I'm sure I've missed some but these are the regulars
Check the event viewer and verbose log to find out why it requires the source
Posted by:
raviray
15 years ago
Thanks Angel
but through log file I don't see any errors and even in validation it didnt give any error.
but through log file I don't see any errors and even in validation it didnt give any error.
Posted by:
raviray
15 years ago
First you tell me one thing...
If I create msi for legacy setup or create mst in case of vendor msi & keep the option repair checked to show in add remove programs,will it require that msi to present on machine at time of repair or not.
As I know already one copy of the msi/msi&mst goes to c:\windows\Installer folder so application should get repair from there not should ask for the location from where it was installed.
Please suggest
If I create msi for legacy setup or create mst in case of vendor msi & keep the option repair checked to show in add remove programs,will it require that msi to present on machine at time of repair or not.
As I know already one copy of the msi/msi&mst goes to c:\windows\Installer folder so application should get repair from there not should ask for the location from where it was installed.
Please suggest
Posted by:
AngelD
15 years ago
Ray,
If a component is found broken which in turn includes files the original source is required as the cached msi do not contain the CAB "media".
This normally happens for files located in the user's profile.
Check which components that the self-check triggers on and which component that was found broken; this can be found in the event viewer.
The verbose log will give you more details to go on if needed.
If a component is found broken which in turn includes files the original source is required as the cached msi do not contain the CAB "media".
This normally happens for files located in the user's profile.
Check which components that the self-check triggers on and which component that was found broken; this can be found in the event viewer.
The verbose log will give you more details to go on if needed.
Posted by:
anonymous_9363
15 years ago
Also, the option whether or not to have an entry in ARP is just that - it controls whether or not your app appears in ARP. It doesn't affect whether or not the MSI is required.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.