Jump to content
Welcome to our new Citrix community!
  • 0

User layer error


Michael Quinonez

Question

24 answers to this question

Recommended Posts

  • 0

I do know that you're not allowed to change the 8.3 setting that is in the OS layer.  Basically, all the layers including Elastic and User layers need to have exactly the same 8.3 setting, and the layers all inherit it from the OS layer.  But if there's a GPO which applies to the published image, that is setting it to something other than what it is in the OS layer, that could cause a problem.  But I'm not sure where exactly you're seeing the error, so I don't know who's complaining about the setting.  Can you paste in a screen shot of the error?  And I suggest opening a Support Case so we can gather more information and logs.

Link to comment
  • 0

I have ran a few diff scenarios since the update. When I delete my profile from the storage it does comes up with the error short name settings may not be changed on this volume due to the global registry setting it creates the new profile.

 

When I put my profile back since before the ELM console update. I Get no error.

 

 

file path.PNG

short.PNG

Link to comment
  • 0

I opened the ticket. Waiting for Citrix response. They could not find any issues at first level troubleshooting as everything is setup as per their instructions. Below are the events I get on my VDAs

 

Log Name:      Application
Source:        Citrix Layering Service
Date:          4/11/2020 12:11:33 PM
Event ID:      1310
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Description:
Could not find file \\****\CitrixUserData\UPL\SWIFTVDI\ShareAssignments.json

Log Name:      Application
Source:        Citrix Layering Service
Date:          4/11/2020 12:11:33 PM
Event ID:      1310
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Description:
Could not find file \\****\CitrixUserData\UPL\SWIFTVDI\Shares.json

Log Name:      Application
Source:        Citrix Layering Service
Date:          4/11/2020 12:11:34 PM
Event ID:      1310
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Description:
Unable to load the User Layer for user josephg during login, using temporary non-persistent user layer

Log Name:      Application
Source:        Citrix Layering Service
Date:          4/11/2020 12:11:34 PM
Event ID:      1310
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Description:
Could not find file \\****\CitrixUserData\UPL\SWIFTVDI\ElasticLayerAssignments.json

Log Name:      Application
Source:        Citrix Layering Service
Date:          4/11/2020 12:11:34 PM
Event ID:      1310
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Description:
Could not find file \\****\CitrixUserData\UPL\SWIFTVDI\Layers.json

Log Name:      Application
Source:        Citrix Layering Service
Date:          4/11/2020 12:12:04 PM
Event ID:      1310
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Error encountered while elastically attaching assigned layers.  No layers have been attached.

Log Name:      Application
Source:        Citrix Layering Service
Date:          4/11/2020 12:12:24 PM
Event ID:      1310
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Description:
User josephg logged in successfully.  No elastic layers were attached.

Link to comment
  • 0

As per the theory, it is the correct path to look for json file. However the json file is not there or not created. This is my first testing of user personalization layer. We were in 7.15 LTSR and we migrated to 1912 LTSR and started to test this feature (which is like a replacement for PVD). Not sure how the json file creation happens and looks like it's failing at this part. 

Link to comment
  • 0

You're right i don't know what i was thinking this is UPL not user layers.  I have not actually tried UPL before but i doubt there are json files those are probably not real errors.

 

Are you getting user layers in the share though?

 

It could be a permission issue, normally you set up the share like you would for home directories.  As a test you could try allowing everyone full control.  Also i know the "NT AUTHORITY\SYSTEM" account needs full control starting at the root of the share.

Link to comment
  • 0

Yes, I do get the user layers in the share. but it is not getting mapped. I gave the full permission to the user share and still not working.

 

Yes, this is a new feature and trying for the first time. 

 

Further testing and logging found the below errors

 

