/build/static/layout/Breadcrumb_cap_w.png

Package always self-repairs when user logs on

Here is the event log for a user who gets a self-repair for this component / feature when he logs on.

Can you tell me in "simple lay language" what should I do to my package to stop this from happening in the future for users.

I was thinking about removing the following from the package:

"C:\HUMCLogs\Hummingbird DM AutomaticUpdates-04122006_164440.log".

Do I need to do anything to the PAPIOM.dll.1187 component:

Event Log:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 20/06/2006
Time: 8:31:40 AM
User: bjfeeney
Computer: DBJFEENEY
Description:
Detection of product '{CED8616E-DE5D-4D3A-94C1-B823742DBD85}', feature 'Prime_Feature', component '{770AF87E-035D-4625-94D8-F2D97BF3C4DC}' failed. The resource 'C:\HUMCLogs\Hummingbird DM AutomaticUpdates-04122006_164440.log' does not exist.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:


*************************************************************************************************************************************************************************************************

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 20/06/2006
Time: 8:31:40 AM
User: bjfeeney
Computer: DBJFEENEY
Description:
Detection of product '{CED8616E-DE5D-4D3A-94C1-B823742DBD85}', feature 'PAPIOM.dll.1187' failed during request for component '

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:


Thanks again

0 Comments   [ + ] Show comments

Answers (5)

Posted by: sikkert 17 years ago
Orange Senior Belt
1
As for the log-file:
If it is a log-file that the system itself creates and updates, then you shouldn't have it in your package. Since it probably changes everytime the application is run, I would remove it completely from the package.
Posted by: venki_msi 17 years ago
Senior Yellow Belt
0
Repair will happen in the following cases

1) if the file PAPIOM.dll is not going to presnet in the system, when user logged, sometimes app related process starts may be beacuse of stratup entry or some run key pointing to ur app exe. whether file is present in the respective location?

2) if the component PAPIOM.dll.1187 is having COM information(i.e advertised information) then it might go for repair so in that case you have to remove COM info and include respective regsitartion info in the regsitry table.

3) whethet the app is putting any plugin to internet explorer?


Thanks,

venki.
Posted by: AngelD 17 years ago
Red Belt
0
or you could set another resource as the keypath to the "{770AF87E-035D-4625-94D8-F2D97BF3C4DC}" component
Posted by: Zeke 17 years ago
Orange Belt
0
Thanks to Sikkert.

I removed the package from Active Directory resulting in the unistall of the package from users machines.

I then re-examined the package and removed that log file and pushed it back to computers via Active Directory.

This seems to have solved the problem. A clean install without the launch of a self-repair when a user logs on.

Thanks again for all who made a comment.
Posted by: MSIMaker 17 years ago
2nd Degree Black Belt
0
Nice one sikkert....1 point for that :)

Topic Closed :)
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