Software Status Bulletin

OpenLAB CDS EZChrom Edition     M82xxAA

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: 35900 Control

KPR#:213248 Update to A.04.09 can break 35900E driver installation with CTC
KPR#:307590 Preview run not working in A.04.09 & new RC.Net Driver functions differ
KPR#:381770 Install manual(M8201-90038) references installing Classic Drivers for 35900 and is not correct
KPR#:2121 35900E ADC-instrument cannot be configured with RC.Net driver after reinstalling the OpenLAB CDS application

Keyword: 3rd Party Drivers

KPR#:138882 The running sequence can not be updated
KPR#:389878 Hitachi LCE and CM: Cannot Use Submit Button in Run Queue to Submit Runs
KPR#:394168 Hitachi LCE and CM: Cannot Use Submit Button in Run Queue to Submit Runs

Keyword: 68xx Driver

KPR#:16 Vial Missing Error Message
KPR#:17 How to Change Column Dimensions
KPR#:18 If One Signal Needs to be Saved, it Must be Assigned as Signal 1
KPR#:22 In 68XX driver revision 5.02 - 6.11, it is not possible to Modify a Method During a Run to Extend the Run Time or Change the Oven Temp
KPR#:23 Info in Edit instrument parameters\Columns is incomplete
KPR#:31 Ignore missing vial option is not present in GC
KPR#:33 Instrument Setup graph has incorrect column legend
KPR#:38 ALS errors abort sequence; no Retry/Abort dialog box option offered with 68xx RC.NET Driver
KPR#:59 In 68XX Driver Version 5.02, it is not Possible to Start the 6890 RC.NET from the Front Panel Start Key
KPR#:66 CIS4 inlet is not recognized with 6890 GC RC.NET
KPR#:83 Only Fast Plunger Speed is available for PTV Solvent Vent multiple injections
KPR#:89 Incorrect injection volume shown in method report if PTV solvent vent is used
KPR#:94 68xx Method Download Times Out
KPR#:95 "Method modified after loading" occurs when running a sequence (6890 RC.NET)
KPR#:99 Sequence continues while GC temperature is not ready
KPR#:100 A Method Can be Created Which Will Not Download to the Instrument and the Sequence Does Not Run
KPR#:101 GC Back Injector Not Present in Edit Method Screen
KPR#:102 Validation failed shown on left corner of Resolve Method screen
KPR#:103 Injector Panels in GC Edit Method Show as Uninstalled When an Injector is Installed.
KPR#:105 Plunger Speed is Not Saved with 6850 GC Methods
KPR#:106 Opening the GC method parameters to only look (no change made) and selecting OK to close stops the sequence or single run
KPR#:109 Method Contents Report Displays the Incorrect Configuration of Front and Back Detectors for 6890 GC
KPR#:113 Cannot Run a Packed GC Column with a 6890
KPR#:116 Pulsed Split/Splitless Injection Does Not Wait For Ready on a 6890.
KPR#:117 In 68XX GC Driver Version 6.01, 2 Injections are Made When Using the PTV
KPR#:119 Vial left in gripper; no message shown to alert user about the problem
KPR#:120 6850 vial numbers are not consistent with standard numbering system.
KPR#:122 Method Resolution Changes Oven Temperature Program
KPR#:123 Column info is missing with 6890
KPR#:124 Method Modification Flag is Set after Edit Method: Occurs on first connection or after upload from GC.
KPR#:128 Method Ddownload Failure Occurs Due to Column Calibration Limits
KPR#:129 Instrument actual value for COC inlet does not display correctly
KPR#:130 Instrument actual value for anode purge flow on an ECD does not display correctly
KPR#:132 6850 Support of Column Compensation
KPR#:136 Data Files do not Contain the Correct Signals if the Front Inlet is Connected to Back Detector
KPR#:140 The Oven Ramp table does not display correctly in IR with Acquisition method selected.
KPR#:141 6890 PTV Inlet not recognizable in OpenLAB EZChrom
KPR#:142 Multiple errors when the 6890 doesn't have any inlets
KPR#:143 Sequence table Inj Vol Override goes to wrong stops for 6890/7683: C.01.05, A.04.05, C.01.06, A.04.06
KPR#:145 Often get two or more ChemMain.exe's running following shutdown of Control Panel or online session.
KPR#:147 6890N with 7693 barcode scanning checksum mismatch does not return vial to tray and skips a vial.
KPR#:148 Customer can't install colum information from catalog if column description is blank
KPR#:149 EZChrom: Installation of GC Drivers A.03.02 breaks a 7697 configuration if installed
KPR#:150 Setting a Hold time of 0.0 does not work correctly with GC6890
KPR#:154 Elite: G1888 status only shows connecting after GC driver installation
KPR#:155 Instrument session continues to run in background after session is closed.
KPR#:159 6890 online help has the bad strings in Injector page.

Keyword: 7890A Control

KPR#:272474 Instrument Type does not include 8860 and 8890 GC

Keyword: 7890A Control,Acquisition

KPR#:183609 Dual channel issue online plot

Keyword: 78xx Driver

KPR#:268 Behavior of the Maintenance Screen When Adding Modules to the GC
KPR#:269 ALS Behavior When Aborting a Sequence
KPR#:270 7890B GC Column Maintenance Counter Behavior
KPR#:271 Update GC Column Catalog dialog is limited to 10 items; no way to display the rest (...)
KPR#:272 Method Differences Viewer Behavior with Scanned Columns
KPR#:273 7890B GC Method Compatibility
KPR#:274 Logbook Messages for Scanned Consumables Items
KPR#:275 The Syringe and Liner are Not Shown in the Method
KPR#:276 The PC and GC Clocks Need to be Synchronized to Account for Daylight Savings Time
KPR#:277 Logging of Injection Tower Location
KPR#:279 Explanation for How Default Early Maintenance Feedback Counters Work
KPR#:281 The 7890 GC Goes Offline When Non-English Characters are Entered into the Column Information
KPR#:282 Instrument Actuals Show "GC is Offline" Quickly at the Method or Sequence Start, then Returns Back Online and the Method Does Not Run
KPR#:283 78xx GC configuration fails; Failed to Create Instance
KPR#:284 Data not collected, sequence stopped when vial removed from turret after injection
KPR#:285 C.01.06: Import eMethod or Export eMethod freezes system
KPR#:287 0-volume blank run in overlapped sequence causes injection
KPR#:294 Standard and Easy Sample Prep programs run incorrectly in a calibration sequence (run for unknown samples only) when overlap is involved.
KPR#:295 7890B configuration, model number serial number and IP address change after restart
KPR#:296 Makeup Gas mode terminology should be consistent with the GC front panel
KPR#:297 Agilent Solvent Elimination Wizard issue
KPR#:298 H2 Sensor button crashes EZChrom
KPR#:299 Clicking OK after making changes to Events does not save the changes made to the events.
KPR#:301 Can't select uECD makeup mode to "Does not affect Makeup Flow"
KPR#:302 Can't save "Included in Makeup Flow" on uECD setting screen.
KPR#:304 The IQT is failing for GC Drivers version A.02.03.074(5.03) for Chinese and Japanese and passing for English in EZChrom A.04.05 with update 5 is installed.
KPR#:305 7820 GC: Method modification flag set after starting a sequence or method
KPR#:306 EZChrom: Method returns to the "untitled.met" after running single or sequence.
KPR#:307 EZChrom: Method Parameters incorrect after loading a new method. OpenLAB CDS EZChrom
KPR#:308 Method printout missing column parameters: flow or pressure, setpoint On, (Initial), and post run
KPR#:309 There is an incorrect character when displaying temperature information in the method report in Japanese
KPR#:310 MMI Cryo Fast Cooldown not saved
KPR#:311 Method is always seen as modified, nothing can be added to the queue.
KPR#:312 Oven Slow fan will be off after method is downloaded the slow oven mode on to 7890
KPR#:313 During a pulsed splitless run, the purge time shorter than the pulse time cannot be entered.
KPR#:314 Method print out with 7890 configured does not show total GCc run time.
KPR#:315 There is no "Inlet Septum Purge" event in Runtime Events table - EZChrom
KPR#:316 External Device "Not Ready" ignored by OpenLAB CDS ChemSataion and EZChrom
KPR#:318 Aux Flow Limited to 150 mL/min even when pressure is less than Maximum
KPR#:319 Post Run Flow Rate has default that out of range and value seems not to be stored
KPR#:320 Method User Interface does not correctly load the content of a method.
KPR#:324 Does not delete previous open GC method event table when load method. Wrong injections can be created.
KPR#:325 Method download to GC while in sequence causes it to disconnect and sequence stops.
KPR#:326 7890 method print doesn't include post run time
KPR#:335 Crash of Software after check "Show Threshold Value as remaining time" in EMF Options
KPR#:339 Not allowed to set proper GC column max temp because it is less than 150degrees.
KPR#:340 FID signal subtraction setting changes spontaneously from "Nothing" to "Column Compensation" during run.
KPR#:341 "Extend Run" in GC settings does not work correctly
KPR#:342 Cannot configure a 7890B on an existing client server system
KPR#:343 Copy to Clipboard Function in Instrument Actuals throws exception error
KPR#:344 The column flow calculator calculation is off by almost 3x the flow rate for the system
KPR#:345 Sample Overlap settings can not be edited after driver update, but are still part of the method.
KPR#:346 Error Unhandled Exception when changing columns and a Gerstel CIS4 in installed in the 7890.
KPR#:347 Incomplete Method Parameters for xCD in Acquisition Method Report
KPR#:349 Actual flows displayed by CDS aren't the same as the setpoint flows
KPR#:350 Print method does not include all MMI setpoints: Purge time, Post Run Temp, Time, Flow
KPR#:351 Extend run does not extend the acquisition of the Intuvo 9000 GC
KPR#:352 Cannot Add User-Defined EMFs on Intuvo 9000 GC
KPR#:353 EZChrom: Some settings not accepted after method migration
KPR#:355 ChemStation Instrument actuals showing D2 Bus Temperature with no D2 bus installed
KPR#:356 Method print is showing Solvent wash mode as A-A2, B-B2 when it should be A,B since it is a 16 vial turret
KPR#:357 Inlet pressure setpoint displayed assuming all thermal zones are turned ON, results in confusing mismatch when heated zones are Off.
KPR#:359 IQT report failed on EZChrom Elite 3.3.2 SP2 with GC Driver B.01.01.
KPR#:360 Method Editor for PP inlet & Packed Column incorrectly allows both flow and pressure setpoints to be entered
KPR#:361 ChemStation can lock up when changing Intuvo Bus Flow Chip types with ChemStation session running.
KPR#:364 Selection box remains after selection made on Events page
KPR#:365 Gray bars hide setpoints after context menu download of method
KPR#:366 Multiple clicks necessary for combo box to list choices.
KPR#:367 Right Clicking on Method Editor makes UI hide behind Instrument Screen
KPR#:368 Incorrect Values in 9000 Pressure/Flow Calculator
KPR#:369 Make changes to guard chip on Intuvo 9000 GC, audit trail just says temperature changed
KPR#:370 Backflush Wizard illogically sets trial backflush times after the elution time of last peak of interest
KPR#:371 Should not be able to download a method while a in a GC run or sequence.
KPR#:375 No indication that the AutoSampler tray is in park mode.
KPR#:376 The Local User Interface(LUI) on the Intuvo 9000 GC shows long name for connected data system.
KPR#:377 For both the 7890 and Intuvo 9000 there is no change in the UI to show the user that a rack is not present.
KPR#:378 Post Run Backflush. The Guard Chip temperature was not set to the Post Run Oven Temperature.
KPR#:379 Location of Intuvo 9000 GC System Health Report should be moved
KPR#:380 Link to Intuvo 9000 GC help does not work.
KPR#:381 Event drop downs are black when creating a new method
KPR#:383 PCM will not control in constant flow.
KPR#:388 RTL for OpenLAB CDS 2.X does not calculate the pressure correctly when locking or re-locking the method when setting a Target retention time.
KPR#:422 HS Sleep/Wake mode should sync with GC Sleep/Wake mode
KPR#:431 Overlap injections on the 9000 uses only the injection volume from the first injection for subsequent injection.
KPR#:439 Downloading method parameters (like oven temperature) on a 6890A does not work with OpenLab CDS 2.4
KPR#:472 Chromeleon: Intuvo trigger two instrument notification for configuration changed
KPR#:473 Chromeleon: GC: Change of column length (and related parameters like flow etc) via calibration in online method sometimes reported in audit trail sometimes not
KPR#:474 Chromeleon: GC: Column length can only be calibrated once in Online Method Editor
KPR#:475 Chromeleon: Setting Liner on Intuvo triggers two config change messages in audit trail
KPR#:476 8860 Open Lab CDS EZChrom compact license is invalid.
KPR#:477 Selecting Partial Data for the 6890 causes the retention times and areas to be wrong.
KPR#:478 6890 - cannot set post run flow for packed column
KPR#:479 Chromeleon: GC 6850A and 6890A: GC online method is not editable
KPR#:480 Chromeleon: GC 6890A: Wrong temperature shown in chromatogram for signal GC_OvTempe_Act
KPR#:481 Chromeleon: GC 6850A: Cannot create instrument method
KPR#:482 Chromeleon: GC8890: Current Signal Value in 'Blank evaluation' shows incorrect value in Method editor
KPR#:483 Chromeleon: GC8890: Blank evaluation setpoints missing in method report
KPR#:484 Signal Scaling is incorrect for the 6890
KPR#:485 Chromeleon: Intuvo: Help button in window 'Configure Agilent Intuvo 9000 GC' opens 78xx Series GC Help
KPR#:486 Chromeleon: GC8890: Issues during sequence execution
KPR#:487 Chromeleon: Changes made in 68xx Edit Online Method not applied or reported
KPR#:488 Error when loading GC method without Blank Run Analysis setpoint
KPR#:489 Chromeleon: Corrected column length will not save after manual method resolution
KPR#:490 Chromeleon: Signals from previous method persist in new method
KPR#:491 Chromeleon: ECD Help page cannot be accessed
KPR#:492 Chromeleon: All 8860 signals not displayed or available in report
KPR#:493 Chromeleon: Error occurred at several points of operation
KPR#:494 Chromeleon: GC6890: Front Injector parameter change in Online method not applied
KPR#:495 Chromeleon: GC6890A: Method download fails
KPR#:496 8860 on Chromeleon -Unhandled exception in Chromeleon Driver Host (CmDDKHost): AgilentTechnologies.DdkIcfAdapter|Agilent
KPR#:497 Chromeleon does not recognize the tray with Back Injector installed.
KPR#:498 Chromeleon: Automatic de-activation of not supported feature blank evaluation cannot be saved
KPR#:499 Getting multiple Errors in the PC Event Log for AgGC7890 after disconnecting and Reconnecting LAN cable.
KPR#:500 GC6890: Valid vial ranges are not correct for 6890 in some cases
KPR#:501 Chromeleon: GC6890A: Error 'The communication FIFO of the DDK driver is corrupted.' after connecting and disconnecting several times.
KPR#:502 When click the "Apply the Option" in GC Chromatographic Column Directory under Column Configuration, an exception occur on Openlab 2.4
KPR#:503 Upgrade installation from GC B.01.03 to 3.0 SR2 fails to install Ag7697WS.dll (and .pdb)
KPR#:504 Chromeleon: GC6850A: Changing method parameter creates method inconsistent to configuration
KPR#:505 Chromeleon: GC6850: Partial Data option causes issues during sequence execution
KPR#:506 Chromeleon: GC6890: Unexpected audit trail entries during endurance run
KPR#:507 SR1 for the GC3.0 drivers breaks the connection between an 8890 and 7000D transferline temperature reading in MH ACQ 10.
KPR#:508 Not able to download flow setpoints to 6890 VI inlet.
KPR#:509 Chromeleon: Incorrect conversion and missing unit when using pressure setting bar
KPR#:510 68xx: Chromeleon: System with G4513 won't make 1.1 uL injection
KPR#:511 Chromeleon: System crash: system slow and then crashing
KPR#:512 8860 with Headspace/PAL does not consume correct VL license for OpenLAB 2.4
KPR#:513 B,04.03 SP2 will not connect to an 8890 GC.
KPR#:514 Chromeleon: 6890GC Oven temperature disabled in method - Run does not start.
KPR#:515 3.0 SR2 driver fails SVT on OL CS C.01.09.144
KPR#:516 OLCS C.01.09 with Driver 3.0.650 will not launch any instrument.
KPR#:517 Chromeleon: SVT Chameleon 2.1.30 Fails
KPR#:518 Function_build number not display in SVT report in EzChrom and OpenLab CDS 2.4
KPR#:519 8890: the MS transfer line temp displayed is 0 C but its actual temp is 250 C.
KPR#:599 Instrument Status shows HS Comm as 'OFF' when it is not.
KPR#:1196 7890A: Shutdown events are not published to the software GC Status screen

Keyword: 88xx GC

KPR#:345674 8860 GC System: there is no core license available

Keyword: Acquisition

KPR#:138296 On-line signal for Hitachi Chromaster is only displayed during acquisition
KPR#:146968 Certain auxiliary traces of Accela pump are not supported
KPR#:147007 The default "Use Method" setting is not working as expected.
KPR#:147010 Mismatched channel/peak data for Thermo Trace 1310GC
KPR#:147797 LC does not abort sequence after pressure exceeds upper limit
KPR#:200819 Delay observed when comparing the Run Time and Analysis Time of the data.
KPR#:220292 Shimadzy 2010 GC and HS-20 synchronization issue
KPR#:316749 Delay observed when comparing the Run Time and Analysis Time of the data.
KPR#:356008 Hitachi LCE and CM: Cannot Use Submit Button in Run Queue to Submit Runs
KPR#:380636 Bruker GC: Changing the current time of the computer makes the driver go offline sporadically
KPR#:401753 No error message for missing vial
KPR#:536644 Hitachi Chromaster LC: No Injection Happens if "No injection/Instrument blank" Used as the Injection Source
KPR#:695883 Hitachi ChromasterUltra RS: Displayed Runtime Doubles for Detectors Online Plot During a Run
KPR#:949857 Data is not being saved when executing a sequence using the PAL 3 RTC with Tool changes
KPR#:1192808 Shimadzu LC: Manual Injection Starts Without Waiting for Trigger
KPR#:1382228 CTC PAL: Activity Log: “Could not read barcode” message does not identify the vial/tray position

