Software Status Bulletin

Agilent_Instrument_Control_Framework_(ICF)     

Preface
-------------------------
This Software Status Bulletin (SSB) documents all known problems in the software
product designated above. The SSB is derived from Known Problem Reports (KPR)
which result from user problems that have been classified as documentation
problems or software defects. When a KPR is written, an identifying number is
assigned to it, and the KPR is added to the next edition of the SSB.

User inputs that have been classified as Enhancement Requests are not documented
in the SSB. User problems that have been submitted, but that have not been
classified by the time the SSB is generated are not included in the SSB.

How to use the SSB
-------------------------
When you experience a problem with a product, first check this SSB to see if the
problem has been reported already, and if there is a temporary workaround
available for the problem, or if the problem has already been fixed by a new
revision. If the problem is not listed in this SSB then you may wish to report
it to the Response Center or to your field support representative.

To determine if your problem is documented in this SSB, first look in the
Keyword Index section of the SSB. Under each keyword is a listing of one-line
descriptions of related KPRs. If any of these sound like yours, locate the KPR
# in the Known Problem Reports section of the SSB, and read the full KPR. The
KPRs in the Known Problem Reports section are sorted by KPR #.

There are two sections in the SSB:
Keyword Index: This index is categorized by keyword. For each KPR there is a
brief description and a KPR #. A KPR may be associated with more than one
keyword.

Known Problem Reports: This section contains KPRs, with all the available
information relevant to the problem. KPRs in this section are sorted by KPR #.

Keyword Glossary

Keyword Index

Keyword: Acquisition

KPR#:3 Random Performance Dips during instrument control
KPR#:44 Calling abort between runs does not abort the sequence
KPR#:50 ICF cannot start another run after a run has been aborted
KPR#:49 ICF gets stuck in run state

Keyword: Acquisition , LC Control

KPR#:49 ICF gets stuck in run state

Keyword: Administration

KPR#:745243 Interoperability issues when using a barcode reader in ICF versions before 3.0 Update 3
KPR#:754631 Upgrade installation of ICF 3.2 to ICF 3.2 Update 1 results in an error

Keyword: Audit Trail

KPR#:4 Logging of all user actions concerning instrument parameters available
KPR#:15 Inconsistent formatting of method and timetable parameter in reports possible

Keyword: CE Control

KPR#:43 The actual state of the instrument could be incorrect.

Keyword: CE Control , GC Control , LC Control

KPR#:43 The actual state of the instrument could be incorrect.

Keyword: Configuration

KPR#:2 Single LC module configuration changes triggers instrument wide configuration change
KPR#:11 Exception message opening a module status interface
KPR#:13 G1330A/B Thermostat Temperature Settings are not applied like configured
KPR#:14 Possibility of identical modules in configuration screen after auto configuration
KPR#:22 The Close button on the post-auto configuration dialog disappears when the dialog window is resized.
KPR#:24 Detection of changes within the instrument auto configuration are not propagated to the CDS. User is not aware of all changes made.
KPR#:31 Creating custom well plates leads in some cases to unwanted handling exception warnings
KPR#:38 Sometimes the "Auto Configure" in the Instrument Configuration is interrupted
KPR#:42 Auto Configuration Button does not work for HeadSpace devices

Keyword: GC Control

KPR#:43 The actual state of the instrument could be incorrect.
KPR#:16 ICF does not provide the InjectorName fields for GC
KPR#:17 ICF does not provide the FirmwareVersion fields
KPR#:19 GC specific RunDelayTime features is not available
KPR#:36 Extend Run is ignored by G1888 HS Driver

Keyword: Installation

KPR#:5 Wrong link in IQT reports
KPR#:6 Improved IQT handling
KPR#:26 Uninstalling ICF before uninstalling GC drivers leads to an error and a rollback of the GC Drivers Uninstall.

Keyword: LC Control

KPR#:49 ICF gets stuck in run state
KPR#:43 The actual state of the instrument could be incorrect.
KPR#:7 Custom plates not working using German local settings
KPR#:8 Validation of Custom plates not working using German local settings
KPR#:9 Method Download for G1390B UIB fails using non-US local settings
KPR#:10 Calculation of Solvent Consumption
KPR#:12 Manual injector systems are not working in some Third Party Environment

Keyword: Localization (Chinese)

KPR#:21 English buttons instead of localized once in the configuration screens and autoconfiguration
KPR#:23 The instrument configuration dialog is not fully localized in all languages.
KPR#:25 The instrument Pre-configuration tool is only available in English language

