I installed a native MSI file. I ran this command

msiexec /I "\\Server\Share\Calendar\Oracle Calendar 9.0.4.msi" /QB!

It installs fine and it works fine. But, if any user who is "not" an Admin of the local box starts up Oracle Calendar from the Start Menu they see that MSI Install Window pop up as if the software was installing for the first time. And they see this every time they run the app.

Is there any PROPERTY I can pass to my MSI command line that will prevent this from happening? I have even tried this:

msiexec /I "\\Server\Share\Calendar\Oracle Calendar 9.0.4.msi" REINSTALLMODE=omus REINSTALL=ALL ALLUSERS=1 REBOOT=R /QB!

and it still does this.

I feel this is flat out dumb for a native installer to do this.

Any ideas?
Thank you.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I may be out to lunch, but is that not because of the self-healing? Have you tried opening the MSI and checking to see if there are any HKEY_CURRENT_USERS registry entries... and if there are, can you get rid of them and still have it work?

So, it only happens when a user logs on that a) hasn't logged onto that box before and b) is NOT an admin? What if a new admin user logs on, it's fine then?
Answered 09/20/2006 by: SutherlandAndrew
Senior Yellow Belt

Please log in to comment
Hi. If a new user logs in who is an admin it works fine. It is only when a non admin user starts the app. And I ran a native MSI so I never did an edit of it.

But, if you look in event veiwer you will see what components are failing and then you can fix it within the MSI.
Answered 09/20/2006 by: mhsl808
Fifth Degree Brown Belt

Please log in to comment
Check to see if that failed component's keypath is a registry value. There may be a permissions issue in the registry to where this value is trying to be written to.
Answered 09/20/2006 by: danr29
Purple Belt

Please log in to comment
Do you have a component with %UserProfile% files with a keypath of a file instead of a HKCU registry? This is one possibility that would give you this issue.
Answered 09/20/2006 by: AngelD
Red Belt

Please log in to comment
The reason why it is being repaired will be in the event viewer.
On a user account after it has repaired, go to Control Panel->Administrative Tools->Event Viewer->Application

You will have a few MSI events grouped together with the source being MsiInstaller. One will have more information than the others
What does it say there?

Answered 09/21/2006 by: looeee
Senior Yellow Belt

Please log in to comment