Skip to end of metadata
Go to start of metadata

The FSLogix Profile feature and the Office 365 Container feature set three values that represent the state of the FSLogix Profile or Office 365 Container.  These are "Status", "Reason", and "Error".  The Profile values can be viewed with the FrxTray utility.

FSLogix Profiles stores these here: HKLM\Software\FSLogix\Profiles\Sessions\<UserSID>

FSLogix Office 365 Containers stores the values in two places:

  • HKLM\Software\Policies\FSLogix\ODFC\Sessions\<UserSID>
  • HKCU\Software\FSLogix\ODFC\Sessions

If "Status" is zero, the system is in a working state and "Reason" will reflect the state.  For example, if "Status" and "Reason" are both zero, then the FSLogix Container is attached and working for this user.

Status Codes

0STATUS_SUCCESSThe system is working as expected. Check "Reason" to see the state of the Profile.
1STATUS_ERRORThe system is in an error state.
2STATUS_ERROR_VIRT_DLLThe DLL that provides the Virtual Disk API ("virtdisk.dll") cannot be found.
3STATUS_ERROR_GET_USERUnable to get the user SID from the user token.
6STATUS_ERROR_VHD_PATHThere was an error determining the path to the VHD/X file.
7STATUS_ERROR_CREATE_DIRThere was an error creating a directory.
8STATUS_ERROR_IMPERSONATIONThere was an error impersonating the user.
9STATUS_ERROR_CREATE_VHD There was an error creating the VHD/X file.
10STATUS_ERROR_CLOSE_HANDLEThere was an error closing a handle.
11STATUS_ERROR_OPEN_VHDThere was an error opening the VHD/X file.
12STATUS_ERROR_ATTACH_VHDThere was an error attaching the VHD/X.
13STATUS_ERROR_GET_PHYSICAL_PATH There was an error getting the physical path of the virtual disk.
14STATUS_ERROR_OPEN_DEVICEThere was an error opening the device.
15STATUS_ERROR_INIT_DISKThere was an error initializing the disk.
16STATUS_ERROR_GET_VOL_GUIDThere was an error retrieving the volume GUID.
17STATUS_ERROR_FORMAT_VOLThere was an error formatting the volume.
18STATUS_ERROR_GET_PROFILE_DIRUnable to determine the user's profile directory.
19STATUS_ERROR_SET_MOUNT_POINTThere was an error creating a junction in the file system.
20STATUS_ERROR_REG_IMPORTThere was an error importing registry data.
21STATUS_ERROR_CHK_GRP_MEMBERSHIPThere was an error checking group membership for the user.
22STATUS_ERROR_HANDLE_PROFILEThere was an error trying to determine the profile type.
23STATUS_ERROR_PROFILE_SUBFOLDER_REDIRECTIONThere was an error processing the redirections.xml file.
100STATUS_WAITING_FOR_PROFILE_DIR_SETThe VHD/X is attached and ready. The system is waiting for the Windows Profile Service to begin creation of the user's profile.
200STATUS_IN_PROGRESSThe FSLogix Profile system is currently working on setting up the profile.
300STATUS_ALREADY_ATTACHEDThe FSLogix Profile was already attached for the user logging on. This only happens on a machine that has been configured to allow multiple, concurrent logons for the same user.

Reason Codes

0REASON_PROFILE_ATTACHEDThe FSLogix Profile has been attached and is working.
1REASON_NOT_IN_WHITE_LISTThe user is not a member of the "FSLogix Include" group, and should therefore not receive a FSLogix Profile.
2REASON_IN_BLACK_LISTThe user is a member of the "FSLogix Exclude" group, and should therefore not receive a FSLogix Profile.
3REASON_LOCAL_PROFILE_EXISTSA local profile for the user already exists.
4PROFILE_REASON_SHORT_SIDThe FSLogix system will not handle profiles for special users.

Error Codes

Usually when the system is not working, "Error" will be set.  When it is set, it corresponds to a standard Windows Error Code.

  • No labels