Keyword: Localization (Japanese)

KPR#:21 English buttons instead of localized once in the configuration screens and autoconfiguration
KPR#:23 The instrument configuration dialog is not fully localized in all languages.
KPR#:25 The instrument Pre-configuration tool is only available in English language

Keyword: Localization (Japanese) , Localization (Chinese) , Localization (Portuguese)

KPR#:21 English buttons instead of localized once in the configuration screens and autoconfiguration
KPR#:23 The instrument configuration dialog is not fully localized in all languages.
KPR#:25 The instrument Pre-configuration tool is only available in English language

Keyword: Localization (Portuguese)

KPR#:21 English buttons instead of localized once in the configuration screens and autoconfiguration
KPR#:23 The instrument configuration dialog is not fully localized in all languages.
KPR#:25 The instrument Pre-configuration tool is only available in English language

Keyword: Method

KPR#:27 Opening a pretreatment method for a G1329A standard LC Autosampler and loading it for a G5667A Bio-inert Well-Plate Sampler results in an application error - thread exception.
KPR#:40 ICF: Dual Simultaneous injection sequence runs incorrectly when overlap method is used

Keyword: Performance

KPR#:401099 Method upload may result in deadlock identified by “server busy ” message

Keyword: Reports

KPR#:215586 IQT does not generate any reports
KPR#:560439 Installation of ELSD drivers is not qualified with SVT
KPR#:574380 Agilent ICF is missing in the Software Verification Tool
KPR#:584377 Incorrect version of LC drivers 3.3 SR1 in SVT Report
KPR#:586852 SV Report fails after LC drivers have been uninstalled

Keyword: Test - Application

KPR#:41 Error "could not open <zipfile>" when running Logfile Collector tool

Keyword: User Interface

KPR#:18 Auto-sampler User Interface shows wrong injection volume using overlap injection
KPR#:20 GC Status not updated in graphical user interface after termination of applicaiton
KPR#:28 Modification and printing of the RF Tag information is not possible
KPR#:45 "Status poll thread caught an exception" error in status dashboard
KPR#:201519 Applying the configuration to the SoftConfigurationUI a 2nd time did not have any effect
KPR#:245236 The tab to collect support information does not provide online help
KPR#:294753 Error collecting support info on 32 bit systems
KPR#:294842 Collect Support Info fails when executed 2nd time
KPR#:541584 Error collecting support info on 32 bit systems
KPR#:541585 Collect Support Info fails when executed 2nd time
KPR#:550677 Headspace status shows online after disconnect
KPR#:603948 HS 7697 The instrument status event feed is inactive/active
KPR#:642810 HS runs without signal source are aborted
KPR#:644815 GC-ALS/HS: Dual injection using barcode reading for only one injection fails
KPR#:650734 GC-ALS/HS: Using different barcode mismatch actions in full sequence mode is not supported
KPR#:714702 Status Dashboard crashes in localized versions of ICF
KPR#:754470 ELSD 1.8 instrument method not applied

Keyword: 

One-line Description:

Pretreatment may not downloaded to instrument prior a run

Problem:

It has been reported that methods using pre-treatments (injector program) may fail to downolad prior a run.

Temporary Solution:

Review the injection program parameters, save the method again and re-run the method.

Fix Information:

n/a

Keyword: 

One-line Description:

ICF: 6890 with G1888 missing vial proceeds, but sequence gets out of sync

Problem:

Framework 2.04.122 with driver 101 connected to 6890N.06.07 and G1888 Headspace . Start a 4 line sequence to G1888 with vial 2 missing. The hardware skips to vial 3, etc, correctly. The Instrument Log correctly shows that Vial 2 was missing, skipping to vial 3. However, the sequence does not abort vial 2, instead putting vial 3's data into vial 2's line in Run Automation. At completion of the sequence which seemingly runs for the time of the four runs, vial 2 shows Error: unexpected exception, Vial 3 is noted as 'State: Executing' and Vial 4 is 'Scheduled.'

Temporary Solution:

n/a

Fix Information:

The problem fixed in Headspace software B.01.07.2.

Keyword: 

One-line Description:

Online help for the instrument dashboard is not available.

Problem:

Nothing happens if you press "F1" when viewing the instrument dashboard. There is no help information displayed. Similarly there is no help information for the EMF status shown on the dashboard.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

The Status progress bar stops at 90% when using Multiple Headspace Extractions

Problem:

A sequence using a MHE method with 3 injections to vial 1 followed by 2 injections to vial 2 results in the status progress bar to show 90% 'Completing' as the final step after injecting.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

