Di you know how we can fix AlarmServer1, CT_ERROR_NAMED_PIPE_WRITE_FAILED error

Hi Miguel 

I recommend you reach out to AVEVA Technical Support to get further assistance on this issue.

It is strange that you can't start the Alarm Server. I'd recommend consulting the Alarm Server syslog for further details.

The Client syslog (syslog.dat) message regarding CT_ERROR_NAMED_PIPE_WRITE_FAILED is expected when the Alarm Server is offline. It can also briefly occur during startup of a system, when the Client tries to connect and the Alarm Server is not completely started up.

Wish you the best in finding the root cause of this issue, and hope Support can provide further assistance.

Kind regards

Olivier

Hi  Miguel 

Have you taken a look at syslog_Alarm,c1.AlarmServer1.dat? It should log some message for alarm process start-up failure.

If the alarm server had been running and failed to start up again, it could be caused by low disk space or corrupted databases. You could try the followings to narrow down the issue

• Check disk space
• If not low disk space, try to restart all processes together. If you change the alarm memory mode, you must restart all processes together.  
• If the issue persists, go to the data folder where the alarm database is located, find the folder name that matches your project name. This folder contains the alarm database of your project. Rename the folder name as backup, restart your project and a new alarm database will be created. If the project is up running, the issue is caused by a corrupted alarm database.

If the above troubleshooting doesn't help, reach out to AVEVA Technical Support as Olivier suggested.

Note that the error (Name=@@) you mentioned above is an IPC error (inter-process communication).

Do you have dual network adapters on your PC with both networks connected at some point? Alarm server doesn't like it if it sends a request out on one NIC and receives it on the other NIC.

I changed Extended Memory to FALSE in alarm server settings and alarm Server start