Keyword: Administration

KPR#:36 Windows Domain tab is grayed out in OpenLAB Server Utility
KPR#:39 Cannot stop Shared Serviceshost service on computer after changing the Domain Account password

Keyword: Agilent LC Driver

KPR#:179143 Error in RCNet_RCPluginProvider::SetConfigSettings...-Exception
KPR#:400080 Warning message “The installed OpenLAB software is incomplete” or “Repair is not possible as no complete

Keyword: Audit Trail

KPR#:146969 Timetable changes audit traces on general level only
KPR#:146973 PDA 2998/ UV 2489 : Audit trail messages do not contain unit information when values are reported
KPR#:191802 Error message for e-signing twice can be unclear on Citrix Clients
KPR#:210882 Level changes in Peak Table are not captured in the Method Audit Trail
KPR#:251903 Method audit trail will be lost once loading method in different instruments
KPR#:292456 Units for carrier A timetable
KPR#:297766 Method Audit Trail Incorrectly References Detector A Gas 2 as Gas 3
KPR#:589099 Hitachi Chromaster Ultra: No System Activity Log Entries Upon Vial Settings Change

Keyword: Automation

KPR#:256374 “Unable to Create UILess IR control” error message in Instrument activity after launching instrument from Automation tool.

Keyword: Autosampler

KPR#:338 EZChrom: PAL XT module not available after installation

Keyword: CDS

KPR#:146999 EZChrom Edition only: Increased memory consumption after a sequence.
KPR#:516793 PE LC300: Incorrect Status of Non-Detector Modules While Running Shutdown Method
KPR#:517638 Bruker GC456: Stepwise Online Signal
KPR#:548087 Hitachi Chromaster and LaChrom Elite LC: Differences in DAD channel naming in Data Analysis
KPR#:554454 CTC PAL3 for LC Cannot be Launched with OpenLab CDS 2.6
KPR#:1378523 Shimadzu LC: A Task with Shutdown Functions Not Executed

Keyword: Client Report Rendering

KPR#:46 Intelligent report of English openlab chemstation can not show chinese name in PDF report
KPR#:628 Large matrix reports may produce additional empty pages
KPR#:653 Calculating the standard deviation of identical numbers may return NaN
KPR#:657 Changes in report templates are not immediately shown on report printouts
KPR#:659 Rendering error when using a template containing a large result matrix

Keyword: Configuration

KPR#:22100 Auto-configuration for instruments is not supported
KPR#:146924 Starting Acquity instrument for first time after an AIC reboot has errors
KPR#:146964 Some Autosampler parameters are not uploaded e.g. loop size.
KPR#:146966 Manual tray type configuration required
KPR#:146970 Auto-configuration for instruments is not supported
KPR#:146988 It is not possible to configure a Shimadzu SPD-M20A detector in the same system configuration as a Shimadzu Nexera integrated system.
KPR#:147000 200uL Sample loop not configurable in Alliance instrument configuration
KPR#:147014 For the GC column properties, there are missing units for column length and internal diameter.
KPR#:285964 Hitachi LaChrom Elite auto configuration fails on EZChrom with Win 10
KPR#:288817 Instrument status shows temperature value for non-configured injector
KPR#:397013 Two different pressure units displayed in data analysis
KPR#:456679 Hitachi LCE and Chromaster LC: Comma as a Digital Separator Limitations
KPR#:486957 PE AutoSystem XL GC: cannot add VICI valves
KPR#:551474 PE TurboMatrix HS with Agilent GC Cannot be Configured More Than Once
KPR#:715153 PE Flexar LC: Configuration of Flexar Column Oven with Peltier Fails
KPR#:1216158 CTC PAL: Imported/removed scripts are not reflected in Method editor unless acquisition is relaunched

Keyword: Configuration,Instrument Control

KPR#:732721 PE TurboMatrix HS: High Pressure Injection Not Usable Without Vial Pressure Sensor
KPR#:800415 PE TurboMatrix HS: High Pressure Injection Not Usable Without Vial Pressure Sensor

Keyword: Control Panel

KPR#:117721 Exception when login in OpenLab Control Panel. ECM does not display all the subfolders when browsing for Project Path during project creation; exception displayed

Keyword: Custom Reports

KPR#:1995 FIltering syntax has changed

Keyword: DAD/MWD Driver

KPR#:149830 High load on CAN may cause "Spectra runbuffer overflow" entries and a loss of spectra
KPR#:149837 Autobalace executed although in Sequence table set to "OFF"
KPR#:149898 Lowest possible DAD wavelength is 190.5 nm

Keyword: Data Analysis

KPR#:139618 Incorrect value entered at peak group table if GC method parameter window is open using Agilent GC driver B.01.02
KPR#:153192 Chromatogram Annotation for Purity does not reflect actual value less than 1
KPR#:379394 Sequence audit trail create time differs from report

Keyword: Data Analysis,Installation

KPR#:408720 Analyses turns into error state "HRESULT: 0x80010105 (RPC_E_SERVERFAULT)"

Keyword: Data Store Integration

KPR#:191223 The Users and Groups report generated on a A.02.02 client from a 2.0 Datastore Server is incorrect

Keyword: Data Store Integration,ECM Integration

KPR#:339790 Mismatch between result set modification time and result set creation time on CM and ECM3.5 backend

Keyword: Documentation

KPR#:31 The module type of the Alliance instrument is reported as a 'Detector' in OpenLAB CDS ChemStation Edition reports
KPR#:146997 Instrument Configuration report can not be printed when offline.
KPR#:147024 The firmware version required by the driver is incorrectly stated as v1.41.6164 for the Waters Alliance 2489 detector in the User Guide
KPR#:177259 No help for reason type in Method Audit Trail
KPR#:260862 PE Clarus GC: Some Method parameters are missing in the method report
KPR#:391787 Hitachi's Sub CPU Firmware can Only be Visible from Hitachi Maintenance Tool
KPR#:601921 Hitachi Chromaster Ultra Rs: Document for the Hitachi Maintenance Software is not the latest
KPR#:634039 Shimadzu LC: No Information about Wavelength for UV Detector in Chromatogram in DA
KPR#:651995 PE Clarus GC 500: Min Firmware for Mainboard Missing in Training
KPR#:701847 Hitachi Chromaster Ultra LC: Inconsistent driver version 3.20 reported in Software Verification Tool

Keyword: ECM Integration

KPR#:251997 ECM LCDF name ending with a period "." prevents resultset download
KPR#:277494 Report Template Long File Name Not Uploaded and Causes InstClient crash
KPR#:278036 Long File Name Prevents Single Level Calibration

Keyword: External Component

KPR#:350455 Hitachi Chromaster can't Initialize after AIC reboot with "IFC cannot be found" error
KPR#:658322 Hitachi LC: Incorrect Display of Parameters in Maintenance Tool with Win 11
KPR#:708791 Hitachi LC: USB Drivers incompatible with OS Memory Integrity Option
KPR#:762177 Hitachi LC: USB Drivers incompatible with OS Memory Integrity Option
KPR#:788048 Shimadzu LC: Current Value of Wavelength Accuracy 656nm (NAR) Not Displayed in Shimadzu LC System Check Report
KPR#:1036196 Shimadzu LC: SPD-M20A Excluded from the System Check Report if Upgraded to SPD-M40
KPR#:1077556 Hitachi LC: Incorrect Display of Parameters in Maintenance Tool with Win 11
KPR#:1092976 CTC PAL 3 for LC: Importing Pre-installed LC Injection Script Leads to Exception

Keyword: Headspace

KPR#:180 EZChrom: Original method not restored when sequence run from EZChrom

Keyword: Help

KPR#:22140 Error with detectors help
KPR#:90310 Incorrect units for autosampler method setup shown in Help
KPR#:592464 Hitachi Chromaster Ultra: Help Clarification for the Purge Options of the Pump
KPR#:592467 Hitachi Chromaster Ultra: Help Clarification to Rack Settings of Autosampler
KPR#:595483 Hitachi LaChrom Elite: Incorrect Error Message for Analog Input Device Issue

Keyword: Installation

KPR#:22 FTP protocol is enabled by default on OpenLAB Data Store A.01.02 systems
KPR#:38 Project activity logs not displayed after upgrading to A.02.01
KPR#:42 OpenLAB Control Panel does not open after upgrading Windows Server 2008 R2 to Windows Server 2012 R2
KPR#:94355 Installer & Uninstaller wizards still show incorrect references to the driver name as an "Addon" in the installer screens
KPR#:130809 If a privilege is removed from the default roles in OLSS the application registration fails at installation
KPR#:175952 SVT report does not work when installing the driver in non-default location
KPR#:175999 SVT Report Does Not Check 34 Files for Thermo Fisher Trace GC Driver
KPR#:203907 Not all SVT reports get displayed on the screen when manually run SVT on Server
KPR#:222652 Missing file in the reference file in the MSI Package for Shimadzu LC in EZChrom Edition
KPR#:281960 SVT report has 41 files not found in reference
KPR#:290491 No warning when installing later PE GC driver version with the preinstalled older version might lead to malfunction
KPR#:297111 SVT for OpenLab CDS disappears upon uninstalation of PE Clarus GC Drivers
KPR#:298681 There is no Warning When Another Version of PE Driver is Installed Over The Previous One
KPR#:303159 SVT report does not show the installed driver for non-default path CDS installation
KPR#:605033 Mixed Mode OpenLab EZChrom A.04.10 and CDS 2.5 Warning
KPR#:606448 Error During Driver Installation
KPR#:2121 35900E ADC-instrument cannot be configured with RC.Net driver after reinstalling the OpenLAB CDS application

Keyword: Installation , 35900 Control

KPR#:2121 35900E ADC-instrument cannot be configured with RC.Net driver after reinstalling the OpenLAB CDS application

Keyword: Instrument Control

KPR#:32 OpenLAB CDS ChemStation Edition sequence shutdown macro PUMP ALL OFF is not executed.
KPR#:146967 Thermo Accela pump communication LED remains active
KPR#:146992 During acquistion of aWaters Alliance HPLC connected to OpenLab CDS EZChrom Edition, the software allows access/change instrument parameters even if roles/privileges for manual control are disabled.
KPR#:146993 Unexpected change of Alliance pump flow rate and solvent composition after a run observed on a French operating system
KPR#:147009 Shimadzu HPLC shows "Ready" even if Pump or Lamp is set to Off
KPR#:211507 Inlet time program does not work properly
KPR#:212506 Only one valve functions
KPR#:212515 GSV and Split valves cannot be controlled from the events table
KPR#:286720 Status of Oven and Autosampler is "Ready" when the GC is switched off
KPR#:288479 PE Clarus GC: at the end of a run ""The current method has changed" message
KPR#:394374 Shimadzu 2010 Plus GC: instrument connection not closing gracefully
KPR#:401780 "Switch Valve to Load" not available after "Switch Valve to Inject"; "Home arm" action needed first
KPR#:492287 Hitachi LC: Long Launching Time if Instrument Setup Window Left Open Prior To Exiting Instrument Window
KPR#:516796 PE LC300: Uploading Method to the Instrument with Turned off Pump Switches Pump On
KPR#:536651 Hitachi LaChrom Elite: Intermittent Waiting For Trigger Does Not Start the Run
KPR#:543340 VICI Valves: Acquisition Crash on Pressing Change Button in VICI Dashboard
KPR#:645291 Bruker 456 GC: FID Flame status inconsistent
KPR#:723437 PE Clarus 480 GC Cannot Be Connected to the AIC Due to Communication Error
KPR#:939675 PerkinElmer Flexar LC: Communication to Instrument Lost During Long Sequence
KPR#:947158 VICI +Agilent 7890: Changing Position of VICI Valve during a Sequence Can Cause Its Abortion
KPR#:962546 Shimadzu PDA Cannot Be Configured with Agilent LC
KPR#:1129855 Hitachi Chromaster: Script Error Appears Under Certain Conditions
KPR#:1185772 Shimadzu LC: Manual Injection Starts Without Waiting for Trigger

Keyword: Integration

KPR#:138745 Application crash if back data files resultset is reprocessed with the clear calibration flag
KPR#:263508 Reprocess or analyze of data file causes instclient.exe crash

Keyword: Localization

KPR#:287503 PE Clarus GC: Decimal symbol for syringe volume
KPR#:738391 Hitachi CM and LCE: Acquisition Window Crashes if Non-English OS Used for AIC/Client

Keyword: Method

KPR#:146963 Pretreatment methods are saving invalid parameter
KPR#:146971 Method upload functionality is not supported for both OpenLAB CDS Chemstation and EZChrom Editions
KPR#:146977 Run Time Mismatch after running a Gradient Method
KPR#:146995 The 450GC oven does not cool down as expected when the run finishes.
KPR#:146996 Not Ready in Run status/warning appears during run of 450GC and stops run
KPR#:147008 Missing instrument configuration information in the method reports.
KPR#:147013 Instrument Configuration information is not contained within method report.
KPR#:147017 Instrument Configuration information is not contained within method report.
KPR#:279725 Shimadzu LC Vial message: "Object reference not set to an instance of an object"
KPR#:288808 Split flow in instrument status is always X mL/min higher than in instrument setup
KPR#:290303 Instrument Setup Window: Time constant for FIDW is displayed without a unit
KPR#:297200 Incorrect Units (°C) for carrier gas settings in Method report
KPR#:354452 Shimadzu LC 2030C+: invalid range(0.1-50.0) error for syringe >50 uL
KPR#:370796 Method resolution is possible without privilege "Instrument Setup"
KPR#:530381 PE TurboMatrix HS: New Method Throws an Error Message Upon Saving
KPR#:542480 PE AutoSystem XL: Method Downloading to the Instrument Not Logged in the Activity Log
KPR#:695899 Hitachi Chromaster Ultra LC: Direct Control "Turn on at" Functions Properly Only at UTC Time Zone Entry
KPR#:751372 Hitachi CMU: Method Resolution Error When Upgrading from CMU1.0 to CMU1.1
KPR#:761728 PE TurboMatrix and Clarus GC: System Sometimes Prompts to Save Unmodified Method
KPR#:781493 Hitachi Chromaster LC: Actual Run Time Can Be 10x Longer Than Set in the Method Due to Certain System Settings
KPR#:800420 PE TurboMatrix and Clarus GC: System Sometimes Prompts to Save Unmodified Method
KPR#:1063041 PE Clarus GC Default Method Setting Combination for Carrier Not Allowed with EZChrom
KPR#:1155105 Clarus GC: Method UI Might Appear Hanging For Carrier Tab Under Certain Condition

Keyword: Method Usage

KPR#:147025 After data has been acquired on Shimadzu LC-20 systems, a warning "The current method has changed would you like to save it?" is displayed.
KPR#:297768 Incorrect Carrier Info in Method Report
KPR#:414461 Incorrect Absorption Value in the Online signal and Status of 6420 UV-VIS Detector When Non-Default Range Value Used.
KPR#:415474 Hitachi ChromasterUltra Rs: DAD Online Signal Wavelength Needs to be Selected in DAD Direct Control Option
KPR#:691353 Shimadzu GC: Method Resolution Error Does Not Provide Details

Keyword: Output

KPR#:246004 EZChrom GPC/SEC uses a time slice algorithm that gives different results from other GPC software

Keyword: Performance

KPR#:261090 Abort Current Run Sets Instrument in Error State
KPR#:281316 Sporadic internal error "timeout expired" for activity log queries
KPR#:377731 Thermo SII Driver: Corona Veo Not Supported in Agilent LC stack
KPR#:511004 Refresh period of the Online Plot Might Increase for Long Sequences
KPR#:511440 Thermo Fisher SII: Submitting Shutdown Method in Acquisition Leads to Error for Corona Veo Detector
KPR#:614017 Thermo Fisher Ultimate 3000: The Injection Collection Could Not Be Initialized
KPR#:614020 Thermo Fisher SII: "Blank" Type Injections Cause Sequence to Abort
KPR#:658297 Hitachi Chromaster LC: Long Acquisition Launch Time
KPR#:664341 Thermo Fisher Trace GC, Integrion, Aquion: Method Part of the UI Not Accessible Due to Missing Scrollbar
KPR#:667230 Thermo Fisher Aquion Remains Offline After Reset
KPR#:667234 Thermo Fisher Aquion: Error Due to "Non-Specified Flow Rate"
KPR#:667333 Thermo SII Integrion: Setpoint Column Temp Shown Instead of Actual Temp in OpenLab Instrument Status
KPR#:667424 Termo SII: Integrion Method Editing Issues
KPR#:683446 Thermo CAD with Agilent LC: The Sequence Aborts if it Encounters No Injection/Blank Run
KPR#:695395 Shimadzu GC: Online Signal Does Not Work
KPR#:801770 Sequence aborts after updating running sequence
KPR#:804696 PE Clarus 680: Attenuation Time Change Events Do Not Work Properly
KPR#:1029458 Thermo Fisher SII: Take/Release Functionality Leads to an Unhandled Exception
KPR#:1058303 Injector temp Error happened when method switch from high temp. to low
KPR#:1064776 Thermo SII 1.3 with CDS 2.8: Issue about log4net in Station IQ and some Thermo instruments cannot be configured
KPR#:1073349 Sequence stalling and the time in log back to 1601 year
KPR#:1076815 Run can't be aborted due to Auxiliary trace enabled
KPR#:1087709 Unable to configure instrument in ChemStation
KPR#:1378700 Thermo Fisher SII: SQL engine not starting after installation on Win 11 and Win Server 2022 OS

