Applies to: Nerdio for Azure WVD (NFA) Professional and Enterprise users only.
When encountering an FSLogix profile mounting error such as the one below, you can review the cause of this error by reviewing the event logs on the host that was displayed in the error message via the Event Viewer on that host, or by accessing the text logs via UNC.
Here's those steps to access the event logs from a central location, FS01. This is a great approach when assessing this as by default the user's FSLogix profile containers are stored on FS01 (\\FS01\Profiles).
Login to FS01 as a Domain Admin, if you do not have Domain Admin permissions, please see our guide HERE on granting those.
Open Event Viewer on FS01 and connect to the host remotely by the host's IP address (Can be found in the NAP). You can do this by right-clicking the current Event Viewer (local) option and clicking "Connect to Another Computer":
Review the Operational events under Applications and Service Logs>FSlogix Apps>Operational. You may see several errors for a particular user login, but most often you'll find event ID 26 with details regarding the failure to load the profile. In this case below you can see that the "Test" user's profile failed to open due to the file being used by another process:
Open Computer Management on FS01 and review open sessions and open files, you may need to close any open profile containers (VHD/VHDX files) and/or sessions for the user in question. In this case we find that Test user's session is still open, which is likely a stale session based on this connection time. Logging this user off the host displayed here corrected this and the user was able to login:
- You can also access the FSLogix text logs: browse to \\Pool-n00000#\c$\ProgramData\FSLogix\Logs\Profile\ and open the profile*.log files. See FSLogix logging documentation for more information