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

Question

Question

How to limit the Weblink download time

How To
Updated August 30, 2024
asked on June 24, 2024

We have users downloading multiple documents / folders longer than 3 hours.

They are using Weblink 11. I know I can set a timeout for idling, but the idling timeout setting does not apply to download time.  

I want to know if there is a setting to log out users automatically when their download time is too long ?

 

thanks

0 0

Answer

SELECTED ANSWER
replied on July 1, 2024

Re:

I checked Session via LF Admin  Console, there are two or three session longer than 3 hours.  I already set the idling limit is 15 minute so that I assume those long sessions are doing download.

It is extremely unlikely that users are downloading anything for that long. There are a few bugs and issues that can cause WebLink to fail to properly close repository sessions in a way where Laserfiche Server "Idle Timeout" setting will not apply. That's almost certainly what's happening.

First, you should update WebLink to the latest release if you're not already on it. Some of the issues sound like ones that may have been fixed, like the Welcome page not always loading correctly. The latest as of today is WebLink 11 Update 3, which you can download here. Make sure to back up your existing configurations using the WebLink Settings Bundler utility before upgrading.

If you're still experiencing issues after upgrading to 11 Update 3, it's possibly happening as a result of this Microsoft patch that broke WebLink for some customers:

KB 1014527: The May 14, 2024 Cumulative Update for .NET Framework May Cause Reliability Issues with the Laserfiche Web Client and Laserfiche WebLink.

If so, please try the workarounds / mitigations suggested in that KB article.

If you are still having issues after both having WebLink on version 11 Update 3 and applying the .NET Framework Update issue workarounds, please open a support case through your Solution Provider so our team can investigate further.

0 0

Replies

replied on June 25, 2024

What is the scenario where people are regularly downloading content from WebLink that's taking more than 3 hours?

Can you help provide some background context on what problem you're trying to solve here and why?

0 0
View 3 previous replies
replied on June 26, 2024

here are our settings :

Laserfiche server 11 on windows server 2019  with IIS 10.  

We use the extensionless URL for user to use Weblink ,e.g. https://www.ourterver.com/weblink

Users sometimes report that our custom Welcome page missing the text box but a blank page.

I checked Session via LF Admin  Console, there are two or three session longer than 3 hours.  I already set the idling limit is 15 minute so that I assume those long sessions are doing download .

I check the windows event log, there are w3wp.exe error and LF error as below :

Error reading configuration file 'C:\Program Files\Laserfiche\Web Access\Web Files\.\Config\WebAccessConfig.xml'
 (The process cannot access the file 'C:\Program Files\Laserfiche\Web Access\Web Files\Config\WebAccessConfig.xml' 
because it is being used by another process.)

 

after I reboot the server, everything is back to normal.  

This issue keep happening .

 

 

0 0
SELECTED ANSWER
replied on July 1, 2024

Re:

I checked Session via LF Admin  Console, there are two or three session longer than 3 hours.  I already set the idling limit is 15 minute so that I assume those long sessions are doing download.

It is extremely unlikely that users are downloading anything for that long. There are a few bugs and issues that can cause WebLink to fail to properly close repository sessions in a way where Laserfiche Server "Idle Timeout" setting will not apply. That's almost certainly what's happening.

First, you should update WebLink to the latest release if you're not already on it. Some of the issues sound like ones that may have been fixed, like the Welcome page not always loading correctly. The latest as of today is WebLink 11 Update 3, which you can download here. Make sure to back up your existing configurations using the WebLink Settings Bundler utility before upgrading.

If you're still experiencing issues after upgrading to 11 Update 3, it's possibly happening as a result of this Microsoft patch that broke WebLink for some customers:

KB 1014527: The May 14, 2024 Cumulative Update for .NET Framework May Cause Reliability Issues with the Laserfiche Web Client and Laserfiche WebLink.

If so, please try the workarounds / mitigations suggested in that KB article.

If you are still having issues after both having WebLink on version 11 Update 3 and applying the .NET Framework Update issue workarounds, please open a support case through your Solution Provider so our team can investigate further.

0 0
replied on August 7, 2024

LaserFiche has hot fix for this issue.  We installed the hot fix to solve this issue without uninstall the .net framework.

0 0
replied on August 7, 2024

I beg to differ. We have users downloading for hours and we have used it for years like that. Evidence as in huge video files and currently all of them are timing out. (since about 2 weeks or so) We applied the hotfix (mentioned above) from Laserfiche today and have set the idle time to 10 hours again. But Now I need to make sure they can download files up to (preferably more) 10Gb again since it looks like it was quitting around 350 Mb... And obviously that is not sufficient for evidence. 

 

0 0
replied on August 7, 2024

Can you please open a support case? The hotfix for the .NET Framework update issue has worked in most (80%+) but not all WebLink cases. We are actively seeking more diagnostic information from customers where it hasn't worked so we can identify what else may be going on in those scenarios and address it. 

0 0
replied on August 8, 2024

Not only LF, you may need to set timeout in IIS server too.

 

0 0
replied on August 30, 2024

Apparently our internal view only users are still having issues being disconnected constantly from weblink. I am trying to find any and all places where timeouts may be set so that I can check them all to see if we missed anything. Our downloads are generally Gigs is size (video and/or audio) however it is even doing it with small PDF's

 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...