Keyword: Project Configuration

KPR#:227940 "Edit running method" privilege has no effect on user privileges

Keyword: Pump Driver

KPR#:149838 Misrepresentation of Bottlefillings in Dashboad of PumpValveCluster
KPR#:149845 PumpValveCluster with ISET - Solvent composition: resulting %A is wrong (at 1 line in timetable)

Keyword: Report Template Design

KPR#:25 Intelligent Reporting : Last displayed digits might be cut off, in cases where the number is zero
KPR#:40 Missing named peaks are reported in Intelligent Reporting for all the channels or signals
KPR#:42 The Fixed Text field in IR Templates does not accept Chinese characters
KPR#:50 Intelligent Reporting - Spaces are stripped from filters when they are saved
KPR#:56 Error seen in Intelligent Report header (#error) if any related data field is used in an expression
KPR#:58 Intelligent Reporting - Stacked Chromatograms do not display the time axis in reports
KPR#:59 Intelligent Reporting - Square brackets cannot be used in filter expressions
KPR#:60 Cannot calculate summary statistics on columns containing variable or aggregator
KPR#:620 Error message when adding a chromatogram to a report template
KPR#:621 Internal grouping of tables and usage of calculation variables cannot be applied at the same time
KPR#:622 Summary Calculations cannot be applied to table columns containing calculation variables
KPR#:623 Adding a template description to a previously erased and saved description field causes a KeyNotFoundException
KPR#:627 Customized composite groups should have a unique name
KPR#:662 Filter definition does not always allow usage of OR operators
KPR#:668 Reporting time format does not offer an option of (dd/mm/yyyy and time)

Keyword: Report Templates

KPR#:36 Min and Max column summary calculations report GMT and not local time for date fields
KPR#:39 The report date is printed incorrectly in the Agilent supplied intelligent reports
KPR#:43 The template fields "SignalToNoise_EP" and "SignalToNoise6Sigma" do not work in Japanese version
KPR#:47 Center of triangular calibration point labels do not represent the measured value
KPR#:48 XLS export of intelligent reporter templates generate hidden rows
KPR#:658 Customized chromatogram or axis lables may not display correclty
KPR#:138370 Esignature table does not remember the formatting in Standard report
KPR#:138858 Only 50 .srp active template are reflecting under Report -> View option
KPR#:241653 VICI Valves: No Serial Number and no Firmware in IR report
KPR#:288580 Carrier table in method report is incorrect
KPR#:301630 Peaks and Repeating property in IR template does not present Missing Peaks
KPR#:309865 No Module Information is Reported in the Sequence Summary Report

Keyword: Reports

KPR#:138810 Versioning in the Method Report (Classic Reports)
KPR#:138849 System hangs when trying to generate sequence summary reports with Primaide Modules
KPR#:224121 QC Check Rounding limitation
KPR#:372183 SII: Wrong Entry in Instrument Module Report
KPR#:414840 An Additional Warning on Station IQ report for OpenLab CDS 2.5
KPR#:1370829 Thermo SII Instruments: Missing Information in Module List and Reports for Some Modules

Keyword: Reports - IR

KPR#:213496 "Not-found compound" table in IR report not working
KPR#:242758 Difference in compound group area reported on standard and intelligent reports
KPR#:290069 Difference in compound group area reported on standard and intelligent reports
KPR#:291693 Wrong value of Sample Type in IR - A.04.08
KPR#:316761 "Not-found compound" table in IR report not working
KPR#:547223 Zeroes-trimming for injection volumes lower than 1
KPR#:709423 Integration droplines may not be displayed on a report chromatogram when using Intelligent Report templates

Keyword: Roles and Privileges

KPR#:177092 Analyze tab not greyed out for those without the privilege
KPR#:508781 SII: Direct Control Context Menu Disabled During a Run for User with All Permissions
KPR#:508896 SII: Direct Control Context Menu Disabled for User with Manual Control (in Run) Permissions
KPR#:509382 SII: Instrument Control is Still Possible for User Without Manual Control Privileges
KPR#:933834 Thermo SII: Method "Approve" Function Does Not Allow Method Changes Anymore

Keyword: Sampler Driver

KPR#:149831 LC driver starts run with ALS Chiller turned off
KPR#:149841 ICF A.01.04 - No method download, if method contains pretreatment/injector program steps.
KPR#:149880 For overlapped injections in vial samplers G1313A and G1329A/B, injection volumes and sample locations are not updated synchronously in the status UI

Keyword: Sequencing

KPR#:226629 Error message: Unable to open method (2) when the sequence is started
KPR#:236585 Sequence Table Column width, reduced making column invisible cannot be restored
KPR#:266379 Saving Easy Sequence without change results in "Filed to upload..."

Keyword: User Interface

KPR#:22101 The alignment of the instrument module icons on the Instrument status display within OpenLAB CDS Chemstation Edition are not correctly aligned and in some cases, may be partially obscured.
KPR#:22136 Comment field is not available in the Instrument setup dialog for the 2998 PDA
KPR#:138857 In Windows 10 Data Appearance Properties Schemas cannot be saved.
KPR#:146965 Tray image for 'Custom 384 well settings' is not displayed.
KPR#:146976 The alignment of the instrument module icons on the Instrument status display within OpenLAB CDS Chemstation Edition are not correctly aligned and in some cases, may be partially obscured.
KPR#:146978 Waters Alliance: The elapsed run time dislayed on the instrument dashboard is not updated when a UV2489/PDA2998 detector is connected (ChemStation Edition only)
KPR#:146990 Improved handling of spectrum acquistion wavelength paremeters requried in user interface.
KPR#:146998 Comment field is not available in the Instrument setup dialog for the 2998 PDA
KPR#:257130 Context Menu Entries in Instrument Status Appear Active During Run
KPR#:257664 No Online Help for Thermo Fisher Instruments Available in Status Dashboard
KPR#:391501 Column Oven Pictogram Displays the Oven is ON in case of a door opened condition even if it is OFF
KPR#:415443 Entries in Method Audit Trail Are Unclear
KPR#:489974 SII: Configuring The First Instrument for SII Might Display Two Modules, One being Empty
KPR#:502441 Using Non Unique Method for Identical Instruments Prompts to Save Changes Even When No Changes Exist
KPR#:508118 SII: Smart Startup, Smart Shutdown, Smart Standby Not Supported
KPR#:508900 SII: Method Can Still Be Edited But Not Saved Without Create and Edit Acquisition Method Permission
KPR#:664364 Thermo Fisher Trace GC: Method Parameters Out of Range Warnings Not Properly Displayed
KPR#:667210 Thermo Fisher Trace GC: AI/AS 1600 Autosampler Missing Info in Module List
KPR#:667219 Thermo Fisher Aquion: Imperfect Method Parameters Input Validation
KPR#:667312 Thermo Fisher Integrion: Waveforms Cannot Be Edited at First Trial
KPR#:675175 Acquisition delay is reset to 0 after reconnecting
KPR#:682958 Thermo SII: ICS-6000 Acquisition Method Parameter Not Correctly Shown
KPR#:684251 Thermo SII: Not Showing Online Signals Outside a Run
KPR#:703570 Thermo Fisher Trace GC, Integrion, Aquion: Method Part of the UI Not Accessible Due to Missing Scrollbar
KPR#:708978 uGC Channel status disappear from OpenLab CDS Aquisition
KPR#:710021 Don't support Aux trace feature on Openlab CDS
KPR#:735528 Method_Acqusition delay makes all peaks move backward
KPR#:758653 VICI valve can't configure successfully
KPR#:760039 No injection delay in EZ chrom 04.10
KPR#:763799 Hitachi ChromasterUltra RS: Selection in Tray A Display Also Reflects in Tray B of Microplates
KPR#:763901 Hitachi ChromasterUltra RS: Selection Column by Column on Tray Display Not Supported
KPR#:801393 SII Module Status May Show As Not Ready in Idle State
KPR#:948202 SII module cannot be selected during configuration
KPR#:978882 The color of Actuals for Gasifier should be updated after plug the USB cable.
KPR#:1038023 Truncation in Pump Limit Field Makes Input Semi-Invisible
KPR#:1043038 Hitachi Chromaster: Name of 2nd Channel Changes to None Outside Run in Online Signal View
KPR#:1052659 Dashboard shows pump as idle when running out of rear seal wash solvent
KPR#:1074052 Hitachi ChromasterUltra RS: Selection in Tray A Display Also Reflects in Tray B of Microplates
KPR#:1074053 Hitachi ChromasterUltra RS: Tray Display Vial Format Requirements
KPR#:1074165 OpenLab CDS--Method save must be before download.
KPR#:1080182 Temperature of Gasifier is blank when Status is not Ready
KPR#:1082987 Version on "About" page not consistent with actual installed version
KPR#:1084188 Difference driver version between Configuration and Windows Control Panel (On ChemStation C.01.10 Update07)
KPR#:1091615 The updated value for Sampler is not displayed in reopened method.
KPR#:1092105 VICI 2 and VICI 3 related entries display on method audit trail even instrument has only VICI 1
KPR#:1173424 Thermo Fisher SII: Open file dialog moved to back when tooltip is shown
KPR#:1375236 PE Flexar: Incorrect Driver Version in Module List

Keyword: 

One-line Description:

Resultset locked after run started by Sample Scheduler

Problem:

Resultsets that were run from Scheduler were blocked from being reprocessed until another run was started on the same instrument

Temporary Solution:

Schedule a dummy run on the same instrument to release the resultset

Fix Information:

Fixed in Sample Scheduler for OpenLAB CDS EZChrom A.02.02

Keyword: 

One-line Description:

Pump settings not set to initial value after run and/or after loading a Method

Problem:

During run a stop is requested to the Software.
Opening the User Interface where the system is shown the Initial pump parameters were not loaded.
It was still  A: 99.84%  B: 0.16% instead of A:100% and B:0%.
Loading the Default method still the gradient is wrong displayed in UI.

Temporary Solution:

n/a

Fix Information:

there's any fix for this issue.
The simptoms was very seldom and random.
Restarting the PC and the Modules will erase the wrong information displayed on the User Interface.

Keyword: 

One-line Description:

Scheduling Back Tower run on a 6890 or 7890 GC with only a Back Tower installed causes error and hanging EZChrom

Problem:

Scheduling a Back Tower run on a 6890 or 7890 GC with only a Back Tower installed causes error and hanging of EZChrom

Temporary Solution:

As a workaround schedule the Back Tower run as Front Tower run with the correct vial number (e.g. 201)

Fix Information:

A fix is planned for a later version of Sample Scheduler together with a later version of CDS

Keyword: 

One-line Description:

Scheduling a dual Gas Sampling Valve injection on a 7890B

Problem:

Scheduling a dual Gas Sampling Valve injection on a 7890B get stuck in "in progress" state with same vial number for Front and Back.
When scheduling with 2 different valid vial numbers the run gets scheduled a second time and the data from the first run is lost.

Temporary Solution:

Schedule a dual injection from Gas or Liquid Sampling Valves without vial numbers. 
To test the method in OpenLAB EZChrom create a sequence, and select Dual as Tower.

Fix Information:

Fixed with GC driver B.01.01
Scheduling one dual injection from Gas or Liquid Sampling Valves with 2 different vial numbers is injecting dual once.
Scheduling a dual injection from Gas or Liquid Sampling Valves with the same vial number for both the GC is running twice.

Keyword: 

One-line Description:

LIMS Agent can't write to trash if LimsCommandId has the wrong type

Problem:

If in the SQL query, the LimsCommandId gets mapped to a string, the LIMS Agent fails to write to the trash file because of the way it constructs the path.

Temporary Solution:

n/a

Fix Information:

This defect is planned to be fixed in a later revision of Sample Scheduler

Keyword: 

One-line Description:

Detector status not shown in OLCDS driver when detector is set to 'off' or "PeakSimulation"

Problem:

TCD status check in the OpenLab, when TCD is turned off, but it still has a number. 
When TCD is setup as Peak simulation, it shows the "Det off" in Openlab but not "peak sim".

Temporary Solution:

n/a

Fix Information:

It has fixed in 1.11.2.

Keyword: 

One-line Description:

OpenLabCS C.01.07 Print method does not include any 490 parameters

Problem:

OLCS C.01.07.107 on CBC-Win81 with 490 Driver 1.11.2.1048. Print method. The method parameters of the 490 are not printed in the file.

Temporary Solution:

n/a

Fix Information:

Fixed in 1.11.2.1109.

Keyword: 

One-line Description:

Uninstall of the Sample Scheduler with the installer msi is sometimes not successful

Problem:

The uninstallation of the Sample Scheduler with the installer msi is sometimes not successful.

Temporary Solution:

Do the uninstallation of the Sample Scheduler in Windows Programs and Features.

Fix Information:

A fix is planned for later releases.

Keyword: 

One-line Description:

490 on C.01.07 has invalid injection source: only Manual

Problem:

OLCS C.01.07.107 on CBC-Win81 with 490 Driver 1.11.2.1048. With Autosampler set to None in instrument config, the only option to start a run is Manual, which holds it limbo forever waiting. Can't abort.

Temporary Solution:

n/a

Fix Information:

Fixed in 1.11.2.1171

Keyword: 

One-line Description:

Invert signal function disable when upload method from Micro GC

Problem:

Edit a methods and enable invert signal, now download methods to micro gc 490, then using another PC with OpenLab to control micro gc 490 and upload method, the invert signal is disabled.

Temporary Solution:

n/a

Fix Information:

Fixed in 1.12.2

Keyword: 

One-line Description:

Sequence hang up after first run is finished

Problem:

The sequence process hang up after the first run is finished, GC is ready but the next run won't start at all.
The problem is found in both Openlab EZChrom and Chemstation software.

Temporary Solution:

n/a

Fix Information:

Fix in B 01.12.2

Keyword: 

One-line Description:

No Sampling time checkbox in OpenLab Chemstation/EZChrom when using continuous flow

Problem:

Configure sample mode to Continuous flow, the sample time is disabled, it's not comparable with PROStation.
Add the sampling time checkbox in OpenLab Chemstation / EZChrom software.

Temporary Solution:

n/a

Fix Information:

Add the sampling time checkbox in 1.12.2

Keyword: 

One-line Description:

Invert signal function is not working properly

Problem:

Check the invert signal check box, save method and then download to 490 Micro GC. Start a run, it is unable to invert the signal of the TCD.

Temporary Solution:

n/a

Fix Information:

Fix in 1.12.2

Keyword: 

One-line Description:

PAL3 method fails at runtime when an inject amount is out of range for the installed syringe

Problem:

If you have a 10 ul syringe installed and specify a 10 ul injection volume, the system will not indicate any problem until runtime. This is because the driver cannot look into the script to determine total volume (ie sample volume and air gap). This calculation is done at run and the error shows then.

Temporary Solution:

Use has to calculate total volume required when setting up the method.

Fix Information:

n/a

Keyword: 

One-line Description:

Check Remote access with UserDataStore in control panel, pops up "Unable to active UserDataStore, MFC71.dll is missing "

Problem:

Check Remote access with UserDataStore in control panel, pops up "Unable to active UserDataStore, MFC71.dll is missing "

Temporary Solution:

n/a

Fix Information:

Fix in 1.12.2

Keyword: 

One-line Description:

Online signal freeze after network reconnection at Openlab platform

Problem:

Cable disconnect during the running, online signal stopped.  After reconnecting the cable, communication came back normally, but the online signal still freezed.

Also checked the same issue on Openlab Chemstation.

Temporary Solution:

n/a

Fix Information:

Fix in 1.12.2

Keyword: 

One-line Description:

Legacy mainboard can't drive the new VICI valve (EUTA)

Problem:

Legacy mainboard with Firmware less than 2.44 can't support the new VICI valve (EUTA)

Temporary Solution:

Upgrade the driver

Fix Information:

n/a

Keyword: 

One-line Description:

Failed to configure 990 in Chemstation C.01.10

Problem:

OpenLab Chemstation C.01.10.239
Mirco GC Driver 2.2.2
Try to configure 990, in pops up window, enter correct IP, clcik "OK" button, back to instrument configuration, at the bottom, there is warning message "unconfigured moduel here" (actually configured already).

Temporary Solution:

NA

Fix Information:

Fixed in Driver 2.2.5

Keyword: 

One-line Description:

Driver 2.2.1 running at 990 FW 1.03.71: Failed to send the configuration to the GC

Problem:

Communication established successfully with 990, if any configuration (disable channel, flush cycles, pressure unit...) changed and applied, a warning message pops up: communication lost with XX: failed to send the configuration to GC.
Driver 2.2.1
FW 1.03.71
Openlab 2.5

Temporary Solution:

NA

Fix Information:

Fixed in 2.2.5

Keyword: 

One-line Description:

TCD stays OFF even method download

Problem:

TCD stays OFF even method download, but web page indicates the TCD has been calibrated well.

Temporary Solution:

n/a

Fix Information:

Fixed in 1.12.3

Keyword: 

One-line Description:

Gasifier can't be found in 990 configuration

Problem:

Configure Gasifier from 990 Micro GC, Openlab CDS is 2..6, driver is 2.2.7.0, but Gasifier can't be found in configuration.

Temporary Solution:

n/a

Fix Information:

Fixed in 2.2.11

Keyword: 

One-line Description:

990 Micro GC can not configure VICI valve

Problem:

Try to configure VICI valve, and click "Check VICI communication", warning message pops up "Gasifier configured, do not allow to configure VICI valve" see below screenshot. Actually, no gasifier connected.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

GC goes offline when starting a run while the VICI valve physically disconnect

Problem:

Configure VICI valve but not physically connect to a valve, the Instrument Status goes offline when starting a single run or sequence.

Temporary Solution:

n/a

Fix Information:

Fixed in 2.3.6

Keyword: 

One-line Description:

