Current NCDesk Icon NCDesk

Error Codes

NCDesk will produce error codes under error conditions. The following are detail descriptions for each error code. If applicable, a solution or help for escaping the error condition is provided. Error conditions that do not give error codes are mentioned at the bottom of this page.

Error Code
Number
Ranges
Description of Error Category
0-99
Non-specific Application or File System
100-199
Spreadsheet Application
200-299
Database Application
300-399
Editor Application
400-499
Window Manager Application
500-599
E-Mail Application
600-699
Communication with Test Server
700-799
Autoupdate/Test Connection

 

Error
Message
Text
1
Cannot connect to test server.
2
Difficulty communicating with test server.
3
Installation has been corrupted.
Please reinstall NCDesk.
4
File system error.
Please see the NCDesk web site for more information.

Error Codes/Problems/Possible Solutions

Error Code Error Message
Text
Error Category Short Description Possible Problem(s) Possible Solution(s) Exception
1
3
Application Missing help file(s). Help files that were installed along with NCDesk cannot be found by NCDesk. NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
5
3
Application Preferences or NCDesk resource file missing. A file that maintains preference settings and was installed along with NCDesk cannot be found by NCDesk. NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
6
3
Application Error message properties file missing. A file that contains error messages and was installed along with NCDesk cannot be found by NCDesk. NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
7
3
Application NCDesk Launcher file is missing.
A file that is used to perform startup operations and was installed with NCDesk cannot be found. NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
2
4
File System Cannot open a help file.
        
A help file that was installed along with NCDesk cannot be opened by NCDesk. This message indicates that something is wrong with the file system or permissions. Possible solutions include reinstallation of NCDesk or changing the current user logged into the workstation environment. If these options have no effect, then there may be a hardware problem.  
3
4
File System Unable to open the log file.
        
The log file cannot be opened by NCDesk. This message indicates that something is wrong with the file system or permissions. Possible solutions include reinstallation of NCDesk or changing the current user logged into the workstation environment. If these options have no effect, then there may be a hardware problem.  
4
4
File System Unable to bind to a port.
        
NCDesk cannot bind to an IP port. The default port used by NCDesk is 6131. This message indicates that some other application is bound to the port NCDesk is trying to use. Open the file NCPreferences.properties found in the NCDesk installation directory with a plain text editor. Change the setting for PortNumber= (originally 6131), save changes, and attempt to start NCDesk.  
Error Code Error Message Error Category Short Description Possible Problem(s) Possible Solution(s) Exception
300
3
InstallCorrupt The editor resource file is missing.   NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
301
3
InstallCorrupt The editor resource file is corrupt.   NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
400
3
InstallCorrupt The window manager resource file is missing.   NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
500
3
InstallCorrupt A mail resource file is missing.   NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
501
3
InstallCorrupt A mail resource file is missing.   NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
502
3
InstallCorrupt A mail resource file is corrupt.   NCDesk should be reinstalled since this message indicates that something is wrong with the installation.  
601
2
Communication Could not establish a connection to our servers NCDesk is not able to get to the test server. Several things can cause this including but not limited to: local network is down, computer network card unplugged, firewalls, testing server offline, etc. Find where the network is disconnected or where the client computer is being blocked from using the Internet. TCP Ports 80 and 443 should be open to data.ncsu.edu. URLConnectException
602
2
Communication Connected to server but there was a problem transmitting data to or from the server NCDesk is able to get to the test server, but something is interfering with data transmission. Several things can cause this including but not limited to: LAN or WAN had excessive load (which comes and goes), packet filtering, computer network card malfunctioning, testing server malfunctioning, etc. Attempt to lower the use of the Internet and/or other LAN/WAN use at the test administration location.

Some students may have to be taken off the test if enough bandwidth cannot be allocated for their sessions.