A sequence with overlapped injection for a GC/HS instrument causes the GC to lose connection.

Problem:

Set up a sequence with overlapped injection. Configure Recoverable Error for "GC Stop Button" to continue.
After pressing the GC stop button when the first sample is running and the 2nd vial has finished preparing, the sequence aborts and the application hangs. The GC loses the connection but this is not reflected in the status window.

Overlapped injection for GC combined with a HS is not supported.

Temporary Solution:

Overlapped injection for GC combined with a HS is not supported.

Fix Information:

Fixed with GC/HS drivers 3.6/3.2 included in ICF 3.1 Update 1.

Keyword: 

One-line Description:

Agilent.DriverLogFileCollector.exe does not collect logfiles when "Show hidden folders" is disabled in Windows.

Problem:

The Agilent.DriverLogFileCollector.exe tool cannot collect the ICF logfiles from C:\ProgramData when "Show hidden folders" is disabled in Windows and produces an empty .zip file.

Temporary Solution:

After enabling "Show hidden folders" in Windows, the Agilent.DriverLogFileCollector.exe tool is able to collect the logfiles.

Fix Information:

The Agilent.DriverLogFileCollector is obsolete. Since ICF 2.6 logfiles can be collected via the Support Info Tool integrated as a Tab in the StatusUI.

Keyword: 

One-line Description:

No solvent consumption calculation possible for Flexcube

Problem:

Unlike for pumps, ICF does not offer solvent consumption calculation for Flexcubes.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Repeated auto configuration fails

Problem:

When the "Clear" button was pressed in the ICF Configuration UI after a successful AutoConfiguration, then all subsequent AutoConfiguration attempts for the same host/IP will fail and the list of configured modules will remain empty.

Temporary Solution:

A workaround is to close the ICF Configuration UI and open it again.

Fix Information:

Fixed in ICF 2.6.

Keyword: 

One-line Description:

Possible missing or wrong monitor signal data when the configuration changes.

Problem:

On rare occasions, during a very small time period after a configuration change, monitor signal data can contain wrong data or no data at all.

All other acquired data that is stored in data files is not affected.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 3.2

Keyword: 

One-line Description:

Signal data is only acquired when detector and inlet are on the same channel

Problem:

Currently, only signal data is acquired for detectors that are on the same channel as the inlet.

This means that:
- all signals related to the back injector are not acquired when injecting from the front inlet
- all signals related to the front injector are not acquired when injecting from the back inlet

Monitor signals / Online Plot is not affected by this issue and all selected signals are displayed.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 3.1

Keyword: 

One-line Description:

Method upload may get wrong settings for 7697 Headspace

Problem:

The 7697 Headspace can contain wrong method settings during a method upload when both the following conditions are true:
1. Run time of the GC is less than the Headspace processing time. Processing time is the time from picking up the sample vial until it is returned.
2. The Headspace method for the current sample is different compared to the method for the previous sample.

Temporary Solution:

Workaround: Do not use different Headspace methods in a sequence.

Fix Information:

Fixed in ICF 3.2

Keyword: 

One-line Description:

Second run does not start when AUX traces are disabled

Problem:

When data collection for AUX traces are disabled, the first run will complete normally but all following runs will not start. An exception or message "Run still ongoing" may appear. 
This problem does not happen if all AUX traces are enabled.
This only affects applications that use the latest ICF interface for enabling/disabling AUX traces.

Temporary Solution:

Workaround: Make sure that all AUX traces are enabled.

Fix Information:

Fixed in ICF 2.6 Update 3

Keyword: 

One-line Description:

Injection does not start for 7890+1888 with Gas Saver mode on and splitless inlet

Problem:

As a G1888 headspace sampler does not send a “preprun” signal by the hardware, the Gas saver does not switch off and the inlet source for the splitless injection will not get the used conditions to inject. With these conditions the GC does not become “Ready” and no injection and run will be started. Affected systems are all devices not sending a “preprun” signal via hardware, e.g. G1888A or external non-Agilent devices.

Temporary Solution:

n/a

Fix Information:

With ICF 3.0 Update 1 and GC driver 3.4 a checkbox “Prep Run on Manual Request” was introduced. When activated, a prepare command is automatically send to the GC before a manual or external injection occurs (not supported with 6890).

Keyword: 

One-line Description:

Signal data is only acquired when detector and inlet are on the same channel

Problem:

Currently, only signal data is acquired for detectors that are on the same channel as the inlet.

