Clarity Error Messages
List of error messages:
▌An unknown error occurred while accessing C:\Users\<user name>\AppData\Local\Temp\Clarity\$ch1run.raw
It can be displayed during the start of the acquisition, probably when the User does not have writing rights into C:\...\Clarity.
▌Attempted an unsupported operation.
It may occur when accessing a broken dialog or window. Please contact our support and describe in which window it happened.
▌Blocked HW key
Your HW key has for some reason been blocked. Contact our support for help.
▌Cannot add device group
When trying to drag the whole group of devices (AS, GC, ...) over to the Instrument. To add device to the instrument drag always one device at once.
▌Cannot add selected (sub)device:
The message lists the reasons, why it is not possible to add selected device to the Instrument (for example the device and selected Instrument Type exclude each other, or the station does not have unlocked corresponding license, the device is already added to another Instrument, etc.).
▌Cannot create Detector/Pump/Autosampler...
This error message can occur if the device requires registration of an library, that was not successful. Please contact our support.
▌Cannot create RAW file
Cannot create raw file C:\Users\<user name>\AppData\Local\Temp\Clarity\$ch1temp.raw indicates some problems during creation of the chromatogram at the end of the analysis.
After starting the analysis, the file $ch1run.raw is created. When the analysis finishes, it is then renamed to $ch1last.raw from which the chromatogram *.prm is created. The file $ch1temp.raw gets created in case the renaming is not possible - usually due to a modal error message which awaits confirmation.
▌Cannot establish communication with XXXX SN xxx! XXXX SN xxx might not be turned on, connected, installed, configured or it might be malfunctioning or in use by another user.
In an attempt to open Instrument which has an uncommunicative device in configuration (e.g. the device is turned OFF). Retry if you think you resolved the problem (e.g., you turned the device ON), or cancel to continue to Instrument window that will be in Communication Error state - no measurement possible, but you can work with already measured chromatograms or prepare methods/sequences.
▌Cannot open file XXX. The file is already open on Instrument YYY.
If you attempt to open any file that is already opened on another instrument.
▌Cannot open USB communication for XY
For example Colibrick. Possible causes are if the A/D converter is connected over a USB hub or if there is a problem with DLL registration.
▌Changing project requires to restart instrument. (You will be prompted to save modified files.) Is this OK ?
If you have unsaved changes in any window of the Instrument and you also want to change a project.
▌Clarity is already running!
Appears during the startup of clarity.exe if another instance is already running.
▌Clarity is unable to find HW key
Appears if Clarity has lost communication with the HW Key. The dialog is displayed for a predefined period of time and then the application is closed. The option Retry checks again for the HW Key and resumes to Clarity upon detection. Clicking Close closes Clarity.
▌Clarity.psw file has been changed. Please see help file for possible reasons.
When upgrading Clarity from versions older than 8.0, this dialog may occur at first run
When manipulation with the *.psw file has been detected, it appears during the start of Clarity . This manipulation may mean a *.psw file from another station was copied to the Clarity configuration folder (CLARITY\CfG).
▌Clarity.psw file has been corrupted. Clarity will now terminate. Replace the corrupted Clarity.psw file in Clarity folder (C:\Clarity\Cfg) with default file from the backup folder C:\Clarity\Cfg\Back\Last installation. All user accounts will be lost.
Appears during the start of Clarity when *.psw file is corrupted (illegible). Clarity will not start at all. An empty *.psw file from the \Cfg\BACK\LAST_INSTALLATION\ subfolder can be used, all user accounts must be recreated and all GLP options (if used) must be re-selected, or in the case you have made back up of Clarity.psw file, you can use it now, and do not have to set all the user accounts and settings again.
▌Configuration file C:\Clarity\Cfg\Clarity.cfg is not valid. The file was either damaged or created with a later version of the software. The backup copy will be used.
Appears when starting Clarity with a non-compatible *. cfg file. Used Clarity.cfg is empty so all the System Configuration settings and adding devices to the Instruments have to be done again.
▌Configuration file C:\Clarity\Cfg\Clarity.cfg is not valid. The file was either damaged or created with a later version of the software. Contact support for help.
Appears when starting Clarity with a non-compatible *. cfg file. Backup cannot be restored in this case. If possible you can try to copy Clarity.cfg from installation media, or another installation of Clarity, and rewrite the corrupted file with it. Then you will have to manually reconfigure the System Configuration settings.
▌Detector 1 (= NAME OF SIGNAL) is not acquiring any data
In case of high load on a low performance PC. This error may also occur due to physically damaged A/D converter during acquisition.
▌Error Occurred During Setup.
This message can happen during the configuration of a control module.
▌FAILED to send method to (sub)device
If the sending of the method is unsuccessful, e.g., device stops communicating with any of its parts.
▌Fraction table contains overlapping time intervals. Please amend the table so that the time intervals don't overlap.
This error occurs if the user creates a wrong table for a fraction collector with overlapping times. It is a warning for the user that the fraction table needs to be corrected in order to avoid presence of the overlapping time segments in the table.
▌HW Key test Failed
Your HW key is not working correctly. Contact our support for help.
▌Incompatible device driver
The kernel driver and the driver in the Clarity do not match.
▌Invalid rows detected in the Method Setup - Event Table. The invalid rows will be marked out and skipped from events processing
This message appears during the opening of a method whose Event Table uses something that is not in the configuration anymore.
▌Method file XXX does not exist. Please select a valid method. For more information about warnings and errors on the other rows, point mouse cursor over the left side of "Status" Column for each row.
This happens when opening or checking a sequence which contains a name of a non-existent method.
▌Microsoft Visual C++ 2005 Redistributable Package (x86) installation failed. Exit code: 1618. Installation of Windows update or another program is already in progress. Let it finish first, restart the PC if necessary, and then start Clarity installation again.
This can happen when Windows update or another program is already being installed, in rare cases this is caused by Windows installer process not being terminated properly. Waiting for installation to finish and restarting PC should resolve the issue.
▌Missing keylock drivers
The drivers for the HW key are missing or corrupted. They need to be reinstalled. Please contact our support.
▌No data received for 10 s.
This message may occur during an acquisition if Clarity has not received any data for a prolonged period of time. Make sure the PC is not under high load during the acquisition.
▌Please enter valid Data Size. Minimum is 2.
The content of the imported file is too short (only one data point on the graph).
▌Project directory <Project name> already exists but has no project file! Do you want to create the project file?
Project directory with this name already exists but it misses its project *.prj file. If you select Yes, the project *.prj file will be created, and Project can be used.
▌Project file <Project name> already exists but has no project directory! Do you want to create the project directory?
Project *.prj file with given name already exists, but there is no project folder with matching name. If you select Yes, the empty project folder with matching name will be created.
▌Project <Project name> already exists! Choose a different name.
Project with this name already exists. Select unique name for newly created project.
▌Stop time must be larger than Start time for individual fractions.
This message concerns fraction collectors. The Fraction table contains incorrect settings of Start Time and Stop Time for one or more rows. Each row of the Fraction table has to be set such that the Stop Time is always higher than the Start Time on the same row.
▌The directory specified for instrument x does not exist: C:\...... It is necessary to set correct directory with projects for instrument x in Directories dialog.
This message appears during the opening of an Instrument window while deleting/renaming or damaging the respective directory in the meantime.
▌The report style "*.sty" does not exist or is damaged. Default report style "Noname" will be used instead.
This message appears during the opening of any window while deleting/renaming or damaging the respective *.sty file in the meantime.
▌Too many peaks in chromatogram. Try to increase peak width or threshold
Peak Width was set to a low value (e.g. to 0.001 minutes in a 80 minute noise chromatogram).
▌Too much data for FFT. Max. number of samples in interval is 2E6
FFT filter is applied to a too large interval.
▌Unable to lock instrument in unprotected mode!
When no user is created and you attempt to Lock an opened instrument.
▌XXX.met does not match current instrument configuration. To use this method for acquisition, it must be adapted and then saved. Do you want to adapt the method? If you click No method will be opened as read only.
If the instrument or method being opened does not correspond to the hardware which is currently present in the configuration.
▌You are attempting to paste incompatible or out of range values
This message may occur while copying a sequence table prepared in Excel. Make sure the form of the table and its values are correct.
Error messages in IQ report:
▌Wrong checksum (size), probably different version of the file
Check the IQ Report to see if the Clarity installation is correct.
▌Warning: unknown control module
Happens e.g. in Clarity Lite for drivers of control modules if the PC finds a full version of Clarity installed.
▌Failed: bad size
The file has a different size (compared to iq.chk) - occurs e.g. in Clarity Full for .dll from Lite, if that one was the last registered.
▌Failed: bad checksum
The file has a different checksum (compared to iq.chk) - occurs for .dll which has the right size, but the checksum does not match. For example if you edit the size of iq.chk manually.