Easy Sequence Setup not refreshing the Injection Location

Problem:

7890/7693: Create methods for front, back, and dual ALS injection sources.
Easy Seqeunce Setup does not refresh to show the correct injection location of the loaded method until user loads the corresponding method in ChemStation.

Even loading a different method, the previous injection source is kept.

Temporary Solution:

If the injection source has been changed, use the "Clear All" button and reload the method.

Fix Information:

n/a

Keyword: 

One-line Description:

VICI failed the first activation with uGC, need 2nd time to activate

Problem:

Driver 1.12.3.008
Using the VICI valve EUTA model, open configuration to activate the VICI, it failed at first time. need to re-activate the VICI.
It will result in the broken communication between VICI and uGC after system rebooting, SW will crash

Temporary Solution:

n/a

Fix Information:

Fixed in Driver 2.4.8

Keyword: 

One-line Description:

No error checking for vial ranges in Easy Sequence Setup; fails at runtime

Problem:

There is no error checking within Easy Sequence Setup to determine if the vial range of the loaded method's injection source is accurate.

The method can be saved and submitted to the queue.  It fails at this time with:

'---------------------------
Error
---------------------------
Invalid location found in FRONT sequence, line 1
There may be others
---------------------------
OK   
---------------------------'

This defect occurs because there is a difference between the loaded method's injection source and the method that is selected in the Easy Sequence Template.

Temporary Solution:

Load the method in ChemStation from Method > Load Method menu that will be used to create the Easy Sequence Setup Template.

Fix Information:

n/a

Keyword: 

One-line Description:

Pause/Resume button is in the wrong state after a sequence is edited and then pauses

Problem:

Send a sequence to the Queue and while it is running, edit it. This modified/changed sequence pauses the Queue, but the first blue button is still in a 'Pause||' state. Click the button and change it to Resume, but it does not do anything as it is waiting for the current sequence to be saved before starting the next sequence.

In this case, because the sequence has been modified, the ChemStation is not accepting sequences. If you click pause || button, you pause the queue and it does not do any thing. The message on the active queue is red and the message says the sequence has been modified.

Temporary Solution:

Save the sequence that has been modified.  Once the sequence has been saved, the queue will resume running the next sequence.

Fix Information:

n/a

Keyword: 

One-line Description:

7890A with no ALS shows Read Barcode button in Easy Sequence Sample List

Problem:

Load an Easy Sequence.es for a valve or HeadSpace Injection Source and the Sample Name cell in the Sample List shows a Read barcode button.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

HeadSpace Simple Calibration Blank type should only allow 'Blank with injection'

Problem:

HeadSpace software will not run a sequence without a vial location.  Therefore, the Easy Sequence Setup\Calibration\Simple Calibration options should only allow Blanks with Injection and not allow blanks without injection.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Calibration Blank with no injection loads with Inj Vol as 0

Problem:

Create a setup with a blank with injection and a blank with no injection.
Save and load to Easy Sequence. The Injection volume for the Blank with no injection is entered as 0. Native sequence table also shows this as zero.
This is not consistent with the volume for the blank with injection

Temporary Solution:

n/a

Fix Information:

Fixed in revision 2.2

Keyword: 

One-line Description:

Calibration table clears on method reload from Samples tab

Problem:

Create a Setup with Calibration. Return to Sample tab and load the same or a different method with the same injection location. Return to Calibration tab and all has been cleared. Reloading a method does not clear entries made on the Samples tab.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Queue displays running vials incorrectly when initial HeadSpace vial not found

Problem:

Start a 3 line headspace sequence from the queue, but remove the FIRST vial in the sequence. Queue does not update correctly, showing the first vial as running, though the HeadSpace has moved on to vial 2.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Aborted HeadSpace run displays Status as 'Complete' in Queue History

Problem:

HeadSpace aborts, but ChemStation does not. Select the Abort Run button from the Waiting for ready dialog and ChemStation aborts the sequence.
Queue History shows this run as 'Complete' instead of 'Aborted'.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Easy Sequence does not advise of invalid vial locations until sequence is fully loaded into Queue

Problem:

There is no advisory about the invalid vial locations until the sequence has been added to the queue.

Temporary Solution:

n/a

Fix Information:

Fixed in revision 2.3

Keyword: 

One-line Description:

Sequence submitted to queue but will not run and can not be removed/deleted

Problem:

Sequence submitted to the queue but will not start and cannot be deleted.

Temporary Solution:

As a workaround, delete the following file:  SequenceQueue.que from the C:\Chem32\4\TEMP directory.

Fix Information:

Fixed in revision 2.4.

Keyword: 

One-line Description:

Injection Volume on ES Setup should show units (uL); valved inj are in mL and user must convert

Problem:

The Easy Sequence Setup dialog should show Injection volume units, which in ChemStation always seem to be uL. 

When the user uses EasySequence with a Valved injection, the volume, which for valves is mL, must be multiplied by 1000 to get a value that will be accepted.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Easy Sequence Setup should check for Sample Name length and not allow invalid entries

Problem:

Enter a long Sample Name in Easy Sequence Setup and add a counter.
Save and load to Easy Sequence. Fill Samples. Not until then is the user warned (with a red X) in the Sample list that there is a 40 character limit.
It is possible to save this but it will not be possible to add to the Queue.

Temporary Solution:

n/a

Fix Information:

Fixed in Easy Sequence 2.4[014].

Keyword: 

One-line Description:

Vial Status shows first run as completed for Easy Sequence following Run Method

Problem:

Run a single vial using Run Method.

Send sequence to queue vials 2-4. When the run method completes and the sequence loads and then the first vial in the sequence starts, Vial status shows the first line (vial 2) as immediately 'completed'.

The system stalls at Sequence running.  The GC is in prerun state and the system cannot start another run until it is shutdown and restarted.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Easy sequence actions are not included in the audit trail and no separate audit log exists

Problem:

Any changes done on Easy Sequence are not included in the audit trail; there is no separate audit log present for Easy Sequence.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Vial not found reported in software Status not consistent with instrument status

Problem:

Run an Easy Sequence using a HeadSpace injection source. When a Vial not Found event happens, the final Status for this run, which did not start a run, is reported as 'Completed'. The status being reported by the HS device is 'Run Aborted'.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

The GC Enters Prerun Too Early for Splitless Modes and Pulsed Split

Problem:

Set up a splitless (or pulsed split) method. The 7890 goes into pre-run at the beginning of the sample movement, rather than just prior to injection. This means for long vial equilibration times that the inlet is not being purged.

Temporary Solution:

Do not use splitless mode with the 7694 and G1888A headspace samplers.

Fix Information:

This will work in the 7697A headspace sampler with a minimum firmware revision of A.01.02.  The user needs to deselect the "Manual Run on Prep Run Request" on the 7890 configuration screen to make it work.

Keyword: 

One-line Description:

In EZChrom, it is Possible in Some Cases that the 7890A GC Aborts a Sequence but tne Headspace Will Continue On

Problem:

This occurs in Open Lab EZChrom Version A.04.02 workstation and earlier when  Sequence Action Continue for the 7697A or Proceed with the G1888/7694B in EZChrom

Temporary Solution:

Do not use Sequence Action Continue for the 7697A or Proceed with the G1888/7694B in EZChrom

Fix Information:

n/a

Keyword: 

One-line Description:

User is not able to save 'Column Parameter' changes at the same time when change is made

Problem:

User is not able to save 'Column Parameter' changes at the same time when change is made unless they click on another field on the screen

Temporary Solution:

n/a

Fix Information:

Resolved in B.01.02

Keyword: 

One-line Description:

Invalid Resource Item implementation for oven program

Problem:

Invalid Resource Item implementation for oven program

Temporary Solution:

n/a

Fix Information:

Resolved in B.01.02

Keyword: 

One-line Description:

Exponential calibration curve plot isn't shown in Calibration Report when using Intelligent Reporting.

Problem:

Exponential calibration curve plots cannot be reported with Intelligent Reporting. An empty plot is shown instead.

Temporary Solution:

If exponential calibration curves plots need to be reported, the (old) classic reporting needs to be used in ChemStation. 
EZChrom users need to use the EZChrom standard reporting.

Fix Information:

A potentially fix is currently under investigation.

Keyword: 

One-line Description:

LC detector lamps and column ovens do not turn off when using "Shutdown" sequence run types.

Problem:

LC detector lamps and column ovens do not turn off when using "Shutdown" sequence run types.

Temporary Solution:

Manually shutdown lamps and column ovens when required.

Fix Information:

Fixed in OpenLAB CDS A.04.05.

Keyword: 

One-line Description:

"Additional Reports" cannot be viewed from EZChrom instrument interface

Problem:

When specifying "print additional reports" as a sequence runtype, aquiring a sequence and then reviewing it, there are no sequence reports listed when selecting Reports, View, Sequence from the client.

Temporary Solution:

Browse to the folder where the report was stored and open the report to view.

Fix Information:

Fix is currently under investigation.

Keyword: 

One-line Description:

GC triggered by external device starts prior to platform readiness

Problem:

When using an Agilent GC that triggers an external device that is not part of the configuration, the trigger may happen prior to the system being ready to acquire data. This may result in the data system not correctly triggering for acquisition.

Temporary Solution:

Use samplers and devices supported within the configuration of the GC.

Fix Information:

Fix is currently under investigation.

Keyword: 

One-line Description:

Values for the Instrument Modules snippet not shown in the report

Problem:

Added 'Instrument Modules' snippet to report template.  The part number, serial number, and firmware values are not shown in the report.

Temporary Solution:

n/a

Fix Information:

Resolved in OpenLAB CDS EZChrom Edition A.04.07.

Keyword: 

One-line Description:

Intelligent Report InjOrderNumber issue

Problem:

In the Intelligent Report, the InjOrderNumber increses from 1..2..3. till the number of runs in the sequence. This is acting as an injection counter instead of acting as the number of injections/vial.

Temporary Solution:

n/a

Fix Information:

Resolved in OpenLAB CDS EZChrom Edition A.04.07.

Keyword: 

One-line Description:

OLCDS EZChrom IR should report both parameters: Peak Amount and Peak Concentration (corrected by multipliers)

Problem:

Right now only Peak Amount is recorded in IR.  Peak Concentration is not recorded.

Temporary Solution:

n/a

Fix Information:

This is planned to be fixed in OpenLAB CDS EZChrom A.04.05 Update 1.

Keyword: 

One-line Description:

6890 GC ALS cannot be deactivated by entering blank vial number

Problem:

When using GC 6890 with ALS and built-in valves, the ALS injection  works fine.

While using the valves, we give the input of a vial "0" or leave vail position blank so that the ALS wil not expect a vial/sample and the GC expects a manual start from the GC keyboard (Start run). However the ALS does not wait for trigger and immediately starts the run.

Temporary Solution:

Configure another instrument by disconnecting the ALS and then submit run while using the valves. Then the GC waits for trigger and the run starts only when the GC start button is pressed.

Fix Information:

This issue is resolved with an update to the GC driver.  The driver that is included with the A.04.06 release of EZChrom contains the update.  Using the EZChrom application, look for the drivers version currently in use.  It should say 68xx GC 6.23 (009).  The update is included in version 6.21 and higher.  This update is not currently available in any driver version that is validated with EZChrom A.04.05 (with any software patch) or earlier.  Although additional Software Updates may be available for A.04.05 in the future, there are none currently scheduled.

Keyword: 

One-line Description:

Cannot do dual channel data collection on 5890

Problem:

When you want to collect both the front and back detector channels into a single data file, you set the signal source in Instrument set up for detector 1 and detector 2.  In both A.04.04 and A.04.05, both signals will change back to the channel that you last setup when you save the method.

Temporary Solution:

It may be necessary to use EZChrom Elite in a Workstation mode to control the 5890 in this manner.  The instrument is long out of support, and the intention for OpenLAB CDS support is only for use in a Read Only manner.

Fix Information:

There are currently no plans to enhance the OpenLAB CDS support for the 5890 to be able to fully control the instrument.

Keyword: 

One-line Description:

A.04.05 - Inst Client Crash on Windows 7 When Processing Result with Method Report window open

Problem:

When reprocessing with the Method Report window InstClient crashes with an error saying "Instrument client has stopped working".

Temporary Solution:

Make sure the Method Report Window is closed during reprocessing

Fix Information:

This will be fixed in OpenLAB CDS EZChrom A.04.05 Software Update 3.

Keyword: 

One-line Description:

Intelligent Reporter Not Displaying per Peak Custom Parameter for Unnamed Peaks

Problem:

Intelligent reports in EZChrom (IR and OLIR) do not display values for per peak custom parameters for unnamed peaks (unknown peaks). The custom parameter value displays correctly in the EZChrom method report. This behavior is different from the behavior in OpenLAB ICM where values for per peak custom parameters displayed for all peaks in an injection, named and unnamed.

Temporary Solution:

n/a

Fix Information:

Fixed in OpenLAB CDS EZChrom Edition A.04.06.

Keyword: 

One-line Description:

The Intelligent Report cannot generate a report for a Single Data File

Problem:

When user opens the single Data file in EzChrom and try to preview the related data in an Intelligent Report(IR), the IR rendered the demo data instead of data in loaded data file. 

This is because the IR required the Result Set (ACAML file) to render the data in loaded data file.

This is the expected behavior in EZChrom system.

Temporary Solution:

Intelligent reporting should always be used in a sequence summary context. The *.RDL files can still be of "single run" type, but you would always reports across the entire sequence.

In order to get a single run Intelligent Reports for single, dedicated runs use the following workflow:
1. Load a result set
2. Change the run type of the samples runs you like to report to Begin summary (and select the template you like to use), Summary run and/or End Summary
3. Reprocess the entire sequence or the selected runs only (this will update the sequence ACAML file)
4. Go to the Reports tab> View > Sequence Report:  The dialog would display all the runs you have selected for the summary and the report template name
5. Press Preview report

This workflow allows you to use a specific summary template for e.g. System suitability runs and e.g. Single run templates for the unknowns.

Fix Information:

A solution is being evaluated for a future release of OpenLAB CDS EZChrom.

Keyword: 

One-line Description:

The Spectrum Similarity Table Does Not Show The Correct Colors

Problem:

The Spectrum Similarity Table does not show the correct colors when overlaying different spectra.

Temporary Solution:

n/a

Fix Information:

Fixed in OpenLAB CDS EZChrom Edition A.04.06.

Keyword: 

One-line Description:

Saved PDF reports inside SSIZIP May not Reflect The Latest Revision Inside ECM

Problem:

When reprocessing saving PDF reports inside a result set is an optional field. If a user does not choose to save the report inside the result set during reprocessing but the option was selected during acquisition, you will only have reports from the previous revision in ECM.

Temporary Solution:

n/a

Fix Information:

Fixed in OpenLAB CDS EZChrom A.04.05 Software Update 5.

Keyword: 

One-line Description:

Report prinout sizes were different based on different printing options in EZChrom

Problem:

The difference in printout sizes were observed in EZChrom A.04.05 when manually printing versus automatically printing.  The following setup was used to produce the printouts.

For Manual printout:
1. The "Result review mode" window is opened and displayed
2. Open the report of the method (method -custom report)
3. Print the report by doing Report>Print>Method report.

For automatic printout:
1. Reprocess the sequence and select "print hard copy" of the"method report"
2. The report is printed also but with a different format. The report is smaller, and the margins are bigger.

In conclusion there are two different report sizes.

Temporary Solution:

n/a

Fix Information:

A fix is planned for a future release of OpenLab CDS EZChrom.

Keyword: 

One-line Description:

Automation Guide instructions for no-vial analysis does not work

Problem:

The Agilent OpenLAB CDS EZChrom Edition (version A.04.05 and A.04.06) Automation Guide includes a couple of ways to submit a no-vial analysis using the SubmitSingleRun method.  This is in page 58:

PropInitialVial Property - Sets or returns the vial that will be used for the first injection of a sample in a single run by the SubmitSingleRun() method. This is a member of the
SingleRun object. To specify no vial, the ezAutosamplerNoVial constant may be used.

PropInitialVialText Property - Sets or returns the vial that will be used for the first injection of a sample in a single run by the SubmitSingleRun() method. This is a member of the
SingleRun object. To specify no vial, an empty string may be used.

Both scenarios does not work.

Temporary Solution:

The ability to do no vial runs using automation was a feature in EZChrom Elite.  That went away with the new drivers so the feature is no longer available in the Open CDS EZChrom Editions.

A no-vial analysis can still be done, but in the OpenLAB CDS EZChrom Edition application by submitting a run leaving the vial field blank in the sequence.

Fix Information:

There will be a correction to remove the appropiate sections in the manuals in a future release of OpenLAB CDS EZChrom Edition.

Keyword: 

One-line Description:

Doing two RefreshInstruments causes the instruments object to disappear

Problem:

We found that RefreshProjects and RefreshInstruments functions in the automation interface do not work as expected. Those function can only be called once.

We found that the Enterprise object must be cached after logging on. When getting the Enterprise object multiple times from the Application object, the automation interface does not close properly.

Since we know what not to do on the automation interface, we can work around this in our code. If we close this issue it is likely that the scenarios described here are not resolved or tested. I consider this up to you since we have workarounds in place but from my perspective the functions are broken.

Temporary Solution:

Do not do two RefreshInstruments.

Fix Information:

Resolved in OpenLAB CDS EZChrom A.04.07 SR2.

Keyword: 

One-line Description:

When performing "Add Runs to a Result" , the activity does not show in Result Set Sequence Audit Trail.

Problem:

The Result Set Sequence Audit trail does not show any entries when adding runs to the existing result sequence, even though the result sequence has changed.  Other changes in entries such as Sample ID, Run type, etc. do show up.   Some customers use this feature to keep using one Result Set to perform multiple runs without having to have separate files.

Temporary Solution:

