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

Question

Question

Laserfiche Connector with Chrome works on one computer but not another

asked on September 30, 2021 Show version history

I have configured LF connector to search the repository based on a value that appears in a Laserfiche form loaded in Google Chrome browser. This works perfectly on my computer, but not on another computer.

We are both using the exact same path to a network folder to load profiles. The profile I'm trying to use loads on her computer--it just fails to find the value in the browser. I looked at the Chrome extensions she has loaded and made sure they were all loaded in my computer. Still, Connector works on my computer but not on hers.

I am using Laserfiche Connector 11 whereas my servers are still at version 10.3, but I don't think that discrepancy could cause the problem I'm seeing.

I would be very grateful for any ideas about how to troubleshoot this.

Screenshot 2021-09-30 120843.jpg
0 0

Replies

replied on November 2, 2021

Do you use the same version of Chrome or the same OS? This may result in subtle differences in the elements on the page, and then Connector cannot read the value of the specified control.

1 0
replied on November 2, 2021

Thank you for your reply. Those are excellent questions.

Let me post here what happened. I hope that either your questions or this post will help someone else puzzled by similar behavior.

On close investigation I found that on one computer, the profile was not actually loading from my shared location but instead was loading a profile of the same name that was local to that computer. I had mistakenly thought that once I set a computer to load profiles form the shared location, that would apply for every profile used on that machine.

That meant that contrary to the belief I posted above I was actually running different profiles on the two computers. Once I understood that it was a simple matter to fix the problem.

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

Sign in to reply to this post.