You are viewing limited content. For full access, please sign in.

Question

Question

Windows Client Load Error in Azure Virtual Desktop

asked on September 22, 2022 Show version history

Note:  This problem was solved by Bruce Green, MultiMed Billing Systems, LF Wizard Extraordinaire. Hopefully this helps someone if they encounter this issue.

 

Running LF Win Client 10.4 in an AVD environment, we found that one user was unable to load the exe successfully.  All other users were unaffected.  Moreover, this started in the middle of the day - in the morning this user had no issues.  When she the clicked the icon, the client did not display itself, nor did an icon appear on the Taskbar. There was an instance of LF.exe in the process list, but it only shows 2.680K of RAM, and the instance was taking no CPU.

 

Remedy:

Turns out the LF Client had crashed, and it left temp file paths in the registry, pointing to a local copy of the user profile that was created by FSLogix at login, destroyed at logoff, and recreated under a different name at next login. Removing the temp file paths allowed LF to load properly.

See: https://learn.microsoft.com/en-us/fslogix/overview

If the above does not work, here is the initial debugging process from Ray Cruz, LF Support:

1. Are they (Azure Devops) logging the problem virtual desktop? If so, can we get those logs?
See: https://learn.microsoft.com/en-us/azure/virtual-desktop/diagnostics-log-analytics
You'll need to get the DevOps to set it up. Once that is set, reproduce the issue and let us know what you find.
2. Get a list of installed applications on the Virtual Desktop.
Step 1: Open command prompt with admin rights. That is, type in cmd either in Start menu search box or in Run dialog box and hit Ctrl + Shift +Enter to open the command prompt with admin rights. Alternatively you can also go to All Programs > Accessories and right-click on Command Prompt and select Run as administrator.
Step 2: Click continue button if you get User Account Control (UAC) Prompt.
Step 3: In the Command Prompt, type "WMIC" and hit enter. Once you type hit enter
Step 4: Next, you need to type the following command and press Enter key to execute the same.
/output:C:\Users\Public\InstallList.txt product get name,version
Where "C" is the drive letter where Windows will store the installed applications list. You can also change the name of the output file and drive letter if you want to modify the output location. Also note that this should work in Windows 2000 & XP operating systems without problems.
 

4 0

Answer

SELECTED ANSWER
replied on March 9, 2023

Regarding the issue with the Windows Client crashing when viewing PDFs, please make sure to apply Windows Client 11 Update 3 from https://support.laserfiche.com/kb/1014418/list-of-changes-for-laserfiche-windows-client-11-update-3

It contains a fix for the following:

Certain interactions between antivirus software and the Laserfiche Windows client could cause the document viewer to become unresponsive switching between multiple PDF files in a folder. This issue is now resolved. (401663)

2 0

Replies

replied on October 17, 2022

Thanks Bill!

1 0
replied on October 27, 2022 Show version history

The plot thickens...as it turns out, the client crashes are specific to situations where the user is viewing a pdf.  The pdf is downloaded into a temporary path in the user's profile, and a key is added to the registry. There are situations where the registry key is not removed. This always happens when the client crashes, and occasionally happens in what appear to be normal operations.

 

In one occurrence, the pdf was being viewed in the normal Win client display. 

 

The problem seems to be the registry key, which is not removed, and not the downloaded pdf file. When the registry key is removed the Win client will launch again.

 

Also, this is an intermittent problem, and cannot be reproduced on demand - but it seems to be happening with some frequency.

 

Update: We are submitting this to support.

1 0
replied on March 9, 2023

Following up on this...

  • Upgrading to LF 11.0 didn't help
  • New AVD servers (from a clean image) helped for about a month, then it came back
  • Redirecting temp files away from FSLogix didn't help

 

The problem went away for a month or two after replacing the AVD servers, so we closed the support ticket, but it came back. I don't mind increasing the server replacement cadence but monthly is too often. We're on LF 11.0 now, using Group Policy to set a registry key to redirect the temp files away from FSLogix to a fast SSD. We've had to fix this issue enough times that we now have a Powershell script to clear the offending registry keys and end the user's active LF.exe processes.

I think there are two problems here:

  1. The client is crashing when navigating through PDF files. It seems more likely to happen when using the previous/next document buttons to quickly move through a folder full of PDFs. At least, that's how I was able to replicate it.
  2. The client won't load again while the temporary files are referenced in the registry. If the client is going to care that the registry keys exist, it should either offer to re-open them, or silently remove them and the temp files they reference. Instead, it seems to freeze mid-launch.
0 0
SELECTED ANSWER
replied on March 9, 2023

Regarding the issue with the Windows Client crashing when viewing PDFs, please make sure to apply Windows Client 11 Update 3 from https://support.laserfiche.com/kb/1014418/list-of-changes-for-laserfiche-windows-client-11-update-3

It contains a fix for the following:

Certain interactions between antivirus software and the Laserfiche Windows client could cause the document viewer to become unresponsive switching between multiple PDF files in a folder. This issue is now resolved. (401663)

2 0
replied on March 24, 2023

Thank you!  I applied that update two weeks ago, and have only seen the issue once since then. Somehow a temp file from a week prior to the patch got back in the registry. Once that registry entry was cleared, and the file was deleted, we've been crash-free for a week and a half.

2 0
replied on April 11, 2023

It seems the issue with logging in still persists, just without the crash. First login for the day will fail to launch until the temp files are cleared from the registry. We don't know how the program was exited the previous day. This has happened twice in two weeks.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.