Problem/Symptom

Description

Remedial Action

System aborts the batch during the initial phase of a sample run, after some lengthy timeout.

Audit trail messages refer to an "exception from run control", and the Status UI shows that one or more modules are "Not Ready".

Upon batch ready check, Chromeleon checks whether the instrument is currently "Idle" and no module is in "Not Ready" state.

However, at that time, the module state is determined by the method currently active in the instrument. (This method can be inspected via the Status UI: right-click to open the context menu and then select Method).

When the batch ready check passes, and the first sample downloads the method defined for this sample, method settings may not be the same as in the previously active method. Thus, a module state may change to "Not Ready". Some conditions will only be temporary (for example, until a different nominal oven temperature has been reached, or required lamps are ignited and warmed up). Some conditions, however, may persist, for example, lamp failures or a mixer mismatch. A result of such a permanent condition is that eventually a method start timeout will occur. The respective error messages are then logged in the Audit Trail.

Prior to batch ready check, make sure that the settings in the currently active method match the settings for relevant parameters used in the sample methods, such as "Enable Analysis when front door open", "Enable Analysis With any temperature", "Lamps on required for acquisition", or "Required Mixer".

As a result, any module that is not ready for the first analysis will then be clearly indicated in the Status UI prior to the batch ready check.

Screen flickers when you open ICF status window from the ICF panel when Chromeleon is running as a published Citrix application.

This scenario occurs when connecting to a Windows Server 2003 terminal server by using a third-party terminal client, such as a Citrix ICA client.

This issue does not occur when you use Remote Desktop Connection (RDC) to create the terminal server session.

This is a Microsoft Windows issue. The problem occurs because the non-administrator user account cannot access the %WINDIR%\System32 folder.

To resolve this problem, install the Microsoft hotfix for Windows Server 2003. For a detailed problem description and download information, refer to the corresponding Windows Server 2003 support page (Article ID: 955692) provided in the Microsoft Support Solution Center.