This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This is the third time it happens.
It works flawlessly for a whole week and then it just throws this error and then a bunch of errors follows:
It looks like the error.cpp(13) triggers those "WTSQueryUserToken" and "openVirtualDisk" errors.
OpenVirtualDisk also behaves quite oddly: at first it says "file not found" and then changes to "Filetype not spported".
Is there a way to see what file are those errors referring to??
this persists until i restart the rds.
I have 2 rds with the same exact config, last week the same exact thing happened on both (with +-1 hour of difference), this time the other server stayed clean and didn't throw any error.
I have no idea where to look for!
edit
a downgrade to FsLogix 2004 (2.9.7349.30108) fixed the whole thing.
Hello @GianlucaMelis-0017,
I don't think that I can be of much help here (I have no experience of FsLogix), but I just wanted to mention a few small points.
The error code in the "error.cpp(13)" message is 0x3B01 = ERROR_MUI_FILE_NOT_LOADED with error message text "The resource loader cache doesn't have loaded MUI entry." so the subsequent text (Bei der Verarbeitung des Steuerungsanforderung ist ein Ausnahmefehler im Dienst aufgetreten) is not a description of error 0x3B01 but rather just a report that some type of error has occurred.
Secondly, the time delay between this error and the WTSQueryUserToken/OpenVirtualDisk errors is so large (more than 3 hours) to cast substantial doubt about whether there is a causal link...
Gary
general knowledge is always helpful! I thank you a lot for that..
I would have thought the same seeing the 3 hours delay and the error not being related but this exact scenario repeated itself 3 times already almost exactly.
this log is from the second time it happend:
(the yellow marks is when i restarted the service manually after applying some minor changes)
Hello @GianlucaMelis-0017,
Have you checked whether there is a de-DE directory in the directory containing FsLogix and whether the de-DE directory contains a .mui for FsLogix?
Tracking down and attempting to resolve the ERROR_MUI_FILE_NOT_LOADED problem might be a "wild goose chase" (a foolish and hopeless search for or pursuit of something unattainable), but if you have got no other leads...
Gary
@Gary Nebbett
If you mean under c:\programFiles\FsLogix\apps then no..
there is no .mui language file there to be found.
It could really be that this cpp error is purely related to some language issues and has nothing to do with the following "WTSQueryUserToken" and "OpenVirtualDisk" errors.
Actually, when googling it in combination with FsLogix, the few results I've found were also showing logs with errors in German language.
So yeah, this doesn't solve the initial problem but at least it seems like i should not focus too much on it.
Thanks again, Gary!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 18%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELK%3C/text%3E%3C/svg%3E)
Hello @GianlucaMelis-0017 ,
Thanks for all your effort. Will the issue be fixed if you downgrade to FSLogix 2004 (2.9.7349.30108)?
@Leila Kong
Well.. I can try downgrading to 2004 and see what happens.
I rather prefer not to tho, especially due to the "CleanupInvalidSessions" function which has been quite helpful and only compatible with 2009.
Btw i had this cpp error yesterday aswell without WTSQueryUserToken or OpenVirtualDisk errors following. So what @Gary Nebbett has supposed may be true. I am also starting to think that cpp13 has nothing to do with login errors but with some sort of language files missing (probably caused by using the system in German language).
I Think i will open a new thread focusing more on those errors.
I will Answer to this thread again after installing version 2004
well wow.. 2004 automagically fixed everything.. I have changed 0 settings! just uninstall 2009 -> restart -> install 2004 -> restart -> Success!
I have Backed up my FsLogix Registry Hive but it wasn't necessary as all the settings were not deleted after uninstalling.
Still i would like to have a working 2009 because of the Profile Cleanup gpo which is kinda nice to have, but for now i'm pretty happy with 2004!
Hello @GianlucaMelis-0017 ,
Did you change any settings before the error occurred? Do you use cloud cache?
What’s the version of your fslogix? Did you configure profile container? Where did you put the vhd?
Did you use Onedrive?
Hope the below articles may give you any help:
https://learn.microsoft.com/en-us/answers/questions/202415/frxsvc-service-transaction-timeouts.html
https://learn.microsoft.com/en-us/answers/questions/259063/fslogixs-crash-errorcpp13-high-availability-filese.html
https://www.meinekleinefarm.net/caution-fslogix-2009-2-9-7621-30127-profiles-wont-logoff-completely/
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.
@Leila Kong Thanks a lot for answering!
Did you change any settings before the error occurred?
no. the error shows up since the first log.
Do you use cloud cache?
no
What’s the version of your fslogix?
Latest: FSLogix Apps 2009 HF_01 (2.9.7654.46150)
Did you configure profile container?
yes (office365+FSL profile container).
Where did you put the vhd?
The vhdx are hosted on a refs formatted raid 10 ssd drive on a dedicated file server (ws2019). the files are accessible via standard smb share and on a 10gb network
Did you use Onedrive?
no (maybe in the future)
now about the links you sent;
these are the installed updates:
Description HotFixID InstalledBy InstalledOn
-----------
-------- ----------- -----------
Update KB4601055 NT-AUTORITÄT\SYSTEM 24.03.2021 00:00:00
Update KB4486153 RDS22\Administrator 24.03.2021 00:00:00
Security Update KB4512577 07.09.2019 00:00:00
Security Update KB4535680 NT-AUTORITÄT\SYSTEM 02.03.2021 00:00:00
Update KB4577586 RDS22\Administrator 03.03.2021 00:00:00
Security Update KB4580325 NT-AUTORITÄT\SYSTEM 02.03.2021 00:00:00
Security Update KB4587735 NT-AUTORITÄT\SYSTEM 30.11.2020 00:00:00
Security Update KB4601393 NT-AUTORITÄT\SYSTEM 02.03.2021 00:00:00
Security Update KB5000859 NT-AUTORITÄT\SYSTEM 24.03.2021 00:00:00
Security Update KB5000822 NT-AUTORITÄT\SYSTEM 24.03.2021 00:00:00
this link https://learn.microsoft.com/en-us/answers/questions/259063/fslogixs-crash-errorcpp13-high-availability-filese.html does not apply to my case.
this one https://www.meinekleinefarm.net/caution-fslogix-2009-2-9-7621-30127-profiles-wont-logoff-completely/ was my first attempt fixing it. I had those groups set locally and i set them via gpo after reading it. it was working fine until last week..
what is even the error.cpp(13) referring to? I cant seem to find it in any documentation.
I am also willing to provide logs or any more information if needed.