Source
Category
Tags
EventSentry
ID Event Message
48 Congratulations! You have just installed and setup up EventSentry (on host %1), which we believe to be the most efficient and economic event log and system monitoring application on the market. Please visit https://www.eventsentry.com or http://www.netikus.net/ for more information on EventSentry. Thank you for using EventSentry.
100 The process action "%1" successfully executed the process "%2".
101 The process action "%1" was unable to execute the process "%2" due to error "%3".
152 The following error occurred while trying to read the "%1" event log: "%2". In most cases the only way to resolve this problem is to save (if possible) and clear the %1 event log. EventSentry will not be able to monitor the %1 event log until this problem is resolved.
153 EventSentry has successfully re-opened a handle to the "%1" event log after it has become invalid due to error "%2".
201 Unable to allocate memory (for %1) in routine %2
206 Unable to create event %1 in %2.
210 The EventSentry agent was unable to create a collector backup file and will not be able to cache data during extended outages of the remote collector.
240 Unable to open parallel port %1. Please make sure that no application is currently using this printer port, also make sure that no printer is using port %1. You might have to restart the service after the resource conflict is solved.
500 Unable to connect to any of the available SMTP hosts for action "%1". The following errors were encountered: %2.
501 A connection with the secondary SMTP server %1 (action %4) was successful, but a prior connection attempt with the primary SMTP host %2 was unsuccessful due to error "%3".
502 Error during SMTP communication with SMTP host "%1". After sending "%2" the following error occurred: "%3".
510 Action "%1" was unable to create/open file "%2" due to error: %3
520 Action "%1" was unable to create a TCP connection with host "%2" due to error: %3
521 Action "%1" was unable to create a UDP socket to connect to host "%2" due to error: %3
522 The TLS certificate presented by remote host "%1" does not match the locally cached certificate. This could indicate a Man-In-The-Middle attack if the certificate on the remote host was not changed. EventSentry will continue to submit events. The new certificate is shown below: %2
530 Action "%1", invoked by feature, "%3" was unable to connect to the database due to error "%2". EventSentry will queue events and continue to attempt the delivery of events.
531 EventSentry was unable to connect to the ODBC target %1 due to error "%2". EventSentry will cache data and forward it to the ODBC target once the database has become available again.
532 The following errors or warnings occurred within the last 5 minutes while communicating with the database: %1
533 A string had to be truncated in order to be successfully written to the database: Table: %1 (max %2 characters) Original String: %3 Truncated String: %4
550 Action "%1" was unable to send a message to host "%2" due to error: %3
560 Action "%1" triggered process "%2", which ran for %3 seconds with the result shown below. Return code was %4. %5
561 The process action "%1" was unable to execute process "%2" due to error "%3".
562 Process %1 (triggered by action "%2") exceeded the maximum allowed time interval of %3 minute(s) and EventSentry was unable to terminate the process due to the following error: %4
563 Process %1 (triggered by action "%2") exceeded the maximum allowed time interval of %3 minute(s) and the process was terminated. Please increase the timeout interval for this process in the management application (System Health -> Application Scheduler).
564 Action "%1" triggered process "%2" successfully.
565 Process %1 (triggered by action "%2") exceeded the maximum allowed time interval of %3 minute(s) and EventSentry was unable to terminate the process and %4 child processes due to the following error: %5
566 Process %1 (triggered by action "%2") exceeded the maximum allowed time interval of %3 minute(s) and the process, including %4 child processes, was terminated. Please increase the timeout interval for this process in the management application (Actions -> %2).
567 The checksum for executable file "%1" changed from the original checksum "%2". Only the EventSentry agent should have access to this file. This change indicates a potential security breach, and the process will not be launched. The contents of the file should be verified; restarting the EventSentry will re-create the file.
580 Action "%1" was unable to create a mailslot for host "%2" due to error: %3
581 Action "%1" was unable to send a notification to the (remote) Growl listener. Make sure the remote host is running Growl, accepting network messages, and no firewall is blocking traffic.
590 Action "%1" was unable to send trap to SNMP host "%2" due to error: %3
600 Action "%1" was unable to connect to SNPP host "%2" due to error: %3
601 Action "%1" was unable to send a message to pager ID "%2" due to error: %3
602 Action "%1" was unable to send the message due to error: %2
611 Unable to connect to the SCM (service control manager) due to error %1 (%2). The action "%3" failed to execute.
612 Unable to open the requested service (%1) due to error %2 (%3). The action "%4" failed to execute.
613 Unable to send the requested control to service %1, most likely due to error %2 (%3). The action "%4" failed to execute.
614 The service %1 could not be restarted because the it could not be stopped in the first place. The notification "%2" failed to execute.
615 The requested service control was successfully sent to service %1, however the current service status is still %2. Please monitor the status of the %1 service to ensure it is in the desired state.
616 The process "%1" was terminated successfully. Instances Terminated: %2 Affected Process Identifiers (PIDs): %3
617 The process "%1" could not be terminated due to error "%2".
620 Action "%1" was unable to initiate a system shutdown/reboot due to error: %3
630 Action "%1" was unable to connect to Jabber host "%2" due to error: %3
631 Action "%1" was unable to send a message to chat room "%2" due to error: %3
640 Action "%1" was unable to submit an event to "%2" due to error "%3".
641 Action "%1" was successfully submitted event with number %3 to "%2".
642 Action "%1" was successfully submitted event with number %3 to "%2". Result: %4
900 The remote collector service has been unavailable for an extended period of time and the agent has been caching data locally. The size of the local backup file has reached the limit of %1 Mb, and collected data will now be discarded. Restore connectivity to the collector as soon as possible.
Criticial
901 The remote collector service has been unavailable for an extended period of time and the agent has been caching data locally. The remaining size of the %1 drive is below the limit of %2 Mb, and collected data will now be discarded to avoid that all remaining space on the %1 drive will be consumed. Restore connectivity to the collector as soon as possible.
902 The backup file "%1" has been parsed successfully and %2 items were submitted for processing.
903 The backup file "%1" could not be opened for processing due to error "%2".
904 The backup file "%1" (%2 KB) will not be processed since a connection with the collector cannot be established.
905 The EventSentry %2 is unable to establish a secure connection with any of the listed collectors: %1 See KB article 348 (https://www.eventsentry.com/kb/348) for help on troubleshooting connectivity issues.
906 The EventSentry %2 is unable to establish a clear text connection with any of the listed collectors: %1
907 The certificate provided by the collector "%1" does not match the locally cached certificate. The remote collector is considered unknown and the agent will now disconnect. The remote certificate is shown below: %2
908 The EventSentry %3 disconnected from collector %1@%2.
910 The EventSentry %4 successfully established a secure connection with the collector (%1:%2 from local port %5). %3
911 The EventSentry %3 successfully established a clear text connection with the collector (%1:%2 from local port %4).
912 The EventSentry %1 was unable to connect securely to any of the configured collectors and will now attempt to fallback to a non-secure connection.
914 The EventSentry %2 disconnected from the remote collector since it was unable transmit data. The agent will attempt to reconnect and transmit data in %1 seconds.
915 The remote collector did not accept the local authentication credentials, the agent will attempt to reconnect in %1 seconds.
916 The remote collector did not confirm receipt of the local authentication credentials, the agent will attempt to reconnect in %1 seconds.
920 A configuration or agent update was received from the collector but did not pass checksum validation, most likely due to a transmission error. The update file was discarded as a result. Please use the management console to push configuration updates or manage remote agents until the issue is resolved.
921 The remote collector has not acknowledged %1 bytes of data sent by the local agent over the %2 connection. This may indicate high latency or an issue with the remote collector, it's recommended that you ensure that data sent from this host is present in the web reports. The agent will now throttle data sent to the collector until the collector acknowledges receipt of sent data.
922 The remote collector has not acknowledged %1 bytes of data sent by the local agent over the %2 connection (see previous 921 event). This may indicate high latency or an issue with the remote collector, it's recommended that you ensure that data sent from this host is present in the web reports. The agent will now disconnect from the collector attempt to reconnect in %3 minutes.
1009 A boot scan is currently in progress and has taken more than %3 minutes. The agent is currently processing the %1 event log, %2 records have been processed so far.
1010 The boot scan for event log %1 is complete. %2 events were processed in %3 seconds.
1011 The agent was unable to find the local hostname (%1, %2) in the configuration, most likely due to a license problem. Make sure that only as many full hosts are configured in the EventSentry groups as licenses are installed. Heartbeat-Only hosts which have the "Monitor Agent" option set count towards full host licenses.
1012 Unable to start service because the End User License Agreement was not accepted
1013 Unable to start service because of an invalid configuration, contact support.
1014 The EventSentry agent is ready. Version: %1 Configuration Revision: %9 Codepage: %2 Hostname: %7 Group: %8 The following packages are assigned: Event Log Packages: ------------------- %3 Log File Packages: ------------------- %4 System Health Packages: ----------------------- %5 Security and Compliance Packages: ----------------------------- %6 Validation Script Packages: ----------------------------- %10
1015 Since the EventSentry agent cannot find itself in any of the available groups, it will use "Unknown" as the associated group name and may not be able to load all assigned packages. See https://www.eventsentry.com/kb/373 for more information.
1017 The EventSentry agent is stopped
1018 The EventSentry agent is stopping
1019 Unable to start service because no valid license was found
1021 The backup file for action "%1" has events queued, but the "%1" action is currently disabled. The backup file for this action has been backed up to file "%2" and the original file has been deleted.
1022 EventSentry was unable to process the backup queue file "%1" for action "%2" because it was unable to create a backup copy. The error was: "%3".
1023 EventSentry created a backup copy of the backup queue file for action "%1", but the backup file failed a checksum verification. Previously queued events will not be processed. Please see the agent debug log file for possible indicators of an error.
1024 The number of events cached for action "%1", which has been unreachable, exceeded %2 events. If this action is no longer in use then you should disable or delete the action so that events are no longer cached. EventSentry will continue to cache events until the maximum size of the temporary backup file "%6" (%3 Mb) is reached. %4 events are currently cached, the backup file size is %5 Mb.
1025 An attempt to store collected events in the database for action "%1" is taking more than %2 seconds, and events are not currently being added to the database in real-time. This might indicate that the database is busy with a maintenance schedule or other tasks that block INSERT statements. This is a warning message only and can be ignored if you are running a maintenance job on this database, but you should ensure that EventSentry is correctly storing events in this database.
1026 The database action "%1" that has previously been unable to record events in the database in real-time has finished inserting events and is available again.
1027 A backup file for action "%1" has been found and EventSentry will now attempt to deliver the previously failed messages. The backup file is %2 bytes big and contains %3 events.
1028 The backup file for action "%1" has been processed and EventSentry attempted to re-deliver all events. Any errors reported by the respective notification engine will be logged separately.
1029 The ODBC driver for action "%1" in the %3 has been automatically adjusted to use "%2", which is the latest version installed on this system. Dynamically added connection options: %4.
1030 The EventSentry agent successfully installed the %1 ODBC driver, using %2 as the installation source. This ODBC driver is required for EventSentry to connect to the central %1 database. If software monitoring is enabled, then you should receive a notification when the ODBC driver was successfully installed, it will also appear in the control panel as "%3". You may uninstall the %1 ODBC driver when you are no longer using a %1 database, by executing the following command: "msiexec /x %2"
1031 The EventSentry agent was unable to install the %1 ODBC driver (%3), using %2 as the installation source. This driver is not currently installed but required for the agent to communicate with a central %1 database. Please review the Application and System event log to determine why this MSI-based installation package could not be automatically installed. You can also install the driver manually by launching "%2".
1032 The EventSentry agent successfully upgraded the %1 ODBC driver from version %2 to %3.
1033 The configuration for the agent was automatically re-read since a service change enabled/disabled one or more auto-assigned packages. The following packages are assigned: Event Log Packages: ------------------- %1 Log File Packages: ------------------- %2 System Health Packages: ----------------------- %3 Security and Compliance Packages: ----------------------------- %4 Validation Scripts Packages: ----------------------------- %5
1034 The configuration for the agent (service) could not be re-read because the "%1" feature/function is busy and preventing an on-line configuration update. The agent will try again in 5 minutes, or the EventSentry service can be restarted to force a configuration update.
1035 A new configuration (revision %6) has been applied successfully after an update was received from host %1. The following packages are assigned: Event Log Packages: ------------------- %2 Log File Packages: ------------------- %3 System Health Packages: ----------------------- %4 Security and Compliance Packages: ----------------------------- %5 Validation Scripts Packages: ----------------------------- %7
1036 User %1 has successfully connected to host %3 from host %2 with the EventSentry management application.
1037 The agent was unable to update the configuration from the registry because the agent is busy. The agent tried for %1 minutes but gave up. Please try again or restart the agent.
1038 The EventSentry agent has successfully adjusted the permissions of %2. %1 ACE entries (one of the following: Users, Power Users, Everyone) were removed to increase security.
1039 The EventSentry agent has successfully changed the buffer size from %1 bytes to %2 bytes after the Operating System returned the following error: "The data area passed to a system call is too small".
1040 The EventSentry agent was unable to queue more events for delayed reading. A total of %1 events are already queued for a delayed reading, which might indicate that the EventSentry agent is having difficulties monitoring the event log consistently. Please make sure that no events are being missed by comparing the event logs with the EventSentry targets (e.g. database). You may also contact NETIKUS.NET support by visiting https://www.eventsentry.com/ or by sending an email to support@netikus.net.
1041 When monitoring the %1 event log, the EventSentry agent missed events between number %2 to %3. EventSentry will attempt to read those events at a later time to make sure that all events from the %1 log are being processed.
1042 The EventSentry agent determined that the default ADMIN$ share does not exist and that the directory C:\Program Files\EventSentry\RemoteUpdate is not shared as ES$. In order for this agent to receive remote configuration updates from the EventSentry Management Console, you will have to share the C:\Program Files\EventSentry\RemoteUpdate as ES$ to only Administrators.
1043 The EventSentry agent determined that both the C:\Program Files\EventSentry\RemoteUpdate directory and the ES$ share exist. The agent will continue to monitor the C:\Program Files\EventSentry\RemoteUpdate for configuration updates.
1044 The EventSentry agent determined that both the ADMIN$ share and the C:\Program Files\EventSentry\RemoteUpdate directory exist. Since the C:\Program Files\EventSentry\RemoteUpdate directory is not shared as ES$, the ADMIN$ share will be used instead. If you would like remote update to use the C:\Program Files\EventSentry\RemoteUpdate directory then you will have to share this directory as ES$, giving only Administrators access to it.
1045 The EventSentry agent determined that neither the ADMIN$ share nor the C:\Program Files\EventSentry\RemoteUpdate directory exists. As such, this agent will not be able to receive configuration updates from the central management console. You can either re-enable the ADMIN$ share, or create the C:\Program Files\EventSentry\RemoteUpdate directory and share it as ES$. The ES$ share should only be accessible to Administrators. You will have to restart the agent after you created the ES$ share.
1046 The EventSentry agent received a configuration update, but an active ODBC connection is blocking the update. The agent cannot re-read the new configuration until the database connection is complete and all queued events are sent to the database. You can restart the EventSentry service to force an update, but some events might not be transferred to the database.
1047 Since the previously active ODBC connection is still active, the EventSentry agent has re-read the configuration. It is recommended that you restart the EventSentry agent if changes to the actions were made.
1048 Monitoring component %1 is unable to connect to database "%2" for an extended period of time, which is currently locked by component %3 (thread id %4). This may indicate a stalled connection attempt; if this agent is not reporting data to the database then the EventSentry service should be restarted.
1049 The monitoring feature %2 which has previously been blocking while connecting to the EventSentry database "%1", has resumed. This does not mean that the database connection was successful. If this computer has a reasonably fast connection to the database (LAN), then you should review the Application event log for any potential database connection problems.
1050 A connection attempt for action "%1" has been blocking for more than %2 seconds, indicating either a network connection problem between the agent and the database, or a problem with the responsiveness of the database server. You should restart the EventSentry agent as soon as possible.
1051 The EventSentry agent missed events while monitoring the %1 event log. EventSentry cannot rescan the event log since the missing events are no longer available, which usually happens when the size of the event log is too small. It is recommended that you increase the size of the %1 event log.
1052 The EventSentry agent has not received any events from the event logging subsystem in Windows for %1 hours. This may indicate a critical issue with the current service instance, and the EventSentry Agent will restart now to recover.
1053 The EventSentry Agent will restart to recover from an unknown problem (%1). If you see this message frequently, then set the "Debug Level" under "Services" in the management console to "High" and contact EventSentry support.
1054 The EventSentry agent missed events between number %2 and %3 while monitoring the %1 event log. %4 events were successfully processed after an attempt to rescan the event log for the missing events.
1060 The queue size for action %1 reached %2 events, resulting in excess caching of events by the agent. Please verify that the action is reachable.
1061 The background thread for action %1 was unresponsive and a restart was attempted. Result: %2.
1070 An agent update has been received from the collector and the EventSentry agent will now be updated from v%1 to v%2.
1071 Unable to apply an agent update from the collector: %1. Additional Error Information: %2.
1072 The agent update has been applied but the service could not be (re)started. The agent binary will now be reverted back to version v%1.
1073 The local agent has been successfully reverted back to v%1 and restarted.
1074 The local agent could not be reverted back to v%1. Upgrade the agent on this machine using the management console (Other Actions -> Upgrade Agent(s)). Additional Information: %2
1075 The local agent was successfully upgraded to build v%1.
1076 The local agent was successfully upgraded to build v%1 but the status of the service could not be verified.
1080 The %1 field of filter %2 is incorrect (%3). Either all or no strings in the %1 field will need to use the negation character !. For example, the following configuration is incorrect: !NTBackup, Print The following examples show a correct configuration: !NTBackup,!Print DiskQuota,DNSApi
1090 %1 was run for %2 seconds with the result shown below. Return Code was %3. %4
1091 The process %1 could not be created due to the following error: %2
1092 The process %1 exceeded the maximum allowed time interval of %2 seconds. EventSentry was unable to terminate the process due to the following error: %3
1093 The process %1 exceeded the maximum allowed time interval of %2 minute(s). The process was terminated. Please increase the timeout interval for this process in the EventSentry management console (Actions -> Process Action -> Options).
1094 %1 was executed successfully.
1095 The process "%1" could not be execute because a thread did not process a data structure in the specified time period (%2 seconds).
1100 The EventSentry Remote Update Utility has completed, %1 host(s) were updated successfully.
1101 The EventSentry Remote Update Utility has completed. %1 host(s) were updated successfully, %2 host(s) failed. The following hosts could not be updated: %3.
1102 The EventSentry Remote Update Utility has completed. %1 host(s) were verified successfully.
1103 The EventSentry Remote Update Utility has completed. %1 host(s) were verified successfully, %2 host(s) failed. The following hosts could not be verified: %3.
1205 The custom event log %1 does not exist on this system and will not be monitored.
1256 The temporary file %1 has been found but no filter referencing this target (%2) is configured for a summary notification. The file has been deleted.
1400 EventSentry was unable to adjust the permissions on folder "%1" due to error "%2". If the embedded scripts contain sensitive information such as usernames and passwords then you should correct this problem and/or adjust the permissions on the script files.
1401 EventSentry was unable to create file "%1" due to error "%2". Please make sure that no other process is currently accessing the file, and that the agent has full permissions to write to this file.
1402 EventSentry was unable to delete the temporary file "%1" during the service shutdown due to error "%2". Please make sure that no other process is currently accessing the file, and that the agent has full permissions to write to this file.
7000 The default SNMP v3 engine ID for action "%1" was set to 0x%2.
8000 Text matched one or more filter rules: Name: %3 Path: %1 Search Pattern: %5 %2 Context: %4
8001 EventSentry is caching more than 1024 files in the monitored directory %1. To keep the resource consumption of the EventSentry agent low it is recommended that you move old files to a sub directory or another directory.
8002 A line in the previously monitored file %1 did not contain a CRLF and as such was not processed according to the filter rule. The line from the text file is shown below: %2
8050 The log file "%1" which is mapped to the file definition "%2" does not contain enough field names (delimiters) and was not processed. Please make sure that the file definition setup in EventSentry matches the layout of the monitored log file. The first 128 characters of the encountered line are shown below: %3
8051 The log file "%1" which is mapped to the file definition "%2" encountered a string that needed to be truncated. The maximum string length for this field is %3 characters, but the parsed string length was %4 characters. This message will not be logged again for this file type. The original string was: %5
10100 The status for service %1 (%2) changed from %3 to %4. Additional Service Information: Startup type: %5 Executable: %6 Service account: %7 How do I configure this feature? https://www.eventsentry.com/kb/356
10101 A service was added: Name: %1 (%2) Status: %3 Startup type: %4 Executable: %5 Service account: %6 How do I configure this feature? https://www.eventsentry.com/kb/356
10102 A service was removed: %1 (%2). Additional Service Information: Status: %3 Startup type: %4 Executable: %5 Service account: %6 How do I configure this feature? https://www.eventsentry.com/kb/356
10103 The service %1 (%2) is now being monitored. Additional Service Information: Status: %3 Startup type: %4 Executable: %5 Service account: %6
10104 The service %1 (%2) will not be monitored anymore. Last service status was %3.
10105 The following %1 service(s)/driver(s) are configured to AUTOSTART but are currently not running: %2 How do I configure this feature? https://www.eventsentry.com/kb/356
10106 Unable to connect to the Service Control Manager (SCM), services and drivers cannot be monitored.
10107 Unable to enumerate services, services and drivers cannot be monitored.
10108 The state of service %1 was %2, requested state is %3. EventSentry successfully changed the service status to %3.
10109 The state of service %1 is %2, requested state is %3. EventSentry was not able to change the service status due to the following error: %4.
10110 The Startup Type for service %1 (%2) changed from %3 to %4. Additional Service Information: Status: %5 Executable: %6 Service account: %7 How do I configure this feature? https://www.eventsentry.com/kb/356
10111 The user account for service %1 (%2) changed from %3 to %4. Additional Service Information: Status: %5 Startup type: %6 Executable: %7 How do I configure this feature? https://www.eventsentry.com/kb/356
10112 The executable for service %1 (%2) changed from "%3" to "%4". Additional Service Information: Status: %5 Startup type: %6 Service account: %7 How do I configure this feature? https://www.eventsentry.com/kb/356
10114 The status for service %1 (%2) remains %3. Additional Service Information: Startup type: %4 Executable: %5 Service account: %6 How do I configure this feature? https://www.eventsentry.com/kb/356
10150 The status for driver %1 (%2) changed from %3 to %4. Additional Service Information: Startup type: %5 Executable: %6 How do I configure this feature? https://www.eventsentry.com/kb/356
10151 A driver was added: Name: %1 (%2) Status: %3 Startup type: %4 Executable: %5 How do I configure this feature? https://www.eventsentry.com/kb/356
10152 A driver was removed: Name: %1 (%2) Status: %3 Startup type: %4 Executable: %5
10153 The driver %1 (%2) is now being monitored. Additional Driver Information: Status: %3 Startup type: %4 Executable: %5
10154 The driver %1 (%2) will not be monitored anymore. Last driver status was %3.
10158 The state of driver %1 was %2, requested state is %3. EventSentry successfully changed the driver status to %3.
10159 The state of driver %1 is %2, requested state is %3. EventSentry was not able to change the driver status due to the following error: %4.
10160 The Startup Type for driver %1 (%2) changed from %3 to %4. Additional Driver Information: Status: %5 Executable: %6 How do I configure this feature? https://www.eventsentry.com/kb/356
10162 The executable for driver %1 (%2) changed from "%3" to "%4". Additional Driver Information: Status: %5 Startup type: %6 How do I configure this feature? https://www.eventsentry.com/kb/356
10164 The status for driver %1 (%2) remains %3. Additional Driver Information: Startup type: %4 Executable: %5 How do I configure this feature? https://www.eventsentry.com/kb/356
10200 %1 was run for %2 seconds with the result shown below. Return Code was %3. %4
10201 The process %1 could not be created due to the following error: %2
10202 The process %1 exceeded the maximum allowed time interval of %2 minute(s). EventSentry was unable to terminate the process due to the following error: %3
10203 The process %1 exceeded the maximum allowed time interval of %2 minute(s). The process was terminated. Please increase the timeout interval for this process in the management console (System Health -> Application Scheduler).
10204 %1 was executed successfully.
10205 The process %1 exceeded the maximum allowed time interval of %2 minute(s). EventSentry was unable to terminate the process due to the following error: %3 %4 child processes were successfully terminated.
10206 The process %1 exceeded the maximum allowed time interval of %2 minute(s). The process and %3 child process(es) was terminated. Please increase the timeout interval for this process in the management console (System Health -> Application Scheduler).
10210 The process %1 was not started because the script is configured for local isolation and another instance of the same script is already running.
10211 The process %1 was not started because a script which is configured for global isolation (%2) is already running.
10300 The %1 event log was successfully cleared.
10301 Event log was successfully backed up: Event log: %1 File: %2 File size: %3 KB Checksum: %4
10302 Event log was successfully backed up and cleared: Event log: %1 File: %2 File size: %3 KB Checksum: %4
10303 The %1 event log could not be cleared due to the following error: %2.
10304 The %1 event log could not be backed up to file %2 due to the following error: %3.
10305 The %1 event log could not be backed up to file %2 due to the following error: %3.
10306 The event log backup file "%1" could not be compressed due to the following error: %2.
10307 The event log backup file "%1" appears to have been compressed successfully, but the compressed event log backup file "%2" could not be verified due to error "%3". The original event log backup file will not be deleted.
10401 %2 instance(s) of process "%1" on host %4 are active, but %3 instance(s) is/are required.
10402 %2 instances of process "%1" is/are currently active on host %3.
10410 A new process is listening for incoming TCP connections: Process Name: %1 (PID=%2) Local TCP Port: %3 Local Address: %4 Note: Connection requests may be blocked if a firewall is active.
10411 A process previously listening for incoming TCP connections is no longer actively listening on this port: Process Name: %1 (PID=%2) Local TCP Port: %3 Local Address: %4
10500 Free disk space for drive %1 (%5) on host %6 is below the configured limit of %2 percent. %3 percent of disk space (%4 Mb) are currently available on drive %1. Top %7 Directories: %8 Top %7 Files: %9 How do I configure this feature? https://www.eventsentry.com/kb/357
10501 Free disk space for drive %1 (%4) on host %5 is below the configured limit of %2 Mb. %3 Mb of disk space are currently available on drive %1. Top %6 Directories: %7 Top %6 Files: %8 How do I configure this feature? https://www.eventsentry.com/kb/357
10502 Trend analysis has determined unusual high disk usage on drive %1. The average recorded trend on drive %1 was %2 kb, the current trend was %3 kb, an increase of %4%. If this trend change is expected (for example, caused by a daily backup routine) then you will see this message two more times before the pattern is recognized. With the recorded trend, disk space will be exhausted in %5 days, with the current trend in %6 days.
10503 EventSentry was unable to access drive %1 due to error "%2". This drive will not be monitored until the problem is resolved.
10504 Directory and file analysis of drive %1 has been initiated by an earlier 10500 or 10501 event and is now complete. Top %2 Directories: %3 Top %2 Files: %4
10505 Enumerating the largest %1 files on drive %2 took longer than %3 seconds %4 times in a row, and large file monitoring has been temporarily disabled on drive %2 for 24 hours.
10509 The percentage-based threshold on drive %1 has been dynamically adjusted from %2 percent to %3 percent based on the total drive size of %4. A low disk space alert will be triggered when the available space on this volume falls below %5.
10510 The %1 size of folder "%2" exceeded the configured limit of %3 bytes. Folder Information: Logical Size: %4 bytes Physical Size: %5 bytes Files: %6 How do I configure this feature? https://www.eventsentry.com/kb/358
10511 The %1 size of folder "%2" is below the configured limit of %3 bytes. Folder Information: Logical Size: %4 bytes Physical Size: %5 bytes Files: %6 How do I configure this feature? https://www.eventsentry.com/kb/358
10512 The maximum file count of %1 files in folder "%2" was exceeded, %3 files were found. Folder Information: Logical Size: %4 bytes Physical Size: %5 bytes Files: %3 How do I configure this feature? https://www.eventsentry.com/kb/358
10513 Folder "%2" contains %3 files, which is below the minimum of %1 files. Folder Information: Logical Size: %4 bytes Physical Size: %5 bytes Files: %3 How do I configure this feature? https://www.eventsentry.com/kb/358
10550 Free disk space for drive %1 (%5) on host %6 is back above the configured limit of %2 percent. %3 percent of disk space (%4 Mb) are currently available on drive %1. How do I configure this feature? https://www.eventsentry.com/kb/357
10551 Free disk space for drive %1 (%4) on host %5 is back above the configured limit of %2 Mb. %3 Mb of disk space are currently available on drive %1. How do I configure this feature? https://www.eventsentry.com/kb/357
10560 The %1 size of folder "%2" is back below the configured limit of %3 bytes. Folder Information: Logical Size: %4 bytes Physical Size: %5 bytes Files: %6. How do I configure this feature? https://www.eventsentry.com/kb/358
10561 The %1 size of folder "%2" is back above the configured limit of %3 bytes. Folder Information: Logical Size: %4 bytes Physical Size: %5 bytes Files: %6. How do I configure this feature? https://www.eventsentry.com/kb/358
10562 The number of files (%5) in folder "%1" is back below the configured limit of %2 files. Folder Information: Logical Size: %3 bytes Physical Size: %4 bytes Files: %5. How do I configure this feature? https://www.eventsentry.com/kb/358
10563 The number of files (%5) in folder "%1" is back above the configured limit of %2 files. Folder Information: Logical Size: %3 bytes Physical Size: %4 bytes Files: %5. How do I configure this feature? https://www.eventsentry.com/kb/358
10600 Event log filter %1 exceeded the configured threshold (%2 entries / %3 second(s)). %4 events (out of a total of %5) were dropped by this filter. You can review the dropped events in the event log or the web reports. The matching events and their frequency were: %6
10601 Event log filter %1 has reached the configured threshold (%2 entries / %3 second(s)). The matching events and their frequency were: %4
10602 Event log filter %1 has reached the configured threshold (%2 entries / %3 second(s)). Events matching this filter will now be processed. The matching events and their frequency were: %4
10603 Event log filter %1 has reached or exceeded the configured threshold (%2 entries / %3 second(s)). %4 events were processed during the interval. The matching events and their frequency were: %5
10620 No event matching filter %1 has occurred in the event log in the configured time period. According to the schedule, at least one event matching filter %1 should have been logged during the last %2 minutes.
10621 No event matching filter %1 has occurred in the event log in the last %2 minute(s). According to the schedule, at least one event matching filter %1 should be logged every %2 minute(s).
10650 The filter chain for event log package %1 is complete. Duration: %2 second(s) Insertion Strings (if any): %3
10700 The EventSentry debug log file %1 has reached a size of %2 bytes. We recommend changing the debug logging option (Service Options -> Debug and Logging) to "Low" or "Medium" unless you are beta-testing or have been instructed by netikus.net support to activate debug logging.
10803 The currently configured audit policies on this system were insufficient for one or more Security and Compliance package. One or more errors occured while attempting to configure all required policies. The following audit policies have been changed: %1 The following audit policies were already configured correctly: %2 The following audit policies could not be set: %3 Error: %4. Security and Compliance will not work reliably if not all required audit policies are configured correctly. If this computer is part of a domain environment, then it is recommended that you configure the respective audit policies with a group policy.
10804 EventSentry determined that all audit policies listed below which are required for Security and Compliance are configured correctly: %1
Compliance
10805 The currently configured audit policies on this system were insufficient for one or more Security and Compliance package and have been adjusted. The following audit policies have been changed: %1 The following audit policies were already configured correctly: %2 If this computer is part of a domain environment, then it is recommended that you configure the respective audit policies with a group policy.
10807 The requested auditing policies have been adjusted, but the "Log Size" properties of the Security event log are not configured properly. In order for tracking features to work reliably it is recommended that you reconfigure the security event log (with "Event Viewer") to "Overwrite events as needed".
10809 EventSentry was configured to disable auditing for one or more audit policies. The following audit policies have been configured to not generate audit events: %1 The following audit policies are not currently generating audit events: %2 The following audit policies are generating audit events, but could not be changed: %3 Error: %4
10815 EventSentry will now be processing the checksum of all monitored directories. This process may take several minutes, depending on the hardware and on the number and size of the monitored files. Event 10816 or 10817 will be logged once all directories have been successfully initialized.
10816 EventSentry has successfully processed the checksum of all files in directory "%1". Initialization took %2 second(s).
10817 EventSentry has successfully processed the checksum of all monitored directories and object access activity will now be monitored. Initialization of all directories took %1 second(s).
10820 EventSentry has reached the maximum buffer size of %1 items for its checksum buffer in the "File Tracking" feature. Please consider changing the "Event Analysis" option to "Normalize" for one or more directories.
10901 The configured temperature limit of %1 degrees (%3) has been exceeded, the current temperature is %2 degrees (%3).
10902 The configured humidity limit of %1% has been exceeded, the current humidity level is %2%.
10903 EventSentry was unable to find a temperature and/or humidity sensor on serial port %1. Please make sure the device is connected properly. Additional troubleshooting information: %2
10904 The database write interval for environment monitoring is set too small. The interval was automatically adjusted to %1 seconds.
10906 The current temperature is below the configured limit of %1 degrees %3 %4 (%5). The current temperature is %2 degrees (%3).
10907 The current humidity level of %2% (%3) is below the configured limit of %1%.
10908 The current temperature of %3 degrees %4 (%5) is outside the configured range (%1%4 to %2%4).
10909 The current humidity level %3% (%4) is outside the configured range (%1% to %2%).
10910 The current temperature of %3 degrees %4 (%5) is back in the configured range (%1%4 to %2%4).
10911 The current humidity level of %3% (%4) is back in the configured range (%1% to %2%).
10912 Motion sensor (%1) detected motion.
10913 Smoke sensor (%1) detected smoke.
10914 Water sensor (%1) detected water.
10915 EventSentry failed to detect the required self-test of the smoke sensor which is run every 24 hours. Please press the TEST button on the smoke sensor for at least 30 seconds to make sure that the sensor works correctly and an alert is generated by EventSentry.
10916 The attached %1 sensor reported an error, or no sensor is attached. This feature has been turned off.
11000 Host %1 [%6] in group "%2" changed its PING status from %3 to %4. The reason for the status change was: "%5". %8 %9
11001 Host %1 [%6] in group "%2" changed its AGENT status from %3 to %4. The reason for the status change was: "%5".
11002 Host %1 [%7] in group "%2" changed the status of TCP port %6 from %3 to %4. The reason for the status change was: "%5".
11004 The EventSentry Heartbeat monitor is waiting for the system to finish booting and will start monitoring in %1 seconds.
11005 The EventSentry Heartbeat monitor is ready and will now start monitoring the configured hosts.
11006 The EventSentry Heartbeat agent was unable to find the required HTML template files in %1\Heartbeat. Please make sure that the following files exist in %1\Heartbeat: template_status_start.html template_history_start.html template_end.html image subdirectory These files are optional if you are already logging heartbeat information to a database.
11007 The EventSentry Heartbeat agent was unable to find the required HTML template files and is not configured to log heartbeat status information to a database. The heartbeat agent will only notify you of host status changes through the event log.
11008 The database action specified for the heartbeat monitoring service is invalid and database logging has been disabled. Please review the configuration ("Global Options") and restart the heartbeat monitoring service.
11009 The Heartbeat Monitor detected that the EventSentry service is currently not running. If the EventSentry service is not running, then event log alerts generated by the Heartbeat Agent cannot be forwarded to a notification. You can disable this check under "Global Options -> Heartbeat".
11010 The EventSentry Heartbeat service encountered an unrecoverable error and will now automatically restart. If you see this message on a regular basis, then set the "Debug Level" under "Heartbeat" to "High" and contact support@netikus.net the next time this message is generated.
11011 Scanning of host %1 was forcefully aborted because the scan duration (%3) exceeded the maximum allowed time (%2 seconds). Review the monitoring settings of this host, and optionally disable SNMP, Agent and/or TCP checks on this host.
11012 Scanning of host %1 was interrupted %3 consecutive times because the scan duration exceeded the maximum allowed time (%2 seconds). TCP Port and/or SNMP scanning may be incomplete on this host.
11014 SNMP monitoring of host %1 has failed %2 consecutive times and is now disabled. To re-enable SNMP monitoring of host %1, restore SNMP connectivity and restart the EventSentry Heartbeat Monitor service.
11015 %4 monitoring of host %1 has failed %2% of the time over the last %3 minutes and is now disabled. To re-enable SNMP and/or agent monitoring of host %1, restore full connectivity to the remote host, locate the host in the management console and click the "Retry" button in the summary view.
11016 The following error occurred while communicating, or attempting to communicate with database action "%1": "%2". Please verify that the database is accessible and the database is on the latest schema.
11017 The connection with database action "%1" has been reestablished, the database is no longer offline.
11018 Starting with EventSentry build 3.2.1.28, the heartbeat agent can query the EventSentry database to determine a remote agent status, instead of querying the remote agent status using the Windows API. This can drastically improve the monitoring speed and is recommended for networks consisting of 50 or more Windows hosts. To enable this functionality, the following SQL query will need to be executed on the EventSentry database: --Built-In Database (PostgreSQL) REVOKE ALL ON TABLE eventsentry.essysinfo FROM eventsentry_svc; GRANT SELECT, UPDATE, INSERT, DELETE ON TABLE eventsentry.essysinfo TO eventsentry_svc; -- SQL Server GRANT SELECT ON ESSysinfo (UptimeTimestamp) TO eventsentry_svc -- MySQL GRANT SELECT (computer, Uptime, UptimeMax, UptimeTimestamp), INSERT, UPDATE, UPDATE (UptimeTimestamp, lastserverinventoryupdate), DELETE ON essysinfo TO eventsentry_svc It is also recommended to set the "Refresh uptime every" interval in the "Inventory" System Health package to 5 minutes.
11019 Monitoring of the remote EventSentry agent on host %1 has been unsuccessful %2 times in a row. Remote RPC agent monitoring will now be disabled on host %1.
11020 The heartbeat agent will monitor the following host using SNMP: Host: %1 SNMP Version: %2 System Description:%3
11021 EventSentry was unable to retrieve SNMP data from host %1 and cannot monitor this host using SNMP. This event is being logged because this host was successfully monitored via SNMP in the past. To retry, open the management console, select the host and click the retry button on the top right.
11022 Monitoring of the remote EventSentry agent on host %1 took more than %2 seconds (%3 seconds). Remote agent monitoring via RPC will now be disabled on host %1.
11023 SNMP monitoring on host %1 has been unsuccessful for more than %2 minutes and has now been disabled. To retry, open the management console, select the host and click the retry button on the top right.
11024 The database action "%1" is currently using the legacy SQL Server ODBC driver "{SQL Server}" which may cause performance and stability issues. It is recommended to install the latest ODBC driver for SQL Server, see https://www.eventsentry.com/kb/378 for additional details.
11050 The PING status of host %1 (%2) remains at %4 due to error "%5". Current downtime is %7 minutes. %9
11051 The AGENT status of host %1 (%2) remains at %4 due to error "%5".
11052 The status of TCP port %6 on host %1 (%2) remains at %4 due to error "%5".
11090 The Heartbeat Agent was unable to retrieve the stored authentication credentials for computer "%1", using user "%2". Please make sure that the "EventSentry Heartbeat Monitor" service is running under the same user account that configured the credentials for this group/computer in the EventSentry Management Console.
11100 A new configuration was applied successfully.
12000 Application %1 (%2) was installed. Additional Information: Publisher: %3 Installation Directory: %4 Version: %5 Platform: %7 User: %8 Currently logged on user(s): %6
12001 Application %1 (%2) was uninstalled. Additional Information: Publisher: %3 Installation Directory: %4 Version: %5 Platform: %7 User: %8 Currently logged on user(s): %6
12002 Application %1 registered itself in the registry key HKLM\%2 and will be automatically run when a user logs into the system. Currently logged on user(s): %3
12003 The registry value %1 in key HKLM\%2 changed from "%3" to "%4". All files specified in this value will be automatically run when a user logs into the system. Currently logged on user(s): %5
12004 Application %1 was removed from the registry key HKLM\%2 and will no longer be run when a user logs into the system. Currently logged on user(s): %3
12005 The application %1 registered itself in the directory %2 and will be automatically run when a user logs into the system. Currently logged on user(s): %3
12006 The shortcut %1 (using file %2) registered itself in the directory %3 and will be automatically run when a user logs into the system. Currently logged on user(s): %4
12007 The shortcut %1 (using file %2) was removed from directory %3 and will no longer run when a user logs into the system. Currently logged on user(s): %4
12008 Application %1 was added to the registry key HKLM\%2 and will be automatically run when the system boots. Currently logged on user(s): %3
12009 Application %1 was removed from the registry key HKLM\%2 and will no longer be run the system boots. Currently logged on user(s): %3
12010 The application %1 registered file %2 in registry key %3 and might be automatically run when a user logs into the system. Please see the help file (search for ACTIVE SETUP) for more information. Currently logged on user(s): %4
12011 Application %1 (using file %2) was removed from the registry key HKLM\%3 and will no longer be run when a user logs into the system. Currently logged on user(s): %4
12012 Error %1 (%2) occurred while trying to monitoring registry key %3. Please restart the EventSentry agent or notify NETIKUS.NET support if this problem persists. Software/Hardware monitoring will be incomplete until the issue is resolved.
12013 The explorer extension DLL %1 (using file %2) was removed from the registry key HKLM\%3 and will no longer be loaded into explorer.exe. Currently logged on user(s): %4
12014 The explorer extension DLL %1 (using file %2) registered itself in registry key %3 and will be automatically loaded into explorer.exe when a user logs into the system. Currently logged on user(s): %4
12020 The %1 browser extension "%2" was added to user %4: Web Browser: %1 Name: %2 Version: %3 User: %4 Enabled: %5
12021 The %1 browser extension "%2" was modified for user %4: Web Browser: %1 Name: %2 Version: %3 User: %4 Enabled: %5 Field Changed: %6 ("%7" -> "%8")
12022 The %1 browser extension "%2" was removed from user %4: Web Browser: %1 Name: %2 Version: %3 User: %4 Enabled: %5
12030 The amount of physically installed memory changed from %1 Mb to %2 Mb.
12031 The number of installed processors changed from %1 to %2.
12032 The number of installed floppy drives changed from %1 to %2.
12033 The number of installed CDROM drives changed from %1 to %2.
12034 The number of installed DVD drives changed from %1 to %2.
12035 The number of removable drives changed from %1 to %2.
12036 The link speed of adapter %1 changed from %2 to %3.
12037 The BIOS version changed from "%1" to "%2".
12040 A %1 drive has been added: Model: %2 DeviceID: %3 Serialnumber: %4 Size: %5 Mb Interface: %1 S.M.A.R.T. Status: %6 Firmware Revision: %7 Partitions: %8
12041 A %1 drive has been removed: Model: %2 DeviceID: %3 Serialnumber: %4 Size: %5 Mb Interface: %1 S.M.A.R.T. Status: %6 Firmware Revision: %7 Partitions: %8
12042 The drive "%2" (%3) reported the SMART status error "%6". Drive Details: Model: %2 DeviceID: %3 Serialnumber: %4 Size: %5 Mb Interface: %1 S.M.A.R.T. Status: %6 Firmware Revision: %7 Partitions: %8
12090 EventSentry determined that the recommended management suite ("%1") from the hardware manufacturer (%2) is either not installed or not currently running on this server. Without this software, EventSentry will not be able to alert you of critical hardware warnings and/or errors, such as a hard drive failure in a RAID. Please visit the manufacturer's web site to obtain more information and install the recommended management suite. Additional Information: Manufacturer: %2 Model: %3 Bios Version: %4
12100 The performance counter "%5" (%1) on host %9 fell below the threshold of %2, the current values are: Average: %3 Minimum: %6 Maximum: %7 Counter Description: %8 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%10", expand it and click Performance / SNMP 4. Locate the object "%11" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12101 The performance counter "%6" ("%1", instance "%2") on host %12 fell below the threshold of %3, the current values are: Average: %4 Minimum: %7 Maximum: %8 Bottom %9 instances: %10 Counter Description: %11 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%13", expand it and click Performance / SNMP 4. Locate the object "%14" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12102 The performance counter "%4" (%1) on host %6 equals the value of %2. Counter Description: %5 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%7", expand it and click Performance / SNMP 4. Locate the object "%8" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12103 The performance counter "%5" ("%1", instance "%2") on host %7 equals the value of %3. Counter Description: %6 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%8", expand it and click Performance / SNMP 4. Locate the object "%9" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12104 The performance counter "%5" (%1) on host %9 exceeded the threshold of %2, the current values are: Average: %3 Minimum: %6 Maximum: %7 Counter Description: %8 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%10", expand it and click Performance / SNMP 4. Locate the object "%11" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12105 The performance counter "%6" ("%1", instance "%2") on host %12 exceeded the threshold of %3, the current values are: Average: %4 Minimum: %7 Maximum: %8 Top %9 instances: %10 Counter Description: %11 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%13", expand it and click Performance / SNMP 4. Locate the object "%14" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12107 The performance counter "%1" (%2) on host %3 does not equal the value of %4, the current value is %5. Counter Description: %6 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%7", expand it and click Performance / SNMP 4. Locate the object "%8" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12108 The performance counter "%1" ("%2", instance "%3") on host %4 does not equal the value of %5, the current value is %6. Counter Description: %7 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%8", expand it and click Performance / SNMP 4. Locate the object "%9" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12110 One or more required function entry points could not be found in the dynamic link library PDH.DLL. Please make sure that the latest version of PDH.DLL is installed on this machine, for example you may copy the DLL from another machine running a later Operating System. Performance monitoring cannot continue.
12111 The dynamic link library PDH.DLL could not be found and is required for performance monitoring. Please make sure that the latest version of PDH.DLL is installed on this machine, for example you may copy the DLL from another machine running a later Operating System. Performance monitoring cannot continue.
12112 The performance counter "%2\%1" (%3) could not be monitored. Please make sure that the performance counter exists. If you are running a non-english version then you might have to adapt the name of the performance counter so it matches the language of the Operating System.
12114 The EventSentry agent is experiencing an unusually high handle count (%1 handles) and/or high memory usage (%2 bytes), which is most likely due to a known issue in Windows Server 2003 SP2 (http://support.microsoft.com/kb/938135). It is recommended that you navigate to http://support.microsoft.com/kb/938135 to download and install a hotfix to resolve this issue. If you cannot install the hotfix then you can also restart the EventSentry service as a temporary work-around. It is not recommended that you continue to run the agent for an extended time period without installing the Microsoft hotfix. Failure to install the hotfix may eventually result in system instability. Installation of the hotfix will require a reboot.
12120 The performance counter "%6" (%1) on host %10 is between the range of %2 and %3, the current values are: Average: %4 Minimum: %7 Maximum: %8 Counter Description: %9 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%11", expand it and click Performance / SNMP 4. Locate the object "%12" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12121 The performance counter "%7" ("%1", instance "%2") on host %11 is between the range of %3 and %4, the current values are: Average: %5 Minimum: %8 Maximum: %9 Counter Description: %10 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%12", expand it and click Performance / SNMP 4. Locate the object "%13" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12122 The performance counter "%6" (%1) on host %10 is not between the range of %2 and %3, the current values are: Average: %4 Minimum: %7 Maximum: %8 Counter Description: %9 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%11", expand it and click Performance / SNMP 4. Locate the object "%12" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12123 The performance counter "%7" ("%1", instance "%2") on host %11 is not between the range of %3 and %4, the current values are: Average: %5 Minimum: %8 Maximum: %9 Counter Description: %10 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%12", expand it and click Performance / SNMP 4. Locate the object "%13" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the conf
12150 The performance counter "%4" (%1) on host %9 is back above the threshold of %2, the current values are: Average: %3 Minimum: %6 Maximum: %7 Counter Description: %8 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%10", expand it and click Performance / SNMP 4. Locate the object "%11" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12151 The performance counter "%5" ("%1", instance "%2") on host %10 is back above the threshold of %3, the current values are: Average: %4 Minimum: %7 Maximum: %8 Counter Description: %9 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%11", expand it and click Performance / SNMP 4. Locate the object "%12" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12152 The performance counter "%4" (%1) on host %6 no longer equals the value of %2. Counter Description: %5 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%7", expand it and click Performance / SNMP 4. Locate the object "%8" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12153 The performance counter "%5" ("%1", instance "%2") on host %7 no longer equals the value of %3. Counter Description: %6 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%8", expand it and click Performance / SNMP 4. Locate the object "%9" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12154 The performance counter "%4" (%1) on host %9 is back below the threshold of %2, the current values are: Average: %3 Minimum: %6 Maximum: %7 Counter Description: %8 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%10", expand it and click Performance / SNMP 4. Locate the object "%11" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12155 The performance counter "%5" ("%1", instance "%2") on host %10 is back below or at the threshold of %3, the current values are: Average: %4 Minimum: %7 Maximum: %8 Counter Description: %9 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%11", expand it and click Performance / SNMP 4. Locate the object "%12" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12156 The performance counter "%3" ("%1", instance "%2") on host %4 which previously exceeded the configured threshold, is not available anymore and will not be monitored.
12157 The performance counter "%1" (%2) on host %3 equals the value of %4 again. Counter Description: %5 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%6", expand it and click Performance / SNMP 4. Locate the object "%7" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12158 The performance counter "%1" ("%2", instance "%3") on host %4 equals the value of %5 again. Counter Description: %6 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%7", expand it and click Performance / SNMP 4. Locate the object "%8" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12170 The performance counter "%5" (%1) on host %10 is not between the range of %2 and %3 anymore, the current values are: Average: %4 Minimum: %6 Maximum: %7 Counter Description: %9 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%11", expand it and click Performance / SNMP 4. Locate the object "%12" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12171 The performance counter "%6" ("%1", instance "%2") on host %11 is not between the range of %3 and %4 anymore, the current values are: Average: %5 Minimum: %7 Maximum: %8 Counter Description: %10 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%12", expand it and click Performance / SNMP 4. Locate the object "%13" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12172 The performance counter "%5" (%1) on host %10 is back between the range of %2 and %3, the current values are: Average: %4 Minimum: %6 Maximum: %7 Counter Description: %9 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%11", expand it and click Performance / SNMP 4. Locate the object "%12" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12173 The performance counter "%6" ("%1", instance "%2") on host %11 is back between the range of %3 and %4, the current values are: Average: %5 Minimum: %7 Maximum: %8 Counter Description: %10 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%12", expand it and click Performance / SNMP 4. Locate the object "%13" and double-click it 5. Click the "Alert" tab to adjust the threshold or clear the event log alert check box 6. Save or Save and Deploy the configuration
12174 EventSentry detected a potential leak for performance counter "%1" ("%2") over the last %3 hours. During this time, the counter value increased from %4 to %5, with an average increase of %6% per hour. Out of a total of %3 hours, the hourly average increased %7 times (%8%). Average: %9 Minimum: %10 Maximum: %11 If available, then you should review the performance data history in the web-based reporting to determine whether you need to take action. If this counter value is not leaking memory, then you may be able to adjust the leak detection settings in the management console. Counter Description: %13 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%14", expand it and click Performance / SNMP 4. Locate the object "%15" and double-click it 5. Click the "Alert" tab and change the "Detect Leaks" setting 6. Save or Save and Deploy the configuration
12175 EventSentry detected a potential leak for performance counter "%1" ("%2", instance "%13") over the last %3 hours. During this time, the counter value increased from %4 to %5, with an average increase of %6% per hour. Out of a total of %3 hours, the hourly average increased %7 times (%8%). Average: %9 Minimum: %10 Maximum: %11 If available, then you should review the performance data history in the web-based reporting to determine whether you need to take action. If this counter value is not leaking memory, then you may be able to adjust the leak detection settings in the management console. Counter Description: %14 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%15", expand it and click Performance / SNMP 4. Locate the object "%16" and double-click it 5. Click the "Alert" tab and change the "Detect Leaks" setting (this will affect ALL instances) 6. Save or Save and Deploy the configuration
12176 The potential leak for performance counter "%1" ("%2") has been resolved, during the last %3 hours the hourly average increased %4 times. The current values are: Average: %5 Minimum: %6 Maximum: %7 Counter Description: %9 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%10", expand it and click Performance / SNMP 4. Locate the object "%11" and double-click it 5. Click the "Alert" tab and change the "Detect Leaks" setting 6. Save or Save and Deploy the config
12177 The potential leak for performance counter "%1" ("%2", instance "%10") has been resolved, during the last %3 hours the hourly average increased %4 times. The current values are: Average: %5 Minimum: %6 Maximum: %7 Counter Description: %9 To adjust this threshold or exclude this alert: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%11", expand it and click Performance / SNMP 4. Locate the object "%12" and double-click it 5. Click the "Alert" tab and change the "Detect Leaks" setting (this will affect ALL instances) 6. Save or Save and Deploy the configuration
12200 A SHA-256 checksum change has been detected: Package: %5 Directory: %1 File: %2 Old Checksum: %3 New Checksum: %4 Signed: %6 Entropy: %7 The content of the above file has been modified. Configuring File Monitoring: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%5", expand it and click File Monitoring 4. Adjust settings or double-click a listed directory 5. Save or Save and Deploy the configuration More information: https://www.eventsentry.com/kb/359
12201 A file size change has been detected: Package: %6 Directory: %1 File: %2 Old Size: %3 byte(s) New Size: %4 byte(s) Change: %5 byte(s) Signed: %7 Configuring File Monitoring: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%6", expand it and click File Monitoring 4. Adjust settings or double-click a listed directory 5. Save or Save and Deploy the configuration More information: https://www.eventsentry.com/kb/359
12202 A file has been added to a monitored directory: Package: %5 Directory: %1 File: %2 Size: %3 byte(s) Checksum: %4 Signed: %6 Entropy: %7 Configuring File Monitoring: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%5", expand it and click File Monitoring 4. Adjust settings or double-click a listed directory 5. Save or Save and Deploy the configuration More information: https://www.eventsentry.com/kb/359
12203 A file has been removed from a monitored directory: Package: %5 Directory: %1 File: %2 Last size: %3 byte(s) Last checksum: %4 Configuring File Monitoring: 1. Open the management console 2. Navigate to Packages -> System Health 3. Locate the package "%5", expand it and click File Monitoring 4. Adjust settings or double-click a listed directory 5. Save or Save and Deploy the configuration More information: https://www.eventsentry.com/kb/359
12210 EventSentry was unable to monitor the directory %1 for changes due to the following error: %2. The directory will not be monitored.
12211 EventSentry was unable to associate the directory %1 with an existing I/O completion port due to error: %2. The directory will not be monitored.
12212 EventSentry was unable to open the directory %1 due to error: %2. The directory will not be monitored.
12214 The temporary file currently being used for the "File Monitoring" feature has been deprecated for all builds after and including 2.90.0.28. The temporary file will now be deleted, and a new file will automatically be generated. Any file changes in monitored directories that occured while the EventSentry service was stopped will not be detected during this conversion.
12215 File monitoring will now index all monitored directories. This process can take several minutes, depending on the number of files and the performance of the computer. When complete, event 12216 will be logged.
12216 File monitoring has finished indexing all monitored directories.
12217 The recurring directory scan ("Re-Scan every") took approximately %1 minutes, which is longer than the suggested maximum of %2 minutes. Consider unchecking the "Re-Scan every" option in the file monitoring package(s) which apply to this host.
12300 The time difference between this computer and the NTP server "%1" has exceeded the maximum tolerance of %2 milliseconds. The time difference is: %3. How do I configure this feature? https://www.eventsentry.com/kb/360
12301 The local time has been successfully adjusted to %1 after a time difference (%2) has been detected between this computer and NTP server "%3". How do I configure this feature? https://www.eventsentry.com/kb/360
12302 The local time could not be adjusted, even though a time difference (%1) has been detected. The error was: %2.
12303 EventSentry was unable to retrieve the current time from host %1 due to the following error: %2.
12304 EventSentry was unable to retrieve the current time from host %1, the connection timed out.
12305 EventSentry was unable to retrieve the current time from host %1 for %2 seconds. EventSentry will not attempt to connect to this host again for %2 seconds and will try to use the other NTP servers in the list (if available). How do I configure this feature? https://www.eventsentry.com/kb/360
12306 EventSentry was unable to connect to any of the configured NTP servers (%1). Please make sure that at least one of the listed hosts is a valid NTP server. How do I configure this feature? https://www.eventsentry.com/kb/360
12307 Time difference between local host and %1: %2.
12400 The Scheduled Tasks monitoring engine has been initialized. %1 cached tasks have been found, %2 tasks are currently configured on this system.
12410 A new scheduled task has been added: Name: %1 Enabled: %2 User: %3 State: %4 Triggers: %5 Actions: %6 How do I configure this feature? https://www.eventsentry.com/kb/361
12411 A scheduled task has been removed: Name: %1 Enabled: %2 User: %3 State: %4 Triggers: %5 Actions: %6 How do I configure this feature? https://www.eventsentry.com/kb/361
12412 A scheduled task has been changed: Name: %1 Field Changed: %2 New Value: %3 Old Value: %4 How do I configure this feature? https://www.eventsentry.com/kb/361
12500 EventSentry will monitor the attached UPS devices and/or built-in batteries. %1 detected device(s): %2
12501 At least one connected UPS/battery is now running on battery power. EventSentry will periodically log event 12502 with estimated run times until the UPS is back online. EventSentry will perform a system shutdown when the remaining battery or runtime gets below a configured threshold. %1
12502 At least one connected UPS/battery continues to operate on battery power. Charge Remaining: %1% Estimated remaining runtime: %2 seconds
12503 All connected UPS/battery devices are back online. %1
12504 All connected UPS/battery devices are fully or almost fully charged. %1
12510 The charge level of all attached UPS devices is at or below the threshold of %1%% and a shutdown will now be initiated. %2
12511 The estimated runtime of this system is at or below the threshold of %1 minutes and a shutdown will now be initiated. %2
12512 System Shutdown Result: %1.
12600 EventSentry detected changes in a protected area of a hard drive, the new contents are embedded as binary data. If this change is unexpected, then the original data (MBR) can be downloaded from the EventSentry Web Reports (Inventory -> Host) and subsequently restored with boot media. Drive: \\.\PhysicalDrive%1 Sectors Monitored: %2 - %3 (MBR) Bytes Changed: %4
12601 EventSentry detected changes in a protected area of a hard drive, the new contents are embedded as binary data. If this change is unexpected then you can restore the boot loader by retrieving the original BootLoader from the EventSentry Web Reports (Inventory -> Host) and copying the data over with boot media. Drive: \\.\PhysicalDrive%1 Sectors Monitored: %2 - %3 Bytes Changed: %4
12605 EventSentry detected more than %d changes in a protected area of a hard drive in the last hour. It is recommended that you manually review the host and all attached disks.