This means that:
- all signals related to the back injector are not acquired when injecting from the front inlet
- all signals related to the front injector are not acquired when injecting from the back inlet

Monitor signals / Online Plot is not affected by this issue and all selected signals are displayed.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 2.6 Update 4

Keyword: 

One-line Description:

Application hangs during second method download after an error in the first method download occurred

Problem:

The problem starts when an error occurs during method download. The run preparation is aborted. The next download or upload of a method will cause the application to hang.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 3.0 Update 2

Keyword: 

One-line Description:

Module goes offline causing runs to get aborted

Problem:

At random times, one module can go offline causing a run or sequence to get aborted. This is due to rare communication losses with the LC caused by interaction of various software components.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 3.1

Keyword: 

One-line Description:

LC driver takes over Application.ThreadException event

Problem:

The LC Driver 3.5 delivered with ICF 3.2 and 3.2 Update 1 assigned an event-handler to the Application.ThreadException event but only the most recently added handler will be called on an unhandled exception, so Data systems could not handle ThreadExceptions. 

Temporary Solution:

n/a

Fix Information:

Fixed in LC driver 3.5 SR2 (ICF 3.2 Update 2)

Keyword: Acquisition

One-line Description:

Random Performance Dips during instrument control

Problem:

Memory Process Handling need to be improved, as it is possible that the memory is not cleared of all processes which may results in slow interaction with the instrument.

Temporary Solution:

n/a

Fix Information:

Fixed in A.02.01

Keyword: Acquisition

One-line Description:

Calling abort between runs does not abort the sequence

Problem:

When calling an abort in between runs of a sequence, then the sequence is not aborted and the next run will start.

Temporary Solution:

Call abort when the next run has started.

Fix Information:

Fixed in A.02.05

Keyword: Acquisition

One-line Description:

ICF cannot start another run after a run has been aborted

Problem:

When a run is being aborted after more than 30 seconds and there was one or more modules for which no signals were acquired, then sometimes no further runs can be started in ICF. Some Modules (e.g. Valves) do not have signals, and therefore can cause this behavior.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF A.02.05

Keyword: Acquisition , LC Control

One-line Description:

ICF gets stuck in run state

Problem:

At the end of a run, some LC Modules may trigger another run and cause ICF to get stuck in the run state. The Status UI shows idle, but no further runs are possible until ICF is restarted.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF A.02.05

Keyword: Administration

One-line Description:

Interoperability issues when using a barcode reader in ICF versions before 3.0 Update 3

Problem:

False barcode reader inconsistency preventing method download for methods interoperating between ICF versions higher and lower than 3.0 Update 3 (GC driver 3.5 SR1).

Temporary Solution:

Download the method outside of a run, upload and save it again. It may also be necessary to reset the configuration of the GC.
Alternatively, avoid interoperability scenarios across ICF 3.0 Update 3 when using GC/HS with barcode reader.

Fix Information:

Fixed in ICF 3.0 Update 3 (GC driver 3.5 SR1)

Keyword: Administration

One-line Description:

Upgrade installation of ICF 3.2 to ICF 3.2 Update 1 results in an error

Problem:

Upgrading to ICF 3.2 Update 1 from ICF 3.2, leads to the error "Another version of this product is already installed" for the LC driver installation.

Temporary Solution:

Remove the LC driver before installing ICF 3.2 Update 1. 

Fix Information:

Fixed in ICF 3.2 Update 2

Keyword: Audit Trail

One-line Description:

Logging of all user actions concerning instrument parameters available

Problem:

Currently instrument parameter changes within the method execution are logged. Configuration changes and modifications outside a run are not documented.

Temporary Solution:

n/a

Fix Information:

Starting with A.02.01 all parameters changes and actions are logged.

Keyword: Audit Trail

One-line Description:

Inconsistent formatting of method and timetable parameter in reports possible

Problem:

The LC drivers offer component to the hosting analytic systems to handle method and timetable parameters. One component has inconsistent formatting information for the decimal places of method and timetable parameters. Depending on the hosting analytic system, certain reports may show inconsistent formatting of these parameters when they are reported.
e.g. Two digits instead of three.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: CE Control , GC Control , LC Control

One-line Description:

The actual state of the instrument could be incorrect.

Problem:

In rare occasions, due to driver synchronization issues, the actual state of the instrument could be wrong and reports an incorrect state.
This means an incorrect state is displayed in the CDS, or certain actions depending on the instrument state can not be performed.

Temporary Solution:

