How to Recover a Corrupted EyeDetect Test
If EyeDetect won’t open and shows an “Unhandled Exception” error message, it usually means there’s a corrupted test in the system. This happens when EyeDetect fails to properly save test files after a test is completed—often due to a system interruption or file writing issue.
This article will help you:
- Understand what a corrupted test is
- Locate and identify the corrupted test
- Inspect and repair the test files
- Restore the test so EyeDetect can function properly
Note: This guide only applies if the test was completed and saved before the corruption occurred.
Step 1: Open the Test Repository Folder
This is where all EyeDetect test files are saved.
How to get there:
- On your desktop, double-click on This PC (you may also see it listed as "Computer" or "My Computer").
- Double-click on Local Disk (C:) — this is your main hard drive.
- In the C: drive, double-click the DataLocker folder.
- Inside DataLocker, double-click the Converus folder.
- Inside Converus, double-click the TestRepository folder.
You are now inside the folder where all test files are stored. You will see the test
Step 2: Understand the Folder Structure
Each test is stored in a Test ID folder (e.g., ABC123XYZ).
Inside that folder is a Test Key folder, which contains the actual test data files. This Test Key folder name is what appears in EyeDetect’s test list.
Do not rename either folder — both names must remain exactly as they were created.
Inside the Test Key folder, you will typically find:
- Data.xml – Eye tracking data collected during the test
- Test.xml – Structure, logic, and questions of the test
- Test.ini – Metadata about the test, including tags and settings
- Test.zip – A compressed version of the test files, required for EyeDetect to load the test
not rename either folder — both the Test ID and Test Key must stay exactly the same.
Step 3: Find the Corrupted Test
If you have multiple tests in the TestRepository folder:
- Move one Test ID folder at a time from the TestRepository to your Desktop.
- After each move, open EyeDetect.
- If EyeDetect still shows the error, move the next folder.
- Once EyeDetect opens successfully, the last folder you moved is the corrupted one.
Keep that folder on the Desktop for repair.
Step 4: Inspect the Test Files
- Open the Test ID folder that you moved to the Desktop.
- Then open the Test Key folder inside.
- Verify the presence of the following files:
- Data.xml
- Test.xml
- Test.ini
- Test.zip (may be missing or corrupt)
About Test.ini
This file contains the identifying details of the test. If you open it in Notepad, you’ll see the test name, type, topics, and other metadata. If these fields are empty or incomplete, the test may still load but may not display correctly in EyeDetect.
Step 5: Check Data.xml
- Right-click Data.xml > Choose Open with > Notepad.
- If the file is completely blank, the test cannot be recovered.
- If the file contains data (even zeros), continue to the next step.
Step 6: Recreate the Test.zip File
If Test.zip is missing or corrupted, EyeDetect cannot load the test.
To fix this:
- Delete the existing Test.zip file, if present.
- Select both Data.xml and Test.xml by holding Ctrl and clicking on each.
- Right-click one of them and choose Send to > Compressed (zipped) folder.
- A new ZIP file will be created.
- Rename it to Test.zip (exact spelling required).
Why this works: EyeDetect looks specifically for a Test.zip file that contains both XML files. If that ZIP file is missing or malformed, the test becomes unreadable.
Step 7: Return the Fixed Test to the Repository
Once the corrupted test has been repaired:
- Move the full Test ID folder (which includes the fixed Test Key and new Test.zip) back to:
- This PC
- Local Disk (C:)
- DataLocker
- Converus
- TestRepository
- Launch EyeDetect.
If it opens without errors, the corrupted test has been successfully recovered.
Final Notes
- The Test Key folder name must match what appears in EyeDetect.
- If Data.xml is blank, there is no recoverable data.
- Most corruptions occur when the system fails to generate a valid Test.zip file at the end of a test.
- This process only works for tests that were fully completed and saved.
Comments