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

Olivier over 1 year ago

There is a performance limitation (access to memory) when running in Service Mode due to Windows operating system. There are work arounds.

See these articles:

https://docs.microsoft.com/en-us/archive/blogs/ntdebugging/desktop-heap-overview

https://stackoverflow.com/questions/17472389/how-to-increase-the-maximum-number-of-child-processes-that-can-be-spawned-by-a-w

Edit the registry key value:

Key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

Value:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=16

to

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,2048 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=16

restarting OS and running the Alarm server in 64 bit.

Hope this helps.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Olivier over 1 year ago

There is a performance limitation (access to memory) when running in Service Mode due to Windows operating system. There are work arounds.

See these articles:

https://docs.microsoft.com/en-us/archive/blogs/ntdebugging/desktop-heap-overview

https://stackoverflow.com/questions/17472389/how-to-increase-the-maximum-number-of-child-processes-that-can-be-spawned-by-a-w

Edit the registry key value:

Key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

Value:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=16

to

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,2048 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=16

restarting OS and running the Alarm server in 64 bit.

Hope this helps.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data