NXPowerLite Server does not have a built-in alerting mechanism for errors, warnings or software progress. However, it logs key events in the Application section of the Windows Event Viewer, which can be monitored. If your server already uses a monitoring system like Zabbix or similar, you can easily set up rules to trigger email alerts when specific NXPowerLite events occur.
Server Events for monitoring
Below is a list of NXPowerLite Server events that can be monitored for effective integration into your alerting system, so you are informed swiftly about issues with NXPowerLite Server. We have not listed all the events that can be reported, but have selected specific codes that we think are helpful to be notified about.
Informational alerts
| Event Code | Description |
|---|---|
| 106 | NXPowerLite Service resumed |
| 107 | NXPowerLite Service paused |
| 125 | A new 'Loop Automatically' optimize cycle started |
| 126 | A new 'Loop Automatically' optimize cycle started |
| 127 | A 'Loop Automatically' optimize cycle completed |
| 128 | A 'Single Pass' optimize cycle completed |
| 129 | A 'Loop Automatically' optimize cycle terminated because of an error in the application |
| 130 | A 'Single Pass' optimize cycle terminated because of an error in the application |
| 134 | The subscription key for NXPowerLite for file servers has expired. |
Warnings and Errors
| Event Code | Description |
|---|---|
| 1006 | Failed to scan directory [Directory path & Description]. |
| 1007 | Failed to scan directory [Directory path]. Unknown error in internal API |
| 2054 | Unrecoverable error |
| 2079 | An unexpected exception occurred in NXPowerLite for File Servers (Front End): [Error description] |
| 2096 | NXPowerLite Windows Service failed to start up properly |
Process monitoring
It may be preferable for you to monitor a process if you want to know whether there has been an issue with NXPowerLite Server. The following processes are associated with NXPowerLite Server.
- RunCoordinator.exe (Main process which manages file processing and the Windows service)
- FileServer.exe (GUI)
- Optimizer.exe (Optimizer thread - designed to crash!)
- PauseUtility.exe (Part of the scheduling feature)
We only recommend monitoring RunCordinator.exe and/or FileServer.exe.