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

Question

Question

Forms Real Time Notifications Not Working on Secondary Server in LB

Forms Version 11
Updated March 6, 2023
asked on February 10, 2023 • Show version history

I have followed the online documentation for setting up Forms in a Cluster, but the real time notifications are not working on the secondary server. Below is our setup:

  • Server1 - Primary Forms Server (Forms Routing Service, Notification Hub, Notification Master)
  • Server2 - Forms
  • Our Load Balancer is a Citrix NetScaler. A VIP has been created for ports 80/443 and includes both Server1 and Server2. Another VIP has been created for port 8181 and includes Server1 only. The LB URL is https://laserfiche.example.com.

 

If I access Forms on Server1 the real time notifications work correctly. If I access Forms on Server2 I receive a 500 error when I look at F12 Dev Tools:

I do see the 'signalr?' call as well:

How do I determine where it is failing?

0 0

Answer

SELECTED ANSWER
replied on February 14, 2023

This is now working in our Test environment. Here is our configuration for anyone else that may be using Citrix Netscaler.

  • Server1 - Primary Forms Server (Forms Routing Service, Notification Hub, Notification Master)
    • Laserfiche Forms Routing Service is running as a domain service account.
    • Laserfiche Notification Hub Service is running as a domain service account.
    • Laserfiche Notification Master Server is running as a domain service account.
  • Server2 - Forms
    • Laserfiche Forms Routing Service, Notification Hub, and Notification Master are all disabled.
  • Our Load Balancer is a Citrix NetScaler. A VIP has been created for ports 80/443 and includes both Server1 and Server2. Another VIP has been created for port 8181 and includes Server1 only. The LB URL is https://laserfiche.example.com.

 

We followed the online help documentation for changing the web.config file.

1 0

Replies

replied on February 10, 2023

The first step in the Notification Service flow is obtaining a "Push Notification (auth) Token" from Forms over HTTPS/443 at the main Forms URL. I believe the Routing Service generates this token. Once the browser client receives this token, it sends it in a call to https://formsnotificationurl.example.com:8181/* to open a SignalR (WebSocket) connection and authenticate to the Notification Hub service itself.

You're getting a server-side HTTP 500 error at the first step. I think you want to check the Forms Routing Service event logs on the Primary server. You should find something corresponding there.

As a side note, you should use "example.com" for example URLs. https://www.company.com/ is a real domain owned by a private party. https://example.com/ (as well as .org and .net) are IANA-managed Reserved Domains registered to them in perpetuity as domains for "For Testing & Documentation Examples" per RFC 2606.

2 0
View 3 previous replies
replied on February 10, 2023 • Show version history

Thanks for the reply, Sam. I checked the Server1 logs, and nothing is recorded when the error occurs in the browser. On Server2 there are errors in Laserfiche\Forms\App\Operational log that says "A connection to the notification server could not be made. Notifications and real-time updates have been disabled. [LFF8100-NotificationServerConnectionDown]".

Since the error is being recorded on Server2, does that mean that the 8181 traffic is not being redirected correctly to Server1?

0 0
replied on February 13, 2023

On the Primary Forms Server (Server1) I changed the Notification Hub Service and Notification Master Service to run as a domain user and that got me past the original [LFF8100-NotificationServerConnectionDown] error that was being presented in the Server2 Logs.

I do not see any errors being created on Server1 or Server 2 in the Log files, but in F12 Dev Tools I now see a ":8181/signalr/hubs?" error that I believe @████████ was referencing in this post.

This is what the header shows:

I can't find any additional errors in the logs though so I'm not sure where to go from here.

0 0
replied on February 15, 2023

Okay great, the :8181/signalr/hubs call is the actual notification service one. What's error code on that? Should be in the Preview or Response tab in Dev Tools.

Also, make sure you're also checking the Forms Notification event logs, not just the Forms App ones. Separate ETW channels.

0 0
replied on March 6, 2023

Just upgraded our production environment to version 11 and put this in place. I am seeing the same error I mentioned in the screenshot above about :8181/signalr/hubs. There is no error code in the Preview or Response tabs in Dev Tools. I am waiting to hear back from our LB team to see if there is something not configured correctly there. As before, if we happen to connect to the Primary Forms Server the real-time notifications work as expected, but not when connecting to one of the other two servers in the LB.

0 0
replied on March 6, 2023

It appears that someone fat fingered the wrong IP address in the LB for port 8181. All is working correctly.

1 0
replied on March 6, 2023

Classic =D

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

Sign in to reply to this post.

Details
Related Posts
Loading ...