2020-04-13 11:46:33,636 INFO 24 UserLayerCreationService: Format disk with label 'UserLayerVolume' using allocation size 512
2020-04-13 11:46:36,433 INFO 24 UserLayerCreationService: Format disk completed, label 'UserLayerVolume'
2020-04-13 11:46:36,464 ERROR 24 NativeMethodLogger: Failed to disable short names on volume \\?\Volume{bd8a4184-0000-0000-007e-000000000000}\: Error code 304
2020-04-13 11:46:36,464 WARN 24 BaseTransaction: Transaction 'Attach Disk' is being implicitly rolled back
2020-04-13 11:46:36,464 INFO 24 VirtualDisk: Removing volume cache entry '\\?\Volume{bd8a4184-0000-0000-007e-000000000000}\'
2020-04-13 11:46:36,605 ERROR 24 VdiDynamicLayeringService: Caught exception: 'System.ComponentModel.Win32Exception (0x80004005): Short name settings may not be changed on this volume due to the global registry setting
   at Unidesk.Guest.Core.Services.NativeMethodLogger.LogWin32ErrorAndThrow(Int32 errorCode, String format, Object[] args)
   at Unidesk.Guest.Core.Services.VolumeService.EnableShortFileNames(String volumePath, Boolean shouldEnable)
   at Unidesk.Guest.LayeringService.Services.UserLayerCreationService.CreateUserLayerAt(IWindowsId userId, String filename, UInt64 sizeInBytes)
   at Unidesk.Guest.LayeringService.Services.UserLayerService.EnsureUserLayerDiskExists(IWindowsId windowsId)
   at Unidesk.Guest.LayeringService.Services.UserLayerAttachDetachService.OpenUserDiskVdi(IWindowsId windowsId, Boolean& newUserLayerCreated)
   at Unidesk.Guest.LayeringService.Services.UserLayerAttachDetachService.OpenAttachUserDiskVdi(IWindowsId windowsId)
   at Unidesk.Guest.LayeringService.Services.VdiDynamicLayeringService.AttachUepDisk(IWindowsId windowsId)' trying to attach a User Layer
2020-04-13 11:46:36,605 WARN 24 UserLayerAttachDetachService: Unable to load the User Layer for user ****\josephg during login, using temporary non-persistent user layer

Link to comment
  • 0

Issue fixed as per the findings and solution

 

From : %localappdata%

2020-04-14 09:39:54,982 INFO 1 App: *** Unidesk LayerInfo 19.11.0.19243 has started. ***

2020-04-14 09:39:57,951 INFO 1 Commands: Running command 'completelogon' ()

2020-04-14 09:39:58,701 ERROR 1 ResultBaseInterceptor: Error returned from Unidesk.Guest.Core.Remote.Interfaces.IRemoteLayeringService.QueryLogonStatus

2020-04-14 09:39:58,716 ERROR 1 ResultBaseInterceptor: Error message: <value missing>

2020-04-14 09:39:58,716 ERROR 1 ResultBaseInterceptor: Error details: Short name settings may not be changed on this volume due to the global registry setting

2020-04-14 09:40:30,998 INFO 1 RefreshShellService: Waiting for Shell

2020-04-14 09:40:31,045 INFO 1 RefreshShellService: Done waiting for Shell

 

From: C:\programdata

2020-04-14 09:39:06,873 INFO 8 UserLayerCreationService: Format disk completed, label 'UserLayerVolume'

2020-04-14 09:39:06,888 ERROR 8 NativeMethodLogger: Failed to disable short names on volume \\?\Volume{d79bada0-0000-0000-007e-000000000000}\: Error code 304

2020-04-14 09:39:06,888 WARN 8 BaseTransaction: Transaction 'Attach Disk' is being implicitly rolled back

2020-04-14 09:39:06,888 INFO 8 VirtualDisk: Removing volume cache entry '\\?\Volume{d79bada0-0000-0000-007e-000000000000}\'

