ifference between revisions of "EMK:Errors and Troubleshooting"
| Line 64: | Line 64: | ||
| Error viewing result item || Unable to display the selected view of results (Graph, Map or open file) || | | Error viewing result item || Unable to display the selected view of results (Graph, Map or open file) || | ||
|} | |} | ||
| + | |||
| + | ==The System Log== | ||
| + | |||
| + | Entries are made in the System Log for important system events. The '''''System Log Window''''' is accessed by clicking on the System Status Box (Second box from the left in the bottom panel) in the Status Bar at the foot of the Main Window. | ||
Revision as of 13:42, 21 November 2012
There are four types of errors that can occur when running the model.
Fatal Errors: These occur when EMarket fails to execute a Run. An alert is presented to the user and EMarket is closed down. When a fatal error occurs it will usually be due to data corruption and occasionally because a file that is needed is locked or in use. It is good policy to make a backup of the Data directory from time to time in the unlikely case that this happens.
User Alerts: These errors are not normally serious and can be dealt with by you. An error message is presented describing the cause of the alert, and in many cases the window where the problem lies will open for you to correct the problem. The model will not stop other Runs currently under way as this could mean the interruption of a lengthy processing session.
Logged Errors: The model will continue to execute active Runs when these errors occur. They are simply added to the log as information for the user. An example of a logged error is a line constraint breach because of infeasibility. Some items, such as Batch start and finish times are recorded in the log but are not errors.
Unexpected Errors: Bugs are inevitable in any application no matter how well it has been tested, and in EMarket bugs may appear as Unexpected Errors. If you receive an Unexpected Error message, please paste it into an email message and send it to helpdesk@energylink.co.nz, preferably with a brief description of the action that led to the error. The error text format is shown below:
Unexpected error <error number>: <error text>
In: <program section A>-><subsection A>->...-><subsection Z>
Exe: EMarket<version number>
See also: The Run Log
Fatal Errors
| Error Message | Action |
|---|---|
| Your EMarket licence has expired, please install a new licence. | A new licence is required from Energy Link Ltd. |
| Your EMarket licence does not have any valid market codes. You will need to use a new licence. | A new licence is required from Energy Link Ltd. |
| The licence file <licence file name> does not appear to be correct. | A new licence is required from Energy Link Ltd. |
| The licence file for EMarket can't be found. | Place the licence file with the Executable file in the same directory. |
| EMarket needs a Working Directory to run. | Select a Working Directory for EMarket. |
User Alerts
Below is a list of some common user alerts and solutions
| Error Message | Meaning | Possible Cause/Solution |
|---|---|---|
| Cannot calculate Water Values for run <Run.Name> - Security Factors must be greater than 1 | Hydro system Security Factors must be less than 1 in the Run window | Check the Security Factors for the Hydro System and make sure they are greater than 1. |
| Cannot open Resources.csv, It may be locked or in use, program quitting | EMarket cannot open the Resource File | Close any application using the Resource file. |
| Checking for Taupo Inflows - creating records if necessary | Taupo Inflows might not exist in <Inflow Name>_IF.scv | Taupo Inflows need to be created by adding TaupoNatural and TaupoForeign to give only the total inflows to Lake Taupo. |
| Error writing output spec to file <FilePath> . This file may be locked or open | Close the Output spec file <File Name>.csv | |
| Error writing Report to file <FileName> . This file may be locked or open | Close the Report file <FileName>.csv | |
| Map already showing, please close before re-opening | Close the existing map | |
| MapInfo.csv file is missing/invalid - cannot show map | Put MapInfo.csv in the Right location: EMarket\MapDate\<MarketName>\ | |
| Batch Aborted | The currently running batch has been aborted | |
| Run Aborted | The currently executing Run has been aborted | |
| This licence doesn't include the market [<Market Code>],Log_Alert | Your licence does not allow the simulation of this type of market | |
| Water Value files purged | All unused Water value files have been deleted | |
| Error viewing result item | Unable to display the selected view of results (Graph, Map or open file) |
The System Log
Entries are made in the System Log for important system events. The System Log Window is accessed by clicking on the System Status Box (Second box from the left in the bottom panel) in the Status Bar at the foot of the Main Window.