Error Messages
If an error arises the program will output an error message. Each error message follows the same logical structure. The title of the error message will give the error type, an error code and then the error identifier. The body message will give an explanation to the cause of the error and then generic advice as to how to fix or prevent the error. An icon will also be displayed, either an error, warning, or information. An error icon indicates the program is at fault, a warning icon indicates the User is to fault and information is used to indicate generalise information to the User. If you are experiencing an error first try the generic advice stated in the error message. If that fails try the troubleshooting outlined below.
As previously stated error messages will have error code and identifier in the title. Use the error code to distinguish the type/ cause of error and the follow the trouble shooting below. The identifier code should be an alphabetical character and should be sent to your software vendor if you continuously experience problems.
Database errors are most commonly caused by too many Users trying to access the database concurrently. First restart the program and try to perform the action again during a period of slow traffic. If issues persist run the troubleshooting tool, to do so please see section 8.2.
-
The tool will first check that “2007 Office® System Driver: Data Connectivity Components” has been installed on the computer, if this fails please install this required dependency software.
-
Secondly the tool will check a connection can be made, if this fails the database can either not be found or cannot be connected to. Ensure that you have the correct database for the version of the software you are running and check that the database connection string is in the correct format; as explained in 3.4. Also check that the database is in a location that the program has sufficient privileges to access.
-
If the program fails to read from the database but can create a connection to the database check that the database is in a location accessible to the User and program.
-
If the program fails to write to the database but can read from it check that the User has both read and write access to the database location. It is important that they do to save Users exam results.
Windows errors are unlikely to occur, if they do, try running the troubleshooting tool detailed in section 8.2. First try running the tool on a standard account and then try running the tool as an administrator. If the check passes stage two as an administrator, but not a standard User then contact your system administrator to allow the program access to read a current Windows Username.
User errors are at the fault of the User, advice should be given in the error messages body as to how to prevent the issue and its cause. Follow the information highlighted or read the User manual on how to properly operate the software.
Critical program failures are very unlikely to occur, however in the event they do, please run the troubleshooting tool. If any of the stage 3 checks fail you have a corrupt/ incomplete version of the program. As such you should uninstall and re-install the program onto your computer. If any of stage 4 checks fail it is recommended that you check you have the latest version of the .net framework installed on your computer. It may help to reinstall the .net framework and the program. If problems still persist send a copy of the error code, identifier and an explanation of what and where you were when the problem occurred; send this information to your software vendor.