Package trying to self repair hidden system-files
Hiya!
I have a application installing a Virtual Lock (aladdin) into c:\windows\system32\setup\aladdin\.
A normal users does not have access to this folder, and because of that doesn't the package find the files.
That results in a self repair that ends up in a failure. The application starts anyway tho.
The files is needed, beacuse the application will not start anyway.
I have removed the "Key File"-flag for the files, but it is still trying to repair.
Anyone got any idea how to make the package install the files but without trying to repair?
I don't want to set any file permissions.
One way I have been thinking of is to make the package install the files to another folder, and then use a Custom Action to copy the files to the folder. I hope that isn't the best solution. [;)]
Any ideas? Thanks!
/Jonas
I have a application installing a Virtual Lock (aladdin) into c:\windows\system32\setup\aladdin\.
A normal users does not have access to this folder, and because of that doesn't the package find the files.
That results in a self repair that ends up in a failure. The application starts anyway tho.
The files is needed, beacuse the application will not start anyway.
I have removed the "Key File"-flag for the files, but it is still trying to repair.
Anyone got any idea how to make the package install the files but without trying to repair?
I don't want to set any file permissions.
One way I have been thinking of is to make the package install the files to another folder, and then use a Custom Action to copy the files to the folder. I hope that isn't the best solution. [;)]
Any ideas? Thanks!
/Jonas
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
Ilikebananas
18 years ago
Hi Jonas,
You say you removed the key-file flags. Are you sure it's those files that cause the repair?
I think the best way is to find the cause of the repair, and resolve it... [8|][8D]
You say you removed the key-file flags. Are you sure it's those files that cause the repair?
I think the best way is to find the cause of the repair, and resolve it... [8|][8D]
Posted by:
jonasm
18 years ago
Thanks for your fast reply, but according to the Event Viewer it´s "C:\WINDOWS\system32\Setup\aladdin\ does not exist".
It exist, but a normal user does not have list access to the folder....
/Jonas
It exist, but a normal user does not have list access to the folder....
/Jonas
Posted by:
Ilikebananas
18 years ago
Hi,
Do you get a component guid with that? To what component does it refer, and what's the keypath. It looks like a folder path, but as far as I know only files or registry keys can be set as key...
Do you get a component guid with that? To what component does it refer, and what's the keypath. It looks like a folder path, but as far as I know only files or registry keys can be set as key...
Posted by:
jonasm
18 years ago
Thanks again for your fast reply!
While waiting for your reply I did add one HKEY Current User registry value, and set it as a keypath.
After I did that, it does not repair the package at all (not even the HKCU-value).
I guess the problem is "solved", and I will script the HKCU-value instead... [sm=rolleyes.gif]
Must have been a bug...
Thanks for your help!
/Jonas
While waiting for your reply I did add one HKEY Current User registry value, and set it as a keypath.
After I did that, it does not repair the package at all (not even the HKCU-value).
I guess the problem is "solved", and I will script the HKCU-value instead... [sm=rolleyes.gif]
Must have been a bug...
Thanks for your help!
/Jonas
Posted by:
Ilikebananas
18 years ago
Hi,
That HKCU key will of course trigger a repair when a different user starts the app. I would rather check the project for pollution, but if it works in your environment...
Ilikebananas
That HKCU key will of course trigger a repair when a different user starts the app. I would rather check the project for pollution, but if it works in your environment...
Ilikebananas
Posted by:
mgroover
18 years ago
100% sure it's the folder path of the component you need to change in this case.
Skip the HKCU-keys, it's only the folderpath that's triggering the repair.
// martin
Skip the HKCU-keys, it's only the folderpath that's triggering the repair.
// martin
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.