A connection to Web Access cannot be made.

asked on December 12, 2016

Multiple users are receiving this error when clicking "Save attachments to Laserfiche" in outlook. "A connection to Web Access cannot be made. Refresh Web Access and try again."

These are the details:

"A connection to Web Access cannot be made. Refresh Web Access and try again.

Invalid Connection

at Laserfiche.OfficePlugin.Operation.ComponentModel.Outlook.OutlookOpenedFolderProfile.CreateConnector()
at Laserfiche.OfficePlugin.Operation.ComponentModel.Outlook.OutlookOperationBase.SaveAttachmentThreadProc(Object obj)

The problem is the client isn't using web access, they are using their thick client. When they save, the box that says "To Laserfiche Web Access or Client" is checked. How do we get it to see that the thick client is open? This used to work fine before, and we have tried a repair but it hasn't made a difference. Again this is happening to multiple users on different computers. They are on Windows 7, LF 10.1.0.151, and Outlook 2013.

I believe the workaround is to just choose the repository every time, but the user would like to avoid that if at all possible.

Error.PNG (20.3 KB)

| Download

Settings.PNG (25.02 KB)

| Download

Error.txt (333 B)

| Download

0 0

replied on December 12, 2016

Please open a case with Support

0 0

View 4 previous replies

APPROVED ANSWER

replied on December 14, 2016

A case was opened for this issue. We had Ricardo apply 10.1 Update 2 to the LF server and upgrade Web Access to 10.1 update 2 as well which resolved his issue.

0 0

replied on May 8, 2018

I have not been able to resolve this issue all the way up to 10.2.1. Still have no idea why it is trying to connect to the "Web Client" or what that means. I can not explain to the customer what is going on. We do not have it configured to connect to the web client, it is configured to connect directly to the repository server which resides on it's own server.

I get asked about this every week.

0 0

replied on May 8, 2018

Please open a case with Support

0 0

replied on May 8, 2018

I will add it to the queue. Don't want to open another ticket until I hear back on the most critical first. I am also requesting my own workstation at the client site running Outlook, since I am sure that will be required before I can work with support on any troubleshooting. Right now I just get a screenshot of the error and a chance once in awhile to check their configuration and verify it is not configured to access anything called "Web Client" but instead directed at the repository server. When it says "Web Client" does it mean "Web Browser" or does it mean "Internet Information Services"?

0 0

replied on May 8, 2018 • Show version history

The Laserfiche web client is the current name of the module formally known as 'Web Access', used as the primary client application into the Laserfiche content repository Server in a web environment. As it is a new name, many people are inconsistent about using it and continue to use the old name, but the product modules shouldn't actually say 'Web Access' anywhere at this point if you look around.

So in this case, your options are to connect directly to the Laserfiche Server or to route through the web client. You might do the later for example if you are outside of the nework and cannot make a direct connection to the Laserfiche Server but the web client is installed in the DMZ.

0 0

replied on May 9, 2018

Hi Justin

That I understand, sort of. Not sure how it connects to a "website", you mean HTTP post?

In any case, these users have access to the Repository server. So how can we ensure that they never try to connect to the Web Client when using the Outlook Plug-in?

I have gone in and configured their settings so that they use the repository and verify that it is configured that my configuration has not changed each time I get on the workstation, but the next day they send in another ticket with this message about it being unable to reach the "Web Client" every single time. It is frustrating that I am not configuring anything to reach out to the web client.

0 0

replied on May 11, 2018

Basically, for users without a direct connection to the Laserfiche Server, it can piggy-back on the web client's connection to sign in through the plugins.

In your case, is it simply a training thing that the users need to select the repository instead of trying to go into 'attach' to specify the repository? The option to access through the web client is only there if you explicitly select 'Attach'. If the repository is already showing up in their list, there's no reason they should need to go to that in the first place.

0 0

Question

Question

A connection to Web Access cannot be made.

Answer

Replies

Sign in to reply to this post.