Page tree
Skip to end of metadata
Go to start of metadata

Below we will try to collect the various issues that might occur during installation or maintenance of MyTimetable and related software.

MyTimetable displays a blank screen and returns a HTTP 404 Not Found return code.

This usually means MyTimetable did not load correctly. If an unrecoverable error occurs during application initialisation, the Tomcat server will still be listening for requests, but the application will not be available. Check the Tomcat logfiles (tomcat7-stdout, tomcat7-stderr and catalina) for the exact error description. Some of the most common errors are listed below.

MyTimetable shows the error "com.google.gwt.user.client.rpc.StatusCodeException: 500 The call failed on the server; see server log for details"

Please check the Tomcat logfiles (tomcat7-stdout) for more information on this error. Often this error occurs if the timetable source database is not available or the data is incomplete. Also check the MyTimetable status URL (http://<your MyTimetable install>/status) to see which datasource is having issues. Try a full 'refresh' of this data source (e.g., for Syllabus Plus try running ScheduledExtract.exe with the /F switch). If this does not help, please contact our support department.

The Tomcat log shows: "java.sql.SQLException: Cannot open database "xxx" requested by the login. The login failed."

Please verify the requested database is available and the user account specified has the necessary permissions to access the database (db_datareader for source database (e.g., Syllabus Plus), db_datareader + db_datawriter + db_ddladmin for userprefs databases).

The Tomcat log shows: "java.sql.SQLException: Network error IOException...."

Please verify the database server is available, and that any firewalls between the MyTimetable server and database server have been opened.

The Tomcat log shows: "...getClientConfiguration()' threw an unexpected exception: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0"

The Syllabus Plus reporting database seems to be empty, please try a full refresh of the database by running ScheduledExtract.exe with the /F switch.

The Tomcat log shows: "com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence."

Please make sure that all configuration files are saved using the UTF-8 encoding. For instance, in notepad.exe it is necessary to use 'Save as' and select UTF-8 instead of ANSI.

The Tomcat log shows: "SEVERE: Parse Fatal Error at line xx column xx: .... org.xml.sax.SAXParseException; systemId: <filename>"

Please make sure the mentioned configuration file is syntactically correct (i.e., no typo's), and make sure it is saved using the UTF-8 encoding (see previous error).

 

  • No labels