For auditing and traceability purposes, the user will have to rely on a combination of the Sequence Last Modified Time and the Sequence Table on a Sequence Report that is generated at the end of each sequence run.  When creating a new standard report include both the Sequence Creation Time and the Sequence Last Modified Time.  Also include a sequence table by right clicking the mouse and choose Insert Report and then Sequence Table (customized) or (full). Either table shows the complete list of samples or runs in the sequence, and can be compared to the previous report for changes made.

Note that additional activities or changes made  when running the added Sequence will be recorded in the Sequence Audit Trail and not the Result Sequence Audit Trail because the changes occurred during acquisition.

Fix Information:

Fixed in OpenLAB CDS EZChrom Edition A.04.06.

Keyword: 

One-line Description:

Result Set Shows Up as Not Being Saved Eventhough It has been Saved.

Problem:

When printing a report using Reports--> Print Method Report after reprocessing a result set you get a message indicating that the results have not been saved eventhough they have been saved.

Temporary Solution:

To print a report in this scenario load another result set after reprocessing and then load the result set reprocessed earlier.

Fix Information:

This is fixed in OpenLAB CDS A.04.05 Hotfix 05.

Keyword: 

One-line Description:

method changes not saving in results set

Problem:

What I am saying is that if you only change the traces that show up on a method custom report and save the method, the new method custom report is not saved into the result set. If we make any other changes to the method or to the method custom report, and save the method, those changes are saved into the method in the result set (or the master method depending on what we choose to save)

But if you only change what trace (or channel) is shown on the method custom report and save the method, the method in the result set is not saved.

Just open a result set
Change the trace shown on the method custom report
Save the method
Process the result set
Open the method custom report
You will see the trace was not changed

Temporary Solution:

There is no workaround at this time.

Fix Information:

n/a

Keyword: 

One-line Description:

Number Of Reps in A Single Run Is Not Being Handled Correctly

Problem:

You get an error message when you try to start a single run when using reps.  This is due to the fact that reps are not being handled correctly when using a Single Run.

Temporary Solution:

Do not use reps when using a single run.

Fix Information:

Email thread:
-------------------------------------------
From: LINDAHL,JOHN (A-USA,ex1) 
Sent: Saturday, April 23, 2016 8:09 AM
To: MCCULLEY,JENNIFER (A-USA,ex1) <jennifer_mcculley@agilent.com>
Cc: JAIN,BABITA (A-Americas,ex1) <babita.jain@agilent.com> GOLDBERG,SETH (A-SantaClara,ex1) <seth_goldberg@agilent.com>
Subject: RE: Waiting for verification.xlsx

Correction. They are closing as verified from our review here.


From: LINDAHL,JOHN (A-USA,ex1) 
Sent: Saturday, April 23, 2016 8:05 AM
To: MCCULLEY,JENNIFER (A-USA,ex1) <jennifer_mcculley@agilent.com>
Cc: JAIN,BABITA (A-Americas,ex1) <babita.jain@agilent.com> GOLDBERG,SETH (A-SantaClara,ex1) <seth_goldberg@agilent.com>
Subject: RE: Waiting for verification.xlsx

Hi Jennifer,

I reviewed the list and found one already closed and one that I feel needs verification (222978). I assigned that over to Nitin for the HF6 project.

The rest are closing as DNF.

115120,116117,130473,142304,146057,147748,157630,161372,162010,174035,182152,184930,186547,186549,186550,186553,195173,197027,198564,202789,207114,209281,211805,213045,220260,220931

John


 
From: MCCULLEY,JENNIFER (A-USA,ex1) 
Sent: Wednesday, April 20, 2016 6:32 AM
To: LINDAHL,JOHN (A-USA,ex1) <john_lindahl@agilent.com>
Cc: JAIN,BABITA (A-Americas,ex1) <babita.jain@agilent.com> GOLDBERG,SETH (A-SantaClara,ex1) <seth_goldberg@agilent.com>
Subject: RE: Waiting for verification.xlsx

Most if not all are DNF that we missed to close them out entirely.   Therefore we should just close them if DNF works than I am fine with this.  

Regards,

Jennifer


 
From: MCCULLEY,JENNIFER (A-USA,ex1) 
Sent: Tuesday, April 19, 2016 2:11 PM
To: JAIN,BABITA (A-Americas,ex1) <babita.jain@agilent.com> LINDAHL,JOHN (A-USA,ex1) <john_lindahl@agilent.com> GOLDBERG,SETH (A-SantaClara,ex1) <seth_goldberg@agilent.com>
Subject: Waiting for verification.xlsx
 
There are defects waiting for verification due to the defect clean-up project we did last year.   Since we just had a full suite of testing done on a.04.07 SR2 and no response to the defects, please do a mass update with the x-functional team approval to close the defects.   
 
Thank you.
 
Jennifer
-------------------------------------------

Keyword: 

One-line Description:

Entry for error, when failing to upload results to Data Store,  is not logged within Instrument Activity Log while acquiring data.

Problem:

A log entry does not get inserted into the Instrument Activity log when data does not get uploaded due to the Data Store path not being found or the Alfresco Tomcat Service being stopped.

Temporary Solution:

None

Fix Information:

A fix is being evaluated for a future release of OpenLAB CDS EZChrom.

Keyword: 

One-line Description:

Only the latest revision of a Method Can Be Used For Acquisition

Problem:

When using OpenLAB CDS EZChrom with ECM or Datastore a user can only use the latest revision of a method for acquisition.

Temporary Solution:

OpenLAB CDS EZChrom allows running only the latest revision of a method for acquisition. If a user wishes to perform acquisition with an older revision of a method, the user must save the method before the run.

Fix Information:

n/a

Keyword: 

One-line Description:

When adding samples to a running sequence while the Instrument Monitor is OFF, the added new samples do not get processed in the actively running sequence.

Problem:

When editing a running sequence such as adding samples while the Instrument Monitor is set to OFF, the added samples do not get processed in the actively running sequence.  But in the EZChrom Elite version, changes made while the Instrument Monitor is OFF are taken into effect for the active sequence, and the added samples are processed. 