Depending on the incorrect state:
- make the instrument ready again through the status dashboard
- take the instrument offline and online
- restart the CDS

Fix Information:

Fixed in A.02.05

Keyword: Configuration

One-line Description:

Single LC module configuration changes triggers instrument wide configuration change

Problem:

A single LC module configuration change triggers an instrument wide configuration change, which may result in performance slow down. Single module configuration changes have to be handled as single module change only.

Temporary Solution:

n/a

Fix Information:

Fixed in A.02.01

Keyword: Configuration

One-line Description:

Exception message opening a module status interface

Problem:

Open a module status interface or execute a module reconfiguration the system may respond with an exception message.

Temporary Solution:

n/a

Fix Information:

Fixed with A.02.01

Keyword: Configuration

One-line Description:

G1330A/B Thermostat Temperature Settings are not applied like configured

Problem:

The Agilent G1330A/B Thermostat allows the operator to configure, if the temperature setting for this module is handled a method parameter or as simple control parameter. This kind of configuration handling differs to configuration handling of some hosting data systems and it might be possible that this configuration step is not executed in some CDS environments.

Temporary Solution:

The Instrument Control Framework revision A.02.01 offers a pre-configuration tool offering a possibility to perform the G1330A/B Thermostat configuration. The pre-configuration tool is part of the installation package. Please locate the file Agilent.InstrumentControl.InstrumentPreConfigurator.exe using your explorer and execute the file to perform the configuration.

Fix Information:

n/a

Keyword: Configuration

One-line Description:

Possibility of identical modules in configuration screen after auto configuration

Problem:

The Instrument Control Framework A.02.01 offers the possibility to configure instruments of different families. Executing the auto configuration cumulative adds the detected instruments. Up till A.02.01 the already configured modules were cleared, now the new modules are added without clearing the current configuration. In case an identical module is detected again and it shows up twice in the configuration.

Temporary Solution:

The doubled, identical modules need to be removed manually.

Fix Information:

n/a

Keyword: Configuration

One-line Description:

The Close button on the post-auto configuration dialog disappears when the dialog window is resized.

Problem:

This problem refers to the additional instrument configuration windows that appear if additional configuration options are available.

Temporary Solution:

n/a

Fix Information:

The close button stays visible when resizing the post-auto configuration window.

Keyword: Configuration

One-line Description:

Detection of changes within the instrument auto configuration are not propagated to the CDS. User is not aware of all changes made.

Problem:

The event is only raised after manually adding, removing, clearing and modifying the configuration.
After auto configuration, the IICConfigUI.DirtyEvent is not raised.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Configuration

One-line Description:

Creating custom well plates leads in some cases to unwanted handling exception warnings

Problem:

Creating custom well plates leads in some cases to unwanted handling exception warnings

Temporary Solution:

n/a

Fix Information:

In order to resolve these warnings ICF A.02.03 SP1 layer is required. This is supplied in ICF package A.02.03 Driver Update 2.

Keyword: Configuration

One-line Description:

Sometimes the "Auto Configure" in the Instrument Configuration is interrupted

Problem:

During the "Auto Configure" procedure sometimes an error message appears. If this happens, the instrument will not be configured.

Temporary Solution:

Repeat "Auto Configure".

Fix Information:

Fixed with ICF A.02.05

Keyword: Configuration

One-line Description:

Auto Configuration Button does not work for HeadSpace devices

Problem:

Nothing happens when clicking on the auto configuration button for HeadSpace devices.

Temporary Solution:

HeadSpace devices can only be configured manually.

Fix Information:

Autoconfiguration has been disabled for all GC/Headspace devices. These devices must be configured manually.

Keyword: GC Control

One-line Description:

ICF does not provide the InjectorName fields for GC

Problem:

ICF need to be enhanced to handle GC/Headspace Injection Samplers.

Temporary Solution:

n/a

Fix Information:

Fixed in A.02.02

Keyword: GC Control

One-line Description:

ICF does not provide the FirmwareVersion fields

Problem:

ICF need to be enhanced to show the GC/Tray/Sampler Firmware revisions.

Temporary Solution:

n/a

Fix Information:

Fixed in A.02.02

Keyword: GC Control

One-line Description:

GC specific RunDelayTime features is not available

Problem:

The Agilent GC allows to minimize the data packages using the RunDelayTime feature. If a peak is expected at e.g. 2.5 min, the collection can be set to start at 2 min.
This features is not available for 68xx and 78xx GC´s running in ICF A.02.01/A.02.02

Temporary Solution:

n/a

Fix Information:

Fixed with A.02.03

