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

Question

Question

Weblink 8.2.2 A lost connection condition has been detected

asked on August 1, 2018 Show version history

I have a customer that is running WebLink 8.2.2 (they originally had WL7 installed on this server and at some point upgraded to WL8) on Windows 2008 6.0 build 6002 SP2 and IIS 7.  They were having issues with the custom searches on the home page not working, so some changes were made (I do not know what was changed).  Now they are reporting that when they try to open a document, they get an error stating "A lost connection condition has been detected".

When I search for the error, all I find is about when WL is hosted by XP (not my case).  I went ahead and ran the AdminScript that is listed as the fix, and that did not resolve my issue.  I then went to IIS and under the Default Site settings, I edited the Limits and set the Connections = 100 and that did not have any effect.

Where do I need to look to increase the connection limits to resolve this? (They are unwilling to upgrade to WL 9 or 10 at this time)

0 0

Replies

replied on August 2, 2018 Show version history

That error message is triggered by the tiles failing to load.  The expected scenario is that the user loads the viewer and some of the image loads.  If the user leaves the page idle for too long their session will expire.  When they scroll down to view more pages, there will no longer be a connection to use and WebLink will display this error.  In your case it looks like it's coming up on the initial page load, so there's something else going on.  What kinds of errors are those tile requests returning?  What if you try opening the requested tile URL in a new tab?

0 0
replied on August 2, 2018

Thanks for the response.  I do not know what was causing the problem, but I removed WebLink, deleted the WebLink folder, re-installed WebLink, and then reconfigured it and that seems to have resolved the issue.

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

Sign in to reply to this post.