Question

9.1 LFImageEnable80 LoadLaserFiche cannot establish connection

SDK

Updated September 14, 2016

asked on October 30, 2014

Versions up to 9.0 have all worked fine. After upgrading to 9.1 or 9.1.1 using LoadLaserFiche will give the error "cannot establish connection" if the client isn't already open. If the client is open then LoadLaserFiche does not need to be called and the user can continue and search for a document.

This is a legacy vb6 application so upgrading to CAT is not an immediate option.

The following is the code used:

Dim ie as LFIMAGEENABLE80Lib.ImageEnable

Set ie = New LFIMAGEENABLE80Lib.ImageEnable

If Not ie.IsLaserFicheOpen then ie.LoadLaserFiche False

0 0

Answer

APPROVED ANSWER

replied on February 25, 2015

Please see KB 1013619 to obtain an updated version of LFImageEnable80.dll which addresses this issue.

0 1

Replies

replied on October 31, 2014

Alright, we think we found the issue. Depending on what version was initially installed on the machine, you might have a file called LfStart.exe in the Client install directory. The current release version of ImageEnable uses that file to launch the Client. That file was removed in 9.1.x, but the change to ImageEnable to account for that is in the upcoming 9.2 SDK.

As a workaround, try taking the LfStart.exe on the working machine and copy it to a machine that doesn't work. Can you confirm whether that addresses the issue? We're hoping to have the 9.2 SDK avaliable sometime next week, although if that doesn't happen we should at least be able to make the updated ImageEnable file accessible.

1 1

View 1 previous reply

replied on February 19, 2015

I have the exact same problem as described here. I copied the FLStart.exe (from 9.1) to the Laserfiche Install folder and now it works.

My scenario differs though. My customer has installed LF 9.2 client on that machine and i installed the latest (released) 9.2 runtime SDK. To my knowledge, no V9.1 was installed of either the SDK or the Client.

My read of this thread leads me to believe this issue would be resolved if the 9.2 SDK runtime was used. Yet i can confirm that this problem occurs on my 9.2 Client (and 9.2 SDK runtime) unless i copy the LFStart.exe file over from my other machine running 9.1.

Please advise, my deadline hangs over my head.

Thanks in advance

0 0

replied on February 19, 2015

Hi Joe,

The issue is still present in the 9.2 SDK IF you are using LfImageEnable.dll, as that's unchanged. It's not an issue if you are using the current ClientAutomationTools instead of ImageEnable, but that isn't your scenario here.

We have a recent fix for LfImageEnable such that it no longer requires LfStart to be present. We're figuring out the best way to deploy it (most likely an SDK 9.2 update alongside the upcoming 9.2.1 release), but for now you should be able to contact Laserfiche Support and they can provide you with the updated file.

0 0

replied on February 19, 2015

Sorry, but i cannot figure out how to "contact LF support". Is there an email or phone number?

0 0

replied on February 20, 2015

In order to contact Laserfiche Support, you need to go through your VAR. Cantact your VAR and have them contact LF Support on your behalf.

0 0

replied on October 30, 2014

What's the specific version of LfImageEnable80.dll? Also, did anything on the machine itself change during the upgrade (arch, OS)? There were some specific issues to certain environments that have been resolved in certain (post-80) versions of the SDK, although the dll itself is still 80.

Looking through our records, I see confirmation that LfImageEnable80.dll 8.0.5.0 works with the 9.1.1 Client, at the very least.

0 0

replied on October 31, 2014

This happens for everyone but the dev machine, so machine changes can probably be ruled out. I also know of at least one case where upgrading was the only thing done. The dev machine is using 8.0.5.0. I will get information from some of the installed systems. I am guessing that there are at least a few that don't have version 8.0.5.0 but I don't yet know that they all fit that scenario.

There are also issues with sessions staying open now. Do you think this could be related or is it most likely a completely separate issue? I thought that if it had trouble opening the client that it might have trouble closing things also. I was going to solve one problem first to see if the other went away.

0 0

replied on November 6, 2014

Hi Melissa,

If your question has been answered, please let us know by clicking the "Mark this reply as the answer" button on the appropriate response.

If you still need assistance with this matter, just update this thread. Thanks!

0 0

replied on November 20, 2014

It does not seem to be fixing it. Is there an updated LFImageEnable to test with?

0 0

replied on November 20, 2014

You copied LFStart.exe to c:\Program Files (x86)\Laserfiche\Client (where LF.exe is) and it still doesn't work?

0 0

replied on December 22, 2014 • Show version history

Additional information is known about this issue.

The error occurs...

When the laserfiche client application install includes the "Laserfiche Office Intergration" AND

MS Outlook is running ... AND

The command LFImageEnable.LoadLaserfiche (False) is sent.

No errors occur if..

the laserfiche client application install Does NOT include the "Laserfiche Office Intergration" ...OR

MS Outlook is closed ...OR...

the command LFImageEnable.LoadLaserfiche (True) is sent.

The combination of LFImageEnable.LoadLaserfiche(FALSE) and Outlook running is where the problem lies.

0 0

replied on March 31, 2015

I am experiencing the same issue with 9.2 with a custom integration.

I used the updated LFImageEnable80 file from the KB, which is supposed to no longer require the LFStart, correct? It didn't work.

I was only able to get my function to work if I copy LFStart from my dev machine to my test machine.

Will there be an update that restores the LFStart file for the customers?

0 0

replied on March 31, 2015

Are you sure you updated the correct copy of LFImageEnable80.dll? Are you getting the same "Cannot establish connection" error?

0 0

replied on April 1, 2015

Got it! I missed copying to both Program Files and Program Files (x86). It's working now!

0 0

replied on September 13, 2016

Does the new LF10 version of LFImageEnable80.dll have issues with this as well? I recently upgraded my LF install and upgraded an integration to the LF10 SDK, and started experiencing errors again. I changed my reference to the LFImageEnable80.dll in KB1013619 and that seems to have corrected the issue.

Just checking if my upgrade is buggy or if this was an actual issue again.

Thanks

0 0

replied on September 14, 2016

This should be fixed in version 10. Are you getting the same "cannot establish connection" error?

0 0

You are not allowed to follow up in this post.

Question

Question

9.1 LFImageEnable80 LoadLaserFiche cannot establish connection

Answer

Replies

Sign in to reply to this post.