I have a client that is using the Tyler ICM integration to Laserfiche and the integration works as such but when you close out the document view result the LFSession.exe does not terminate. Of course Tyler has told the client that this is not their issue. Has anyone dealt with this issue and come up with a resolution?
Question
Question
Replies
Also, I just realized that the original report is about LFSession.exe not being released. This is not an issue caused by the integration. After logging into a PC, the first time you open the Laserfiche client, it starts the LFSession.exe process and that runs in the background until it is manually killed or you log out of the PC. It is normal and expected to see the LFSession.exe process running even though you do not have the LF Client open.
The fact that Laserfiche is not releasing connections is not related to the LFSession.exe running but is most likely an issue cased by the Tyler integration.
What version of the client is your customer running? If I remember correctly, the Incode integration can run with either client 7.2.x or 8.1.x.
The client is running LF 8.3.2 and the integration works fine with regards to finding the correct document and displaying the view. The resulting view looks like the Laserfiche document view without the LF client actually being open. When you click to close the document the document closing just fine but DOES NOT release the LFSession.exe so Laserfiche still thinks the user is logged in. Of course once they hit 4 sessions they exceed users. the only work around they have is to manually end the task as an admin because users are not allowed to do that or logging into the LF admin console and ending the user session. I am thinking the Tyler integration should be closing the session just like it opens it up when it runs. When they called and asked Tyler about the terminating the LF Session they told them that was not their issue.
The integration is built with either the 8.1 or 8.2 versions of the SDK DLL files. The customers that I have that use the Incode integration have all stayed on the 8.1 client version to ensure compatibility. My guess is that the older version of the DLL is not properly releasing the newer version of the client and causing the open session.
The problem is that Tyler is no longer a Laserfiche partner and so no longer has access to the new DLLs and as such, they can not update their integration to work with the newer clients. Try downgrading 1 of the client workstations to LF 8.1 and see if that resolves the issue they are seeing.
I wanted to update this note to clarify that Tyler in fact has had continual access to development environments including our SDK. We are currently working to assist them with updating their integration to support Laserfiche 10.