Multiple Clusters, Multiple Alarms Servers, running Citect as a Windows Service

Hi,

Are there any special requirements to run a multi cluster configuration as a service. I'm working with a customer that has multiple Alarm Server instances that encounter problems when running Citect as a Service.

I believe there is 5 Clusters with an Alarm Server for each Cluster. Whenever starting as a service at least one Alarm Server remains in the 'Starting' phase with the Waiting for Alarm Database Initialization messages. So I was wondering if there are any special requirements or limitations for Multi Clustering and running as a Service.

Kind regards,

Gavin

Parents
  • I haven't run into this exact problem, but I did work on a project at a site with multiple Citect clusters on a slow network a number of years ago. We found that having every Citect client and server runtime process connect to every other cluster/server created a large number of connections and caused problems. In that case, we ran the Computer Setup Wizard on each PC and on the Cluster Connections Setup page, chose which process(es) connected to which clusters. For example, the alarm server only needed to connect to its own cluster, but the client process needed to connect to 2 or more clusters, depending on the pages it needed to display.

Reply
  • I haven't run into this exact problem, but I did work on a project at a site with multiple Citect clusters on a slow network a number of years ago. We found that having every Citect client and server runtime process connect to every other cluster/server created a large number of connections and caused problems. In that case, we ran the Computer Setup Wizard on each PC and on the Cluster Connections Setup page, chose which process(es) connected to which clusters. For example, the alarm server only needed to connect to its own cluster, but the client process needed to connect to 2 or more clusters, depending on the pages it needed to display.

Children
No Data