Error: "505: An import to the LocalDB failed" When Enabling enable LHC on XenApp 7.13

Error: "505: An import to the LocalDB failed" When Enabling enable LHC on XenApp 7.13

book

Article ID: CTX225725

calendar_today

Updated On:

Description

When disabling Connection Leasing and enabling LHC Local Host Cache feature the database does not get copied to the controllers.

The database copy starts and the file gets created in C:\Windows\ServiceProfiles\NetworkService but it gets deleted shortly.
The following error message shows up in Event Logs •505:

An import to the LocalDB failed;
Error message: “Security Identifier does not represent a Windows Account”

Resolution

  1. SID exists under Limit Visibility Section for application, So  run PowerShell Scripts to avoid going through every single Application.

  2. From Delivery Controller, open PowerShell

    Asnp Citrix* Get-BrokerApplication | select applicationname, associated usernames -This should give you a list of application names.

  3. Filter them by Application Name and Associated Usernames

  4. Find the SID from above under the Associated UserNames Column, this may appear for a few applications.

  5. From here, we’ll manually have to go to each Application that the SID is associated with and remove from the Limited Visibility section

  6. You will probably see “Show this application to the entire Delivery Group” selected here and the SID listed in the Limit Visibility part.

  7. Highlight the SID and click Remove. -Once we have removed this SID, run the command again to see if there are anymore SIDs

    Get-BrokerApplication | select applicationname, associated usernames

  8. Then enable the Local Host Cache again using Set-BrokerSite -LocalHostCacheEnabled $true -ConnectionLeasingEnabled $false

  9. Restart Config Sync Service.


Problem Cause

SID exists under Limit Visibility Section for the application.