locked
Profile Container - Error 1064, Unable to find parent path of "" RRS feed

  • Question

  • Hi all

    I am trying to bring FSLogix Profile Container up and running but struggling with the issue on a Win10 Client (Build 1709) that no virtual disk is created during logon. Instead the error 1064, unable to find parent path "" is created.

    The following configuration has been made with GPO, except DirectAttachOnCreateVHD which has been created manually:

    [HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles]
    "ProfileType"=dword:00000001
    "IsDynamic"=dword:00000001
    "SizeInMBs"=dword:00007530
    "ConcurrentUserSessions"=dword:00000001
    "DeleteLocalProfileWhenVHDShouldApply"=dword:00000001
    "ReAttachIntervalSeconds"=dword:00000001
    "SetTempToLocalPath"=dword:00000003
    "ReAttachRetryCount"=dword:00000005
    "VolumeType"="VHDX"
    "Enabled"=dword:00000001
    "FlipFlopProfileDirectoryName"=dword:00000001
    "VHDLocations"="P:\\VHD"
    "DirectAttachOnCreateVHD"=dword:00000001

    Log File:

    ===============================================================================

    Log file created 2019-08-09 at 08:34:48
    UTC+01:00
    Origin: C:\Program Files\FSLogix\Apps\frxsvc.exe (Version 2.9.7117.27413)
    Windows 10.0.16299  (Windows 10 Enterprise 64-bit)
    Computer Name: [Removed from Log]    User Name: SYSTEM
    WinDir: C:\WINDOWS
    User Profile: C:\WINDOWS\system32\config\systemprofile
    Profile Version: 6
    Installed system RAM: 8189 MB  (load: 19 %)

    FSLogix Service Version 2.9.7117.27413  Status: RUNNING
    FSLogix Kernel Driver Version 2.9.7117.27413  Status: RUNNING
    FSLogix Kernel Virtualization Driver Version 2.9.7117.27413  Status: RUNNING
    ---------------------------------------------------------------
    [08:34:48.688][tid:00001b80.000004d0][INFO]           ===== Begin Session: Logon
    [08:34:48.688][tid:00001b80.000004d0][INFO]            User: S-1-5-21-3922914203-3133930492-1997048973-56482 (username)
    [08:34:48.688][tid:00001b80.000004d0][INFO]            Acquiring mutex for user logon
    [08:34:48.688][tid:00001b80.000004d0][INFO]            Configuration setting not found: SOFTWARE\FSLogix\Profiles\LogonSyncMutexTimeout.  Using default: 60000
    [08:34:48.688][tid:00001b80.000004d0][INFO]            Mutex acquired
    [08:34:48.688][tid:00001b80.000004d0][INFO]           ===== Begin Session:  LoadProfile: username
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\Enabled.  Data: 1
    [08:34:48.688][tid:00001b80.000004d0][INFO]             User: username. SID: S-1-5-21-3922914203-3133930492-1997048973-56482.
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Include group SID: S-1-5-21-30459483-1910287886-2352178642-1012
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Exclude group SID: S-1-5-21-30459483-1910287886-2352178642-1013
    [08:34:48.688][tid:00001b80.000004d0][INFO]             User is a member of the include group
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Status set to 200: Setup in progress
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\RedirectType.  Using default: 2
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\ConcurrentUserSessions.  Data: 1
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\VolumeWaitTimeMS.  Using default: 20000
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\DeleteLocalProfileWhenVHDShouldApply.  Data: 1
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\FSLogixShellPath.  Using default:
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\AccessNetworkAsComputerObject.  Using default: 0
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Accessing network as user object
    [08:34:48.688][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\AttachVHDSDDL.  Using default:
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Successfully removed Profile for S-1-5-21-3922914203-3133930492-1997048973-56482
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\ProfileType.  Data: 1
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Profile type: Read/Write
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\CCDLocations.  Using default:
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration Read (REG_SZ): SOFTWARE\FSLogix\Profiles\VHDLocations.
    [08:34:52.626][tid:00001b80.000004d0][INFO]             VHDLocations found - configured to use Local Disk
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\DiffDiskParentFolderPath.  Using default: C:\WINDOWS\TEMP\
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\NoProfileContainingFolder.  Using default: 0
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\FlipFlopProfileDirectoryName.  Data: 1
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\VHDNameMatch.  Using default: Profile*
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration Read (REG_SZ): SOFTWARE\FSLogix\Profiles\VolumeType.  Data: VHDX
    [08:34:52.626][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\VHDNamePattern.  Using default: Profile_%username%
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\DisableRegistryLocalRedirect.  Using default: 1
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\LockedRetryCount.  Using default: 12
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\LockedRetryInterval.  Using default: 5
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Profile VHD not found.  Creating new VHD.
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Configuration Read (BOOL): SOFTWARE\FSLogix\Profiles\DirectAttachOnCreateVHD.  Data: TRUE
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Overriding ProfileType and directly attaching the VHD.  This will only happen when the VHD is created.
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Status set to 1: Cannot load user's profile
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Error set to 1064
    [08:34:52.641][tid:00001b80.000004d0][ERROR:00000428]   Unable to find parent path of "" (Bei der Verarbeitung der Steuerungsanforderung ist ein Ausnahmefehler im Dienst aufgetreten.)
    [08:34:52.641][tid:00001b80.000004d0][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\PreventLoginWithFailure.  Using default: 0
    [08:34:52.641][tid:00001b80.000004d0][ERROR:00000428]   LoadProfile failed.  User: username. SID: S-1-5-21-3922914203-3133930492-1997048973-56482. (Bei der Verarbeitung der Steuerungsanforderung ist ein Ausnahmefehler im Dienst aufgetreten.)
    [08:34:52.641][tid:00001b80.000004d0][INFO]             loadProfile time: 3953 milliseconds
    [08:34:52.641][tid:00001b80.000004d0][INFO]           ===== End Session:  LoadProfile: username
    [08:34:52.641][tid:00001b80.000004d0][INFO]           ===== End Session: Logon
    [08:34:52.657][tid:00001b80.00002404][INFO]           ===== Begin Session: Profile Directory Changed: S-1-5-21-3922914203-3133930492-1997048973-56482
    [08:34:52.657][tid:00001b80.00002404][INFO]            New Profile Directory: C:\Users\username
    [08:34:52.657][tid:00001b80.00002404][INFO]            Error set to 1064
    [08:34:52.657][tid:00001b80.00002404][INFO]           ===== End Session: Profile Directory Changed: S-1-5-21-3922914203-3133930492-1997048973-56482
    [08:35:08.611][tid:00001b80.000004d0][INFO]           ===== Begin Session: StartShell
    [08:35:08.611][tid:00001b80.000004d0][INFO]            User: S-1-5-21-3922914203-3133930492-1997048973-56482 (username)
    [08:35:08.611][tid:00001b80.000004d0][INFO]            Acquiring mutex for user logon
    [08:35:08.611][tid:00001b80.000004d0][INFO]            Configuration setting not found: SOFTWARE\FSLogix\Profiles\LogonSyncMutexTimeout.  Using default: 60000
    [08:35:08.611][tid:00001b80.000004d0][INFO]            Mutex acquired
    [08:35:08.642][tid:00001b80.000004d0][INFO]           ===== Begin Session:  Logon notification: username
    [08:35:08.642][tid:00001b80.000004d0][INFO]             Session configuration read (REG_SZ): SOFTWARE\FSLogix\Profiles\Sessions\S-1-5-21-3922914203-3133930492-1997048973-56482\ActivityId = '6c9960a9-4775-0004-ff8c-996c7547d501'
    [08:35:08.642][tid:00001b80.000004d0][INFO]             Configuration Read (DWORD): SOFTWARE\FSLogix\Profiles\ConcurrentUserSessions.  Data: 1
    [08:35:08.642][tid:00001b80.000004d0][INFO]             Checking Profile Data Export for S-1-5-21-3922914203-3133930492-1997048973-56482
    [08:35:08.642][tid:00001b80.000004d0][INFO]             Error set to 1064
    [08:35:08.642][tid:00001b80.000004d0][INFO]             Not a profile we care about
    [08:35:08.642][tid:00001b80.000004d0][INFO]           ===== End Session:  Logon notification: username
    [08:35:08.658][tid:00001b80.000004d0][INFO]           ===== End Session: StartShell

    ===============================================================================

    Any ideas out there about what could be the reason and how it could be resolved?

    thanks and kr

    Friday, August 9, 2019 8:23 AM

Answers

  • Hello

    Thank you all for your support. It was not a permission issue but FSLogix could not find the path to the VHD Folder.

    The idea was to create the profile container on users homeshare for testing purposes. First try was to set the VHD Location to %homeshare%\VHD. This ended with error 1064. Then I tried P:\VHD (as P: is the mapped home drive) which also ended with error 1064. Today I have tried with \\%servername%\%username%$\VHD and this one works.

    @brbish

    Setting DirectAttachOnCreateVHD to 1 was just another try to resolve the issue because in the logfile I saw that Default is false. So do you recommend to keep this setting on default false? I couldn't find any documentation about this parameter. When should it be enabled and when disabled?

    kr

    Monday, August 12, 2019 8:37 AM

All replies

  • Hi

    I had the same error because the user had not enough rights on the vhd share to create his folder and the vhd files.

    Bruno

    Friday, August 9, 2019 9:13 AM
  • I agree with Bruno, 

    this sounds like a permissions issue to me, but unlike bruno, I would look at "access based Enumeration" this sounds like it's the more fitting culprit. 

    Friday, August 9, 2019 10:14 PM
  • Hi,

    Verify permission are set correctly: https://docs.microsoft.com/en-us/fslogix/fslogix-storage-config-ht

    If the permissions are set correctly, you may want to open support ticket and send the full logs: https://social.msdn.microsoft.com/Forums/en-US/14ea5f6f-760b-4ad2-83cf-23c3cbc1bcc4/how-to-open-an-fslogix-support-request?forum=FSLogix

    Here is the support tool so you can upload the logs during your ticket submission: https://aka.ms/fslogix_support_tool

    Friday, August 9, 2019 10:51 PM
  • Hi,

    Where did the idea of setting the DirectAttachOnCreateVHD = 1 come from? I think this might be the issue. I would try turning that off. I am checking on the details but that setting doesn't appear to be documented and I don't recall using it in the last couple of years if ever.

    Regards

    Friday, August 9, 2019 11:17 PM
  • Hello

    Thank you all for your support. It was not a permission issue but FSLogix could not find the path to the VHD Folder.

    The idea was to create the profile container on users homeshare for testing purposes. First try was to set the VHD Location to %homeshare%\VHD. This ended with error 1064. Then I tried P:\VHD (as P: is the mapped home drive) which also ended with error 1064. Today I have tried with \\%servername%\%username%$\VHD and this one works.

    @brbish

    Setting DirectAttachOnCreateVHD to 1 was just another try to resolve the issue because in the logfile I saw that Default is false. So do you recommend to keep this setting on default false? I couldn't find any documentation about this parameter. When should it be enabled and when disabled?

    kr

    Monday, August 12, 2019 8:37 AM