Installation and use of traffic shaping technology can help prioritize the type of Internet traffic on the LAN/WAN.
URLIOException - request was accepted by the server, but no valid OIS was provided, or OIS did not contain expected data amounts or types, or OIS could not be read from
Error Code Error Message Error Category Short Description Possible Problem(s) Possible Solution(s) Exception
603
3
Corrupt Installation Installation is fatally corrupt. Can't find required navigation keys.   Reinstall NCDesk on computer DirectionKeyInvalidException
604
2
Data Corruption System trying to re-download data unnecessarily For some reason the client is trying to get the next or previous item multiple times. Abort test session and restart test. QuestionElementAlreadyExistsException
605
2
Data Corruption Question number requested exceeds number of questions in the section. Somehow the test server is attempting to send bad data. Abort test session and restart test. QuestionExceedsSecBoundsException
606
2
Data Corruption Corrupt/invalid data received from server for authentication. The test server data being sent is badly formed or the client is garbling the data as it is being received. It is possible that some network appliance located between host and client is affecting data transmission -- this would have to be traced, indentified, and repaired. CorruptLoginResponseDataException
607
2
Data Corruption Problem converting data to different formats. This may happen as items are pulled from the server and displayed to the student. Retry accessing the next or previous item. CNFExceptions
Error Code Error Message Error Category Short Description Possible Problem(s) Possible Solution(s) Exception
608
2
Communication Problem initializing the SSL tools for security. SSL is required to login and access the test. This is a component that is used by NCDesk. Reinstall JRE 1.5.0_08 and NCDesk SSLException
609
2
Corrupt Installation Installation is fatally corrupt. Can't find required configuration file in the archive. Reinstall NCDesk MissingBundleException
616
2
Communication There was a problem retrieving your question, or storing your response The test server encountered a problem either saving your answer or getting the next or previous question. It is likely that the test server is not communicating with the database server. Retry to move to the next or previous item in the test. If the problem continues, abort the test session and attempt to restart the test. DbCommException
617
2
Communication Could not uniquely identify you and link to your server side test profile. The test server has lost the ability to match a session to the student taking the test. This could be caused by client computer problems, network interruptions, response timeout, or data transfer corruption. Retry to move to the next or previous test item. If this error continues, restart the test. If this error keeps showing up for a single computer, then there may be hardware problems. If this error keeps showing up for an entire lab or school, then there may be local network appliances that are striping important data off the communication. If this is the case, then tracing, identification, and repair will have to occur. NoSessionException - an established session could not be found
618
2
Communication Improperly formatted request. Could not redirect to proper worker servlet. The test server could not take the request and figure out what to do with it. Retry getting the next or previous test item. If this continues, exit NCDesk and restart the test. MalFormedDispatcherRequestException
619
2
Test Server Communication Missing request data. Worker servlet could not process. The most likely cause of this error code is test session inactivity for 30 minutes or more (since the session will time out and be removed at that point). This most often occurs on login if the admin login happens more than 30 minutes prior to student pressing the Start button. Close NCDesk, restart NCDesk and log back into the test. MalFormedRequestException
621
2
Communication Cannot find data in your test profile on the server The test server found a student test record, but it does not contain data about a student's test. See 619. Restart test. InvalidStudentBeanException - StudentSessionData object stored in the session under the attribute name "studentBean" is a) null, or b)corrupt
631
2
Test Login Invalid login. One or all of the school code, username, or password did not match up with a user record in the database. Find the correct information on school code and your user account to login to a test session. This information should be available from the school test coordinator or the district test coordinator. The help desk cannot help with this -- they can only give out 6-digit/numeric accountability school codes. InvalidCredentialsException
Error Code Error Message Error Category Short Description Possible Problem(s) Possible Solution(s) Exception
641
2
Session State Test profile on server is out of sync with local data. The test server and the client software have a different record of the test session. Exit NCDesk and restart the test. SessionUserMissMatchException
642
2
Test Login School does not have any test sessions registered for this time, or the testing window is closed. School has no scheduled test administration times recorded in the NCRegistation system or the window for testing is closed. Have school or district test coordinator use NCRegistration to schedule a testing session for the number of students needing to test. They may need to schedule several test administrations depending on the number of students testing or the available lab and/or network bandwidth. TestSessionWindowClosedException
643
2
Test Login or Session State Data received by the server during login request doesn't match an available, 'login-ready' student Failed to find the student/admin combination requested when choosing student to test. Student may already be logged in on another computer. Check to see if the student is already logged in on another computer and getting ready to take the test or actively taking the test. Otherwise, contact the helpdesk immediately (cskills@ncsu.edu) InvalidStudentRequestedException
644
2
Test Login or Session State Student login data is all valid, but your institution has no more test session slots available. The number of scheduled test administrations needs to be reset in the NCRegistration system. Have the school or district test coordinator check the NCRegistration system to see if they can make scheduling adjustments. May need to reset the scheduling. Have the school or district test coordinator contact ncregistration@ncsu.edu if they need to recover past scheduled test administrations. AllSessionsFullException
651
2
Session State Required syncronization data not received by server. The test server did not get data that is sent by client. Retry moving to next or previous test item. If the problem continues, then exit NCDesk and restart the test session. NoSyncVerificationDataException - failed to recieve, or it was invalid data, the clients current sectionID for sync verification.
652
2
Session State Required synchronization data received by server, but does not match expected values. The test server got data from the client, but it did not match expectations. Retry moving to next or previous test item. If the problem continues, then exit NCDesk and restart the test session. SyncVerificationFailedException - client section ID did not match the current sectionID stored in the session student bean object
661
2
Session State Student and questions validation data sent to server during an answer storage request did not match test The test server got data from the client, but it did not match expectations. Retry moving to next or previous test item. If the problem continues, then exit NCDesk and restart the test session. ResponseRequestValidationFailedException
662
2
Session State Student's answer could not be saved. The test server either didn't get the data from the student or it could not save it. Retry moving to next or previous test item. If the problem continues, then exit NCDesk and restart the test session. ResponseDatabaseSubmissionFailedException
671
2
Session State Student data received by server during a test completion operation did not match test profile data. The test server didn't get expected data from the client. Retry moving to next or previous test item. If the problem continues, then exit NCDesk and restart the test session. StdtVerificationFailedException
Error Code Error Message Error Category Short Description Possible Problem(s) Possible Solution(s) Exception
700
Auto Update Failure to save update(s) to client's disk. NCDesk either didn't get all of the download or it could not save it to the hard drive/file system.