Keyword: GC Control

One-line Description:

Extend Run is ignored by G1888 HS Driver

Problem:

Extend Run is ignored by G1888 HS Driver. Extending runs is not supported by this module.

Temporary Solution:

Extending runs is not supported by this module.

Fix Information:

n/a

Keyword: Installation

One-line Description:

Wrong link in IQT reports

Problem:

Following the link given in the ICF IQT report, the system responds with an error as it does not find the reference file.

Temporary Solution:

n/a

Fix Information:

The defect is fixed in A.02.01.

Keyword: Installation

One-line Description:

Improved IQT handling

Problem:

The current ICF Installation Qualification requires IQT execution per component, in this case 
LC Driver Package and Framework, located at different locations.

Temporary Solution:

n/a

Fix Information:

Starting with A.02.01 there is only one access point to the IQT, supporting attended and unattended execution.

Keyword: Installation

One-line Description:

Uninstalling ICF before uninstalling GC drivers leads to an error and a rollback of the GC Drivers Uninstall.

Problem:

The installer of the GC drivers depends on ICF being present first.

Temporary Solution:

n/a

Fix Information:

The GC Drivers install package no longer depends on the ICF Install Package.

Keyword: LC Control

One-line Description:

Custom plates not working using German local settings

Problem:

The method download for customer plates using non-US local settings the method download will result in an error.

The system required the following settings (US-local settings)
Decimal symbol = '.' 
Digit  grouping symbol = ','

Temporary Solution:

Apply US regional settings to avoid the method download problem.

Fix Information:

Fixed in A.02.01

Keyword: LC Control

One-line Description:

Validation of Custom plates not working using German local settings

Problem:

The validation for customer plates using non-US local settings the method download will result in an error.

The system required the following settings (US-local settings)
Decimal symbol = '.' 
Digit  grouping symbol = ','

Temporary Solution:

Apply US regional settings to avoid the method download problem.

Fix Information:

Fixed in A.02.01

Keyword: LC Control

One-line Description:

Method Download for G1390B UIB fails using non-US local settings

Problem:

Executing a G1390B UIB method in a non-US local setting environment, the method download will result in an error.

The system required the following settings (US-local settings)
Decimal symbol = '.' 
Digit  grouping symbol = ','

Temporary Solution:

Apply US regional settings to avoid the method download problem.

Fix Information:

Fixed in A.01.05 SP1

Keyword: LC Control

One-line Description:

Calculation of Solvent Consumption

Problem:

Starting with A.02.01 ICF enables the possibility for the hosting CDS to calculate solvent consumption (on method level).

Temporary Solution:

n/a

Fix Information:

Implemented with A.02.01

Keyword: LC Control

One-line Description:

Manual injector systems are not working in some Third Party Environment

Problem:

The Agilent manual injector triggers the run automatically on the instrument. This behavior differs to other vendors implementation, whereas the manual injector requires a start run by the data system.
Due to this different handling some 3rd party data systems are not yet prepared to implement the Agilent control of manual injectors. Therefore manual injections can not be executed in that particular Third Party environment.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Localization (Japanese) , Localization (Chinese) , Localization (Portuguese)

One-line Description:

English buttons instead of localized once in the configuration screens and autoconfiguration

Problem:

On localized systems, some English buttons are present in the configuration screens and autoconfiguration instead of localized once.

Temporary Solution:

n/a

Fix Information:

Fixed with ICF A.02.03

Keyword: Localization (Japanese) , Localization (Chinese) , Localization (Portuguese)

One-line Description:

The instrument configuration dialog is not fully localized in all languages.

Problem:

In Japanese, Chinese and Portuguese languages some text in the dialog appears in English.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Localization (Japanese) , Localization (Chinese) , Localization (Portuguese)

One-line Description:

The instrument Pre-configuration tool is only available in English language

Problem:

Japanese, Chinese and Portuguese languages for the instrument Pre-configuration tool are missing.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Method

One-line Description:

Opening a pretreatment method for a G1329A standard LC Autosampler and loading it for a G5667A Bio-inert Well-Plate Sampler results in an application error - thread exception.

Problem:

However a method resolution for these modules does not appear.

Temporary Solution:

n/a

Fix Information:

The application error no longer appears.
Instead, a method resolution dialog appears and works as expected.

Keyword: Method

One-line Description:

ICF: Dual Simultaneous injection sequence runs incorrectly when overlap method is used

Problem:

ICF A.02.03 with GC/HS A.03.01.90 connected to T7890B.02.03.2 with 7693 system.
Create 1 min ALS method with Sample overlap checked. Create a sequence that will generate dual simultaneous injection: 6 lines of sequential vials alternating front and back injector. When the vials are sequential: 1/2, 2/3, 3/4, the second injection tries to pick up the same vial as the front for the back injection.
When the vials skip one vial for each line: 5/6, 7/8, 9/10, then the vials are run incorrectly for all but the first line: 5/6, 6/7, 8/9, though the Run Automation shows the vials run as set in the sequence.

Temporary Solution:

n/a

Fix Information:

The problem was fixed in GC/HS Driver B.01.07.2.

Keyword: Performance

One-line Description:

Method upload may result in deadlock identified by “server busy ” message

Problem:

In Empower 3 using ICF the following sporadic issue has been reported:
During a method down- or upload within a sequence (sample set) the system enters into a deadlock showing a  Windows message box with the title "Server Busy". The "Switch To …" and "Retry" button are accessible but do not correct the problem.
The system becomes unusable after this error and a reboot of the controller is required or a restart of the instrument control services.

Temporary Solution:

n/a

Fix Information:

Fixed with ICF 2.6 Update 2

Keyword: Reports

One-line Description:

IQT does not generate any reports

Problem:

If the computer name is longer than 15 characters, iqt.exe does not work properly, gives no feedback and no reports are being generated.

Temporary Solution:

Rename the computer, using less than 15 characters

Fix Information:

Fixed in ICF 3.0

Keyword: Reports

One-line Description:

Installation of ELSD drivers is not qualified with SVT

Problem:

The "Software Verification Tool" (SVT) does not check the installation of the ELSD drivers. The report does not contain any of the driver files. The driver itself is installed and operational.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 3.0 Update 3

Keyword: Reports

One-line Description:

Agilent ICF is missing in the Software Verification Tool

Problem:

When only ICF is uninstalled (and not the driver packages) and ICF is later reinstalled, then Agilent ICF no longer appears in the Agilent Software Verification Tool.

Temporary Solution:

Do a repair of the LC driver package.

Fix Information:

Fixed in ICF 3.1

Keyword: Reports

One-line Description:

Incorrect version of LC drivers 3.3 SR1 in SVT Report

Problem:

In the SVT report, the LC drivers 3.3 SR1 display a wrong version text (3.2 SR1 instead of 3.3 SR1). The build number (3.3.42.0) in the same line is correct. 

Temporary Solution:

n/a

Fix Information:

The version text in later versions of the LC drivers is correct.

Keyword: Reports

One-line Description:

SV Report fails after LC drivers have been uninstalled

Problem:

When uninstalling the LC driver, the agilent.diagnostics.dll will be removed.
The SV report then shows this file as missing.

Temporary Solution:

Workaround: Perform a repair installation of the ICF framework.

Fix Information:

Fixed for all Upgrades from versions higher than ICF 3.2

Keyword: Test - Application

One-line Description:

Error "could not open <zipfile>" when running Logfile Collector tool

Problem:

When running the Agilent.DriverLogFileCollector.exe, an error message "Could not open <zipfile>" is displayed.
The log files have actually been collected and the error can be ignored.

Temporary Solution:

Click away the error.

Fix Information:

Fixed in A.02.05

Keyword: User Interface

One-line Description:

Auto-sampler User Interface shows wrong injection volume using overlap injection

Problem:

Using the overlap feature within a sequence, the Auto-sampler status User interface updates the injection volume with the injection volume of the next sequence line directly after starting the current run. The vial location shown in the UI remains on the current executed sequence line information. 

This user interface defect is only reported for autosamplers, not for high-throughput samplers.

Temporary Solution:

n/a

Fix Information:

Fixed in A.02.03

Keyword: User Interface

One-line Description:

GC Status not updated in graphical user interface after termination of applicaiton

Problem:

GC Status is not updated in the graphical user interface after disconnecting the CDS.

Temporary Solution:

n/a

Fix Information:

Fixed in A.02.03

Keyword: User Interface

One-line Description:

Modification and printing of the RF Tag information is not possible

Problem:

Currently it is only possible to display the RF Tag information in the instrument dashboard window, but it is not possible to edit or report this information.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: User Interface

One-line Description:

"Status poll thread caught an exception" error in status dashboard

Problem:

On rare occasions, the status dashboard may report the error: "Status poll thread caught an exception".
The device goes offline.

Temporary Solution:

Restart the CDS.

Fix Information:

Fixed in A.02.05

Keyword: User Interface

