Question

Trimin Connection issues

Laserfiche Version 10 Search and Retrieval

Updated January 29, 2024

asked on January 29, 2024

We have an interface with a vendor named Trimin to display images from Laserfiche. However they have been seeing the attached errors every once in a while, not consistent and no errors show on Laserfiche servers Event Viewers. They also seem sluggish when retrieving documents, again not consistent and want to verify that it is not a Laserfiche issue. They keep mentioning an LFSO08.LIB file that is used to call the items from Laserfiche but can't provide us with this Library, and am wondering if anyone else has ever had issues with the vendor? Or if anyone has anyother ideas as to if there would be any other logs that I can look for regarding the .LIB file.

Also - when the Trimin server is rebooted the system is fine

trimin.png (203.61 KB)

| Download

0 0

Replies

replied on January 29, 2024

This particular error is commonly due result of a firewall or proxy between the SDK application and the Laserfiche server. You can use Wireshark to inspect the network traffic for signs of what is interfering.

The fact that the problem resolves after a reboot suggests that the application could be leaking resources. Check the memory usage on the Trimin server when the error occurs. A memory leak could lead to the application eventually becoming sluggish.

1 0

replied on January 29, 2024

LFSO80 is a COM library, and in order to call into it from a .Net language (as they appear to be doing) an "interop" file is required. It's been a while, but I recall that those files are typically named "interop.XXXLib". Visual Studio can generate one automatically from a COM library, but I believe we also shipped an "official" one with our SDK. As the library is just glue code to provide .Net definitions for COM classes and functions, there isn't anything interesting in there for you to see.

1 0

You are not allowed to follow up in this post.

Question

Question

Trimin Connection issues

Replies

Sign in to reply to this post.