Retry starting NCDesk (which will make it try to get the update again).

 
701
Auto Update Deletion of old files failed.      
702
Auto Update DataBase connection failed. Communication error.

If this continues, check network connections or network appliances that filter packets.

 
703
Auto Update Database returned an empty set. Communication error.

If this continues, check network connections or network appliances that filter packets.

 
704
Auto Update Update file name mismatch. Communication error.

If this continues, check network connections or network appliances that filter packets.

 
705
Auto Update No Files returned from the webserver. Communication error.

If this continues, check network connections or network appliances that filter packets.

 
706
Auto Update Failure reading object from the webserver. This error code indicates that the data in the stream header returned from the server is invalid in some way (empty or corrupt).

If this continues, check network connections or network appliances that filter packets.

 
707
Auto Update Failure parsing information from the database. Communication error.

If this continues, check network connections or network appliances that filter packets.

 
708
Auto Update Problem updating critical file NCVersion. This indicates a disk or file system error.    
709
Auto Update Webserver communication garbled. This error code indicates that the data in the stream header returned from the server is invalid in some way (empty or corrupt).

If this continues, check network connections or network appliances that filter packets.

 
710
Auto Update Failure reading data from the webserver. Communication error.

If this continues, check network connections or network appliances that filter packets.

 
711
Auto Update Integrity check of update failed. Communication error.

If this continues, check network connections or network appliances that filter packets.

 

 

Other (Non-coded) Errors

Java Virtual Machine Launcher
     If any of the main jars (i.e. ncdesk, ncdata, ncsheet, etc) are missing from the NCDesk installation folder, Java will display an error box on NCDesk startup titled "Java Virtual Machine Launcher". The error message will be either: "Could not find the main class. Program will exit." OR "Fatal exception occurred. Program will exit." In either case, users will need to reinstall the NCDesk application. (FYI - there are other situations where the user might see this type of error so re-installation may not always resolve the issue).
     If the NCDesk launcher package is missing, users will see our standard "Installation has been corrupted. Please reinstall NCDesk." message with an error code of 7.

This file was modified on Tuesday, October 09, 2007; at 2:39:00 PM