Event Troubleshooting Codes

Source file: appendix-2-event-troubleshooting-codes.htm

Event Description Cause Fix Priority
E-1 Monitoring alarm triggered. All conditions for a monitoring alarm have been satisfied.   User-defined
E-2 Scanner disconnected. Scanner physically unplugged or powered off, or the network adapter was disabled. This event will be delayed for 2 minutes to allow time for the scanner to reconnect. Reconnect and power on the scanner. Re-enable the network adapter. High
E-3 Hard drive is almost full. The hard drive that holds the .maptekobj is filling up. Events will be triggered when there are approximately 7 days left (Low), 3 days left (Medium), 1 day left (High) and the hard drive is full (High). Free up space on the hard drive (at least one day above the threshold, otherwise the event will not re-trigger). See Cause.
E-4 Error reported by scanner. Scanner has reported an error code. Report the problem to Maptek. Low
E-5 Problem sending email. Invalid email address, lack of internet connectivity, incorrect SMTP preferences or firewalls blocking data. Check spelling of email address. Contact site IT to check network availability. Use the test buttons in the preferences for sending test emails to verify the SMTP settings. High
E-6 Weather station disconnected. Weather station has been unplugged. If the weather station fails to respond to a query it will be retried once, if that retry fails then this event will be triggered. Plug the weather station back in. Low
E-7 License expired / almost expired. Licence is nearing expiration date. Events will be triggered when the following time remaining thresholds are crossed: 4 weeks, 2 weeks, 1 week, 6 days, 5 days, 4, days, 3 days, 2 days, 1 day, 12 hours, 6 hours, 3 hours, 2 hours, 1 hour. Renew your licence and update the licence on the system. High if days remaining <=3, Medium if days remaining <= 7, Low otherwise.
E-8 Server crashed. Unknown. When servers crash Sentry should gracefully recover back to the state it was in prior to crashing. Low
E-9 Unknown error occurred while adding a scan to a scene (scan was not added). Unknown exception occurred while either importing, registering or adding a scan to a scene.

Obtain the scan that failed and inspect it in PointStudio. If possible get it to the Technical Services team for inspection.

 Medium
E-10 Registration attempted on scan with no visible points (scan was not added). Any of the scans used in the registration process had all points hidden. This could happen if a bad registration region was used. This occasionally happens to some scans that have only a few scattered points, not enough to form any cells. Either change the registration region or ignore the dud scan (which will be done automatically). Medium
E-11 Registration terminated early because there was insufficient correspondence between the scans (scan was not added). A bad registration region could be defined that results in too few overlapping areas. Change the registration region. Medium
E-12 Registration terminated early because of an unknown issue (scan was not added). Unknown. Unknown. Medium
E-13 Registration failed (scan was not added). Registration resulted in an invalid transformation, unknown why. Unknown. Medium
E-14 Adding scan to scene failed (scan was not added). The scan being processed was acquired before the latest time stored in the temporal scan grid. Or a scan that doesn’t share the same extents as the scene was attempted to be added (so that adding the scan didn’t fit any cells). May happen if global registration is disabled and a scan comes in that only has a few valid returns. Ignore this scan, do not add it to the scene. Medium
E-15 Only .3dp, .3dr or .r3s scans are supported. Scan file that is not a .3dp, .3dr or .r3s is attempted to be added to the scene. This shouldn’t happen, there are earlier checks that guard against this. Do not try adding an unsupported scan. Medium
E-16 Problem importing scan. Scan file does not contain any grid or point information. Pass the scan to your representative for further analysis. Medium
E-17 Scan has no valid returns (empty scan). Most likely a problem occurred with the scanner that resulted in no point data being acquired. Send the scanner back for a service. Medium
E-18 Scan from an unsupported scanner.

Using a scanner and Sentry software version that are incompatible.

  • 8200[SR/ER]: Sentry 1.1–2.5, 2021–2023

  • 8820 series: Sentry all versions

  • Gen3 (except UR3): Sentry 2.0 and newer

  • Gen3[UR3]: Sentry 2023 and newer

Match the software version to the scanner.

 Medium
E-19 Data Engine cache has become full or fragmented. The scene processed by Sentry is too large for the available amount of DataEngine cache. Sentry needs to hold 3 scans in the cache for registration, if the cache becomes fragmented then all 3 scans may not be able to be opened at the same time. Sentry will automatically restart when this occurs to start from a fresh cache. Installing more RAM to your computer will improve performance. Define a scene to use smaller scans. Low
E-20 System has recovered from an unexpected restart. Sentry was shut down unexpectedly. This can happen if Microsoft Windows is shutdown before the Sentry software, for example, an automatic Windows update restarts the computer or the shut down procedure of the Sentry system was not followed. Run Windows updates at scheduled times and shut down the Sentry software properly while doing so. Follow the shut down procedure of the Sentry system. Low
E-21 Scan has insufficient coverage of the scene area (area covered by the first scan added to the scene). Fog, dust, rain or other environmental conditions cause a significant enough reduction in point coverage (missing returns) that the scan is deemed unsuitable for registration. The percentage coverage is user configurable in the "Scene processing" preferences in Sentry Field. Adjust the percentage coverage in the preferences if it is too aggressive. Wait until the fog/dust/rain has passed. Low
E-22 Solar controller disconnected. Solar charge controller has been unplugged or powered off. Plug the solar charge controller back in. Low
E-23 Scanning has stalled. No new scans have been acquired for a period of time defined when creating the scene (+ the expected time to acquire the scan). This could indicate a hardware issue with the scanner. Try restarting the scanner and Sentry. Contact your representative. Medium
E-24 Scan processing has stalled. The system has not successfully processed a scan within a period of time. This timeout is the time required to acquire a scan + the delay time specified when creating a scene. This could happen if there is a fog/dust/rain event occurring such that no scans are being added to the scene. This could happen if there is an issue with a scan file that Sentry is unable to handle properly and so gets stuck repeatedly trying to process that scan. If it is caused by environmental events, wait until valid scans start coming in again. If this is caused by a bad scan file then remove that scan file from the scene folder and provide it to the Maptek representative to investigate. Medium
E-25 Sentry Remote Status has lost connection to the Sentry Field instance. Sentry Field has crashed, lost power, or otherwise lost network connection to Sentry Remote Status. Check network connections, ensure Sentry Field is running. High
E-26 Battery state of charge is too low. Battery Charge Controller is receiving readings for the state of charge which are below a certain threshold. Check the battery and generator fuel levels and ensure generator is charging the battery correctly. High
E-27 Partial backup created. A backup for a day was created without all of the data for that day. This occurred because not all of the data had arrived within 3 hours of the backup attempting to start. Determine why scans are being acquired very slowly. Contact your Maptek representative. Low
E-28 Previous backup still running An automatic backup attempted to begin while one was already in progress. The previous backup could still be in progress due to being written over a slow network. Check the network connectivity to the backup writing location. Medium
E-29 Failed to create backup. An automatically started backup failed to complete. Check permissions for the backup writing location are set up correctly and there is an appropriate amount of storage space available to write to. Medium
E-30 Backup failed to start. The backup process has been idle for a large period of time without beginning the next backup. Unknown. Contact Maptek representative. Medium
E-31 Backup process died. The Sentry process responsible for handling automatic backups has crashed while performing a backup. The backup process should relaunch itself naturally. However, if the backup in progress is lost then a manual backup will need to be created if needed. Medium
E-32 Backup missed during downtime. Sentry software was not running when an automatic backup would have occurred. Use "Create Archive" to generate the archives for the missed days. Low
E-33 Fuel level low Always triggers when fuel level reaches 0.
Users can configure another alarm trigger level through preferences.		 Refill generator fuel tank. High if fuel level reaches 0.
Medium if fuel level falls below alternative threshold.
E-34 Diagnostic module disconnected Sentry detects that the diagnostic module has disconnected. Reconnect or replace Ethernet cable between IPC and x420 controller. High
E-35 Fuel gauge wire disconnected The diagnostic module detects that the fuel gauge wire has disconnected. Restore or repair connection between fuel gauge and x420 controller. High