Question

Two authentication services trying to listen on the same port, failing to do so

Updated July 17, 2018

asked on July 16, 2018 • Show version history

Laserfiche has two services called Laserfiche Authentication Service. If you have 10.2 installed one is called Authentication 10.0 and one is called Authentication 10.2 If you have 10.3 installed one is called 10.2 and one is called 10.3.

One always starts and the other one fails to start because it is trying to use the same port, and they don't seem to want to share. It normally never causes any issues except today it appears to have confused the workflow service when the 10.0 service was running, but not the 10.2 service.

Is there something that needs to be done so that they can share the same port?

0 0

Answer

SELECTED ANSWER

replied on July 16, 2018

Those are used by Web Access and Mobile, so it might be possible to get two versions installed if you have different versions of those products. They are backwards compatible though, so you should be able to just disable the older one.

0 0

replied on July 17, 2018

Ah that could explain things! We usually don't have mismatched web services but the server I am working on had web access installed to cover a downed web server once. I compared the services with my dev environment which could have all sorts of mixed matched versions.

I need to make sure the older auth services are disabled, which was the first thing I did. But I thought maybe they both need to run.

0 0

Replies

replied on July 16, 2018

What do you mean by " it appears to have confused the workflow service"? Workflow does not use the Laserfiche Authentication Service.

0 0

replied on July 17, 2018

I was trying to view the workflow subscriber trace log, but it was empty. I tried restarting the service, still empty. No errors found in any of the recent workflow logs under the admin console, none found in the LFWorkflow event viewer log.

There was an error from the day before after a windows update and re-boot, from the Auth 10.2 service saying it could not listen on it's port. I found the Auth 10.0 service started before the 10.2 service. I stopped 10.0 and started 10.2.

The subscriber trace log appeared again full of entries and workflows that had not started since the reboot the night before all kicked off.

0 0

You are not allowed to follow up in this post.

Question

Question

Two authentication services trying to listen on the same port, failing to do so

Answer

Replies

Sign in to reply to this post.