One-line Description:

Applying the configuration to the SoftConfigurationUI a 2nd time did not have any effect

Problem:

Applying the configuration to the SoftConfigurationUI a 2nd time did not have any effect. The UI was not reset to the initial values.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 2.6.

Keyword: User Interface

One-line Description:

The tab to collect support information does not provide online help

Problem:

There is no help button to provide online help for the info tab to collect support information. Pressing F1 also does not open a help file.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 3.3

Keyword: User Interface

One-line Description:

Error collecting support info on 32 bit systems

Problem:

Collecting support information with one of the "Installed Programs" checkboxes active will fail on 32 bit systems.

Temporary Solution:

Collect support information without "Installed Programs" checked. This will not result in an error.

Fix Information:

Fixed in ICF 3.0.

Keyword: User Interface

One-line Description:

Collect Support Info fails when executed 2nd time

Problem:

If you collect the support information a second time with less checkboxes checked than the first time, an error will prevent support information being collected.

Temporary Solution:

As a workaround you can close and reopen the dialog or application hosting the support information collection tool.

Fix Information:

Fixed in ICF 3.0.

Keyword: User Interface

One-line Description:

Error collecting support info on 32 bit systems

Problem:

Collecting support information with one of the "Installed Programs" checkboxes active will fail on 32 bit systems.

Temporary Solution:

Collect support information without "Installed Programs" checked. This will not result in an error.

Fix Information:

Fixed in ICF 3.0.

Keyword: User Interface

One-line Description:

Collect Support Info fails when executed 2nd time

Problem:

If you collect the support information a second time with less checkboxes checked than the first time, an error will prevent support information being collected.

Temporary Solution:

As a workaround you can close and reopen the dialog or application hosting the support information collection tool.

Fix Information:

Fixed in ICF 3.0.

Keyword: User Interface

One-line Description:

Headspace status shows online after disconnect

Problem:

After the connection to the headspace has been disconnected, the status for this headspace continues to show online. This only an incorrect display behavior of the status window. The connection state of the headspace is actually offline.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 3.1 Update 1

Keyword: User Interface

One-line Description:

HS 7697 The instrument status event feed is inactive/active

Problem:

Network interruptions or HS power-cycle can lead to repeated status event feed inactive/active entries in the log, 

Temporary Solution:

The message itself does not affect the connection and the runs, but the root cause of the message (network interruption or power-cycle) should be avoided. The message disappears after rebooting the AIC/LACE. 

Fix Information:

Fixed in HS driver 3.3

Keyword: User Interface

One-line Description:

HS runs without signal source are aborted

Problem:

Full sequences using a method without a signal source and a HS injector are aborted. 

Temporary Solution:

Select at least one signal in the method to be saved (for example, Diagnostic: Test Plot) 

Fix Information:

Fixed in GC driver 3.8 (ICF 3.3)

Keyword: User Interface

One-line Description:

GC-ALS/HS: Dual injection using barcode reading for only one injection fails

Problem:

When using barcodes in dual injection mode on GC-ALS/HS, where only one injection uses barcode reading, match/mismatch actions do not behave as expected and runs can be aborted.

Temporary Solution:

For dual injection only use barcode reading for both injections or do not use the barcode function.

Fix Information:

n/a

Keyword: User Interface

One-line Description:

GC-ALS/HS: Using different barcode mismatch actions in full sequence mode is not supported

Problem:

When using different mismatch actions for several runs in a full sequence with GC-ALS/HS, only the mismatch action of the last sequence line is applied to all runs. 

Temporary Solution:

Use the same mismatch option for all runs in a full sequence. 

Fix Information:

Fixed in GC driver 3.9 (ICF 3.3)

Keyword: User Interface

One-line Description:

Status Dashboard crashes in localized versions of ICF

Problem:

When ICF is run on a Chinese, Japanese or Portuguese system, the Status Dashboard causes an exception and crashes on initialization. The Dashboard will remain empty and not show anything.

Temporary Solution:

Run ICF 3.2 in English version only

Fix Information:

Fixed in ICF 3.2 Update 1

Keyword: User Interface

One-line Description:

ELSD 1.8 instrument method not applied

Problem:

If GetPropertyDescriptions() is used which calls the ELSD driver function GetResourceDescriptions(string category) it will result in the ELSD instrument method not being applied on the hardware. The setpoints currently residing on the instrument will be used for analysis regardless of the instrument method specified in the sequence.

Temporary Solution:

n/a

Fix Information:

Fixed in ICF 3.2 Update 2