MicrosoftI installed this version hoping it would solve some of the APPX issues we are having. It became immediately apparent that logoff's are no longer 100% successful. We have only about 5 users on our test server, and 3 of them experienced a logoff issue. The log shows the following sequence of events (which don't give us a lot of info to go on):
[11:22:44.584][tid:00001120.00003d50][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\ControlTileService. Using default: 0
[11:22:44.611][tid:00001120.00003d50][INFO] Status set to 1: Cannot load user's profile
[11:22:44.611][tid:00001120.00003d50][INFO] ErrorCode set to 1064 - Message: An exception occurred in the service when handling the control request.
[11:22:44.611][tid:00001120.00003d50][ERROR:00000428] invalid map<K, T> key (An exception occurred in the service when handling the control request.)
[11:22:44.613][tid:00001120.00003d50][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\ShutdownOnUserLogoff. Using default: 0
[11:22:44.613][tid:00001120.00003d50][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\RebootOnUserLogoff. Using default: 0
[11:22:44.613][tid:00001120.00003d50][INFO] Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\ProfileType. Data: 0
[11:22:44.613][tid:00001120.00003d50][ERROR:00000428] UnloadProfile failed. Version: 3.25.202.4223. User: XXXXXXXX. SID: S-1-5-21-XXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXX. SessionId: 20. FrxStatus: 1064 (An exception occurred in the service when handling the control request.)
[11:22:44.613][tid:00001120.00003d50][INFO] unloadProfile time: 367 milliseconds
The profile disk is left connected, and the user is unable to access the profile disk on subsequent logins because it is "in use". The situation requires and administrator to dismount the disk, which allows it to be used on the next login.
Noting that this did not happen to every test user, but it did happen to 60% of our test users.
Reverting to 2.9.8884.27471 resolved the issue for us.
We are also having this issue after updating to this version.
Along with the Invalid map(K, T) error in the logfile we are also seeing error "Get token groups (Er is geprobeerd te verwijzen naar een token dat niet bestaat.)" with Event ID 26 in the event log.
When testing i noticed that when i made a new profile disk for a user with the issue the problem didnt happen for that user anymore.
I found a workaround by enabling cleanup invalid sessions, which doesnt fix the issue but a few seconds after the logoff it dismounts the disk anyways.
We have also seen this EventID 26. It seems to happen when a disconnected user is being forced logged out, or when the time setting expires and the user is bening logged out by the system. It reports "Disk was compacted : false
Until now we have not received any issues reported by users.
Observing the same issue for some of the test users. With "CleanupInvalidSessions" set to "1" the excluded content (local_%username%) isn't cleaned up.
Jason_Parker: Any official information on this one?
Just noting that I'm seeing the same behavior. The users that get the profile unload issue leave behind their profile folder. The log entry states ERROR:00000091 Failed to remove the original profile folder: C:\Users\<USER> (The directory is not empty).
I reviewed the folder and they are mostly empty. The few folders that exist are C:\Users\<User>\AppData\Local\Microsoft\Credentials and C:\Users\<User>\AppData\Roaming\Microsoft\Credentials. Both of these folders are empty.
I agree that the "cleanup invalid sessions" option helps. We have never needed this option in the past. Enabling this new option does seem to resolve the immediate problem but does not address the root issue. The cryptic "Invalid map(K, T)" error needs to be explained by FSLogix.
My biggest concern here is that the FSLogix group pushes this thought that "Customers are required to run the latest version" (in principle); yet, the FSLogix group is completely silent when legitimate issues are encountered.
There should be a public acknowledgement of the issue and an explanation as to what it means and what (if anything) can/should be done. Instead we just have this glowing announcement that this new version is great and everyone should upgrade. Hate to be critical here but I don't think this situation is good.
Has there been any progress on this issue?
