FSLogix recreated new profile and create error 0x00003b01

Question

User profiles will be recreated on a Windows 2016 terminal server with FSLogix 2.9.7654.46150 and SMB if the affected user is logged on at the same time on another server. Even if the profile is free again the profile will still be recreated on the same server.

Here are the important settings:
[HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles]
"Enabled"=dword:00000001
"PreventLoginWithFailure"=dword:00000001
"ClearCacheOnLogoff"=dword:00000001
"ReAttachIntervalSeconds"=dword:0000000a
"ReAttachRetryCount"=dword:0000003c
"ConcurrentUserSessions"=dword:00000001
"SetTempToLocalPath"=dword:00000001
"SizeInMBs"=dword:000007d0
"VolumeType"="VHDX"
"RedirXMLSourceFolder"="\\fs123\fslogix$\Redirection"
"ProfileType"=dword:00000000
"LockedRetryInterval"=dword:00000005
"PreventLoginWithTempProfile"=dword:00000001
"VolumeWaitTimeMS"=dword:0000ea60
"KeepLocalDir"=dword:00000000
"DeleteLocalProfileWhenVHDShouldApply"=dword:00000001
"LockedRetryCount"=dword:0000000c
"HealthyProvidersRequiredForRegister"=dword:00000001
"ClearCacheOnForcedUnregister"=dword:00000001
"CCDLocations"="type=smb,connectionString=\\fs123\fslogix$;type=smb,connectionString=\\fs234\fslogix$"
"FoldersToRemove"=hex(7):00,00

Here is the log:
[11:12:50.419][tid:00000918.000022a0][INFO] Status set to 1: Cannot load user's profile
[11:12:50.419][tid:00000918.000022a0][INFO] ===== End Session: LoadProfile: usr12345
[11:12:50.419][tid:00000918.000022a0][ERROR:00000428] error.cpp(13): [WCODE: 0x00003b01] (Bei der Verarbeitung der Steuerungsanforderung ist ein Ausnahmefehler im Dienst aufgetreten.)
[11:12:50.419][tid:00000918.000022a0][INFO] ===== End Session: Logon
[11:12:50.450][tid:00000918.0000259c][INFO] ===== Begin Session: Profile Directory Changed: SID123456
[11:12:50.450][tid:00000918.0000259c][INFO] New Profile Directory: C:\Users\usr12345
[11:12:50.450][tid:00000918.0000259c][INFO] ===== End Session: Profile Directory Changed: SID123456
[11:12:56.610][tid:00000918.000022a0][INFO] ===== Begin Session: StartShell
[11:12:56.610][tid:00000918.000022a0][INFO] User: SID123456 (usr12345)
[11:12:56.610][tid:00000918.000022a0][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\LogonSyncMutexTimeout. Using default: 60000
[11:12:56.610][tid:00000918.000022a0][INFO] Acquired start shell lock for user SID123456 (Elapsed time: 0)
[11:12:56.610][tid:00000918.000022a0][INFO] Session configuration read (REG_SZ): SOFTWARE\Policies\FSLogix\ODFC\Sessions\SID123456\ActivityId = 'ae9db6ca-1d42-416a-896c-0e0cdbdea055'
[11:12:56.610][tid:00000918.000022a0][INFO] Session configuration wrote (DWORD): SOFTWARE\FSLogix\Profiles\Sessions\SID123456\LogonStage = '1'
[11:12:56.626][tid:00000918.000022a0][INFO] ===== Begin Session: Logon notification: usr12345
[11:12:56.626][tid:00000918.000022a0][INFO] Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\Enabled. Data: 1
[11:12:56.626][tid:00000918.000022a0][INFO] Checking Profile Data Export for SID123456
[11:12:56.626][tid:00000918.000022a0][WARN: 00000000] User session for SID123456 has an unexpected status. STATUS = 200
[11:12:56.626][tid:00000918.000022a0][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\FSLogixShellPath. Using default:
[11:12:56.626][tid:00000918.000022a0][INFO] Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\PreventLoginWithFailure. Data: 0
[11:12:56.626][tid:00000918.000022a0][INFO] ===== End Session: Logon notification: usr12345
[11:12:56.641][tid:00000918.000022a0][INFO] Session configuration wrote (DWORD): SOFTWARE\FSLogix\Profiles\Sessions\SID123456\LogonStage = '4'
[11:12:56.641][tid:00000918.000022a0][INFO] ===== End Session: StartShell

Downgrade to older FSLogix Apps release 2004 (2.9.7349.30108) fixes this bug. Is this problem being worked on?

Another problem: If the profile disc becomes nearly full, the user can usually no longer logged off himself from the server. The deregistration hangs.

Answer 1

Hello @Hoffmann Werner ,

1.We noticed that you set the "ConcurrentUserSessions"=dword:00000001, while "ProfileType"=dword:00000000
NOTE: All sessions trying to use the VHD concurrently must have a ProfileType of 1, 2, or 3. If the VHD isn't accessed concurrently, ProfileType should be 0.
Profile Container registry configuration reference: https://learn.microsoft.com/en-us/fslogix/profile-container-configuration-reference
Configure Profile Container and Office for concurrent connections and multiple connections: https://learn.microsoft.com/en-us/fslogix/configure-concurrent-multiple-connections-ht

2.There's also a known issue that CCDLocations and ProfileType=3 will cause RW vhd(x) can’t be merged without an exclusive lock if RW machine is signed out first.
Our product group has solved this issue and the fix will be released in the next version of FSLogix due May/ June 2021. For now, we suggest you to use VHDLocations and ProfileType=3 first, as it is more stable. Please wait for the release of new FSLogix, thank you.

3.Other references:
Do you use Microsoft Teams? https://james-rankin.com/articles/quickpost-how-to-stop-fslogix-profile-containers-bloating-when-running-microsoft-teams/
USING THE SAME FSLOGIX PROFILE CONTAINER AT THE SAME TIME ON DIFFERENT MACHINES: https://blog.prianto.com/2016/09/using-the-same-fslogix-profile-container-at-the-same-time-on-different-machines/

Best regards,
Leila

---

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hello Leila,

thank you very much for the answer. We will wait for the new update and then switch to Profile Type 3.

Best regards,
Werner

Answer 3

"FoldersToRemove"=hex(7):00,00

What does this do?