Here's an example of a workflow that describes the problem in OpenLAB CDS EZChrom Edition:
1. Run the sequence
2. Disable the Instrument Monitor (Done by going to Control and uncheck Monitor "Instrument Name"
3. Add new samples in a timely manner
4. Save the modified sequence
5. Enable the Instrument Monitor
6. Although the new samples are visible, they DO NOT get processed
7. But new samples added while Instrument Monitor is ON does get processed.

Temporary Solution:

The current workflow of not being able to edit a sequence with the instrument monitor off is by design in OpenLAB CDS EZChrom Edition.  It was made different from the old version, because in EZChrom Elite the function presented a risk and a compliance issue; a user from any other instrument was able to make accidental or unwanted changes to the running sequence.

In the OpenLAB CDS EZChrom Edition the sequence was separated so that one is running on the AIC, and the other one, when Instrument Monitor is OFF, is opened from storage.  In addition to this change, another new feature allowed different instruments to run the same sequence concurrently.

Suggested Workaround for Issue:  Make changes to the sequence while the Instrument Monitor is ON.  The user should be able to perform all other tasks while Instrument Monitor is OFF.

Fix Information:

There is no plan to re-design the sequence editing function for changes made while the Instrument Monitor is OFF to be implemented and processed in the running sequence.

But we do recognize the confusion of the user interface when the Instrument Monitor is back ON, which shows the changes made to the sequence while the Instrument Monitor is OFF.  We will evaluate a change to make the user interface less confusing in a future version of OpenLAB CDS EZChrom Edition.

Keyword: 

One-line Description:

Hitachi Primaide Detectors may not Get Configured

Problem:

A Hitachi Primaide detector is detected when you run the Hitachi Maintenance program but may not get configured when you run autoconfigure when configuring an instrument on OpenLAB CDS EZChrom A.04.06.

Temporary Solution:

n/a

Fix Information:

There is an updated Hiatchi Primaide driver coming out shortly for OpenLAB CDS EZChrom A.04.06 which will fix this.  Inquire about this update before installing a Hitachi Primaide with OpenLAB CDS EZChrom A.04.06.

Keyword: 

One-line Description:

Error trying to display the Instrument Status Screen For Hitachi LaChrom Elite

Problem:

The instrument status screen for Hitachi LaChrom Elite on OpenLAB CDS EZChrom A.04.06 opens but a blank message box displays on the screen causing the instrument status screen to become disfunctional.

Temporary Solution:

n/a

Fix Information:

There is an updated Hiatchi LaChrom Elite driver coming out shortly for OpenLAB CDS EZChrom A.04.06 which will fix this.  Inquire about this update before installing a Hitachi LaChrom Elite with OpenLAB CDS EZChrom A.04.06.

Keyword: 

One-line Description:

Use external program before run doesn't work

Problem:

In the Method\Advaned\Files menu, there is a checkbox for Before Run. One can enter an executable here that will be called up before the run. Something like calculator.exe works fine for this. It is called up for EZChrom Elite, however it doesn't work on my OLCDS EZChrom work station.

Temporary Solution:

None as yet

Fix Information:

n/a

Keyword: 

One-line Description:

Wrong signal runtime acquired if the last sample from a previous sequence is aborted or it is defined as a shutdown sample.

Problem:

Each LC module has the possibility to define its own runtime. That feature should not be used with OpenLAB CDS EZChrom A.04.05 . Set a runtime in the pump and set all other modules with the "as pump runtime"  option.

Temporary Solution:

Do not set method runtime at different LC modules.

Fix Information:

n/a

Keyword: 

One-line Description:

Instclient.exe crashing during sequence reprocessing due to long Sample ID length while printing in landscape mode from the Method Report

Problem:

Reprocessing of sequence failed at line that has a long Sample ID name in the Method Report..  

The crash occurred with specific settings in the OpenLAB CDS EZChrom's Method Report. For example, choose the Landscape option in the View / Preferences / Page settings options, Load the Result Set and go to Result Set / Process, Set Processing to Use Last Results, and Report to Save as PDF / check the Method box.  Then start reprocessing and wait so see the failure at the line with the long Sample ID.

The following settings will not fail: page setting is not Landscape, user changes the "SAMPLE ID" to something equal or less than a certain number of characters, and if it is not printing or saving to PDF.

Temporary Solution:

Below are two workarounds:

1. Shorten the Sample ID, or other fields that may be causing the problem.

2. Reconfigure the Method Report to allow sufficient space for each field.  In the SSB Problem example, the method report contained a line with multiple fields: Sample ID, Computer Name and User who Acquired the Data.  If the Sample ID had its own line in the method report, there will be no crashing.

The length that is causing problem is not only the sample ID length but the length of the whole line which includes the sample ID, Computer name, User who acquired the data, etc.  It appears that in certain case the initial calculation of the length of the line with respect to available length for that orientation appears to be OK but while rendering the line it is causing the problem.  This rendering is also specific to the way the Method report is configured.

Fix Information:

A fix will be evaluated for a future release of OpenLAB CDS EZChrom.

Keyword: 

One-line Description:

Strings in exported CDF file produced by EZChrom are truncated

Problem:

Users have reported that several strings in the CDF file that EZChrom generates get truncated so that the file name may not be totally visible. 

The following strings are truncated to certain character lengths when the file path names and or file names are too long:

detection_method_name : truncated to 63 characters
peak_processing_method_name: truncated to 63 characters
sample_name: truncated to 29 characters
sample_id : truncated to 29 characters

Temporary Solution:

Reduce the combined strings of the file path names and file names to be below the character limits for each of the following fields:

detection_method_name : below 63 characters
peak_processing_method_name: below 63 characters
sample_name: below 29 characters
sample_id : below 29 characters

Note that the strings for detection_method_name and peak_processing_method_name are the ones that include the file path.  The other ones do not.

Fix Information:

A solution is being evaluated for a future release of OpenLAB CDS EZChrom.

Keyword: 

One-line Description:

Error in RCNet_RCASTrayUI when opening a tray view before instrument connection.

Problem:

This is regarding the error: "Error in RCNet_RCASTrayUI:: SetVialColor : Invalid Location Vial 81", that we are seeing in an Agilent LC.  

Software: OpenLAB CDS EZChrom A.04.05
Configuration:  The LC is a 1290 with a G4226A sampler that contains a 100 vial tray.

The error stems from  not being able to set the vial color on the  Control/Autosampler Trays/HiP Sampler view. 
If one opens the instrument and injects from vial 1-10, open the tray view, close and reopen the instrument, no error will occur. 

However, if one injects from a vial outside of the 96Agilent tray range like 81, close the instrument with the tray view still open then reopen the instrument, the error will occur.

Temporary Solution:

The simple workaround would be either to not open the tray view or wait until the instrument connects before opening it and being sure to close the view before closing the instrument. 

Upon opening the instrument, this default tray view (Agilent96) is seen until a connection with the ALS is made, then the correct tray is seen.

Fix Information:

A fix is being evaluated for a future release of OpenLAB CDS EZChrom.

Keyword: 

One-line Description:

Sequence will NOT reprocess unless all data files reside in the same Result Path folder in a Project set as File mode

Problem:

In older OpenLAB CDS EZChrom versions, users were able to reprocess data files from many different subdirectories.

In OpenLAB CDS EZChrom A.04.06, a sequence will NOT reprocess data files unless they all happen to reside in the same Result Path.  This only occurs if the Project settings is in the "File Mode".


In the "Result Package Mode" for A.04.06, this is not an issue.

Temporary Solution:

When creating a project use the other Project setting: Result Package Mode.

If the project settings change is not acceptable and the user wants to reprocess an aggregate of data files from multiple subdirectories, the user has to copy the data files to a central location and then point the "Result Path" to this location.

Fix Information:

A fix is planned for a future release of OpenLAB CDS EZChrom.

Keyword: 

One-line Description:

New Sequence Has Read Only Fields When In Result Review Mode

Problem:

If you create a new sequence while you are in result review mode and a result sequence is open, the newly created sequence has read only fields that cannot be edited.

Temporary Solution:

The workaround for this is to close the open result sequence before creating a new sequence.  This will allow a new sequence to be created without read only fields.

Fix Information:

n/a

Keyword: 

One-line Description:

Unable to report values of "SignalToNoise" and "SignalToNoise6Sigma" in Intelligent Report for Japanese version

Problem:

An Error message "An error occurred during report rendering. The report cannot be reprocessed�."  is displayed when a user previews an intelligent report template after adding the parameters "SignalToNoise_EP" and "SignalToNoise6Sigma" in the Japanese version.

Temporary Solution:

n/a

Fix Information:

A hotfix for A.04.05 will be made for this issue but we do not have any dates yet.

Keyword: 

One-line Description:

Unable to See Chromatogram when Processing a Sequence with Review-Result Review for Data Store only

Problem:

When the user performs Process Sequence with the Review-Result Review (Pause after each run) turned on, the chromatogram does not pause.  The user presses the down arrow to process the next sample, but the chromatogram pops up quickly for a second then dissappears.

This observation occurs only when the system using Data Store.  It does not occur for other OpenLAB CDS EZChrom systems.

Temporary Solution:

The reprocessed sample chromatograms can be seen at the end of reprocessing.

Fix Information:

Resolved in OpenLAB CDS EZChrom A.04.07 SR2.

Keyword: 

One-line Description:

Peak Names Truncated in CDF Files When Working With Double Byte Characters

Problem:

In OpenLAB CDS EZChrom A.04.06, peak names are getting truncated in CDF files when working with double byte characters.

Temporary Solution:

n/a

Fix Information:

This will be resolved in OpenLAB CDS EZChrom A.04.06 Software Update 3.

Keyword: 

One-line Description:

The Area Ratio Custom Parameter Does Not Work in OpenLAB CDS EZChrom A.04.05

Problem:

In OpenLAB CDS EZChrom A.04.05 the Area Ratio Custom Parameter does not work.  Results do not show up in the report.

The Area Ratio Custom Parameter does work in OpenLAB CDS EZChrom A.04.06.

Temporary Solution:

n/a

Fix Information:

The Area Ratio custom parameter will not be fixed in OpenLAB CDS EZChrom A.04.05.  If this fuctionality is needed, the recommendation is to upgrade to OpenLAB CDS EZChrom A.04.06.

Keyword: 

One-line Description:

When creating a sequence to reprocess data with the same names from different Results Set folders, data files are overwritten in the new Result Set folder..

Problem:

When a user creates a sequence that contains data files from different Result Set folders, and if the data files have the same name, those data files in the new Result Set folder are overwritten by the latter ones in the sequence.

For example, if a customer wants to evaluate the standard response of a data point from multiple folders to check the response factor variation, the data files need to have distinctive names.  If all the files names are exactly the same, there will only be one data point, and the new Result Set folder will contain only one data file.

OpenLAB CDS EZChrom does not prevent this and there is no warning to show the user.

A warning and or an Auto-renaming of those files when reprocessing will be a good idea.

Temporary Solution:

The workaround is to manually rename the files (or copy and rename the files to another folder) to be reprocessed.  

If the system is using an Advanced File System (AFS) mode, there is also a manual way to rename the files or create new folders.  The user will have to log into Windows with an Enterprise Service Account, or a member of the AFS group, that has access to the enterprise path under the restrictions of AFS.

Another workaround is to prevent the data files from having the same name by using the Date/Time naming convention when acquiring the data files.

Fix Information:

A solution will be evaluated for a future release of OpenLAB CDS EZChrom

Keyword: 

One-line Description:

The function Add Single Run to Result does not allow the use of replicates

Problem:

When you use the function "Add Single Run to Result" the replicates field is greyed out.  The use of replicates should be allowed with any type of run addition.

Temporary Solution:

The work-around for this workflow is to use "Add Runs to Result" instead of "Add Single Run to Result".  Create a new sequence with one run and enter in the number of replicates to use.  Then open the Result Set and use the function "Add Runs to Result" and use the new Sequence with the one run.  This will allow the one run to be added along with the replicates.

Fix Information:

A solution will be evaluated in a future release of OpenLAB CDS EZChrom.

Keyword: 

One-line Description:

Aborting the current run will abort all replicates in a run when using the Single Run option

Problem:

If the user is performing a Single Run with replicates and aborts only the current run, the current run will be aborted along with the rest of the replicate runs.  Only the current run should be aborted and the rest should continue to be processed.

Temporary Solution:

Instead of using the Single Run option, create a Sequence with one run, enter the desired number of replicates (Reps) and perform a Sequence Run.  Then aborting a run will stop only the current run and any replicate after will continue to be processed.

Fix Information:

A solution will be evaluated for a future release of OpenLAB CDS EZChrom.

Keyword: 

One-line Description:

Instrument window crashes when adding spaces in header of snandard report

Problem:

After adding spaces between a letter and adding spaces in the header of standard report instrument window crashes

Temporary Solution:

Instead of using spaces use TAB as space separator

Fix Information:

n/a

Keyword: 

One-line Description:

Single Sign on with Automation

Problem:

Single sign on with Automation does not work.

Temporary Solution:

n/a

Fix Information:

Resolved in OpenLAB CDS EZChrom A.04.07 SR2.

Keyword: 

One-line Description:

Edited sequence during "pause pending" not instantiated

Problem:

1. Create & launch any instrument online.

2. Create & submit two line sequence (with two replicates, Unknown as run type and with filename as 'Date & Time') for acquisition.

3. Pause sequence while first replicate acquisition is in progress.

4. In pending pause state, make some changes in 'Run type' column for pending pause line (Begin summary) and for next line (End summary) and save the sequence.

5. Resume run queue in processing (pending pause) state.

6. Result set completed successfully but result set is not created as per changes made in sequence.

7. From Report->View sequence report. Report is seen in it but it's not viewable to user.

8. Report is uploaded to respective backend.

Temporary Solution:

Edit only paused sequence

Fix Information:

Ready for development

Keyword: 

One-line Description:

Unable to set the calibration curve of Log amount & Log response scale

Problem:

Unable to set the calibration curve of Log amount & Log response scale in OpenLAB CDS EZChrom Compact A.04.07.  This only occurs in the Japanese version.

Temporary Solution:

n/a

Fix Information:

Resolved in OpenLAB CDS EZChrom A.04.07 SR2.

Keyword: 

One-line Description:

Double samples are submitted to headspace when using sequence bracketing when using a headspace with OpenLAB CDS EZChrom

Problem:

Double samples are submitted to headspace when using sequence bracketing when using a headspace with OpenLAB CDS EZChrom.

Temporary Solution:

n/a

Fix Information:

Resolved in OpenLAB CDS EZChrom A.04.07 SR2.

Keyword: 

One-line Description:

A User Can Edit A Running Sequence Without The Privilege

Problem:

In OpenLAB CDS EZChrom A.04.07 SR1 a user can edit a running sequence after pausing even if they do not have the privlege to do so.  The save sequence menu item is disabled; however, the user is prompted and able to save the sequence after restarting the run.

Temporary Solution:

n/a

Fix Information:

Resolved in OpenLAB CDS EZChrom A.04.07 SR2.

Keyword: 

One-line Description:

Method Resolution window not "finishing."

Problem:

When the Method Resolution window pops up, the oven tab is the default. A box is not being drawn completely, leaving the bottom portion missing. The window is also much larger than it needs to be.

Temporary Solution:

n/a

Fix Information:

Resolved in OpenLAB CDS EZChrom A.04.07 SR2.

Keyword: 

One-line Description:

OpenLAB Control Panel crashes after configuring an instrument for the 35900

Problem:

The OpenLAB Control Panel can crash when closing the configuration window after configuring a 35900 instrument with version B.01.01 of the 35900 driver.  This only occurs during the initial configuration.

Temporary Solution:

n/a

Fix Information:

To prevent the control panel from crashing install the Microsoft .NET fix using the link below.

https://download.microsoft.com/download/2/8/7/2870C339-3C77-49CF-8DDF-AD6189AB8597/NDP453-KB2969351-x86-x64-AllOS-ENU.exe

Keyword: 

One-line Description:

User not able to uninstall the "Agilent OpenLAB CDS EZChrom Edition-Agilent A/D" driver from Uninstall a Program on a Window 8.1 machine

Problem:

A user is not able to uninstall the "Agilent OpenLAB CDS EZChrom Edition-Agilent A/D" driver from Uninstall a Program on a OpenLAB CDS EZChrom A.04.07 Window 8.1 machine.

Temporary Solution:

n/a

Fix Information:

On the Windows 8 machine disable the following local security policy before uninstalling:  Security Settings->Local Policies->Security Options->User Account Control: Run all administrators in Admin Approval Mode

Keyword: 

One-line Description:

Need to verify that Hitachi registry key is deleted after Hitachi Drivers Are Uninstalled

Problem:

If the Hitachi drivers installed with the OpenLab CDS EZChrom A.04.07 are uninstalled, please verify the registry key below is deleted from the registry after the uninstall.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\Analytical

Temporary Solution:

Manually delete the registry key if it persists after the driver uninstallation:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\Analytical

Fix Information:

There is no fix planned.

Keyword: 

One-line Description:

Software crash if Front Exponential Skim integration event is used and a peak is not defined.

Problem:

The Front Exponential Skim integration event can cause the instrument client to crash when you reprocess if the start and stop time range defined does not contain a valid peak.

Temporary Solution:

When using the Front Exponential Skim integration event make sure there is a valid peak in the defined start and stop time range.

Fix Information:

n/a

Keyword: 

One-line Description:

OpenLAB CDS EZChrom Antivirus Exclusions

Problem:

It is recommended that the following paths be excluded when using an antivirus program with OpenLAB CDS EZChrom:
The path that you use to store your data
C:\programdata\chromatography system\recovery data
C:\programdata\agilent
%programfiles%\agilent
%programfiles%\common files\agilent
%programfiles(x86)%\common files\agilent
%programfiles%\agilent technologies
%programfiles(x86)%\agilent technologies
%programfiles%\common files\agilent technologies
%programfiles(x86)%\common files\agilent technologies
%programfiles%\common files\agilent shared
%programfiles(x86)%\common files\agilent shared

Temporary Solution:

n/a

Fix Information:

Antivirus Exclusions are documented in the installation manuals of A.04.08

Keyword: 

One-line Description:

Manual integration fixes while data is being acquired get lost after data acquisition is complete.

Problem:

The manual integration fixes table is enabled during data acquisition which allows customers to make changes to this table while data is being acquired.  When changes are made to this table while data is being acquired the changes are lost after data acquisition is complete.

Temporary Solution:

If manual integration changes should be saved, they cannot be edited during running acquisition. Make the changes afterwards. 

Fix Information:

n/a

Keyword: 

One-line Description:

Missing Advanced Run Information in Method Report

Problem:

The LC Driver A.02.13 introduced the implementation of IRCControlAnalyticalResults to add advanced run info to the acquired data, such as temperature at start of run etc. In ChemStation these advanced run info are part of the ACAML and can therefore be reported via IR. Running a sample in EZChrom shows that no DiagnosticData are written to the ACAML result.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

error on project creation in mixed mode when Project Group has a name with leading space

Problem:

When creating a project under a project group with leading space in mixed, an error message can show up: "An error prevented project changes from being saved". The project has not been created.

Temporary Solution:

There should not be leading spaces in front of Project Group Names

Fix Information:

A fix is planned for a later revision.

Keyword: 

One-line Description:

Unable to integrate old data after Upgrade from A.04.07 sr1 to A.04.07 sr2

Problem:

Unable to integrate old data after Upgrade from A.04.07 sr1 to A.04.07 sr2. LC drivers were also upgraded to latest version.

Temporary Solution:

Create a new instrument for reprocessing using the old data.

Fix Information:

n/a

Keyword: 

One-line Description:

After reprocessing, the result set name will be reported twice in IR instead of the result set and sequence template name

Problem:

Before reprocessing the sequence name field, will report the result set name as well as the sequence template name. 
After reprocessing the result set name will be reported twice and the sequence template name no more.

Temporary Solution:

n/a

Fix Information:

A fix is planned for a later revision.

Keyword: 

One-line Description:

Data lost by using Chinese special characters with ECM backend

Problem:

With A.04.07 SR2 HF05 there is a new separate location in the Enterprise Path with the name "RSTBackup" which is used with ECM backend when a file is unzippable. Files which can not be zipped and uploaded to ECM will be backed up to this separate location in the Enterprise Path: (\\EnterprisePath\RSTBackup\AICName\SSIZIP_Date-Time)
However since ECM does not support localization, when customers are using ECM, their OS needs to be an English OS with an English keyboard.

Temporary Solution:

n/a

Fix Information:

Fixed in A.04.07 SR2 HF05 and in A.04.08

Keyword: 

One-line Description:

Able to print sequence without saving

Problem:

Users are able to print a sequence without saving the sequence.

Temporary Solution:

n/a

Fix Information:

A fix is planned for a later revision.

Keyword: 

One-line Description:

Printouts for injection reports may not print in their injection order

Problem:

Reprocessing a sequence, each injection report creates its own pdf file and sometimes those pdf files are not sent to printer in the proper order (inj1, in2, inj3...). They get printed in the order they get processed by the printer server.

Analysis of the cause:
The difference in the order of sample in the sequence and the order of the physical printout is possibly caused by multiple factors, but mainly by various data complexity and network latency. These lead to a result that data reprocessing and report generation for later sample in the sequence may be completed faster than earlier samples. Or in a distributed setup, the report of later sample may reach the printer faster than earlier samples. 

 

Temporary Solution:

Recommendations to avoid printout out-of-order
Use the relevant best practice based on actual customer workflows:
1.	If the customer perform batch reprocess with automatic report generation and printing. The best practice is to define the printout in the method, so that the samples are reprocessed and report print out as soon as the data acquisition is completed. There is no racing of multiple reports reach to the printer, due to the gap introduced between reports (i.e. data acquisition time).
2.	If the customer reviews the result post acquisition, perform manual integration before print out. (It is very unlikely that the print out-of-order would happen in this scenario, but if it does), customer can use reprocess with review option (check the pause after each run). 

Fix Information:

DNF

Keyword: 

One-line Description:

IQT/SVT Fix for RC IF Deployment for OpenLAB EZChrom A.04.08

Problem:

Software verification report for Agilent Rapid Control .NET [3.0] [5] is FAIL. IQT/SVT Fix for RC IF Deployment for OpenLAB EZChrom A.04.08

Temporary Solution:

n/a

Fix Information:

Resolved in B.01.02.059

Keyword: 

One-line Description:

CDS EZChrom with ECM doesnot display all the subfolders when browsing for Project Path during project creation

Problem:

Problem - When the when creating projects and specifying project path, If you have more than 100 Sub folders, then you would not be able to set the project path correctly because ECM window displays only the first 100 folders.

Temporary Solution:

n/a

Fix Information:

Fixed in OLSS 2.1 - Hotfix 4 which does not support ECM 3.4.1

Keyword: 

One-line Description:

CDS is getting crashed as we trace large size data file (184 MB)

Problem:

The issue is to overlay traces (chromatograms) from very large data file (>184MB) in viewer. 
1.Create a sequence using large size data file.
2.Process the sequence twice to create two result set.
3.Open any one result set and perform Add Trace -> Other data file.
4.Choose data file from another result set created above.

Temporary Solution:

n/a

Fix Information:

Do not fix. Low risk and corner case.

Keyword: 

One-line Description:

The online signal is missing after an acquisition run has started.

Problem:

The signal is present until the start signal of the injection. After the acquisition was started, the online signal is no longer displayed. This behavior was observed with a GC-2010 with FID-detector but can also happen with a GC-2014. The run will not be interrupted and the data is  completely collected and stored in a data file.

Temporary Solution:

The "Sampling rate" in the method must be in "Cycle" mode. The value of the "Sampling rate" must be the same as the "Base period" of the instrument configuration window of the detector.

Fix Information:

Fixed in Shimadzu GC v2.00

Keyword: 

One-line Description:

Flexible Cube G4227A does not work with HiP ALS G1367E

Problem:

On Chinese or Japanese CDS only the 1290 Infinity Flexible Cube G4227A does not work with High Performance Autosampler G1367E. 

On English CDS the operation of 1290 Infinity Flexible Cube G4227A with High Performance Autosampler G1367E is not affected.

Temporary Solution:

n/a

Fix Information:

Resolved in revision A.02.02

Keyword: 

One-line Description:

Lamps and cells of G1314F show incorrect dates in the RFID tags

Problem:

Lamps and cells of G1314F show incorrect dates in the RFID tags

Temporary Solution:

n/a

Fix Information:

Fixed with the driver version A.02.06

Keyword: 

One-line Description:

AFC & UIB II: AFC does not fractioning as expected

Problem:

System configuration:
1 DAD
1 UIB II
2 AFCs -> 1 AFC Cluster
Analog out of DAD connected to Analog In of UIB II
Simulated signal of DAD was used

Method settings for modules (expect threshold for UIB II signal): see attached method

1. Created a data file with the simulated signal recorded by the UIB II
2. Loaded data file into Fraction Preview
3. Used Fraction Preview to collect peakbased fractions with threshold > 0.12 V
4. The value 0.12 V is written into the table on the left side without conversion (the table shows mV as unit)

Using this method will cause that the AFC will fractioning all the time.

Cause:
The firmware interface expects the threshold in mV but the driver writes 0.12 (V) to the AFC
This causes that the AFC is fractioning all the time.

Temporary Solution:

n/a

Fix Information:

Fixed in UIB II signal is delivered as mV signal similar to  UIB I since LC Driver Release A.02.07.

Keyword: 

One-line Description:

Use Vial as Fraction collections

Problem:

Started a run with fraction collection.

The fraction collector config does not show 10 vials but only trays.

Temporary Solution:

If you have installed a 2 WP-Tray, vials are allways forbidden to use for fractionation, regardless if there are wellplates inserted or not.

Fix Information:

Issue fixed with LC and CE Driver revision A.02.07

Keyword: 

One-line Description:

Recovery volume and fraction volume: behaviour for reset volume

Problem:

I worked with one AFC.
Configured 2 wps +10 vials and 15 vial tray for recovery.

Started multiple runs. 
For each run a new Recovery location was used.
Then removed the recovery tray and entered it again.

Next run started with first recovery location --> this was already used.

Temporary Solution:

If you want to reset the Funnel Trays only, use "Reset Funnel Tray Volume"

If you want to reset Wellplates and vials (all except funnels), use "Reset Fraction Volume"

Fix Information:

Issue fixed with the LC and CE driver revision A.02.07

Keyword: 

One-line Description:

Fraction start location in a sequence parameter cannot accept the number "1" when using 2P+10Funnel tray at RC.net driver.

Problem:

The customers want to use 10 Funnels at the tray 2P+10Funnel without plates.

Temporary Solution:

Solved with LC & CE Drivers A.02.09

Fix Information:

N/A

Keyword: 

One-line Description:

After applying HF6, Customer workflow cannot be used any more due customer needs 2 user, samelevel, esign each datafile

Problem:

When a user with same level role tries to apply signature, user get following error:
“Failed to apply electronic signature. Data file is already signed by <user> (<User level>).”

Temporary Solution:

n/a

Fix Information:

OpenLAB CDS EZChrom Edition A.04.07 SR2 Update8 Point Patch 1
Fix is implemented around the e-signature functionality to resolve the issue wherein the multiple users having same signature levels are restricted from signing already signed data i.e. users are restricted from doing peer reviews. 

Keyword: 

One-line Description:

Windows 10 feature updates can corrupt existing EZChrom A.04.08 installation 

Problem:

When Windows 10 feature updates are performed on systems with existing OpenLab CDS EZChrom A.04.08 installations, the EZChrom installation can become corrupt. In some cases repair was successful, but with the later feature updates of Windows 10, like this to version 1709 or 1803, it happened frequently that EZChrom installations did break and could not be repaired. In such cases uninstall, reapply the necessary system settings and reinstall EZChrom is supposed to solve the problem. 

Temporary Solution:

Updates can be deferred for a different time depending on the Windows 10 servicing channel assigned. E.g.: Windows 10 Enterprise Long-Term Servicing Branch edition (LTSB)
For domain environments Windows 10 feature updates can be controlled with different Servicing Tools. E.g. the optional server role: Windows Server Update Services (WSUS)

Fix Information:

The identified defect will be fixed in OpenLab CDS EZChrom A.04.09. 
This should improve stability for future Windows feature updates 

Keyword: 

One-line Description:

Printouts for injection reports may not print in their injection order

Problem:

Reprocessing a sequence, each injection report creates its own pdf file and sometimes those pdf files are not sent to printer in the proper order (inj1, in2, inj3...). They get printed in the order they get processed by the printer server.

Analysis of the cause:
The difference in the order of sample in the sequence and the order of the physical printout is possibly caused by multiple factors, but mainly by various data complexity and network latency. These lead to a result that data reprocessing and report generation for later sample in the sequence may be completed faster than earlier samples. Or in a distributed setup, the report of later sample may reach the printer faster than earlier samples. 

 

Temporary Solution:

Recommendations to avoid printout out-of-order
Use the relevant best practice based on actual customer workflows:
1.	If the customer perform batch reprocess with automatic report generation and printing. The best practice is to define the printout in the method, so that the samples are reprocessed and report print out as soon as the data acquisition is completed. There is no racing of multiple reports reach to the printer, due to the gap introduced between reports (i.e. data acquisition time).
2.	If the customer reviews the result post acquisition, perform manual integration before print out. (It is very unlikely that the print out-of-order would happen in this scenario, but if it does), customer can use reprocess with review option (check the pause after each run). 

Fix Information:

DNF

Keyword: 

One-line Description:

Monitor Baseline disabled

Problem:

The Monitor Baseline feature accessible via the Instrument View is disabled.

Temporary Solution:

Create and execute a blank run to monitor the baseline

Fix Information:

n/a

Keyword: 

One-line Description:

No 3D data access

Problem:

3D field data, e.g., DAD or FLD spectral data is not accessible. Selecting 3D data acquisition in the instrument method has no effect on the recorded data.
Online spectra are not available and the result files do not contain 3D data.

Temporary Solution:

n/a

Fix Information:

This was implemented in SII 1.1

Keyword: 

One-line Description:

Unable to retrieve method from ECM

Problem:

A.04.09 with ECM 3.6 and previous versions

Steps to reproduce:
 1. Launch and instrument online from a long project (Project name with 100 characters or more).
 2. Create a method and save it with long name. Method name with 75 characters or more).
 3. Open Blank New method from File > New > Method.
 4. Now try to open the method created at step 2.

