Question

Web Client and LF Office Integration

Web Client Laserfiche Version 11

Updated April 27, 2021

asked on April 26, 2021

We recently upgraded to LaserFiche 11 from 10.4.2 (on premise). We have a small select team testing out Web Client, Office integration etc.

Post upgrade, when a document is checked out, and after 20+mins Office Integration seems to lose (and not be able to re-establish a connection to the repository. The document can then only be checked in as a new document or by closing Word, and opening again from the Web Client.

I have enabled tracing on the office add-in and found on the client and web server that there are errors re-connecting to the repo server. On the server event viewer I usually get a object reference not found and then an invalid connection and an unable to find token.

I have disabled the idle timeout on the web client in IIS and on STS on LFDS - which is not ideal, but trying to elminate possible issues one by one.

The Office Integration does not appear to have it's own timeout in the web config.

In Word - after the timeout has occured - the login dialog appears and then fails to connect and the ribbon is greyed out. As a workaround (on a local PC) I am able to close Word, open the doc again from the Web Client with the changes I made to the doc intact (from the temporary checked out doc location on my PC) as it is clever enough to see that the doc is already downloaded and checked out. And as long as I check it in before the repo connection is lost it works.

Any ideas would be helpful.

0 0

Replies

replied on April 27, 2021

In another post you mentioned having issues using LFDS 11. In this case, the Office Integration is using LFDS 11 to authenticate, so seeking support for your LFDS installation will probably resolve your Office Integration issue.

1 0

replied on April 27, 2021

Thanks. And while that is true, the cookie timeout was a significant factor in preserving the session for long enough to complete work on a document without losing the connection. I had noticed in the event log that it was failing to retrieve a valid token from the cookie - most likely because it had expired.

Wrt to the LFDS issue. A service restart has fixed many of the issues I was having although we had to downgrade to 10.4.3 to correct a fairly regular lack of response from LFDS.

0 0

replied on April 26, 2021

It would be possible for them to read the following IIS document:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831780(v=ws.11)?redirectedfrom=MSDN

Use Cookies - associates session information with client information for the duration of a user's connection to a website. Cookies are passed on together with all requests between a client and a Web server in an HTTP header. Using cookies is a more efficient way to track session state than any of the methods that do not use cookies, because cookies do not require any redirection. Additionally, cookies let users bookmark web pages, and they retain state if a user leaves one site to visit another and then returns to the original site.

0 0

replied on April 26, 2021

Thanks Manuel;

We use cookies but I think it may be that the expiry was set to 30 mins. I have extended this to see if that eleviates the problem.

0 0

You are not allowed to follow up in this post.

Question

Question

Web Client and LF Office Integration

Replies

Sign in to reply to this post.