• State Not Answered
  • Replies 4 replies
  • Subscribers 583 subscribers
  • Views 2409 views
  • Users 0 members are here
Options
Related

Di you know how we can fix AlarmServer1, CT_ERROR_NAMED_PIPE_WRITE_FAILED error

Miguel

Hello

The Alarmserver is stopped and i cannot start it.

consulting the debug Syslog file, i found:

2025-08-26 19:11:30.408 +01:00 TranWrite(6, 19): Name=@@c1.AlarmServer1, CT_ERROR_NAMED_PIPE_WRITE_FAILED

someone knows this kind of issue and how we can fix?

Parents
  • 0

    Hi   

    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).

Reply
  • 0

    Hi   

    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).

Children
No Data