Question

Desktop 12, Template with dynamic fields becomes unresposive

Version 12 Administration Self-Hosted

Updated June 9

asked on May 20 • Show version history

Hello,

We have an peculiar issue with Laserfiche 12 desktop client (does not appear to affect web client). When selecting a dropdown field, which is the parent of another dynamic field, the client greys out and becomes unresponsive. It only appears to affect one template (we have several that use dynamic fields, all using this same externalTables SQL connection). If I let it sit long enough I get an error "Error" The underlying connection was closed: An unexpected error occurred on a send." I'm not 100% certain that error message is related, as I only saw it happen the one time and had several apps open. We don't see this in the Test repository.

Has anyone else encountered this?

0 0

Answer

APPROVED ANSWER

replied on June 9

A hotfix is available to resolve this issue. Please contact LF Support and reference Bug 594641 and ask for the hotfix if you do not have it yet.

0 0

View 2 previous replies

replied on June 9

The hotfix supplied did not fix our issue. While it no longer caused the application to become unresponsive, it no longer gave a drop-down list of options to choose from.

0 0

replied on June 9

We just applied to hotfix to ours, and so far everything looks good.

0 0

replied on June 9

Strange. I have tested it on two different computers with the same result.

0 0

replied on June 9

I have heard the same from my solution provider that the hotfix has an issue and we are waiting to see if there is another hotfix for the current hotfix.

0 0

replied on June 9

You should try the patch then update the case if it does not work so we can troubleshoot it further.

0 0

Replies

replied on June 3

I would suggest opening a support ticket with your Solution Provider so they can collect the necessary information to pass to Laserfiche to troubleshoot the issue.

1 0

replied on June 3

I am able to recreate it and just opened a support ticket with our Solution Provider.

0 0

replied on June 3

I opened a case with our Solution Provider also.

0 0

replied on June 3

Hi all,

We have created bug 594641 for this issue. But we cannot reproduce it stably. It would be great if have more information, like logs under %localappdata%\Laserfiche\Tracing (Help -> About Laserfiche -> Tracing to open it)

Thanks.

1 0

View 2 previous replies

replied on June 4 • Show version history

I supplied trace files to my SP. Also please note that this was/is working in version 11.

0 0

replied on June 4 • Show version history

Hi Qing,

Can you send me an upload link or someone to email it to, I'll send you our logs. Or you can email me EMoore@KentWA.gov

0 0

replied on June 4

You need to contact your Solution Provider so they can open a case with Laserfiche.

0 0

replied on June 4

I was just answering Qing's request for the files. Seems a bit redundant to open another case, when at least two are open and a bug number has been assigned?

0 0

replied on June 4

I don't make the rules, that's just how it works

0 0

replied on June 2

We are having the same issue, any news on this from Laserfiche?

0 0

replied on June 2

Nope, radio silence so far.

0 0

replied on June 4

We've opened a case in your behalf (245522) and have notified your service provider. He will ask you for the client trace files.

1. Can you enable client tracing, Help > About > Tracing?
Enable LFSO tracing then reproduce the issue.
The logs will be under %localappdata%\Laserfiche\Tracing
Zip those up and attach it to the case.
2. Get the Admin and Operational trace logs from the repository as well.

Thanks!

0 0

replied on June 4 • Show version history

Does it look like this? I am using lookup tables for these and I have had two people say it is grey and I cannot replicate it.

If it is the same thing, we are on Laserfiche 11

You are not allowed to follow up in this post.

Question

Question

Desktop 12, Template with dynamic fields becomes unresposive

Answer

Replies

Sign in to reply to this post.