we have lately experienced an odd issue regarding user config file and an auto-repair function.
The scenario is as following:
We install an application on a user target station, which has a single or multiple files, that are going to be installed to a user roaming profile via auto-repair the first time the user runs it. In our case it's just a single file (license.xml) that goes to "c:\Users\*username*\AppData\Roaming\*appname*\license.xml". We have multiple users running the station, so User A runs the app for the first time and auto-repair determines missing license.xml, puts it in the User A profile and the app starts normally. So far so good. Then he exits the app, logs out and User B comes and runs the same app for his first time. Auto-repair runs again and puts the file in place, as expected. As long as any of those users remain logged on, the app works just fine, they can close it and run it again - auto-repair doesn't trigger the second time.
But then User B logs out, User A comes back and runs the app - he already has his license.xml file in the right place but the advertised shortcut triggers auto-repair again for no obvious reason. I checked the msi installer log in the user profile for more information and it states license.xml has an unknown state, all other files have state Local which is fine. I also tried to google more information about MSI installer client state for components, but couldn't fine any valuable information:
MSI (s) (60:B8) [17:54:03:730]: Component: license.xml; Installed: Local; Request: Local; Action: Local; Client State: Unknown
So User A gets the app "repaired" and he can continue working, he can close it and run again whenever he wants until he logs out. When User B comes back he gets auto-repair triggered the same way as User A with license.xml being unknown client state.
Attributes on the file are in order, it isn't hidden or anything else. In the application AI project everything also appears to be fine, without any modifications to the file component. But we also tried various component attributes, such as 'Shared amongst packages', 'Transitive', etc. with no luck.
This isn't the only application that we have troubles with, lately we run around 10 applications and more keep coming, sharing the same issue. We thought it might be a bug with AI, because we didn't notice this behavior before.
Please help
Regards,
Tom
FOLLOW US
Get the latest news in Application Packaging