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

Question

Question

Forms Routing Service Error Log Location?

Forms Administration
Updated February 10, 2023
asked on February 9, 2023

The Event Viewer logs for LF Forms appear to be only for the IIS web service, not the Windows based Routing Service itself.

Is there a log anywhere that shows any possible issues with the Routing Service installed as a Windows Service?

We have a situation where it stopped listening on it's dedicated port, the service itself did not stop, but it just gave up it's listening port making it impossible for the web service to talk to it even on the localhost. The Event Viewer logs made this clear because the IIS web service noticed it was not listening any longer. 

What we don't know is when and why it stopped listening because I don't see any logs from the service itself.

0 0

Answer

SELECTED ANSWER
replied on February 9, 2023

The Event Viewer logs for LF Forms appear to be only for the IIS web service, not the Windows based Routing Service itself.

This is not the case. Both the Laserfiche Forms Routing Service and the Forms IIS app write to the same two Windows Event log channels:

  1. Applications and Services Logs -> Laserfiche -> Forms -> App -> Admin (Laserfiche-Forms-App/Admin)
  2. Applications and Services Logs -> Laserfiche -> Forms -> App -> Operational (Laserfiche-Forms-App/Operational)

If you are running the Forms components as the default built-in identities, SYSTEM (Local System) for the Routing Service and IIS APPPOOL\FormsAppPool for the IIS app, you can differentiate which events came from which component by looking at the User field:

However, you should be aware that the Routing Service only logs errors that it itself generates.

The problem you're describing with regards to port listeners is a Windows-level problem. In this case, you should also check:

  1. Windows Logs -> Application
  2. Windows Logs -> System

For any errors or warnings about service ports, conflicts, permissions, etc.

3 0
replied on February 9, 2023 • Show version history

They are all coming from IIS APPPOOL, we run the service as SYSTEM.

If I could know when the Routing Service decided to stop listening on it's port, then I could check the App and System logs for any additional signs of a problem.

I see many logs from the apppool stating that Mr. Routing stopped listening and I confirmed that Mr. Routing is not listening using netstat but that he IS running.

I need to know from Mr. Routing when he stopped listening at the very least to find out anymore information.

Every single one of these Unable To Trigger is related to the fact that the Windows Service is not listening any longer. But there is not a single error for the entire day of 2/5 when the problem started and no errors from SYSTEM at all beyond this point. I did find older errors from SYSTEM like when a SQL server went down, so your right it is reporting here. But it doesn't tell me when it stopped listening on the port before 7:30pm on 2/5

0 0
replied on February 9, 2023

I would personally avoid the thought line of "the routing service stopped listening" because while useful shorthand, it's prescriptive in a way that might not reflect the root cause of the issue. For example, say Windows is somehow blocking the Routing Service from registering a listener on the port. Different mechanism of action.

Anyway, if this is a standalone Forms instance (has both Routing Service and IIS app) and there are no other Forms instances attached to it or its database in any way (DMZ server, etc.), I'd honestly just try running the installer and Repairing the installation. If that doesn't work, uninstall, then re-install Forms. It'll keep your configs. Better to let the installer try to re-set the Forms port listeners and url acls to the known good default state before trying to mess with it by hand.

And just in case you haven't rebooted the entire server yet, do that first.

0 0
replied on February 10, 2023

I was looking for a log that might shine some light on the reason for the service currently not listening when previously it was listening. We have a situation where some days the service is listening and some days it is not. So was trying to pop the hood and figure out what is really going on.

Extensive troubleshooting was done over the last few weeks that I would rather not go into again on this post.

The purpose of this post was just to find the log of the routing service and now I do see that it is where I was already looking, not in some other place. It just has not posted anything for awhile, not since the beginning of the month and well before the most recent period where it is no longer listening.

0 0

Replies

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

Sign in to reply to this post.

Details
Related Posts
Loading ...