ClientAutomation & Windows 11 22H2

replied on December 15, 2023

Hi Joseph,

If the same ClientAutomation code works with the same version of the Laserfiche Windows Client in Windows 10 and/or pre-22H2 Windows 11 and/or Windows Server OSes in the same environment, that's suspicious and I'd recommend opening a support case. If you haven't checked those cases yet, do that first.

While Windows version/update related issues can and do occur with Laserfiche software in general, they are relatively rare and low on the probability list of root causes for a given issue. Was this ClientAutomation code in active usage prior to a Win11 22H2 update rollout after which it stopped working on all systems that received the update (or similar)?

If you can, it may also help to share the portion of the code that's failing to work as expected (get/detect client instances).

0 0

replied on December 18, 2023

Sam,

Per support, here is the code. Support also requested credentials, but I am testing against my self-hosted system, so I am not sure why I have to provide that. The tracing files that Support requested has been uploaded to the case (236055).

Joe

            using (ClientManager clientManager = new ClientManager())
            {
                if (clientManager.IsClientOpen())
                {
                    Console.Write("The Laserfiche client is open.");
                    Console.ReadKey();
                }
                else
                {
                    Console.Write("The Laserfiche client is closed.");
                    Console.ReadKey();
                }
            }

1 0

replied on January 8, 2024

Sam,

I did a clean reinstall of Lf Windows Client and 10.4 SDK Runtime and that resolved the issue. I am not sure if a Windows Update caused this issue, but I wanted to pass it along. Thank you!

3 0

replied on January 8, 2024

Glad to hear it's working now! Thanks for returning to provide the update.

0 0

Question

Question

ClientAutomation & Windows 11 22H2

Replies

Sign in to reply to this post.