SecureClient is a delivery app with offline test support and built-in protections against internet and device failure. For general information on SecureClient and the Surpass test driver, see the Test Delivery section of the Surpass Help Site.
This article will provide information on some of the common troubleshooting issues that may be encountered using SecureClient for each operating system and offer advice on how they can be fixed.
If you have tried the steps outlined in this article and are still having issues with SecureClient, or you are encountering any issues with SecureClient not listed here, contact support@surpass.com.
Table of Contents
SecureClient for Windows
TIP: It is recommended that SecureClient is always installed with administrative permissions on Windows devices. For information on installing SecureClient, read Installing SecureClient.
The following details how to troubleshoot issues specific to the Microsoft Windows operating system.
Antivirus software
If you are experiencing general test performance issues, particularly concerning files being opened during a test (for example, opening a PDF file), this may be due to interference from antivirus software installed on your device.
The following instructions detail how you can whitelist SecureClient to be excluded from antivirus protection.
Navigate to your device’s Settings.
Select Windows Security from the Privacy & security settings.
Select Manage settings from the Virus & threat protection settings.
Select Add or remove exclusions from the Exclusions section.
Allow Windows Security to make changes to your device.
Select Add an exclusion and choose Folder from the drop-down menu.
Locate and select the folder in which SecureClient is installed. The default file path for this is: C:\Users\Public\SecureClient
Error 821: SecureClient core
When an Error 821 message is shown it means there was an error trying to decrypt an item for the current question.
This is caused by an on-access virus scan preventing SecureClient from reading or writing files.
To resolve this issue, add the SecureClient folder as an exclusion from the on-access scan.
Error 827: Error validating keycode
When a candidate enters a keycode for an online test, they may encounter an Error: 827 message:
Error: 827Secure Client Core – OFFLINE – There was an error validating the keycode
This means SecureClient is being forced into an offline state where it cannot communicate with the database and validate the keycode.
To resolve this issue, try the steps below.
Check the keycode has been inputted correctly
Check that the keycode has been written correctly.
Check the proxy configuration
To check if your LAN connections go through the proxy server, open Windows 10 settings and search ‘proxy’ in the search bar.
If the toggle buttons are set to On, the network goes through the proxy server. This may prevent SecureClient from accessing Surpass and allowing the test to start. To resolve this, set the toggle buttons to Off.
Authenticate the proxy server
To authenticate the proxy server, first enter your details into the proxy.XML file. This can be found in (C:\Users\Public\SecureClient\configfiles).
If your proxy server requires authentication, enter the username between <user></user> and the password between <password></password>.
If you are not sure which proxy settings to use, you can check the settings in Windows 10 by searching for ‘proxy’ in the search bar.
Check the folder permissions
To check the folder permissions for SecureClient, follow these steps:
Select Open file location on your local shortcut for SecureClient.
Select the folder prior to the one you are directed to.
Select the SecureClient folder.
Select Properties.
Select Security.
Select Advanced.
Tick the checkbox labelled Replace permission entries on all child objects with entries shown here that apply to child objects.
If the steps above are still not working, log in as an administrator.
TIP: You could add the ‘Everyone’ group in here and grant ‘Full control’. This would mean all users would have access to Read/Write and run executables in this folder.
Error 8008: Source material does not open in SecureClient
If your device’s settings are improperly configured, you may see an Error: 8008 message when attempting to open source material in SecureClient.
This error is caused by an incompatibility with the Trusted Documents setting in Microsoft Office.
To resolve this issue, follow the steps below.
Open Microsoft Word/Excel.
Navigate to File.
Select Trust Center.
Select the Trust Center Settings button.
Select the Trusted Documents tab.
Ensure that the Allow documents on a network to be trusted checkbox is ticked.
You should also ensure that Microsoft Word and Excel are set as the default programs for documents and spreadsheets. To do this:
Navigate to Control Panel.
Select Programs.
Select Default Programs.
Select Set Your Default Programs.
Assign Microsoft Word and Excel as default programs.
After a candidate has taken a test, tests appear as In Progress/User disconnected in the Invigilate screen despite the tests actually having been completed.
This is caused by a lost or slow internet connection when the test was submitted by the candidate.
To resolve this issue, follow the steps below.
Check there is an internet connection available.
Relaunch SecureClient on the computer used by the candidate.
The result should then be uploaded. You can check if this is successful by viewing the Invigilate screen.
Installing SecureClient on a locked-down laptop
When trying to download SecureClient, issues may be encountered because test centres might have restricted permissions on laptops.
To resolve this issue, try the steps below.
Installer blocked
The SecureClient installer will not run because the files are blocked.
To fix this, select Unblock in the Properties section of the MSI file.
MSI files not recognised by Windows
The MSI files are not recognised as installation files. This is due to restrictions set on the laptop.
To fix this, the installer needs to be run using the Command Prompt. Follow the steps below to do this.
Open Command Prompt by selecting Start, then Run, then cmd.
Change the Directory to where the SecureClient installer is saved.
Enter the command msiexec /i SecureClientInstaller.msi.
Trouble installing SecureClient in a default location
You may struggle to install SecureClient successfully in a default location due to the command being incorrect.
To fix this, ensure that the command is written correctly. The command must be entered as follows:
msiexec.exe /i SecureClientInstaller.msi /q
Trouble installing SecureClient in My Folder as a custom location
You may struggle to install SecureClient successfully in My Folder as a custom location due to the command being written wrong.
To fix this, ensure that the command is written correctly. The command must be entered as follows:
Unable to install SecureClient in the default file location
You may be unable to install into the default file location, caused by restricted file permissions.
To fix this, create a new folder and install the SecureClient in this location. Follow the steps below to do this.
Create a new folder within the root of C:\.
Run the installer.
Select the folder you created as the install location.
SecureClient Update Loop
When SecureClient is launched it can get stuck in an update loop.
To resolve this issue, follow the steps below.
Find the folder on your computer where you have installed SecureClient.
Open the folder.
Right-click SecureClientInitialRun.
Run as administrator.
TIP: If SecureClient is still stuck on an update loop then you may need to grant read/write permissions on the SecureClient folder. You can do this by logging in as a user with higher permissions.
NOTE: If the above fails, your version of SecureClient may be more than two versions behind and thus you will need to reinstall it using the latest MSI file, which you can find on the /launchtest page.
Updates are invalid
When SecureClient is launched, it initially checks the Surpass server for any updates made to the software. If the error message Updates are invalid appears, this means SecureClient has tried to check for updates but has been prevented from doing so.
The most common cause of this block is a proxy server. Alternatively, updates may have been found, but there are not enough local user permissions on the PC to write to this directory.
To resolve these issues, follow the steps below.
Ensure that Read/Write permissions have been granted for the SecureClient folder.
Log in as an administrator to download updates.
Check whether a proxy server is blocking access to the update’s URL. Resolve this by allowing access to the update URL, or by entering the correct proxy details into the proxy.XML.
Ensure that firewall or anti-virus software is not preventing the application from running correctly.
SecureClient for iPad/Mac
While the common troubleshooting issues found on desktop devices are not applicable to tablet devices, there are some issues exclusive to SecureClient for iPad and Mac.
This includes the simulated Word and Excel editors enabled for Managed File Attach XLSX and DOCX files if Requires BYOD Mode is enabled in Test Creation. For more information on BYOD mode, read ‘Setting up BYOD mode‘ in Configuring a test for SecureClient.
For more information on what media and source material file types are supported in other delivery methods, read ‘Supported file types’ in Importing files to the media library.
Microsoft fonts not displaying correctly
Microsoft-specific fonts revert to the closest available Apple font family on SecureClient for iPad/Mac.
NOTE: This is a limitation of iPadOS/MacOS devices and there is currently no fix for this issue.
Test feedback
Feedback shown to candidates at the end of tests is not supported in SecureClient for iPad/Mac tests. For more information on test feedback, read ‘Test feedback’ in Creating a test with the Test Wizard.
Test session states
Tests delivered using SecureClient for iPad/Mac only display as Ready in the Invigilate grid, until they are Finished. Their state is otherwise not reflected in the Invigilate grid (for example, if the User disconnected) and test sessions cannot be manually affected by an invigilator (for example, Paused). For more information on test session states, read About the Invigilate screen.
NOTE: These limitations also mean candidates cannot switch device during a test session.
Videos not autoplaying
For items with MP4 video attached, the media does not autoplay in SecureClient for iPad/Mac tests. The Media Player Mode setting uses the Standard setting regardless of whether it is set to Autoplay. Candidates must manually start video playback.
NOTE: This is a limitation of iPadOS/Mac devices and there is currently no fix for this issue.
For more information on video player options, read ‘Additional options’ in Adding video to an item.
Further reading
Read the following articles to learn more about SecureClient: