Hello All, I am having a problem with Adobe PhotoShop 6.0.1 and creating a package. The package works fine as an administrator but when a user logs in I get the following errors:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 7/29/2005
Time: 11:47:18 AM
User: "Domain"\"User"
Computer: "computer's name"
Description:
Detection of product '{22B7A9C4-56E8-48AB-B4D3-D7FE322F5A5F}', feature 'AdobePhotoShop6NewFeature', component '{A3C692FA-2847-48C4-9728-226BAA93C233}' failed. The resource 'HKEY_CURRENT_USER\SOFTWARE\InstallShield Repackaged Applications\ONE-NET\AdobePhotoShop^6\Folder_AdobePhotoshop6Settings\Installed' does not exist.

and

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 7/29/2005
Time: 11:47:18 AM
User: "Domain"\"User"
Computer: "computer's name"
Description:
Detection of product '{22B7A9C4-56E8-48AB-B4D3-D7FE322F5A5F}', feature 'AdobePhotoShop6NewFeature' failed during request for component '{648402AE-B63B-406C-99C0-35C326ED1127}'

Any help would be greatly appreciated. Thank you.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
X304,

Your app is self repairing a HKCU key that doesn't exist for your user because you installed it as admin and then logged in as a user.

This is a normal event in this case.

Does PhotoShop run correctly after the self repair finishes? It should if your package has been done correctly.

If you don't want this to happen then you can remove all of the HKCU keys in your package and try that. Personally I would leave them in because Adobe products tend to look for them by default and may give you an error if they are not found.

The other thing to note is that if you repackage an Installshield msi then you MUST remove all traces of Installshield in order to not get errors. I would check the component table to ensure that the component isn't linked to another key that is part of Installshield as well.
Answered 07/29/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
Hello Jim, thanks for your reply. After self healing the app does run correctly but this means that the msi must be on the local machine for every user that wants to execute the application for the first time. I am a little to new at this to honestly understand what you mean by " if you repackage an Installshield msi then you MUST remove all traces of Installshield in order to not get errors. I would check the component table to ensure that the component isn't linked to another key that is part of Installshield as well " I also could not identify which of the registry keys are the HKCU keys. I am very new to this and I am just trying to survive at this point but thank you for replying.
Answered 08/01/2005 by: X304
Yellow Belt

Please log in to comment
0
After self healing the app does run correctly but this means that the msi must be on the local machine for every user that wants to execute the application for the first time.
When installing through MSI the installation will cache a local MSI file but without the file cab, which means that if the repair is repairing missing files the original MSI file must be accessable. If you install from a share and the share is accessable for the users there will be no problem.

I am a little to new at this to honestly understand what you mean by " if you repackage an Installshield msi then you MUST remove all traces of Installshield in order to not get errors.
When you run the original installation media before you repackaged it, did it say InstallShield in the dialog? In that case it's a InstallShield MSI.

I would check the component table to ensure that the component isn't linked to another key that is part of Installshield as well " I also could not identify which of the registry keys are the HKCU keys. I am very new to this and I am just trying to survive at this point but thank you for replying.
If you did repackage through WPS it usally create a component called CurrentUser and stuff the resources within this component. If the original installation media was an InstallShield you could go through this component to se what the snapshot did add regarding InstallShield.
Answered 08/02/2005 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity