Preamble
This document lists possible reasons why E10 crashes or you get the error “Internal check has identified an issue”.
If E10 crashes please try to download a fresh copy of E10 app and replace the old one. Download link and information here.
If this does not resolve the issue then it’s possible your etz file has violated at least one of the things listed below and you will need to rectify in the latest etz version you can access.
Admin > Setup:
- Faculty data: Faculty names cannot contain spaces. Use underscore if necessary.
- Campus data: Cannot use “main” as a Campus name.
Admin > Setup > Grid Structure:
- Period codes can ONLY be a combination of letters or numbers. Period codes cannot have hyphens or other symbols. Examples of invalid period codes: 3-6AM, RC/TF, K-2R.
- Period names cannot have any part of a day, e.g Mon, Tue.
Teachers > Teacher Data:
- Teacher's name cannot contain the word "teacher" or "teach".
- Teacher's name cannot contain the word "Study".
Teachers > Duty Roster:
- Name of Duty areas cannot be the same as a Faculty name, e.g. Faculty = “Inclusion”, Duty area = “Inclusion”.
- Duty areas > Period column should not have invalid period references indicated by question marks ‘???’. These are caused by changing period names in the Grid Structure. Re-enter which periods the Duty needs to run.
- Do not use the same separators used for class codes (dots . , hyphen - , underscore _ ).
Class data:
- Class data > Period column should not have invalid period references indicated by question marks ‘???’. These are caused by changing period names in the Grid Structure (Setup > Grid Structure). Re-enter which periods the class needs to run. Make sure to check Class data screens for all year levels.
Various data entry screens:
- Do not use the same code in different areas of the file, eg. Campus code = “Gateway” and Faculty = “Gateway”. You can only use a code to refer to one object in the file.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article