Actual Result
• Error message “Unable to retrieve the file from content management” and method is not open.

ECM URL: If this URL encoded path length exceeds 245 characters, the file will not be uploaded. Read entire section, General Constraints on File Path Lengths, in ECM 3.5 ECM Administrator's Guide.pdf, for special character interpretation. 

UNC Path: Enterprise path length is limited to 245 characters by OpenLAB CDS EZChrom. If the enterprise path length exceeds 245 characters, the file will not download.
 

Temporary Solution:

Agilent recommends using as short as possible file names and/or comply with the Windows OS path limitations.

Fix Information:

n/a

Keyword: 

One-line Description:

UV/Vis Chromaster Ultra RS detector displays dual channel mode only during the run

Problem:

If a dual acquisition mode for the UV/Vis detector is selected in the method, the instrument status window for the detector shows only a single channel A until the run is started. On starting the run, both channel A and B are properly displayed in the Instrument Status window.

Temporary Solution:

n/a

Fix Information:

This will not be fixed due to technical difficulties of implementation. This is documented as a driver limitation in the User's Guide.

Keyword: 

One-line Description:

G3581A 490 Micro GC Windows 10 Compatibility

Problem:

As of A.04.08 and A.04.09, Windows 10 supported, the CDS_SupportedInstFirmware.pdf does not reflect compatibility for G3581A 490 Micro GC with Windows 10 64 bit. The Windows 10 reference is missing.

Temporary Solution:

n/a

Fix Information:

G3581A 490 Micro GC compatibility with Windows 10 64 bit tests passed for A.04.09. The 490 Micro GC PSP does also contain compatibility. Please verify documented supported firmware and drivers.

Keyword: 

One-line Description:

All Signals Are Named The Same in DA: By  The Instrument Name

Problem:

All detector signal traces are named SII1 in the Data Analysis. The signal names do not distinguish detectors.

Temporary Solution:

n/a

Fix Information:

This has been fixed in SII 1.1.
However, the fix breaks backwards compatibility in Data Analysis. See ReadMe document in the SubscribeNet package for SII 1.1 for details.

Keyword: 

One-line Description:

Take/Release Control Feature Does Not Work

Problem:

The Take/Release feature to gain exclusive access over an instrument does not work in this driver version. Clicking the Take/Release button does not have an effect. Also, direct control is always possible independently of the user permissions.

Temporary Solution:

There is no work around.

Fix Information:

Fixed in SII 1.1 with limitations: 
The direct control is now only possible for the instrument that is not taken via the "Instrument View" Instrument Status context menu. All other context menu options function as expected.

Keyword: 

One-line Description:

Entries in method audit trail are ambiguous

Problem:

In Method Audit Trail, the corresponding retention time is missing if changes are made in a table of a method. For example, in the gradient table, Method Audit Trail does not reflect to which row the changes refer.

Temporary Solution:

n/a

Fix Information:

This has been fixed in SII 1.1.

Keyword: 

One-line Description:

Missing scrollbar in Method Setup window

Problem:

Thermo Fisher SII v1.00 driver, Thermo Trace GC, OpenLab CDS 2.5
Detector tab in Method Setup window is missing a scrollbar and it prevents the user from accessing the bottom part of the screen. 

Temporary Solution:

n/a

Fix Information:

This has been fixed in SII 1.1.

Keyword: 

One-line Description:

SII: No 3D Signals Available for FLD

Problem:

No 3D signals are provided for FLD detector in Data Acquisition even though the method allows to select 3D data collection.

Temporary Solution:

None.

Fix Information:

To be addressed in the future revisions of SII driver.

Keyword: 

One-line Description:

SII: Inverse Gradient Feature Not Supported For Vanquish Instruments

Problem:

The Inverse Gradient feature is currently not available for Vanquish Instruments. However, it is supported by Chromeleon CDS. Online Help of OpenLab CDS mentions this feature as supported.

Temporary Solution:

None

Fix Information:

This is fixed in Thermo Fisher SII Control 1.4.

Keyword: 

One-line Description:

SII: Instrument Activity Log Mixes Entries of Several Instruments

Problem:

Launching and operating two SII instruments at the same time can lead to an Instrument Activity Log which also contains some entries from the wrong instrument.

Temporary Solution:

None

Fix Information:

The activity log entries created by the utility drivers RS232 Input Port and Remote Inject Driver now appear in the appropriate Activity Log. However,
some Activity Log entries created during instrument configuration cannot be addressed and hence left unfixed.

Keyword: 

One-line Description:

Perkin Elmer LC300: "No injection/instrument Blank" Injection Source Not Supported

Problem:

Injection source "No injection/instrument Blank" is not supported with Perkin Elmer LC 300 system.

Temporary Solution:

A possible workaround to perform an instrument blank run is to run the sample with the LC 300 Autosampler as the injection source but use 0 for the injection volume.

Fix Information:

To be considered in the future revisions of the driver.

Keyword: 

One-line Description:

PE LC300: Uploading Method From Instrument Does Not Retrieve Pump Time Program

Problem:

When a method is uploaded from the instrument, only the initial conditions of the LC 300 pump are retrieved, not the entire pump time program (if any).

Temporary Solution:

Manually enter the desired pump program after the initial method creation from current instrument settings.

Fix Information:

To be considered for the future revisions of the driver.

Keyword: 

One-line Description:

Channel information is incorrect from Web Browser

Problem:

Check Channel information from web browser, the wording BF2D should be 'backflush to detector', not 'backflush to vent installed'.

Temporary Solution:

n/a

Fix Information:

Fixed in 2.3.6

Keyword: 

One-line Description:

Status always display "injecting" even instrument is idle

Problem:

Configure 990 Micro GC, create a method, then single run. But run can not stop even running is completed though Web Browser.

Temporary Solution:

n/a

Fix Information:

Fixed in 2.3.6

Keyword: 

One-line Description:

Software OpenLab CDS stays online even 990 Micro GC shut off already

Problem:

Software OpenLab CDS stays online even 990 Micro GC shut off already

Temporary Solution:

n/a

Fix Information:

2.6.8

Keyword: 

One-line Description:

 Help initial page showing folder content

Problem:

 Help initial page showing folder content

Temporary Solution:

n/a

Fix Information:

fixed and released in 2.5.5

Keyword: 

One-line Description:

Online Help initial page show folder content on Data System Configuration 

Problem:

Online Help initial page show folder content on Data System Configuration 

Temporary Solution:

n/a

Fix Information:

fixed in driver 2.5.5

Keyword: 

One-line Description:

The Help file of Driver in Configure Instrument need to be updated 

Problem:

The Help file of Driver in Configure Instrument need to be updated 

Temporary Solution:

n/a

Fix Information:

fixed in driver 2.5.5

Keyword: 

One-line Description:

The abnormal color for Gasifier status

Problem:

The abnormal color for Gasifier status

When switch off the transfer line heater and the Gasifier vaporizer heater, the color for Gasifier status 'OFF' is yellow. 

Temporary Solution:

n/a

Fix Information:

fixed in driver 2.5.5

Keyword: 

One-line Description:

The text of 'VICI stream position' need optimize.

Problem:

The text of 'VICI stream position' need optimize.

Temporary Solution:

n/a

Fix Information:

2.6.8

Keyword: 

One-line Description:

No error happen if load method has invalid initial pressure

Problem:

Load a method include invalid initial pressure, try to download or run, no error message.

Temporary Solution:

n/a

Fix Information:

fixed in driver 2.5.5

Keyword: 

One-line Description:

Hitachi ChromasterUltra RS: Selection Column by Column on Tray Display Not Supported

Problem:

For Hitachi CMU RS instrument, only row by row vial selection can be done in the Tray Display. Column by column vial selection pattern is not available.

Temporary Solution:

n/a

Fix Information:

To be addressed in the newer revision of the driver.

Keyword: 

One-line Description:

Hitachi ChromasterUltra RS: Selection in Tray A Display Also Reflects in Tray B of Microplates

Problem:

For Hitachi CMU RS instrument, when multiple racks are set, the vial selection made in the Tray display for the first rack is also reflected in the second rack. This does not affect data acquisition.

Temporary Solution:

N/A

Fix Information:

To be addressed in OpenLab CDS.

Keyword: 

One-line Description:

CTC PAL 3: Acquisition Crashes Upon Vial Fill Down in Sequence Table

Problem:

In OpenLab Acquisition, in the Sequence editor, when selecting the option "Fill down - increment" for the column "Vial", an error message appears.

Once the error message is closed, the OpenLab Acquisition window closes. The instrument remains connected to the AIC in case of a Client/Server.

Temporary Solution:

Do not use Vila fill down function until the fix is issued.

Fix Information:

In investigation by the driver team.

Keyword: 

One-line Description:

Thermo SII: Connection to the Instrument Failed in Method Editor

Problem:

SII 1.3: When creating a new method with a Thermo Ultimate instrument (possibly with other instruments, too), the system shows the error:
“Connection to the instrument "<Instrument_name>" on <PC_Name> failed”. 
Clicking "Retry" on the error message leads to the same result. Upon clicking "Cancel", the sampler method window is greyed out; starting a run typically fails or runs inconsistently.
The issue prevents normal method creation.

Temporary Solution:

None.

Fix Information:

The issue is being investigated by Thermo Fisher.

Keyword: 35900 Control

One-line Description:

Update to A.04.09 can break 35900E driver installation with CTC

Problem:

After Upgrade from Agilent OpenLAB CDS EZChrom Edition A.04.07 SR2 +CTC drivers  to A.04.09 , it happend that a 35900E can no more be configured as Generic instrument

Temporary Solution:

After Upgrade from Agilent OpenLAB CDS EZChrom Edition A.04.07 SR2 +CTC drivers  to A.04.09 , Repair  of Agilent A/D driver is required to configure a Generic instrument.

Fix Information:

n/a

Keyword: 35900 Control

One-line Description:

Preview run not working in A.04.09 & new RC.Net Driver functions differ

Problem:

The preview run feature is no longer available with the 35900E RC.net drivers.

There is a difference in 35900E behavior between OpenLab CDS EZChrom Edition A.04.08 and A.04.09, due to the native 35900E driver. The functional differences are between the native 35900E and new RC.Net 35900E drivers. 

A. OpenLAB CDS A.04.08 released build. (Agilent A/D :4.7.1.0 - Native) 

External: Run started immediately, but stops on “Pre-Run: Waiting for start” Manually hit start button on 35900 and data acquisition starts and the run completes. 

Manual: Run starts, “Start Data Acquisition” dialog displays. Use the PC mouse to press “Ok”. The acquisition starts and completes. 

None: Run starts immediately and completes without any error. 

B. OpenLAB CDS EZChrom Edition A.04.09 released build. (Agilent 35900 A/D Drivers: 2.3.53 - RC.Net)

External: Run starts immediately and complets without any error.

Manual: Run starts, “Start Data Acquisition” dialog displays. Use the PC mouse to press “Ok”. Acquisition stops on “Pre-Run: Waiting for start”.  Manually press the start button on 35900E. Data acquisition starts and the run completes.

None: Run starts immediately, but stops on “Pre-Run: Waiting for start”.
Manually press the start button on 35900. Data acquisition starts and completes.

Summary:
A.04.08: The run starts without pressing the start button. For 'External' trigger, the behavior is vice versa.

A.04.09: Using the RC.Net drivers requires pressing the start button for trigger 'None' and 'Manual'.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 35900 Control

One-line Description:

Install manual(M8201-90038) references installing Classic Drivers for 35900 and is not correct

Problem:

35900 is supported with the supplied drivers and does not require installing classic drivers.  Installing classic can lead to unpredictable issues

Temporary Solution:

N/A

Fix Information:

Do not install classic drivers. Firmware and Instrument guide updated.

Keyword: 3rd Party Drivers

One-line Description:

The running sequence can not be updated

Problem:

With the EZChrom Edition A.04.05 Hitachi driver for AAA L-8800/L-8900 the sequence lines cannot be edited like with other instruments. 

Temporary Solution:

n/a

Fix Information:

With the EZChrom Edition A.04.05 Hitachi driver for AAA L-8800/L-8900 the sequence lines cannot be edited as with other instruments. The sequence can be paused and resumed but the driver does not fully support editing. 

Keyword: 3rd Party Drivers

One-line Description:

Hitachi LCE and CM: Cannot Use Submit Button in Run Queue to Submit Runs

Problem:

Hitachi (LaChromElite and Chromaster) LC does not start a single run from a Run Queue window via "Submit" button in OpenLab EZChrom edition.

Temporary Solution:

Submitting via "Advanced" option in the Run queue works. 

Fix Information:

Under Investigation

Keyword: 3rd Party Drivers

One-line Description:

Hitachi LCE and CM: Cannot Use Submit Button in Run Queue to Submit Runs

Problem:

Hitachi (LaChromElite and Chromaster) LC does not start a single run from a Run Queue window via "Submit" button in OpenLab EZChrom edition.

Temporary Solution:

Submitting via "Advanced" option in the Run queue works. 

Fix Information:

Under Investigation

Keyword: 68xx Driver

One-line Description:

Vial Missing Error Message

Problem:

When the 6890 GC encounters a missing vial, the IALog displays Stop key pressed error #1 instead of "Missing Vial."

Temporary Solution:

None

Fix Information:

This is fixed in 68XX Driver version 6.21 which is included in C.01.05 OpenLAB ChemStation and A.04.05 OpenLAB EZChrom.

Keyword: 68xx Driver

One-line Description:

How to Change Column Dimensions

Problem:

Changing Column Dimensions requires being logged in as an administrator.

Temporary Solution:

Column dimensions are part of the GC Configuration and the end user must be logged on as an Administrator to change these parameters.

Fix Information:

This is fixed in GC Driver version 6.01/6.02 which is included in OpenLAB ChemStation C.01.01 and OpenLAB EZChrom A.04.01 and later.

Keyword: 68xx Driver

One-line Description:

If One Signal Needs to be Saved, it Must be Assigned as Signal 1

Problem:

If only one signal needs to be saved, you must assign it as signal 1.

Temporary Solution:

If only one signal needs to be saved, you must assign it as signal 1.

Fix Information:

Fixed in 68xx driver revision 6.11[008].  This driver is included in B.04.03 SP1 ChemStation and C.01.03 OpenLAB CDS.

Keyword: 68xx Driver

One-line Description:

In 68XX driver revision 5.02 - 6.11, it is not possible to Modify a Method During a Run to Extend the Run Time or Change the Oven Temp

Problem:

It is possible to the software edit parameters screen and change the oven hold time or oven temp and select OK.  The GC does not accept the updates.  The method in the software is changed to the new values; the GC ignores all.

Temporary Solution:

n/a

Fix Information:

68XX Driver 6.11 is included in B.04.03 SP1, OpenLAB ChemStation C.01.04 and OpenLAB EZChrom A.04.04.

Keyword: 68xx Driver

One-line Description:

Info in Edit instrument parameters\Columns is incomplete

Problem:

Edit instrument parameters; columns

Applies to GC’s: 7890A, 6890N, 6850A

The window displayed is incomplete; it shows the column type and flow/pressure parameters, but does not give the length, ID or film thickness.  These are critical parameters, and should be displayed just as they were in the previous ChemStation revisions.  To find these parameters, the user now has to look on the configuration window.

Temporary Solution:

n/a

Fix Information:

Fixed in 68xx driver revision 6.11[008].  This driver is included with OpenLAB ChemStation C.01.03 and OpenLAB EZChrom A.04.03.

Keyword: 68xx Driver

One-line Description:

Ignore missing vial option is not present in GC

Problem:

Run a sequence with 11 runs and the 11th vial is missing.  The sequence aborts and SSIZip file was not uploaded to ECM as the 11th vial was missing.

The ignore missing vial option is not present in GC.

Temporary Solution:

n/a

Fix Information:

This is fixed in GC Driver version 6.21, which is included with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

Instrument Setup graph has incorrect column legend

Problem:

In the 6890, the legend for the Instrument Setup graph says Column 2, irrespective of which column is highlighted.  The graph is correct, it is just the legend that is wrong.

Temporary Solution:

n/a

Fix Information:

This has been fixed in 68XX Driver version 6.21, which is included with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

ALS errors abort sequence; no Retry/Abort dialog box option offered with 68xx RC.NET Driver

Problem:

6890A RC.NET driver with ALS. 

If an ALS error occurs such as a Vial not found event, there is no dialog box option presented to Retry/Abort.  The sequence simply aborts.

Temporary Solution:

n/a

Fix Information:

This is fixed in GC Driver version 6.21, which is available with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

In 68XX Driver Version 5.02, it is not Possible to Start the 6890 RC.NET from the Front Panel Start Key

Problem:

In 68XX Driver Version 5.02, it is not possible to start the 6890 RC.NET from the front panel Start key.  Software configuration is Injection source = manual.  6890 is READY, press start and get error message "ERROR Start Key disabled".

Temporary Solution:

The workaround is for the user to start the run from the "run control" then "run Method" in the Chemstation software and then press start at the GC.

Fix Information:

Fixed in driver revision 6.10.  This driver is included with B.04.03 DSP1 ChemStation.  It is also included with OpenLAB ChemStation C.01.02 and OpenLAB EZChrom A.04.02.

