| Error number | Error message | Additional info and instruction |
|---|---|---|
| 5021 | Unable to communicate with the testing server. Please contact your administrator. | Contact your local system or network administrator; the network connection was either not found or the connection was lost during authentication. A network connectivity problem might cause the issue. Verify the network connection and try again. If the second attempt is unsuccessful, close TestNav. Fix any network connectivity issues found. Check that the testing machine is connected to the school's network. Check ethernet cables or wireless connections, routers and switches, and so on. Check that proctor caching is running on any proctor caching computer in use and that the appropriate ports are open in the firewall. When a working network connection is confirmed, try again. After the connection is restored, check the student's test status in the administrative application and reset, if needed. Resume the student's test, and instruct the student to log in. |
| 5022 | Unable to communicate with the testing server. Please contact your administrator. | Contact your local system or network administrator; the testing server URL that was requested was not found (404) or there was an internal server error (500) during authentication. This is usually the result of a network connectivity problem. Verify the network connection, and try again. If you cannot connect after the second attempt, close TestNav. Fix any network connectivity issues. Check that the testing machine is connected to the school's network. Check ethernet cables or wireless connections, routers and switches, and so on. Check that proctor caching is running on any proctor caching computer in use and that the appropriate ports are open in the firewall. When a working network connection is confirmed, try again. After the connection is restored, check the student's test status in the administrative application and reset, if needed. Then, you can resume the student's testing session and have the student log in. |
| 5023 | Unable to communicate with the testing server. Please contact your administrator. | Contact your local system or network administrator; there was a parser error (bad data was sent from the application to the engine or from the engine to the server) during authentication. The user's login information was sent to the server, but either it or the response was empty, malformed, or corrupted. A network connectivity problem likely caused the issue. Verify the network connection, and try again. If you cannot connect after the second attempt, close TestNav. Fix any network connectivity issues. Check that the testing machine is connected to the school's network. Check ethernet cables or wireless connections, routers and switches, and so on. Check that proctor caching is running on any proctor caching computer in use and that the appropriate ports are open in the firewall. When a working network connection is confirmed, try again. After the connection is restored, check the student's test status in the administrative application and reset, if needed. Then, you can resume the student's testing session and have the student log in. |
| 5024 | Unable to communicate with the testing server. Please contact your administrator. | Contact your local system or network administrator; the transmission timed out during authentication. This is usually a network connectivity issue. Verify the network connection, and try again. If you cannot connect after the second attempt, close TestNav. Fix any network connectivity issues. Check that the testing machine is connected to the school's network. Check ethernet cables or wireless connections, routers and switches, and so on. Check that proctor caching is running on any proctor caching computer in use and that the appropriate ports are open in the firewall. When a working network connection is confirmed, try again. After the connection is restored, check the student's test status in the administrative application and reset, if needed. Then, you can resume the student's testing session and have the student log in. |
| 5025 | There has been a problem loading this item. Please contact your administrator. | Contact your local system or network administrator; the transmission aborted during authentication. This is usually the result of a network connectivity problem. Verify the network connection, and try again. If you cannot connect after the second attempt, close TestNav. Fix any network connectivity issues. Check that the testing machine is connected to the school's network. Check ethernet cables or wireless connections, routers and switches, and so on. Check that proctor caching is running on any proctor caching computer in use and that the appropriate ports are open in the firewall. When a working network connection is confirmed, try again. After the connection is restored, check the student's test status in the administrative application and reset, if needed. Then, you can resume the student's testing session and have the student log in. |
| 5026 | Invalid login token. Please try again. | Logout and log back in. Autologin using an authentication token has failed because the token has expired or is otherwise invalid or not recognized. The authentication token is requested from TestNav by the customer site and must be used within five minutes to allow the examinee to access the test; extended inactivity or network connections can cause this. |
| 5027 | TestNav is unable to write to the local drive due to browser security settings. Testing cannot continue. | Contact your local system administrator; TestNav can't write necessary files to the local system. This is because the operating system is keeping the browser in a sort of quarantine (sandbox). Some operating systems do this to applications that can be used to cause system instability or other harm. Select a new location for student responses to be saved. If that does not work, view the student's responses and save or print a record of the files so that the responses can be reentered after you close TestNav and retake the test using a different machine. |