2020-04-14 09:39:07,060 ERROR 8 VdiDynamicLayeringService: Caught exception: 'System.ComponentModel.Win32Exception (0x80004005): Short name settings may not be changed on this volume due to the global registry setting

   at Unidesk.Guest.Core.Services.NativeMethodLogger.LogWin32ErrorAndThrow(Int32 errorCode, String format, Object[] args)

   at Unidesk.Guest.Core.Services.VolumeService.EnableShortFileNames(String volumePath, Boolean shouldEnable)

   at Unidesk.Guest.LayeringService.Services.UserLayerCreationService.CreateUserLayerAt(IWindowsId userId, String filename, UInt64 sizeInBytes)

   at Unidesk.Guest.LayeringService.Services.UserLayerService.EnsureUserLayerDiskExists(IWindowsId windowsId)

   at Unidesk.Guest.LayeringService.Services.UserLayerAttachDetachService.OpenUserDiskVdi(IWindowsId windowsId, Boolean& newUserLayerCreated)

   at Unidesk.Guest.LayeringService.Services.UserLayerAttachDetachService.OpenAttachUserDiskVdi(IWindowsId windowsId)

   at Unidesk.Guest.LayeringService.Services.VdiDynamicLayeringService.AttachUepDisk(IWindowsId windowsId)' trying to attach a User Layer

2020-04-14 09:39:07,060 WARN 8 UserLayerAttachDetachService: Unable to load the User Layer for user ****\josephg during login, using temporary non-persistent user layer

2020-04-14 09:39:07,076 INFO 8 UniRsdConfigurationService: Configuring unirsd

2020-04-14 09:39:07,091 INFO 8 UnifltrConfigurationService: No User Layer label, configuring unifltr and unikcdrv for a default, nonpersistent UEP

2020-04-14 09:39:07,091 INFO 8 CompositingManager: Beginning compositing app layers: user ****\josephg (S-1-5-***-42344331-*******)

2020-04-14 09:39:07,091 INFO 8 WindowsId: Impersonating ****\josephg

 

Solution applied

1. Disable 8dot3 name creation on all volumes (https://support.microsoft.com/en-gb/help/121007/how-to-disable-8-3-file-name-creation-on-ntfs-partitions)

2. Even though security settings were applied as per the documentation to the data share path, it did not work. I have added the permission for the computer account to the share to have modify permission.

Link to comment
  • 0

Ok it seems this is a complicated issue.  If you have that setting set to be per volume then we try to set it so it will not be disabled.  BUt evidently we will still work if it is disabled.  The engineers are wondering if we cant see the mode properly for some reason.  By setting it to 1 you are making the setting per machine and not per volume so I think we not longer try to change it so it works.  My guess is that setting it to 0 should also work.

Link to comment
  • 0

I am having the same issue.  

 

Citrix Cloud

VDA 2112

User Personalization Layer enabled

The share setup is WIDE OPEN

 

I get these in the event logs on the VDAs:  

The specified share does not exist:

Could not find file ShareAssignments.json (<---I got this once one 1 VDA)

 

I tried setting the 8.3 to DWORD = 1 based on what was tried here:  https://discussions.citrix.com/topic/397895-user-layer-error/page/3/

 

Any thoughts ?

 

Link to comment
  • 0

Hello.

I have the same strange issue.

We use just the User Profile Layer with GPO in CVAD (no app layering)

2 environments. Pre-Prod and Prod with the same golden image, same setup. The only thing different is the share path so I suspect something has changed regarding the file share.

In Pre-Prod is not working.

In Prod is working fine.

After changing the registry on the golden image in Pre-Prod: HKLM\System\CurrentControlSet\Control\Filesystem\NtfsDisable8dot3NameCreation DWORD 1, it's working as well in Pre-Prod.

Before it was set to DWORD 2.

Would be interesting to know exactly what changed. In case I find out, I come back with a feedback

Link to comment
  • 0

It seems after CVAD 2203 CU2 the issue is not there anymore, could anyone confirm?

Also for us, changing the above value to 1, was also damaging the AppV applications, that we found out only later. AppV apps were not syncing anymore.

Now with update of CVAD components to CU2 the newly created disk is mounted even if the 8dot3 settings is set to 2 in the registry, so all back to normal it seems.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...