Keyword: 68xx Driver

One-line Description:

CIS4 inlet is not recognized with 6890 GC RC.NET

Problem:

CIS4 inlet is not recognized with 6890 GC RC.NET

Temporary Solution:

n/a

Fix Information:

This is fixed in GC Driver version 6.21, which is available with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

Only Fast Plunger Speed is available for PTV Solvent Vent multiple injections

Problem:

The fast plunger speed is only available when using multiple PTV Solvent Vent injections.  Most users of multiple PTV Solvent Vent injections need to use Slow or Variable plunger speed, not Fast.

Temporary Solution:

n/a

Fix Information:

Fixed in driver revision 6.10.  This driver is included with B.04.03 DSP1 ChemStation and OpenLAB C.01.02 ChemStation and OpenLAB A.04.02 EZChrom.

Keyword: 68xx Driver

One-line Description:

Incorrect injection volume shown in method report if PTV solvent vent is used

Problem:

6850 with a PTV inlet

The method specifies PTV solvent vent mode with 3 injections, ten seconds apart.  The method volume is 5 µL.  Specify the method to use method volume for three injections.  Each injection is 5 µL.  However the report shows the injection volume as 1 µL.  This is incorrect.  The report should show the injection volume as either 5 µL or 5 µL x 3, or 15 µL.

Temporary Solution:

n/a

Fix Information:

Fixed in software driver 6.10 [023].  This fix is included in B.04.03 DSP1 and later versions of ChemStation.  It is included in OpenLAB ChemStation C.01.02 and OpenLAB EZChrom A.04.02 and later.

Keyword: 68xx Driver

One-line Description:

68xx Method Download Times Out

Problem:

Connect to 6890N GC.

Within seconds of successfully opening an online session, logbook logs the following simultaneously with the loading of the method.

'Logbook      Welcome to ChemStation                         12:17:12 06/28/10
   0 1da6 4c28cb1f    0
6890       1 Timed out waiting for method download to fin>  12:17:35 06/28/10
   0 1da6 4c28cb1f    0
6890       1 ish.                                           12:17:35 06/28/10
7da 41e0 4c28cb1f    0
Method       Loading Method LCV_GCCONTROL.M                 12:17:35 06/28/10'

Temporary Solution:

n/a

Fix Information:

Fixed in GC Driver revision 6.10 [027].  This driver version is included in B.04.03 DSP1 ChemStation and C.01.02 OpenLAB ChemStation and A.04.02 OpenLAB EZChrom.

Keyword: 68xx Driver

One-line Description:

"Method modified after loading" occurs when running a sequence (6890 RC.NET)

Problem:

The "Method modified after loading" flag occurs after lauching the sequence.

Started the sequence from the ChemStation software.  The method modification status indicates that the method has changed when it was not changed and the report will indicate 'modified after loading'.

The GC had a calibrated capillary column that was changed to a packed column.  When using this method that now has a packed column, the GC reports an error in the length parameter, and that is causing the method download not to reset the 'modified after loading' flag.

Temporary Solution:

There is a workaround: bring Method into MethodEdit UI, and "reconfigure" column (Packed to Packed would be OK) to get new structure.

Fix Information:

Fixed in GC Driver revision 6.10 [027].  This driver is included in B.04.03 DSP1 ChemStation and OpenLAB C.01.02 ChemStation and OpenLAB A.04.02 EZChrom.

Note, this fix will only apply to new methods, not to current methods.

Keyword: 68xx Driver

One-line Description:

Sequence continues while GC temperature is not ready

Problem:

When running a sequence where consecutive runs use the same method using the ALS on a data system containing 6890 driver version 6.10.027 or earlier, the data system may proceed to start a new run before the GC has equilibrated after the conclusion of the previous run.  This is more likely if the method contains a post run period of sufficient length that the GC equilibrates to the post-run conditions and the data system has completed data analysis well before the end of the post-run period.

This could result in a (retention time) RT shift.

Temporary Solution:

n/a

Fix Information:

Patch available for RC.NET GC driver revision 6.10 [027] for B.04.03 DSP1 [54].

Fixed beginning in: B.04.03 SP1 [87] and OpenLAB C.01.03 [37].

Keyword: 68xx Driver

One-line Description:

A Method Can be Created Which Will Not Download to the Instrument and the Sequence Does Not Run

Problem:

Method download fails, sequence aborts after start; no injection made

Error reported in logbook:
Attempt to download method to GC failed.

The Data System will not allow the run to continue when the method download has failed.

Temporary Solution:

n/a

Fix Information:

This fix is in the 68xx driver version 6.10.032 and 6.11.001.  

This fix is included in B.04.03 SP1 and OpenLAB ChemStation C.01.03 and OpenLAB EZChrom A.04.03.

Keyword: 68xx Driver

One-line Description:

GC Back Injector Not Present in Edit Method Screen

Problem:

After successfully running a sequence with a back method, another back method is loaded. The back injector is not present in the edit method screen.

Temporary Solution:

Change a parameter at the GC keyboard and click "upload from instrument" in the edit method screen. The back injector will show in the edit method screen.

Fix Information:

This has been fixed in 68XX Driver version 6.21, which is included with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

Validation failed shown on left corner of Resolve Method screen

Problem:

Load a method which was developed for both detectors and has the front detector signal chosen under signals tab.
Load this method on a GC with no front detector - method resolution. 

Changes made to the detector signal tab are not detected, tab remains yellow (invalid).

Temporary Solution:

Click on a different tab and modify the value of any field to a valid value or click on the configuration tab and then click away. Change the signals tab to a valid value or turn it off to resolve the method.

Fix Information:

This has been fixed in 68XX Driver version 6.21, which is included with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

Injector Panels in GC Edit Method Show as Uninstalled When an Injector is Installed.

Problem:

The front injector was unplugged. Close software, plug injector in, restart software.  Method Configuration/ALS panel and Injector panel both say: Front Injector Not Installed. The GC shows that it is installed.  Software inlet and injection parameters panel show that it is installed as well.

Temporary Solution:

n/a

Fix Information:

This has been fixed in 68XX Driver version 6.21, which is included with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

Plunger Speed is Not Saved with 6850 GC Methods

Problem:

Plunger speed parameters are not saved in methods.

Temporary Solution:

n/a

Fix Information:

Fixed in driver revision 6.11[002].  This fix is included in B.04.03 SP1 ChemStation, C.01.03 OpenLAB ChemStation and A.04.03 OpenLAB EZChrom.

Keyword: 68xx Driver

One-line Description:

Opening the GC method parameters to only look (no change made) and selecting OK to close stops the sequence or single run

Problem:

During a run, the GC method parameters are opened via the instrument diagram icon.  Select OK after looking at the oven parameter to close the screen.  The sequence or single run will just stop and the method is dirty.  See Log File for error message.

Log File:
  67 41e2 4e69f8b3    0
Method       Method started                                 07:29:55 09/09/11
  67 41e2 4e69f8b4    0
Method       Instrument running sample Vial 1 (front)       07:29:56 09/09/11
  67 41e2 4e69f8b4    0
Method       Instrument running sample Vial 2 (back)        07:29:56 09/09/11
   0 1da5 4e69f91a    0
6890       1 Attempt to download method to GC failed.       07:31:38 09/09/11
  67 41e2 4e69f91a    0
Method       Instrument Error - Method/Sequence stopped     07:31:38 09/09/11
  67 41e2 4e69f91a    0
Method       Method aborted                                 07:31:38 09/09/11

Temporary Solution:

Click the Cancel button rather than the OK button if the intent was to check the values of some of the instrument setpoints.  This would not interfere with any run which is in progress.

Fix Information:

Fixed in 68xx driver revision 6.11[008].  This is included in B.04.03 SP1 and OpenLAB ChemStation C.01.03 and OpenLAB EZChrom A.04.03.

Keyword: 68xx Driver

One-line Description:

Method Contents Report Displays the Incorrect Configuration of Front and Back Detectors for 6890 GC

Problem:

The report displays the incorrect configuration. With signal-1 selected as the back detector and integration events for back detector. The method contents report displays the integration events for the front detector and the remaining paramaters are for the back detector are configured to the front detector.

Temporary Solution:

n/a

Fix Information:

Fixed in 68xx driver revision 6.11[003].  This fix is included in B.04.03 SP1 ChemStation, C.01.03 OpenLAB ChemStation and A.04.03 OpenLAB EZChrom and later.

Keyword: 68xx Driver

One-line Description:

Cannot Run a Packed GC Column with a 6890

Problem:

Method download fails, sequence aborts after start when trying to run a 6890 with a packed column.  
  
Error reported in logbook:
Attempt to download method to GC failed.

The Data System will not allow the run to continue when the method download has failed.

Temporary Solution:

This can be run by setting the column as a capillary column but that changes the chromatography.

Fix Information:

Fixed in driver revision 6.10[032] and 6.11[001].

This fix is included with B.04.03 SP1 GC ChemStation, C.01.03 OpenLAB ChemStation and A.04.03 OpenLAB EZChrom

Keyword: 68xx Driver

One-line Description:

Pulsed Split/Splitless Injection Does Not Wait For Ready on a 6890.

Problem:

The GC does not wait for the inlet pressure to increase to and stabilize at the pulsed pressure before injection and data acquisition. The GC starts and injects sample at the same time, then starts data acquisition and increase of inlet pressure to pulsed pressure.

Temporary Solution:

If the 6890 is operated from the GC keyboard, the GC has the expected result.

Fix Information:

Fixed in 68xx driver revision 6.11[007].

This fix is included with B.04.03 SP1 ChemStation, OpenLAB ChemStation C.01.03 and OpenLAB EZChrom A.04.03

Keyword: 68xx Driver

One-line Description:

In 68XX GC Driver Version 6.01, 2 Injections are Made When Using the PTV

Problem:

Set up the injector to make 1 ul injection x 1. The number of injections will revert to 2 even if the user enters 1.

Temporary Solution:

n/a

Fix Information:

This is fixed in driver revision 6.10 [27]  which is included in B.04.03 DSP1 [54] GC ChemStation, C.01.02 OpenLAB ChemStation and A.04.02 OpenLAB EZChrom.

Keyword: 68xx Driver

One-line Description:

Vial left in gripper; no message shown to alert user about the problem

Problem:

After a stop, if there is a vial in the gripper it is not returned to its original location, it is kept in the gripper until the start of a new run. In the interim, if a new vial is placed in the open location, during the next run the system runs into an error because the gripper wants to return the vial to its original location which is now occupied.

Temporary Solution:

n/a

Fix Information:

This is fixed in GC Driver version 6.21, which is available with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

6850 vial numbers are not consistent with standard numbering system.

Problem:

A 6850 with a G2613A tower and a three vial turret will accept only single digit vial locations, ie., 1, 2, 3 instead of 101, 102, 103. Attempts to enter the correct vial number generates an error message "The vial 101 is not allowed with the current device configuration."

The also occurs when entering correct vial locations in a sequence table.

Temporary Solution:

n/a

Fix Information:

Fixedi n 68XX driver revision 6.11.  This driver is included with B.04.03 SP1 ChemStation, OpenLAB C.01.03 OpenLAB ChemStation and A.04.03 OpenLAB EZChrom.

Keyword: 68xx Driver

One-line Description:

Method Resolution Changes Oven Temperature Program

Problem:

Load a method from a 6890 GC with a fast oven on a 6890 GC with different hardware and a normal oven. Method resolution occurs. The oven temperature program from the fast oven GC has not been loaded on the normal oven GC.

Temporary Solution:

n/a

Fix Information:

Fixed in 68xx driver revision 6.11[002].  Fix is included in B.04.03 SP1 ChemStation, OpenLAB ChemStation C.01.03 and OpenLAB EZChrom A.04.03.

Keyword: 68xx Driver

One-line Description:

Column info is missing with 6890

Problem:

The column specified as being used is missing information: description, Manufacturer and Model Number.

Temporary Solution:

n/a

Fix Information:

Fixed in 68xx driver revision 6.11[005].

This fix is included in B.04.03 SP1 GC ChemStation, C.01.03 OpenLAB ChemStation and A.04.03 OpenLAB EZChrom.

Keyword: 68xx Driver

One-line Description:

Method Modification Flag is Set after Edit Method: Occurs on first connection or after upload from GC.

Problem:

1. First Connection to an online GC and save the method OR connect to an instrument and save the method, open method editor, click on ‘Upload from instrument’. Click ‘Ok’.
3. Click ‘Edit entire Method’, go on clicking ‘Ok’ without making any change.
4. Method is dirty at the end.

This only occurs on 6850 GCs with G4513A injectors.

Temporary Solution:

Save the method as a new name after initial connection or subsequent method upload.

Fix Information:

Fixed in 68xx driver revision 6.11[008].  This is included in B.04.03 SP1 and OpenLAB ChemStation C.01.03 and OpenLAB EZChrom A.04.03.

Keyword: 68xx Driver

One-line Description:

Method Ddownload Failure Occurs Due to Column Calibration Limits

Problem:

A valid column calibrated using calculate diameter function will result in a method download failure if the change from the original diameter is more than 20 microns. 

This occurs after OKing method changes that are downloaded, and will occur even if the column values are valid dimensions.

Temporary Solution:

n/a

Fix Information:

This is fixed in 68XX GC Driver Version 6.21, which is included with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

Instrument actual value for COC inlet does not display correctly

Problem:

6890N GC with COC inlet connected to FID. The COC inlet pressure setpoint reflects the correct pressure set for the column, however the instrument actual value (blue text) in the setup method screen is displayed as 0.0.

Temporary Solution:

Enable setup actuals (inlet) in the setup method screen, the inlet pressure is properly displayed.

Fix Information:

Fixed in 68xx driver revision 6.11[018].  This driver is included in B.04.03 SP1 ChemStation and OpenLAB ChemStation C.01.03 and OpenLAB EZChrom A.04.03.

Keyword: 68xx Driver

One-line Description:

Instrument actual value for anode purge flow on an ECD does not display correctly

Problem:

The ECD anode purge flow setpoint reflects the correct value, however the instrument actual value (blue text) in the setup method screen is displayed as 0.0.

Temporary Solution:

Enable setup actuals in the setup method screen, the actual anode purge flow displayed properly.

Fix Information:

Fixed in 68xx driver revision 6.11[018].  This driver is included in B.04.03 SP1 ChemStation and OpenLAB ChemStation C.01.03 and OpenLAB EZChrom A.04.03.

Keyword: 68xx Driver

One-line Description:

6850 Support of Column Compensation

Problem:

The 6850 GC does not support column compensation from the software. This is only able to be done with the G2629A handheld controller which is now obsolete.

Temporary Solution:

n/a

Fix Information:

This is fixed in 68XX GC Driver Version 6.21, which is included with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

Data Files do not Contain the Correct Signals if the Front Inlet is Connected to Back Detector

Problem:

Data files do not contain the correct signals if front inlet is connected to back detector

Temporary Solution:

n/a

Fix Information:

This is fixed in GC Driver version 6.21, which is available with OpenLAB ChemStation C.01.05 and OpenLAB EZChrom A.04.05.

Keyword: 68xx Driver

One-line Description:

The Oven Ramp table does not display correctly in IR with Acquisition method selected.

Problem:

When you specify an Intellignet Report with Method Info report added to the  Sample Summary report to get the Acquisition method it is formatted incorrectly..

Temporary Solution:

n/a

Fix Information:

The rows in tables now have the same names and IDs so that the data system can organize them into a table. Fixed in revision 6.25 (GC Driver revision A.02.05).

Keyword: 68xx Driver

One-line Description:

6890 PTV Inlet not recognizable in OpenLAB EZChrom

Problem:

The Extracted configuration shows PTV back inlet and AIB Back Detector. Launching the instrument offline shows the column connected to the Back Inlet and the Back Detector.The Module Configuration Lists the PTV Back Inlet with Blank Back Detector, however the Back Inlet is seen as  Unrecognized inlet type.

Temporary Solution:

n/a

Fix Information:

The code wasn't checking for the right inlet type code for a PTV mounted in the back. Fixed in revision 6.25

Keyword: 68xx Driver

One-line Description:

Multiple errors when the 6890 doesn't have any inlets

Problem:

The OpenLAB CDS ChemStation gives errors when the 6890 doesn't have inlets installed and both inlets are configured as none on the 6890 GC.

Temporary Solution:

n/a

Fix Information:

The error was occurring in the code which set up the possible inlet connections for columns. Fixed in revision 6.25

Keyword: 68xx Driver

One-line Description:

Sequence table Inj Vol Override goes to wrong stops for 6890/7683: C.01.05, A.04.05, C.01.06, A.04.06

Problem:

If an Injection volume is entered into the Sequence which overrides the method injection volume setting the injector goes to the wrong stops for a 6890 with a 7683 ALS. The injection volume will be incorrect for versions C.01.05, A.04.05, C.01.06, A.04.06 of the software

Temporary Solution:

n/a

Fix Information:

Fixed in 68xx Driver Version 6.23 [011].

Keyword: 68xx Driver

One-line Description:

Often get two or more ChemMain.exe's running following shutdown of Control Panel or online session.

Problem:

Run Task manager always on top.  With no ChemMain.exe's running, open a 6890 online session. Close session and the ChemMain.exe does NOT go away.

Temporary Solution:

n/a

Fix Information:

Fixed in A.02.05

Keyword: 68xx Driver

One-line Description:

6890N with 7693 barcode scanning checksum mismatch does not return vial to tray and skips a vial.

Problem:

There was a timeout in the driver; if the reading of the bar code was not complete by the time that the timer timed out, the driver would declare that the reading had terminated.  This was misleading the data system into advancing to the next vial.  The time required to finish reading the bar code or declare that the attempt had finished is indeterminate.  If the tray is parked, the system will sit there waiting to move until the tray is unparked.  The timeout was removed from the code.

Temporary Solution:

n/a

Fix Information:

Fixed in A.03.01