App installs though just installed..?

[rgouette]

Hate to sound dumb, but here's the scenario:
1) repackaged applicationX to MSI
2) install app as admin user
3) launch applicationX as normal(lockdown) user, and the application seems to re-install as if doing a self-healing operation?!

Any ideas?
O/S = Windows 2000 SP-2
Installshield 10.50 SP-1
MSI = 2.0

Thanks,
Rich

[Pugster]

Check out the application event log using Event Viewer, this will tell you what feature/component is being reinstalled.

[rgouette]

The following is in the App evt log:

Product: _install -- Error 1931.The Windows Installer service cannot update the system file C:\WINNT\system32\catsrv.dll because the file is protected by Windows. You may need to update your operating system for this program to work correctly. Package version: 2000.2.3511.0, OS Protected version: 2000.2.3504.0



This, along with several other files actually......(system files)

[Christopher_Pai]

You probably have a component with a keyfile thats part of the users profile ( HKEY_CURRENT_USER or Docs and Settings ) When MSI installs as Admin it sets up the profile for that user but when another user logs on its missing so it "repairs" it. MS Office installs do the same thing.

Be sure to check my blog and read my repackaging rant. Repackaging isn't ( in my not so humble opinion ) point-n-click wizardry.

[Pugster]

Catsrv.dll looks like a file thats protected as part of Windows File Protection, are you sure that when you took the original snapshot it was on one of your company standard PC's fully patched and up to date with the latest service packs ?
I would imagine you can probably remove the file from your application as it is most likely to be already on your company PC's
As Chris kindly pointed out, you might also take a look at which component it is in and check whether its a user related component if you really think you still need it.

[rgouette]

thanks much: I'll look into it!
Rich