Software Status Bulletin
OpenLAB CDS M84xx
Known Problem Report as of Dec 23 2024 4:00AM
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
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#:150
Setting a Hold time of 0.0 does not work correctly with GC6890
KPR#:156
GC Driver and OpenLAB CDS 2.2 Version Number clarification.
KPR#:157
OpenLAB 2.1: Unable to download syringe change to GC
KPR#:159
6890 online help has the bad strings in Injector page.
KPR#:308
Method printout missing column parameters: flow or pressure, setpoint On, (Initial), and post run
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#: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#: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#:360
Method Editor for PP inlet & Packed Column incorrectly allows both flow and pressure setpoints to be entered
KPR#:362
GC driver is missing for the current build installed while upgrading from 2.1 to 2.2.
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#:373
Method Resolution Does not take into account default column temperature limits.
KPR#:376
The Local User Interface(LUI) on the Intuvo 9000 GC shows long name for connected data system.
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#:385
RTL for OpenLAB CDS: Calibration Runs dialog shows no chromatogram or compound table for loaded data or Results from calibration runs
KPR#:386
RTL Wizard crashes when run with OpenLAB 2.2 and mandatory sample is selected.
KPR#:387
Acquisition crashes when user clicks on RTL Import/RTL wizard
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#:432
Defect: there is an empty tooltip on the button "maintenance" in the "control" ribbon in ACQ.
KPR#:435
GC Method Resolution results in “Object Reference” error message and occasional crash
KPR#:438
When attempting to save the method in OpenLab CDS 2.2, a dialog box appears with the title "[debug] Surprise Dirty!".
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#:597
68xx: Chromatogram for channel randomly offset, shifted
KPR#:44589
"Autoscale Y-axis" toggle does not work in Online Signal window
KPR#:44591
Sequence editing and updating may get stuck at wrong state due to timing issue
KPR#:57764
Auto config twice in succession cause system hang
KPR#:68592
Agilent OpenLAB Instrument Service would take longer than 2 mins to go to running state
KPR#:70704
User cannot import an English CSV file in European OS
KPR#:72004
"Injection time" of aborted injections are given Epoch Time of 1600-12-31 followed by time and UTC
KPR#:72639
From an OpenLAB CDS 2.0 client, Viewing currently running sequence on any instruments configured on an OpenLAB CDS 2.1 AIC is not possible
KPR#:72656
When using Date and Time as token, the resolved values for Single Sample Analysis and Sequence are not consistent
KPR#:73666
Exception is thrown when result filename starts with spaces
KPR#:73942
Instrument Modules section in report does not list the SS420x or its properties
KPR#:75469
TIC signal is not displaying in Online Signal window during data acquistion if none is selected in GC's signal setting
KPR#:80705
EZChrom methods fail to import in OpenLAB CDS 2.1
KPR#:85551
Network issues with DHCP may cause unexpected behavior on a Workstation installation
KPR#:85599
GC/MS sequence aborts when Server is disconnected
KPR#:85603
Connection problems with hardware could put the instrument in indeterminate state
KPR#:85608
Submitted or Validating run items will get aborted if connection to OpenLAB Server is lost
KPR#:85619
In case of overlap injections, "Stop sequence after current run completes" aborts the current run ONLY and discards the already prepared sample
KPR#:85631
After performing 'Review Completed Injections", the subsequent injections within the same sequence will have the same injection time
KPR#:89033
Cannot re-launch LC instrument after closing acquisition client
KPR#:98690
35900E module list is truncated when printing to XPS in landscape orientation
KPR#:101690
Replicate injections may not run when editing current running sequence more than once
KPR#:119595
Cannot print sequence from sequence layout
KPR#:120121
Instrument status goes Idle during sequence more than 250 runs
KPR#:123245
Printing method in Word format shows incorrect total page count in footer
KPR#:143348
TIC signal is not displaying in Online Signal window during data acquistion if none is selected in GC's signal setting
KPR#:163990
Acquisition Client does not get failover notification when AIC switches to failover
KPR#:181523
Instrument client crashes upon opening a dual GC sequence file longer than 155 lines
KPR#:182676
Need warning message that mismatched labels in sequence will cause reports not to be generated
KPR#:183680
Sequence is stuck in "Reporting" when processing method calls for hardcopy report but default printer is not configured
KPR#:184578
Acquisition crashes on the second click on "Print" to display GC Headspace method parameters
KPR#:186458
Cannot take snapshot of current running injection after closing/opening same client or opening new client
KPR#:197007
Session connection to instrument controller is lost when ELSD is left in standby mode
KPR#:198003
Detectors do not perform auto-balance when no injection/instrument blank is selected as injection source
KPR#:215920
The current running/pending sequences might be interruptted due to unstable network
KPR#:217569
In OpenLab CDS v2.x, the raw data (.dx) acquired on Agilent LC modules in general are larger in size
KPR#:219860
Sequence creation template not working for back injector on GCs
KPR#:230280
If default printer is not a physical printer, RX files may to be missing in result sets
KPR#:242941
Possible network printing issue after upgrade to CDS 2.4
KPR#:244275
RX files missing in result sets
KPR#:269040
There is no indication for user to start a manual injection when the injection source is specified "External"
KPR#:272160
Cannot "Submit Sequence File" from API due to case sensitive in compound custom parameter name
KPR#:281641
Acquisition crashes with error "System.Argument.Exception: name already exists" when selecting processing method
KPR#:282199
Sample or compound custom parameter values with "," digit separator not handled properly
KPR#:283230
Cannot "Submit Sequence File" from API when optional sample custom parameter is missing
KPR#:298529
Acquisition client crashes upon launching Hitachi instrument
KPR#:303675
The configured instrument modules in acquisition method report may show in alphabetical order
KPR#:305373
Print icon in Acquisition is greyed out
KPR#:314007
"Unable to connect to instrument server" after OpenLab CDS client is locked
KPR#:314956
User sporadically fails to connect to instruments when using Sample Scheduler or Walkup
KPR#:318941
RX file generation fails sporadically when saving results
KPR#:343559
Injection audit trail records the changed objects of an acqusition method not the corresponding values when the acqusition method can be automatically resolved upon sequence submission
KPR#:346715
Instrument goes offline upon opening incompatible sample prep method
KPR#:353246
Failed to upload partially acquired result sets due to system failure
KPR#:367304
MS instrument cannot run sequence after upgrading to OpenLab CDS 2.3 Update 08
KPR#:373129
User specified result path is not saved with the user settings
KPR#:377012
Performing snapshot or review completed injections may cause current running single sample analysis or sequence to terminate due to unstable network
KPR#:378842
Stopping runs from 6890 GC's key pad does not get recorded in activity log and injection audit trail
KPR#:387598
Manual editing of column tags used in G1316A/B/C is not supported
KPR#:387714
Chromatogram is shifted, offset in 6890
KPR#:391994
A sequence audit trail entry "Sequence automatically updated: Removed duplicated entry ids" is observed on an upgraded system
KPR#:393545
Changing instrument setpoints is not possible from instrument status dashboard without the proper permissions
KPR#:401312
Instrument Client may close unexpectedly after repeatedly clicking on Take/Release Control of the instrument
KPR#:404386
Shimadzu GC stays connected after closing connection
KPR#:409420
Acquisition method UI is not displaying for Agilent GC with PAL3 if not configured properly
KPR#:414614
Session connection has been lost
KPR#:414957
"Failed to set fraction start info. Operation is not valid due to the current state of the object."
KPR#:416240
Sequence creation template (.stx) can be overwritten in Portuguese system
KPR#:417310
The current data acquisition may get interrupted after performing a snapshot
KPR#:421099
OpenLab CDS v2.5 Russian system crashes when editing sample custom field
KPR#:422891
Sample Scheduler doesn't offer dual External injection when GC is configured with dual gas sampling valves only
KPR#:426647
Part of the configuration UI on some instruments is cut off due to resizing issue
KPR#:427117
Partially acquired result set may not be available due to AIC power failure
KPR#:427662
Starting acquisition with 7697A headspace causes XML error entry in Activity log
KPR#:431478
Last lines of dual sequence gets unchecked after submission
KPR#:450186
Instrument stays "not connect" after successfully launching instrument client
KPR#:451902
Run queue layout is not saved and always back to default settings
KPR#:461280
Current running dual sequence table locks pending lines from editing as run progresses
KPR#:474496
Error occurs upon launching instrument
KPR#:480593
After changing a vial in a running sequence, the old vial is injected
KPR#:485102
Sequence may get aborted with error "same file is being used from different folders"
KPR#:487578
Editing a running sequence on Agilent GC with Headspace may fail
KPR#:488808
Microsoft.NET framework error when displaying TIC Scan signal on Online Signals plot
KPR#:496334
Acquisition client stuck at loading with an empty acquisition method UI
KPR#:496468
Cannot edit current running sequence, review completed injections or perform snapshot sporadically from instrument client
KPR#:510068
Not able to view current running sequence when result name exceeds 28 double byte characters
KPR#:536263
The injection time is Window's epoch time if there is no injection performed.
KPR#:536337
Instrument client may close unexpectedly with errors upon maximizing its window
KPR#:538303
Instrument client may close unexpectedly upon clicking "Release" button
KPR#:585417
Not able to load result set due to a failure editing/updating running sequence
KPR#:586513
Instrument client sporadically becomes non-responsive upon starting snapshot on current running sample
KPR#:589714
Sporadically an unexpected error occurs upon relaunching Hitachi LC
KPR#:590549
Instrument client crashes upon unlocking a locked manual resolution screen by a different user
KPR#:594679
Result set cannot be loaded in Data Analysis due to duplicate data files
KPR#:603515
Result set cannot be loaded for reprocessing due to corrupted data
KPR#:610537
Diagnostic data sometimes not available for reporting
KPR#:616603
Error occurs upon clicking on "Edit Signature Settings" of a project
KPR#:619757
Running sequence gets interrupted by unexpected exception during editing
KPR#:623774
"Lost Connection" message pops up upon launching instrument with no designated storage path
KPR#:625464
Sample Scheduler not able to get the proper sequence line information when sequence is aborted due to method validation error
KPR#:626689
Not able to edit a running sequence due to a timing issue when switching between "View Running Sequence" and "Editing" mode
KPR#:627087
The version of Apache HTTP Server is out of date
KPR#:627390
Unexpected error occurs upon closing manual resolution UI window
KPR#:635218
"Agilent Test Services" and "Agilent Test Services Central Management" services are not started after a server restart
KPR#:639409
Run gets interrupted when run queue being re-ordered
KPR#:647289
Ad Hoc mode is in general not supported for Agilent LC or GC with a 3rd party module
KPR#:652699
Sequence run gets interrupted due to an unexpected error
KPR#:653140
Incomplete injection list after a result set loaded in Data Analysis
KPR#:662162
Current running sequence is stuck in "In Review" mode
KPR#:667955
Runs submitted using Sample Scheduler gets interrupted
KPR#:668002
"Unsaved changes" message box prompts upon closing Hitachi LC
KPR#:683209
FLD signal not integrated by delay calibration
KPR#:688272
Error occurs when PC name is changed and then reverted back to the original name
KPR#:692104
Online Signal sporadically disappears
KPR#:698266
Reports cannot be generated at the designated folder (Windows file system) when using Sample Name or Data File Name with a trailing space as subdirectory.
KPR#:703592
Acquisition or Data Analysis window closes unexpectedly upon unlocking
KPR#:718091
A suspended sequence run with a wait line may resume and complete data acquisition without waiting
KPR#:722995
Instrument client times out intermittently when browsing open an acquisition method in a heavily loaded folder
KPR#:725215
Sequence name token used in data file name is not properly resolved
KPR#:726036
A sequence run stays in "In Review" state and cannot proceed to completion
KPR#:728775
Empty data files may be stored when a sequence run is aborted due to a hardware error
KPR#:730405
Sequence is stuck in pending state on PerkinElmer GC
KPR#:732076
Some columns defined in a sequence CSV file (in Portuguese) cannot be imported
KPR#:732078
Front sample type defined in a dual sequence CSV file is applied to all back samples upon importing
KPR#:736250
Fraction Collection does not happen per the defined locations when sequence is run as Separate single injections
KPR#:737649
Sequence run stays in "Aborting" state forever
KPR#:738062
Sporadically the method UI window stays blank for more than 30 seconds after instrument has been launched
KPR#:738064
Instrument client crashes upon canceling out multiple method resolution windows
KPR#:741211
Communication error occurs while trying to reach Agilent.Scheduler.Agent
KPR#:753959
Sequence is in aborting endlessly due to method resolution
KPR#:760565
Cannot import "Injection Source" information in a CSV/TSV file into sequence table
KPR#:763591
Instrument shutdown on Agilent GC/HS system causes unrecoverable pause
KPR#:773167
Missing injections when a completed result set is loaded in Data Analysis
KPR#:774529
Acquisition method UI does not refresh to display the updated configuration settings on Agilent GC instruments
KPR#:781008
PE TurboMatrix HS with Agilent GC Cannot be Configured More Than Once
KPR#:781990
Bracketing mode specified in sequence table is reset back to "None" when the completed result set is loaded in Data Analysis
KPR#:786509
Sequence submitted from Sample Scheduler failed to run when fraction collection is disabled in the specified acquisition method.
KPR#:791399
Change in status of the GC not being properly broadcast to external interface.
KPR#:809132
No rx file is generated when submitting a sequence with a sample prep method which has a long name
KPR#:935393
A certain injection line is locked from being edited in a running sequence
KPR#:936041
Run queue stays in "Paused" state after the current acquiring sequence is aborted due to missing vials
KPR#:936076
Not able to select delay sensor for Delay Volume Calibration when two or more fraction collectors are present in the instrument configuration
KPR#:937168
"Failed to set resource properties for SQ" exception thrown when performing retrieve method from instrument by an SDK based application
KPR#:947599
Sequence can't be opened for editing
KPR#:953005
Microsoft .NET Framework unhandled exception occurs when viewing a currently running or pending sequence.
KPR#:954500
Wrong sample prep method is used for overlap injection
KPR#:958457
Online signals window shows red start line when a run is aborted due to a missing vial on Agilent GC
KPR#:960515
Submission time for runs submitted from GC plugins is not displayed in Run Queue
KPR#:960914
Bin files that contain LCMS signals are randomly missing from some injections in a completed sequence run
KPR#:961459
Acquisition method version is not displayed for some injections in report
KPR#:969144
Unhandled exception occurs upon launching instrument or viewing a running sequence
KPR#:988157
Result set loaded in Data Analysis is found missing injection(s)
KPR#:989142
"Failed to process injection" occurs due to invalid xml characters entered in sample description
KPR#:990425
LC/MS SQ instrument client crashes upon printing sequence report
KPR#:991150
Run Queue displays wrong sequence name when an untitled sequence run as separate single injections
KPR#:1026879
Cannot connect to instrument successfully
KPR#:1030169
Importing a sequence CSV file failed with error.
KPR#:1044117
Sequence run is stuck in aborting state
KPR#:1048903
AIC replication issue in mixed CDS / MassHunter systems
KPR#:1051436
LCMS SQ driver logs are no longer saved in AcqusitionServer-<ID>.log, AcquisitionClient-<ID>.log and AcquisitionAgente-<ID>.log in v2.8
KPR#:1057373
Missing activity records for injections that are aborted due to barcode mismatch
KPR#:1057750
Acquisition client closes when browsing to a method folder from a sequence.
KPR#:1063281
Signals from two instrument traces of VWD that are previously suppressed to collect data points in CDS v2.7 and earlier versions are saved in dx files in v2.8.
KPR#:1063452
Instrument connection lost if custom wellplate configured
KPR#:1063778
Failed to connect to the instrument upon launching an Agilent LC
KPR#:1067083
Some Thermo instruments cannot be configured
KPR#:1070357
WalkUp 4.3 stopping with not ready condition after every run with CDS v2.8
KPR#:1075412
Reports cannot be generated at the designated folder (Windows file system) when using Sample Name or Data File Name with a trailing space as subdirectory.
KPR#:1085098
Failed to create sequence when using Retention Time Locking with ECM 3.x
KPR#:1088274
The vial locations on a Hitachi instrument are not properly displayed from Sequence's Tray View UI
KPR#:1096666
GC Signal Delay is not displayed properly
KPR#:1098656
Readback from LC may contain tokens instead of values
KPR#:1101488
Run queue displays wrong method for wait line under certain conditions
KPR#:1115138
Online plots may be scaled incorrectly on the y-axis
KPR#:1116178
GCMS Tune Reports not being saved with the result set
KPR#:1118195
Copy/Paste from Excel to Sequence table is truncating or missing data
Keyword: Acquisition,Data Analysis
KPR#:174167
Acquisition setpoints for single injection not reflecting the parameters used
KPR#:940702
Roles and Privileges Report causes error
KPR#:244534
New users don't see data and projects in Content Manager
KPR#:376731
Not possible to delete project related files form the Content Management user interface.
KPR#:477707
No specific privilege is required to access the CM Admin console
KPR#:487437
Java JMX RMI vulnerability
KPR#:534773
Restore fail when the new server is on a different subnet
KPR#:539989
A new domain user can't create projects
KPR#:549030
Archive fails if a file with the same name has already been archived
KPR#:567527
Backups can fail if the available C disk storage space is too small
KPR#:567986
Backup aborts due to timeout error
KPR#:577035
Installation stalls at Agilent Distributed Transaction coordinator install step
KPR#:582137
Backup Utility fails if IP address is used for DB server connection
KPR#:588447
If one archive job fails, the others should continue
KPR#:588450
Archive jobs get stuck, requiring a cleanup
KPR#:588458
Archive job in a sub-folder should be removed when manually archiving a parent
KPR#:600186
Data files with names including semicolons (;) cannot be uploaded to Content Management
KPR#:663493
OpenLab ECM XT not affected by security issues in log4j-1.2.17
KPR#:687074
Customer IT scan identified vulnerability CVE-2021-4104
KPR#:694366
Script to update system passwords seems to update the wrong registry elements
KPR#:708407
Version mismatch in SVT for Data Collection Agent and Service
KPR#:714173
Analytics.json moved to OpenLab Platform and no longer listed in Diagnostics save files
KPR#:954003
Cannot resotre FB database
KPR#:954006
Rest API crashes with domain users in CP but removed from domain
KPR#:1044816
OpenLab Software Installation Verification Test fails with ECM backend
KPR#:1048901
The AGTOL.log file is missing from 2.7 systems
KPR#:1058057
Supporting OpenLab v2.8 in multi-domain environments where Clients/AICs are members of a different domain than the OpenLab Server/ECM XT server
Keyword: Administration,User Interface
KPR#:267323
Activity Log in OLCP does not record the Application name when login from the Web UI
KPR#:119673
Audit Trail shows "Unknown" user and "Manual Control" category when running method with "Acquire" option unchecked
KPR#:120285
Audit Trail shows "Unknown" user if you make changes to current running method
KPR#:171556
Audit trail shown “Unknown” in the Manual Control category for method changes in running sequence
KPR#:220418
Review button in Audit Trail is disabled for entry "Upgraded method from previous version"
KPR#:229036
Audit trail table in sequence report printed from instrument client is spanned in two rows for each entry
KPR#:288861
Reprocessing injection triggers log with different wording in audit trail and activity log
KPR#:303841
Reprocessing injection triggers log with different wording in audit trail and activity log
KPR#:303980
Injection time for imported ChemStation data is rounded down to the minute
KPR#:307681
Sequence/method loses its audit trail if it is saved with same name
KPR#:348093
User who last modified and saved the method appears in method audit trail upon resolving method resolution
KPR#:378080
E-Signature description not automatically updated for new created user
KPR#:435442
Processing method audit trail shows incorrect values after changing values in signals smoothing tab
KPR#:449320
No record in Audit Trail when disabled calibration points are re-enabled after reprocessing
KPR#:450949
The original user who created the sequence is listed in the sequence audit trail as the user who imported the sequence from a result set
KPR#:467098
Processing method audit trail not displayed from processing method settings after loading new data
KPR#:468541
'Save Method As' generates incorrect method audit trail entry for UV reference spectrum
KPR#:529592
Result set name not recorded in activity log after import
KPR#:548332
Renaming compound creates calibration curve removal entry in audit trail
KPR#:555984
Some of the Injection audit trail entries may not be recorded due to a failure downloading of a result set
KPR#:606512
User ID is used to record injection audit trail entries under certain circumstancess
KPR#:653350
Processing method audit trail entry for existing “Relative from” option is shown incorrect when changed from “On blank” to” On Current”.
KPR#:727200
Modifying properties of MS library report snippet will not get recorded in the report template audit trail.
KPR#:732157
User is not prompted to enter 'Reason for Changes' when linking method
KPR#:971312
Value of RRT ratio, or factor of reference compound are not captured in the audit trail
KPR#:58
Activity Log not displayed in web browser when using Chrome 5.1
KPR#:183239
Sequence/sample reports and Injection Audit Trail only show user who submitted sequence, not user who modified running sequence
KPR#:44803
Performing MS Quantitation using OpenLAB CDS ChemStation data
KPR#:44942
Calibration curve update timestamp for missing compound
KPR#:44965
Data field CalibCurve_CorrCoefficient is not properly labeld
KPR#:98815
Log / Log calibration curve model not drawn correctly in the report printout
KPR#:395508
Help and Learning needs updated statement regarding all calibration options or levels are supported with timed groups
KPR#:1
Instrument opened with a channel conflict is in a quasi-Not Connected state
KPR#:2
COM port information for clients does not match AIC COM port information
KPR#:44563
Canceling out of instrument auto configure still deletes all previous configurations
KPR#:146950
Using OpenLAB CDS Waters Acquity driver the PDA ( 3D option) is pre-set as default values as well for 2D Detectors
KPR#:195581
Unconfigured Sample Scheduler Agent causes Windows logs on CDS 2.3 AIC's
KPR#:480262
Authentication issue in a multi-domain environment
KPR#:592977
Logon to OLCP is not possible
KPR#:602493
Instrument can't be configure with TLS 1.0 disabled
KPR#:733079
Slow login performance when server and user domain don't match forest name
KPR#:751581
Multiple domain support is lost after upgrade
KPR#:751589
CDS 2.7 won't add user in a multi-forest domain
KPR#:751772
When starting "OpenLab Configuration" or "Shared Services Maintenance" an error is shown
KPR#:787329
Unable to start Agilent OpenLab Data Collection Service after installing OpenLab CDS 2.6 update 09
KPR#:804967
OpenLab CDS is not starting due to invalid host name
KPR#:967789
On Server Installed update page shows 'Agilent OpenLab CDS 2.6 Update 11'
KPR#:1046816
Vulnerabilities CVE-2018-1285 and CVE-2023-34152 detected
KPR#:1049554
Apache HTTP Server vulnerabilities
KPR#:465565
PDF extraction failing
KPR#:44755
Custom Calculation results containing a list of values and empty values, will lead to empty value in case of summary calculation performed with another Custom Calculation
KPR#:44838
Incorrect EIC exctraction
KPR#:55476
Create processing Method without the proper privileges.
KPR#:56074
Signal Alignment doesn't refresh
KPR#:56585
Wrong error message is thrown while opening same PDF report twice from DA
KPR#:71335
"Extract Chromatogram" option not available for LC/MS Chemstation data
KPR#:72603
Manual integration: different results for nested baseline for reprocess with and without clear
KPR#:73281
"Add/Update MS compounds" does not work on SIM data acquired in OpenLAB CDS 2.0
KPR#:73594
Amount is not calculated
KPR#:73632
New result set with baseline corrected is not showing the * next the signal name
KPR#:73953
"Response Window Type" is disabled for manually added compounds and qualifier ions
KPR#:85380
Importing a result set file (.olax) could lead to misleading versions
KPR#:105659
The master processing method is not linked properly to the imported EZChrom result set file
KPR#:106822
Incorrect Signal Names after importing ChemStation Data
KPR#:109858
LC/MS SIM data acquired in MMI is not displayed in TIC in Data Analysis
KPR#:111165
"Send spectra to NIST MS program" works only for first user, fails for all subsequent users
KPR#:111815
Import raw data from the ChemStation fails
KPR#:124594
Quantification of compounds or groups using a reference calibration curve fails if reference is missing in injection
KPR#:127347
Search field does not return all applicable results when searching for a result name
KPR#:130739
Cannot load result set in Data Analysis due to missing/corrupted .acaml or .rx files
KPR#:135459
Incorrect injection date for data file imported from OLCDS CS C.01.05
KPR#:137136
Cannot process data after adding a qualifier to ISTD compound
KPR#:146452
Asterisk * is shown next to injection even though all manual integration is removed
KPR#:147267
Slow performance in processing SIM data
KPR#:148123
File Upload Queue Error "Target file is inaccessible. Upload cannot be performed."
KPR#:148301
"Qualifier group details" table is not displayed for ISTD that fails qualifier criteria
KPR#:155331
Incorrect injection date for data file imported from OLCDS CS C.01.05
KPR#:155332
Incorrect injection date for data file imported from OLCDS CS C.01.05
KPR#:155661
Incorrect category displayed in the "Reason for Changes" window
KPR#:160749
Injection error "Cannot run integration" if data has two MS signals with same name
KPR#:160878
Sliders in the isoabsorbance plot are not always synchronized
KPR#:172088
User without "Save Master Method" privilege can still save master method in Data Analysis
KPR#:172479
Not all signals of EZChrom method are imported
KPR#:173214
"Data storage not available" when starting Data Analysis
KPR#:176350
Canceling a method link will lead to different method parameters
KPR#:176774
No signal in snapshot if snapshot is performed immediately after start of run
KPR#:178050
User without “Save master method” privilege cannot save results
KPR#:178215
Calibration curve does not start from zero
KPR#:178342
Data Analysis is slow to open with projects that have many folders
KPR#:180840
Incorrect injection date for data file imported from OLCDS CS C.01.05 or ChemStation B.04.03
KPR#:181176
Data Analysis crashes with GPC 1.0 plugin (G7860AA)
KPR#:181560
Incorrect calibration curve date after reviewing completed injections or reprocessing
KPR#:184527
Unexpected error occurs while importing raw data (ChemStation or EZChrom)
KPR#:188689
User without "Save Master Method" privilege can still save master method.
KPR#:188789
Compound identification fails when different compounds have same quantifier ion
KPR#:188930
Loading multi signal in DA causes software crash
KPR#:194201
RX files are missing in result sets due to EZChrom integration "Split peak" events
KPR#:195784
AIA export has minutes as time units
KPR#:196102
When using signal delay, EICs do not line up with TIC peaks
KPR#:196103
MS Peak Purity should only be calculated for TIC peak, not EIC
KPR#:198415
Disabled calibration point will be enabled after reprocessing
KPR#:202218
Default CDF file name of AIA export is not working for SIMDIS
KPR#:202580
Front exponential skim does not work or integrate properly
KPR#:214925
USP theoretical plates are different in OpenLab CDS versus ChemStation.
KPR#:220122
Drift calculation differences in OpenLAB EZCHrom and OpenLab CDS 2
KPR#:222870
Error while importing OpenLab CDS ChemStation Edition data
KPR#:224261
AIA export of GPC method isn't working
KPR#:228375
System suitability results are not calculated for specific peaks
KPR#:232522
Unable to integrate Child-Parent peak using EZChrom Integrator in OpenLab CDS 2.3
KPR#:233622
Long processing time for MS data
KPR#:237693
"detector_name" field in cdf file is not unique when using the AIA Export Plugin in DA
KPR#:237789
Missing peak entries get duplicated in DA and IR
KPR#:245031
RT calculation values in Data Analysis (Result view) and Intelligent Report do not match
KPR#:261157
Corrected expected retention time is not visualized correctly
KPR#:265397
Unexpected error occurs during processing of Custom Calculation due to a stop injection in sequence
KPR#:268319
Tree: Upload in progress icon disappears after refresh
KPR#:268885
When importing OLAX, the file disappears from the tree after Refresh
KPR#:269543
S/N ratio not calculated when using data acquired with Waters Acuity
KPR#:277719
Data Analysis is slow to open with projects that have many folders
KPR#:279012
Unhandled exception when closing custom calculation editor if connection with shared services server has been lost
KPR#:280784
Not all injections might get reprocessed if UV impurity check for all peaks is selected
KPR#:283099
DA does not display data in failover mode and data can't be reprocessed
KPR#:283201
Cannot extract spectrum from TIC SIM with multiple fragmentors
KPR#:285489
In some cases manual integration might be erased when reprocessing
KPR#:286172
EIC is not automatically extracted for MS timed group compounds
KPR#:286264
The Retention Time definition in the Data Analysis Reference Guide is misleading because of a wrong drawing
KPR#:289666
Error occures when a different user tries to link a new method to data
KPR#:289867
ISTD amounts not considered for calibration curve recalculation in some circonstancies
KPR#:293016
Error occurs upon reprocessing MS data with system suitability calculations
KPR#:293118
Reprocessing legacy data acquired from 2.1 or 2.2 can no longer integrate after extract chromatograms
KPR#:293411
"Add/Update MS compounds" is not working with SIM data
KPR#:294515
Noise, signal-to-noise and system suitability calculations for extracted chromatograms
KPR#:296088
Locking a unsaved result set will show a warning "Newer version exists"
KPR#:297380
Manually extract UV Wavelength chromatograms is part of Privilege control on the manual but this function does not exist
KPR#:298958
Fill down sample type might cause an unexpected issue
KPR#:303797
Manual integration will show wrong peak width
KPR#:309715
Empty project name in report for new created or imported result sets
KPR#:318706
Different values for relative retention time according to EP in ChemStation vs. CDS 2
KPR#:344871
A data processing component during acquisition became orphaned process and could not be closed automatically after a single or sequence run
KPR#:358009
Revoke signature when "Enforce signature order" is enabled
KPR#:371060
Reprocessing of locked result sets
KPR#:372581
Exception error occurs when loading result set
KPR#:373135
MS peak purity failing to compute purity calculation
KPR#:379410
Weird profile spectrum and incorrect mass with Fast scan on LCMSD iQ and OpenLab CDS v2.5
KPR#:381349
Post-Processing plugin is not working for injection data file names containing { or }
KPR#:389770
LC/MS profile data acquired in Chemstation C.01.XX is displayed as centroid data in OpenLab CDS v2.5
KPR#:392042
Named Group does not appear in Injection Results
KPR#:394440
Cannot "Send spectrum to NIST MS program" if it has more than 800 m/z ions
KPR#:394495
Modification date for the manually integrated injection does not change when saving reults
KPR#:394933
Blank subtraction is not possible with data generated on Hitachi Amino Acid Analyzer
KPR#:395892
Peak to peak or ASTM method using different value to calculate S/N as descriet in the EP
KPR#:397440
UV reference spectrum assigned to compound identified in FLD signal
KPR#:398303
Importing ChemStation B04.01 data into OpenLab CDS 2.4 can have incorrect injection time
KPR#:402658
Fraction collection data loaded incompletely on a distributed system with ECM 3.6
KPR#:402909
Manual integration influences automatic integration of next peak
KPR#:402989
Method report shows additional parameter for same data file after reprinting
KPR#:407469
Selected fraction is not highlight in the sample container
KPR#:409218
Imported OpenLab CDS EZChrom data has incorrect injection time when daylight saving time is activated is turned on
KPR#:409935
Unhandled exception when OLSS server is unavailable during search
KPR#:410912
"Identified peaks" is not working in MS Peak Purity workflow
KPR#:413432
Wrong "Rsp (%)" values are calculated in the “Qualifier group details” table
KPR#:413781
Loading single injections in Data Analysis is slow
KPR#:415746
OpenLab CDS v2.5 crashes with exception error when viewing MS spectrum
KPR#:422270
Fraction collection data loaded incompletely on a distributed system with ECM 3.6
KPR#:425417
OpenLab CDS v2.5 shows no TIC signal when "Import Raw Data" acquired with MSD ChemStation
KPR#:425749
MS data takes long time to reprocess in OpenLab CDS v2.5
KPR#:427364
Import OpenLab EZChrom raw data fails if File System Security is enabled
KPR#:431130
Data Analysis gets unresponsive when canceling the reasons dialog
KPR#:432465
HTML tags appear in the sample description
KPR#:432540
In-completed injection on migrated OpenLab CDS ChemStation data is not shown in the injection list
KPR#:432679
Modification date of calibration standards gets changed to current time after import
KPR#:433296
No signal displayed while loading data when the system is in failover mode
KPR#:433548
Modification date of calibration standards gets changed to current time while loading a result in Data Analysis
KPR#:434519
Data export to AIA cannot be used for spectral analysis with 3rd party Software
KPR#:435447
Weird diagonal line in MS spectrum extracted from LC/MS iQ profile data
KPR#:435460
RX files missing after sequence completed if physical printer is not configured
KPR#:437309
Click on "Select Project" in DA takes some time to show the projects
KPR#:439998
Mistranslation of "Norm amount(s)" and "Norm concentration(s)" in Chinese
KPR#:442672
Cannot extract EICs if signal alignment (Use delay) is selected in processing method
KPR#:443824
ChemStation single injections not displayed in Data Selection
KPR#:443842
Concentration and amount of the compound are not calculated if qualifier ratio fails
KPR#:443852
Qualifier RT not updated when compound RT is changed in Compound Table
KPR#:448018
System Suitability calculations are not performed when operating system language is Russian
KPR#:450429
Can't load multiple calibration points if they have the same Data file name
KPR#:450831
Qualifier RT not updated if "Assign Compound" is selected from peak in chromatogram
KPR#:456072
Click on turn custom scaling on/off will show an error
KPR#:459236
User without "Save master method" privilege can modify and save the master method
KPR#:459647
Order of custom parameter fields in the injection list is not saved.
KPR#:465446
Value for sample amount cannot be read from an exported AIA file
KPR#:466407
Data Analysis shows an error when changing run type or bracketing mode in the Injection List
KPR#:469739
Modification date of calibration standards gets changed to current time while loading a result in Data Analysis
KPR#:471047
No MS peak purity result shown if "Identified peaks" is selected for MS peak calculation
KPR#:472237
Reprocessing large result sets might take some time
KPR#:472708
No m/z values shown in report generated from automated processing after acquisition run is done
KPR#:473649
Create new result set does not contain instrument traces
KPR#:474766
Re-quantification of a single injection in a large result set takes longer as expected
KPR#:476730
Relative Retention Time (RRT) is not calculated for peaks with no compound assignment
KPR#:482530
Calibration level values are erased if the number of levels gets changed to 10.
KPR#:490201
Processing method last modified date
KPR#:494008
Not all ions are extracted after performing "Reprocess All" on GC/MS CI SIM data acquired in 2 time segments
KPR#:494448
"Add/Update MS compounds" not working for GC/MS CI SIM data
KPR#:494679
Incorrect retention time after manual integration
KPR#:495802
Injection modification date changed after "Print All" reports
KPR#:497674
"Error loading data: ...sequence.acaml: Object reference not set to an instance of an object"
KPR#:501755
Result set audit trail contains only for closing bracket an entry for processing
KPR#:516949
View E-Signatures will throw an unexpected error
KPR#:522333
Loading large result sets might take some time
KPR#:523042
DA terminates with error "System.Xml.XmlException: Root element is missing"
KPR#:528367
Fields import from NIST libraries
KPR#:528390
Arbitrary spectrum library search results cannot be reported
KPR#:529868
EZChrom integrator may suppress rider peak's baseline
KPR#:531497
Signal to noise calculation could not be computed for the GC front signals using EP
KPR#:533604
Tooltip for "Extract spectra from integrated peaks on reprocessing" checkbox not localized in Chinese
KPR#:535090
Manual Integration Undo Button does not work for all steps
KPR#:536780
OpenLab CDS v2.6 crashes after deselecting signals from imported MassHunter data
KPR#:537429
In "all spectrum same scale" display mode, threshold is removed after reprocessing
KPR#:537430
Varying threshold limits with "all spectrum same scale (per pane)"
KPR#:537640
Chromatogram extraction error after processing data
KPR#:538334
Data Analysis crashes in OpenLab CDS v2.5 when opening Extract Chromatogram dialog for LCMS multimode data
KPR#:538747
Data Analysis stops working when loading recovered result set containing fraction collection data
KPR#:539604
No MS peak purity computed if compound is missing or group is defined in the method
KPR#:540410
DA API is not working on a workstation plus
KPR#:541386
Removal of MS reference spectrum for compound is not logged in the audit trail
KPR#:548413
Misleading processing method version in the result set audit trail
KPR#:551002
Error with peak details window when selecting a compound with an undetected qualifier
KPR#:553817
Loading single injection runs shows error "Unable to change selection. The given key was not present in the dictionary"
KPR#:555730
Signal not found when processing a result set even though signal exists
KPR#:558818
MS EICs not showing same decimal places in injection tree and chromatograms as in CDS v2.5 and earlier
KPR#:559315
Specific integration events defined on extracted signal may not be applied in OpenLab CDS v2.6
KPR#:559325
Reports defined to be printed on specific signals are not printed in OpenLab CDS v2.6
KPR#:564303
Duplicate Integration Optimizer icon in layout section of the home tab
KPR#:565818
Signal names are not displayed correctly in OpenLab Data Analysis for localized EZChrom methods.
KPR#:565825
Chinese characters in ANSI Custom Calculator constants file causes issues
KPR#:567164
Inconsistency on the 8th signal name
KPR#:567749
"Removed MS reference spectrum for compound..." is not translated in method audit trail.
KPR#:572630
MS Signals missing for Single Sample Sequence
KPR#:574075
MS EICs not showing same decimal places in injection tree and chromatograms as in CDS v2.5 and earlier
KPR#:576021
Instrument traces are compressed in overlay mode
KPR#:579266
Error occurs if a DA API loaded result set gets unloaded
KPR#:580458
Task Manager shows > 4GB memory consumption for Agilent.OpenLab.DataAnalysis.exe
KPR#:581394
Snapshot did not close after 30 minutes.
KPR#:582152
2DLC: performance issue related to manual integration
KPR#:584120
Only 2 digits for sample amount on an AIA export
KPR#:590076
Data Analysis hangs when RT Update setting is used
KPR#:591215
Adjustment of MS peak threshold causes lockup or crash
KPR#:596393
Data Analysis not able to load all MS SIM signals imported from ChemStation
KPR#:598024
Qualifier Signal Name updates during reprocessing causing Qualifier Status to fail
KPR#:610901
Not enough quota
KPR#:613471
Empty injection results table and chromatogram graphs with no integrated peaks upon loading a saved result set
KPR#:614880
Custom calculator results not being calculated
KPR#:615992
Sample custom fields are "linked" after a new result set is created
KPR#:620325
One of the acquired data is missing from result injection list
KPR#:621912
Loading context menu in signal plot window in Data Analysis leads to an unexpected error
KPR#:632753
When loading GCMS or LCMS data from CDS version 2.1 into later versions of CDS Data Analysis, adding a compound from a peak in the TIC to the compound table does not function as expected.
KPR#:638109
Issue while using the IProcessingMethod interface
KPR#:648671
Snapshot cannot be launched
KPR#:653037
Random sorting of injections in Audi Trail sorted by descending Date
KPR#:653510
Post processing plugin output export fails for FQDN path
KPR#:654632
Warning message "Cannot load methods (not found)" after loading a result set
KPR#:656971
Negative value for tailing factor
KPR#:658525
RRT is not taken into account for compound identification
KPR#:658526
E-signatures and audit trail information are lost after second signing
KPR#:658878
Report will not be created if report filename starts or ends with a whitespace
KPR#:668598
Error occurred while importing GC7890 EZChrom dual tower method in OpenLab CDS 2.7
KPR#:672553
Data Analysis is not responding after previewing report
KPR#:676810
EZChrom method with history points for log amount ‘0’ or less than zero is not imported
KPR#:677814
Cannot select all spectra when multiple spectra are extracted from one peak
KPR#:680210
Unable to add qualifiers from MS spectrum in some circumstances
KPR#:681553
Memory leak on Signal Transformation View
KPR#:683141
Missing MS channels in new results sets
KPR#:686226
Integration Events from EZChrom method are not imported on the correct signal name in OpenLab CDS
KPR#:689877
Reviewing or adding a manual entry to the audit trail no longer triggers a new result version
KPR#:691556
Option to Save results is missing in "Cannot print reports" dialog for single samples
KPR#:692754
Adding peak as compound from TIC scan leads to an unexpected error
KPR#:692811
Data Analysis does not get initialized
KPR#:694076
Qualifier ratio may not be calculated as expected when adding MS qualifiers to a method
KPR#:695070
EIC extraction window is not calculated correctly when signal alignment is applied
KPR#:695471
Sample amount in AIA export of EZChrom data is 1.00
KPR#:697151
Smoothed qualifier EICs can unsmooth themselves unexpectedly
KPR#:697180
"inconsistent between result and parameter" warning after using scaling in report settings
KPR#:698709
MS Chromatogram Smoothing does not use EIC extraction window setpoint
KPR#:698717
Toggling smoothing on and off may result in compounds no longer linked to extracted signals
KPR#:702680
Manual integration options are not visible
KPR#:703034
Qualifier retention time shift is incorrect if retention time update is set to after each run
KPR#:703426
Scaling settings in processing method are editable even if custom scaling is active
KPR#:703810
Unable to do manual integration in first signal from Waters Acquity PDA
KPR#:703895
Use of EIC extraction windows with SIM data can cause qualifier RSP% to not be calculated and DA to crash in certain cases
KPR#:707034
Qualifier may be assigned to wrong compound
KPR#:707114
Unexpected error occurs after deselecting a history point
KPR#:708783
"Is time ref." and "Is RRT ref." columns are not displayed in processing method
KPR#:710753
Unexpected error after reprocessing a result set with timed / named groups
KPR#:713668
SIM data may calculate qualifier ratio incorrectly when signal is changed to TIC SIM
KPR#:716111
Changes are discarded after closing and saving a result set
KPR#:716452
Method not found when loading first version of a result set
KPR#:722012
Changing signal from EIC to TIC causes qualifier ratios not to be calculated
KPR#:723035
ASR (Analytical Studio Reviewer) export file not being written correctly
KPR#:725618
Manually extracted spectra within an integrated peak can erroneously become the linked display spectrum
KPR#:726904
Adding compounds to method from SIM data when signal alignment is enabled can cause Data Analysis to crash
KPR#:729785
EIC changes depending on the selected number of compounds
KPR#:733574
Loss of MS spectral granularity when sending to or retrieving from a library
KPR#:736987
Blank subtraction 1D and 2D do not work together.
KPR#:738475
X-axis of Max Wavelength Chromatogram is updated erroneously updated when ASR plug in is enabled
KPR#:740800
EICs not automatically extracted when chemical formulas are entered as targets
KPR#:742997
DA is processing endlessly
KPR#:745819
MS profile reference spectra displayed incorrectly
KPR#:746473
Different versions of acquisition methods with same name are not available after creating a new result set.
KPR#:747725
Amount and Concentration unit is blank in column header of compound table
KPR#:748104
MS Spectrum window does not behave correctly when using pinned injections
KPR#:753515
"Review selected run in DA" does not work.
KPR#:766195
DA Launcher log files are overwritten.
KPR#:768811
Data Analysis can become unresponsive when extracting all SIM signals
KPR#:768814
Automatically searching TIC peaks in MS library can cause Data Analysis to crash
KPR#:768815
Reopening processed data which has spectral smoothing enabled may cause Data Analysis to crash
KPR#:770446
Unexpected error after using Manual Integration
KPR#:770754
Changed value is not kept for custom fields but recorded in audit trail
KPR#:787422
Using pinned injections while viewing profile MS spectra in overlaid mode does not refresh properly
KPR#:790363
Resolved EZChrom methods do not display the correct Signal names after migrating to CDS
KPR#:790665
Ion labels missing for overlaid profile MS spectra
KPR#:791706
Assigning qualifier can cause Data Analysis to crash under certain conditions
KPR#:798907
Smoothed MS chromatograms may exhibit splining under certain conditions
KPR#:808593
EZChrom to OpenLab CDS migration: Additional peaks detected in OpenLab CDS after migration
KPR#:935255
Manipulating overlaid profile spectra with pinned injections causes DA to crash
KPR#:948441
Smoothed MS profile spectra may exhibit splining and negative abundance values
KPR#:952244
Locked result set cannot be unlocked
KPR#:953853
Opening and closing imported MS data without saving before closing can result in MS TIC(s) not displayed for first injection
KPR#:954334
Loading method causes error One or more errors occurred. (Content cannot be converted to the type Int. Line 1, position 94)
KPR#:955614
Target formula not accessible in custom calculation and reporting
KPR#:957988
Quickly drag and drop Data Analysis windows will show a black area
KPR#:958930
Modification date of linked injections gets changed after linking same processing method to an unlinked injection.
KPR#:959233
UV Purity value is blank for some peaks
KPR#:964305
MS Base Peak may return incorrect value for polarity switching data when smoothing is enabled.
KPR#:972140
Processing error: The given key not present in dictionary
KPR#:974489
Missing entry in system activity log for signing or revoking a signature on a result set
KPR#:980434
LCMS data exported to ChemStation format using AIA export is lacking metadata
KPR#:980825
EIC extraction window erroneously applied to TIC signals
KPR#:981589
Quantitation cannot be performed on MS compounds if the Single m/z expansion chromatogram window is changed after compounds already exist in the compound table
KPR#:984711
Missing injection in the result set after loading in Data Analysis
KPR#:985357
Renaming a compound causes error "unable to update data value: An item item with the same key has already been added"
KPR#:1024094
Individual peaks are not quantified in a timed group
KPR#:1026486
Some injections might not be processed when using Walkup
KPR#:1028367
Locking of result set is not permanent
KPR#:1032336
Parent peak is not correctly updated if rejected shoulder peak is nested in rider peak
KPR#:1037748
Only the first 10 calibration levels are imported when creating a new method from EZChrom
KPR#:1047275
Qualifiers can be added to multiple methods
KPR#:1048045
Qualifiers can be removed if multiple methods with the same compounds are open
KPR#:1049217
Swap qualifier to target with EIC extraction windows does not work as expected if target and qualifier Retention Times are different
KPR#:1049349
Adding qualifiers after performing Swap qualifier to target can result in incorrect qualifier RSP% calculations
KPR#:1050500
CEMS data imported from ChemStation may not function as expected in Data Analysis
KPR#:1051274
Missing blank can trigger crash
KPR#:1054966
Unexpected error occurred after importing *.cdf files exported with OpenLab CDS 2.x
KPR#:1055068
DA API: Exceptions when accessing advanced ChemStation integration parameters
KPR#:1055415
Adding compounds to SIM data imported from OpenLab ChemStation can result in a crash
KPR#:1056127
The sample name of the data exported by AIA is incorrect
KPR#:1060626
Loading processing method is slow if output path for post-processing plugin is long
KPR#:1063075
Spectra extracted over a range are not re-associated with their chromatographic peak when undoing a manual integration event
KPR#:1063769
Intermittent processing error
KPR#:1067591
Changing retention time of a compound in one method will change it in another method as well
KPR#:1068025
Shoulder has slightly too small peak area when using Gaussian baseline
KPR#:1070072
Wrong user recorded in Activity Log after unlocking DA with another user
KPR#:1070811
Simple chart in reporting has only linear trending line
KPR#:1071997
DA API request for MS spectrum fails if spectral smoothing is enabled
KPR#:1074559
Compound units are not available in DA API
KPR#:1074934
Unexpected error occurred when printing sequence audit trail.
KPR#:1076856
Custom Calculation Editor stops working when a new file gets created
KPR#:1077322
DA API returns error 500 for all requests
KPR#:1078622
Calculate sensitivity does not refresh as expected
KPR#:1078707
Crash when reprocessing data when injection selected for Blank Subtraction cannot be found
KPR#:1086660
If a CC Display Name contains ">" it is displayed as ">" in Injection Results and CC report
KPR#:1097003
DA API handles Custom Fields case-sensitive but DA does not.
KPR#:1100867
DA API session host stops running the API Server instance after 30 minutes of inactivity
KPR#:1106303
DA API does not clear history calibration points if clear calibration is set.
KPR#:1107981
An intermediate version of a result set can be locked/signed when clicking cancel
KPR#:1108079
Entering a target mass in the sample sequence table of >3000 will be rejected
KPR#:1110364
Unexpected error after loading a processing method from 2.7 with post processing plugin
KPR#:1110895
Numeric compound custom field reverts to original value when changed in injection list
KPR#:1114859
Result set not locked for user with lower signature level
KPR#:1121005
Data Analysis crashes upon clicking on "Up" arrow to browse outside of Methods folder in "Open Method" window.
KPR#:1129315
Missing blank can trigger crash
KPR#:1129747
The Data Analysis application does not start and error message is shown
KPR#:1130287
Cannot start Data Analysis from Acquisition
KPR#:1152460
Switching rows in the compound table can cause a Data Analysis crash in certain scenarios
KPR#:1172957
LC/MS Sample Purity calculation omits neutral losses if neutral loss cannot result from target formula - but still lists the neutral loss in the Sample Purity results table
KPR#:190865
Run on GC hung in processing state when performing a snapshot
KPR#:1
Setting source temperature as a Timed Event does not change the setpoint on the Dashboard
KPR#:2
Selecting a SIM or Scan time segment line highlights the entire row
KPR#:7
Starting EI 5977A Tune does not wake up a sleeping 7890B GC after it was in sleep mode.
KPR#:9
While in Vented, Venting or Pumping down and network connection is lost, on re-connection the UserInterface state goes to Idle.
KPR#:11
Manual Tune Scan plot does not show all of the information
KPR#:12
Prepare to Vent disappears from MSD LUI
KPR#:13
Vacuum fault not clearing on turbo pump without Lcomm, 5977B and 7890B system.
KPR#:15
Manual Tune profile plot does not show all the information
KPR#:18
Signals acquired in "SIM" mode or "SIM and Scan" mode can drop out below the baseline
KPR#:117113
Unable to close Acquisition if connection is lost while tuning or in Tune Control
KPR#:134542
Filament selection is not updated when changing methods
KPR#:139960
It is possible to acquire data with un-tuned tune files.
KPR#:160081
Tuning and Tune related activities are not recorded in activity log
KPR#:177340
GC/MS method update change from 'Version 100' to 'Version 101'
KPR#:177496
Data file is collected but cannot be opened in Data Analysis
KPR#:223710
AcquisitionServer.exe process does not close when Close Connection is used
KPR#:224414
Acquisition Method Report does not show exact MSD model configured
KPR#:231685
GC/MS autotune using a saved atune file results in manual tune report template
KPR#:234855
Discrepancy in "Run time" value user entered in Acquisition UI vs displayed in the Acquisition Method Report
KPR#:235934
Acquisition Method Report shows generic "Detector EMV Override" label in SIM Table
KPR#:264274
Autotune report always shows the default masses for PFTBA even if the selected masses are changed
KPR#:267319
Switch Filament options should not be shown for CI GCMS configurations
KPR#:306994
MS stays in a not-ready status following autotune if using JetClean in Acquire & Clean mode
KPR#:347742
PCI autotune fails to complete on some instruments after an initial successful autotune
KPR#:366073
Aborting bakeout during equilibration may cause the timing problems
KPR#:370668
Autotune icons are grayed out after clicking "Cancel" in Delete Tune File dialog
KPR#:370684
User created tune files cannot be deleted if a default tune file is currently loaded
KPR#:387039
No warning message after method is loaded with invalid tune file
KPR#:389009
Actual values for bakeout and equilibrium time are incorrect
KPR#:389044
Vacuum Control: If the acquisition client is closed during vent and then reconnected, the time elapsed value is lost
KPR#:389509
Vent: Turbo speed may not be accurate below 3%
KPR#:392073
Tune Report PDF may not display in some situations
KPR#:392865
Cannot release Tune Control
KPR#:394987
Using "Generate Report" in PCI mode the calibrant valve is not opened
KPR#:396350
Custom Tune: Correct masses will not be displayed in report if changed
KPR#:398529
Custom Tune: Using masses that are fewer than 100 amu apart will abort with error
KPR#:412557
Acquisition can't be closed during GC-MSD venting
KPR#:181
Cannot get 7697 Comm setup in OpenLab CDS 2.2.0.600; Connection always makes the HS's GC IP revert to previous setpoint
KPR#:194
Sequence aborts with "address may not be null" error
KPR#:53
Data Store server synchronization fails if the computer hostname contains an underscore.
KPR#:55
Old icon displayed for links after upgrading your Data Store server to rev. 2.0
KPR#:146982
OpenLAB CDS crashes after power cycling the Waters Acquity instrument
KPR#:218620
Changes to Manual Tune parameters have no respond in spectrum display windows LC/Single Quad
KPR#:246022
Charging voltage displayed as Nozzle Voltage in the check tune report for MultiMode Source
KPR#:246030
AJS source Sheath Gas Temp & Sheath Gas Flow parameters not validating in the Method Override
KPR#:246035
Single Quad UI always display "Not Ready" state when the instrument in "Standby"
KPR#:246037
Cannot close OpenLab CDS Acquisition if connection to server is lost during LC SQ tune check
KPR#:257678
Missing Data Point crossed the chromatographic peak on G6135C SQ
KPR#:269242
'Review Tune Report' dialog may freeze UI
KPR#:320141
APG remote triggering LC shutdown
KPR#:339311
Abundance change with dwell time when changing detector gain factor
KPR#:347214
Shutdown method leaves LCMSD iQ actively scanning and not "Off"
KPR#:349670
Getting prompted to save method when no change is made in the method
KPR#:359660
Divert valve may not switch to waste during hardware fault
KPR#:371542
SQ online signal is missing after windows restart
KPR#:385359
Autotune report results are incorrect on FWHM
KPR#:394789
Heaters faults cannot be cleared on LC/MSD iQ
KPR#:402489
Embedded Software (ESW) crash during autotune
KPR#:409473
AIC installation was cancelled during install of LCMS driver, which caused it to roll back. After relaunching installer, LCMS driver install failed
KPR#:438688
Unstable spray warning in EMF
KPR#:474201
Applying LogAmp calibration coefficients
KPR#:478099
Mismatch between gain factor in acquisition method and gain displayed in DA
KPR#:481643
Quad resolution during SIM mode (Wide & Widest).
KPR#:482908
New EM Horn caused estimate Gain to jump around with low abundance
KPR#:527627
527627 - Mass shifted issues on 400ms dwell time in Acquisition
KPR#:581848
Running Sequence with LC/MSD gets stuck in Not Ready
KPR#:737754
Checktune fails when FastScan is checked
KPR#:750291
Checktune Icon grayed out
KPR#:454142
Support of automatic Russian localization in OpenLab CDS v2.5 Update installer
KPR#:492092
Concentration calculation formula is not reported correctly on Chinese version of OpenLab CDS 2.
KPR#:933253
Regional settings are not used in custom calculator implicit type conversions
Keyword: Localization,Report Template Design
KPR#:277791
Composite group saved with special character in the name
KPR#:44824
Cannot start Data Analysis because it is bocked during "Initializing modules" step
KPR#:145396
WorkArea is not cleaned up on shutdown
KPR#:178350
New domain users can't access content management to save methods or any other file
KPR#:281307
Internal server error when searching the System Activity Log
KPR#:319219
Processing slowness
KPR#:401255
SQL Server Database - 100% CPU Usage
KPR#:483280
Performance issues in Data Analysis due to network interruptions during reprocessing
KPR#:492041
C:\ProgramData\Agilent\SecureFileSystem is growing significantly
KPR#:578831
Many log files created, opening Diagnostics node in OLCP is slow
KPR#:580348
Custom Calculation takes very long to be executed
KPR#:580688
Active Directory query searches the entire forest and causes login slowness.
KPR#:580690
Control Panel Lab-At-A-Glance display of instruments is slow.
KPR#:609704
Control Panel freezes when many users launch Acquisition and Data Analysis at the same time in a client server system.
KPR#:628048
SQL Parameter xact abort prevents Data from being uploaded
KPR#:638587
Improvements to address archive problems
KPR#:651438
Excessive logins can cause com.agilent.datastore.cache file to grow and impact performance
KPR#:666045
Slow performance when blank subtracted signal gets manually integrated
KPR#:725014
Slow performance when loading projects tab in Control Panel
KPR#:726704
Sample Scheduler Acquisition can get slower over the time with CDS 2.5, 2.6, 2.7
KPR#:733131
Duration of project creation is extremely long
KPR#:751590
High CPU Load with ActivityLog disabled(SharedServicesHost/ApacheHTTPServer)
KPR#:767591
Unable to open method, sequence, and result files in Data Analysis
KPR#:954001
OutOfDate is not reset after first instrument's data is read (multi-instrument)
KPR#:954005
Loading Sequence from result set takes >1 minute for Browse box to appear
KPR#:954008
OpenLab Shared Services Crashes frequently
KPR#:962671
Unable to process result sets with big ACAML files from Terminal Server
KPR#:1114686
Unable to load a single run from DA search results
KPR#:1125395
Data will not open with a ' or ˚ character in the path
KPR#:1125677
Activity Log indexing paused when HDD space is low
KPR#:1128202
Leading/trailing spaces trigger an "Import data failed" error when importing data in DA
KPR#:1153885
OpenLab v2.8 cannot be uninstalled after installing Update 02
KPR#:1159951
OpenLab Server 2.8 Update 03 is not backward compatible with older clients
Keyword: Performance,Roles and Privileges
KPR#:304709
New domain users can't access content management to save methods or any other file
Keyword: Project Configuration
KPR#:1125397
Insufficient validation when configuring a project's folder path
KPR#:44971
Report generation to .doc file format containing the method information may lead to a very long report containing blank spaces
KPR#:56834
Trend Micro OfficeScan will prevent OpenLAB CDS to report instrument traces
KPR#:68907
Blank spaces may be seen in CDS 2.1 on report printout
KPR#:73690
Overlapping library search spectra plot when saving the report as doc and xls file formats
KPR#:90883
Report template migration to OpenLAB CDS 2.1
KPR#:120051
EIC may disappear when using the option "report only selected signals"
KPR#:123267
Incorrect value displayed in Reporting for compound custom parameter containing blank spaces
KPR#:141937
Certain report generation steps will lead to report the previous version of the result set
KPR#:142710
Theoretical plates USP not reporting the correct value for Chinese/Japanese/Portuguese CDS versions
KPR#:160085
Misleading data file directory path for results moved from one project to another
KPR#:198670
With some result sets the chromatogram peak drawing may fail
KPR#:261124
Report template file path is missing when generating reports in Reporting View
KPR#:277965
Report not generated when copied to Windows file system with ECM 3.x back end
KPR#:286844
Reporting spectra legend in reporting
KPR#:290438
Report printout may show more method set points if reloaded
KPR#:317320
Empty fields in the report of imported OpenLAb CDS EZChrom Edition data in OpenLab CDS
KPR#:351328
Timed group calibration correlation factor not printed in reports
KPR#:356133
Specific report generation workflow can lead to print previous results version
KPR#:371827
Quantified point may be not be drawn correctly using log/log calibration curve
KPR#:397976
Reporting matrix not correctly exported to csv report output
KPR#:403968
Printing, locking and signing of unsaved data if two users load the same result set and modifying it
KPR#:417017
Cannot preview report for ion chromatogram snippets or default templates on Chinese and Portuguese systems
KPR#:417467
Shimazu GC column oven temperature not reported
KPR#:422588
It is not possible to preview report using the default template "Purity_Flow.rdl" on Chinese and Portuguese OpenLab CDS v2.4
KPR#:440915
Report will not be generated when using default processing method "GC/LC Norm Percent"
KPR#:440919
Unattended Processing Client throws an exception when it cannot find the report template specified in the processing method and the run will be aborted
KPR#:450957
A failed automated printout error is logged in category "Configuration" and not "Instrument"
KPR#:453474
MS profile spectra not correctly labelled
KPR#:468440
Performance of report generation decrease with added pressure plot
KPR#:487420
Summary calculation update for calibration curves
KPR#:489079
Calibration curve not reported
KPR#:503299
Reprocessing with custom calculation enabled fails with an exception
KPR#:523017
Mass Abundance value in Report Spectra incorrectly shown as two decimal value
KPR#:538141
Cannot report Peak_tail_Factor and Asymmetry 10 Perc when in Russian
KPR#:540399
Error occurred during report rendering due to ‘&’ special character in data file name
KPR#:544385
Sometimes when using the contour plot 2D item on reporting an exception occurs
KPR#:553424
Corrected expected retention time fields for 2DLC are not available in reporting
KPR#:557632
2DLC: do not display lost cuts in chromatograms
KPR#:561798
Incorrect translation in CHS Data Dictionary
KPR#:561928
Values of deactivated fields are listed on the Method Report
KPR#:567166
MS profile spectra not correctly labelled
KPR#:569299
An issue occurs when a custom parameter and a variable are used in same expression at the same time
KPR#:570687
Show 2DLC cut annotations not working
KPR#:580884
Report templates cannot be used on Chinese system
KPR#:583091
No result set version is printed on injection reports automatically generated during acquisition
KPR#:603762
Difference in Date an Time between pre-viewed PDF report and saved PDF report
KPR#:611863
Search result limitation not working as expected using multiple libraries
KPR#:618528
Using the Single Acquisition Method Parameter snippet, many 1220 parameters are reported as unavailable
KPR#:623780
Slow performance when saving a sequence summary report with ECM 3.x integration
KPR#:638044
Adverse scale marking causes poor readability
KPR#:639220
Scaled response value of a timed group is listed on a report as area
KPR#:642070
An error occurs when a generated pdf report is opened using Acrobat Reader
KPR#:651985
"EngineFormatNumber" issue shows up using the reporting editor
KPR#:665022
Some default Document Templates failed to open if system language is Japanese
KPR#:706298
MS Spectrum from UV/GC peak snippet sometimes displays No spectra available
KPR#:714169
Report cannot be previewed
KPR#:716568
MS Spectra sometimes not reported as expected with positive/negative switching data
KPR#:733285
MS Library Search snippet can display the incorrect spectrum under certain conditions
KPR#:779752
Rendering process hangs and consumes memory until it reached system limits
KPR#:784136
Peak labels cannot be changed to no label in chromatography properties
KPR#:804981
Aggregators return wrong values if visibility of table is controlled by an expression
KPR#:936448
Reports generated automatically when the ASR post-processing plugin is enabled show rendering issues for Max WL and Total WL UV chromatograms
KPR#:940580
Rendering MS Spectra in Overlaid mode increases rendering time
KPR#:1054131
Ions may be mislabeled in deconvolution snippet graphics
KPR#:1061551
Arbitrary profile MS spectra in data imported from ChemStation are not displayed in the report
KPR#:1063284
Arbitrary spectra are not associated with a peak if integration is added after the spectrum has been manually extracted
KPR#:1066773
Wrong peak type on report if peak baseline code' is 'VV G'
KPR#:1071941
Sequence line numbers greater than 9 are not properly displayed for Japanese OpenLab CDS sequence reports
KPR#:1072208
'Not all available columns are visible' appears for MS Sample Purity Results
KPR#:1084314
Chart snippets using non-rounded numbers for y-axis labels
KPR#:1085600
Compound custom fields set as type Numeric which contain no value are being displayed in reports with an error
KPR#:1100261
Reporting the execution time in body adds the time offset
KPR#:1117180
Summary calculation settings are not kept if custom calculation results are used as column values
KPR#:1119266
Overridden column parameters are not reported
Keyword: Report Template Design
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#:44936
Missing syntax warning: Variables extended by a unique key need to be enclosed in brackets if used in mutiplications or divisions
KPR#:55868
.NET Framework 4.6.1 update not compatible with OpenLAB CDS 2.0
KPR#:56166
Report design with MS spectra plots
KPR#:71235
No report generated when the expressions are not completed or correct
KPR#:90697
Intelligent reporting composite groups having misleading names in the report template folders
KPR#:93291
Error editing Intelligent Report templates migrated from OpenLAB CDS ChemStation or EZChrom
KPR#:112794
Chromatogram custom signal axis scalling
KPR#:116526
Report parameters as boolean in report editor must only have "Default Value"
KPR#:116987
Single Data Analysis method parameter values may not be accessible for expected compounds
KPR#:150911
Filtering report item with the same data field containing several values
KPR#:165325
Variables saved in the table summary calculation must be used after the table
KPR#:217394
Report missing peaks with other peak types (identified and part of groups)
KPR#:234300
Migration of ChemStation Report template to OpenLab CDS v2.x
KPR#:291101
Diagnostic data such as column information, module temperatures are not available in reporting
KPR#:319688
Migration of report template containing multi-line expressions
KPR#:322678
Report document template failing with error
KPR#:348575
Edition of custom variable, custom parameter or method override parameter expression may lead to corruption
KPR#:349873
Custom parameter expression error in OpenLab CDS 2.4 Update 03
KPR#:385844
Reporting method information snippets are duplicated in summary report outputs
KPR#:409055
Formatting option is not available for MS peak purity ion table
KPR#:457828
Error in editing compound summary matrix
KPR#:479783
Matrix report item becomes uneditable
KPR#:513192
Expressions not correctly appearing in report editor
KPR#:646866
Error when loading report preview "AsyncHelpers.Run threw an exception"
KPR#:794650
Sorting Chromatogram in Intelligent Report not working
KPR#:804973
Expression for visibility is not kept in case of using an if statement.
KPR#:937245
Filtering issues when compound name includes "["
KPR#:61
Sequence Summary Extended template in Excel format not reporting the acquisition or processing method information correctly
KPR#:62
Generating a report to word file format may generate a report containing not aligned report items
KPR#:383434
Export to excel does not export the report header logo
KPR#:400986
The selection of RSD summary calculation is not saved with the report template
KPR#:482862
MS qualifier results not correctly reported
KPR#:542932
"Template version" is named "Template Version of content management" in report template document
KPR#:543932
Document template failing for Calibration and Stability report templates
KPR#:556931
Adding a Signal to Noise S/N column to report results in error with Russian version
KPR#:581131
Mistranslations in snippet and default templates
KPR#:587252
Not possible to generate the template documentation because of "Failed to document the template"
KPR#:613470
The audit trail table of a report template is not properly printed
KPR#:641384
Report template from OpenLab CDS 2.1 gets unusable in OpenLab CDS 2.5
KPR#:701140
Reporting Spectrum legend text is not matching with Data Analysis view
KPR#:744127
Modifying report template stability_report.rdl will cause report rendering issues.
KPR#:810613
Field label and value not shown if field is placed in the header or footer of the report template
KPR#:951644
Report template documentation can't be generated
KPR#:978287
Selected summary calculations changed after re-opening the column properties
KPR#:1118511
Intelligent Report Footer hides values of peak table when table continues to next page
KPR#:73111
Description on unsaved entries is incomplete in Audit Trail dialog
KPR#:249784
Non-identified peaks may be missing in reports with non-Agilent instruments data
KPR#:299468
"Delete" entry in the audit trail raises an audit concern
KPR#:389530
Tune Report: The autotune report does not include instrument name
KPR#:187399
User with empty password cannot unlock Acquisition or Data Analysis
KPR#:207007
Users can delete their own data without deletion permission via web client
KPR#:580868
Folder move requires Everything role
KPR#:976277
Users added to a domain group can't access content management
Keyword: Roles and Privileges,User Interface
KPR#:318470
Orphan Property ID leading to sync failure
KPR#:56
Chinese, Japanese, or Russian file names corrupted after download as a compressed zip
KPR#:79117
SIM table is disabled if the last method loaded was SIM
KPR#:90053
Copy paste a row in the SIM table causes the acquisition Client to crash
KPR#:99440
Cannot unlock session locked by user from different domain
KPR#:105332
Archive Offline feature has been removed in OpenLAB Server 2.1
KPR#:119122
One UIB II channel is acquired but two signals are displayed in Data Analysis
KPR#:130075
Search cannot handle Metadata which contains a µ
KPR#:131472
EI tune evaluation report displays incorrect limit for 502/69 ratio
KPR#:137961
Not able to filter system activity log based on Time
KPR#:168842
PDFs Which Include Localized Characters Can Appear Garbled in Web UI Previews
KPR#:180338
First time login to the Content Management Web UI can take up to 60s
KPR#:225514
Activity Log Not Viewable in Chrome 67 or later (ECM XT 2.2, 2.3)
KPR#:272423
Time displayed in QualA does not match local time if DST is not set correctly
KPR#:296392
No Tree in DA after CDS 2.3 Update 06 installation with CM
KPR#:306783
The information of the modified person on the folder is incorrect in the Datastore WebPage
KPR#:307134
Pagination disappears when search returns more than 250 results
KPR#:372530
Incorrect rendering of MS Office documents in preview
KPR#:407029
Storage System Test cannot be executed after changing account on ECM 3.x
KPR#:411974
Switching from domain to internal authentication can break security and storage tests
KPR#:576609
Backup Utility is failing fail at verification step due to exhausting connections to the MS SQL server
KPR#:589105
After running the server configuration utility, the Instrument service is not started
KPR#:605536
Error message occurs if server name in Storage Locations contains dot on Content Paths page
KPR#:611857
OpenLab Server Update 10 installed on an AIC without warning message
KPR#:623684
"modified" timestamp after sequence has been archived triggered by filtering for PDF
KPR#:665419
Japanese Language Files are not included in Content Management Security Update 01
KPR#:976274
Installation of Cary-UV server plugin removes Security and storage test.
KPR#:1050337
Test Services Workflow test is not compatible with Cary UV Instrument Controller
KPR#:58
Activity Log not displayed in web browser when using Chrome 5.1
Keyword: User Interface , Audit Trail
KPR#:58
Activity Log not displayed in web browser when using Chrome 5.1
KPR#:443407
Lost connection when launching an instrument from an RDS Remote Desktop
KPR#:44846
Processing Method Role issue
KPR#:354011
Data acquisition is interrupted on GCMS SQ when system is in failover mode
KPR#:468519
Data collection Service does not start after upgrade
KPR#:557485
Minimum required Windows 10 version is different in SPT and the requirements guide for v2.6
KPR#:570208
OpenLab v2.6 Update 01 can be uninstalled on a workstation file system
KPR#:590163
Port 8006 is not tested by SPT
KPR#:625497
Installation fails at the reverse proxy step due to port 5443 being used by another program
KPR#:670922
System preparation sometimes hangs at the Tcp Port Sharing and Activation step
Keyword:
One-line Description:
Source Parameters are not part of the tune file and are not saved/reloaded when loading tunes
Problem:
The users is allowed to change and download the source parameters when doing manual tune to run experiments, but those values will not be part of the tune file saved and will not be replaced with the source defaults with atunes is loaded
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
NGA/RGA Add-on Software revision 2.7 has wrong characters in Chinese font
Problem:
The characters of Chinese font in NGA/RGA Add-on Software revision is wrong.
Temporary Solution:
None
Fix Information:
This defect is planned to be fixed when the Gas Analyzer 2.7 is run on future OpenLab CDS version.
Keyword:
One-line Description:
Network issues with DHCP may cause unexpected behavior on a Workstation installation
Problem:
On a Workstation installation when the main network which is connected through DHCP drops and the network IP can change to default non-reachable IP address, communication with Shared Services/Automation Service could stop. This will adversly affect acquiring runs and the client application.
Temporary Solution:
Use STATIC IP address to avoid DHCP failures.
Fix Information:
n/a
Keyword:
One-line Description:
Delta EMV relations may not be obvious to users
Problem:
In the time segments table there are entries for positive and negative Delta EMVs. The values entered by the user get stored with scan segments of the same polarity. If the user sets up a method that is only positive polarity scan segments and enters a negative Delta EMV value, there are no scan segments to associate it with. When the method is saved, the negative Delta EMV value is not saved as it would have no meaning. Likewise the audit trail will not log an entry for this change in negative Delta EMV.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
Submitted or Validating run items will get aborted if connection to Shared Services is lost
Problem:
Any submitted or validating runs will get aborted if connection to Shared Services is lost in the mean time. All the pending runs will go to completion.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Charging voltage displayed as Nozzle Voltage in the check tune report for MultiMode Source
Problem:
The Charging voltage displayed as Nozzle Voltage in the check tune report for MultiMode Source.
Temporary Solution:
Users beware that there is a typo in the Checktune Report, it should be Charging voltage on the MultiMode Source(MMI) NOT Nozzle voltage.
Fix Information:
No fix available at this time. To be fixed in a later version
Keyword:
One-line Description:
A mismatch of configured custom plate will throw invalid location message.
Problem:
If user launches a pre-configured instrument where the configured custom plate does not match the hardware, then invalid location message is seen while validating the vials.
Temporary Solution:
Close instrument connection and re-configure the instrument to update the configuration, so it matches the hardware.
Fix Information:
n/a
Keyword:
One-line Description:
Connection problems with hardware could put the instrument in indeterminate state
Problem:
During an acquisition run, If connection problems are encountered between the hardware and the application, the software would abort the runs. The hardware is not aware of the disconnection and reconnecting to the hardware could put the instrument in indeterminate state.
Temporary Solution:
Perform a close connection and stop the hardware. Relaunch the application to get to a good state.
Fix Information:
n/a
Keyword:
One-line Description:
SmartCard 4 disk failure
Problem:
When the SmartCard 4 disk stop working, it require to reboot the SmartCard 4, closed the instument online conneciton and flash the firmware.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
LC/MS SIM/Scan parameters information are inaccurate in the report function
Problem:
For SIM/Scan time segments, both Scan and SIM rows will appear in the same scan segment table. Scan rows will appear first with their column information and SIM rows will be appended below and the columns appended after the Scan columns. Cells that do not contain information for the scan type will be blank.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
In case of overlap injections, "Stop sequence after current run completes" aborts the current run ONLY and discards the already prepared sample
Problem:
In the case of overlap injections, when user performs "Stop sequence after current run completes", only the current injection will complete its data acquisition. The already prepared sample (already in the autosampler's sample loop) for the next run will be discarded, the sequence will be aborted. When user run a subsequent sequence, an error will occur depending on the instrument technique (LC or GC) due to the leftover sample in the injector loop, user has to re-submit the same sequence to be able to continue.
Temporary Solution:
Re-submit the sequence to continue
Fix Information:
It is fixed in OpenLAB CDS 2.1. When user performs "Complete current run and abort sequence", sequence will be aborted after the data acquisition has completed for the already prepared sample (the overlapped sample).
Keyword:
One-line Description:
Printing administrative reports from OpenLAB Control Panel directly to a physical printer does not work properly
Problem:
As a system administrator, when user prints the administrative reports from OpenLAB Control Panel directly to a configured printer, the hard-copy printouts are blank pages.
Temporary Solution:
User has to print the reports as PDF files and then print the PDF reports on the configured printer to obtain your hadr-copy printouts.
Fix Information:
This issue has been solved in OpenLAB CDS 2.1.
Keyword:
One-line Description:
Activity Log does not show the negative values of method override parameters for LC/MS
Problem:
In the time segment, if there are scan segments with both polarity, the log will have two lines to say parameter name changes from xxx to xxx. One is for the positive polarity, the other one is for negative polarity. Whether the Positive comes first or negative comes first will depend on which polarity comes first in the scan segment. If there is only one polarity, there will be only one line in the log to specify the value has been changed to xxx to xxxx. There will be no indication to specify which polarity. User will need to find that out.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
Selecting multiple ranges of cells will not fill down as expected
Problem:
In the scan segments table, if the user selects a range of cells and clicks filldown (click-drag), the first cell selected will be the value used. If the user selects a range of cells and additional individual cells (click-drag followed by Ctrl-clicks), the first cell select will be the value copied. But if the user selects 2 ranges of cells (click-drag and Ctrl-click-drag) and clicks filldown for some reason the 1st cell of the *2nd* range is copied.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
Same injection time for multiple runs if Review data during running
Problem:
Customer performed a "Review Completed Injections", then the injection audit trail show different injection time but in the DA and the reports show the same injection time for followed runs.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Adjust Mass Peaks in Manual Tune does not automatic set the peak width back to 0.7 FWHM
Problem:
The Adjust Mass Peaks in Manual Tune does not automatic set the peak width back to default 0.7 FWHM it set will peak width to 0.8 FWHM. The peak width has a tolerances of +/- 0.1 FWHW
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
AJS source Sheath Gas Temp & Sheath Gas Flow parameters not validating in the Method Override
Problem:
If the user overrides either the sheath gas temp or sheath gas flow in the sequence method override, the system will not validate this against the allowable ranges for the other parameter. The override parameters that cannot be achieved, the firmware will prevent unsafe conditions and the system will remain “not ready”. Sequence override parameters have a single validation range and no way to check validation of another parameter. Users who use the sequence override conditions should be aware of the conditions they are using and the affect they have on the system; relationship between the Sheath Gas Temp and Sheath Gas Flow.
Temporary Solution:
Both parameters need to changed at same time. Flow : Temp 7.5, 400.0 6.5, 350.0 5.5, 300.0 4.5, 250.0 3.5, 200.0 2.5, 150.0 0.0, 20.0
Fix Information:
N/A- The information will be included in the Help file
Keyword:
One-line Description:
Post-run diverter position information is missing when creating a LC/MS report
Problem:
Post-run diverter position information is missing when creating a LC/MS report. Since the post run box did not get "checked", it means users do not want to setup for the post run therefore, the post-run diverter position information is not in the report.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
Changes to Manual Tune parameters have no respond in spectrum display windows
Problem:
Changes to Manual Tune parameters have no respond in spectrum display windows on all 61xxC Single Quad LC/MS. When making changes to the width gain/offset, mass axis/offset, or ion optics voltages, the spectrum display windows have no affect to the tune peaks.
Temporary Solution:
The workaround : 1) Switch ion polarity from Positive to Negative mode 2) Make change to MS parameters (i.e. width gain/offset, mass axis/offset or ion optics) 3) Download tune parameters to instrument icon button 4) Switch ion polarity back to Positive mode 5) Download tune parameters to instrument icon button
Fix Information:
Fix will be in the future release of LC/MS drivers.
Keyword:
One-line Description:
Signal Plot frozen and Run Queue shows "Acquiring" and data is inaccessible
Problem:
Online plot signal window can be frozen and the run queue can be stuck in "Acquiring" state even though the run is done. The data is not accessible. In DA the icon for the data set shows up as a folder icon, but will not have any results to open. The data structure is incomplete, but there is usually dx data and sometimes RX data.
Temporary Solution:
n/a
Fix Information:
Fix in 1.12.2
Keyword:
One-line Description:
Single Quad UI always display "Not Ready" state when the instrument in "Standby"
Problem:
Single Quad UI always display "Not Ready" when you put the instrument in" Standby" or turn off the device button because the "Standby" the Drying Gas Flow is 3.0 L/min. If the current method has a Drying Gas Flow settings greater than 3.0 L/min, then the UI always "Not Ready" when users put the Single Quad in Standby.
Temporary Solution:
Workaround: 1) Create a "Standby" SQ method with the Drying Gas Flow 3 L/min, Drying Gas Temperature 300C, and Nebulizer pressure 15 psi 2) Save the method 3) Download Standby method to the instrument before putting the Single Quad in Standby
Fix Information:
Fix will be in the future release LC/MS drivers.
Keyword:
One-line Description:
LC/MS data acquired with ions ending in .9 m/z will appear in EIC as two ions ending in .9 m/z and .91 m/z
Problem:
If your LC SQ acquisition method has ions that end in .9 m/z, the Extracted Ion Chromatogram (EIC) in Data Analysis will show two ions, one ending in .9 and one ending in .91 that is not part of the acquisition method. For example, 1696.9 m/z is specified in acquisition method to collect, but 1696.91 m/z also appears in the EIC even though this ion is not part of the method.
Temporary Solution:
n/a
Fix Information:
This issue is resolved by the LC/MS Driver that is included in OpenLAB CDS 2.2.
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:
PDF preview in DataStore is truncated in Chinese and English Secure Workstation
Problem:
PDF preview in the DataStore User Interface is not rendered properly and may look misaligned or truncated in Chinese and English Secure Workstation. The pdf document opens properly with any pdf reader when downloaded from the Data Store repository
Temporary Solution:
N/A
Fix Information:
Fixed with OpenLAB Server revision 2.1
Keyword:
One-line Description:
"Value contains illegal character' message is displayed while typing a new folder name
Problem:
While typing a folder name, the software will provide instant feedback and warn the user when an invalid character is entered. If you continue typing the "red" field will disappear until an invalid character is again detected. Folder names can't start or end with a space.
Temporary Solution:
n/a
Fix Information:
This issue will be addressed in the next version of the software
Keyword:
One-line Description:
Deleted content doesn't release space from the disk storage when using PostgreSQL as database engine
Problem:
Deleted content doesn't release space from the disk storage when using PostgreSQL as database engine Affected version: OpenLAB Data Store A.02.02 and OpenLAB Data Store 2.0
Temporary Solution:
n/a
Fix Information:
This issue is resolved with OpenLAB Server 2.1
Keyword:
One-line Description:
FIltering in File Details page does not work for ZIP filenames with Japanese character
Problem:
The problem is caused by Java interpreting the encoding from non-English Windows.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
Folder icon is missing on content page when using Internet Explorer 11
Problem:
This is can be fixed by changing the rendering in the Intenet Explorer options "Use software rendering instead of GPU rendering* Related issue reported here: https://issues.alfresco.com/jira/browse/MNT-13231 Steps are given here: https://support.microsoft.com/en-us/kb/2528233
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Clicking on the "Browse" button to Upload Files does not trigger the "browse window" in IE11/Win10
Problem:
This is a known issue and will be fixed in the next revision of the software.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Users can't log in with domain authentication - Message User must change Password
Problem:
When using Windows Domain Authentication, the message "User must change the password" is displayed even when this is not correct.
Temporary Solution:
When using Domain Authentication, the application needs to read user attributes like userAccountControl (https://msdn.microsoft.com/en-us/library/ms680832(v=vs.85).aspx) and pwdLastSet (https://msdn.microsoft.com/en-us/library/ms679430(v=vs.85).aspx) In order to get information whether or not a user must change password. When read permission is not granted to the user, the application will assume that the password of the user expired and will refuse the access Steps to enable the permissions to read attributes: 1 Open Active Directory Users and Computers 2 In the View menu, click Advanced Features 3 Under Users, select a user that is not able to log in to OLCP 4 Right click and go to properties 5 In the Security tab, click select 'Authenticated Users' 6 Check 'Read' checkbox below and click OK
Fix Information:
n/a
Keyword:
One-line Description:
WEB User Interface returns Error 500 after rebooting the server
Problem:
If rebooting the OpenLAB Server, and the tomcat service starts before the database instance is up and running, you will have a database connection issue returning and error 5600 on the web interface. There are no dependencies between Tomcat and external databases resources.
Temporary Solution:
Ensure the dabase server is up and running before rebooting the OpenLAB Server.
Fix Information:
N/A
Keyword:
One-line Description:
Deletion of Files in Content Management - Freeing of Disk Space
Problem:
When you delete contents in DataStore or OpenLAB Server 1) DataBase: Contents in database will be deleted. Database size might not be reduced due to activity log information being written to the database and also some database size might not be reduced even the contents are deleted. 2) Solr index: Solr index size will not be reduced unless you click on the "optimize now" button in Solr Admin user interface 3) Content Store: Content Store size will be reduced when you delete files in DataStore. A clean-up job runs everyday at 11:00 PM to clean the content store folder.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Preview not available if size is larger than 10MB for certain files.
Problem:
In Content Management, preview feature is not available for certain file types that exceed a size limit. This limit is 10 MB for the file types mentioned below Office Documents ( .doc, docx, .xls, .xlsx, .ppt, .pptx ) CSV files ( .csv ) TXT files ( .txt ) XML files (.xml)
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Web UI - Characters are not being previewed and some are correctly converted
Problem:
Alfresco expects UTF-8 encoding on all documents for previews to work correctly on extended characters. Cause: Notepad saves .txt files as ANSI by default, which is incompatible with Alfresco.
Temporary Solution:
n/a
Fix Information:
Solution: In Notepad, do "Save As..." to save the file in UTF-8 format instead of the default ANSI, and upload the file to CM for extended characters to be previewed correctly.
Keyword:
One-line Description:
Reprocessing on an archived project should generate error
Problem:
OpenLAB CDS does not check when a project is archived in OpenLAB Data Store 2.0 or in OpenLAB Server 2.1. It is therefore possible to select the archived project to load results, modify and save them. The application will then try to upload the modify results and an upload error will occur in the upload queue. As a temporary solution, we recommend to remove the Project_Edit_Content permission on archived projects.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
After an upgrade to CDS 2.1, the reporting tab is missing for some users
Problem:
When a custom role for creating and modifying Reports is assigned to users. After an upgrade to CDS 2.1, Any user assigned this role will no longer be able to create reports. The Reporting tab will be completely missing for them
Temporary Solution:
n/a
Fix Information:
This issue is planned to be fixed with CDS 2.3
Keyword:
One-line Description:
RDL files downloaded via the web interface through Internet Explorer are saved with the wrong extension
Problem:
When a user chooses to download an RDL file from the web interface in Internet Explorer, the file itself is saved with the wrong extension (typically a .bin or .txt extension).
Temporary Solution:
as a temporary solution, yo can download using a different browser (such as Chrome), you can also choose to right-click and "Save As" instead of a standard click to to download or rename the file back with the correct extension.
Fix Information:
n/a
Keyword:
One-line Description:
Misleading audit trail entries when running an imported sequence from results without saving
Problem:
When user imports a sequence from a result set, makes changes to the sequence, and runs the modified sequence without explicitly clicking "Save" to save the sequence, the audit trail entries for the modified sequence in result set is misleading.
Temporary Solution:
The workaround is to save the sequence first by clicking "Save" before running it or submitting it to run queue.
Fix Information:
n/a
Keyword:
One-line Description:
Add/Update does not use manually integrated peaks
Problem:
Manually integrated peaks are not found when Add/Update is performed.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5.
Keyword:
One-line Description:
License error occurs after upgrade from OpenLAB CDS 2.0 to 2.1
Problem:
After upgrading from OpenLAB CDS 2.0 to 2.1, the following error message appears when launching an instrument: "Failed to connect to the instrument Not enough license features -Agilent OpenlabCDS Core" This error is due to the name change of the core license from AgilentOpenLABCore" in OpenLAB CDS 2.0 to "AgilentOpenLABCDSCore" in OpenLAB CDS 2.1.
Temporary Solution:
n/a
Fix Information:
To resolve this issue, regenerate the license from SubscribeNet (https://agilent.subscribenet.com) and use the new license file in OpenLAB CDS 2.1.
Keyword:
One-line Description:
Software Verification report of Agilent Data store Fail While upgrading Server of A.04.07 SR1 to A.04.07 SR2
Problem:
Running the Software Verification Tool (SVT) with a user other than the user who did the upgrade will result in a failed report.
Temporary Solution:
The user performing the upgrade should be the user that runs the SVT tool.
Fix Information:
n/a
Keyword:
One-line Description:
Old DS Icon visible on Internet Explorer Tabs after an upgrade
Problem:
The original DS favicon (icon) is visible in the Internet Explorer Tabs and address bar if the system was updated from version 2.0 to 2.1 or 2.2
Temporary Solution:
n/a
Fix Information:
Clearing manually browser's cache forcing it to download all latest data from a website, and this is done only one time after the system is upgraded with latest version.
Keyword:
One-line Description:
When two Agilent LC instruments with VWD are running sequences on one Workstation or AIC, the sequence aborts after 55 minutes of runtime on one of the LC instruments.
Problem:
With multiple instruments starting at about the same time, longer run times, sequence or single runs may abort with the error “Store must be open for this operation” in the Activity Log. For example, with an Agilent VWD detector or 1220 LC Compact System, a run time of 55 minutes or higher can cause this condition. This error occurs due to a Microsoft .NET issue with multiple program threads writing to a temporary Windows file where the signal size exceeds 10MB. For the VWD or 1220 in particular, the reference and sample intensity instrument traces store enough data to exceed this size in about 55 minutes. This issue only occurs when more than one instrument will exceed the required signal size. For example, if using one instrument with a VWD detector and one with PDA, the PDA may not generate the required signal size and the issue will not occur.
Temporary Solution:
n/a
Fix Information:
This is resolved in OpenLAB CDS v2.1 SR1, and OpenLAB CDS v2.2.
Keyword:
One-line Description:
An issue has been identified when installing OpenLAB CDS directly from USB install media. The installation stalls at .NET Framework 4.5 install and will not proceed.
Problem:
On PCs that do not have Microsoft .NET framework 4.5 or later installed, when you run setup.exe directly from the USB install media, the installer will start installing .NET Framework 4.5 and will try to write some of the components on the install media. Since the install media is read-only, writing the media is not possible and as a result the install is stalled.
Temporary Solution:
To avoid this, copy the entire content of the installer to your local drive, remove the USB media from the PC, and run setup.exe from the local drive. If you do not remove the USB media, the same error will occur.
Fix Information:
n/a
Keyword:
One-line Description:
Running a method with a tune file that has never been tuned will crash the acquisition Client
Problem:
If a GC/MS method is run with a tune file that has not yet been tuned, the acquisition Client will crash.
Temporary Solution:
n/a
Fix Information:
This issue will be resolved in a future release of GC/MS driver for OpenLAB CDS.
Keyword:
One-line Description:
Result type "Unknown" in Data Analysis search results after an upgrade to CDS 2.1
Problem:
After upgrading a Workstation or a Client Server environment from 2.0 to 2.1 Searching results in Data Analysis will show "unknown" for results acquired with CDS 2.0.
Temporary Solution:
n/a
Fix Information:
The result type field extraction has been added in version 2.1. Search will properly populate this field for newly acquired results or after reprocessing results acquired in CDS 2.0
Keyword:
One-line Description:
Current acquiring and pending runs get aborted in case of database disconnection
Problem:
When using an external database server, if the database is disconnected, but the communication between OpenLAB Server and AIC stay intact, the current acquiring and pending runs will get aborted.
Temporary Solution:
The communication to database server should not be interrupted during data acquisition.
Fix Information:
n/a
Keyword:
One-line Description:
Installed Start Menu Shortcuts (on the Server) will not work if the Default Browser on the Server is not set
Problem:
Clicking on the shortcuts for Bulk Import Utility and Content Browser will bring up an explorer app with an error saying the page cannot be displayed. Affected versions: OpenLAB Data Store 2.0 and OpenLAB Server 2.x
Temporary Solution:
n/a
Fix Information:
If the default browser is not set on the server, these errors will occur for this application (and all applications that have internet shortcuts on the start menu). Set the default browser to Internet Explorer to avoid this problem.
Keyword:
One-line Description:
Double upgrades from DataStore A.0x to OpenLAB Server 2.1 will cause "Alfresco_administrators" group to be missing.
Problem:
During the upgrade to OpenLAB Data Store 2.0, a group called Alfresco_administrators is added to the application, but when an additional upgrade is done before like for instance from A.01.02 to A.02.01 and then to 2.0, the group will not be created and will cause the upgrade to OpenLAB Server 2.1 to fail.
Temporary Solution:
As a temporary solution, the following two steps need to be done before upgrading to OpenLAB Server 2.1 1. The missing group "ALFRESCO_ADMINISTRATORS" needs to be created manually in the Alfresco Share. 2. The DataStore_System user and the Administrators group must be added to the newly created group.
Fix Information:
n/a
Keyword:
One-line Description:
Delete file action in content management does not ask for a reason for deletion
Problem:
Delete file action in content management will not ask for a reason for deletion nor ask for a second login. Deletion of files can only be done from users having the "Manage Security" privilege or the "Everything" Role. The deletion will be traced in the Content Management Activity Log
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
System Timeout Exception error occurs when OpenLAB Control Panel is kept open
Problem:
On a Client, after closing the instrument connection but keeping the OpenLAB Control Panel open, the system times out and throws a System Timeout Exception error. No data is lost.
Temporary Solution:
The user can simply start OpenLAB CDS Control Panel again.
Fix Information:
This issue will be resolved in future OpenLAB CDS release.
Keyword:
One-line Description:
Some LC Help contents not shown
Problem:
Some LC instrument topics are not shown in Help and Learning.
Temporary Solution:
Press F1 in the Acquisition method window to access .CHM formatted Help. Topics are available in this format.
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword:
One-line Description:
Exception when logging in OpenLab Control Panel. ECM does not display all subfolders when browsing for Project Path during project creation; exception is displayed
Problem:
When the user creates projects, the standard procedure is to browse to the folder Location when selecting the Project Path. However, there are more than 100 sub-folders, it is not possible to set the project path correctly, because when browsing, the ECM window displays only the first 100 folders. The following exception is displayed: "Agilent.OpenLab.SharedServices.SharedServicesInternalException: The incoming request has too many parameters. The server supports a maximum of 2100 parameters..." An exception also occurs when logging into OpenLab Control Panel: "Agilent.OpenLab.SharedServices.SharedServicesInternalException: The incoming request has too many parameters..."
Temporary Solution:
n/a
Fix Information:
The issue is resolved in OpenLab CDS 2.3. It is also resolved in OpenLab Shared Services (OLSS) 2.1 Hotfix 4.
Keyword:
One-line Description:
Network disconnection prevents result set from being completely uploaded to Content Management
Problem:
If a network disconnection occurs while uploading a result set via the Failover Uploader Tool, then a result set will be partially uploaded to Content Management (CM). Partial result set cannot be opened in Data Analysis. The whole result set is still cached locally on the AIC. However, re-upload the result set is not possible if the partial result set exists on CM server.
Temporary Solution:
The temporary fix is to first delete the partial result set from the Results folder under the project directory on CM server and then use the Failover Uploader Tool again to upload the complete result set.
Fix Information:
n/a
Keyword:
One-line Description:
Exported data to AIA with OpenLab CDS 2 cannot be loaded in TCM fingerprint software
Problem:
Exported data to AIA with OpenLab CDS 2 cannot be loaded in TCM fingerprint software.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.6.
Keyword:
One-line Description:
Current acquiring and pending runs get aborted during database disconnection
Problem:
When using an external database server, if the database is disconnected, but the communication between OpenLAB Server and AIC stays intact, the current acquiring and pending runs will get aborted.
Temporary Solution:
The communication to database server should not be interrupted during data acquisition.
Fix Information:
n/a
Keyword:
One-line Description:
"Close Data" in Data Analysis does not respond
Problem:
Clicking the "Close Data" the button does not work if you are in working in the Method sections and the Sequence or Result Set is selected.
Temporary Solution:
Select the Injection and not just the Sequence/Result Set before you click the "Close Data" button.
Fix Information:
n/a
Keyword:
One-line Description:
Custom Compound Field values are not saved with result set
Problem:
If SIM result set contains custom compound fields, the custom compound field values are reset to default values after the user performs either of the following: • Add peak as compound to method • Add / Update MS compounds This issue does not occur with Scan data.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword:
One-line Description:
Data lost after sequence completed successfully but .dx files cannot be found
Problem:
The sequence completed successfully, however, the result set contains sequence and method files, but no .dx files.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3, v2.2 Update 2, and v2.1 SR1 Hotfix 5.
Keyword:
One-line Description:
MS signals may not appear in Data Analysis after acquisition
Problem:
MS signals acquired with a LC/MS or a GC/MS may be missing in Data Analysis due to an inconsistent signal information stored in the results (time segment information). In such cases, the online signals can be seen in the Acquisition signal plot, but would not be accessible in Data Analysis. The issue can occur intermittently or persistently depending on the considered system and method used for acquisition.
Temporary Solution:
Please contact your local Agilent Technologies support representative.
Fix Information:
The issue will be fixed in OpenLab CDS v2.2 Update 03, and in further major software releases, starting from OpenLab CDS v2.3.
Keyword:
One-line Description:
Cannot start Acquisition and Data Analysis on Terminal Server for all users
Problem:
Every couple days, Acquisition and Data Analysis cannot be started on Terminal Server for all users. In both cases, the start up process is stuck after calling AddServicesLogMessageAboutApplicationStarted.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3 and v2.2 Update 4.
Keyword:
One-line Description:
Peak(s) are not integrated using EZChrom Integration
Problem:
Some Peak(s) using the EZChrom Integrator are not integrated. All is working properly with the ChemStation Integrator. Data Analysis makes sure that the signals to be integrated always start at zero. If the signal does not start at zero, a new data point at zero is added (as the first element) to the data arrays and a re-sampling is done. Adding a new data point at zero at the start of the data array works as long as the smallest original x value is larger than zero. However, if the first x value is negative, adding a new data point at zero will lead to the fact that the signal x values are no longer monotonically increasing,
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3
Keyword:
One-line Description:
Reason for changes - OK button not available
Problem:
When a reason for changes has to be entered, the OK button in the window is disabled.
Temporary Solution:
In the "Reason for changes" window, select the check box for "Apply same reason for all injections". This will enable the OK button. After that uncheck the "Apply same reason for all injections" and the OK button remains enabled.
Fix Information:
This issue will be fixed in a future release of OpenLab CDS.
Keyword:
One-line Description:
Running sequences with methods or report templates with long file names can prevent the result set from being created correctly
Problem:
When acquiring data, several files are copied into the result set folder. If one of these files exceeds the limit of 247 characters, it will cause issues with storing the data. Before running a sequence in Acquisition, the maximal length of the result set name is calculated as: Projectpath + result set name + ".rslt" + result set name + ".acaml" The maximal length (total path including file name) to must be lower than 247 characters. If it is higher, the run cannot be started. This verification does not take into account the long file names for report template and acquisition method, which can cause the result set to not be created correctly.
Temporary Solution:
It is advised to not use file names containing more than 60 characters for: - report templates - acquisition methods
Fix Information:
The situation will be addressed with the OpenLab CDS 2.4.
Keyword:
One-line Description:
The data system does not display what changed when it declares a configuration changed event.
Problem:
When the GC is idle and a method with a different configuration such as column film thickness is downloaded, the Activity Log reports the details of what has changed. But during a run, GC configuration changes are not allowed. The message "Configuration change notification received but ignored because run queue was not idle" indicates this without outlining details as to which configuration change was requested. A rejected "soft" configuration change request, e.g. a new column film thickness, does not lead to an abortion of the run. The Activity Log entry is to alert the user to review and resolve the method settings before running a single sample or sequence.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Incorrect Instrument name shown in Sample information in DA and reporting
Problem:
After an instrument is renamed while it is idle, the old name is still recorded in the acquired data.
Temporary Solution:
The correct way to rename an instrument is: 1. Select "Close Connection" for the instrument to be renamed 2. Rename the instrument 3. Start Acquisition again In case data was already acquired, the instrument name can't be changed for this data. A "Close connection" also updates the instrument name if selected after changing the instrument name.
Fix Information:
n/a
Keyword:
One-line Description:
Cannot launch Data Analysis or Acquisition due to corrupted user configuration file
Problem:
When Data Analysis or instrument client was launched from OpenLab Control Panel, an exception occurred due to a corrupt user.config file.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4, OpenLab CDS v2.3 Update 03, and OpenLab CDS v2.2 Update 05.
Keyword:
One-line Description:
Upgrade from v2.1 fails when the application is installed on a folder name with short name
Problem:
Upgrade from v2.1 fails when the application is installed on a folder name with 2 or less characters
Temporary Solution:
Do not install the application on folder where the name is less than 3 characters
Fix Information:
n/a
Keyword:
One-line Description:
Special characters in OpenLab/ECM XT Server administrator password cause AIC or client installation to fail
Problem:
Special characters in OpenLab/ECM XT Server administrator password cause AIC or client installation to fail.
Temporary Solution:
The characters currently supported for administrator's password are: A-Z, a-z, 0-9, underscore (_), dot (.) and dash (-).
Fix Information:
Resolved in OpenLab CDS v2.4.
Keyword:
One-line Description:
ADF file cannot be opened by the user that started the analysis
Problem:
An ADF file created during acquisition cannot be directly opened by the user that started the analysis. When trying to open it with ADFexplorer, the user is told to contact the file owner or an administrator to obtain permissions. Workaround: copy the files to another location then the files can be opened.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Adjust Mass Peaks in Manual Tune does not automatic set the peak width back to 0.7 FWHM
Problem:
The Adjust Mass Peaks in Manual Tune does not automatic set the peak width back to default 0.7 FWHM it set will peak width to 0.8 FWHM. The peak width has a tolerances of +/- 0.1 FWHW
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
On systems with OpenLab CM installed (workstations or client / server) using a PostgreSQL database, the Windows application log contains many errors.
Problem:
On systems with OpenLab CM installed (workstations or client / server) using a PostgreSQL database, the Windows application log contains many errors like ERROR: duplicate key value violates unique constraint "idx_alf_conturl_cr" DETAIL: Key (content_url_short, content_url_crc)=(574d8e0d.bin, 643884882) already exists. STATEMENT: insert into alf_content_url (id, content_url, content_url_short, content_url_crc, content_size, orphan_time) values ($1, $2, $3, $4, $5, $6)
Temporary Solution:
As a workaround you can change the type of logging PostgreSQL does: In the file postgresql.conf change the line with the parameter log_min_error_statement to log_min_error_statement = fatal This would prevent application-level failed statements from being logged at all. The DB startup/shutdown messages can also be toned down to only include errors: log_min_messages = fatal
Fix Information:
The error messages: ERROR: duplicate key value violates unique constraint "idx_alf_conturl_cr" can be ignored This is a known issue. According to Alfresco Engineering, do not worry about it if you are ONLY seeing this issue: 1. in PostgreSQL database and not other databases (eg. MySQL, etc) 2. logged in PostgreSQL locking' policy means that sometimes concurrent transactions collide and hit unique constraint errors. These are normally silently retried by alfresco. But unfortunately, the default PostgreSQL configuration logs these to their log. The "duplicate key violation" exceptions are produced by copy/paste, versioning and a number of other well-handled conditions, including ANY concurrency violation.
Keyword:
One-line Description:
Error loading data (invalid or missing checksum) if one of ACAMLs is corrupted
Problem:
When loading bunch of single injections, "error loading data (invalid or missing checksum)" occurs if one of the injections has ACAML that is corrupted. As a consequence, nothing is loaded.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 11.
Keyword:
One-line Description:
License error: Content Manager cannot be used in cluster system intermittent
Problem:
Intermittently the error "There is no Content Management Server license" is displayed when the OpenLab Control Panel is started. This is caused by the fact that only three servers can be used as license servers in a cluster. In case the fourth server of the cluster is interrogated by the client to provide a license, the error is displayed.
Temporary Solution:
Only configure three servers to be used for load balancing. The third server can be used as a separate index server. This requires OpenLab CDS 2.3
Fix Information:
n/a
Keyword:
One-line Description:
No error message shown when entering forbidden symbols in server name or instance name
Problem:
The validation process will pass when entering forbidden symbols in the server name.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Data cannot be loaded after a previous "Load Data" cancelation
Problem:
After a prior "Load Data" that was canceled while loading, sometimes Data Analyisis is not able to load the data anew. Instead it shows a message that this data is already loaded when trying to load. As a temporary workaround until this defect will be fixed in CDS 2.5 the user can close Data Analysis, restart it and load the data again. Prior to closing, all unsaved data should be saved.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
E-signature information may get lost from a signed result set
Problem:
E-signature information may get lost from a signed result set due to a timing issue.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue and this issue is fixed in OpenLab CDS v2.4, OpenLab CDS v2.3 Update 07 and OpenLab CDS v2.2 Update 08.
Keyword:
One-line Description:
Acq. method modified date is incorrect for new created result set
Problem:
In a result set created from a different result set, the values for the following fields are empty: Fields->Injection->Acq Method Modified Date Fields->Injection->Acq Method Version Fields->Injection->Acq Software
Temporary Solution:
The “Acq Method Modified Date” is correctly available in: Method Information->Single Acquisition Method Parameter->Method_Information.ID_Method_Modified
Fix Information:
n/a
Keyword:
One-line Description:
Printed files stuck in the upload queue if files are being used
Problem:
From Data Analysis, when clicking on 'Print All', the files (pdf, docx, etc) are correctly generated. However, when opening one (or several) file(s), like open the excel file in Excel, the Pdf in Acrobate Reader, the docx in Word, and trying to print again, the files are stuck in the upload queue with an error message, while in DA, user feedback is the files were successfully generated. In the activity log of the OpenLab Control Panel, it is also written that the printing was successful. All other files uploaded afterwards are pending and therefore can also not be uploaded. When closing the application(s) (pdf, docx, etc), the upload queue gets unblocked and all files pending will be uploaded.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Instrument activity log entries could be missing after an upgrade
Problem:
After upgrading to OpenLab CDS 2.2 or 2.3, instrument activity log entries could be missing. The issue is fixed in release 2.4
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
The "Modifier" value of a folder created by a project creation in OpenLab Control Panel is set to "System" a few minutes after the folder is created.
Problem:
In Content Management, the "Modifier" value of a folder resulting of a project creation in OpenLab Control Panel is set to "System" a few minutes after the folder is created. The "Modified Date" is also updated, even if there was no change done to the folder. This change is caused by the synchronization between the OpenLab Control Panel and the Content Management happening every 5 minutes. This scheduled sync process runs as the 'system' user. It updates the permissions on the folder performed by user 'system' and also updates modifier" to 'system' and "modified date" to current timestamp . Affected version(s): v2.3, v2.4
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab Server v2.5 and Openlab ECM XT v2.5
Keyword:
One-line Description:
Instrument models type not being updated when method is saved
Problem:
If user opens an G61XXC method on a different model G61XXC and save the method, the new model information is not saved in the method on OpenLab CDS 2.2, 2.3, or 2.4. The audit trail will display the incorrect instrument model. For example: a. Create a method in G6120C system with LCMS 2.2\2.1 driver. b. Open the method in G6135 C system in LCMS 2.2\2.1 driver. Save it. c. Now, open the method on a LC/MSD iQ, the Audit trail shows. "Model changed from G6120C to LC\MSD iQ". Which is not correct because it was G6135C method which is opened in LC/MSD iQ not G6120C.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
Incorrect wording in Audit trail when method migration into OpenLab CDS 2.4
Problem:
a. Created method with 2.1 LCMS driver with “Calculate scan times from peak width (min)” set to 0.5. b. Migrated the method to LC/MSD iQ. Audit Trail has entries “Targeted Points Per Second changed from 0.5 to 1” and “Targeted Points Per Second Enabled changed from True to False”. While migrating the 2.1 driver method to LC/MSD iQ 2.3 driver, the Audit Trail shows 'Calculate scan times from peak width (min)' as 'Targeted Points Per Second'. This is not correct because peak width is different than points per second. It also shows that “Targeted Points Per Second Enabled changed from True to False”, which is not correct because there is no ‘Targeted Points Per Second’ in 2.1 LCMS driver.
Temporary Solution:
N/A
Fix Information:
N/A
Keyword:
One-line Description:
"Manage Security" is restricted to delete files/folders outside of a project
Problem:
With the privilege "Manage Security" you can delete files/folders in Content Management - as long as the files/folders are not within a project! When in a project, only projects related privileges are applied, therefore it will not be possible to delete files in a project if you have the Manage Security privilege Inside a project, there is also a role called everything. If you grant this role to a user within that project, he will be able to do everything, including deleting files. Manuals and online help will be improved to point this behavior out more clearly.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
CDS2.3 Update 5 cannot be installed
Problem:
In case customer is using an external NAS ... the user for the Tomcat service is not local system but as example openlabadmin This leads to the problem that the installation of CDS 2.3 Update 5 stops at 33% because the user for the Tomcat service is switching to local system during the installation and therefore was not able to start the service (got stuck at 700 MB).
Temporary Solution:
Stop the Tomcat service manually and change the user to e.g.: openlabadmin again. Afterwards the service started and the update will proceed.
Fix Information:
This issue is fixed in the OpenLab CDS v2.5 OpenLab ECM XT v2.5 This issue is fixed in the following updates: OpenLab CDS 2.4 Update 6 and OpenLab ECM XT 2.4 Update 02 OpenLab CDS 2.3 Update 10 and OpenLab ECM XT 2.3 Update 07 OpenLab CDS 2.2 Update 07 and OpenLab ECM XT 2.2 Update 01
Keyword:
One-line Description:
Data are not present in ECM after the run completed successfully
Problem:
On a client/server system integrated with ECM 3.x, there are cases where the run completed successfully but the data are not present in ECM. 1. Missing ECM privileges. A CDS user who submitted the run does not have read/write permission to the folder (CDS project) created on ECM. 2. ECMAPI service stopped on the AIC
Temporary Solution:
n/a
Fix Information:
This issue has been fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 07.
Keyword:
One-line Description:
Sequence run get aborted upon submission when downloading failed due to network disconnection
Problem:
On a client/server system, a sequence run may get aborted immediately upon submission at the time when there is network disconnection between AIC and OpenLab Server/ECM XT. The network disconnection will cause file downloading failure, which will further leads to abort the sequence.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Missing documentation for the Deleted Objects filter in the System Activity Log
Problem:
In the OpenLab Control Panel System Activity Log there is an "Object Deleted" filter for the Subsystem Instrument which is not explained in the OpenLab Help. This item is used for viewing activity log entries for instruments that have been deleted (there is a separate activity log entry for the administrator action to delete the instrument). The entries with "Object Deleted = Yes" are about actions that have been taken on the instrument. They do not relate to items created by the instrument such as sequences, methods, results, etc. As Activity Log entries themselves are never deleted, this way also entries for deleted instruments can be reviewed.
Temporary Solution:
Use this software status bulletin as documentation of the Deleted Object filter.
Fix Information:
OpenLab Help will be updated in a future version to describe the Deleted Object filter.
Keyword:
One-line Description:
Instrument electronics may not be ready during the first measurement in a method
Problem:
Instrument electronics may not be ready during the first measurement in a method
Temporary Solution:
n/a
Fix Information:
LC/MS Driver 2.4.452 / ESW 6.72.28
Keyword:
One-line Description:
OLSS passwords are not hidden in logs
Problem:
Passwords for OpenLab Shared Services are not hidden in installation logs.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 07.
Keyword:
One-line Description:
Alfresco Tomcat Service Credentials Lost
Problem:
The installation of OpenLab Server 2.4 Update04 / ECM XT 2.4 Update 01 on respective server will fail / get stuck if the customer’s server is using UNC paths to store data or uses domain users to run alfrescotomcat/content management search service. During the installation of the patch, the users will be reset to the respective service System accounts of the local machine.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in the OpenLab CDS v2.5 OpenLab ECM XT v2.5 This issue is fixed in the following updates: OpenLab CDS 2.4 Update 6 and OpenLab ECM XT 2.4 Update 02 OpenLab CDS 2.3 Update 10 and OpenLab ECM XT 2.3 Update 07 OpenLab CDS 2.2 Update 07 and OpenLab ECM XT 2.2 Update 01
Keyword:
One-line Description:
Methods that are saved in any subfolders of Project\Methods folder can be overwritten
Problem:
CDS does not allow to overwrite an existing method in Project/Methods folder, however it allows to overwrite an existing method in Project\Methods subfolders with a warning message.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 07.
Keyword:
One-line Description:
Data failed to upload when reprocessed in failover mode
Problem:
Failover Results Uploader failed to upload raw data files reprocessed in failover mode to the Content Management. As a result, when the result set is loaded in DA, no chromatogram can be viewed.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue. A fix is provided in the following release: OpenLab CDS v2.5 OpenLab CDS v2.4 Update 07
Keyword:
One-line Description:
"Injection aborted" information may not be recorded in its injection audit trail due to unstable network
Problem:
Sequence or single sample analysis will be interrupted hence aborted when running an Agilent LC due to unstable/flaky network. However, in some cases, the reason why the injection was aborted may not be recorded in its injection audit trail due to the timing issue.
Temporary Solution:
Ensure a stable network
Fix Information:
The issue has been fixed.
Keyword:
One-line Description:
Installation issue when using localized characters
Problem:
The data repository part of the OpenLab CDS and ECM XT installation is getting installed on a fixed folder. This is due to issues when using localized characters in the installation folder.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Configuration not available for "ServerWithECM3x~Win2019" in System Preparation Tool
Problem:
The System Preparation Tool configuration for Shared Services Server of CDS 2.5 for ECM 3.x on Windows Server 2019 is missing. Installation of an CDS 2.5 Shared Services Server is supported on Windows Server 2019.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SPT: update applied for Fast User Switch setting but not reflected in Group Policy Editor
Problem:
The SPT report shows that the "System - Local Group Policy Requirements" setting PASSed. The “Set Hide entry points for Fast User Switching” is applied correctly by SPT. However, since SPT is disabling the feature in the Windows registry, the change is not reflected in the Group Policy Editor and will be displayed as Not Configured. To verify the Fast User Switching is not available for the user, open regedit and go to the 2 registry keys: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Policies\System Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System and look for: "HideFastUserSwitching"=dword:00000001
Temporary Solution:
Fix Information:
n/a
Keyword:
One-line Description:
Concentration mass % of timed groups with cross-referencing DAD signals is not calculated for unknown peaks
Problem:
If the result set has two signals (DAD1A and DAD1B) and two compounds. One compound per signal (Compound Signal A on DAD1A, compound Signal B on DAD1B). And two timed groups with "quantify each peak individually" activated and calibration mode "reference". In the calibration settings calculate concentration mass % is activated. If then timed group A is assigned to DAD1B and referenced to Signal A (DAD1A) and timed group B is on DAD1A and reference is Signal B (DAD1B) the calculation of the concentration mass% gets screwed up. In this case only the amount of the unknown peaks gets calculated but not the concentration mass %.
Temporary Solution:
Only use peaks from a single signal for quantification with timed groups
Fix Information:
This issue is fixed in following versions: OpenLab CDS v2.5 OpenLab CDS v2.4 Update 08 OpenLab CDS v2.3 Update 12
Keyword:
One-line Description:
Purification in OpenLab CDS 2.5 - Error when using legacy Fraction Collector Cluster with added Recovery collector
Problem:
When using OpenLab CDS 2.5 together with the legacy Fraction Collector Cluster (supporting G1364A/B/C and G5664A), an error can occur during sequence setup. The error is caused by using the graphical "Sample Trays" UI when one of the collectors in the cluster is used as Recovery collector.
Temporary Solution:
As a temporary workaround, users are asked to not use the graphical "Sample Trays" UI when setting up sequences for the Legacy Fraction Collector Cluster.
Fix Information:
There is no fix for this issue at the moment.
Keyword:
One-line Description:
Services for CM - Installer overrides cache folder value to default during installation and reinstallation
Problem:
The installer overrides the cache folder value to default during installation and reinstallation for 'Services for CM'.
Temporary Solution:
n/a
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword:
One-line Description:
35900 A/D version in SVReport do not match Programs and Features
Problem:
The Agilent 35900 A/D version listed in OpenLab CDS Software Verification report (SVReport) and Control Panel Programs and Features do not match.
Temporary Solution:
n/a
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword:
One-line Description:
Instructions to deploy .NET Framework 3.5 offline.ps1' script are incorrect
Problem:
Instructions to deploy .NET Framework 3.5 offline.ps1' script are incorrect.
Temporary Solution:
n/a
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword:
One-line Description:
Project cannot be created when the system configuration is changed to a network location
Problem:
Shared a network path folder on disk D:\ and set all permissions correctly. When creating a project, the following error is shown: Sequence Templates must be a folder or subfolder within the directory.
Temporary Solution:
n/a
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword:
One-line Description:
Walkup 4.0 generates enormous size of log files
Problem:
Walkup 4.0 running on OpenLab CDS generates enormous size of log files.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.4 Update 07.
Keyword:
One-line Description:
Verification of QualA Tests is case sensitive
Problem:
If You start QualA (Test Services) and configure Storage System Test and Security Test to use admin and non-admin user for the test, but use different case than the case in the system (for example enter "AdMiN" instead of "admin" for admin user), the tests are failing in activity log verifications.
Temporary Solution:
Ensure that the usernames provided in the Storage System test and Security test are typed with the same cases as setup in the Control Panel.
Fix Information:
The Issue is fixed in QualA 3.4
Keyword:
One-line Description:
QualA System Report Test status is "Not Available" if certain software is installed on the machine
Problem:
System Report Test assembles the list of installed software on the machine where it is executed. One of the places from where this information is obtained is registry, the test iterates through the entire set of sub-keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. If any of the sub-keys contains a value which is not of the expected type, the test will crash when reading this value from the registry, and the result is that the report is not generated and the test result status is "Not Available".
Temporary Solution:
n/a
Fix Information:
The Issue is fixed in QualA 3.4
Keyword:
One-line Description:
Power save mode on network card not detected correctly by SPT
Problem:
The System Preparation Tool (SPT) reports that the power save mode was disabled for a network card but it was actually enabled.
Temporary Solution:
n/a
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword:
One-line Description:
Could not execute and complete SPT call if running installer from a different location on the computer
Problem:
Running installer (setup.exe) from a different location other than the original causes the System Preparation Tool (SPT) tool to fail to run. Error message: Could not execute and complete SPT call is shown.
Temporary Solution:
n/a
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword:
One-line Description:
Port 6629 is required for communication
Problem:
Port 6629 is required to be open on the Agilent Instrument controller. This port is used for secure HTTPS data transfer to and from the remote work area.
Temporary Solution:
n/a
Fix Information:
Documentation updated in version 2.6
Keyword:
One-line Description:
Latest version of OpenLab Shared Services is not included in CDS Update
Problem:
The latest version of OpenLab Shared Services is not included with CDS Update installation.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 03.
Keyword:
One-line Description:
Update for OpenLab CDS AIC can fail after upgrading to OpenLab CDS 2.5 when Sample Scheduler is configured
Problem:
After the upgrade, installing an update on an AIC cannot be applied as it detects the previous CDS version 2.3 or 2.4. Checking "Programs and Features" of Windows Control Panel shows the previous OpenLab CDS version. A similar message may appear when installing the update: "Agilent OpenLab CDS 2.5 Update xx can only be installed on Agilent OpenLab CDS 2.5. Check that you are patching the correct version." One component of Sample Scheduler is always installed with the CDS installation of the AIC. If the Sample Scheduler is configured, remnants of the older CDS version is left behind after an upgrade. This will prevent installation of any update on OpenLab CDS 2.5. If Sample Scheduler is no installed on the whole distributed system where the component from the AIC installation can connect to, the Sample Scheduler is not configured and upgrading the CDS goes smoothly.
Temporary Solution:
Workaround: 1. After the upgrade, remove this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Dependencies {645F3E18-1ED9-458F-A8A9-2EF44104B074} 2. Uninstall the old version of CDS from "Programs and Feature" of WindowsControl Panel Note: A PowerShell script is available for the suggested workaround. CDS_AIC_2.3-2.4_uninstall_workaround.ps1 script attached. This script should be run after the upgrade of OpenLab CDS if there are 2 CDS entries in the add/remove program and Sample Scheduler was configured. The script deletes the registry key listed above and uninstalls the old version of CDS on the AIC.
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword:
One-line Description:
Sporadically the "OpenLab Shared Services" service on the OpenLab Server is turned off
Problem:
During the replication of data to the AICs (for operational continuity / failover), OLSS server may crash with “OutOfMemoryException” because the data being replicated are too big and there is not enough memory for the OLSS process to handle this. The likelihood of the issue increases with the number and type of instruments, for example if Mass Spectrometers are involved. In that case you can reduce the likelihood by deleting unnecessary tune files.
Temporary Solution:
The replication can be turned off. Please contact Agilent Support for details. Note that under this condition there is only limited operational continuity on the AICs,
Fix Information:
The issue is fixed in CDS 2.4 Update 10 and CDS 2.5 update 05. The fix will also be in CDS 2.6. At this time there is no fix for CDS 2.3.
Keyword:
One-line Description:
"No license granted" error displayed when launching MatchCompare on OpenLab CDS 2.5 Client PC
Problem:
"No license granted" error is displayed when launching MatchCompare on OpenLab CDS 2.5 Client PC(s). This error is only shown on OpenLab CDS 2.5 Clients. The MatchCompare installer determines which version of MatchCompareHelper.dll to install using the C:\ProgramData\Agilent\Installation\CdsConfiigured file. This file is no longer created for the CDS Client in v2.5 causing MatchCompare installer to install the wrong DLL and preventing MatchCompare from getting a license.
Temporary Solution:
For all installations of MatchCompare on CDS Clients v2.5, use the following workaround to create the CdsConfigured file: 1. On the CDS Client PC, right-click on the Windows start button 2. Select run and enter: 3. echo 2.5.0.927 > C:\ProgramData\Agilent\Installation\CdsConfigured 4. Proceed with the MatchCompare installation. For systems experiencing the licensing error, uninstall MatchCompare and perform the 4 steps described above.
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword:
One-line Description:
IQ report fails after the installation of update 1 for Sample Scheduler 2.5
Problem:
After the installation of the Update 01 package for Sample Scheduler 2.5, the IQ report fails, reporting 3 deviations: .\Sample Scheduler for OpenLab\documentation\xml\sample_scheduler_for_openlab_command_guide.chm .\Sample Scheduler for OpenLab\bin\zh-hans\agilent.scheduler.cds.icdsinstrument.resources.dll .\Sample Scheduler for OpenLab\bin\ja-jp\agilent.scheduler.cds.icdsinstrument.resources.dll These deviations can be ignored. Update 01 does not contain / replace these files, The error is caused by an erroneous IQ xml reference file of Update 01.
Temporary Solution:
n/a
Fix Information:
The issue will be fixed with a future update.
Keyword:
One-line Description:
Scaling factor for area conversion of imported EZChrom data
Problem:
An analysis done by CDS 2.x results in different peak areas and heights compared to EZChrom Elite and OpenLAB CDS EZChrom edition. While calibrated results, Area% and Height% are not affected, absolute peak areas and heights differ by detector dependent scaling factors in case you analyze the same sample with the same method in both CDSs. Also, when you import EZChrom data into CDS 2.x, the EZChrom units for peak area and peak height are maintained and differ from the results from samples being analyzed directly by CDS 2.x.
Temporary Solution:
n/a
Fix Information:
Using the 2.x Intelligent Reporting or Custom Calculation, a detector dependent scaling factor can be applied in order to adjust the CDS 2.x results for better comparison, for example in the context of method validation. The scaling factor only applies to the results. It does not change raw data. Following the detailed calculation and a list of detector dependent scaling factors: Scaled areas/heights with detector specific units can be obtained by multiplying the unit-less EZChrom “counts” by the matching detector specific scaling factor. Peak Height [CDS 2.x] = Peak Height [EZChrom] * Scaling factor Peak Area [CDS 2.x] = Peak Area [EZChrom] * Scaling factor Likewise, unscaled areas/heights, i.e. detector counts, can be obtained by dividing the CDS 2.x data by the scaling factor. Peak Height [EZChrom] = Peak Height [CDS 2.x] / Scaling factor Peak Area [EZChrom] = Peak Area [CDS 2.x] / Scaling factor In order to obtain CDS 2.x equivalent values for GC signals in the appropriate scale for each detector, the reported value in EZChrom must be divided by 7680 for all detector types. This is based on the GC Least Significant Value (1/7680), i.e. the scaling factor to put into the formulas is 1/7680. For Agilent LC detector signals the scaling factors used to transform Peak Area and Height from counts to detector units are as follows: VWD Detector Models - G1314A\G1314B\G1314C\G1314D\G1314E\G1314F\G7114A\G7114B Scaling Factor = 0.000059604644775390625 mAU (=1000/2^24) DAD\MWD Detector Models - G1315A\G1315B\G1315C\G1315D\G1365A\G1365B\G1365C\G1365D\G7115A Scaling Factor = 0.000476837158203125 mAU (=1000/2^21) DAD Detector Models - G4212A\G4212B\G7117A\G7117B\G7117C Scaling Factor = 0.000007450580596923828125 mAU (=1000/2^27) FLD Detector Models - G1321A\G1321B\G1321C Scaling Factor - 0.0000059604644775390625 LU (=100/2^24) RID Detector Models G1362A\G7162A\G7162B Scaling Factor = 100 nRIU
Keyword:
One-line Description:
System Preparation Tool report does not open
Problem:
The System Preparation Tool report does not open due to an old version of Symantec.
Temporary Solution:
The System Preparation Tool report is opening with Symantec version 14.2 or higher. Removing Symantec also fixes this issue.
Fix Information:
n/a
Keyword:
One-line Description:
Uploading many files causes the web UI to freeze with 0% progress
Problem:
Uploading a large number of files using drag and drop in the content management web interface may result in a frozen interface showing no progress
Temporary Solution:
n/a
Fix Information:
There is a limitation on the number of files one can drag and drop via a browser at one time, and this is due to a limitation on the browser type and OS combined that we have no control over. Each browser type may have a different limitation. If you have thousands of files and folders to upload via a browser, please consider upload them in separate batches. The documentation in the next release will be updated to include this information.
Keyword:
One-line Description:
After restoring backup, the Instrument service is not started
Problem:
After a restore operation on a Workstation Plus, the Agilent OpenLab Instrument Service is not re-started. This will prevent starting an instrument in the OpenLab Control Panel.
Temporary Solution:
Manually restart the Agilent OpenLab Instrument Service after a restore or Reboot the workstation.
Fix Information:
n/a
Keyword:
One-line Description:
Data collection Service does not start after upgrade
Problem:
After the Upgrade of an OpenLab 2.3 Server with external SQL DB the Data Collection Service could not be started anymore after the upgrade is finished.
Temporary Solution:
A repair of the Data Collection Service will solve the issue. Navigate in the Windows Control Panel to Programs and Features and execute a repair on "Agilent OpenLab Data Collection Service". A reboot will be required after the repair.
Fix Information:
This Problem is addressed in Version 2.6 of OpenLab
Keyword:
One-line Description:
During a software update step 4 fails at fails at 36% in the "Shared Services Deploy and check" step
Problem:
During a software update with a SQL server database step 4 fails at fails at 36% in the "Shared Services Deploy and check" step. This can happen when the SQL server sa user's password was changed after the installation of the OpenLab version that needs to be updated. There is no dialog to enter the new password for the sa user, the password of the original installation will be used.
Temporary Solution:
Reset the sa user password to the password at the time of the installation of the initial OpenLab version. In case that is not possible, contact your Agilent support representative with the KPR#:602950 for further instructions.
Fix Information:
n/a
Keyword:
One-line Description:
Installation fails after restoring a backup
Problem:
After the restore procedure was completed on a clean operating system, OpenLab CDS installation fails due to installing a 'base' version that contains an older version of the database (no updates) against a restored database (with updates). The system cannot be restored to software that does not include the updates.
Temporary Solution:
Install the application and the latest software update and then restore your backup.
Fix Information:
n/a
Keyword:
One-line Description:
TCP port 5443 required during installation
Problem:
TCP port 5443 is required during installation for the reverse proxy setup. This port is not mentioned in the manual. During operation port 443 is used and port 5443 is no more needed. This will be fixed in CDS 2.7. From then on, TCP port 5443 will not be required any longer.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Silent upgrade 2.4 to 2.7 returns error code 1067
Problem:
When upgrading from OpenLab CDS 2.4 to 2.7, the batch script returns error code 1067 and fails. It is missing a data repository (DR) password. The properties and config files from the initial 2.4 install do NOT have a DR password in them. DR was not part of 2.4. Using the installer works without a problem. The silent approach needs all fields necessary for 2.7.
Temporary Solution:
Generate a properties file from a 2.7 upgrade using the OpenLab Installer.
Fix Information:
n/a
Keyword:
One-line Description:
Workflow Test is failing on CDS2.5 System under specific circumstances
Problem:
If you run the workflow test with QualA on a CDS2.5 does not have the everything privilege, the workflow test will be failing if you run the test a second time. As part of the workflow test the Sequence Template for the earlier Test must be deleted. This is only possible with the everything privilege
Temporary Solution:
Execute the Workflow Test with a User which has the everything privilege or delete the Sequences from the content manually with a different user which has the required privilege.
Fix Information:
This Problem is fixed in OpenLab CDS2.6 onwards with introduction of a delete privilege in the Control Panel.
Keyword:
One-line Description:
SPT status check fails in Windows 11: Power options: Set Turn off hard disk after to Never for Performance Power Plan
Problem:
In Windows 11, the SPT status check, “Power options: Set Turn off hard disk after to Never for Performance Power Plan” fails even when the hard disk power option has already been turned off or when re-running SPT. However, after selecting the Apply button, the setting is correctly applied.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SPT status check fails in Windows 11: Power options: Set Put the computer to sleep to Never for Performance Power Plan
Problem:
In Windows 11, the SPT status check, “Power options: Set Put the computer to sleep to Never for Performance Power Plan” fails even when the computer has already been configured for high performance or when re-running SPT. However, after selecting the Apply button, the setting is correctly applied.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
SPT status check fails in Windows 11: Network: Disable Power Management options for Network Adapter
Problem:
In Windows 11, the SPT status check, “Network: Disable Power Management options for Network Adapter” fails even when the computer network adapter power management has already been disabled or when re-running SPT. However, after selecting the Apply button, the setting is correctly applied.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
A logging library running on the remote host has multiple vulnerabilities.
Problem:
A customer found multiple vulnerable versions of Log4j in their security scans, specially the one which were reported in CVE-2021-4104, CVE-2019-17571 nor CVE-2021-4104 and are affecting Alfresco, the underlaying Product of Agilent OpenLab.
Temporary Solution:
n/a
Fix Information:
According to the Alfresco support (https://hub.alfresco.com/t5/alfresco-content-services-forum/log4j-vulnerability-impact-on-alfresco-community-edition/m-p/311033#M26495) Alfresco is not affected by CVE-2021-4104, CVE-2019-17571 nor CVE-2021-4104. In order to be exposed to those vulnerabilities you need to enable explicitly some Log4j services that are off when using Alfresco by default in Agilent OpenLab.
Keyword:
One-line Description:
Installation of OpenLab CDS 2.7 fails if the required ASP.NET Core Runtime versions are not present
Problem:
Installation will fail if ASP.NET Core Runtime versions higher than 3.1.23, 5.0.15, and 6.0.3 are already installed, or if there is a .NET Core version mismatch.
Temporary Solution:
Refer to attached Service Note solution section: Install of CDS 2.7 fails if the required ASP.NET Core Runtime versions are not present_D0028702 for workaround.
Fix Information:
n/a
Keyword:
One-line Description:
"Invalid floating point operation" error upon importing Thermo U3000 data from OpenLab CDS into a 3rd party software
Problem:
Upon importing an AIA file (obtained with the Thermo U3000 LC) from OpenLab CDS into a 3rd party software, one gets an error message: "Invalid floating point operation".
Temporary Solution:
None
Fix Information:
There is no fix.
Keyword:
One-line Description:
Hitachi Chromaster: Acquisition Window Crashes if Non-English OS Used for AIC/Client
Problem:
Once a Chromaster instrument is launched, after 5 ~ 10 minutes OpenLab CDS is generating error messages in Activity log: "Le format de la chaîne d'entrée est incorrect" (Input String is not in correct format) until the system crashes.
Temporary Solution:
Change the format of system account to English (United States). In Region settings select [Administrative][Copy current settings] to [Welcome screen and system accounts], and re-boot the AIC/Client.
Fix Information:
N/A
Keyword:
One-line Description:
Windows 11 version 22H2 will not list installed updates for OpenLab CDS software
Problem:
With Windows 11 version 22H2, the OpenLab CDS installed updates are not listed in Control Panel > Programs > Programs and Features > Installed Updates.
Temporary Solution:
To verify that the update was installed, match the version of each OpenLab component listed in the Update Readme file with: - the version shown in File>About for Acquisition and Data Analysis - go to Control Panel > Programs > Programs and Features and look for the Agilent OpenLab CDS component and compare the build number with the version listed in the readme file of the update. - Run the following command from an elevated CMD prompt: wmic /output:C:\programs.txt product get name, version Open the programs.txt. Match the component versions listed in the program.txt with the versions listed in the Update Readme file for: Agilent OpenLab Content Management Agilent OpenLab Shared Services Agilent OpenLab Data Analysis Agilent OpenLab Acquisition - Run the Software Verification Tool and select the “Show OK files in report” check box to verify that it passes the overall evaluation of installation check, and the updated components have the correct version. - the software update component versions will be listed in the C:\ProgramData\Agilent\InstallLogs\SoftwareUpdate
Fix Information:
n/a
Keyword:
One-line Description:
Unexpected termination in OpenLab Shared Services
Problem:
Intermittently, OpenLab Shared Services stops running and needs to be restarted. In the Windows Event Log, an error occurs such as “The process was terminated due to an unhandled exception”. Agilent Engineering has identified two causes for this problem: - In large systems, the replication of AIC instrument configuration information required to support failover operation exceeds the available memory. -The Lucene search indexer used for the System Activity Log is consuming excessive memory with a large number of search results.
Temporary Solution:
Agilent technical support can provide instructions for disabling the replication of AIC instrument configurations and adjusting the activity log search index memory usage. These steps significantly reduce the frequency of unexpected termination events. Reducing the use of keyword searches in the System Activity Log and limiting searches to a narrow time range should also reduce the frequency of unexpected termination events. In case the OLSS service crashes that are neither caused by replications nor by searches, the recommendation is to go to OLSS Service properties, switch to the "Recovery" tab and select "Restart the Service" for the "First failure", "Second failure", and "Subsequent failures".
Fix Information:
Agilent Engineering is developing a fix for this issue for version 2.7. For versions 2.5 and 2.6, the status of a fix will be communicated later.
Keyword:
One-line Description:
Modifying report template stability_report.rdl will cause report rendering issues.
Problem:
After modification of the stability_report.rdl report template, it is not possible to generate a report out of it. There will be an error and the rendering process stops.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.7 Update 03 and in OpenLab CDS v2.6 Update 09.
Keyword:
One-line Description:
SVT can fail on Citrix Server if the location of the files is not c:\
Problem:
After an upgrade, if the location of the files is not c:\ the running of the SVT can result in a FAIL for missing files.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Acquisition is freezing after opening a sequence
Problem:
Acquisition is freezing when opening a sequence with more then about 100 files in the Sequences folder. This happens when content management is configured in the OpenLab Control Panel using https://hostname
Temporary Solution:
Configure content management using https://FQDN in the OpenLab Control Panel.
Fix Information:
n/a
Keyword:
One-line Description:
Apache HTTP Server vulnerability CVE-2023-25690 on CDS and ECM XT
Problem:
There has been uncertainty if and to which extent the Apache HTTP Server vulnerability CVE-2023-25690 (see https://httpd.apache.org/security/vulnerabilities_24.html) has impact on CDS and ECM XT. A pre-requisite for this vulnerability are specific settings in the httpd.conf configuration file that can be found in c:\Program Files\OpenLab Reverse Proxy\Apache24\conf. The settings that enable an abuse can be found under https://httpd.apache.org/security/vulnerabilities_24.html. Note: The httpd.conf as it gets installed by CDS and ECM XT does NOT have settings that enable security breaches. Hence, there is no risk, unless httpd.conf gets intentionally modified to include these kind of settings.
Temporary Solution:
For the time being, the recommendation is to protect unauthorized httpd.conf changes by related Active Directory / OS measurements. This concerns the following machine types: Workstation, Workstation Plus, AIC, OpenLab Server, ECM XT, Index server.
Fix Information:
Agilent is preparing a patch to update Reverse Proxy in CDS 2.6 and 2.7 to the latest stable Apache version. This will not roll up in a CDS Update, but be released independently of CDS.
Keyword:
One-line Description:
Content management fails to start after restore
Problem:
After a data restore to a new installation, Content Management does not start. The alfresco.log file shows, for example, Module 'amp-olss' version 2.6.2-REL_2.6.2.15 is currently installed and must be uninstalled before version 2.6.0-REL_2.6.0.664 can be installed. This happens when the software installation does not match the patch level of the source software installation where the backup was generated.
Temporary Solution:
There are two restore scenarios that use the Restore Utility outlined in the OpenLab CDS Workstation Plus Guide and the OpenLab ECM XT Administration Guide: restore on a system where the OpenLab application is already installed or restore on a clean machine and then install the application afterward. Both approaches work without issue when the backup's source system does not have any OpenLab updates installed. However, if OpenLab updates have been installed on the source system, then the following procedure should be used: Install the application on the target system (Workstation Plus or OpenLab Server / ECM XT server) and apply the same OpenLab CDS or OpenLab Server updates that were installed on the source system when the backup was performed. After this is done, restore the system successfully.
Fix Information:
This problem will be addressed in future releases of OpenLab software.
Keyword:
One-line Description:
A restored System can create a Cluster with the Source System
Problem:
In cases where a restored system will run at the same time as the source system (where the backup was taken,) it is imperative that the restored system is on a network isolated from the source system. For example, if a test system is created from a backup of the production system, it must be on a network that is isolated from the production system. If the test system and the production system are on the same network, it may cause the two servers to create a cluster and interact with each other. This can lead to data corruption and loss and upgrades on the restored system may fail.
Temporary Solution:
To prevent this you can do the following steps: 1.- On the restored server, open C:\Program Files (x86)\Agilent Technologies\OpenLAB Data Store\tomcat\shared\classes\alfresco-global.properties. Find the alfresco.cluster.enabled property and set it to false, as follows: alfresco.cluster.enabled=false 2.- Restart the AlfrescoTomcat service. Alternatively you can isolate the restored system and the source system by adding a firewall rule, that the system cannot access each other.
Fix Information:
This Problem is fixed in Version 2.6 onwards.
Keyword:
One-line Description:
Cutted end of Peak Baseline if EZChrom integrator is used
Problem:
If the EZChrom integrator is used to integrate peaks in OpenLab CDS 2.x the end of the peak baseline might show a hard cut if zoomed in very deeply.
Temporary Solution:
Workaround: If possible, use ChemStation integrator.
Fix Information:
n/a
Keyword:
One-line Description:
Match Compare files cannot be saved to expected locations within Workstation Plus systems.
Problem:
In a Workstation Plus or Client/Server system, MatchCompare files are supposed to be in the Data Store. While this is the case for some O/S and MC combinations, for some it is not.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Windows 10 LTSC support
Problem:
CDS 2.7 is fully supported on Windows LTSC 2019 and LTSC 2021. On page 27 of the CDS requirements guide, there is contradicting information from what is on Agilent.com. The requirements guide states that the use of OpenLab CDS 2.7 requires a custom SMA agreement if running on Windows 10 LTSC. This information is outdated and incorrect. The website contains the corrected information: "For OpenLab CDS version 2.7, support for LTSC 2019 has been added." There is no requirement to maintain a custom SMA in this configuration.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
System Preparation Report fails on supported LTSC version 2019
Problem:
In case of Windows LTSC 2019, the CDS/ECM XT system preparation tool that runs before the installation reports a failure in the O/S section. This failure can be ignored - Windows LTSC 2019 is fully supported. A fixed version of the system preparation tool is planned for the next CDS/ECM XT release.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
When starting "OpenLab Configuration" or "Shared Services Maintenance" an error is shown
Problem:
The error is "A referral was returned from the server" and is caused when the GPO "Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Only elevate executables that are signed and validated" is enabled.
Temporary Solution:
The "OpenLab Configuration" can be started from the OpenLab CDS 2 setup program, in the Installation section with the "Configure Client/Server" option.
Fix Information:
n/a
Keyword:
One-line Description:
Communication error occurs while trying to reach Agilent.Scheduler.Agent
Problem:
A private key for the certificate that gets generated by the CertTool for the port used by REST APIs on the AIC (52088) gets deleted by an Acquisition SDK process. After that no network communication to that port is possible, breaking the functionality. The issue manifests in two user observable symptoms: - Sample Scheduler services cannot be remotely restarted through Sample Scheduler configuration - Opening Data Analysis from CDS Acquisition client doesn’t work
Temporary Solution:
Take the following actions to temporary fix the problem: 1. Delete the certificate on the AIC. Open certmgr.msc and delete under "Trusted Root Certification Authorities/Certificates" the "OpenLab Root CA". 2. Renew certificate. Open a command prompt as administrator and change to the installation directory of the Certificate Service Tool binaries, default path is "C:\Program Files (x86)\Agilent Technologies\Certificate Service Tool\Bin" and run from there: "Agilent.OpenLab.CertService.CertTool.exe RegisterRootCert -h <servername>". 3. Reboot AIC .
Fix Information:
A fix is planned for OpenLab CDS 2.7 Update 06.
Keyword:
One-line Description:
Alert message not helpful when AIC/Client/CM Client cannot connect to Server during installation
Problem:
For Chinese and Japanese systems, the current alert message during installation is insufficient when the AIC/Client/CM Client cannot connect to the Server.
Temporary Solution:
The alert message should say, "Check if the Shared Services is running on the specified server and the TLS version on this machine is compatible with the server". The TLS vesion on the AIC or client is higher than the version on the server (1.3 vs 1.2). Run the script located on the 2.8 media under Setup\Tools\Support\TLS
Fix Information:
n/a
Keyword:
One-line Description:
A Shared Services Administrator Credentials empty dialog box appears during new installation
Problem:
When installing a new OpenLab ECM XT system, a Shared Services Administrator Credentials empty dialog box appears during step 4.
Temporary Solution:
To continue the installation, select OK.
Fix Information:
n/a
Keyword:
One-line Description:
System Preparation Tool does not install .NET framework 3.5 offline for Windows 11 22H2
Problem:
System Preparation Tool does not install .NET framework 3.5 offline for Windows 11 22H2
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Shared Services Database upgrade fails if password contains certain symbols
Problem:
Database upgrade fails when special characters like % or @ are used in the PostgreSQL user password.
Temporary Solution:
The recommendation is not to proceed with an upgrade if % or @ are used in the PostgreSQL user password.
Fix Information:
n/a
Keyword:
One-line Description:
OpenLab CDS v2.8 Data Analysis crashes when Windows 11 is set up without an internet connection
Problem:
If Windows 11 was set up without an internet connection and the network requirements step was bypassed during the configuration, the latest Windows updates will not be in place. Starting with OpenLab CDS v2.8, Data Analysis requires the Microsoft Edge WebView2 Runtime, which is preinstalled on Windows 11 with version 100. Typically, it will be updated if an internet connection is available. However, the Microsoft Edge WebView2 Runtime version 100 is not working correctly, and as a result, Data Analysis will crash.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS 2.8 Update 01.
Keyword:
One-line Description:
Data analysis does not launch, error message appears
Problem:
Launching Data Analysis displays the following error message: "Please restart Agilent OpenLab Data Analysis Web Application Server". Restarting the service does not resolve the issue.
Temporary Solution:
Go to Setup\Tools\Support\TLS and run the FixTLSVersions.ps1 script.
Fix Information:
n/a
Keyword:
One-line Description:
Create Content Management Database fails when NT username includes special character
Problem:
OpenLab Server and WorkStation Plus fail to install at the Content Management Database step when the Windows username includes a special character such as ! ' "/[]:;|=,+*?<>.
Temporary Solution:
Correct windows login name or connect as a different local administrator and repeat the installation
Fix Information:
n/a
Keyword:
One-line Description:
Installation fails at the Agilent.OpenLab.OpenSearch step when NT username includes special character
Problem:
OpenLab Server and WorkStation Plus fail to install v2.8 at the Agilent.OpenLab.OpenSearch step when the username includes a special character such as ! or '.
Temporary Solution:
Choose a user name, which has no “!” included. Re-run the OpenLab installation.
Fix Information:
This defect is planned to be fixed in the next minor release.
Keyword:
One-line Description:
After a cleanup of a user's temp directory the OpenLab and instrument's activity log shows error: Activity log is not ready.
Problem:
It has been reported that after a cleanup of a user's Windows temp directory the OpenLab and instrument's activity log index is no longer ready for usage and the activity log is not accessible. This error can be seen if the OpenSearch service is not running. This defects potentially affects OpenLab CDS 2.8 and patched OpenLab CDS 2.7 systems only.
Temporary Solution:
Navigate to the Windows services panel and start up service OpenSearch 2.11.1. In case the service does not start up successfully, open Windows explorer and navigate to folder "C:\Users\<USERNAME>\AppData\Local\Temp\opensearch". The <USERNAME> is the user that installed OpenLab CDS. If the folder "opensearch" does not exist, the "OpenSearch 2.11.1 (opensearch-service-x64)" service is not starting. Create the folder "opensearch" manually and start the service OpenSearch 2.11.1 again.
Fix Information:
This issue will be fixed in a future release.
Keyword:
One-line Description:
Security vulnerabilities found in Software Verification Tool (SVT) version 6.2
Problem:
Security vulnerabilities found in Software Verification Tool (SVT) version 6.2.
Temporary Solution:
n/a
Fix Information:
OpenLab CDS 2.8 Update 03 includes SVT version 6.3. SVT version 6.3 addresses security issues CVE-2024-0057, CVE-2023-51714, CVE-2023-45853, CVE-2023-36049, CVE-2022-37434, CVE-2022-32893, CVE-2021-1871, CVE-2020-24742, CVE-2020-11656, CVE-2020-1147, CVE-2019-8457, CVE-2019-19646, CVE-2018-4441, CVE-2017-13798, CVE-2017-13796, CVE-2017-13795, CVE-2017-13794, CVE-2017-13792, CVE-2017-13791, CVE-2017-13785, CVE-2017-13784, CVE-2017-13783, CVE-2017-10989, CVE-2017-10904, CVE-2016-2108, CVE-2016-0705, CVE-2010-4204, and CVE-2010-4197.
Keyword:
One-line Description:
Npgsql security vulnerable to SQL Injection via Protocol Message Size Overflow
Problem:
Security vulnerability, CVE-2024-32655 has been reported for Npgsql.
Temporary Solution:
n/a
Fix Information:
Npgsql.dll version 7.0.2 updated to version 7.0.7 to fix security vulnerability CVE-2024-32655.
Keyword:
One-line Description:
OpenLab CDS 2.8 Workstation Plus and Server installation fails when PostgreSQL super user password has {}
Problem:
During PostgreSQL configuration, an error is displayed that the password of the super user login does not match, and the database cannot be accessed. The error is caused by specifically placing the open { and then the closed } paired curly brackets.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Unable to launch OpenLab Data Analysis v2.8 Update 02 when 2DLC plugin is installed
Problem:
Unable to launch OpenLab Data Analysis v2.8 Update 02 when 2DLC plugin is installed
Temporary Solution:
n/a
Fix Information:
This issue has been resolved in OpenLab CDS v2.8 Update 03.
Keyword:
One-line Description:
Alert message not helpful when AIC/Client/CM Client cannot connect to Server during installation
Problem:
For Chinese and Japanese systems, the current alert message during installation is insufficient when the AIC/Client/CM Client cannot connect to the Server.
Temporary Solution:
The alert message should say, "Check if the Shared Services is running on the specified server and the TLS version on this machine is compatible with the server". The TLS vesion on the AIC or client is higher than the version on the server (1.3 vs 1.2). Run the script located on the 2.8 media under Setup\Tools\Support\TLS
Fix Information:
n/a
Keyword:
One-line Description:
Installation of RabbitMQ fails when user profile is on a network share
Problem:
If the user profile is on a network share the installation of CDS 2.8 and ECM XT 2.8 may fail at RabbitMQ. It may be necessary for the customer to create an admin account, which has NO mapping of the user home drive to a network folder to allow the installation to complete.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
Activity Log Count reported higher than in Backup on system with slow / full disk
Problem:
In certain conditions (i.e. on slow machines), the number of ActivityLog entries returned for the backup is too low. This behavior is likely to be a latency-related issue when re-indexing is still ongoing.
Temporary Solution:
n/a
Fix Information:
This issue has been resolved in OpenLab CDS 2.8 Update 03 and OpenLab Server 2.8 Update 03.
Keyword:
One-line Description:
Restarting services fails during Restore on systems with Sample Scheduler activated
Problem:
On systems where Sample Scheduler is activated, system services can fail to restart during the Restore of a backup, using the OpenLab Backup & Restore utility. The Restore progress dialog will then show a failure in the step where services are supposed to start after databases have been restored.
Temporary Solution:
The following workaround is available if this problem occurs during a restore on a system where Sample Scheduler application is activated: An entitled user needs to update the name of the service "Agilent Sample Scheduler LIMS Agent" in the backup.xml, in the backup folder. For a full backup: in the backup folder "...\Current\backup.xml", change <string>Agilent Sample scheduler LIMS Agent</string> to <string>Agilent Sample Scheduler LIMS Agent</string> For a scheduled backup: in the backup folder in "...\Current\backup.xml" and in "...\Incremental\backup.xml" change <string>Agilent Sample scheduler LIMS Agent</string> to <string>Agilent Sample Scheduler LIMS Agent</string>
Fix Information:
The issue has been resolved in OpenLab CDS 2.8 Update 03 and OpenLab Server 2.8 Update 03.
Keyword:
One-line Description:
An error is seen when opening DA or running injections with existing projects but not seen with new projects.
Problem:
An error is generated when trying to open Data Analysis or running injections from ACQ using old existing projects. The issue can be resolved by checking that users which have been deleted from the Domain are removed from OpenLab Control Panel. Shared Services service must be restarted after the change is made.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in CDS / ECM XT 2.8. A fix is planned for a future 2.6 and 2.7 Update.
Keyword:
One-line Description:
No distinction made between full- and half-width characters when using Microsoft SQL Server
Problem:
Secure Storage fails to distinguish between one-byte alphanumeric characters (e.g., “1”) and two-byte Japanese characters (e.g., “1”) in folder and file names. As a result, folders named “test1” and “test1” are recognized as the same, preventing them from coexisting in the same directory. The error message displayed is: “This folder name already exists in this location.”
Temporary Solution:
n/a
Fix Information:
n/a
Keyword:
One-line Description:
An error is seen when opening DA or running injections with existing projects but not seen with new projects.
Problem:
An error is generated when trying to open Data Analysis or running injections from ACQ using old existing projects. The issue can be resolved by checking that users which have been deleted from the Domain are removed from OpenLab Control Panel. Shared Services service must be restarted after the change is made.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in CDS / ECM XT 2.8. A fix is planned for a future 2.6 and 2.7 Update.
Keyword:
One-line Description:
An error is seen when opening DA or running injections with existing projects but not seen with new projects.
Problem:
An error is generated when trying to open Data Analysis or running injections from ACQ using old existing projects. The issue can be resolved by checking that users which have been deleted from the Domain are removed from OpenLab Control Panel. Shared Services service must be restarted after the change is made.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in CDS / ECM XT 2.8. A fix is planned for a future 2.6 and 2.7 Update.
Keyword:
One-line Description:
No ability to select which signals to use with blank subtraction
Problem:
OpenLab CDS 2.8 was released with feature to enable blank subtraction for mass spec signals. However, there is no option to select which signals to use for blank subtraction, so it is not possible to process methods from older versions (where only non-MS signals were subtracted) under the same conditions in CDS 2.8.
Temporary Solution:
n/a
Fix Information:
This issue will be resolved in a future release by adding the ability to specify in the processing method whether blank subtraction should be performed on only non-MS signals, only MS signals, or both MS and non-MS signals. (There will continue to be the ability to turn off blank subtraction as well.)
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
Keyword: 68xx Driver
One-line Description:
Customer can't install colum information from catalog if column description is blank
Problem:
OpenLAB EZChrom A.04.06 and 6890N Step: 1, Customer selects 122-10BE column. this column doesn't have description. 2, Error message appears when you try to install this column.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.01
Keyword: 68xx Driver
One-line Description:
Setting a Hold time of 0.0 does not work correctly with GC6890
Problem:
Setting up Hold Time of 0.0 does not work correctly with GC6890.
Temporary Solution:
No fix planned.
Fix Information:
None
Keyword: 68xx Driver
One-line Description:
GC Driver and OpenLAB CDS 2.2 Version Number clarification.
Problem:
GC Driver versions do not display correctly in OpenLAB CDS. The leading alpha character does not get displayed. This makes the "B" version appear to be older than previous "A" version.
Temporary Solution:
This is a cosmetic defect only. It does not affect the operation of the software. The version numbers are still unique.
Fix Information:
n/a
Keyword: 68xx Driver
One-line Description:
OpenLAB 2.1: Unable to download syringe change to GC
Problem:
OpenLAB 2.1: Unable to download syringe change to the 6890 GC.
Temporary Solution:
n/a
Fix Information:
Resolved in B.01.02
Keyword: 68xx Driver
One-line Description:
6890 online help has the bad strings in Injector page.
Problem:
6890 online help has the bad strings in Injector page.
Temporary Solution:
n/a
Fix Information:
Resolved in B.01.02
Keyword: 78xx Driver
One-line Description:
Method printout missing column parameters: flow or pressure, setpoint On, (Initial), and post run
Problem:
Using Print Method from the ChemStation Software C.01.05, the method printout is missing column parameters: flow or pressure, setpoint On, (Initial), and post run. Column Column #1 Flow or Pressure Setpoint On (Initial) 2.3922 mL/min Post Run 2.1209 mL/min Agilent 19091J-413: 496.46579 HP-5 5% Phenyl Methyl Siloxan
Temporary Solution:
n/a
Fix Information:
Resolved in A.02.05.024.
Keyword: 78xx Driver
One-line Description:
Oven Slow fan will be off after method is downloaded the slow oven mode on to 7890
Problem:
OL CDS EZChrom A,04.05 and 7890B 02.03.1 step1. turn on Oven Slow fan, step2. click "Download Method to GC". step3. 7890B turned Oven Slow fan on correctly. then "Method Download Complete" message appeared on OL EZChrom. step4. instrument set up screen refreshed. step5. Oven Slow fan check box turned off.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.01
Keyword: 78xx Driver
One-line Description:
During a pulsed splitless run, the purge time shorter than the pulse time cannot be entered.
Problem:
On a 7890B one of the modes of operation is pulsed splitless. In some cases the purge time needs to be shorter than the pulse time. Recent changes in GC driver has invalidated this parameter change. Many customers need to turn the purge time shorter than the pulse time.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.01
Keyword: 78xx Driver
One-line Description:
Method print out with 7890 configured does not show total GCc run time.
Problem:
With 7890 configured; printing the method does not show total GC run time, however if 6890 configured it does show total run time.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.01
Keyword: 78xx Driver
One-line Description:
There is no "Inlet Septum Purge" event in Runtime Events table - EZChrom
Problem:
Method setting; On OpenLAB EZChrom Online session, Click dropdown list on Runtime events table, there is no "Inlet Septum Purge" event in this list.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.01
Keyword: 78xx Driver
One-line Description:
External Device "Not Ready" ignored by OpenLAB CDS ChemSataion and EZChrom
Problem:
When doing a valve injection with a Multi-Position valve and an external device the system ignores the external device readiness. When the external device is "Not Ready" the sequence will continue to make the injection and ignore the APG readiness. If a sequence is initiated locally at the front panel of the 7890 with the external device being "Not Ready" the sequence will wait for the external device to become ready prior to making the injection and starting the run. (This is the correct behavior.)
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.01
Keyword: 78xx Driver
One-line Description:
Aux Flow Limited to 150 mL/min even when pressure is less than Maximum
Problem:
Aux Flow Limited to 150 mL/min even when pressure is less than Maximum
Temporary Solution:
n/a
Fix Information:
Fixed in A.02.05
Keyword: 78xx Driver
One-line Description:
Post Run Flow Rate has default that out of range and value seems not to be stored
Problem:
Post Run gas flow defaults to 250 mL min even though the highest allowed value is 150 mL min. Even if you change it to save the analysis method as soon as you re-open the method it defaults back to 250 mL min.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.01
Keyword: 78xx Driver
One-line Description:
Method User Interface does not correctly load the content of a method.
Problem:
The content of a loaded method is only partly reflected in the method user interface. I seems that only the visible tab is updates. Steps to reproduce: 1.) Create a new method 2.) Change Oven Ramp, Events table or Signals 3.) Go back to the ALS Tab and save the method 4.) Create new method or load a different one 5.) Load the method saved in step 3 Verify the content of Oven Ramp, Events table or Signals. It does not display the correct content. See also attached document. This issue was found during the integration in Waters UNIFI and could also be reproduced in ICF TestApp and Shimadzu LabSolutions.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.01
Keyword: 78xx Driver
One-line Description:
Does not delete previous open GC method event table when load method. Wrong injections can be created.
Problem:
Steps: Open instrument setup panel Create method with some lines into the event table. Save method Create a second method with empty event table. Click detectors tab to see detectors info. Save this method. Open the first method, detectors tab is shown. Go to events table and it is blank.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.02
Keyword: 78xx Driver
One-line Description:
Method download to GC while in sequence causes it to disconnect and sequence stops.
Problem:
When a method is downloaded to the GC while running a sequence the GC disconnects and the sequence stops.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.02
Keyword: 78xx Driver
One-line Description:
7890 method print doesn't include post run time
Problem:
When printing a method the GC setpoints section does not include the post run time as expected.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.02
Keyword: 78xx Driver
One-line Description:
Crash of Software after check "Show Threshold Value as remaining time" in EMF Options
Problem:
Once you check the "show threshold value as remaining time" in EMF options, and close the EMF dialog. Once you re-enter the dialog, software freezes and has to be closed by task manager.
Temporary Solution:
n/a
Fix Information:
Fixed in A.03.02
Keyword: 78xx Driver
One-line Description:
Error Unhandled Exception when changing columns and a Gerstel CIS4 in installed in the 7890.
Problem:
If e a Gerstel CIS4 installed and the columns is reconfigured, a msinctl error occurs and the MassHunter software shuts down.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Incomplete Method Parameters for xCD in Acquisition Method Report
Problem:
When we do an Acquisition report, not all the xCD parameters are stored. The Reaction Cell Pressure and the Flow through the Ozone generator should also be reported. Can be confusing to customer.
Temporary Solution:
None
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Actual flows displayed by CDS aren't the same as the setpoint flows
Problem:
Examples: Setpoint Actual 3.000 3 2.998 3 2.95 3 2.92 2.9 The display for the 7890 shows three digits to the right of the decimal for both the setpoint and the actual. As shown above, the data system sometimes shows one digit to the right of the decimal and sometimes nothing to the right of the decimal (e.g. just "3")
Temporary Solution:
none
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Print method does not include all MMI setpoints: Purge time, Post Run Temp, Time, Flow
Problem:
Print method for the Intuvo 9000 GC doesn't have any MMI Purge time or Post Run temp or Post Run total Flow or time.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Extend run does not extend the acquisition of the Intuvo 9000 GC
Problem:
Intuvo 9000 GC on C.01.07.255 SR2. Extend run does not extend the run. LUI shows Idle during the extended part of the run.
Temporary Solution:
none
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Cannot Add User-Defined EMFs on Intuvo 9000 GC
Problem:
Unable to created a user defined EMF Intuvo 9000 GC. Enter a name and tracking type, but nothing appears on the User-defined panel or any other panel. There are five user defined (seemingly blank) entries on that panel.
Temporary Solution:
none
Fix Information:
To Be fixed in B.01.02
Keyword: 78xx Driver
One-line Description:
ChemStation Instrument actuals showing D2 Bus Temperature with no D2 bus installed
Problem:
ChemStation Instrument actuals showing Second Detector Bus Temperature with no second Detector.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
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
Problem:
Intuvo 9000 with a ALS and a 16 vial turret. MassHunter software, the configuration of the ALS is set to Solvent Wash Mode A,B. Saved and printed the method. Solvent Was Mode on the method print shows A-A2, B-B2.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Inlet pressure setpoint displayed assuming all thermal zones are turned ON, results in confusing mismatch when heated zones are Off.
Problem:
CDS displays inlet pressure setpoint assuming all thermal zones are turned ON, results in confusing mismatch when heated zones are Off.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Method Editor for PP inlet & Packed Column incorrectly allows both flow and pressure setpoints to be entered
Problem:
When in flow mode, pressure should not be allowed. Entering a value messes up the flow setpoint. When in pressure mode, flow should not be allowed. Entering a value messes up the pressure setpoint.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
GC driver is missing for the current build installed while upgrading from 2.1 to 2.2.
Problem:
GC driver is missing for the current build installed version while upgrading from 2.1 to 2.2 using the OpenLAB CDS Upgrade Wizard. This only occurs with "A" versions of the Agilent GC Drivers.
Temporary Solution:
The fix is to continue with the upgrade as it will still complete successfully.
Fix Information:
n/a
Keyword: 78xx Driver
One-line Description:
Right Clicking on Method Editor makes UI hide behind Instrument Screen
Problem:
Right Clicking on Method Editor makes UI hide behind Instrument Screen
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Incorrect Values in 9000 Pressure/Flow Calculator
Problem:
The values within the pressure/flow calculator when initializing from "Inlet 1" still do not match the instrument parameters.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Make changes to guard chip on Intuvo 9000 GC, audit trail just says temperature changed
Problem:
With Audit trail enabled, I make changes to the GC parameters panel of the Intuvo 9000 GC. Changed the guard chip temperature and hold time and saved the method. Looked at the audit trail and it showed events but it just said Temperature setpoint changed and Temperature hold time changed. There was no reference to the guard chip.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Backflush Wizard illogically sets trial backflush times after the elution time of last peak of interest
Problem:
Backflush Wizard illogically sets trial backflush times after the elution time of last peak of interest
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Should not be able to download a method while a in a GC run or sequence.
Problem:
Downloading a method while a in a GC run or sequence can cause issues.
Temporary Solution:
n/a
Fix Information:
Resolved in revision B.01.02
Keyword: 78xx Driver
One-line Description:
Method Resolution Does not take into account default column temperature limits.
Problem:
Methods from a 7820 do not have either a minimum temperature or a program maximum temperature. Hence these methods specify the use of default values for these parameters. When such a method is imported into a 7890 that support these parameters, the optional flags need to be cleared.
Temporary Solution:
n/a
Fix Information:
Resolved in B.01.02.059
Keyword: 78xx Driver
One-line Description:
The Local User Interface(LUI) on the Intuvo 9000 GC shows long name for connected data system.
Problem:
The front panel LUI shows the PC name with other information appended to it. Customers would like to see just the PC name.
Temporary Solution:
n/a
Fix Information:
Fixed in B.01.03
Keyword: 78xx Driver
One-line Description:
Location of Intuvo 9000 GC System Health Report should be moved
Problem:
Location of Intuvo 9000 GC System Health Report is not consistent with the location on the LUI of the GC.
Temporary Solution:
The System Health Report location has been moved to the Maintenance/Diagnostics screen.
Fix Information:
Resolved in B.01.03
Keyword: 78xx Driver
One-line Description:
Link to Intuvo 9000 GC help does not work.
Problem:
Click on options > Show 9000 Help and Information. This gives a message that the 9000 cannot be found.
Temporary Solution:
n/a
Fix Information:
Resolved in B.01.03
Keyword: 78xx Driver
One-line Description:
Event drop downs are black when creating a new method
Problem:
When creating a new GCMS method and adding events, drop downs are black. If the screen is switched and you go back to events, it works.
Temporary Solution:
n/a
Fix Information:
Resolved in B.01.03
Keyword: 78xx Driver
One-line Description:
PCM will not control in constant flow.
Problem:
PCM will not control in constant flow. Configured two packed columns using PCM Module to a single detector. The PCM will control in pressure mode but not flow mode. This was reported by a customer using OpenLAB 2.2 and tested using OpenLAB CDS ChemStation. .
Temporary Solution:
Use pressure control mode and ramp the pressure.
Fix Information:
Resolved in B.01.04
Keyword: 78xx Driver
One-line Description:
RTL for OpenLAB CDS: Calibration Runs dialog shows no chromatogram or compound table for loaded data or Results from calibration runs
Problem:
Select GC Plugins\RTL Wizard. Advance to the Calibration Runs dialog. There is no chromatogram or table shown for my loaded data, which was real data, from which to select my target compound. Enter vial numbers, RT and compound name. Start RTL sequence and at conclusion, the three resulting chromatograms are empty.
Temporary Solution:
n/a
Fix Information:
Fixed in B.01.03.096
Keyword: 78xx Driver
One-line Description:
RTL Wizard crashes when run with OpenLAB 2.2 and mandatory sample is selected.
Problem:
RTL Wizard crashes when run with OpenLAB 2.2 and mandatory sample is selected. If a mandatory parameter was found, when the user clicks "RTLWizard" to start up the wizard, an error message would appear explaining the problem. RTLWizard would then not continue.
Temporary Solution:
n/a
Fix Information:
Fixed in B.01.03.096
Keyword: 78xx Driver
One-line Description:
Acquisition crashes when user clicks on RTL Import/RTL wizard
Problem:
Acquisition crashes when clicked on RTL Import/RTL wizard.Configure and launch a GC 7890 Navigate to GC plugins layout and click on RTL Import. An unexpected error happens and crashes the acquisition client.
Temporary Solution:
n/a
Fix Information:
Fixed in B.01.03.096
Keyword: 78xx Driver
One-line Description:
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.
Problem:
RTL for OpenLAB CDS 2.X does not calculate the pressure correctly when locking or re-locking the method. This only occurs when the Target Retention field is set to a different retention time than the peak in the chromatogram.
Temporary Solution:
The work-around is to not update target retention time when selecting the peak for RTL locking. Use the retention time of the peak selection and the calculations are correct.
Fix Information:
Resolved in B.01.05
Keyword: 78xx Driver
One-line Description:
HS Sleep/Wake mode should sync with GC Sleep/Wake mode
Problem:
When a 7697 is configured to a 7890B, it should communicate such that the Sleep or Wake state of either one should be mimicked on the other.
Temporary Solution:
n/a
Fix Information:
Resolved in B.01.05
Keyword: 78xx Driver
One-line Description:
Overlap injections on the 9000 uses only the injection volume from the first injection for subsequent injection.
Problem:
Overlap injections on the 9000 uses only the injection volume from the first injection for subsequent injection.
Temporary Solution:
n/a
Fix Information:
Resolved in B.01.05
Keyword: 78xx Driver
One-line Description:
Defect: there is an empty tooltip on the button "maintenance" in the "control" ribbon in ACQ.
Problem:
Defect: there is an empty tooltip on the button "maintenance" in the "control" ribbon in ACQ.
Temporary Solution:
n/a
Fix Information:
Resolved in 3.0
Keyword: 78xx Driver
One-line Description:
GC Method Resolution results in “Object Reference” error message and occasional crash
Problem:
GC Method Resolution results in “Object Reference” error message and occasional crash
Temporary Solution:
n/a
Fix Information:
Resolved in 3.0
Keyword: 78xx Driver
One-line Description:
When attempting to save the method in OpenLab CDS 2.2, a dialog box appears with the title "[debug] Surprise Dirty!".
Problem:
When attempting to save the method in OpenLab CDS 2.2, a dialog box appears with the title "[debug] Surprise Dirty!".
Temporary Solution:
n/a
Fix Information:
Resolved in 3.0
Keyword: 78xx Driver
One-line Description:
Downloading method parameters (like oven temperature) on a 6890A does not work with OpenLab CDS 2.4
Problem:
Downloading method parameters (like oven temperature) on a 6890 does not work with OpenLab CDS 2.4. The GC is connected (current values are correctly displayed) and setting these parameters from the keyboard does work. Settings are updated in the method when selecting "Upload method".
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Intuvo trigger two instrument notification for configuration changed
Problem:
Chromeleon: Intuvo trigger two instrument notification for configuration changed. Configure an Intuvo with guard chip feature and open the online method in context menu of status panel and get two config changed events with a timely distance of 30 seconds.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC: Change of column length (and related parameters like flow etc) via calibration in online method sometimes reported in audit trail sometimes not
Problem:
Chromeleon: GC: Change of column length (and related parameters like flow etc) via calibration in online method sometimes reported in audit trail sometimes not
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC: Column length can only be calibrated once in Online Method Editor
Problem:
Chromeleon: GC: Column length can only be calibrated once in Online Method Editor
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Setting Liner on Intuvo triggers two config change messages in audit trail
Problem:
Chromeleon: Setting Liner on Intuvo triggers two config change messages in audit trail
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
8860 Open Lab CDS EZChrom compact license is invalid.
Problem:
8860 Open Lab CDS EZChrom compact license is invalid.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Selecting Partial Data for the 6890 causes the retention times and areas to be wrong.
Problem:
Selecting Partial Data for the 6890 causes the retention times and areas to be wrong.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
6890 - cannot set post run flow for packed column
Problem:
6890 - cannot set post run flow for packed column
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC 6850A and 6890A: GC online method is not editable
Problem:
Chromeleon: GC 6850A and 6890A: GC online method is not editable
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC 6890A: Wrong temperature shown in chromatogram for signal GC_OvTempe_Act
Problem:
Chromeleon: GC 6890A: Wrong temperature shown in chromatogram for signal GC_OvTempe_Act
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC 6850A: Cannot create instrument method
Problem:
Chromeleon: GC 6850A: Cannot create instrument method
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC8890: Current Signal Value in 'Blank evaluation' shows incorrect value in Method editor
Problem:
Chromeleon: GC8890: Current Signal Value in 'Blank evaluation' shows incorrect value in Method editor
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC8890: Blank evaluation setpoints missing in method report
Problem:
Chromeleon: GC8890: Blank evaluation setpoints missing in method report
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Signal Scaling is incorrect for the 6890
Problem:
The real time plot scaling is incorrect. The offset shown in the GC Status is 10.2. The Real time plot shows the signal level to be about 7.8 x10^4. It appears that the signal is not being scaled correctly, but is using the signal directly.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Intuvo: Help button in window 'Configure Agilent Intuvo 9000 GC' opens 78xx Series GC Help
Problem:
Chromeleon: Intuvo: Help button in window 'Configure Agilent Intuvo 9000 GC' opens 78xx Series GC Help
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC8890: Issues during sequence execution
Problem:
Chromeleon: GC8890: Issues during sequence execution. During the execution of a sequence (using the blank evaluation) I observed some issues: 1.no audit trail entry if blank evaluation was used or not ( was performed as blank run, blank evaluation option enabled) 2.during execution of sequence the GC8890 reported high CPU usage 3.The blank evaluation failure was reported during : 16.04.2019 17:20:29 +02:00 2,059 Agilent Blank Evaluation Failed, Failure Action is Continue
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Changes made in 68xx Edit Online Method not applied or reported
Problem:
Chromeleon: Changes made in 68xx Edit Online Method not applied or reported. 1. With Chromeleon open, selected to open Instrument Actuals 2. Right click in window and select Edit Online Method 3. Attempted several changes to online method. 4. Clicked Set Method Button. 5. No change in instrument actuals reflecting changes to method 6. No audit trail entries for changes made.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Error when loading GC method without Blank Run Analysis setpoint
Problem:
Error when loading GC method without Blank Run Analysis setpoint
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Corrected column length will not save after manual method resolution
Problem:
Chromeleon: Corrected column length will not save after manual method resolution
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Signals from previous method persist in new method
Problem:
Chromeleon: Signals from previous method persist in new method
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: ECD Help page cannot be accessed
Problem:
Chromeleon: ECD Help page cannot be accessed
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: All 8860 signals not displayed or available in report
Problem:
Chromeleon: All 8860 signals not displayed or available in report.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Error occurred at several points of operation
Problem:
Chromeleon: Error occurred at several points of operation. 1. Open instrument, select instrument (8890) and choose Create Method 2. Error pops up (see pic) 3. Click OK and proceed setting method parameters 4. Finish method; new instrument method opens. 5. Error appears again 6. Click OK, check method and save. Method saves 7. Right click on Status window and select Edit Online Method 8. Error appears again 9. Click OK and proceed with method edit 10. No time in this instance did the error impede actual saving method or running a sequence Expected behavior: Method creation and editing proceed without error
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC6890: Front Injector parameter change in Online method not applied
Problem:
Chromeleon: GC6890: Front Injector parameter change in Online method not applied.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC6890A: Method download fails
Problem:
Chromeleon: GC6890A: Method download fails
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
8860 on Chromeleon -Unhandled exception in Chromeleon Driver Host (CmDDKHost): AgilentTechnologies.DdkIcfAdapter|Agilent
Problem:
8860 on Chromeleon -Unhandled exception in Chromeleon Driver Host (CmDDKHost): AgilentTechnologies.DdkIcfAdapter|Agilent
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon does not recognize the tray with Back Injector installed.
Problem:
Connected to a Back inlet only 8890 with a Back Injector and Tray. Was not able to use a vial position on the tray as the vial number in the sequence for Chromeleon.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Automatic de-activation of not supported feature blank evaluation cannot be saved
Problem:
Chromeleon: Automatic de-activation of not supported feature blank evaluation cannot be saved
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Getting multiple Errors in the PC Event Log for AgGC7890 after disconnecting and Reconnecting LAN cable.
Problem:
Getting multiple Errors in the PC Event Log for AgGC7890 after disconnecting and Reconnecting LAN cable.
Temporary Solution:
n/a
Fix Information:
Unable to duplicate the issue.
Keyword: 78xx Driver
One-line Description:
GC6890: Valid vial ranges are not correct for 6890 in some cases
Problem:
GC6890: Valid vial ranges are not correct for 6890 in some cases
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC6890A: Error 'The communication FIFO of the DDK driver is corrupted.' after connecting and disconnecting several times.
Problem:
Chromeleon: GC6890A: Error 'The communication FIFO of the DDK driver is corrupted.' after connecting and disconnecting several times.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
When click the "Apply the Option" in GC Chromatographic Column Directory under Column Configuration, an exception occur on Openlab 2.4
Problem:
When click the "Apply the Option" in GC Chromatographic Column Directory under Column Configuration, an exception occur on Openlab 2.4.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Upgrade installation from GC B.01.03 to 3.0 SR2 fails to install Ag7697WS.dll (and .pdb)
Problem:
Upgrade installation from GC B.01.03 to 3.0 SR2 fails to install Ag7697WS.dll (and .pdb)
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC6850A: Changing method parameter creates method inconsistent to configuration
Problem:
Chromeleon: GC6850A: Changing method parameter creates method inconsistent to configuration
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC6850: Partial Data option causes issues during sequence execution
Problem:
Chromeleon: GC6850: Partial Data option causes issues during sequence execution
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: GC6890: Unexpected audit trail entries during endurance run
Problem:
Chromeleon: GC6890: Unexpected audit trail entries during endurance run
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
SR1 for the GC3.0 drivers breaks the connection between an 8890 and 7000D transferline temperature reading in MH ACQ 10.
Problem:
SR1 for the GC3.0 drivers breaks the connection between an 8890 and 7000D transferline temperature reading in MH ACQ 10.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Not able to download flow setpoints to 6890 VI inlet.
Problem:
Not able to download flow setpoints to 6890 VI inlet. Set up a method at the 6890. The column flow as set to 3 ml/min and the split ratio to 20 giving a total flow of 66.26 ml/min. Changed the split ratio to 10 and downloaded the method. The total flow did not change.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: Incorrect conversion and missing unit when using pressure setting bar
Problem:
Chromeleon: Incorrect conversion and missing unit when using pressure setting bar
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
68xx: Chromeleon: System with G4513 won't make 1.1 uL injection
Problem:
68xx: Chromeleon: System with G4513 won't make 1.1 uL injection
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: System crash: system slow and then crashing
Problem:
Chromeleon: System crash: system slow and then crashing. Chromeleon was unreactive and then suddenly the instrument connection was lost. After restarting the instrument controller the instrument was online again. Audit trail showns an OutOfMemory exception.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
8860 with Headspace/PAL does not consume correct VL license for OpenLAB 2.4
Problem:
8860 with Headspace/PAL does not consume correct VL license for OpenLAB 2.4
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
B,04.03 SP2 will not connect to an 8890 GC.
Problem:
B,04.03 SP2 will not connect to an 8890 GC.There is no way to configure an 8890 and if you try to connect as a 7890 it will not start the instrument session.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: 6890GC Oven temperature disabled in method - Run does not start.
Problem:
Chromeleon: 6890GC Oven temperature disabled in method - Run does not start.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
3.0 SR2 driver fails SVT on OL CS C.01.09.144
Problem:
3.0 SR2 driver fails SVT on OL CS C.01.09.144
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
OLCS C.01.09 with Driver 3.0.650 will not launch any instrument.
Problem:
OLCS C.01.09 with Driver 3.0.650 will not launch any instrument.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Chromeleon: SVT Chameleon 2.1.30 Fails
Problem:
Chromeleon: SVT Chameleon 2.1.30 Fails
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
Function_build number not display in SVT report in EzChrom and OpenLab CDS 2.4
Problem:
Function_build number not display in SVT report in EzChrom and OpenLab CDS 2.4
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: 78xx Driver
One-line Description:
8890: the MS transfer line temp displayed is 0 C but its actual temp is 250 C.
Problem:
8890: the MS transfer line temp displayed is 0 C but its actual temp is 250 C.
Temporary Solution:
n/a
Fix Information:
Resolved in version 3.0.652
Keyword: Acquisition
One-line Description:
68xx: Chromatogram for channel randomly offset, shifted
Problem:
In the GC Drivers 3.0 version, the chromatogram for the channel is shifted when a signal is saved which was not saved in the previous run using 68xx.
Temporary Solution:
n/a
Fix Information:
Resolved in GC driver 3.1.205.
Keyword: Acquisition
One-line Description:
"Autoscale Y-axis" toggle does not work in Online Signal window
Problem:
In Online Signal window, use of "Autoscale Y-axis" toggle to return Y-axis to its original settings specified in signal display settings does not work. The workaround is to use "Autoscale all panes" toggle.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Sequence editing and updating may get stuck at wrong state due to timing issue
Problem:
During editing a running sequence, when user clicks "Update" to update the current modified running sequence at the time when the current run state (sequence's state column) changes from "Acquiring" to "Processing", it may get stuck and user is not able to update the current running sequence due to timing issue.
Temporary Solution:
The workaround is try not to update the sequence during the state transition.
Fix Information:
This issue has been fixed in OpenLAB CDS 2.1.
Keyword: Acquisition
One-line Description:
Auto config twice in succession cause system hang
Problem:
When auto configuring an instrument twice in succession, system gets stuck at "Auto Configuration" message box, there is not time-out. The workaround is to click cancel on the "Auto Configure" message box, click cancel to close the configuration UI, and then reconfigure again.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Agilent OpenLAB Instrument Service would take longer than 2 mins to go to running state
Problem:
Due to dependencies of Agilent OpenLAB Instrument Service on ".Net Tcp Port Sharing" service, the service is registered as "Automatic Delay" which would be started by windows 2 mins after all automatic services have been started. Depending on the time taken by Windows to start all automatic services, the start of Agilent OpenLAB Instrument Service could take longer. You may experience delayed instrument connections after rebooting your standalone workstations or your AICs.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
User cannot import an English CSV file in European OS
Problem:
With European OS settings, when importing an English CSV file into sequence table, an error " incorrect file format" occurs. Importing sequence from an English CSV or TSV is not possible.
Temporary Solution:
Create a CSV file using your local regional settings, replace "." with ","; for column headers that contain any ".", replace with ",", and then put double quotes around them. For example, to import the correct acquisition method, its column header is Acq. method. It should appear in CSV as below: English OS: Acq. method European OS: "Acq, method"
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
"Injection time" of aborted injections are given Epoch Time of 1600-12-31 followed by time and UTC
Problem:
When an injection is aborted during acquisition, the "Injection time" is displayed in Epoch Time UTC as 1600-12-31 16:00:00 -08:00 (YYYY-MM-DD hh:mm:ss UTC) to represent when the injection was aborted. If this data is opened in a different time zone, for example in Central European Time, then the "Injection time" will be displayed in the local time as 1601-01-01 01:00:00 +01:00.
Temporary Solution:
n/a
Fix Information:
Epoch Time UTC is implemented in OpenLAB CDS 2.1 FR1 and later to represent the date and time that the injection was aborted during acquisition.
Keyword: Acquisition
One-line Description:
From an OpenLAB CDS 2.0 client, Viewing currently running sequence on any instruments configured on an OpenLAB CDS 2.1 AIC is not possible
Problem:
On a client/server system, when upgrading from OpenALB CDS 2.0 to 2.1, user can perform a staged upgrade. That is, part of the lab can still run 2.0 clients and AICs connecting to an upgraded 2.1 server. However, when user has a mixed pair, 2.0 client and 2.1 AIC, viewing currently running sequence is not possible. When this happens, user is not prompted with any error message.
Temporary Solution:
To ensure that AIC and clients are on the same version of the software.
Fix Information:
This is resolved in OpenLAB CDS 2.2.
Keyword: Acquisition
One-line Description:
When using Date and Time as token, the resolved values for Single Sample Analysis and Sequence are not consistent
Problem:
Local Date and Time <D> and Short Local Date and Time <DS> can be used as a token for data file name or sample name.The date and time token will not be resolved on the UI as YYYY-MM-DD HH-MM-SS with GMT offset.The resolution happens at the time of submission. For single sample analysis, the resolved value uses acquisition client PC's local date and time. Whereas for sequence, it uses AIC's local date and time.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Exception is thrown when result filename starts with spaces
Problem:
If the result filename starts with spaces, an "Exception of type" error is thrown when submitting single run or in the File Upload Queue.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.2.
Keyword: Acquisition
One-line Description:
Instrument Modules section in report does not list the SS420x or its properties
Problem:
Instrument Modules section in report does not list the SS420x or its properties.
Temporary Solution:
n/a
Fix Information:
This is resolved in OpenLAB CDS 2.2.
Keyword: Acquisition
One-line Description:
TIC signal is not displaying in Online Signal window during data acquistion if none is selected in GC's signal setting
Problem:
TIC signal will not be displayed in Online Signal window when acquiring data if None is selected in GC's signal settings. This is only a display issue, the data is actually acquired and saved.
Temporary Solution:
Select one of the GC signal (e.g. Test Plot, it dose not need to be checked to save), TIC will start showing in Online Signal window during data acquisition.
Fix Information:
The issue will be fixed in a future release.
Keyword: Acquisition
One-line Description:
EZChrom methods fail to import in OpenLAB CDS 2.1
Problem:
EZChrom methods for Waters Alliance (2489/2998 detector) cannot be imported in OpenLAB CDS 2.1.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS 2.2.
Keyword: Acquisition
One-line Description:
Network issues with DHCP may cause unexpected behavior on a Workstation installation
Problem:
On a Workstation when the main network which is connected through DHCP drops and the network IP can change to default non-reachable IP address, communication with Shared Services/Automation Service could stop. This will adversely affect acquiring runs and the client application.
Temporary Solution:
Use STATIC IP address to avoid DHCP failures.
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
GC/MS sequence aborts when Server is disconnected
Problem:
If the Server is disconnected while running sequence with GC/MS instrument, the sequence aborts.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS 2.2.
Keyword: Acquisition
One-line Description:
Connection problems with hardware could put the instrument in indeterminate state
Problem:
During an acquisition run, If connection problems are encountered between the hardware and the application, the software would abort the runs. The hardware is not aware of the disconnection and reconnecting to the hardware could put the instrument in indeterminate state.
Temporary Solution:
Perform a close connection and stop the hardware. Relaunch the application to get to a good state.
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Submitted or Validating run items will get aborted if connection to OpenLAB Server is lost
Problem:
Any submitted or validating runs will get aborted if connection to OpenLAB Server is lost at the time of submission. All the pending runs will go to completion.
Temporary Solution:
n/a
Fix Information:
This is resolved in OpenLAB CDS 2.2.
Keyword: Acquisition
One-line Description:
In case of overlap injections, "Stop sequence after current run completes" aborts the current run ONLY and discards the already prepared sample
Problem:
In the case of overlap injections, when user performs "Stop sequence after current run completes", only the current injection will complete its data acquisition. The already prepared sample (already in the autosampler's sample loop) for the next run will be discarded, the sequence will be aborted. When user run a subsequent sequence, an error will occur depending on the instrument technique (LC or GC) due to the leftover sample in the injector loop, user has to re-submit the same sequence to be able to continue.
Temporary Solution:
n/a
Fix Information:
This is resolved in OpenLAB CDS 2.1. When user performs "Complete current run and abort sequence", sequence will be aborted after the data acquisition has completed for the already prepared sample (the overlapped sample).
Keyword: Acquisition
One-line Description:
After performing 'Review Completed Injections", the subsequent injections within the same sequence will have the same injection time
Problem:
After performing "Review Completed Injections", the subsequent injections within the same sequence will have the same injection time in Data Analysis UI as well as in reports.
Temporary Solution:
n/a
Fix Information:
This is resolved in OpenLAB CDS 2.0 HF02 and OpenLAB CDS 2.1.
Keyword: Acquisition
One-line Description:
Cannot re-launch LC instrument after closing acquisition client
Problem:
After installing the B.01.01 GC Driver on OpenLAB CDS 2.1, it is not possible to re-launch an LC instrument. The AcquisitionClient.exe process does not terminate when closing the application which prevents the re-launch of a previously closed LC instrument.
Temporary Solution:
NA
Fix Information:
Resolved in OpenLAB CDS 2.1 SR1.
Keyword: Acquisition
One-line Description:
35900E module list is truncated when printing to XPS in landscape orientation
Problem:
In Chinese version of OpenLAB CDS 2.1, if you print the 35900E module list using XPS in landscape orientation, the list is truncated on the right side of the page. This issue does not occur if printing to a physical printer.
Temporary Solution:
n/a
Fix Information:
This issue is caused by older version of .NET Framework. It is resolved with .NET Framework 4.6.2.
Keyword: Acquisition
One-line Description:
Replicate injections may not run when editing current running sequence more than once
Problem:
In a sequence having more than 2 replicate injections per line, if the user edits the current running sequence more than once in the middle of acquiring a replicate injection, then the next pending replicate injection will complete, however, all subsequent replicate injections in the line will be skipped and the next line in the sequence will start acquiring. As a result, when the user views the current running sequence, the State column shows "Acquiring" for two adjacent lines in the sequence table.
Temporary Solution:
When a sequence has more than two replicate injections per line, do not edit the current running sequence in the middle of acquiring the replicate run multiple times. Editing the running sequence once is OK and does not cause any problem.
Fix Information:
This issue is resolved in OpenLAB CDS 2.1 SR1 HF02 and OpenLAB CDS 2.2.
Keyword: Acquisition
One-line Description:
Cannot print sequence from sequence layout
Problem:
When trying to print a sequence, an error pops up: "The following method(s) need(s) to be updated, please save them to report their parameters..." and the sequence cannot be printed.
Temporary Solution:
A workaround is to click the "Save" icon in the Sequence Report window and select any of the file options (Excel, PDF, Word) to save. Once the file is saved (e.g., PDF) then you can open the PDF and print the file.
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword: Acquisition
One-line Description:
Instrument status goes Idle during sequence more than 250 runs
Problem:
When running sequence having more than 250 lines (each more than 5 minutes long at maximum data rate) on four SS420x and two 35900 instruments, some of the SS420x instruments would go to an Idle status, however, the Run Queue state says "Acquiring". In these states, the SS420x instruments will not start to collect data and sequence is stuck. The 35900 instruments experience no problem with collecting data.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Acquisition
One-line Description:
Printing method in Word format shows incorrect total page count in footer
Problem:
When printing a method in Word format with multiple pages (e.g., 3 total pages), the footer shows "Page 1 of 1" on all pages, instead of page x of total number of pages.
Temporary Solution:
Use PDF format instead of Word format when printing method.
Fix Information:
This issue is due to a known Microsoft page number rendering issue.
Keyword: Acquisition
One-line Description:
TIC signal is not displaying in Online Signal window during data acquistion if none is selected in GC's signal setting
Problem:
TIC signal will not be displayed in Online Signal window when acquiring data if None is selected in GC's signal settings. This is only a display issue, the data is actually acquired and saved.
Temporary Solution:
Select one of the GC signal (e.g. Test Plot, it dose not need to be checked to save), TIC will start showing in Online Signal window during data acquisition.
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Acquisition Client does not get failover notification when AIC switches to failover
Problem:
In a Client/Server environment, when both AIC and the Client lose connection to the Server, the failover message is not displayed on the Client right away.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Acquisition
One-line Description:
Instrument client crashes upon opening a dual GC sequence file longer than 155 lines
Problem:
An issue has been identified on a dual tower GC instrument in OpenLAB CDS version 2.2. User can create, save and run a dual sequence longer than 155 lines successfully. However, when re-opening this sequence file, instrument client crashes.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.3. This issue is fixed in OpenLab CDS v2.2 Update 04.
Keyword: Acquisition
One-line Description:
Need warning message that mismatched labels in sequence will cause reports not to be generated
Problem:
In a sequence if the filters in "Label" column and "Label selection" column (from "Create report" tab) do not match, then user is not notified that this will cause reports not to be generated.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Acquisition
One-line Description:
Sequence is stuck in "Reporting" when processing method calls for hardcopy report but default printer is not configured
Problem:
When no default printer is configured on standalone workstations or AICs and the sequence “Create report” line is set to print a hardcopy of sequence summary report, then the sequence run will get stuck in “Reporting” without throwing any error.
Temporary Solution:
The workaround for this issue is to kill AcquisitionServer.exe, restart the computer, and re-launch the instrument. After the instrument is launched, the result set will be available to load in Data Analysis. To avoid this issue, do one of the following: 1. Verify that the Default printer is configured before submitting the sequence run. 2. Remove "Default" from the Printer column in the "Create report" tab before submitting the sequence run. This will not print a hard-copy of the report, but an report file (PDF, CSV, Excel, Text, Word) will still be created in the result set.
Fix Information:
This issue will be fixed in OpenLab CDS v2.5 Update 02.
Keyword: Acquisition
One-line Description:
Acquisition crashes on the second click on "Print" to display GC Headspace method parameters
Problem:
If you load a GC Headspace acquisition method and click "Print" to view the method parameters, the Headspace parameters are not displayed. An error message pops up when you click "Refresh". Once you close the sequence print window and click "Print" again, the Acquisition client crashes.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 03.
Keyword: Acquisition
One-line Description:
Cannot take snapshot of current running injection after closing/opening same client or opening new client
Problem:
This behavior is observed on the launch of a new client when an injection is in progress or closing/opening same client. The behavior is also observed if the run was started by a different user. Both have the root cause, which has nothing to do with the user's privilege. The newly launched client doesn't get the notification about the injection in progress because of which it doesn't allow Snapshot. If the user waits for the current injection to complete then they can do snapshot after the next injection starts.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 04.
Keyword: Acquisition
One-line Description:
Session connection to instrument controller is lost when ELSD is left in standby mode
Problem:
If the ELSD is left in Standby mode for approximately 30 minutes, the Acquisition Server appears to time out or lose connection. The error message reported is "The session connection to instrument controller 'PCName' for instrument 'elsd' has been lost".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4, OpenLab CDS v2.3 Update 03, and OpenLab CDS v2.2 Update 04.
Keyword: Acquisition
One-line Description:
Detectors do not perform auto-balance when no injection/instrument blank is selected as injection source
Problem:
Agilent LC detectors do not perform pre- or post analysis auto-balance when the injection source is specified as no injection/instrument blank.
Temporary Solution:
n/a
Fix Information:
Agilent recommends to set injection volume to "0" and use ALS as the injection source.
Keyword: Acquisition
One-line Description:
The current running/pending sequences might be interruptted due to unstable network
Problem:
There are rare cases on a client/server system, when the network is unstable, causing connection loss of AIC to the content management server, the current running/pending sequences might be interrupted/aborted.
Temporary Solution:
Ensure the network is stable, there are no constant drop connections.
Fix Information:
This has been fixed in OpenLab CDS v2.3.
Keyword: Acquisition
One-line Description:
In OpenLab CDS v2.x, the raw data (.dx) acquired on Agilent LC modules in general are larger in size
Problem:
In OpenLab CDS v2.x, the raw data (.dx) acquired on Agilent LC modules in general are larger in size comparing to OpenLab CDS ChemStation or EZChrom Edition’s, especially for the data that are acquired on VWD modules. This is because the data points generated from instrument traces are by default collected and saved with the raw data. Unlike ChemStation or EZChrom Edition, CDS v2.x users do not yet have an option to select which instrument traces to collect from the instrument client UI.
Temporary Solution:
n/a
Fix Information:
OpenLab CDS v2.4, OpenLab CDS v2.3 Update 04, and OpenLab CDS v2.2 Update 05 will significantly decrease the data size on VWD modules only. Agilent is considering providing a proper fix in a future release.
Keyword: Acquisition
One-line Description:
Sequence creation template not working for back injector on GCs
Problem:
Selecting back injector for OpenLab CDS sequence creation template injections does not apply that setting when applying that template to create a sequence. The front injector is selected for the injections even though the template was set to back. If you select back injector in the empty sequence first before you apply the template then the samples field in the apply dialog is inactive and cannot be changed from 1.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Acquisition
One-line Description:
If default printer is not a physical printer, RX files may to be missing in result sets
Problem:
If the default printer set on the AIC is not a physical printer (e.g., Microsoft Print to PDF, Microsoft XPS Document Writer, etc.) and the processing method in sequence contains "Print" for reports, this will cause RX files to be missing in result sets and hence data cannot be loaded in Data Analysis.
Temporary Solution:
Before submitting the sequence run, always verify that the default printer on the AIC is configured with physical printer.
Fix Information:
This issue will be fixed in a future software release.
Keyword: Acquisition
One-line Description:
Possible network printing issue after upgrade to CDS 2.4
Problem:
An upgrade from a previous OpenLab CDS version to OpenLab CDS 2.4 resets the InstrumentService User to "System" w/o checking if the account had been previously changed to a domain account to enable network printing. If that was the case, the InstrumentSystem account has to be set back manually to an appropriate user with network printing rights.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
RX files missing in result sets
Problem:
Intermittently RX files are missing from the result sets resulting in data not visible in the data analysis window. This has been found to be caused by a race condition preventing the file creation.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4, OpenLab CDS v2.3 Update 04, and OpenLab CDS v2.2 Update 05.
Keyword: Acquisition
One-line Description:
There is no indication for user to start a manual injection when the injection source is specified "External"
Problem:
When manual injection is performed in OpenLab CDS, there is no indication for user to start the injection with the injection source specified "External", especially when running a sequence.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Acquisition
One-line Description:
Cannot "Submit Sequence File" from API due to case sensitive in compound custom parameter name
Problem:
If compound custom parameter name is defined as 'Cnb1' in OpenLab project, but is modified as 'CNb1' when creating the sequence file in the API, then an error "Undefined compound parameter 'CNb1' found" occurs upon submitting the sequence file.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and v2.4 Update 07.
Keyword: Acquisition
One-line Description:
Acquisition crashes with error "System.Argument.Exception: name already exists" when selecting processing method
Problem:
Acquisition crashes with error "System.Argument.Exception: name already exists" when selecting processing method that contains compounds with same name but different case sensitivity (e.g., benzene & Benzene).
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, CDS v2.4 Update 03, and CDS v2.3 Update 07.
Keyword: Acquisition
One-line Description:
Sample or compound custom parameter values with "," digit separator not handled properly
Problem:
In a dual sequence, the sample or compound custom parameter values with "," digit separator are not being handled properly for back injector. The "," separator is lost (for example "0,89" becomes "89"). This issue does not occur with front injector.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 07.
Keyword: Acquisition
One-line Description:
Cannot "Submit Sequence File" from API when optional sample custom parameter is missing
Problem:
If the optional sample custom parameter name is missing in the sequence file, when the user tries to "Submit Sequence File" from API, an error "Incorrect number of sample custom parameters found. Expected N but found N-1" occurs.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and v2.4 Update 07.
Keyword: Acquisition
One-line Description:
Acquisition client crashes upon launching Hitachi instrument
Problem:
Acquisition client crashes upon launching Hitachi instrument
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 01.
Keyword: Acquisition
One-line Description:
The configured instrument modules in acquisition method report may show in alphabetical order
Problem:
The order of the configured instrument modules in Acquisition Method UI window may show differently in printed acquisition method report. When user makes changes to an opened acquisition method and save the changes, the printed acquisition method report will show the instrument set points of the configured modules in alphabetical order regardless of what is in the Acquisition Method UI window.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue. This has been fixed in OpenLab CDS v2.5.
Keyword: Acquisition
One-line Description:
Print icon in Acquisition is greyed out
Problem:
The print icon in Acquisition is greyed out after the default printer is removed and a new one is selected.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, CDS v2.4 Update 03, and CDS v2.3 Update 07.
Keyword: Acquisition
One-line Description:
"Unable to connect to instrument server" after OpenLab CDS client is locked
Problem:
With OpenLab CDS v2.4 Client/Server system, two users accessing the same instrument can cause an abnormal termination of the AcquisitionServer process on the Agilent Instrument Controller (AIC). The users will get an access denied error "Unable to connect to instrument server" and acquisition runs in process will stop. When this occurs, the AIC must be restarted. This issue occurs when the OpenLab CDS client is locked either the user or by "Inactivity" timeout.
Temporary Solution:
Agilent recommends that Client/Server users to NOT use "Lock" in Acquisition and to disable automatic locking feature in OpenLab CDS Control Panel. From the OpenLab CDS Control Panel, go to Administration > Security Policy, click on Edit Security Policy, and enter a value of 0 for "Inactivity time before locking the application (mins)". In order for this to take effect, restart the OpenLab CDS Control Panel (no need to "Close Connection") and close the client. Alternatively, Windows lock screen timeout can be used to lock the entire desktop.
Fix Information:
This issue will be fixed in OpenLab CDS v2.4 Update 03 and OpenLab CDS v2.5.
Keyword: Acquisition
One-line Description:
User sporadically fails to connect to instruments when using Sample Scheduler or Walkup
Problem:
Users who use Sampler Scheduler or Walkup in OpenLab CDS 2.x may experience disconnections from the instruments.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 09.
Keyword: Acquisition
One-line Description:
RX file generation fails sporadically when saving results
Problem:
In very rare cases, the generation of .acaml file can fail because a temporary file in the following folder cannot be generated: C:\Windows\system32\config\systemprofile\AppData\Local\Agilent Technologies Subsequently, the RX result file generation fails.
Temporary Solution:
For CDS 2.4 and prior versions, adding the following folder to the Antivirus exclusion list prevents the issue: C:\Windows\system32\config\systemprofile\AppData\Local\Agilent Technologies
Fix Information:
The issue is fixed in OpenLab CDS v2.5.
Keyword: Acquisition
One-line Description:
Injection audit trail records the changed objects of an acqusition method not the corresponding values when the acqusition method can be automatically resolved upon sequence submission
Problem:
When a user opens an acquisition method on an instrument which has different configuration than the one on which the method was originally created, if the method can be automatically resolved, all changes will be recorded in the acquisition method audit trail including the changed objects and their corresponding values. However, when user submits a single or sequence run, if the specified acquisition method does not match the current instrument configuration, but can be automatically resolved, the injection audit trail only records which objects in the acquisition method have been changed, not their corresponding values.
Temporary Solution:
Before submitting any runs, open the acquisition method, resolve the changes, and save it.
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Instrument goes offline upon opening incompatible sample prep method
Problem:
Agilent LC goes offline when opening a sample prep method that needs manual resolution.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 08.
Keyword: Acquisition
One-line Description:
Failed to upload partially acquired result sets due to system failure
Problem:
In a client/server environment, any unexpected failure during data acquisition will trigger a partial result set upload. When uploading fails due to unavailability of the OpenLab Server/ECM XT, system will not retry until next rebooting of the AIC or restarting of OpenLab Instrument Service on the AIC.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue. This has been fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 05
Keyword: Acquisition
One-line Description:
MS instrument cannot run sequence after upgrading to OpenLab CDS 2.3 Update 08
Problem:
After upgrading to OpenLab CDS 2.3 Update 08, the MS instrument (GC/MS or LC/MS) cannot run sequence.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.3 Update 10.
Keyword: Acquisition
One-line Description:
User specified result path is not saved with the user settings
Problem:
The result path by default points to "\Project\Results" folder. When a sub-folder is designated to store the result sets by the user, this path does not saved in the user setting. As a result, the result path is reset to the "\Project\Results" root every time user re-launches the instrument client.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue. This has been fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 07.
Keyword: Acquisition
One-line Description:
Performing snapshot or review completed injections may cause current running single sample analysis or sequence to terminate due to unstable network
Problem:
Current running single sample analysis or sequence may get terminated when user performs a snapshot or review completed injections. This occasionally happens on a Client/Server system where the network is not stable.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, OpenLab CDS v2.4 Update 07, and OpenLab CDS v2.3 Update 12.
Keyword: Acquisition
One-line Description:
Stopping runs from 6890 GC's key pad does not get recorded in activity log and injection audit trail
Problem:
When user stops a run from 6890N GC's key pad, this action is not recorded in the instrument activity log and the injection audit trail. Note: this action is not supported on 6890A model.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in the following releases: OpenLab CDS v2.5 OpenLab CDS v2.4 Update 10
Keyword: Acquisition
One-line Description:
Manual editing of column tags used in G1316A/B/C is not supported
Problem:
Column tags used in legacy modules Agilent 1200/1260 and 1290 Infinity Thermostatted Column Compartments G1316A, G1316B and G1316C do not support editing of otherwise editable fields when used in OpenLab CDS v2.x. This restriction does not apply to column tags used in state-of-the-art column compartments G7116A/B, G7130A and the Valve Thermostat Cluster (VTC). In these modules, column tags can be edited through direct access in the LC Driver.
Temporary Solution:
None available
Fix Information:
No fix available
Keyword: Acquisition
One-line Description:
Chromatogram is shifted, offset in 6890
Problem:
In the GC Drivers 3.0 version, the chromatogram for the channel is shifted when a signal is saved which was not saved in the previous run using 68xx.
Temporary Solution:
n/a
Fix Information:
Resolved in GC driver 3.1.205.
Keyword: Acquisition
One-line Description:
A sequence audit trail entry "Sequence automatically updated: Removed duplicated entry ids" is observed on an upgraded system
Problem:
Sequences that were created in 2.4 or earlier versions using copy/paste lines action have duplicate entry IDs for the added sequence lines. 2.5 and higher versions have unique entry ID for each sequence line. Thus, when a sequence like that opened in 2.5 or higher versions, a new entry will be added to the sequence audit trail to notify user that such a change is automatically updated, and duplicate entry IDs are removed even though user did not make any changes.
Temporary Solution:
n/a
Fix Information:
This is an expected behavior due to a design change in OpenLab CDS v2.5 and higher versions.
Keyword: Acquisition
One-line Description:
Changing instrument setpoints is not possible from instrument status dashboard without the proper permissions
Problem:
When user does not have "Create and modify acquisition method" permission, modifying the instrument setpoints from its status dashboard is not possible with only "Manual control" permissions.
Temporary Solution:
n/a
Fix Information:
This has been fixed in OpenLab CDS v2.5.
Keyword: Acquisition
One-line Description:
Instrument Client may close unexpectedly after repeatedly clicking on Take/Release Control of the instrument
Problem:
Instrument client may close unexpectedly after user repeatedly clicking on Take/Release Control of the instrument. However, this will not interrupt any runs.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.4 Update 09.
Keyword: Acquisition
One-line Description:
Shimadzu GC stays connected after closing connection
Problem:
After user performs "Close Connection" from OpenLab Control Panel, Shimadzu GC still stays connected.
Temporary Solution:
n/a
Fix Information:
This issue has been fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 07.
Keyword: Acquisition
One-line Description:
Acquisition method UI is not displaying for Agilent GC with PAL3 if not configured properly
Problem:
When configuring a PAL3 with an Agilent GC, the order of adding the components to the "configured modules" list matters. 1. Agilent GC and then PAL3: Acqusiiton method UI of Agilent GC displays properly 2. PAL3 and then Agilent GC: Empty acquisition method UI of Agilent GC
Temporary Solution:
To configure Agilent GC with PAL3 properly, add "Agilent GC" first to the configured modules list and then followed by PAL3 to avoid method UI displaying issue.
Fix Information:
Agilent has identified this issue. A temporary fix is provided
Keyword: Acquisition
One-line Description:
Session connection has been lost
Problem:
Run may get interrupted on fraction collector when fraction collection time start is set from 0.0 minute in acquisition method.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 02.
Keyword: Acquisition
One-line Description:
"Failed to set fraction start info. Operation is not valid due to the current state of the object."
Problem:
Error "Failed to set fraction start info. Operation is not valid due to the current state of the object." may occur when submit a sequence created on a fraction collector with recovery collector to the same fraction collector without recovery.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 02.
Keyword: Acquisition
One-line Description:
Sequence creation template (.stx) can be overwritten in Portuguese system
Problem:
Portuguese OpenLab CDS allows to overwrite sequence creation template.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.4 Update 07.
Keyword: Acquisition
One-line Description:
The current data acquisition may get interrupted after performing a snapshot
Problem:
The current running sequence may get interrupted with error "Unable to connect to instrument server" after user has performed a snapshot and closed the snapshot window. This only happens with a specific workflow. On a Client/Server system, when multiple users submit sequences from different projects on the same instrument, for example, user 1 may edit/update a pending sequence from one client, meanwhile user 2 can perform a snapshot on another client. When user 1 commits the changes on a pending sequence, closes the instrument client, and user 2 then closes the snapshot window from another instrument client, these series of actions will interrupt the current running sequence.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6, OpenLab CDS v2.4 Update 09 and OpenLab CDS v2.5 Update 04.
Keyword: Acquisition
One-line Description:
OpenLab CDS v2.5 Russian system crashes when editing sample custom field
Problem:
On OpenLab CDS v2.5 Russian system, when a user tries to edit a running sequence by changing a sample custom field, the Acquisition client crashes.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 01.
Keyword: Acquisition
One-line Description:
Sample Scheduler doesn't offer dual External injection when GC is configured with dual gas sampling valves only
Problem:
Sample Scheduler, running on top of OpenLab CDS v2.5, does not offer External Injection for dual sequences.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 02
Keyword: Acquisition
One-line Description:
Part of the configuration UI on some instruments is cut off due to resizing issue
Problem:
In case of instruments like Shimadzu, the configuration screen may not be entirely visible due to a resizing issue.
Temporary Solution:
n/a
Fix Information:
This issue has been fixed in OpenLab CDS v2.5, OpenLab CDS v2.4 Update 11 and OpenLab CDS v2.3 Update 13.
Keyword: Acquisition
One-line Description:
Partially acquired result set may not be available due to AIC power failure
Problem:
There may be cases where the current running sequence is interrupted and terminated due to a power failure on the workstation PC or an AIC. When this happens, the partially acquired result may not be available to load for further data processing.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue, and the issue is fixed in the following releases: OpenLab CDS v2.5 OpenLab CDS v2.4 Update 09 OpenLab CDS v2.3 Update 12
Keyword: Acquisition
One-line Description:
Starting acquisition with 7697A headspace causes XML error entry in Activity log
Problem:
When the acquisition user interface is started for a GC instrument with a 7697A Headspace configured an error "Error in XML document" is logged in the activity log. This error has no impact on the operation of the system. It will be removed in a future version of the respective instrument drivers.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in headspace driver 3.1 for 7697A that is released with OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
Last lines of dual sequence gets unchecked after submission
Problem:
When user submit a dual simultaneous sequence on a GC and when this sequence is in pending state, view the pending sequence, last lines of the sequence always get unchecked without user intervention.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 02.
Keyword: Acquisition
One-line Description:
Instrument stays "not connect" after successfully launching instrument client
Problem:
A specific workflow will cause instrument to stay in "not connected" state after the instrument client was successfully launched. This often happens on a client/server environment.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, OpenLab CDS v2.4 Update 07, and OpenLab CDS v2.3 Update 13.
Keyword: Acquisition
One-line Description:
Run queue layout is not saved and always back to default settings
Problem:
When user customizes the run queue layout (column width), the settings are not saved.
Temporary Solution:
n/a
Fix Information:
This will is fixed in OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
Current running dual sequence table locks pending lines from editing as run progresses
Problem:
When user edit a current running dual sequence, to insert/paste copied lines below or above a pending injection line, only completed injections and current acquiring run should be locked from editing. However, a number of pending injections are also locked from editing as run progresses.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
Error occurs upon launching instrument
Problem:
"Failure while initializing modules" may occur when launching an instrument. User may encounter this error especially on a scalable client/server system where it generates a large size of system activity logs.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.4 Update 11.
Keyword: Acquisition
One-line Description:
After changing a vial in a running sequence, the old vial is injected
Problem:
When user edits and updates a running sequence to modify an injection vial, the old vial is actually injected instead of the modified one. This is due to a timing issue on the UI. When current running sequence is in "Editing" mode, user can still edit the sequence after having clicked on "Update". As a result, the subsequent update does not get picked up by the instrument.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.4 Update 11.
Keyword: Acquisition
One-line Description:
Sequence may get aborted with error "same file is being used from different folders"
Problem:
Sequence run may get aborted with error "same file is being used from different folders" when it is created by importing a CSV file, then applying a sequence template.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
Editing a running sequence on Agilent GC with Headspace may fail
Problem:
User may fail to edit a current running sequence on an Agilent GC with headspace. This happens when the CDS client gets disconnected unexpectedly from the network while editing the sequence.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
Microsoft.NET framework error when displaying TIC Scan signal on Online Signals plot
Problem:
Microsoft .NET framework error occurs when displaying TIC Scan signal on Online Signals plot. this happens when user runs a LCMSD SQ and displays the TIC Scan signal on Online Signals plot window.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
Acquisition client stuck at loading with an empty acquisition method UI
Problem:
Acquisition client may get stuck at loading forever with an empty acquisition method UI. The session has to be terminated from Windows' task manager. This may happen if a manual method resolution needs to be resolved on an Agilent GC instrument when it was last loaded and did not get resolved manually.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
Cannot edit current running sequence, review completed injections or perform snapshot sporadically from instrument client
Problem:
There is a timing issue which may lead system in a state where editing a current running sequence, review completed injections or perform a snapshot is not possible. This often happens when there are replicate injections in a sequence table. One user may edits/update the current running sequence when data acquisition is in progress on the replicate injection line, at the same time another user from a second client may try to review completed injections or perform a snapshot, or it can happen with one or two users on same client. These actions may lead to a state when user launches a snapshot from Online Signals window, nothing happens and the user cannot edit the current running sequence, or review completed injections.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.4 Update 11.
Keyword: Acquisition
One-line Description:
Not able to view current running sequence when result name exceeds 28 double byte characters
Problem:
User is not able to view current running sequence when a result name exceeds 28 double byte characters. However the sequence will complete successfully and the result can be loaded for data processing.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
The injection time is Window's epoch time if there is no injection performed.
Problem:
The injection time is set to Window's epoch time "1601-01-01T00:00:00Z" if there is no injection performed. For example, the injection time is displayed or reported as 1601-01-01 03:00:00 in the UTC+3 time zone when there is no injection done, or the injection was aborted before the actual injection was done.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Instrument client may close unexpectedly with errors upon maximizing its window
Problem:
Instrument client may close unexpectedly with errors when user maximizes the instrument client windows (on "Status" layout). This only happens when instrument client was closed with a minimized status dashboard of a configured module, e.g. a Valco valve. Since this only occurs on the instrument clients, any current and pending runs will not be interrupted.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01.
Keyword: Acquisition
One-line Description:
Instrument client may close unexpectedly upon clicking "Release" button
Problem:
On an instrument configured with CTC PAL XT, when user clicks on "Release" button from instrument client's ribbon bar to release the control, the instrument client closes with unexpected errors.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01.
Keyword: Acquisition
One-line Description:
Not able to load result set due to a failure editing/updating running sequence
Problem:
A result set cannot be loaded in Data Analysis after a "completed" sequence run. This is due to a timing issue when editing/updating the running sequence failed in the middle of the data acquisition. The failed update can be found in the instrument activity log with the following message: "Run Queue - Update sequence - Failed, Cannot load data context. See inner exception for details."
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5.
Keyword: Acquisition
One-line Description:
Instrument client sporadically becomes non-responsive upon starting snapshot on current running sample
Problem:
Instrument client sporadically becomes non-responsive when user starts a snapshot on a running sample.
Temporary Solution:
Close instrument client and relaunch it.
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 07, and OpenLab CDS 2.5 Update 11.
Keyword: Acquisition
One-line Description:
Sporadically an unexpected error occurs upon relaunching Hitachi LC
Problem:
Instrument client sporadically threw an unexpected error upon relaunching for Hitachi LCs.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Acquisition
One-line Description:
Instrument client crashes upon unlocking a locked manual resolution screen by a different user
Problem:
When an instrument client is locked with a manual resolution screen, and a different user tries to unlock it, the instrument client crashes.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 08.
Keyword: Acquisition
One-line Description:
Result set cannot be loaded in Data Analysis due to duplicate data files
Problem:
A freshly acquired result set cannot be loaded in Data Analysis due to duplicate data files (two versions of .dx files). This could happen during editing a running sequence. Due to a timing issue, where the current acquiring injection in the sequence table is not locked properly when user clicks to edit a running sequence, this allows user to delete the acquiring injection and update the running sequence. As a result, the completed injection above the current acquiring one will re-inject to acquire data. This action leads to two versions of .dx files present in the result set.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.4 Update 11.
Keyword: Acquisition
One-line Description:
Result set cannot be loaded for reprocessing due to corrupted data
Problem:
There is a timing issue in processing of writing data collected from all signal channels, which may cause data corruption.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS 2.6 Update 05 and OpenLab CDS 2.5 Update 09.
Keyword: Acquisition
One-line Description:
Diagnostic data sometimes not available for reporting
Problem:
When using diagnostics data like "Run start - Pressure", "Run start - Flow", "Run Start - Dad - UV Lamp Burn time" in reporting, in rare cases these values are not available. This can be caused when the instrument modules go into run status for a very short time, and he OpenLab CDS acquisition is not triggered during this time. For example when a manual injector is moved to the inject position and then back to flush the injection loop.
Temporary Solution:
Always ensure that a manually started run does trigger data acquisition in OpenLab CDS before stopping the run again.
Fix Information:
Fix under investigation.
Keyword: Acquisition
One-line Description:
Error occurs upon clicking on "Edit Signature Settings" of a project
Problem:
Error "You do not have permission to view or it has been deleted" occurs when a system administrator tried to "Edit Signature Settings" of a project. This might have been caused by a disabled user account with a higher level e-signature assignment.
Temporary Solution:
Workaround is to re-enable the disabled user account.
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Acquisition
One-line Description:
Running sequence gets interrupted by unexpected exception during editing
Problem:
When user edits a running sequence which has been running for a long period of time, an unexpected error occurs, as a result, run gets aborted. This happens sporadically on a long running sequence.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 07, and OpenLab CDS 2.5 Update 11.
Keyword: Acquisition
One-line Description:
"Lost Connection" message pops up upon launching instrument with no designated storage path
Problem:
When the designated data storage has empty storage path configured (OpenLab Control Panel>Administration>System Configuration>System Settings), upon launching an instrument, a misleading error message "Lost Connection" pops up.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 09.
Keyword: Acquisition
One-line Description:
Sample Scheduler not able to get the proper sequence line information when sequence is aborted due to method validation error
Problem:
Sample Scheduler is not able to get the proper sequence line information when sequence is aborted due to method validation error.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Acquisition
One-line Description:
Not able to edit a running sequence due to a timing issue when switching between "View Running Sequence" and "Editing" mode
Problem:
When user clicks on "Edit" on a running sequence, there might be a timing issue that system gets stuck in between "View" and ""Edit" mode, as a result, the "Cancel" and "Update" button are both disabled for user. User has to close instrument client to exit this state.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Acquisition
One-line Description:
The version of Apache HTTP Server is out of date
Problem:
The version of Apache HTTP Server is out of date.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Acquisition
One-line Description:
Unexpected error occurs upon closing manual resolution UI window
Problem:
When loading an acquisition method that involves manual resolution, if acquisition method manual resolution window is closed by using Windows taskbar or short cut "Alt +F4" before all modules get resolved (e.g. Agilent LC modules), unexpected error occurs, which leads to instrument client's crash.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 08.
Keyword: Acquisition
One-line Description:
"Agilent Test Services" and "Agilent Test Services Central Management" services are not started after a server restart
Problem:
It has been observed occasionally that the "Agilent Test Services" and "Agilent Test Services Central Management" services are not started after a server restart. These services depend on the "Agilent OpenLab Data Repository Base Service" and will fail to start if that service is not yet started.
Temporary Solution:
Set the "Agilent Test Services" and "Agilent Test Services Central Management" services to "Automatic (Delayed start)"
Fix Information:
The issue is fixed in OpenLab CDS v2.7.
Keyword: Acquisition
One-line Description:
Run gets interrupted when run queue being re-ordered
Problem:
There might be a timing issue when user submit a request to re-order run queue items, an inner exception is thrown, which interrupts data acquisition, therefore, run gets aborted. This happens sporadically.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 07, and OpenLab CDS 2.5 Update 11.
Keyword: Acquisition
One-line Description:
Ad Hoc mode is in general not supported for Agilent LC or GC with a 3rd party module
Problem:
Ad Hoc run is in general not supported for Agilent LC or GC when a 3rd party module is part of the instrument configuration, unless it is documented differently in the 3rd party driver's documentation.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Sequence run gets interrupted due to an unexpected error
Problem:
Sequence run gets interrupted due to an unhandled exception. This happens sporadically on samplers that support full sequence download, for an example, when pausing a sequence run from Run Queue on a G7697 Headspace sampler, sequence run may get aborted with error "The unit is not in a valid state to execute an operation".
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09 after applying G7696A firmware A.01.08.4.
Keyword: Acquisition
One-line Description:
Incomplete injection list after a result set loaded in Data Analysis
Problem:
Due to timing issue when writing data during "Review Completed Injections", the acquired data may not be registered properly, hence when the result set is loaded in Data Analysis, the injection list does not have the complete acquired injections, even though all acquired injections are present in the designated storage.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in a future release.
Keyword: Acquisition
One-line Description:
Current running sequence is stuck in "In Review" mode
Problem:
On a client/server system, when multiple users from different instrument clients click "Edit" and "Snapshot" or "Review Completed Injections" on the running sequence at the exact same time, the current running sequence may get stuck in "In Review" state.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Acquisition
One-line Description:
Runs submitted using Sample Scheduler gets interrupted
Problem:
When using Sample Scheduler, after a few days of running, data acquisition stops working due to a deleted certificate.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Acquisition
One-line Description:
"Unsaved changes" message box prompts upon closing Hitachi LC
Problem:
"Unsaved changes" message box prompts when nothing has changed. This is observed on Hitachi LC, when user launches the instrument client, releases control of the instrument, then close it.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Acquisition
One-line Description:
FLD signal not integrated by delay calibration
Problem:
FLD signal is not integrated using Delay Calibration for fraction collector.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 01, OpenLab CDS v2.6 Update 08, and OpenLab CDS v2.5 Update 11.
Keyword: Acquisition
One-line Description:
Error occurs when PC name is changed and then reverted back to the original name
Problem:
When PC name (OpenLab CDS Workstation) is changed and then reverted back to the original name, the following error occurs: "Failed connection to instrument controller 'PC NAME'. Please verify if instrument service is in run state. Check activity log for more information."
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Acquisition
One-line Description:
Online Signal sporadically disappears
Problem:
Online signals sporadically disappears during data acquisition. This appears to be a display issue on instrument clients, does not affect data being saved.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in CDS 2.7 Update 01.
Keyword: Acquisition
One-line Description:
Reports cannot be generated at the designated folder (Windows file system) when using Sample Name or Data File Name with a trailing space as subdirectory.
Problem:
When using Sample Name or Data File Name with trailing space as subdirectory to print PDF reports in Windows file system from Data Analysis, error occurs and report cannot be generated. OpenLab CDS does not parse out the trailing space from Sample name or Data File Name, which results in report print failure.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
Acquisition or Data Analysis window closes unexpectedly upon unlocking
Problem:
When user unlocks a locked acquisition or data analysis window, it closes unexpectedly with error "Object reference not set to an instance of an object".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Acquisition
One-line Description:
A suspended sequence run with a wait line may resume and complete data acquisition without waiting
Problem:
In a rare case scenario, a suspended sequence run with a wait line which has no timer specified may resume and complete its data acquisition without going into waiting state.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Acquisition
One-line Description:
Instrument client times out intermittently when browsing open an acquisition method in a heavily loaded folder
Problem:
When opening an acquisition method in a heavily loaded method folder, intermittently user is prompted with "Lost Connection" message, indicating the client will shut down, system goes into failover mode. This is due to a communication time out between the client PC and server.
Temporary Solution:
Using subfolders to evenly distribute methods stored under "Methods" folder may help.
Fix Information:
This issue in fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Acquisition
One-line Description:
Sequence name token used in data file name is not properly resolved
Problem:
When a sequence token <SEQ> is used in data file name in sequence table editor, the token cannot be properly resolved. In the result set, it was resolved as "-SEQ-". Sequence name token <SEQ> was not supposed to be one of the available tokens for data file name in OpenLab CDS v2.7 release. It has been removed.
Temporary Solution:
n/a
Fix Information:
The issue in fixed in OpenLab CDS v2.7 Update 08.
Keyword: Acquisition
One-line Description:
A sequence run stays in "In Review" state and cannot proceed to completion
Problem:
A common workflow may cause a sequence run stuck in "In Review" state, as a result it cannot proceed to end the sequence successfully.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Acquisition
One-line Description:
Empty data files may be stored when a sequence run is aborted due to a hardware error
Problem:
A currently running sequence may be interrupted and aborted due to a hardware error, e.g., wrong trays/vials. Sometimes an empty data file is stored and no signals displayed when loaded in Data Analysis. This issue has been investigated and found to be reproducible only when removing the autosampler tray at a specific time. Other scenarios did not result in an empty data file. This issue affects OpenLab CDS versions 2.7 and earlier.
Temporary Solution:
Agilent recommends laboratories check for empty data files as part of the laboratory procedure for handling aborted sequence runs due to hardware errors.
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
Sequence is stuck in pending state on PerkinElmer GC
Problem:
A sequence run is stuck in pending state upon submission on a PerkinElmer GC when the specified acquisition method does not match the configuration and needs manual resolution.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Acquisition
One-line Description:
Some columns defined in a sequence CSV file (in Portuguese) cannot be imported
Problem:
On a Portuguese system, when user imports a sequence CSV file, an error message prompts that some columns cannot be imported. The impacted columns are "Acquisition Method", "Injection Source" and "Description".
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 03 and OpenLab CDS v2.6 Update 09.
Keyword: Acquisition
One-line Description:
Front sample type defined in a dual sequence CSV file is applied to all back samples upon importing
Problem:
When user imports a dual sequence CSV, the front sample type defined in the CSV file is applied to all back samples.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v.27 Update 03 and OpenLab CDS v2.6 Update 09.
Keyword: Acquisition
One-line Description:
Fraction Collection does not happen per the defined locations when sequence is run as Separate single injections
Problem:
Samples are not collected per the defined locations in the sequence on a Fraction Collector when a sequence is run as separate single injections.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 04 and OpenLab CDS v2.6 Update 09.
Keyword: Acquisition
One-line Description:
Sequence run stays in "Aborting" state forever
Problem:
When a current running sequence gets interrupted and aborted due to hardware errors, run queue will be automatically put into "Paused" state. The next pending single/sequence run will go into "Acquiring" state and then immediately stays in "Aborting" state if the hardware errors are not yet cleared at the time when user explicitly resume the paused Run Queue.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Acquisition
One-line Description:
Sporadically the method UI window stays blank for more than 30 seconds after instrument has been launched
Problem:
Sporadically the method UI window stays blank for more than 30 seconds after instrument has been launched.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Acquisition
One-line Description:
Instrument client crashes upon canceling out multiple method resolution windows
Problem:
When GC configuration has changed while the instrument client is open, a method resolution window appears for each change where the method does not match the new configuration. Users have to deal with the most recent change first then go through all the old ones. The acquisition client throws an exception and crashes.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Acquisition
One-line Description:
Communication error occurs while trying to reach Agilent.Scheduler.Agent
Problem:
A private key for the certificate that gets generated by the CertTool for the port used by REST APIs on the AIC (52088) gets deleted by an Acquisition SDK process. After that no network communication to that port is possible, breaking the functionality. The issue manifests in two user observable symptoms: - Sample Scheduler services cannot be remotely restarted through Sample Scheduler configuration. - Opening Data Analysis from CDS Acquisition client doesn’t work.
Temporary Solution:
Take the following actions to temporary fix the problem: 1. Delete the certificate on the AIC. Open certmgr.msc and delete "OpenLab Root CA" under "Trusted Root Certification Authorities/Certificates". 2. Renew certificate. Open a command prompt as administrator and change to the installation directory of the Certificate Service Tool binaries, default path is "C:\Program Files (x86)\Agilent Technologies\Certificate Service Tool\Bin" and run from there: "Agilent.OpenLab.CertService.CertTool.exe RegisterRootCert -h <servername>". 3. Reboot AIC.
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Acquisition
One-line Description:
Sequence is in aborting endlessly due to method resolution
Problem:
When submitting a run with an acquisition method created from an LC driver older than 3.5 on a 3.5 or later versions, due to method resolution, an unhandled exception was thrown, and sequence could not be aborted gracefully.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
Cannot import "Injection Source" information in a CSV/TSV file into sequence table
Problem:
"Injection Source" information cannot be imported in a CSV/TSV file into a sequence table.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03 and OpenLab CDS v2.6 Update 09.
Keyword: Acquisition
One-line Description:
Instrument shutdown on Agilent GC/HS system causes unrecoverable pause
Problem:
When a GC goes into shutdown state, data acquisition is aborted successfully, however, it also pauses the headspace and provides no way to resume. As a result, user has to manually terminate the process from window's task manager.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Acquisition
One-line Description:
Missing injections when a completed result set is loaded in Data Analysis
Problem:
Problem occurs when a file name including but not limited to data file, method, sequence and result name exceeds the maximum allowed characters including its absolute path. Extra check is implemented to avoid this situation.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 04.
Keyword: Acquisition
One-line Description:
Acquisition method UI does not refresh to display the updated configuration settings on Agilent GC instruments
Problem:
Acquisition method UI does not refresh to display the updated configuration settings on Agilent GC instruments. The issue does not happen all the time, it has been occasionally observed when the configuration change happens while the client is closed and the instrument is disconnected (a close connection is performed) from CDS.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Acquisition
One-line Description:
PE TurboMatrix HS with Agilent GC Cannot be Configured More Than Once
Problem:
The first time configuration of Agilent GC with PE TurboMatrix always succeeds but the subsequent reconfiguration of the instrument sometimes fails to open the configuration dialog -- a busy cursor is shown while doing it. The OpenLab Control Panel does not react any more and has to be closed with Windows Task Manager.
Temporary Solution:
The issue doesn't happen if the TurboMatrix HS module is configured before the Agilent GC module in the instrument configuration window in OpenLab Control Panel. Configure the PE TurboMatrix HS module first and Agilent GC last.
Fix Information:
This issue is fixed in OpenLab CDS v2.6 Update 11.
Keyword: Acquisition
One-line Description:
Bracketing mode specified in sequence table is reset back to "None" when the completed result set is loaded in Data Analysis
Problem:
Bracketing mode specified in sequence table is not properly saved after data acquisition. When the completed result set is loaded in Data Analysis, the bracketing mode is reset back to "None". This issue is only observed when a sequence has a "Create a report" line defined.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 04.
Keyword: Acquisition
One-line Description:
Sequence submitted from Sample Scheduler failed to run when fraction collection is disabled in the specified acquisition method.
Problem:
Sequence submitted from Sample Scheduler failed to run when fraction collection is disabled in the specified acquisition method.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 04.
Keyword: Acquisition
One-line Description:
Change in status of the GC not being properly broadcast to external interface.
Problem:
A third party interface checks the software status in specific periods and then initiates a single run when the system is ready. The system does not always update the interface with GC readiness state resulting in runs being missed. Restarting the software resolves the issue temporarily.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
No rx file is generated when submitting a sequence with a sample prep method which has a long name
Problem:
When submitting a sequence with a sample prep method which has a long name, no rx files are generated. As a result, data cannot be loaded in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Acquisition
One-line Description:
A certain injection line is locked from being edited in a running sequence
Problem:
When editing a running sequence, if the injection source of the current acquiring line is "no injection/instrument blank" or "external", then its adjacent pending sequence line is locked from being edited.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Acquisition
One-line Description:
Run queue stays in "Paused" state after the current acquiring sequence is aborted due to missing vials
Problem:
Run queue stays in "Paused" state after the current acquiring sequence is aborted due to missing vials. As a result, the subsequently submitted sequence stays in "Pending" state and will not start until user explicitly clicks to resume the run queue.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 04.
Keyword: Acquisition
One-line Description:
Not able to select delay sensor for Delay Volume Calibration when two or more fraction collectors are present in the instrument configuration
Problem:
User is not able to select delay sensor of interest for Delay Volume Calibration when two or more fraction collectors are present in the configured instrument. This issue is observed on all localized systems.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
"Failed to set resource properties for SQ" exception thrown when performing retrieve method from instrument by an SDK based application
Problem:
An SDK based application failed to upload method from Agilent LC/SQ MSD system. This is because the single quad MS detector does not support method upload, hence an exception is thrown.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
Sequence can't be opened for editing
Problem:
If the AIC registration uses a different OpenLab Server name (host name only or fully qualified domain name) than a client, running sequences can't be edited.
Temporary Solution:
Always use the fully qualified domain name (FDDN) for any configuration or registration task.
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
Microsoft .NET Framework unhandled exception occurs when viewing a currently running or pending sequence.
Problem:
"Object reference not set to an instance of an object" is thrown when viewing a running or pending sequence. This error is observed after upgrading LC driver to 3.6 or later versions.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Acquisition
One-line Description:
Wrong sample prep method is used for overlap injection
Problem:
Overlap injection is allowed when the same acquisition method is used for consecutive injections in the sequence. However, when different sample pre methods are defined for the consecutive injection lines, overlap injection is performed for the subsequent injection line but using the sample prep method defined in the current injection.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Acquisition
One-line Description:
Online signals window shows red start line when a run is aborted due to a missing vial on Agilent GC
Problem:
Online signals window shows red start line when a run is aborted due to a missing vial on Agilent GC.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Acquisition
One-line Description:
Submission time for runs submitted from GC plugins is not displayed in Run Queue
Problem:
Submission time is not displayed in Run Queue for runs that are submitted from GC plugin features such as Peak Evaluation.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Acquisition
One-line Description:
Bin files that contain LCMS signals are randomly missing from some injections in a completed sequence run
Problem:
When a completed LCMS result set is loaded in Data Analysis, MS signals are missing from some injections. This is because bin files are missing from those injections. Intermittently it occurs due to a timing issue in start and end of MS data collection.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 06 and OpenLab CDS v2.6 Update 11.
Keyword: Acquisition
One-line Description:
Acquisition method version is not displayed for some injections in report
Problem:
Acquisition method version is randomly missing from some injections in sequence summary report.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Acquisition
One-line Description:
Unhandled exception occurs upon launching instrument or viewing a running sequence
Problem:
Microsoft .NET unhandled exception occurrs upon launhcing instrument or viewing a running sequence. The exception is caused by imporper handling of method override parameters columns in the sequence table on Agilent LC with driver version 3.6 or higher or LCMS instruments with the following scenarios: 1. When the instrument client tries to load last opened legacy sequence file created prior to LC driver update. 2. When viewing a currently running sequence which is submitted via API using a csv file.
Temporary Solution:
As a workaround, for user A who has the issue launching LC instrument, another user B could open the sequence file, make any change to the sequence (for instance adding a description), and then save it (using the same sequence file name).
Fix Information:
The issue is fixed in OpenLab CDS v2.6 and will be fixed with a future update for OpenLab CDS v2.5.
Keyword: Acquisition
One-line Description:
Result set loaded in Data Analysis is found missing injection(s)
Problem:
When an acquired and completed result set is loaded in Data Analysis, some injection(s) are found missing, though all data are available in the designated storage. This issue may occur when user clicks "Review completed injections" at the same time closing a previously launched "Review completed injections" session. As a result, acquisition is not aware that DA is launched in "Review" mode. User then processes and save results in restricted DA after one or more injections are acquired and completed. This action will overwrite acaml and lose the completed injection(s).
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8, and OpenLab CDS v2.7 Update 08.
Keyword: Acquisition
One-line Description:
"Failed to process injection" occurs due to invalid xml characters entered in sample description
Problem:
When invalid xml characters are used in sample description in single sample analysis or sequence table, during data acquisition, an error "Failed to process injection" is thrown, rx file cannot be generated.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8, and OpenLab CDS v2.7 Update 08.
Keyword: Acquisition
One-line Description:
LC/MS SQ instrument client crashes upon printing sequence report
Problem:
LC/MS SQ instrument client closes with exception when printing a sequence report from the sequence editor table. The issue is seen with LC/MS SQ instrument driver version 3.0 released along with OpenLab CDS v2.8.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in a future update release for OpenLab CDS v2.7 and v2.8.
Keyword: Acquisition
One-line Description:
Run Queue displays wrong sequence name when an untitled sequence run as separate single injections
Problem:
When an untitled sequence by importing from a result set is submitted as separate single injections, the sequence name being displayed in the run queue is the name of the sequence imported from the result set. This is not a correct behavior. The untitled sequence is automatically saved using the result name specified in the result name field at the time of submission.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
Cannot connect to instrument successfully
Problem:
Sporadically acquisition server goes into nonresponsive mode which leads to instrument connection failure. To recover, the acquisition server process has to be terminated.
Temporary Solution:
To recover from this situation, acquisition server process needs to be terminated from windows task manager.
Fix Information:
This issue got fixed in OpenLab CDS v2.8, and OpenLab CDS v2.7 Update 08.
Keyword: Acquisition
One-line Description:
Importing a sequence CSV file failed with error.
Problem:
Starting from OpenLab CDS v2,7 Update 03, a sequence CSV/TXT file that is saved in ANSI encoding cannot be imported. This is to support importing CSV/TXT files with special characters on localized systems. Sequence CSV/TXT files must be saved in the format of UTF-8 to ensure a successful import.
Temporary Solution:
n/a
Fix Information:
Sequence CSV/TXT files must be saved in the format of UTF-8 to ensure a successful import.
Keyword: Acquisition
One-line Description:
Sequence run is stuck in aborting state
Problem:
Occasionally, after a hardware error, a subsequently submitted sequence may get stuck in an aborting state when instrument is not idle.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in Openlab CDS v2.8 Update 02, and OpenLab CDS v2.7 Update 08.
Keyword: Acquisition
One-line Description:
AIC replication issue in mixed CDS / MassHunter systems
Problem:
The replication on OpenLab CDS 2.x AICs fails if MassHunter 11 or 12 is installed in mixed mode with OpenLab CDS v2.6, or v2.7. As a result, OpenLab CDS AICs cannot run in failover mode. The issue is caused by duplicate privileges and roles in the OpenLab Shared Services database.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in OpenLab CDS v2.8, OpenLab Server v2.8, OpenLab CDS v2.7 Update 06, and OpenLab Server 2.7 Update 06.
Keyword: Acquisition
One-line Description:
LCMS SQ driver logs are no longer saved in AcqusitionServer-<ID>.log, AcquisitionClient-<ID>.log and AcquisitionAgente-<ID>.log in v2.8
Problem:
Due to a change in writing logs in v2.8, LCMS SQ driver logs are no longer saved in AcqusitionServer-<ID>.log, AcquisitionClient-<ID>.log and AcquisitionAgente-<ID>.log. They are written in AcquistionServer-driver-<ID>.log, AcquisitionClient-<ID>.log and AcquisitionAgente-<ID>.log that can be found in C:\ProgramData\Agilent\LogFiles\ for troubleshooting purpose.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in Openlab CDS v2.8 Update 02.
Keyword: Acquisition
One-line Description:
Missing activity records for injections that are aborted due to barcode mismatch
Problem:
Activity records are not properly logged in instrument activity logs for all injections that are aborted due to barcode mismatch.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in OpenLab CDS v2.8 Update 02, and OpenLab CDS v2.7 Update 08.
Keyword: Acquisition
One-line Description:
Acquisition client closes when browsing to a method folder from a sequence.
Problem:
"Error accessing storage" prompt to close acquisition client due to invalid method path when browsing to a method folder from a sequence.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in Openlab CDS v2.8 Update 02.
Keyword: Acquisition
One-line Description:
Signals from two instrument traces of VWD that are previously suppressed to collect data points in CDS v2.7 and earlier versions are saved in dx files in v2.8.
Problem:
Two instrument traces of the VWD (VWD Sample Intensity and VWD Reference Intensity) are suppressed from collecting data points in CDS v2.7 and earlier versions. Data points collected from these two traces should not be saved in dx files, however they are found to be saved in v2.8.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in Openlab CDS v2.8 Update 02.
Keyword: Acquisition
One-line Description:
Instrument connection lost if custom wellplate configured
Problem:
Under certain circumstances, instrument connection may be lost if a custom well plate is configured on G4226A and G1367x LC autosamplers.
Temporary Solution:
Verify that the custom wellplate dimensions are within the defined limits for the sampler. The issue may be resolved by adjusting these dimensions to be inside the limits.
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Acquisition
One-line Description:
Failed to connect to the instrument upon launching an Agilent LC
Problem:
Occasionally user encounters error "Failed to connect to the instrument" upon launching an Agilent LC.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in OpenLab CDS v2.8 Update 02.
Keyword: Acquisition
One-line Description:
Some Thermo instruments cannot be configured
Problem:
Running a Station IQ on a system with SII 1.3 and OpenLab CDS v2.8 shows an error about a wrong version of log4net being installed. This results in the hanging of the application upon configuration of several different Thermo instrument models.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in Thermo SII 1.4 and OpenLab CDS v2.8 Update 01.
Keyword: Acquisition
One-line Description:
WalkUp 4.3 stopping with not ready condition after every run with CDS v2.8
Problem:
Every sample that is submitted via WalkUp stops at the end of each run, the next run does not start.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in Openlab CDS v2.8 Update 02. Note - this fix ALSO requires WalkUp 4.3 Update 1 concomitantly. WalkUp 4.3 base revision will not be compatible with CDS 2.8 Update 02.
Keyword: Acquisition
One-line Description:
Reports cannot be generated at the designated folder (Windows file system) when using Sample Name or Data File Name with a trailing space as subdirectory.
Problem:
When using Sample Name or Data File Name with trailing space as subdirectory to print PDF reports in Windows file system from Data Analysis, error occurs and report cannot be generated. OpenLab CDS does not parse out the trailing space from Sample name or Data File Name, which results in report print failure.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Acquisition
One-line Description:
Failed to create sequence when using Retention Time Locking with ECM 3.x
Problem:
With ECM 3.x as storage, the CDS project root must be set up at drawer level (Location>Cabinet>Drawer), so that the folder level contains "Methods", "Report Templates", "Results", "Sequence Templates", "Sequences". If it is not set up properly, sequence creation fails when using Retention Time Locking wizard.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
The vial locations on a Hitachi instrument are not properly displayed from Sequence's Tray View UI
Problem:
The vial locations of the current configured sample tray (Sequence table editor>Tray View) are not properly displayed when using a Hitachi instrument.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in Openlab CDS v2.8 Update 02.
Keyword: Acquisition
One-line Description:
GC Signal Delay is not displayed properly
Problem:
When a GC signal is acquired with a signal delay, it should appear shifted by that delay amount when viewed in Data Analysis. However, while the signal is being acquired as expected, it is not being displayed with the shift corresponding to the delay.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Acquisition
One-line Description:
Readback from LC may contain tokens instead of values
Problem:
When referencing readbacks directly from an LC (rather than in CDS Acquisition), the displayed values may include tokens (e.g. <I>-<U>-<001>) instead of the actual values (e.g. HPLC12-JChemist-001).
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Acquisition
One-line Description:
Run queue displays wrong method for wait line under certain conditions
Problem:
If a wait line is queued up which does not have a method, and it follows another injection or wait line which did have a method defined, rather than displaying no method, the wait line will display the previously used method in the run queue.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Acquisition
One-line Description:
Online plots may be scaled incorrectly on the y-axis
Problem:
The y-axis scaling may not be updated as expected when switching between online signals and diagnostic signals in the online plot.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Acquisition
One-line Description:
GCMS Tune Reports not being saved with the result set
Problem:
Tune reports are normally saved in the result set with mass spec data. For GCMS instruments in OpenLab CDS v2.8, the reports are not being saved.
Temporary Solution:
Print or save tune reports when they are first generated until OpenLab CDS v2.8 Update 03 can be applied. Tune reports may also be temporarily found in the Windows Temp directory; they typically are in this folder for around 30 days: C:\Users\<username>\AppData\Local\Temp
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Acquisition
One-line Description:
Copy/Paste from Excel to Sequence table is truncating or missing data
Problem:
If a delimiter character "comma" is used in Sample name column in excel, anything after the delimiter in the specified sample name is trimmed when pasting the copied lines from excel to sequence table. For example, in excel with a sample name as "abc,def", when copying and pasting into sequence table, the sample name becomes "abc".
Temporary Solution:
n/a
Fix Information:
The issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Acquisition,Data Analysis
One-line Description:
Acquisition setpoints for single injection not reflecting the parameters used
Problem:
When acquiring and processing a single injection, the acquisition and processing method linked to the results belong to the master method folder from the acquisition project. If the acquisition set points from the acquisition method are changed after acquisition, the acquisition setpoints in data analysis and generated report of the injection will reflect the new method acquisition parameters and not the acquisition parameters used when the injection had been performed. This relates to the topic single injection and method linkage.
Temporary Solution:
n/a
Fix Information:
This will be fixed in a further software release.
Keyword: Admin Reports
One-line Description:
Roles and Privileges Report causes error
Problem:
With MassHunter Walkup software the Roles and Privileges Report causes error
Temporary Solution:
n/a
Fix Information:
Is fixed in OpenLab CDS 2.7
Keyword: Administration
One-line Description:
New users don't see data and projects in Content Manager
Problem:
New users don't see data and projects in Content Manager. The alfresco.log file shows errors like ------------------------------------ ERROR [org.quartz.core.JobRunShell] Job DEFAULT.ldapPeopleJobDetail threw an unhandled Exception: org.springframework.dao.DataIntegrityViolationException: No property value exists for ID 2393922 at org.alfresco.repo.domain.propval.AbstractPropertyValueDAOImpl.getPropertyById(AbstractPropertyValueDAOImpl.java:848) ------------------------------------ This error prevents successful synchronization between Content Management and Shared services database, so new users do not get the permissions assigned that were set in the OpenLab Control Panel. The cause of this problem are competing synchronization processes were one process fails as the other process already did start deletion of ID's.
Temporary Solution:
To resume synchronization between Content Management and Shared Services database again, use the following commands to delete the orphaned ID's: delete from alf_prop_unique_ctx where prop1_id = 2393922 delete from alf_prop_root where id = 2393922 The commands have to be adapted for the ID listed in the alfresco.log file. These commands might have to be repeated several times for other ID's until synchronization works again.
Fix Information:
Fixed in 2.4
Keyword: Administration
One-line Description:
Not possible to delete project related files form the Content Management user interface.
Problem:
Delete processing method, delete sequence templates or delete reports templates isn’t working via DA. Even when all available privileges except “everything” are given to the user. Directly from CM it’s also possible. With the privilege "Manage Security" you can delete files/folders in Content Management - as long as the files/folders are not within a project! When in a project, only projects related privileges are applied, therefore it will not be possible to delete files in a project if you have the Manage Security privilege Inside a project, there is also a role called everything. If you grant this role to a user within that project, he will be able to do everything, including deleting files.
Temporary Solution:
n/a
Fix Information:
Manuals and online help have been improved to point this behavior out more clearly in the version 2.5
Keyword: Administration
One-line Description:
No specific privilege is required to access the CM Admin console
Problem:
The Admin Console of the Content Management Web page can be opened by any user with the privilege "Project - Access Content using Web client".
Temporary Solution:
The Admin Console is read only and no information that compromises security is available on the Admin page
Fix Information:
n/a
Keyword: Administration
One-line Description:
Java JMX RMI vulnerability
Problem:
Java JMX RMI is accessible with common credentials (unauthenticated check). This could be a security issue on an OpenLab CDS Workstation Plus, an OpenLab Server or an OpenLab ECM XT Server.
Temporary Solution:
On OpenLab Server or ECM XT v2.5, add the following line to the alfresco-global.properties file to resolve the issue. messaging.broker.url=vm://localhost?broker.persistent=false&broker.useJmx=false
Fix Information:
This issue is resolved in version OpenLab Server v2.6 and OpenLab ECM XT v2.6
Keyword: Administration
One-line Description:
Restore fail when the new server is on a different subnet
Problem:
When you have a 2-server system with postgres, restore fail with the Agilent OpenLab Restore Utility when the new server is on a different subnet or you try to restore on a All-in-One server. The restore will fail at the end while running the Server Configuration Utility.
Temporary Solution:
Workaround1: When the new 2-server environment is in a different subnet Edit the pg_hba.conf on the new db server to reflect the correct subnet Run the Server Configuration Utility (from the start program menu)Run the restore utility and select to run the Verification Only Workaround2: When you restore on an All-in-one server Rerun the Restore utility and use the hostname of the new server (don't use localhost)
Fix Information:
n/a
Keyword: Administration
One-line Description:
A new domain user can't create projects
Problem:
Although a user has the required privileges assigned via a domain group, it is not possible to create a new project.
Temporary Solution:
The user will be able to create a new project after the server is restarted. In case of a cluster system, the complete cluster needs to be restarted.
Fix Information:
This is fixed in OpenLab CDS 2.5
Keyword: Administration
One-line Description:
Archive fails if a file with the same name has already been archived
Problem:
If a user attempts to archive a file that has the same name as a file that already exists in the archive location, the archive will fail.
Temporary Solution:
Dearchive the original file before uploading the new file with the same name. Then upload the new file as a new version of the original file. All versions of that file can then be archived without error.
Fix Information:
n/a
Keyword: Administration
One-line Description:
Backups can fail if the available C disk storage space is too small
Problem:
During the backup process, the database is cached on the C drive before it is moved to the specified backup destination. If the C drive is too small to store the database cache, then the backup will fail.
Temporary Solution:
n/a
Fix Information:
This is resolved in the 2.6 Backup & Restore update.
Keyword: Administration
One-line Description:
Backup aborts due to timeout error
Problem:
In case of a slow connection between the OpenLab or ECM XT Server and an external Microsoft SQL Server, the backup execution might run into a timeout error. This is due to a built-in timeout of 30 sec. for a SQL command execution. The issue has been observed sporadically for servers with version 2.6.
Temporary Solution:
n/a
Fix Information:
The issue will be fixed by a separate release of the backup tool, which is planned for Nov. 2021.
Keyword: Administration
One-line Description:
Installation stalls at Agilent Distributed Transaction coordinator install step
Problem:
The installation stops at the Agilent Distributed Transaction coordinator install step. The distributed-transaction-coordinator-configurator.log shows: [ERR] MigrateSchema: Configuration step has failed. System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. The CertService.log shows [ERR] CustomServiceBase - OnStart error System.InvalidOperationException: Requested domain name 'CSM' does not match the service's domain 'CSM' at Agilent.OpenLab.CertService.CertServiceCore.Certificates.CertFactoryService.GetServerCert(String hostName, String domainName, IEnumerable`1 dnsSuffixes) The problem is caused by a domain name that does not conform to the RFCs/standard. In this case it was missing the top level domain. Two letter domain names that are not routed on the internet cause the same problem.
Temporary Solution:
Change the domain name to a domain name that matches the RFCs/standards for non routable domains.
Fix Information:
Will not be fixed
Keyword: Administration
One-line Description:
Backup Utility fails if IP address is used for DB server connection
Problem:
The backup Utility fails if the IP address of the database server is used for the DB server connection in the server configuration.
Temporary Solution:
Do not use the database server IP address for configuration. Always use the host name.
Fix Information:
OpenLab Server/ECM XT uses standard TCP/IP protocols to communicate between the server and client computers. For optimum performance, the network must meet the design criteria for available bandwidth, IP address assignment, name resolution, and appropriate isolation of the lab subnet from the corporate network. The usage of the Hostname for the Database server is required in case of a separate DB-Server is required.
Keyword: Administration
One-line Description:
If one archive job fails, the others should continue
Problem:
If multiple folders are queued to be archived, the failure of one archive job will prevent the remaining folders in the queue from being successfully archived. Any new folder selected to be archived will also fail if there is currently a failed archive job in the queue.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.5 Update 11 and OpenLab ECM XT 2.5 Update 06, as well as OpenLab CDS 2.7 and OpenLab ECM XT 2.7
Keyword: Administration
One-line Description:
Archive jobs get stuck, requiring a cleanup
Problem:
If an archive job fails, it will remain in the archive queue until it is manually cleaned up.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.5 Update 11 and OpenLab ECM XT 2.5 Update 06, as well as OpenLab CDS 2.7 and OpenLab ECM XT 2.7
Keyword: Administration
One-line Description:
Archive job in a sub-folder should be removed when manually archiving a parent
Problem:
If a successfully archived folder contains a sub-folder with an automatic archive task assigned to it, the sub-folder's automatic archive task will remain listed in the Automatic Archive Tasks page of the Content Browser Admin Console.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.5 Update 11 and OpenLab ECM XT 2.5 Update 06, as well as OpenLab CDS 2.7 and OpenLab ECM XT 2.7
Keyword: Administration
One-line Description:
Data files with names including semicolons (;) cannot be uploaded to Content Management
Problem:
In OpenLab CDS 2.6, semicolons (;) should not be used when naming a data file. Data files with names including semicolons will trigger a system error in the File Upload Queue and will not be automatically uploaded to Content Management
Temporary Solution:
n/a
Fix Information:
This defect is fixed in OpenLab ECM XT 2.6 Update 06 / OpenLab CDS 2.6 Update 09 and is also fixed in the 2.7 release of OpenLab ECM XT, OpenLab Server, and OpenLab CDS.
Keyword: Administration
One-line Description:
OpenLab ECM XT not affected by security issues in log4j-1.2.17
Problem:
OpenLAB ECM XT is not using non-default logging configurations that include the JMS Appender. So it is not vulnerable to the known exploits. See https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-cve-2021-44228
Temporary Solution:
n/a
Fix Information:
No fix planned
Keyword: Administration
One-line Description:
Customer IT scan identified vulnerability CVE-2021-4104
Problem:
After a regular vulnerability scan the OpenLab Server / ECM-XT system is classified as Vulnerable to CVE-2021-4104 NVD - CVE-2021-4104 (nist.gov)
Temporary Solution:
N/A
Fix Information:
According to https://hub.alfresco.com/t5/alfresco-content-services-forum/log4j-vulnerability-impact-on-alfresco-community-edition/m-p/311033#M26495 OpenLab Server / ECM-XT is not vulnerable to CVE-2021-4104 NVD - CVE-2021-4104 (nist.gov).
Keyword: Administration
One-line Description:
Script to update system passwords seems to update the wrong registry elements
Problem:
The dr-db-set-system-passwords.ps1 script that is located in the following default location is not functional: C:\Program Files\Agilent Technologies\OpenLab DataRepository\Data Repository\Data Repository\Service\Scripts\PostgreSQL\Mgmt\dr-db-set-system-passwords.ps1
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS 2.7 Update 02 and OpenLab Server 2.7 Update 02.
Keyword: Administration
One-line Description:
Version mismatch in SVT for Data Collection Agent and Service
Problem:
On running the SVT tool, the Software Verification Report returns different versions for: OpenLab Data Collection Agent and OpenLab Data Collection Service The Base Revision Number on the header of the SVT Report is reported as 1.5.0 while on the detailed table for the dlls and under the Programs and Features of the Windows Control Panel Panel version 1.6.0.45 is reported.
Temporary Solution:
N/A
Fix Information:
The correct base version is: 1.6.0. Version mismatch was corrected in later CDS versions.
Keyword: Administration
One-line Description:
Analytics.json moved to OpenLab Platform and no longer listed in Diagnostics save files
Problem:
The analytics.json file contains information on a system's configuration that is helpful in troubleshooting. The analytics.json file can no longer be saved from the Control Panel's Administration>Diagnostics page.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS 2.7 Update 02 and OpenLab Server 2.7 Update 02.
Keyword: Administration
One-line Description:
Cannot resotre FB database
Problem:
When restoring a backup of the OpenLab Shared Services database using the OpenLab Shared Services Maintenance tool, the restore can fail with the following error: "Database cannot be accessed right now."
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab Server 2.8, OpenLab CDS v2.8, OpenLab Server 2.7 Update 04 and OpenLab CDS 2.7 Update 04.
Keyword: Administration
One-line Description:
Rest API crashes with domain users in CP but removed from domain
Problem:
On OpenLab CDS 2.7 client/server systems using OpenLab Sample Scheduler, the Rest API used by Sample Scheduler to query for users can crash if the OpenLab authentication provider is set as the domain and a user that was added to OpenLab has since been removed from the domain.
Temporary Solution:
Remove all users from CDS which are no more available in the domain when the Rest API consuming application crashes or stops.
Fix Information:
This issue has been resolved in OpenLab Server 2.8, OpenLab CDS v2.8, OpenLab Server 2.7 Update 04 and OpenLab CDS 2.7 Update 04.
Keyword: Administration
One-line Description:
OpenLab Software Installation Verification Test fails with ECM backend
Problem:
When running the "OpenLab Software Installation Verification Test" on a shared services server with ECM backend, the test fails. All SVT tests pass, with the exception of the IQTExample test.
Temporary Solution:
The installation of the "ECM Classic Client" updates the list of available products for the SVT used by Test Services incorrectly. Using the Software Verification Tool from the start menu, to correct full list is shown and it can be tested here that all tests are passed.
Fix Information:
Fixed in 2.8
Keyword: Administration
One-line Description:
The AGTOL.log file is missing from 2.7 systems
Problem:
The AGTOL.log file is usually generated after a license file is added to an OpenLab system but fails to generate on 2.7 systems. Its location is dependent on the Installation Folder specified when installing the system. On systems using the default Installation Folder, it can be found at the following path: C:\Program Files (x86)\Agilent Technologies\OpenLab Services\Licensing\Flexera\logs.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab Server 2.8, OpenLab CDS v2.8, OpenLab CDS 2.7 Update 06 and OpenLab Server 2.7 Update 06.
Keyword: Administration
One-line Description:
Supporting OpenLab v2.8 in multi-domain environments where Clients/AICs are members of a different domain than the OpenLab Server/ECM XT server
Problem:
By default, the Agilent OpenLab Certificate Service provides certificates with a list of Subject Alternative Names (SAN) containing entries strictly belonging to the domain in which the Agilent OpenLab Certificate Service resides. This prohibits the generation of certificates for foreign domains and provides higher level of trust. When attempting to install a new client or AIC in a different domain, the installation will fail and the following message will be found in the %ProgramData%\Agilent\LogFiles\OpenLab Certificate Service\CertServiceTool.log: Processing finished with error #202: Malformed response from service. Possibly the requester's domain does not match the server domain.
Temporary Solution:
n/a
Fix Information:
To support installations of OpenLab v2.8 client/server systems across trusted domains, the Agilent OpenLab Certificate Service can be configured to operate in a less restrictive mode. While this working mode is activated, no domain names are checked and the certificates created can contain different domains in the SAN list. If required, this working mode should be activated right after installing and configuring an OpenLab Server/ECM XT server, OpenLab Shared Services server, or any server node that hosts the Agilent OpenLab Certificate Service. On the specified server, create a new registry key as detailed below. • Registry Path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Agilent\OpenLab Platform\Certificate Service • DataItemName: WorkingMode • DataType: REG_SZ • DataValue: 1 The registry key can also be created by running a .reg file that contains the below lines (between the #'s): ################################################################# Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Agilent\OpenLab Platform\Certificate Service] "WorkingMode" = "1" ################################################################# The Agilent OpenLab Certificate Service must be restarted after adding the registry key. This mode can be de-activated by changing the value of the mentioned registry key to 0 and restarting the Agilent OpenLab Certificate Service If the mentioned changes should be applied to an already installed client/server system (e.g., after installation of clients or AICs in a different domain, or moving an AIC to a different domain), the related server certificates must be re-created. To accomplish this, on each server hosting the Agilent OpenLab Certificate Service: • Rename the following folder: %ProgramData%\Agilent\OpenLab Certificate Service\v1\hosts • Restart the Agilent OpenLab Certificate Service After following those steps on the server(s), reboot each client and AIC outside the server's domain to request a new certificate. Please note that this procedure will only work on OpenLab v2.8 and does not apply to previous versions.
Keyword: Administration,User Interface
One-line Description:
Activity Log in OLCP does not record the Application name when login from the Web UI
Problem:
The Activity Log in the OpenLab Control Panel does not record the Application Name (e.g. Content Management) when a user connect to the Content Management web interface, only the action of login in and the user name is recorded.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab Server v2.5 and Openlab ECM XT v2.5
Keyword: Audit Trail
One-line Description:
Audit Trail shows "Unknown" user and "Manual Control" category when running method with "Acquire" option unchecked
Problem:
When you run a VWD method that has the Signal A "Acquire" check box not selected, the Audit Trail Report documents the event with "Unknown" user, "Manual Control" category, "[VWD] Changed Signal Wavelength from 250 nm to 265 nm" in the description, even though 265 nm is not specified in the method. From the VWD Instrument Status, the lamp wavelength never changes to 265 nm.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in a future revision of OpenLAB CDS.
Keyword: Audit Trail
One-line Description:
Audit Trail shows "Unknown" user if you make changes to current running method
Problem:
If the user makes changes to the current running method either from instrument front panel or Instrument Status Dashboard, the Audit Trail shows "Unknown" user name instead of the actual login user name.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Audit Trail
One-line Description:
Audit trail shown “Unknown” in the Manual Control category for method changes in running sequence
Problem:
When acquiring a sequence, if the method settings are changed (i.e. accessing the sequence table and change “Volume”), the new settings are reflected on the system. However, the Audit Trail records that the changes are made by "Unknown” in the Manual Control category rather than the current logged in user.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 by the "Take Control" feature that allows only one Client to take the control of changing instrument parameters and the name of the user who has taken control is logged in Audit Trail.
Keyword: Audit Trail
One-line Description:
Review button in Audit Trail is disabled for entry "Upgraded method from previous version"
Problem:
After upgrading from OpenLab CDS v2.1 to OpenLab CDS v2.3, the Review button in the Audit Trail is grayed out for the "Upgraded method from previous version" entry.
Temporary Solution:
To get the Review button enabled, the user needs to close Audit Trail window and then save the method as new name.
Fix Information:
This issue is fixed in the OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 04.
Keyword: Audit Trail
One-line Description:
Audit trail table in sequence report printed from instrument client is spanned in two rows for each entry
Problem:
Audit trail table in sequence report printed from instrument client is spanned in two rows for each entry. The bold text of the first two Title lines describes the following row contents. First line: User name - Date - Category - Description Second line: Reviewed - Version - Host name - Reason
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Audit Trail
One-line Description:
Reprocessing injection triggers log with different wording in audit trail and activity log
Problem:
Accomplished reprocessing in Data Analysis of injections is logged in the injection and activity logs as "Injection successfully reprocessed", while it stands as "Injection successfully processed" in the audit trail entry of these injections. As one refers to the initial processing of the injection, and the second to repeating the processing process. The difference of the two wordings can affect customers while reviewing the integrity of the results documentation. For this context, this known problem report entry can be used to document the deviance observed in results activity logs (injection or system wise) and the audit trail entries.
Temporary Solution:
n/a
Fix Information:
The entries stated in activity logs as well as audit trails will be revised and fixed in a future software revision.
Keyword: Audit Trail
One-line Description:
Reprocessing injection triggers log with different wording in audit trail and activity log
Problem:
Accomplished reprocessing in Data Analysis of injections is logged in the injection and activity logs as "Injection successfully reprocessed", while it stands as "Injection successfully processed" in the audit trail entry of these injections. As one refers to the initial processing of the injection, and the second to repeating the processing process. The difference of the two wordings can affect customers while reviewing the integrity of the results documentation. For this context, this known problem report entry can be used to document the deviance observed in results activity logs (injection or system wise) and the audit trail entries.
Temporary Solution:
n/a
Fix Information:
The entries stated in activity logs as well as audit trails will be revised and fixed in OpenLab CDS v2.5.
Keyword: Audit Trail
One-line Description:
Injection time for imported ChemStation data is rounded down to the minute
Problem:
Injection time for imported ChemStation data is rounded down to the minute so seconds are always shown as :00 in the injection list. The date and time otherwise is accurate. This is limited data acquired with a G1946A or G1946B LC/MSD.
Temporary Solution:
Make note that seconds are always shown as :00 for imported ChemStation data and keep a copy of this software status bulletin as required
Fix Information:
This issue will be considered for a fix in a future software release.
Keyword: Audit Trail
One-line Description:
Sequence/method loses its audit trail if it is saved with same name
Problem:
Two sequences/methods (A and B) exist, each one with its own Audit Trail (ATA1 and ATB1, respectively). If sequence/method A is saved as sequence/method B, then the audit trail of the original sequence/method (ATA1) is lost. This issue also can occur with sequence templates and sample preparation methods.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, CDS v2.4 Update 07, and CDS v2.3 Update 07.
Keyword: Audit Trail
One-line Description:
User who last modified and saved the method appears in method audit trail upon resolving method resolution
Problem:
When a method was last saved by user A was opened by user B on an instrument where a method resolution was involved, the method audit trail records User A for that change.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue. This issue has been fixed in OpenLab CDS v2.3 Update 11, OpenLab CDS v2.4 Update 11, and OpenLab CDS v2.5.
Keyword: Audit Trail
One-line Description:
E-Signature description not automatically updated for new created user
Problem:
In case the descriptions of the different e-signature levels got changed and a new user gets created, the old descriptions might appear for this user.
Temporary Solution:
After creating a new user open the Edit signatures settings in the OpenLab Control Panel (Projects -> Edit Signature Settings). Check in the levels and users/groups tab for the updated description. Close the window with ok.
Fix Information:
n/a
Keyword: Audit Trail
One-line Description:
Processing method audit trail shows incorrect values after changing values in signals smoothing tab
Problem:
Changing the Number of Points in Processing method > General > Signals > Smoothing to a value higher than the accepted range will report a wrong value in the processing method audit trail after saving the method.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6, OpenLab CDS v2.5 Update 5, and OpenLab CDS v2.4 Update 11.
Keyword: Audit Trail
One-line Description:
No record in Audit Trail when disabled calibration points are re-enabled after reprocessing
Problem:
When a result set that has disabled calibration points is reprocessed, the disabled points are enabled again, but there is no record in the Audit Trail that the points have been reactivated.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 03.
Keyword: Audit Trail
One-line Description:
The original user who created the sequence is listed in the sequence audit trail as the user who imported the sequence from a result set
Problem:
When using the function "Import Sequence from Result set" to create a new sequence, the user that originally created the sequence is listed as user in the first entry of the audit trail. Subsequent entries are correctly listing the logged on user.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Audit Trail
One-line Description:
Processing method audit trail not displayed from processing method settings after loading new data
Problem:
When opening the audit trail in the properties tab of a processing method it might happen that the audit trail will not be visible. This only occurs if the scaling of the display is set to 125%.
Temporary Solution:
Either open the method audit trail directly from the Audit/E-Sign tab on the ribbon bar or change the display scaling to 100%.
Fix Information:
This issue is fixed in OpenLab CDS v2.6
Keyword: Audit Trail
One-line Description:
'Save Method As' generates incorrect method audit trail entry for UV reference spectrum
Problem:
If a UV reference spectra gets added and immediately removed on a saved 3D UV Quantitative processing method, and afterwards the method is being "saved as" another method, the entry for removing the UV reference spectrum is shown in Audit Trail.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7
Keyword: Audit Trail
One-line Description:
Result set name not recorded in activity log after import
Problem:
After importing an .olax file, the activity log records only the .olax file name and not the imported result set name.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 08
Keyword: Audit Trail
One-line Description:
Renaming compound creates calibration curve removal entry in audit trail
Problem:
Renaming a calibrated compound creates an Audit Trail entry "Removed method calibration curve for compound '<old compound name> - <signal>'"
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Audit Trail
One-line Description:
Some of the Injection audit trail entries may not be recorded due to a failure downloading of a result set
Problem:
When loading a result (single sample or result set) and the corresponding rx file could not be downloaded (e.g. network issues), then on saving this result creates a new rx file. This new rx file is missing the audit trail entries from the previous one, which could not be downloaded. Therefore, the audit trail was lost, and the injection number will be displayed as "0".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 05, OpenLab CDS v2.5 Update 09 and OpenLab CDS v2.4 Update 11.
Keyword: Audit Trail
One-line Description:
User ID is used to record injection audit trail entries under certain circumstancess
Problem:
If a user has both Full Name and User ID, Full Name will be used for audit trail record entries. However, under certain circumstances, for example, during a sequence run, when the instrument client is closed, for the subsequent injections, entries of ignored method changes due to dynamic configuration changes during a run are recorded under User ID.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in a future release.
Keyword: Audit Trail
One-line Description:
Processing method audit trail entry for existing “Relative from” option is shown incorrect when changed from “On blank” to” On Current”.
Problem:
Processing method audit trail entry for existing “Relative from” option is shown incorrect when it gets changed from “On blank” to "On Current" or vice-versa.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 07, and OpenLab CDS 2.5 Update 11.
Keyword: Audit Trail
One-line Description:
Modifying properties of MS library report snippet will not get recorded in the report template audit trail.
Problem:
Modifying properties of MS library report snippet will not get recorded in the report template audit trail.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Audit Trail
One-line Description:
User is not prompted to enter 'Reason for Changes' when linking method
Problem:
When the Method Audit Trail Settings of a project are configured to 'Automatically enable audit trail' and 'Prompt for reason when saving methods', users are prompted for a reason when saving a result set method as a new master method, but not when they are linking a master method to data files in a result set (saving a master method as a result set method). After linking, the reason field is empty for the related entries in the method audit trail.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 03 and OpenLab CDS v2.6 Update 09.
Keyword: Audit Trail
One-line Description:
Value of RRT ratio, or factor of reference compound are not captured in the audit trail
Problem:
If RRT or time reference compounds are defined in the processing method, their values for RRT and factor are not captured in the method audit trail.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Audit Trail,Workflow
One-line Description:
Sequence/sample reports and Injection Audit Trail only show user who submitted sequence, not user who modified running sequence
Problem:
The sequence/injection reports and Injection Audit Trail show the user who submitted the sequence, not the actual user who modified (e.g., deleted or added injections, etc.) the running sequence.
Temporary Solution:
To see the actual user who modified (deleted or added injections, etc.) the sequence, you need to refer to the Sequence Audit Trail.
Fix Information:
n/a
Keyword: Calibration
One-line Description:
Performing MS Quantitation using OpenLAB CDS ChemStation data
Problem:
1) User loads a data set acquired in OpenLAB CDS 2.0 and creates a quantitation method (based on TICs or EICs). 2) A user imports a ChemStation file and links to the same recently created OpenLAB CDS 2.0 method. 3) On linking a reprocess is performed and the following behavior occurs: a. If EIC compounds were created then those EICs will be extracted and shown to the user in the ChemStation file also. b. However no peaks will be identified in the EIC or TIC due to signal naming (in ChemStation MSD1 versus Excalibur MS1).
Temporary Solution:
N/A
Fix Information:
This issue will be fixed in future version.
Keyword: Calibration
One-line Description:
Calibration curve update timestamp for missing compound
Problem:
In reporting, the calibration curve update time stamp of the missing compound in the analysis will appear with like "1/1/0001 1:00:00 AM". This is due to the fact the calibration curve cannot be updated for this missing compound.
Temporary Solution:
Use a filter in the calibration curve report item. Use the following expression in the filter: Expression: Compound_Type Operation: <> Value: 5
Fix Information:
This issue is fixed in OpenLAB CDS 2.1
Keyword: Calibration
One-line Description:
Data field CalibCurve_CorrCoefficient is not properly labeld
Problem:
Data reprocessed in OpenLAB CDS ChemStation and OpenLAB CDS EZChrom will return the coefficient of determination "r^2" for the field "CalibCurve_CorrCoefficient", rather than the correlation coefficient "r".
Temporary Solution:
Change the the data field label of your templates to "Corr. Coeff. r^2" or "Correlation r^2"
Fix Information:
The default labeling will be changed in a future release
Keyword: Calibration
One-line Description:
Log / Log calibration curve model not drawn correctly in the report printout
Problem:
Calibration curve of type Log / Log is not drawn correctly. Negative values of the log(amount) response will not be drawn correctly.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in CDS v2.2
Keyword: Calibration
One-line Description:
Help and Learning needs updated statement regarding all calibration options or levels are supported with timed groups
Problem:
In OpenLab CDS v2.4 in Help and Learning, the following statement is true for linear curve, but not for quadratic curve with a negative power. Further clarification is needed to supplement this statement. "A timed group can be quantified according to its own calibration curve. All calibration options or levels are supported."
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5. In OpenLab Help and Learning, under Data Analysis > Calculations and Background References > Quantitation > Quantitation of groups > Definition of a timed group, the following paragraphs have been added: Caution: As Timed Groups use the calibration parameters of the whole group, caution should be taken when using with non-linear and/or calibration curves with a large offset. Usage of a Timed Group with non-linear calibration curves is not recommended as it will calculate potentially imprecise results due to the non-commutative nature of the calculations. If a group calibration curve has a significant off-set (i.e. a large intercept (b) value), the offset gets equally distributed across all peaks found within the time group windows. The equal distribution may not describe each compound adequately.
Keyword: Configuration
One-line Description:
Instrument opened with a channel conflict is in a quasi-Not Connected state
Problem:
When a specific SS420x channel has been configured to more than 1 available instrument an expected conflict occurs however the OpenLAB CDS instrument connection is not closed automatically and stays open. The user must close the instrument connection manually in order to resolve the conflict.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Configuration
One-line Description:
COM port information for clients does not match AIC COM port information
Problem:
When configuring the SS420x Interface in a distributed (AIC) system, you must configure an available COM port only on the AIC. Configuring a COM port shown as available on a client will not work.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Configuration
One-line Description:
Canceling out of instrument auto configure still deletes all previous configurations
Problem:
If you've configured your instrument and accidentally press the "autoconfigure" button again and try to cancel - it deletes your instrument configuration and you have to perform the configurations all over again.
Temporary Solution:
n/a
Fix Information:
It is fixed in OpenLAB CDS 2.1
Keyword: Configuration
One-line Description:
Using OpenLAB CDS Waters Acquity driver the PDA ( 3D option) is pre-set as default values as well for 2D Detectors
Problem:
Using OpenLAB CDS Waters Acquity driver the PDA (3D option) is pre-set as default values as well for 2D Detectors. In case a 2D detector is used the system will ask the user to enter a 3D license.
Temporary Solution:
Deselect the checkmark from the PDA/3D option in the configuration dialog box of the OpenLAB CDS.
Fix Information:
n/a
Keyword: Configuration
One-line Description:
Unconfigured Sample Scheduler Agent causes Windows logs on CDS 2.3 AIC's
Problem:
On CDS 2.3 AIC's a Sample Scheduler Agent gets installed by the CDS installer as default. This Agent is not configured to a Sample Scheduler installation. As long the Sample Scheduler Service is running without being configured it will cause frequently windows log entries of termination and restart.
Temporary Solution:
Disable the Sample Scheduler Agent Service when it is not needed
Fix Information:
This problem is fixed in OpenLab CDS 2.4 and in OpenLab CDS 2.3 Update 04
Keyword: Configuration
One-line Description:
Authentication issue in a multi-domain environment
Problem:
In an Active Directory multiple domain setup, users can be defined in one domain and assigned to a group in a different domain. While the import itself of such a user group into OpenLab Shared Services is possible, a subsequent authentication only works if the users are in the same domain as the imported group. This is also true for universal groups.
Temporary Solution:
User groups that are in the same domain as the users do not exhibit the issue.
Fix Information:
The issue is planned to be fixed in a future OpenLab CDS release.
Keyword: Configuration
One-line Description:
Logon to OLCP is not possible
Problem:
In case of a OpenLab Server in the cloud (A SaaS implementation) in some instances the logon to the OLCP is not possible from an on-premise client. The olcp_main.log on the client shows Exception: System.Net.Sockets.SocketException (No such host is known). This problem can reoccur after the Server configuration utility is run, as the changes implemented following the "OpenLab CDS / Configuration in the Cloud" (Document No: D0010651 Rev. A April, 2021) manual will be reverted when the Server configuration utility is run.
Temporary Solution:
A solution for this is available in the "OpenLab CDS / Configuration in the Cloud" (Document No: D0010651 Rev. A April, 2021) manual. Follow the procedure from the OpenLabCloudConfiguration.pdf manual in the section "Update OpenLab Shared Services Configuration"
Fix Information:
A solution for this is available in the "OpenLab CDS / Configuration in the Cloud" (Document No: D0010651 Rev. A April, 2021) manual. Follow the procedure from the OpenLabCloudConfiguration.pdf manual in the section "Update OpenLab Shared Services Configuration"
Keyword: Configuration
One-line Description:
Instrument can't be configure with TLS 1.0 disabled
Problem:
If TLS 1.0 is disabled the error message "Unable to configure instrument, the connection timed out" is displayed when the instrument configuration is started.
Temporary Solution:
Enable TLS 1.0 on the AIC and the client for instrument configuration.
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Configuration
One-line Description:
Slow login performance when server and user domain don't match forest name
Problem:
The login performance is slow and the server.log file on the OpenLab Server shows the entry "Global catalog for the domain <AAA.BBB> was not found". This is caused when the user and server domain name don't match the forest name, for example. Doman name: AAA.net Forest Name: BBB.net In cases like this, CDS and ECM XT do not use the Global Catalog, hence login slowness can be observed.
Temporary Solution:
n/a
Fix Information:
This is fixed in version 2.7Update02
Keyword: Configuration
One-line Description:
Multiple domain support is lost after upgrade
Problem:
Multiple domain support is lost after upgrading from OpenLab CDS v2.5 or v2.6 to v2.7.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 01.
Keyword: Configuration
One-line Description:
CDS 2.7 won't add user in a multi-forest domain
Problem:
Failed adding and authenticating users from a multi-domain forest.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and CDS 2.7 Update 01
Keyword: Configuration
One-line Description:
When starting "OpenLab Configuration" or "Shared Services Maintenance" an error is shown
Problem:
The error is "A referral was returned from the server" and is caused when the GPO "Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Only elevate executables that are signed and validated" is enabled.
Temporary Solution:
The "OpenLab Configuration" can be started from the OpenLab CDS 2 setup program, in the Installation section with the "Configure Client/Server" option.
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Configuration
One-line Description:
Unable to start Agilent OpenLab Data Collection Service after installing OpenLab CDS 2.6 update 09
Problem:
Unable to start Agilent OpenLab Data Collection Service after installing OpenLab CDS 2.6 update 09
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.6 Update 10.
Keyword: Configuration
One-line Description:
OpenLab CDS is not starting due to invalid host name
Problem:
A host name ending or beginning with a "-" will cause the OpenLab certificate service to not provide valid certificates for the host. This does cause problems in the communication between servers, AICs, clients as well as within Workstations. As a result, Acquisition, Data Analysis, or the OpenLab Control Panel do not start.
Temporary Solution:
Do not use PC and server host names ending or beginning with a "-".
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Configuration
One-line Description:
On Server Installed update page shows 'Agilent OpenLab CDS 2.6 Update 11'
Problem:
On Server Installed update page shows 'Agilent OpenLab CDS 2.6 Update 11'.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 Update 13.
Keyword: Configuration
One-line Description:
Vulnerabilities CVE-2018-1285 and CVE-2023-34152 detected
Problem:
After a vulnerability scan, vulnerabilities CVE-2018-1285 and CVE-2023-34152 are detected on the OpenLab CDS 2.6 system.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 02.
Keyword: Configuration
One-line Description:
Apache HTTP Server vulnerabilities
Problem:
OpenLab CDS and ECM XT 2.6 and 2.7 have the Apache HTTP Server (also referred to as Reverse Proxy) integrated. Depending on the exact Apache version installed, 3rd party security software reports a list of security vulnerabilities, see https://httpd.apache.org/security/vulnerabilities_24.html for details.
Temporary Solution:
n/a
Fix Information:
OpenLab Reverse Proxy Update 04 contains Apache Reverse Proxy 2.4.59 and supersedes OpenLab Reverse Proxy Update 03. OpenLab Reverse Proxy Update 03 contains Apache Reverse Proxy 2.4.58 and fixes all Apache vulnerabilities up to release 2.4.57. The mentioned updates are available on SubscribeNet and can be applied to CDS and ECM XT 2.6 and 2.7. This issue got resolved in OpenLab CDS v2.8.
Keyword: Customization
One-line Description:
PDF extraction failing
Problem:
PDF extraction can be used to extract metadata from a CDS printout for example to import injection results into another system, such as a LIMS or OpenLab ECM XT. If newer extraction technology used for example in OpenLab ECM XT can extract the PDF metadata to import the results in the data backend, other systems may not be able to extract the information. Note, extraction is possible only using standard or PDF/A-1 formats. Secured PDF information will not be extracted, due to privilege restriction. Format selection is available in the reporting editor, under report properties.
Temporary Solution:
Adjust the PDF extraction method.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Custom Calculation results containing a list of values and empty values, will lead to empty value in case of summary calculation performed with another Custom Calculation
Problem:
This known issue is related to custom calculation results used in another custom calculation. When the first calculation is returning a list of values and empty fields, this calculation will not be usable in another custom calculation. Example: 2 Custom Calculations : CC1 returns in the peak or group scope the expression : Compound_Amount CC2 returns in the injection scope the expression : Sum("CC1", CurrentInjection.AllPeaks) The CC2 Custom Calculation result should return the sum of all peaks compound amount for this injection. The CC1 is used in the expression of CC2, and returns the compound amount for every peaks. In an injection containing 2 identified and calibrated compounds, and not identified peaks. The CC1 can have the following list of values in the injection for example: Peak 1 (not identified), value of CC1 = "" (this means, the value will be empty, as no amount can be calculated for not calibrated peaks) Peak 2 (identified), value of CC1 = 2.3 Peak 3 (identified), value of CC1 = 1.2 For this injection, if custom calculation CC2 is computed, the value will be: CC2 ="" (this means the result will be empty) This is a known behavior. When a custom calculation is computing a calculation on a list which contains one or several empty value(s), the calculation will not be computed.
Temporary Solution:
The generic solution is to compute the calculation on a more specific scope where the calculation should be applied. In this example, the solution is to apply the CC2 calculation on all identified peaks from the injection, and not on all peaks. The expression of CC2 will then be: Sum("CC1", CurrentInjection.allIdentifiedPeaks)
Fix Information:
This will be fixed in a future release
Keyword: Data Analysis
One-line Description:
Incorrect EIC exctraction
Problem:
Input: Injection with a) Polarity = Pos & Neg b) FV = 125 (Pos) and 150(Neg) Action: User performs single mass EIC extraction with Polarity = All, FV = All. Outcome: 4 EIC are extracted: 1. Pos & 125V - Valid 2. Pos & 150V - Invalid 3. Neg & 125V - Invalid 4. Neg & 150V - Valid The 2 and 3 EIC's are exctracted as invalid
Temporary Solution:
N/A
Fix Information:
Will be fixed in OpenLAB CDS 2.1
Keyword: Data Analysis
One-line Description:
Create processing Method without the proper privileges.
Problem:
A user without "Create processing method" privilege (but has privileges to "Save master method", "Save results set method", and "Edit contents of project") can bypass and create a processing method with an MSDA feature.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS v2.2.
Keyword: Data Analysis
One-line Description:
Signal Alignment doesn't refresh
Problem:
In Signals > Alignment tab, if you enter two retention times and click on "Calculate delay from RT", the table does not fresh to show the calculated delay time.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS v2.2.
Keyword: Data Analysis
One-line Description:
Wrong error message is thrown while opening same PDF report twice from DA
Problem:
Wrong error message is thrown while opening same PDF report twice from DA when the Microsoft Edge is used a viewer.
Temporary Solution:
Use the Acrobat Viewer.
Fix Information:
The Microsoft Edge is not supported as PDF viewer.
Keyword: Data Analysis
One-line Description:
"Extract Chromatogram" option not available for LC/MS Chemstation data
Problem:
In OpenLAB CDS 2.1 when you load LC/MS Chemstation data acquired by OpenLAB ChemStation Edition, the "Extract Chromatogram" context menu option is not available from the injection panel nor the chromatogram window. As a result, a signal cannot be selected.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS v2.2.
Keyword: Data Analysis
One-line Description:
Manual integration: different results for nested baseline for reprocess with and without clear
Problem:
Create a nested baseline inside a peak. Inside this peak create another nested baseline. Transfer all to the method. Now you get for the main peak different areas for reprocess and reprocess with clear. Reprocessing with clear the inner nested peak will be subtracted and reprocessing without clear not.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLAB CDS v2.2
Keyword: Data Analysis
One-line Description:
"Add/Update MS compounds" does not work on SIM data acquired in OpenLAB CDS 2.0
Problem:
If you acquired SIM data in OpenLAB CDS 2.0 and open it in OpenLAB CDS 2.1, you cannot use "Add/Update MS compounds".
Temporary Solution:
n/a
Fix Information:
In OpenLAB CDS 2.1, if you want to use "Add/Update MS compounds" for SIM data, the data needs to be acquired with OpenLAB CDS 2.1.
Keyword: Data Analysis
One-line Description:
Amount is not calculated
Problem:
The amount value is not calculated when the [Level] in the Method settings is empty.
Temporary Solution:
n/a
Fix Information:
Fill in the [Level] in the Method - Calibration settings
Keyword: Data Analysis
One-line Description:
New result set with baseline corrected is not showing the * next the signal name
Problem:
Creating a new result set with an injection that is baseline corrected and using the same Method with the baseline correction saved, the corrected chromatogram is shown, but without "*" next to the signal name. After closing and reloading the data, the uncorrected signal is shown.
Temporary Solution:
Close and reload the result set after the creation.
Fix Information:
Will be addressed in the new release.
Keyword: Data Analysis
One-line Description:
"Response Window Type" is disabled for manually added compounds and qualifier ions
Problem:
If you add a compound and its qualifier ions manually, the Response Window Type is disabled for the compound. For example, the Absolute Response Window Type cannot be changed to Relative for the manually added compound and qualifier ions.
Temporary Solution:
The Response Window Type can still be changed to/from Absolute or Relative in the Qualifier Setup tab. However, the change would apply to all compounds (not specific compounds) in the Compound Table.
Fix Information:
This issue is resolved in OpenLAB CDS 2.2.
Keyword: Data Analysis
One-line Description:
Importing a result set file (.olax) could lead to misleading versions
Problem:
Assume you have a result set with a linked method that has been reprocessed, you then change the method, save it without reprocessing, and export the result set. When you import it in Data Analysis, the manifest is rewritten and the method version is changed. However, method version and data are now not in sync.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLAB CDS v2.2.
Keyword: Data Analysis
One-line Description:
The master processing method is not linked properly to the imported EZChrom result set file
Problem:
Processing methods cannot be properly linked to the result sets that were acquired in OpenLAB CDS EZChrom Edition. This happens only with EZChrom result set acquired with the project option "do not include method in result set" checked.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Incorrect Signal Names after importing ChemStation Data
Problem:
The importing procedure is modifying the Signal Names. A situation has been discovered where the Signal Names were changed from: DAD 1 A to DAD A; DAD 1 B to DAD B; etc.
Temporary Solution:
n/a
Fix Information:
Update your processing method pointing to updated Signal Names
Keyword: Data Analysis
One-line Description:
LC/MS SIM data acquired in MMI is not displayed in TIC in Data Analysis
Problem:
In OpenLAB CDS 2.1, if LC/MS SIM data acquired in Mixed Mode Ionization (MMI) is extracted per the processing method as part of Acquisition, then the signal does not show up in Total Ion Chromatogram (TIC) in Data Analysis.
Temporary Solution:
In OpenLAB CDS 2.1, do not extract chromatograms during Acquisition as part of processing method if you want to see LC/MS SIM data show up in TIC in Data Analysis.
Fix Information:
This issue is resolved in OpenLAB CDS 2.2.
Keyword: Data Analysis
One-line Description:
"Send spectra to NIST MS program" works only for first user, fails for all subsequent users
Problem:
"Send spectra to NIST MS program" works successfully for the first user who performs this task. However, after the first user exits Data Analysis, all subsequent users who try to perform this task again will get an unexpected error and Data Analysis crashes. It'll work successfully if the first user performs this task again. It won't work for all subsequent users unless they have local admin privileges. This happens on Workstation, Client/Server, Remote Desktop Server (Terminal Server) and Citrix Server environments.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS 2.1 SR1 HF2, and OpenLAB CDS 2.2.
Keyword: Data Analysis
One-line Description:
Import raw data from the ChemStation fails
Problem:
Importing two MS signals acquired either POS/NEG switching or SCAN/SIM from ChemStation C.01.06 results in the following error message in OpenLab CDS v2.1: "Files could not be integrated and reprocessed since there are two signals with the same name."
Temporary Solution:
Use FTP protocol to copy the raw data folder(s) directly to the "Results" folder.
Fix Information:
This issue is fixed in OpenLab CDS v2.2.
Keyword: Data Analysis
One-line Description:
Quantification of compounds or groups using a reference calibration curve fails if reference is missing in injection
Problem:
In Data Analysis, compound or group amounts can be calculated with a reference calibration curve of another compound or group. In the case of missing reference in an injection, the compound or groups referring to this reference will not be calculated in this injection, even if a calibration curve exists.
Temporary Solution:
As temporary fix in OpenLab CDS v2.2 and earlier, a custom calculation or a report template can be designed to calculate the amount.
Fix Information:
This affects OpenLab CDS v2.2 and earlier releases. A fix has been released in OpenLab CDS v2.3.
Keyword: Data Analysis
One-line Description:
Search field does not return all applicable results when searching for a result name
Problem:
Searching data with the keyword (option-search text in data selection) is not displaying all results and showing fewer results than actual. Any result sets that have aborted injection with time stamp 1601-MM-DD-HH:MM:SS will not be searchable.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.3 and OpenLab ECM XT v2.3.
Keyword: Data Analysis
One-line Description:
Cannot load result set in Data Analysis due to missing/corrupted .acaml or .rx files
Problem:
When a result set is missing or contains corrupted .acaml and/or .rx files, it cannot be loaded in Data Analysis. The reason for missing or corrupted .acaml or .rx files may be caused by an incorrect Acquisition / Data Analysis workflow. For more details on the workflow, see service note OpenLAB CDS-046 "A workflow issue may cause data loss for customers running Workstation (File Based System) on OpenLAB CDS v2.1 or v2.2".
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3, OpenLab CDS v2.2 Update 3, and OpenLab CDS v2.1 SR1 Update 6.
Keyword: Data Analysis
One-line Description:
Incorrect injection date for data file imported from OLCDS CS C.01.05
Problem:
Imported the data acquired on C.01.05[35] into OpenLAB CDS 2.1 and 2,2. Then found the injection date was changed. Original date C.01.05[35]: 2017/7/3 17:00:54 Migrated date CDS 2.1: 3/20/2011 9:17:10 PM
Temporary Solution:
n/a
Fix Information:
The issue is resolved in OpenLab CDS v2.3, v2.2 Update 3, and v2.1 SR1 Update 6.
Keyword: Data Analysis
One-line Description:
Cannot process data after adding a qualifier to ISTD compound
Problem:
When the user adds a qualifier to a compound that is an ISTD, a processing error occurs in the compound calibration (ISTD compound can not be found).
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3, v2.2 Hotfix 1, and v2.1 SR1 Update 6.
Keyword: Data Analysis
One-line Description:
Asterisk * is shown next to injection even though all manual integration is removed
Problem:
After the user performs "Undo" on all the manual integration but lock the data, the asterisk * still appears next to the injection.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword: Data Analysis
One-line Description:
Slow performance in processing SIM data
Problem:
In OpenLab CDS v2.3 and earlier, it takes a long time to perform the following data processing functions for SIM data: - Fill down "RT window (%)" column in Compound Table under the Identification tab - Add or remove tick from overlaid EICs - Remove qualifier ions manually and add another - Assign new compound as qualifier ion and vice versa
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Data Analysis
One-line Description:
File Upload Queue Error "Target file is inaccessible. Upload cannot be performed."
Problem:
A workflow issue has been identified in OpenLAB CDS 2.2 and earlier versions that causes an upload error in the File Upload Queue, preventing pending files from being uploaded to OpenLAB Server. The workflow described below is not recommended and should be avoided. 1. Load a result set “ABC.rslt” in Data Analysis 2. Open a processing method “A.pmx” from another result set “DEF.rslt” 3. Link the processing method “A.pmx” with result set “ABC.rslt” 4. Click on “Update Master Method” 5. Save all results By doing above steps, the processing method “A.pmx” will get stuck in the File Upload Queue and causes error "Target file is inaccessible. Upload cannot be performed."
Temporary Solution:
Until the error is cleared, all files in result set folder “ABC.rslt” will stay in "Pending" status and waiting to be uploaded to the OpenLAB Server. Please contact Agilent Support for Service Note OpenLAB CDS-060 for details on how to clear the error in File Upload Queue.
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword: Data Analysis
One-line Description:
"Qualifier group details" table is not displayed for ISTD that fails qualifier criteria
Problem:
When an ISTD compound has a "Fail" qualifier status, then the "Qualifier group details" table is not displayed in the Injection Results window.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 03.
Keyword: Data Analysis
One-line Description:
Incorrect injection date for data file imported from OLCDS CS C.01.05
Problem:
Imported the data acquired on C.01.05[35] into OpenLAB CDS 2.1 and 2,2. Then found the injection date was changed. Original date C.01.05[35]: 2017/7/3 17:00:54 Migrated date CDS 2.1: 3/20/2011 9:17:10 PM
Temporary Solution:
n/a
Fix Information:
The issue will be fixed in CDS 2.3, 2.2 Update 3, and 2.1 SR1 Update 6.
Keyword: Data Analysis
One-line Description:
Incorrect injection date for data file imported from OLCDS CS C.01.05
Problem:
Imported the data acquired on C.01.05[35] into OpenLAB CDS 2.1 and 2,2. Then found the injection date was changed. Original date C.01.05[35]: 2017/7/3 17:00:54 Migrated date CDS 2.1: 3/20/2011 9:17:10 PM
Temporary Solution:
n/a
Fix Information:
The issue will be fixed in CDS 2.3, 2.2 Update 3, and 2.1 SR1 Update 6.
Keyword: Data Analysis
One-line Description:
Incorrect category displayed in the "Reason for Changes" window
Problem:
In the project's Audit Trail Settings, "Automatically enable audit trail" and "Prompt for reason when saving" are selected. In Data Analysis, with the "MS" method configuration selected, when you add a compound to Compound Table and change values in Qualifier RT window, and save the method, the "Reason for Changes" window appears asking for a reason to save. In the "Reason for Changes" window, the category for the first two actions (add compound and change qualifier RT window) is shown as "Extraction" and "Calibration", respectively. The category in the audit trail should have been "Compound identification" for both actions.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Injection error "Cannot run integration" if data has two MS signals with same name
Problem:
Processing data that has identical EICs with same name encounters error message "Two signals with the same name were found. Cannot run integration."
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3. However, for data acquired in version 2.2 or earlier, after you load the data in v2.3, you need to delete all EICs that have same signal name from the injection tree before reprocessing the data again.
Keyword: Data Analysis
One-line Description:
Sliders in the isoabsorbance plot are not always synchronized
Problem:
Moving the slider in the chromatogram in the isoabsorbance plot will not always be synchronized with the slider in the isoabsorbance plot.
Temporary Solution:
n/a
Fix Information:
This got fixed in OpenLab CDS 2.5.
Keyword: Data Analysis
One-line Description:
User without "Save Master Method" privilege can still save master method in Data Analysis
Problem:
User without "Save Master Method" privilege can still save changes to the method through reprocessing single run data and saving the result.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3 and OpenLab CDS v2.2 Update 4.
Keyword: Data Analysis
One-line Description:
Not all signals of EZChrom method are imported
Problem:
In OpenLab CDS v2.3, when you import an EZChrom method with four channels, only signal A as channel A in shown.
Temporary Solution:
n/a
Fix Information:
This is issue fixed in OpenLab CDS v2.5 and OpenLab CDS v2.3 Update 11.
Keyword: Data Analysis
One-line Description:
"Data storage not available" when starting Data Analysis
Problem:
When starting Data Analysis on some projects, a message appears: "The data storage is not available. Check the connection to the server". After confirming twice, the Data Analysis can be used without any further issue. The behavior may depend on the size and/or depth of the directory tree within a project.
Temporary Solution:
"The data storage is not available. Check the connection to the server" is only a warning message. Just click [ OK ] to continue.
Fix Information:
The issue is resolved in the OpenLab CDS v2.3 and OpenLab CDS v2.2 Update 3 by increasing the 1-minute time out.
Keyword: Data Analysis
One-line Description:
Canceling a method link will lead to different method parameters
Problem:
Open an Injection or Result set that has a linked method, change some parameters, reprocess, and then click "Save all results". Next, open a different method and link it to this Injection/Result set. The software warns that a method already exists in the result set and asks if you want to overwrite the existing method. If you click "Cancel link", then the existing (linked) method is now loaded with default parameters instead of parameters that were in the method before the link.
Temporary Solution:
This issue is resolved in OpenLab CDS v2.3.
Fix Information:
NA
Keyword: Data Analysis
One-line Description:
No signal in snapshot if snapshot is performed immediately after start of run
Problem:
If a snapshot is performed in Acquisition immediately after the run just started, no chromatogram is shown in Data Analysis.
Temporary Solution:
Signal is stored after a minimum of 0.25 minutes of run time. Be sure to wait at least 0.3 minutes of run time before you perform a snapshot.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
User without “Save master method” privilege cannot save results
Problem:
When a user without "Save master method" privilege changes parameters of the injection list but does not change the master method in anyway, the "Save All Results" or "Save Selected Result" button is grayed out (not available).
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 06.
Keyword: Data Analysis
One-line Description:
Calibration curve does not start from zero
Problem:
When building a linear calibration curve with 2 points including (0,0), we expect an equation like y=ax. But in some cases, the originate at the origin could be different from zero (for example: y=ax+5e-17). The equation (y=ax+b) is always computed when a Linear calibration curve is selected. Real values (which have a precision of 15 digits) are used for the computations (which leads to values with a higher precision). This difference in precision could lead to a “b” value different from 0 (between 1e-15 and 1e-17) as expected. This value is below the precision of real values.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Data Analysis is slow to open with projects that have many folders
Problem:
When a project has many folders, Data Analysis takes some time to open and list all the folders. With a couple hundred, this can be more than a minute. With a thousand, it can be more than 3 minutes.
Temporary Solution:
For now, Agilent recommends users limit the number of folders in a project to avoid this issue. Currently performance is optimized for data structured in a hierarchical manner. So if you have many result sets in one folder, performance will improve if you organize them in groups in a hierarchical folder structure. Keeping the Data Analysis session opened will also help.
Fix Information:
This issue is fixed in OpenLab CDS v2.4, OpenLab CDS 2.3 Update 5 and OpenLab CDS v2.2 Update 6.
Keyword: Data Analysis
One-line Description:
Incorrect injection date for data file imported from OLCDS CS C.01.05 or ChemStation B.04.03
Problem:
Imported the data acquired on OpenLAB CDS ChemStation C.01.05 or ChemStation B.04.03 into OpenLAB CDS 2.1 and 2,2. Then found the injection date was changed. Example Original date C.01.05[35]: 2017/7/3 17:00:54 Migrated date CDS 2.1: 3/20/2011 9:17:10 PM
Temporary Solution:
n/a
Fix Information:
The issue is resolved in CDS 2.3, 2.2 Update 3, and 2.1 SR1 Update 6.
Keyword: Data Analysis
One-line Description:
Data Analysis crashes with GPC 1.0 plugin (G7860AA)
Problem:
After the upgrade from OpenLAB CDS 2.2 to 2.3, the Data Analysis crashes when executing the GPC/SEC 1.0 plugin.
Temporary Solution:
Upgrade the GPC/SEC software to version 1.1.
Fix Information:
If an OL CDS 2.2 with GPC plugin installed is upgraded to OL CDS 2.3, the GPC s/w needs to be uninstalled (before or after the upgrade) to allow Data Analysis to be used. GPC/SEC software (G7860AA) must be upgraded to Ver 1.1.
Keyword: Data Analysis
One-line Description:
Incorrect calibration curve date after reviewing completed injections or reprocessing
Problem:
Calibration curve date is not correctly updated when the review completed injections or reprocessing is performed. Having the following sequence: Blank Cal Level 1 (clear all calib). Cal Level 2 Cal Level 3 Cal Level 4 Sample 1 Sample 2 After the completion of Sample 1, the completed injections are reviewed in Data Analysis. In review mode a report was created. Issue The calibration last modified date is updated for CAL 1-3, but not for CAL 4. There is no impact of Amount computations.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Unexpected error occurs while importing raw data (ChemStation or EZChrom)
Problem:
In OpenLab CDS v2.3 Workstation (File System) or Workstation Plus (Content Management), if file xys.d or xyz.dat already exists in Project\Results folder and you try import another file with the same name (xyz.d or xyz.dat), this will result in an unexpected error.
Temporary Solution:
Before importing data, make sure the name of the file to be imported does not already exist in Project\Results folder.
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 03.
Keyword: Data Analysis
One-line Description:
User without "Save Master Method" privilege can still save master method.
Problem:
User without "Save Master Method" process method privilege can still save changes to the master process method through reprocessing single run data and saving result.
Temporary Solution:
NA
Fix Information:
Will be addressed in the OpenLab CDS 2.1 Hot Fix 07
Keyword: Data Analysis
One-line Description:
Compound identification fails when different compounds have same quantifier ion
Problem:
With "EIC extraction retention time window for target compounds" set to the default values of 0.20 for "Absolute RT window (min)" and 0.0 for "Relative RT window (%)", the compound identification fails if more than one compound has the same quantifier ion.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Data Analysis
One-line Description:
Loading multi signal in DA causes software crash
Problem:
If an HPLC multi signal (DAD A and DAD B) is identified, and a Peak on Signal B is defined as "Qualifier" for the same peak on Signal A (main Peak), Data Analysis crashes with "An unexpected error has occurred..."
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.3 Update 03, and OpenLab CDS v2.2 Update 04.
Keyword: Data Analysis
One-line Description:
RX files are missing in result sets due to EZChrom integration "Split peak" events
Problem:
RX files are missing from the result sets and the data cannot be viewed in Data Analysis. The root cause is due to EZChrom integration "Split peak" events in the processing method that the user has specified in the sequence.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4, OpenLab CDS v2.3 Update 04, and OpenLab CDS v2.2 Update 05.
Keyword: Data Analysis
One-line Description:
AIA export has minutes as time units
Problem:
The AIA export contains retention unit of the x-axis in minutes. According to the AIA Chromatography Data Standard Specification the default unit for the retention axis is time in seconds. This impacts also peak-area (detection-unit * retention-unit)
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.3 Update 3 and OpenLab CDS 2.4 upwards.
Keyword: Data Analysis
One-line Description:
When using signal delay, EICs do not line up with TIC peaks
Problem:
When signal delay is used, EICs in the Peak Details window for MS Peak Purity feature does not line up with the associated TIC peaks.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.3 Update 04.
Keyword: Data Analysis
One-line Description:
MS Peak Purity should only be calculated for TIC peak, not EIC
Problem:
In OpenLab CDS v2.3, when the user turns ON the MS peak purity calculation in the processing method and reprocess all injections, the MS peak purity is calculated using the peaks in the TIC and EICs. This is not correct.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 04 such that MS peak purity is calculated for TIC peaks only.
Keyword: Data Analysis
One-line Description:
Disabled calibration point will be enabled after reprocessing
Problem:
Reprocessing a result set after disabling a calibration point will enable the calibration point again. The disabled calibration point cannot be applied on other injections.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Default CDF file name of AIA export is not working for SIMDIS
Problem:
SIMDIS cannot work with default output name of AIA export in OpenLab CDS 2.3
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.3 update 03 and OpenLab CDS 2.4 upwards. CDF file naming is <samplename>_<datafilename>_<signal>.cdf Also the AIA subfolder creation for each injection got removed. The .cdf file will be stored directly in the defined output path.
Keyword: Data Analysis
One-line Description:
Front exponential skim does not work or integrate properly
Problem:
When using the integration event “front exponential skim”, the values for intercept and slope were interchanged for exponential baseline. This leads to an incorrect calculation/display of the exponential baseline.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4, OpenLab CDS v2.3 Update 04, and OpenLab CDS v2.2 Update 05.
Keyword: Data Analysis
One-line Description:
USP theoretical plates are different in OpenLab CDS versus ChemStation.
Problem:
Although the same USP formulas for theoretical plates are used, there are small differences between ChemStation and OpenLab CDS due to differences in signal handling. For example, OpenLab CDS is 64 bit while ChemStation is 32 bit. Typically this would be less than 5% but can be much larger depending on the signal and sampling rate (lower sampling rates will result is a larger difference). For more information, refer to the Help topic “Select the ChemStation or EZChrom integrator”. This is also mentioned in the ChemStation to OpenLab CDS Migration guide (MigrationGuide_OpenLABCDSChemStnToCDS2.3.pdf page 32).
Temporary Solution:
None. See Fix Note.
Fix Information:
No change is planned. Results in ChemStation and OpenLab CDS will not be exactly the same. They should be comparable with small differences. Agilent recommends users verify and document that the results are comparable for their specific analyses.
Keyword: Data Analysis
One-line Description:
Drift calculation differences in OpenLAB EZCHrom and OpenLab CDS 2
Problem:
The Drift calculation between the EZChrom and the OpenLab CDS 2.3 are not showing the same values. For the same time range and the same injection the drift results are not the same. The reasons are: The CDS 2 Data Analysis is computing a linear regression between the start and the stop of the range defined in the method. EZChrom computes a ratio (Y2-Y1)/(X2-X1) where X2 and X1 are the start and the stop of the range defined in the method The CDS 2 Data Analysis is showing the drift in (Voltage unit so either mAU, MicroV…)/h In EZChrom, the drift unit is (Voltage unit so either mAU, MicroV…)/min The ASTM is asking for a regression expressed in AU/h. The formula to compute the value in Excel is: =slope (Yvalues : Xvalues) and should be multiplied by 60 to have the Voltage unit/hour.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Error while importing OpenLab CDS ChemStation Edition data
Problem:
Using the import raw data function to import ChemStation data it might occur an unexpected error.
Temporary Solution:
Copy the ChemStation data manually to the result folder of OpenLab CDS 2
Fix Information:
This is fixed in OpenLab CDS 2.4 and 2.3 Update 4
Keyword: Data Analysis
One-line Description:
AIA export of GPC method isn't working
Problem:
Having OpenLab CDS 2.3 with GPC/SEC Add-On when trying to do an AIA export with a GPC method, the export does not work. It works with ChemStation export and OL CDS export. AIA export also works, as soon as you select a different kind of method (e.g. GC/LC Quant).
Temporary Solution:
Use a different kind of Method , not a GPC one.
Fix Information:
Solved in OpenLab CDS 2.4.
Keyword: Data Analysis
One-line Description:
System suitability results are not calculated for specific peaks
Problem:
In some cases, the system suitability results (e.g. the number of theoretical plates per column (USP) or resolution) cannot be reported in the software. To calculate those values the tangent width of a peak is needed. In case of high noise or high data rate of the chromatogram the correct determination of the tangent width will not be possible for some peaks. In such a case a calculation of the system suitability values is not possible.
Temporary Solution:
n/a
Fix Information:
Open Lab CDS rev. 2.6 introduces an advanced tangent calculation mode for noisy or high resolution signals. If this mode is activated the tangent construction is less sensitive with respect to noise.
Keyword: Data Analysis
One-line Description:
Unable to integrate Child-Parent peak using EZChrom Integrator in OpenLab CDS 2.3
Problem:
When using the EZChrom integrator there is a check if the first time data point of the signal to be integrated starts at time zero. If this is not the case one additional data point will be added to the signal at time zero before the integration. This is to allow EZChrom integrator to handle this specific situation. Furthermore the EZChrom integrator can only work with equidistant data. When we add an additional data point at time zero, even previously equidistant data will become non-equidistant. Therefore, the data needs to be re-sampled in a second step. In Data Analysis we do this by spline interpolation. The resampling slightly modifies the data, i.e. the data that is used for integration is slightly different than the originally acquired data. These slight modifications in the data introduced by the re-sampling is the reason why the results differ in OpenLab CDS 2.3 from what the customer gets when using OpenLab CDS EZChrom.
Temporary Solution:
Use the OpenLab CDS ChemStation Integrator or perform a manual integration.
Fix Information:
Fixed in OpenLab CDS 2.4. The fix will affect the Method User Interface. It's not suitable for an OpenLab CDS update/hotfix.
Keyword: Data Analysis
One-line Description:
Long processing time for MS data
Problem:
In OpenLab CDS v2.3 and earlier, MS data with large number of SIM ions (75+) and injections (125+) takes a long time to process in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 04.
Keyword: Data Analysis
One-line Description:
"detector_name" field in cdf file is not unique when using the AIA Export Plugin in DA
Problem:
The CDS2 detector name is assigned to the AIA detector_name field. However, if there are multiple signals with the same detector name (e.g., front FID and back FID), then the detector name alone does not provide unique name for the multiple signals exported using AIA Export Plugin like SimDis XLNC (CNS configuration) and GasXLNC.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and Openlab CDS v2.3 Update 04. The signal description is now used for the AIA detector_name field to ensure that the AIA detector_name field is unique (per injection).
Keyword: Data Analysis
One-line Description:
Missing peak entries get duplicated in DA and IR
Problem:
When a result set is loaded and has missing peak(s), the Data Analysis (DA) view and Intelligent Reporting (IR) report look OK. But if the result set is reprocessed, then the missing peak entries get duplicated. If the result set is closed (without saving) and reopened, then it looks fine again.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 06.
Keyword: Data Analysis
One-line Description:
RT calculation values in Data Analysis (Result view) and Intelligent Report do not match
Problem:
The RT calculation performed in Data Analysis is different than the one performed in the Intelligent Report. When System Suitability (in Method-System Suitability-Properties) is selected, the Retention Time of the peaks is recalculated.
Temporary Solution:
n/a
Fix Information:
The OpenLab Help & Learning in OpenLab CDS v2.4 has been updated with the following text (under the section System Suitability Calculations > Performance test definitions > NOTE: Retention time used for performance tests) to clarify how RT calculation is performed: "Please note that the retention time (RT) depicted in the figure below and determined by the peak integrator is not necessarily associated with the highest data point. The retention time is usually calculated using an parabolic interpolation model. This means that the retention time RT can potentially be smaller or larger than the retention time of the highest data point and the height might also be higher or lower than the highest data point."
Keyword: Data Analysis
One-line Description:
Corrected expected retention time is not visualized correctly
Problem:
When using a processing method setup with one or more time reference peaks, the visualization of the compound identification windows for the non-reference peaks are not adjusted to corrected expected retention time.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.6.
Keyword: Data Analysis
One-line Description:
Unexpected error occurs during processing of Custom Calculation due to a stop injection in sequence
Problem:
Unexpected error occurs during processing of Custom Calculation if there is a stop injection in the sequence. This is because the stop injection has no element and no signal.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4.
Keyword: Data Analysis
One-line Description:
Tree: Upload in progress icon disappears after refresh
Problem:
The information that an upload is in progress is generated on the client side - after clicking the refresh button, the tree is re-built only using the back-end and the upload in progress icon is no longer displayed.
Temporary Solution:
A message is shown when the user try to load a Result Set where the upload is not yet completed.
Fix Information:
The Online Help will be updated to describe the feature.
Keyword: Data Analysis
One-line Description:
When importing OLAX, the file disappears from the tree after Refresh
Problem:
- Imported sequences will show with sequence icon. If not in the backend yet, load will give a message. - Imported single runs are not added as node in the tree.
Temporary Solution:
None
Fix Information:
User can click on folder node (the one that was the target for the import) will see the single injections as soon as the import is done.
Keyword: Data Analysis
One-line Description:
S/N ratio not calculated when using data acquired with Waters Acuity
Problem:
The Signal to Noise (S/N) ratio is not calculated for data acquired with Waters Acquity if the noise is measured on a blank as per European Pharmacopeia.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 06.
Keyword: Data Analysis
One-line Description:
Data Analysis is slow to open with projects that have many folders
Problem:
When a project has many folders, Data Analysis takes some time to open and list all the folders. With a couple hundred, this can be more than a minute. With a thousand, it can be more than 3 minutes.
Temporary Solution:
For now, Agilent recommends users limit the number of folders in a project to avoid this issue. Currently performance is optimized for data structured in a hierarchical manner. So if you have many result sets in one folder, performance will improve if you organize them in groups in a hierarchical folder structure. Keeping the Data Analysis session opened will also help.
Fix Information:
Agilent will correct this issue in a future software release. As soon as a timeline is available, this software status bulletin will be updated.
Keyword: Data Analysis
One-line Description:
Unhandled exception when closing custom calculation editor if connection with shared services server has been lost
Problem:
It might happen that there is a unhandled expectation when closing the custom calculator in case the connection to the shared services server gets interrupted.
Temporary Solution:
n/a
Fix Information:
This will be fixed in OpenLab CDS 2.5
Keyword: Data Analysis
One-line Description:
Not all injections might get reprocessed if UV impurity check for all peaks is selected
Problem:
If the loaded data contains to many small peaks and UV impurity check for all peaks is selected it might be that the reprocessing is not done for all injections.
Temporary Solution:
Reduce the amount of small peaks by adjusting the integration parameters.
Fix Information:
This is fixed in OpenLab CDS 2.4 Update 3 and will be fixed in OpenLab CDS 2.5
Keyword: Data Analysis
One-line Description:
DA does not display data in failover mode and data can't be reprocessed
Problem:
In OpenLab CDS 2.3 in Failover mode, the Data Selection tree in Data Analysis is empty. The user cannot load nor reprocess acquired data .
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.3 Update 07.
Keyword: Data Analysis
One-line Description:
Cannot extract spectrum from TIC SIM with multiple fragmentors
Problem:
In OpenLab CDS v2.4 and earlier, it is not possible to extract spectrum from TIC SIM if the data was acquired with multiple fragmentors.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, OpenLab CDS v2.4 Update 03, and OpenLab CDS v2.3 Update 07.
Keyword: Data Analysis
One-line Description:
In some cases manual integration might be erased when reprocessing
Problem:
When reprocessing injections which contain manual integration, the manual integration events may be removed after reprocessing. This issue is occurring only sporadically on some injections, and particular peaks. This had been observed with extracted ion chromatograms in the context of compound identification.
Temporary Solution:
The manual integration events will persist if the manual integration events are saved in the methods. Alternatively, modifying the signal integration events can be used to trigger the automated peak detection and belonging integration.
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
EIC is not automatically extracted for MS timed group compounds
Problem:
If a compound is assigned as timed group, the EIC is not automatically extracted when you reprocess the data, even though there is a peak in the time range.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
The Retention Time definition in the Data Analysis Reference Guide is misleading because of a wrong drawing
Problem:
The RT value in DA and reports is the highest point of the internally calculated peak curve. The Retention Time associated with the highest data point is called the PeakModelRT in the DA and reports. In the drawing of the OpenLab help and the Data Analysis Reference Guide under “Performance test definitions” the 2 data points are shown reversed.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Error occures when a different user tries to link a new method to data
Problem:
Locking the data analysis windows with a user 1 and unlocking with user 2, then load data and try to link a new method via context menu "link selected injections to selected method" to this data might cause an issue.
Temporary Solution:
Use the "Link Method" in the ribbon bar.
Fix Information:
This will be fixed in OpenLab CDS 2.5
Keyword: Data Analysis
One-line Description:
ISTD amounts not considered for calibration curve recalculation in some circonstancies
Problem:
Using internal standard calibration is associated to fields used in acquisition and in the Data Analysis injection list to enter the related ISTD amounts of each internal standard used in the sample ("ISTD Amt 1", "ISTD Amt 2", ...). These fields, if modified, are used to recalculate the compound calibration statistics. In some circumstances, this calibration curves reevaluation will not occur. In such cases, injection results in Data Analysis will show recalculated compound “amounts” and “concentrations” but based on incorrect calibration curves. The calibration curve details can be used in the "Calibration Curve" window to evaluate and identify this misleading calibration. Scenarios leading to incorrect calibration curves: Calibration sequences without any bracketing mode (Overall, Non overlap, Overlap, Custom) or "Clear all calibration". If any ISTD amount is modified after original calibration curve creation, the amounts and concentrations will be recalculated based on incorrect calibration curves. Scenario not affected by this issue: Calibration sequences which relates to the initial compound calibration. In such cases, the calibration curves will be built based on correct ISTD amounts, independently if there is a bracketing mode or any "Clear all calibration". Calibration sequences with automated calibration bracketing, or in the cases the calibration curves are cleared from the method by: - Performing a "Clear all calibration". - Or manually removing all compound calibration curves.
Temporary Solution:
Problem identification can be performed by evaluating the calibration summary updates, as well as in reporting using the calibration details table. Calibration statistics, history points as well as calibration curve last modification timestamps will help to evaluate the consistency of the results. To update the quantification statistics, performing a "clear all calibration" or using a bracketing mode will force results reevaluation.
Fix Information:
This issue will be fixed in an upcoming OpenLab CDS v2.4 software update, as well as in OpenLab CDS v2.5.
Keyword: Data Analysis
One-line Description:
Error occurs upon reprocessing MS data with system suitability calculations
Problem:
When reprocessing MS TIC scan data with system suitability calculations, the following processing error occurs with some of the data files: "System Suitability: an unexpected error occurred during processing of "System Suitability" This is due to an empty TIC Scan data.
Temporary Solution:
n/a
Fix Information:
This issue has been fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 10.
Keyword: Data Analysis
One-line Description:
Reprocessing legacy data acquired from 2.1 or 2.2 can no longer integrate after extract chromatograms
Problem:
After performing "Extract Chromatograms" on SIM or SIM/Scan data that was acquired in OpenLab CDS v2.2 and earlier, all integrated peaks becomes NOT integrated anymore. The following error message appears in the injection tree. "Injection reprocessed (with errors) Errors: ChemStation integrator: Two signals with same name were found. Cannot run integration." Once this error occurs, it is not possible to "Reprocess All" to get the peaks integrated again.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, OpenLab CDS v2.4 Update 03, and OpenLab CDS v2.3 Update 07.
Keyword: Data Analysis
One-line Description:
"Add/Update MS compounds" is not working with SIM data
Problem:
In OpenLab CDS v2.4, nothing happens when user performs "Add/Update MS compounds" on SIM data. The Compound Table remains empty.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 02.
Keyword: Data Analysis
One-line Description:
Noise, signal-to-noise and system suitability calculations for extracted chromatograms
Problem:
In OpenLab CDS v2.4, when extracted chromatograms are used to perform noise, signal-to-noise or any related system suitability calculations, the calculations will not be performed in cases the noise range is taken within blank injections as per the European pharmacopoeia guidance. This has been identified for UV and MS extracted chromatograms.
Temporary Solution:
n/a
Fix Information:
This will be fixed in OpenLab CDS v2.4 Update 02 and OpenLab CDS v2.5.
Keyword: Data Analysis
One-line Description:
Locking a unsaved result set will show a warning "Newer version exists"
Problem:
In case a user wants to lock a result set which has unsaved changes OpenLab CDS 2 asks the user if the result set should be saved. If the user click on Yes a warning is displayed saying that a Newer version exists. Clicking on "yes, save" will save and lock the result set. Clicking on cancel - the result set seems to be locked but it is not. Closing the data - "Unsaved changed" warning is displayed. But the save buttons in the ribbon are not enabled. Clicking "Yes, don't save" in the warning and reopen the result set which is then not locked.
Temporary Solution:
Save changes before locking the result set.
Fix Information:
This is fixed in OpenLab CDS 2.5
Keyword: Data Analysis
One-line Description:
Manually extract UV Wavelength chromatograms is part of Privilege control on the manual but this function does not exist
Problem:
The Agilent OpenLab CDS Workstation Installation and Configuration manual is by fault stating that the privilege "Do manual chromatogram extraction" would include to manually extract UV wavelength, but it is only working with chromatograms or MS (TIC-SIM/TIC-SCAN) chromatograms from your data. In the UV spectrum UI, there is no way to extract manually a UV chromatogram, and in the Isoabsorbance plot, it is neither possible to extract manually a UV chromatogram.
Temporary Solution:
It is possible to add a line to the processing method in order to "plan" an extraction when processing.
Fix Information:
The manual should be corrected for the next software revision.
Keyword: Data Analysis
One-line Description:
Fill down sample type might cause an unexpected issue
Problem:
Using the fill down function in the injection table in data analysis to populate the sample type may cause an unexpected error. Mainly when switching the sample type black into calibration standard.
Temporary Solution:
n/a
Fix Information:
This will be fixed in OpenLab CDS 2.5
Keyword: Data Analysis
One-line Description:
Manual integration will show wrong peak width
Problem:
In case a peak gets manually integrated (e.g. move baseline) the peak width will be close to the value of the width at 50% independent from the real peak width.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.4 Update 3 and OpenLab CDS 2.5
Keyword: Data Analysis
One-line Description:
Empty project name in report for new created or imported result sets
Problem:
When a new result set gets created or an result set gets imported into a project in OpenLab CDS the project name in a report does not get populated.
Temporary Solution:
n/a
Fix Information:
This is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 4.
Keyword: Data Analysis
One-line Description:
Different values for relative retention time according to EP in ChemStation vs. CDS 2
Problem:
Depending if you take OpenLab CDS ChemStation Edition or OpenLab CDS 2 you will get a different result in Intelligent Reporting for Peak_RelativeRetTime_EP. ChemStation calculates the RRT EP with (RT<peak> - t0) / (RT<peakRef> -t0). In OpenLab CDS 2.4 it gets calculated wit RT<peak>/RT<previous peak>. Reprocessing data from ChemStation in CDS 2.4 will lead to different RRT EP values.
Temporary Solution:
n/a
Fix Information:
This will be fixed in OpenLab CDS 2.5. The RRT EP will be calculated as in ChemStation.
Keyword: Data Analysis
One-line Description:
A data processing component during acquisition became orphaned process and could not be closed automatically after a single or sequence run
Problem:
A data processing component during data acquisition cannot be closed successfully after a single or sequence run, hence becoming orphaned process, consuming memory. As a result, user may experience slowness when operating the software.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue. This has been fixed in OpenLab CDS v2.5.
Keyword: Data Analysis
One-line Description:
Revoke signature when "Enforce signature order" is enabled
Problem:
When a user revokes his/her signature and "Enforce signature order" is enabled, all other signatures are getting revoked, as well. Only when the option "Enforce signature order" is not selected, a user is not allowed to revoke the signature when a user with higher signature level has signed it. A description of this expected behavior is missing in the help text of CDS 2.4 and will be added in a future version.
Temporary Solution:
n/a
Fix Information:
The issue will be fixed in CDS 2.5 - i.e. the help text will describe the expected behavior.
Keyword: Data Analysis
One-line Description:
Reprocessing of locked result sets
Problem:
If a locked result set is selected first and then another non-locked result set is selected, it is possible to reprocess, re-quantify and even save the results.
Temporary Solution:
n/a
Fix Information:
This will be fixed in OpenLab CDS 2.5 and OpenLab CDS 2.4 Update 07
Keyword: Data Analysis
One-line Description:
Exception error occurs when loading result set
Problem:
Exception error occurs when loading a result set in OpenLab CDS 2.4 and earlier. Agilent.OpenLab.Framework.Diagnostics.ExceptionTraceRecordEx, System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Agilent.OpenLab.Framework.UI.Layout.ExternalControlledNavigationViewLayoutService.ActivateSubView() at Agilent.OpenLab.Framework.UI.Layout.ExternalControlledNavigationViewLayoutService.Activate(BaseView view) at Agilent.OpenLab.Framework.UI.Layout.WorkspaceLayoutService.InitializeViewLayoutService(BaseView view) at Agilent.OpenLab.Framework.UI.Layout.WorkspaceLayoutService.OnViewActivated(Object sender, EventArgs`1 e) at Agilent.OpenLab.Framework.UI.XamOutlookBar.XamOutlookBarLayoutService.OnSelectedOutlookBarGroupChanging(Object sender, SelectedGroupChangingEventArgs e)
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, v2.4 Update 07, v2.3 Update 11, and v2.2 Update 08.
Keyword: Data Analysis
One-line Description:
MS peak purity failing to compute purity calculation
Problem:
In OpenLab CDS v2.4, the MS peak purity may fail to evaluate the peak purity with some data. In the peak details window, the number extracted ion chromatogramms taken for purity evaluation will be lower than expected.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5.
Keyword: Data Analysis
One-line Description:
Weird profile spectrum and incorrect mass with Fast scan on LCMSD iQ and OpenLab CDS v2.5
Problem:
Profile fast scan (10K and above) data acquired using OpenLab CDs v2.5 and LCMSD iQ produces weird profile spectrum and incorrect mass.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 01 and OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Post-Processing plugin is not working for injection data file names containing { or }
Problem:
If the injection data file name contains { or } and a post processing plug-in is defined in the processing method then the post-processing plug-in is not working
Temporary Solution:
n/a
Fix Information:
This will be fixed in OpenLab CDS 2.5
Keyword: Data Analysis
One-line Description:
LC/MS profile data acquired in Chemstation C.01.XX is displayed as centroid data in OpenLab CDS v2.5
Problem:
LC/MS data acquired in Chemstation C.01.XX in profile mode is displayed as centroid data when imported in OpenLab CDS v2.5 and earlier.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 07 and OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Named Group does not appear in Injection Results
Problem:
Named Group will not be shown in Injection Results when GC_LC Area Percent_DefaultMethod or LC/MS sample purity Method is used.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.5 Update 4 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
Cannot "Send spectrum to NIST MS program" if it has more than 800 m/z ions
Problem:
In OpenLab CDS v2.4 and earlier, the user cannot "Send spectrum to NIST MS program" if the spectrum contains more than 800 m/z ions. The following error occurs: "Error: file is not a library, or library is too large: <Local drive>:\Users\<username>\AppData\Local\Temp\SPECTRA.MSP."
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and CDS v2.4 Update 07. The user can perform "Send spectrum to NIST MS program" on spectrum that has more than 800 m/z ions, but only 800 m/z ions will be exported to NIST program. To improve the quality of search results, it is recommended that the user eliminates the noise from the data prior to sending it to NIST program. Even if the noise is not eliminated, the noise should be "background subtracted" prior to library search.
Keyword: Data Analysis
One-line Description:
Modification date for the manually integrated injection does not change when saving reults
Problem:
When a injection of a result set get manually integrated and afterwards the result set get saved without reprocessing the injection with the manual integration will have a different modification date. It will have the date when the manual integration happened as modification date. The other injections will have the date when the save was done as their modification date.
Temporary Solution:
n/a
Fix Information:
This will be fixed in OpenLab CDS 2.5
Keyword: Data Analysis
One-line Description:
Blank subtraction is not possible with data generated on Hitachi Amino Acid Analyzer
Problem:
Error occurred when performing a blank subtraction with data generated on Hitachi Amino Acid Analyzer LA8080.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5, OpenLab CDS v2.4 Update 09, and OpenLab CDS v2.3 Update 13.
Keyword: Data Analysis
One-line Description:
Peak to peak or ASTM method using different value to calculate S/N as descriet in the EP
Problem:
The signal-to-noise is calculated using the formula S/N = 2H/h if Peak to peak or ASTM method is used to determine the noise. Where H is the height of the peak h the value of the largest noise fluctuation. According to the 7th edition of the European pharmacopoeia the largest noise fluctuation (h) should be observes over a distance equal to at least five times the width at half height of the peak. In OpenLab CDS the value of h is observed over a distance equal to twenty times the width at half- height of the peak.
Temporary Solution:
n/a
Fix Information:
This will be improved in a future release.
Keyword: Data Analysis
One-line Description:
UV reference spectrum assigned to compound identified in FLD signal
Problem:
For any results that contain both FLD 3D and DAD 3D data, when adding the reference spectrum manually ("Add reference spectrum to method" option), the UV reference spectrum gets extracted from the DAD spectral data using the FLD peak RT while it should be extracted from the FLD 3D data. However, this does not happen with results that contain only FLD 3D data.
Temporary Solution:
n/a
Fix Information:
This issue has been fixed in OpenLab CDS v2.4 Update 07, and OpenLab CDS v2.5.
Keyword: Data Analysis
One-line Description:
Importing ChemStation B04.01 data into OpenLab CDS 2.4 can have incorrect injection time
Problem:
Importing old ChemStation data from B.04.01 can have a incorrect injection time in OpenLab CDS 2.4. For example: In ChemStation B.04.01 the injection time was: 05-May-2014 In OpenLab CDS 2.4 it will be shown as: 2005-05-14
Temporary Solution:
This issue only occurs with English regional settings and short date format set to "yy/MM/dd". Make sure before importing old ChemStation B.04.10 data that the short date is set to M/d/yyyy.
Fix Information:
This got fixed in OpenLab CDS 2.5.
Keyword: Data Analysis
One-line Description:
Fraction collection data loaded incompletely on a distributed system with ECM 3.6
Problem:
When loading a result set with fraction collection data from an ECM 3.6 back-end it might appear that the loading was not complet. In data analysis it might look like some data is missing.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 02.
Keyword: Data Analysis
One-line Description:
Manual integration influences automatic integration of next peak
Problem:
In some situation, if an integrated peak gets modified manually, nearby peaks might disappear automatically.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Data Analysis
One-line Description:
Method report shows additional parameter for same data file after reprinting
Problem:
A method report is printed after reprocessing an MS data and saving the results. After closing Data Analysis and reloading the same MS data, if you print the method report again without further reprocessing, the report shows one additional parameter "single ppm peak width".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Selected fraction is not highlight in the sample container
Problem:
Selecting a fraction in the fraction results table might not be reflected in the sample container. This can happen if a fraction is marked by a "re-injection" or "inconsistency detected" icon in the sample container.
Temporary Solution:
n/a
Fix Information:
This is fixed in OpenLab CDS v2.6
Keyword: Data Analysis
One-line Description:
Imported OpenLab CDS EZChrom data has incorrect injection time when daylight saving time is activated is turned on
Problem:
The injection time of migrated OpenLab EZChrom data might appear incorrect in OpenLab CDS 2. If "Adjust for daylight saving time automatically" is turned on in the operating system settings the injection time is reported like e.g.11:57 +01:00. The correct time should be "11:57 +02:00".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6
Keyword: Data Analysis
One-line Description:
Unhandled exception when OLSS server is unavailable during search
Problem:
During a search in OpenLab Data Analysis with content management it can happen that the OpenLab Shared Services Server is unavailable e.g. due to network issues. In this case a unexpected error can occur.
Temporary Solution:
n/a
Fix Information:
This will be fixed in OpenLab CDS 2.5 Update 02 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
"Identified peaks" is not working in MS Peak Purity workflow
Problem:
When "Identified peaks" is selected in method under Compounds > Spectra > MS Peak Purity tab, the "Injection results" window shows all integrated peaks, instead of identified peaks only.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and in OpenLab CDS v2.5 Update 02.
Keyword: Data Analysis
One-line Description:
Wrong "Rsp (%)" values are calculated in the “Qualifier group details” table
Problem:
In OpenLab CDS v2.5 and earlier, "Rsp (%)" values shown in "Qualifier group details" table of the Compound Table and the Injection Results window are incorrectly calculated, if the qualifier ions are assigned from MS spectrum that is extracted from Total Ion Chromatogram (TIC). This is not an issue if the qualifier ions are assigned from MS spectrum that is extracted from Extracted Ion Chromatogram (EIC).
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and in OpenLab CDS v2.5 Update 03. The Rsp (%) is now calculated using the value of the closest peak in the EIC (derived from the MS base peak m/z ion) rather than the TIC that was used to extract the MS spectrum.
Keyword: Data Analysis
One-line Description:
Loading single injections in Data Analysis is slow
Problem:
In OpenLab CDS v2.3, if hundreds of single injections are stored in subfolders in a project, it takes a long time for the single injections to show up when user clicks on a subfolder.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 Update 08 and OpenLab CDS v2.3 Update 11.
Keyword: Data Analysis
One-line Description:
OpenLab CDS v2.5 crashes with exception error when viewing MS spectrum
Problem:
OpenLab CDS v2.5 crashes with error "System.NullReferenceException: Object reference not set to an instance of an object" when trying to view peak spectrum that was created from spectrum subtraction.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 02 and OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Fraction collection data loaded incompletely on a distributed system with ECM 3.6
Problem:
When loading a result set with fraction collection data from an ECM 3.6 back-end it might appear that the loading was not complet. In data analysis it might look like some data is missing.
Temporary Solution:
Reload the data from the back-end
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
OpenLab CDS v2.5 shows no TIC signal when "Import Raw Data" acquired with MSD ChemStation
Problem:
Using "Import Raw Data" in OpenLab CDS v2.5 to import MSD ChemStation data files (.D), there is no signal in the Total Ion Chromatogram (TIC). This issue does not occur with OpenLab CDS v2.4 and earlier.
Temporary Solution:
n/a
Fix Information:
If the MSD ChemStation data file (.D) is loaded in OpenLab CDS v2.4, reprocessed, saved, and exported as .OLAX file, then the import of this .OLAX file in OpenLab CDS v2.5 works fine. This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 03.
Keyword: Data Analysis
One-line Description:
MS data takes long time to reprocess in OpenLab CDS v2.5
Problem:
In OpenLab CDS v2.5, large MS data with many compounds and injections takes a long time to reprocess in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 01 and OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Import OpenLab EZChrom raw data fails if File System Security is enabled
Problem:
"Failed to import raw data" error occurs when attempting to import OpenLab EZChrom raw data to system that has File System Security enabled.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 03.
Keyword: Data Analysis
One-line Description:
Data Analysis gets unresponsive when canceling the reasons dialog
Problem:
Loading data without a processing method in a project with method audit trail settings 'prompt for reason when saving methods' activated. The 'Create new processing method' window appears. Then click on Link and process and the 'reasons for change' window will show up. After clicking on cancel the "Searching for methods" busy indicator appears. On a system with data back-end it can happen that Data Analysis gets unresponsive at that stage.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 02.
Keyword: Data Analysis
One-line Description:
HTML tags appear in the sample description
Problem:
In acquisition it is possible to enter multiple lines in the sample description. If the sample description has a break at the end of the description, a modification in Data Analysis afterwards can show up HTML tags for the line breaks in the sample description and on the report.
Temporary Solution:
Avoid line breaks in the sample description
Fix Information:
This issue is fixed in OpenLab CDS v2.6, OpenLab CDS v2.5 Update 5 and OpenLab CDS v2.4 Update 10. After installing OpenLab CDS v2.5 Update 5 or OpenLab CDS v2.4 Update 10, a manual action on existing data is needed. Affected results need to be loaded. Click into the sample description field to enter the edit mode. Afterwards leave the edit mode by clicking anywhere else. This will trigger a clean-up of the affected sample description. The result set needs to be saved afterwards.
Keyword: Data Analysis
One-line Description:
In-completed injection on migrated OpenLab CDS ChemStation data is not shown in the injection list
Problem:
After migrating incomplete results (incomplete due to an aborted sequence) from OpenLab CDS ChemStation into OpenLab CDS the in-completed injections are not shown in the injection tree.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Modification date of calibration standards gets changed to current time after import
Problem:
When importing a result set in Data Analysis the injection modification date of a calibration standard gets changed to the current time. This problem occurs only if following conditions are met: • The result set has samples with the sample type calibration standard. • The result set got processed in Data Analysis with a processing method containing a compound. • The Injection List window was not active during processing and saving of the result set.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.5 Update 4 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
No signal displayed while loading data when the system is in failover mode
Problem:
When the system is in failover mode and data gets acquired a review of this data might show "No Signal" for chromatograms in Data Analysis. This occurs only in combination with ECM 3.6.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.5 Update 4 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
Modification date of calibration standards gets changed to current time while loading a result in Data Analysis
Problem:
When loading a result set in Data Analysis the injection modification date of a calibration standard gets changed to the current time. This problem occurs only if following conditions are met: • The result set has samples with the sample type calibration standard. • The result set got processed in Data Analysis with a processing method containing a compound. • The Injection List window was not active during processing and saving of the result set.
Temporary Solution:
Temporary workarounds are: For review only: Close the Injection List window in Data Analysis before loading the result set. Do not display the injection list when the result set is loaded. Check the modification date in the sample information window. For reprocessing a result set: Load the data, activate the Injection List window and reprocess the result set.
Fix Information:
This issue is fixed in the following releases: OpenLab CDS v2.6 OpenLab CDS v2.5 Update 02 OpenLab CDS v2.4 Update 09
Keyword: Data Analysis
One-line Description:
Data export to AIA cannot be used for spectral analysis with 3rd party Software
Problem:
The AIA export plugin to netCDF files was introduced in OpenLab CDS v2.2. This functionality cannot be used to import data in 3rd party software to perform further spectral analysis. This export consists of a 2D chromatogram export for each injection signal and does not contain any spectral data. This export plugin was improved in OpenLab CDS v2.5, allowing users to import the related files to external Software such as AMDIS, MathWorks, or any other CDS supporting netCDF format (revision 3.4) import, according to AIA Chromatography Data Standard Specification V1.0.1.
Temporary Solution:
n/a
Fix Information:
This is fixed in OpenLab CDS v2.5.
Keyword: Data Analysis
One-line Description:
Weird diagonal line in MS spectrum extracted from LC/MS iQ profile data
Problem:
Extracted spectrum from profile data acquired using LC/MS iQ shows weird diagonal line (that looks like negative slope line).
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 02.
Keyword: Data Analysis
One-line Description:
RX files missing after sequence completed if physical printer is not configured
Problem:
If the processing method has "printer" selected to print injection report but no physical printer is configured, then RX files are missing in result set after the sequence completed. Injections without RX files cannot be viewed or reprocessed in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and in OpenLab CDS v2.5 Update 02.
Keyword: Data Analysis
One-line Description:
Click on "Select Project" in DA takes some time to show the projects
Problem:
Click on "Select Project" in DA takes some time to show the projects
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.5 Update 4 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
Mistranslation of "Norm amount(s)" and "Norm concentration(s)" in Chinese
Problem:
In the Chinese version of OpenLab CDS v2.5 the columns "Norm amount(s)" and "Norm concentration(s)" of the Data Injection Results table are incorrectly translated.
Temporary Solution:
n/a
Fix Information:
The issue is fixed from OpenLab CDS v2.5 Update 02 on.
Keyword: Data Analysis
One-line Description:
Cannot extract EICs if signal alignment (Use delay) is selected in processing method
Problem:
If the processing method has "Use delay" check box selected in General > Signals > Alignment tab, then error message "EIC Extractions - Invalid extraction parameters cannot extract EICs" occurs when reprocessing the data.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 03 and OpenLab CDS v2.6
Keyword: Data Analysis
One-line Description:
ChemStation single injections not displayed in Data Selection
Problem:
In OpenLab CDS v2.3 Update 11, ChemStation single injection files (sequence.acam_) are not showing in the Data Selection > Injection List.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.3 Update 12.
Keyword: Data Analysis
One-line Description:
Concentration and amount of the compound are not calculated if qualifier ratio fails
Problem:
In OpenLab CDS v2.5 and earlier, the Injection Results window does not show any value in the "Concentration" and "Amount" columns for compounds/peaks with "Fail" qualifier status.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 03.
Keyword: Data Analysis
One-line Description:
Qualifier RT not updated when compound RT is changed in Compound Table
Problem:
The retention time of the qualifier is not updated when the RT of target compound (quantifier) is changed in the Compound Table.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 04 and OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
System Suitability calculations are not performed when operating system language is Russian
Problem:
If the operating system language is Russian the system suitability values are not calculated in OpenLab CDS Data Analysis
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.5 Update 4 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
Can't load multiple calibration points if they have the same Data file name
Problem:
If a master method with an existing calibration curve gets linked to a new result set it might happen that not all calibration points of the new result set are available. This might be the case if the data file names of the existing calibration points are equal to the ones in the new result set.
Temporary Solution:
Use e.g. timestamp tokes to generate unique data file names.
Fix Information:
This issue is fixed in OpenLab CDS v2.6
Keyword: Data Analysis
One-line Description:
Qualifier RT not updated if "Assign Compound" is selected from peak in chromatogram
Problem:
If you right-click on peak in chromatogram and select "Assign Compound", the qualifier retention time is not updated in the Compound Table.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 04 and OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Click on turn custom scaling on/off will show an error
Problem:
As soon as the instrument traces are selected and button "turn custom scaling on/off" gets clicked Data Analysis will show an error.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.5 Update 4 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
User without "Save master method" privilege can modify and save the master method
Problem:
User who is not granted "Save master method" privilege can modify and save the master processing method by printing a report of a single injection result from Data Analysis > Reporting tab.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.4 Update 09.
Keyword: Data Analysis
One-line Description:
Order of custom parameter fields in the injection list is not saved.
Problem:
The column layout of the injection list in Data Analysis can be change per user. However, the position of the custom parameter fields is not saved. They always appear at the end of the table.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.6.
Keyword: Data Analysis
One-line Description:
Value for sample amount cannot be read from an exported AIA file
Problem:
When data gets exported with the AIA export function the value for sample amount cannot be retrieved on 3rd Party tools after an import of this AIA file.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS 2.5 Update 4 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
Data Analysis shows an error when changing run type or bracketing mode in the Injection List
Problem:
When a property of an injection of type "cal std" or the bracketing mode gets changed and a compound amount is set Data Analysis will show an error.
Temporary Solution:
A workaround is to create and link a new method to the result set. Afterwards bracketing mode, run type etc. can be changed. Then the original method can be linked again.
Fix Information:
This is fixed in OpenLab CDS 2.5 Update 4 and OpenLab CDS 2.6
Keyword: Data Analysis
One-line Description:
Modification date of calibration standards gets changed to current time while loading a result in Data Analysis
Problem:
When loading a result set in Data Analysis the injection modification date of a calibration standard gets changed to the current time. This problem occurs only if following conditions are met: • The result set has samples with the sample type calibration standard. • The result set got processed in Data Analysis with a processing method containing a compound. • The Injection List window was not active during processing and saving of the result set.
Temporary Solution:
Temporary workarounds are: For review only: Close the Injection List window in Data Analysis before loading the result set. Do not display the injection list when the result set is loaded. Check the modification date in the sample information window. For reprocessing a result set: Load the data, activate the Injection List window and reprocess the result set.
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 02.
Keyword: Data Analysis
One-line Description:
No MS peak purity result shown if "Identified peaks" is selected for MS peak calculation
Problem:
the "MS Purity" column in the Injection Results window does not show any value when "Calculate MS peak purity" is set to "Identified peaks".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Reprocessing large result sets might take some time
Problem:
If a result set with many injections gets reprocessed it can take more time than expected.
Temporary Solution:
n/a
Fix Information:
Reprocessing time for large result sets gets reduced with OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 4
Keyword: Data Analysis
One-line Description:
No m/z values shown in report generated from automated processing after acquisition run is done
Problem:
In Acquisition when running sequence/single sample analysis, if the specified processing method has "MS Base Peak m/z" annotation check box selected, the report generated automatically after the run completed does not show the m/z values.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.4 Update 09.
Keyword: Data Analysis
One-line Description:
Create new result set does not contain instrument traces
Problem:
Creating a new result set out of existing injection does not contain instrument traces.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Data Analysis
One-line Description:
Re-quantification of a single injection in a large result set takes longer as expected
Problem:
In a large result set a re-quantification of a single injection can take more time as expected.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 5
Keyword: Data Analysis
One-line Description:
Relative Retention Time (RRT) is not calculated for peaks with no compound assignment
Problem:
The relative retention time is not calculated/reported when an assigned peak gets un-assigned.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.6.
Keyword: Data Analysis
One-line Description:
Calibration level values are erased if the number of levels gets changed to 10.
Problem:
Changing the number of calibration levels to 10 will erase the values existing values entered for different levels.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Processing method last modified date
Problem:
It may happen that the Modified at timestamp in Processing Method Info is different from the one displayed in the Sample Information. This might also affect the last modification dates appearing on a report under "last modification date" and what is shown in the method information reporting printout and the audit trail. Both time stamps may deviate in case a master method was linked to other result set(s) after the last modification or if the processing method got modified and saved, but the result set got closed without saving. Opening the result set again and doing a re-process will lead to a mismatch of the timestamps.
Temporary Solution:
Use method versioning to insure results are reprocessed with the processing methods defined in the standard operating procedure.
Fix Information:
This issue is fixed in OpenLab CDS v2.6, OpenLab CDS v2.5 Update 7, and OpenLab CDS v2.4 Update 11.
Keyword: Data Analysis
One-line Description:
Not all ions are extracted after performing "Reprocess All" on GC/MS CI SIM data acquired in 2 time segments
Problem:
GC/MS CI SIM data has 23 injections acquired in two time segments, each with 2 SIM ions (total 4 SIM ions). Four SIM ions are manually extracted for one of the injections and then added as compounds to the Compound Table so that there are 4 EICs and 4 compounds. After performing "Reprocess All", the other 22 injections only have 2 EICs, not 4 EICs.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
"Add/Update MS compounds" not working for GC/MS CI SIM data
Problem:
Cannot perform "Add/Update MS compounds" on GC/MS data acquired in CI SIM mode. Data Analysis shows "Add/Update MS compounds completed" status wheel but the Compound Table remains empty (i.e., no compounds were added or updated).
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Incorrect retention time after manual integration
Problem:
Modifying the baseline with manual integration on a signal with a drift could cause a incorrect retention time of the peak while using the EZChrom integrator. The retention time is not calculated at the peak apex.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Injection modification date changed after "Print All" reports
Problem:
Print all reports on a saved result set will change the modification date of an injection. Closing and reopening the result set will show the modification date how it was before printing all reports.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
"Error loading data: ...sequence.acaml: Object reference not set to an instance of an object"
Problem:
Data acquired in OpenLab ChemStation A or B can be loaded in OpenLab CDS 2.x after using SequenceAcamlGenerator to generate OpenLab CDS compatible acaml file. However, the following error occurs when trying to load the data in OpenLab CDS v2.5: "Error loading data: ...sequence.acaml: Object reference not set to an instance of an object" This issue does not occur in OpenLab CDS v2.4 and earlier.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 07.
Keyword: Data Analysis
One-line Description:
Result set audit trail contains only for closing bracket an entry for processing
Problem:
In case a sequence with bracketing calibration gets acquired and processed only the last injection will show an entry for successful processing in the injection and result set audit trail.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6
Keyword: Data Analysis
One-line Description:
View E-Signatures will throw an unexpected error
Problem:
Viewing the e-signatures of a signed result set which contains an injection without a signal e.g. a shutdown run will throw an unexpected error in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Data Analysis
One-line Description:
Loading large result sets might take some time
Problem:
If a result set with many injections is loaded, it might take more time than expected.
Temporary Solution:
n/a
Fix Information:
Loading time for large result sets is reduced with OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 7.
Keyword: Data Analysis
One-line Description:
DA terminates with error "System.Xml.XmlException: Root element is missing"
Problem:
Unexpected error "System.Xml.XmlException: Root element is missing" occurs when loading result set in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6, OpenLab CDS v2.5 Update 07 and OpenLab CDS v2.4 Update 11.
Keyword: Data Analysis
One-line Description:
Fields import from NIST libraries
Problem:
In OpenLab CDS v2.x, the following information are retrieved from the NIST library when performing unattended or manual library searching: - Compound name - Match score - Reverse match score - Probability - Library name - CAS number - NIST # - Library ID Other field, such as comments saved with the NIST spectra are currently not available in Data Analysis or when generating a NIST library search report.
Temporary Solution:
Information, can be saved in a constant file, and reported using a custom calculation.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Arbitrary spectrum library search results cannot be reported
Problem:
In OpenLab CDS v2.x, only automated library search results can be reported. Arbitrary spectrum library search results cannot be reported.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
EZChrom integrator may suppress rider peak's baseline
Problem:
The usage of "tangent skim" integration events along with "minimum area" may lead to the following artefact when using the EZChrom integrator option: If the peak area of a rider peak is smaller than the minimum peak area set in the EZChrom integrator settings, the rider peak annotation, rider peak baseline and rider peak integration results are removed from the signal display and the injection result table, respectively. The suppression of the rider peak's baseline lead to the false impression that the area of the rider peak contributes to the reported peak area of the parent peak. However, the integration results of tangent skimmed parent peak are not changed by filtering smaller rider peaks.
Temporary Solution:
If the tangent peak skimming should be overruled by intention and the rider peak area should be explicitly added to the parent's peak area, the manual peak deletion should be utilized.
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Data Analysis
One-line Description:
Signal to noise calculation could not be computed for the GC front signals using EP
Problem:
If a result set got acquired with a GC using dual injection, S/N is only calculated for the signals of the back injection, when using EP.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 01, OpenLab CDS v2.5 Update 09, OpenLab CDS v2.4 Update 11 and OpenLab CDS v2.3 Update 13.
Keyword: Data Analysis
One-line Description:
Tooltip for "Extract spectra from integrated peaks on reprocessing" checkbox not localized in Chinese
Problem:
In Chinese version of CDS v2.6, the tooltip for "Extract spectra from integrated peaks on reprocessing" checkbox under "Automatic spectrum extraction" is not displaying the Chinese localized text for "When selecting this option, data file processing will take longer".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
Manual Integration Undo Button does not work for all steps
Problem:
In case, manual integration was performed on a non-integrated signal with no peaks, it might be the undo function will not work on the last step. All other steps can be undone.
Temporary Solution:
Workaround: Use "Reprocess - Clear corrections" - that is available either per context menu on the injection tree, or via the reprocess button.
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01
Keyword: Data Analysis
One-line Description:
OpenLab CDS v2.6 crashes after deselecting signals from imported MassHunter data
Problem:
GC/MS data acquired in MassHunter is imported to OpenLab CDS v2.6. When the user deselects a signal in the injection, OpenLab CDS v2.6 Data Analysis crashes.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
In "all spectrum same scale" display mode, threshold is removed after reprocessing
Problem:
In "all spectrum same scale" display mode, threshold is removed after reprocessing in OpenLab CDS v2.6.0.841.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
Varying threshold limits with "all spectrum same scale (per pane)"
Problem:
Threshold can be manually adjusted past 100 on a spectrum with lower abundance and blocked before reaching 100 on a spectrum with higher abundance.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 Update 02 Fixed in OpenLab CDS v2.7
Keyword: Data Analysis
One-line Description:
Chromatogram extraction error after processing data
Problem:
If a result set with a linked processing method is loaded and reference chromatograms from an unlinked result set/single run are added to this processing method, it might happen, that a chromatogram extraction error occurs while reprocessing.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
Data Analysis crashes in OpenLab CDS v2.5 when opening Extract Chromatogram dialog for LCMS multimode data
Problem:
Data Analysis crashes in OpenLab CDS v2.5 when opening Extract Chromatogram dialog for LCMS multimode data.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.6 Update 02 and OpenLab CDS v2.7.
Keyword: Data Analysis
One-line Description:
Data Analysis stops working when loading recovered result set containing fraction collection data
Problem:
If a sequence could not be finalized due to unexpected issues, a recovery mechanism will recover the already acquired data. If the data contains faction collection data, it might be that DA stops working with an unexpected error.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01
Keyword: Data Analysis
One-line Description:
No MS peak purity computed if compound is missing or group is defined in the method
Problem:
MS peak purity is not computed if compound is missing or group is defined in the method.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
DA API is not working on a workstation plus
Problem:
It is not possible to use the DA API on a workstation plus installation.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.5 Update 08 and OpenLab CDS v2.6 Update 02
Keyword: Data Analysis
One-line Description:
Removal of MS reference spectrum for compound is not logged in the audit trail
Problem:
When you remove the MS reference spectrum for compound, the audit trail does not show that reference compound is removed.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
Misleading processing method version in the result set audit trail
Problem:
It might happen, that in a result set audit trail a processing method version is mentioned which cannot be found in the content management. This can occur if a linked processing method got modified and the result set got reprocessed without saving the modified processing method. A preliminary version of the processing method will be tracked in the result set audit trail. If a new method gets linked afterwards to this result set and saved after reprocessing, the result set audit trail will show an entry about the processing with the previously linked, modified, and unsaved processing method. Since the modified processing method was not saved, you will not find this version of the previously linked method in your content management.
Temporary Solution:
Save the changes of your linked processing method before you link a new method to the result set.
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Data Analysis
One-line Description:
Error with peak details window when selecting a compound with an undetected qualifier
Problem:
Under certain conditions, selecting a compound with an undetected qualifier and showing the peak details window can cause the application to crash.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Data Analysis
One-line Description:
Loading single injection runs shows error "Unable to change selection. The given key was not present in the dictionary"
Problem:
On system with OpenLab ECM 3.6 as storage backend the error "Unable to change selection. The given key was not present in the dictionary" is shown when trying to load single injection runs in data analysis. This is caused by an invalid single injection result set file (*.sirslt.ssizip) in the projects results folder. Possible causes for invalid files can be - Delete a pending single injection run in run queue, Using the Abort function does not cause file corruption - Manual upload of a file with the name *.sirslt.ssizip
Temporary Solution:
Remove manually moved files or empty .sirslt.ssizip files
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 10.
Keyword: Data Analysis
One-line Description:
Signal not found when processing a result set even though signal exists
Problem:
For MS data it might happen that a signal is not found when processing a result set even though the signal exists.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS 2.6 Update 02
Keyword: Data Analysis
One-line Description:
MS EICs not showing same decimal places in injection tree and chromatograms as in CDS v2.5 and earlier
Problem:
In OpenLab CDS v2.6.0.841, MS EIC signal names are not showing the same decimal places in the injection tree and chromatograms as in the previous versions. As a consequence, the processing methods created in CDS v2.5 and earlier do not work in CDS v2.6 due to mismatch in decimal places.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 Update 01. The processing methods created in CDS v2.5 and earlier should work in CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
Specific integration events defined on extracted signal may not be applied in OpenLab CDS v2.6
Problem:
Specific integration events defined on extracted signal may not be applied in OpenLab CDS v2.6
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 Update 02
Keyword: Data Analysis
One-line Description:
Reports defined to be printed on specific signals are not printed in OpenLab CDS v2.6
Problem:
Reports defined to be printed on specific signals are not printed in OpenLab CDS v2.6
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 Update 02
Keyword: Data Analysis
One-line Description:
Duplicate Integration Optimizer icon in layout section of the home tab
Problem:
In case, the Integration Optimizer Add-On for OpenLab CDS v2.5 did not get uninstalled before upgrading to OpenLab CDS v2.6, the icon for Integration Optimizer will show up twice in the layout section of the Home tab.
Temporary Solution:
n/a
Fix Information:
To remove the second icon for the Integration Optimizer, delete the file AutoIntegrationExtension.xml in the folder C:\Program Files (x86)\Agilent Technologies\OpenLab Data Analysis\Bin\Layouts\default.workspace.extensions
Keyword: Data Analysis
One-line Description:
Signal names are not displayed correctly in OpenLab Data Analysis for localized EZChrom methods.
Problem:
Signal names are not displayed correctly in OpenLab Data Analysis for localized EZChrom methods.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
Chinese characters in ANSI Custom Calculator constants file causes issues
Problem:
On an Englsh system, writing Chinese characters in an ANSI Custom Calculator constant file will cause issues.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 05.
Keyword: Data Analysis
One-line Description:
Inconsistency on the 8th signal name
Problem:
Creating a new method in OpenLab CDS based on a method which contains 8 signals in EZChrom A.04.10 might show an inconsistency on the signal name.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 02
Keyword: Data Analysis
One-line Description:
"Removed MS reference spectrum for compound..." is not translated in method audit trail.
Problem:
On a Japanese system, "Removed MS reference spectrum for compound..." is not translated in method audit trail.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 05.
Keyword: Data Analysis
One-line Description:
MS Signals missing for Single Sample Sequence
Problem:
When acquiring a single sample with MS data as a sequence which is automatically done when remotely acquiring single samples, the injection object does not contain the MS signals in the Signals property.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01
Keyword: Data Analysis
One-line Description:
MS EICs not showing same decimal places in injection tree and chromatograms as in CDS v2.5 and earlier
Problem:
In OpenLab CDS v2.6.0.841, MS EIC signal names are not showing the same decimal places in the injection tree and chromatograms as in the previous versions. As a consequence, the processing methods created in CDS v2.5 and earlier do not work in CDS v2.6 due to mismatch in decimal places.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 01. The processing methods created in CDS v2.5 and earlier should work in CDS v2.6 Update 01.
Keyword: Data Analysis
One-line Description:
Instrument traces are compressed in overlay mode
Problem:
Instrument traces are compressed in overlay mode compared to the chromatogram. This can be observed on imported data from ChemStation.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Data Analysis
One-line Description:
Error occurs if a DA API loaded result set gets unloaded
Problem:
Load two results sets with the same name from different projects into the Data Analysis via DA API. If one of the result sets gets closed, an unexpected error occurs.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 05.
Keyword: Data Analysis
One-line Description:
Task Manager shows > 4GB memory consumption for Agilent.OpenLab.DataAnalysis.exe
Problem:
After loading an injection with more than 2 signals, DA consumes 4GB of RAM.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 08.
Keyword: Data Analysis
One-line Description:
Snapshot did not close after 30 minutes.
Problem:
During acquisition, a snapshot was taken of the current run. Even if the snapshot got closed, the sequence could not be finished. Looks like the snapshot did not close after 30 minutes. This can be caused by an LDAP error.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Data Analysis
One-line Description:
2DLC: performance issue related to manual integration
Problem:
Working with manual integration on a 2DLC signal might have performance issues.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 02
Keyword: Data Analysis
One-line Description:
Only 2 digits for sample amount on an AIA export
Problem:
Number of digits in sample amount with AIA export changed from 4 digits to 2 digits.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 05, and OpenLab CDS 2.5 Update 11.
Keyword: Data Analysis
One-line Description:
Data Analysis hangs when RT Update setting is used
Problem:
When setting the RT update setting to After Each Run and reprocessing, the reprocessing stalls on the first injection and never completes. Data Analysis must be terminated from the Task Manager.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS 2.6 Update 5.
Keyword: Data Analysis
One-line Description:
Adjustment of MS peak threshold causes lockup or crash
Problem:
When adjusting peak threshold in extracted MS spectra, deselecting a spectrum can cause application to crash. Also, when adjusting the threshold using the threshold line within the spectral window, sometimes the line jumps to the bottom of the window and can no longer be moved.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS 2.6 Update 11.
Keyword: Data Analysis
One-line Description:
Data Analysis not able to load all MS SIM signals imported from ChemStation
Problem:
When loading MS data imported from ChemStation, DA is not able to display all MS SIM signals.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 05, OpenLab CDS v2.5 Update 09 and OpenLab CDS v2.4 Update 11.
Keyword: Data Analysis
One-line Description:
Qualifier Signal Name updates during reprocessing causing Qualifier Status to fail
Problem:
Upon reprocessing a data set, the signal name for the Qualifier is updated if the retention time has changed. The Qualifier Status may then Fail, because the signal name in the processing method does not match that of the extracted chromatogram so the Qualifier is marked as Not Found.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS 2.6 Update 5.
Keyword: Data Analysis
One-line Description:
Not enough quota
Problem:
It might happen, an unexpected error "not enough quota is available to process this command" is shown when working in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Data Analysis
One-line Description:
Empty injection results table and chromatogram graphs with no integrated peaks upon loading a saved result set
Problem:
For some MS data, after saving the processed results, where there were results in the injection results table and the chromatogram graph peaks were integrated, closing the data, then reloading the same results data, there are no peaks in the Injection Results table and the chromatogram graph peaks are not integrated.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 11.
Keyword: Data Analysis
One-line Description:
Custom calculator results not being calculated
Problem:
Custom Calculator results are not being calculated for if the injection source is set to No Injection/Instrument Blank.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Data Analysis
One-line Description:
Sample custom fields are "linked" after a new result set is created
Problem:
When a new result set is created and the original result set is not closed, the sample custom field values of the two result sets are linked. Changes done in one result set are also done in the other result set.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS v2.6 Update 07, and OpenLab CDS 2.5 Update 11.
Keyword: Data Analysis
One-line Description:
One of the acquired data is missing from result injection list
Problem:
Due to a timing issue during "Review Completed Injections", one of the acquired injection may not be successfully registered to the result injection list. Hence, when the result set is loaded in Data Analysis, that particular injection is missing from the injection list.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Data Analysis
One-line Description:
Loading context menu in signal plot window in Data Analysis leads to an unexpected error
Problem:
Loading the context menu in signal plot window in Data Analysis will lead to an unexpected error.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 05.
Keyword: Data Analysis
One-line Description:
When loading GCMS or LCMS data from CDS version 2.1 into later versions of CDS Data Analysis, adding a compound from a peak in the TIC to the compound table does not function as expected.
Problem:
When loading GCMS or LCMS data which was acquired and processed in CDS version 2.1 into later versions of CDS Data Analysis, adding a compound from a peak in the TIC to the compound table does not function as expected. Two identical TIC signals are displayed in the navigation tree, the first named like "MS1Front" and the second named like "MS1Front TIC EI". Compounds can only be added from the second signal with "TIC" in the signal name. Compounds cannot be added from the first signal which does not have "TIC" in the signal name. However, even when using the second signal with "TIC" in the signal name, adding a compound by right-clicking a peak in the TIC and selecting "Add peak as compound to method", changing the signal of the newly added compound to the associated EIC signal, then reprocessing the sample will result in the signal for that compound reverting back to the TIC signal in the compound table.
Temporary Solution:
For the issue where peaks cannot be added from the first signal without "TIC" in the signal name, the workaround is to use the second signal with "TIC" in the signal name.
Fix Information:
Signal switching upon reprocessing issue is resolved in OpenLab CDS 2.7.
Keyword: Data Analysis
One-line Description:
Issue while using the IProcessingMethod interface
Problem:
Working with OpenLab SDK, to check which compounds are defined in a "3D UV Quantitive" method, using the IProcessingMethod interface might cause issues if the upper wavelength is not set in the UV Impurity check tab.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Data Analysis
One-line Description:
Snapshot cannot be launched
Problem:
Snapshot cannot be launched. An error "could not open DA. Please confirm Agilent OpenLab Data Analysis Application Service is running." appears.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Data Analysis
One-line Description:
Random sorting of injections in Audi Trail sorted by descending Date
Problem:
If the Audit Trail in OpenLab CDS 2.x get sorted by Date in descending order, some injections appear to be randomly sorted. Since some events are submitted simultaneously in blocks, their time step do not differ even on the millisecond time scale. This can lead to the impression of a random sorting.
Temporary Solution:
A workaround is to set the sorting of the time column to descending. Afterwards, the Injection column can be selected while pressing the shift key. This leads to a double sorting. While pressing the shift key, the sorting of the Injection can be set to descending as well. This workaround cannot be used for sorting the the Audit Trail of the PDF Export. The built-in report template used generating the audit trail report uses a defined and fix sorting order.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Post processing plugin output export fails for FQDN path
Problem:
The post-processing plugin output path will not accept a network path if it has a "." in it, like in \\serv.domain.com\export.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Data Analysis
One-line Description:
Warning message "Cannot load methods (not found)" after loading a result set
Problem:
Importing a result set creates version 1. After re-processing and signing, the result set version will be 2. Opening result set version 1 afterwards will display a warning "Cannot load methods (not found)". This is not the case for OpenLab CDS 2.x Workstation File Systems.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Data Analysis
One-line Description:
Negative value for tailing factor
Problem:
In some cases, the tailing factor might be negative. Typically, if the peak is not well resolved. After the peak data processing, it can happen that the corrected retention time of the peak apex is before the peak start time, the front width will be negative. This results in a negative value for the tailing factor.
Temporary Solution:
To avoid such a situation, make sure the peaks are well resolved.
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 04.
Keyword: Data Analysis
One-line Description:
RRT is not taken into account for compound identification
Problem:
If 'use time reference compound' and 'use RRT reference compounds' is selected in the processing method, the compound identification windows will be corrected only by the shift of the time reference compound. The relative retention time (RRT) value is not taken into account to adjust the compound identification window.
Temporary Solution:
As a workaround, the factors of the compounds can be set to the values of the relative retention times (RRT).
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
E-signatures and audit trail information are lost after second signing
Problem:
After User A has signed a result set, User B is signing this result set as well. It might happen that the signature and the audit trail entry of User A is missing afterwards. This can occur if the result set is still in the upload queue while User B is signing the result set.
Temporary Solution:
To avoid this situation, set "enforce signature order" and assign both users to different levels.
Fix Information:
This issue will be fixed in a future release.
Keyword: Data Analysis
One-line Description:
Report will not be created if report filename starts or ends with a whitespace
Problem:
If the report filename is defined with a starting or ending whitespace in processing method, the report file will not be generated.
Temporary Solution:
Avoid leading or ending white spaces for the report file name. If working with tokens e.g. sample name, make sure the sample name has no white space in the beginning or in the end of the name. Alternatively, a report file name structure like: Prefix-<token>-Suffix can be used.
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Data Analysis
One-line Description:
Error occurred while importing GC7890 EZChrom dual tower method in OpenLab CDS 2.7
Problem:
Importing a GC7890 dual tower method from EZChrom into OpenLab CDS 2.7 can lead to an error if some peaks got unchecked in the EZChrom method.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Data Analysis
One-line Description:
Data Analysis is not responding after previewing report
Problem:
It might happen that Data Analysis is not responding after previewing report.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
EZChrom method with history points for log amount ‘0’ or less than zero is not imported
Problem:
If in EZchrom the levels amount is set to ‘1’ with scaling as log(amt)& log(resp), history points are not imported into OpenLab CDS for level 1 where amount was set as ‘1’. The same is true if log amount is negative.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
Cannot select all spectra when multiple spectra are extracted from one peak
Problem:
When multiple MS spectra are extracted within one chromatographic peak after Add/Update MS Compounds has been run, only one of the spectra can be selected.
Temporary Solution:
Option 1: if multiple manually extracted spectra are needed from within one peak, do not run Add/Update MS Compounds Option 2: delete the unneeded spectra so that only one spectrum is present in each chromatographic peak Option 3: manually split the peak integration so that each spectrum is present in its own peak
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Data Analysis
One-line Description:
Unable to add qualifiers from MS spectrum in some circumstances
Problem:
Adding qualifiers by right-clicking ions in a spectrum only works if the signal for the target compound has already been extracted.
Temporary Solution:
Option 1: use the TIC (which is extracted automatically when the sample is loaded) as your compound signal type Option 2: reprocess the injection after adding the target compound but before adding qualifiers, which will extract the necessary EIC Option 3: add qualifiers from extracted EICs, rather than from the spectrum
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Data Analysis
One-line Description:
Memory leak on Signal Transformation View
Problem:
Memory leak on Signal Transformation View.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 01 and OpenLab CDS v2.6 Update 08.
Keyword: Data Analysis
One-line Description:
Missing MS channels in new results sets
Problem:
When a new results set has been created from existing data in Data Analysis, the MS TIC signal is missing on all but the first injection in the new results set.
Temporary Solution:
There is no known workaround.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Data Analysis
One-line Description:
Integration Events from EZChrom method are not imported on the correct signal name in OpenLab CDS
Problem:
Integration Events from EZChrom method are not imported on the correct signal name in OpenLab CDS.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Data Analysis
One-line Description:
Reviewing or adding a manual entry to the audit trail no longer triggers a new result version
Problem:
The release notes state the following: “Reviewing or adding a manual entry to the audit trail no longer triggers a new result version” This statement is incorrect.
Temporary Solution:
The correct statement is: “For methods and cc files, reviewing or adding a manual entry to the audit trail no longer triggers a new version”
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Option to Save results is missing in "Cannot print reports" dialog for single samples
Problem:
A report of a single sample gets previewed in the Reporting section. If this preview should be printed and the results are not saved yet, a warning “Cannot print reports” shows up. There is no “yes, save” button because of missing saving rights.
Temporary Solution:
Option 1: Assign "save master method" privilege to the role. Option 2 (if option 1 is not possible): Save single sample results before generating a report.
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02, and OpenLab CDS v2.6 Update 08.
Keyword: Data Analysis
One-line Description:
Adding peak as compound from TIC scan leads to an unexpected error
Problem:
Extracting mass spectral data from damaged data files can cause Data Analysis to crash. For data sets which have become corrupted or damaged, and expected mass spectral data is missing, trying to extract EICs or spectra or add an MS compound to the method can cause Data Analysis to crash.
Temporary Solution:
No known workaround.
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 03, and OpenLab CDS v2.6 Update 13.
Keyword: Data Analysis
One-line Description:
Data Analysis does not get initialized
Problem:
Data Analysis does not get initialized.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Qualifier ratio may not be calculated as expected when adding MS qualifiers to a method
Problem:
When adding a qualifier to the processing method from a specific injection, the calculated qualifier RSP% may not match the qualifier RSP% which is calculated upon reprocessing that injection under certain conditions. In some circumstances, particularly when the EIC RT extraction window is very narrow and the peak is wide, or if the peak is small and jagged and smoothing is enabled, the mismatch may be significant enough that when processing the injection the qualifier was added from with no changes after adding it, the qualifier RSP% fails.
Temporary Solution:
Qualifier RSP% may be updated manually in the processing method. The issue may be less pronounced if an EIC RT extraction window is not used (set to 0.0).
Fix Information:
Issue is resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
EIC extraction window is not calculated correctly when signal alignment is applied
Problem:
When a processing method is configured with both signal alignment enabled and a non-zero EIC extraction window, the signal alignment correction is applied twice. This leads to EIC extraction windows in which the peak of interest is not centered. In the case of large signal delays and/or small EIC extraction windows, the window may be shifted so far that the peak of interest is partially or completely outside the window. There are also instances where Data Analysis can crash when signal alignment and EIC extraction windows are used, and the extraction window extends below zero.
Temporary Solution:
Widen or disable EIC extraction windows.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Data Analysis
One-line Description:
Sample amount in AIA export of EZChrom data is 1.00
Problem:
In case of AIA export of EZChrom data loaded in OpenLab CDS 2.x, the sample amount in the CDF file is set to 1.00. Even if the injection list in Data Analysis contains a different sample amount value.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLAb CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Smoothed qualifier EICs can unsmooth themselves unexpectedly
Problem:
Under certain conditions, a smoothed qualifier EIC can unsmooth itself after reprocessing, while retaining the [s] annotation indicating it is still smoothed. One way to trigger this are to add a target to the compound table while smoothing is turned off, then enable smoothing, then add a qualifier to that target and reprocess.
Temporary Solution:
Add targets and qualifiers to the compound table while using the same settings for smoothing.
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
"inconsistent between result and parameter" warning after using scaling in report settings
Problem:
If the scaling is set in the processing method on the injection report section, it might be that the data gets flagged as "inconsistent between result and parameter" after loading.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Data Analysis
One-line Description:
MS Chromatogram Smoothing does not use EIC extraction window setpoint
Problem:
When MS Chromatogram Smoothing is enabled, any setting for the EIC extraction window is not used.
Temporary Solution:
n/a
Fix Information:
The software is updated so that the EIC extraction window setting is utilized when working with smoothed MS chromatograms. If this behavior is not desired once the update has been applied, change the EIC extraction window setting to 0. This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Data Analysis
One-line Description:
Toggling smoothing on and off may result in compounds no longer linked to extracted signals
Problem:
When turning smoothing off and on, it is possible to end up with compounds which are defined on EIC signals (target and/or qualifiers) which are no longer associated with any extracted EICs. Results for these compounds can no longer be calculated until the signal linkage is fixed, typically be deleting and readding the compound and/or qualifier(s).
Temporary Solution:
Configure smoothing before adding MS compounds or qualifiers to the compound table.
Fix Information:
This issue is resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
Manual integration options are not visible
Problem:
After launching Data Analysis, the manual integration options are not visible after activating manual integration.
Temporary Solution:
The manual integration needs to be de- and re-activated.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Data Analysis
One-line Description:
Qualifier retention time shift is incorrect if retention time update is set to after each run
Problem:
Qualifier retention time shift is incorrect if retention time update is set to after each run. The qualifier retention time does not get shifted in the same direction as the compound retention time.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Scaling settings in processing method are editable even if custom scaling is active
Problem:
If custom scaling is set in the Chromatogram Window settings, and a new processing method gets created, or an existing method gets loaded, the scaling settings in the processing method signal tab are editable. The values can be changed without any effect.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Data Analysis
One-line Description:
Unable to do manual integration in first signal from Waters Acquity PDA
Problem:
In case two signals are acquired on a Waters Acquity PDA, it is not possible to perform manual integration on the first signal.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Data Analysis
One-line Description:
Use of EIC extraction windows with SIM data can cause qualifier RSP% to not be calculated and DA to crash in certain cases
Problem:
For SIM data, if an EIC extraction window is enabled, and the retention time of the peak in the target SIM is different from the retention time of the peak in the qualifier SIM (rounded to two decimal places), the qualifier RSP% will not be calculated when the qualifier is added to the method. Upon reprocessing, the results for that qualifier will not populate and it will be flagged as failing. If the peak details window is opened, data analysis will crash.
Temporary Solution:
Do not use EIC extraction windows (set it to 0 in the processing method) on SIM data.
Fix Information:
This issue is resolved in OpenLab CDS v2.8, CDS 2.7 Update 02 and CDS 2.6 Update 07.
Keyword: Data Analysis
One-line Description:
Qualifier may be assigned to wrong compound
Problem:
When assigning a qualifier, if multiple MS compounds exist in the compound table, the software will display a dialog asking which compound the qualifier should be added to. However, if multiple MS compounds have the same retention time, the qualifier may not be added to the compound the user selects, but may instead be added to another compound with the same retention time.
Temporary Solution:
Set the retention times of the compounds to be slightly different from one another before assigning qualifiers.
Fix Information:
The issue is resolved in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Data Analysis
One-line Description:
Unexpected error occurs after deselecting a history point
Problem:
If a result set from EZChrom with no method linked gets opened and a EZChrom calibration method gets linked to only one injection of the result set, deselecting any history point will lead to an unexpected error.
Temporary Solution:
Link the method to more than only one injection of the result set.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Data Analysis
One-line Description:
"Is time ref." and "Is RRT ref." columns are not displayed in processing method
Problem:
If a user has hidden "Is time ref." and "Is RRT ref." columns in OpenLab CDS 2.4 and save the processing method, the column is saved as hidden inside the processing method. If such a method gets loaded in OpenLab CDS 2.7 the column is no longer available in the column chooser and cannot be displayed again.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Unexpected error after reprocessing a result set with timed / named groups
Problem:
In case an injection of a result set has no signal, and timed or named groups are defined in the linked processing method, reprocessing leads to an unexpected error.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
SIM data may calculate qualifier ratio incorrectly when signal is changed to TIC SIM
Problem:
For existing compounds on MS SIM data, if the signal is changed to TIC SIM and the data is reprocessed, the qualifier RSP% calculates using the TIC SIM peak as the denominator (instead of a peak from the largest SIM ion in that TIC SIM peak).
Temporary Solution:
n/a
Fix Information:
Issue is resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
Changes are discarded after closing and saving a result set
Problem:
In case a result set with a modified, unsaved processing method gets closed, and the dialogue box is closed with "save and close" the method modification might get discarded.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab cDS v2.7 Update 03.
Keyword: Data Analysis
One-line Description:
Method not found when loading first version of a result set
Problem:
When trying to load an early version of a result set, where changes to the processing method were done in review mode during acquisition, the early method version is not found.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Changing signal from EIC to TIC causes qualifier ratios not to be calculated
Problem:
For MS Scan data, if the signal of an existing compound is changed from an EIC to a TIC, and the data is reprocessed, the qualifier RSP% for that compound will not be calculated.
Temporary Solution:
If the signal must be changed, delete the compound and re-add it by right clicking a TIC peak and choosing Add peak as compound to method. Re-add any qualifiers to this new compound.
Fix Information:
Issue is resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
ASR (Analytical Studio Reviewer) export file not being written correctly
Problem:
A number of issues with ASR file generation were addressed: 1. Peaks were marked confirmed/green if they were listed in the compound table, not if their sample purity score was above the threshold 2. Errors could be thrown by ASR when opening ASR exports for data processed under certain conditions 3. Profile data was not be identified correctly in ASR export files 4. Losses and aggregates were not being processed correctly in ASR export files 5. Issues with dual polarity data when generating ASR export files
Temporary Solution:
n/a
Fix Information:
The issue is resolved in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 04 and OpenLab CDS v2.6 Update 11.
Keyword: Data Analysis
One-line Description:
Manually extracted spectra within an integrated peak can erroneously become the linked display spectrum
Problem:
If automatic spectrum extraction is enabled or automatically search TIC peaks (in an MS library) is enabled, a mass spectrum will be extracted automatically from each integrated chromatographic peak. When clicking that peak in the chromatogram window, the automatically extracted spectrum is expected to be displayed (focused) in the MS Spectrum window. However, if another spectrum is manually extracted which also falls within that integrated peak, under certain conditions this spectrum may be the one displayed (focused) when selecting that peak.
Temporary Solution:
Select the spectrum of interest directly from the navigation tree, rather than by clicking the chromatographic peak.
Fix Information:
This is resolved in OpenLab CDS v2.8, OpenLAB CDS v2.7 Update 03 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Adding compounds to method from SIM data when signal alignment is enabled can cause Data Analysis to crash
Problem:
Adding a compound to the compound table from SIM data while signal alignment is enabled can cause Data Analysis to crash under certain conditions.
Temporary Solution:
Do not use signal alignment with SIM data.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Data Analysis
One-line Description:
EIC changes depending on the selected number of compounds
Problem:
Extracted Ion Chromatogram (EIC) changes depending on the selected number of compounds. As a consequence, areas and quantitative results also change. Agilent Engineering has identified the root cause as variation in whether or not the data points at the end points of the spectral range are included. When a different number of compounds is selected, this can change. As a result, the EIC and peak areas change. The amount of change depends on the number of data points in the spectrum and the intensity at the end points. This problem occurs in the mass spectrometry data analysis in the OpenLab CDS software. This is not an issue with the acquired data from the mass spectrometer. This does not occur when extracting wavelength chromatograms from UV photodiode array data.
Temporary Solution:
Users can avoid this issue by maintaining the same number of compounds in their data analysis method for both standards and unknown samples.
Fix Information:
This issue got resolved in OpenLab CDS v2.8. Agilent Engineering has developed a fix for this issue and that is released as a point patch for OpenLab CDS 2.6 and OpenLab CDS 2.7. This fix addresses the cases where the end points of the spectral extraction window are multiples of the profile scan step size. This point patch is available upon request.
Keyword: Data Analysis
One-line Description:
Loss of MS spectral granularity when sending to or retrieving from a library
Problem:
When sending an MS spectrum to NIST MS Search or retrieving an MS spectrum from a search library, the spectrum is being flattened to integers for m/z values and relative abundance values. This can cause loss of spectral detail, particularly for low intensity ions. Spectra are also being flattened in the same manner when converting a .L library to NIST format using the Lib2NIST conversion tool from NIST20 and prior.
Temporary Solution:
N/A
Fix Information:
This issue got resolved in OpenLab CDS v2.8. It is also addressed in point patches for CDS v2,6 and CDS v2.7 - available upon request. The library conversion issue is addressed in the NIST23 release of the Lib2NIST conversion tool.
Keyword: Data Analysis
One-line Description:
Blank subtraction 1D and 2D do not work together.
Problem:
Blank subtraction 1D and 2D do not work together.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Data Analysis
One-line Description:
X-axis of Max Wavelength Chromatogram is updated erroneously updated when ASR plug in is enabled
Problem:
When a result with a Max Wavelength Chromatogram is reprocessed using a processing method with the ASR post-processing plug in enabled, the x-axis of the Max Wavelength Chromatogram is updated to incorrect values.
Temporary Solution:
Disable ASR plug in when using Max Wavelength Chromatograms.
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 03 and OpenLab CDS v2.6 Update 10.
Keyword: Data Analysis
One-line Description:
EICs not automatically extracted when chemical formulas are entered as targets
Problem:
When an MS flavor method is used, and molecular weight(s) are entered into the target fields in the sequence/injection list, extracted ion chromatograms (EICs) are automatically extracted for each target. However, when chemical formulas are entered into these fields, EICs are not automatically extracted.
Temporary Solution:
Enter molecular weights instead of chemical formulas into the target fields.
Fix Information:
This issue is resolve in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 06 and OpenLab CDS v2.6 Update 11.
Keyword: Data Analysis
One-line Description:
DA is processing endlessly
Problem:
In case the expected retention time gets modified, and the focus stays in this cell while the user clicks on "reprocess all" the processing gets stuck.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Data Analysis
One-line Description:
MS profile reference spectra displayed incorrectly
Problem:
MS profile reference spectra saved to the processing method are displayed as discrete ions (like centroid spectra) instead of as a continuum.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
Different versions of acquisition methods with same name are not available after creating a new result set.
Problem:
In case, a new result set should be created based on 3 different sequences where 3 different versions of the same acquisition method are available, wrong acquisition parameters will be displayed in the acquisition set point.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 03 and OpenLab CDS v2.6 Update 10.
Keyword: Data Analysis
One-line Description:
Amount and Concentration unit is blank in column header of compound table
Problem:
On a report, amount and concentration unit is blank in column header of compound table when ISTD compound is missing in one of the samples.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03
Keyword: Data Analysis
One-line Description:
MS Spectrum window does not behave correctly when using pinned injections
Problem:
Under certain conditions, when unpinning injections while MS spectra are already extracted, the MS spectrum window may appear empty with an x-axis scale of 0-10.
Temporary Solution:
If the issue occurs, click on any extracted MS spectra for the unpinned injection in the navigation tree and the window will populate correctly.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Data Analysis
One-line Description:
"Review selected run in DA" does not work.
Problem:
"Review selected run in DA" does not open Data Analysis.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Data Analysis
One-line Description:
DA Launcher log files are overwritten.
Problem:
The log files for DA launcher service might reach the limit of entries very fast.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Data Analysis
One-line Description:
Data Analysis can become unresponsive when extracting all SIM signals
Problem:
In CDS v2.6, under certain conditions Data Analysis may become unresponsive with an endless spinning wheel when attempting extract one or more SIMs.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Automatically searching TIC peaks in MS library can cause Data Analysis to crash
Problem:
In CDS v2.6, in certain circumstances, Data Analysis may crash when Automatically search TIC peaks is enabled under the MS library search section of the processing method and a results set is reprocessed.
Temporary Solution:
Deselect Automatically search TIC peaks and reprocess. If this is successful, consider manually triggering the MS search for peaks of interest.
Fix Information:
This issue is resolved in CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Reopening processed data which has spectral smoothing enabled may cause Data Analysis to crash
Problem:
In CDS v2.6 and v2.7, under certain conditions, when a results set has automatically extracted spectra and spectral smoothing enabled, and the results set is processed, saved, closed, and reopened, Data Analysis may crash.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.7 Update 03 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Unexpected error after using Manual Integration
Problem:
Unexpected error after using Manual Integration.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.6 Update 09.
Keyword: Data Analysis
One-line Description:
Changed value is not kept for custom fields but recorded in audit trail
Problem:
If the value of a custom field gets changed - the field is still in focus (cursor is blinking) - and immediately start a reprocessing with a save followed, the value change is tracked in Audit Trail, and it is displayed in the UI. If you close the result set and re-open it, the change is still tracked in AT, but no longer visible in the injection list.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.6 Update 10.
Keyword: Data Analysis
One-line Description:
Using pinned injections while viewing profile MS spectra in overlaid mode does not refresh properly
Problem:
This issue only affects profile data when their spectra are being viewed in Overlay mode. If pinned injections are used, the display does not refresh properly when attempting to navigate between spectra or between injections. This leads to the appearance that the display may be frozen.
Temporary Solution:
Use Separate mode when working with pinned injections with profile MS spectra.
Fix Information:
This issue is resolved in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 06, and OpenLab CDS v2.6 Update 13.
Keyword: Data Analysis
One-line Description:
Resolved EZChrom methods do not display the correct Signal names after migrating to CDS
Problem:
Resolved EZChrom methods do not display the correct Signal names after migrating to CDS
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03
Keyword: Data Analysis
One-line Description:
Ion labels missing for overlaid profile MS spectra
Problem:
When overlaying MS spectra acquired in profile mode, ion labels are sometimes not shown as expected.
Temporary Solution:
Ions are labeled properly in Separate mode.
Fix Information:
Issue is resolved in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 06, and OpenLab CDS v2.6 Update 13.
Keyword: Data Analysis
One-line Description:
Assigning qualifier can cause Data Analysis to crash under certain conditions
Problem:
When assigning a qualifier from existing or duplicated rows of the compound table, if the active injection is not linked to the method being edited, Data Analysis may crash.
Temporary Solution:
Make sure to assign qualifiers when the active injection is linked to the method being edited.
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Data Analysis
One-line Description:
Smoothed MS chromatograms may exhibit splining under certain conditions
Problem:
Under certain circumstances, smoothed MS chromatograms may exhibit splining - significant baseline disruptions at the start of a chromatographic peak, the end of the peak, or both. This issue is more likely to occur when the data rate is slower (for example, on fast polarity switching data, or on SIM/Scan data), and when smoothing with fewer points and/or passes is used.
Temporary Solution:
Disable smoothing or use a higher number of smoothing points and/or passes.
Fix Information:
This issue is resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
EZChrom to OpenLab CDS migration: Additional peaks detected in OpenLab CDS after migration
Problem:
EZChrom to OpenLab CDS migration: Additional peaks detected in OpenLab CDS after migration. This issue occurs because the absolute retention time window is not getting imported correctly.
Temporary Solution:
Double-check the value for absolute retention time window of the compound and correct it if needed.
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Data Analysis
One-line Description:
Manipulating overlaid profile spectra with pinned injections causes DA to crash
Problem:
When profile spectra are used in overlaid mode and multiple injections are shown via pinning, manipulating the spectra - in this case, by adjusting the threshold - causes DA to crash.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Smoothed MS profile spectra may exhibit splining and negative abundance values
Problem:
Smoothed MS profile data may see splining and baseline abnormalities introduced by the smoothing algorithm. This may include negative abundance values, particularly if spectral background subtraction is used.
Temporary Solution:
Do not use MS Spectral smoothing if this behavior is observed. Existence of negative values abundance may be partially mitigated by not using background subtraction for the spectra, but the splining effect may still be present.
Fix Information:
This issue is resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
Locked result set cannot be unlocked
Problem:
In case a previous version of a result set gets signed and automatically locked (controlled by a project setting), the result set cannot be unlocked, or the signature cannot be revoked after loading.
Temporary Solution:
Possible workaround: Deactivate automatic locking after signing on the project level. Afterwards, the result set can be unlocked again.
Fix Information:
This issue got resolved in OpenLab CDS v2.8, and OpenLab CDS v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
Opening and closing imported MS data without saving before closing can result in MS TIC(s) not displayed for first injection
Problem:
Under certain conditions, when a result set which contains MS data is imported, opened, and closed without saving, the MS signal(s) (TIC(s)) from the first injection may not be displayed upon re-opening the result set.
Temporary Solution:
Save imported result sets which contain MS data before closing. If the issue occurs, re-import the results set, open it, and save it before closing.
Fix Information:
This issue is resolved in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Data Analysis
One-line Description:
Loading method causes error One or more errors occurred. (Content cannot be converted to the type Int. Line 1, position 94)
Problem:
In case the processing method got created in an updated OpenLab CDS 2.x, an error might show up if the processing method get loaded on the base version.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
Target formula not accessible in custom calculation and reporting
Problem:
If a chemical formula is set as target, it is not possible to access it in custom calculation and reporting.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Data Analysis
One-line Description:
Quickly drag and drop Data Analysis windows will show a black area
Problem:
Quickly drag and drop Data Analysis windows will show a black area
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 06, and OpenLab CDS v2.6 Update 13.
Keyword: Data Analysis
One-line Description:
Modification date of linked injections gets changed after linking same processing method to an unlinked injection.
Problem:
In case a processing method, which is already linked to some injections in a result set, gets linked to an unlinked injection, all linked injections will be processed after the linking. This will create a new modification date for all linked injections.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Data Analysis
One-line Description:
UV Purity value is blank for some peaks
Problem:
In some cases, UV purity values are blank for some peaks and a warning is shown: "Spectra: Not enoug spectra after filtering in peak at <retention time> and signal <signal name> for peak purity calculation". This can happen if all spectra get discarded because the standard deviation of noise is below a certain limit, which can be caused by solvent absorption.
Temporary Solution:
How to make sure UV purity can be calculated, read dependencies and follow recommendations on https://openlab.help.agilent.com/en/index.htm#t=mergedProjects%2FDataAnalysis%2FiDA_DataAnalysis_Method_CompoundsSpectra_UVImpurity.htm
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
MS Base Peak may return incorrect value for polarity switching data when smoothing is enabled.
Problem:
The MS Base Peak field may in some cases return the base peak value from the negative spectrum to the positive TIC, or from the positive spectrum to the negative TIC when smoothing is enabled for the TICs. This issue is only seen on polarity switching data. The MS Base Peak field can be accessed via annotations in the Chromatogram window, via Intelligent Reporting fields, and via Custom Calculator.
Temporary Solution:
If smoothing is disabled and the results are reprocessed, the issue should be resolved. Manual integration may need to be deleted and re-performed to resolve the issue for manually integrated peaks.
Fix Information:
This issue has been fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 13.
Keyword: Data Analysis
One-line Description:
Processing error: The given key not present in dictionary
Problem:
When processing a result set which has more than one compound defined, and those compounds have MS reference spectra saved, occasionally a processing error occurs which gives the description as "The given key was not present in the dictionary".
Temporary Solution:
If the MS reference spectra are removed from the method, the error will not occur.
Fix Information:
This issue is resolved in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 06, and OpenLab CDS v2.6 Update 13.
Keyword: Data Analysis
One-line Description:
Missing entry in system activity log for signing or revoking a signature on a result set
Problem:
Missing entry in system activity log for signing or revoking a signature on a result set
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, and OpenLab CDS v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
LCMS data exported to ChemStation format using AIA export is lacking metadata
Problem:
When exporting LCMS data to ChemStation format using the ChemStation and AIA post-processing plugins, the MS metadata needed by ChemStation to properly identify data attributes such as polarity and acquisition time zone is not generated. One consequence of this is that LCMS data which has been exported to ChemStation format cannot be re-imported to OpenLab CDS.
Temporary Solution:
ChemStation will prompt the user to identify the data polarity, if needed for the workflow being executed. Otherwise, there is no known workaround. This workflow (export LCMS data to ChemStation format, then reimport that exported data into OpenLab CDS) is not supported; this should not be used as a data backup procedure. Data which is intended for re-import into OpenLab CDS should be exported as an OLAX.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
EIC extraction window erroneously applied to TIC signals
Problem:
In OpenLab CDS v2.4 and v2.5, if a non-zero EIC extraction window is specified in the processing method and one or more compounds are quantitated using a TIC signal, the signal name in the compound table will be appended with the extraction range upon reprocessing. This will result in no results being calculated for that compound. This is not an issue if all compounds are calculated on EIC or SIM signals.
Temporary Solution:
If quantitating using TIC signals in OpenLab CDS v2.4 or v2.5, do not use an EIC extraction window (set the value to 0).
Fix Information:
This issue is resolved in OpenLab CDS v2.6 and later.
Keyword: Data Analysis
One-line Description:
Quantitation cannot be performed on MS compounds if the Single m/z expansion chromatogram window is changed after compounds already exist in the compound table
Problem:
If MS compounds already exist in the compound table and meet the following criteria, changing the Single m/z expansion chromatograms window setting will cause quantitation to fail for these compounds: -Scan data only is affected (not SIM) -Compound and/or qualifiers are defined on either TIC signal or EIC signal where it is an EIC of a single mass (typically written as EIC(278.7-279.7) or similar), as opposed to a user-defined range (example: EIC(275.5-285.5))
Temporary Solution:
If the Single m/z expansion chromatograms window setting must be changed, remove the MS compounds from the compound table and readd them with the new setting in place.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Missing injection in the result set after loading in Data Analysis
Problem:
When an acquired and completed result set is loaded in Data Analysis, some injection(s) are found missing, even though the acquisition completed successfully. This issue might occur if the result set was modified during review completed injection or snapshot, while it is also loaded in another Data Analysis session and saved.
Temporary Solution:
n/a
Fix Information:
In OpenLab CDS v2.7 Update 08 Data Analysis will detect if the loaded result set was modified and saved in parallel in a review completed injection or snapshot session and prevent saving in Data Analysis.
Keyword: Data Analysis
One-line Description:
Renaming a compound causes error "unable to update data value: An item item with the same key has already been added"
Problem:
The error "unable to update data value: An item with the same key has already been added" might show up if compound name gets changed. This can issue can occur if a compound gets renamed and the master method gets updated. Once the master method gets used again and a compound gets renamed to the old name, the error shows up. This might also affect the calibration curve of the compound.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
Individual peaks are not quantified in a timed group
Problem:
Unknown peaks might not be quantified in a timed group if the curve model is set to quadratic. The same might happen if the curve reference has a quadratic curve model. The quantification of the individual peaks in the timed group is based on the group amount and the group response. In case the quadratic curve has more than one solution for the group amount/group response, nothing will be displayed. This can occur if the minimum or maximum of the quadratic curve is within the range.
Temporary Solution:
n/a
Fix Information:
In general, it is not recommended to use nonlinear and/or calibration curves with a large offset for timed groups, since the calibration parameters are used for the whole group. Reference: https://openlab.help.agilent.com/en/index.htm#t=mergedProjects%2FDataAnalysis%2FDA_DefinitionTimedGroup.htm
Keyword: Data Analysis
One-line Description:
Some injections might not be processed when using Walkup
Problem:
Some injection might not be processed when using Walkup 4.2 Update 01 to run samples. The samples are all injected and data is acquired, but the unattended processing does not happen.
Temporary Solution:
n/a
Fix Information:
The OpenLab CDS Data Analysis related part is fixed in OpenLab CDS v2.8 Update 03, and OpenLab CDS v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
Locking of result set is not permanent
Problem:
ChemStation data with (non-) injections where the vial was missing might lose the locking state after reloading.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.7 Update 08. and OpenLab CDS v2.6 Update 13.
Keyword: Data Analysis
One-line Description:
Parent peak is not correctly updated if rejected shoulder peak is nested in rider peak
Problem:
When using the ChemStation integrator in OpenLab CDS 2.x the area of a shoulder peak nested inside of rider peak on the tail side is not added back correctly to the parent peak when it is rejected by area or height reject parameter.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Data Analysis
One-line Description:
Only the first 10 calibration levels are imported when creating a new method from EZChrom
Problem:
Only the first 10 calibration levels are imported when creating a new method from EZChrom.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
Qualifiers can be added to multiple methods
Problem:
If two methods are open which each contain a compound with the same name, retention time, and signal, and a qualifier is added to that compound in one of the methods, the qualifier may also be added to the other method.
Temporary Solution:
If two methods with the same compound(s) are both open, close the one you do not wish to edit before adding qualifiers to the other.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Qualifiers can be removed if multiple methods with the same compounds are open
Problem:
If two methods are open - one of which contains compound(s) with qualifier(s) - and a compound with the same name, RT, and signal as one of the compounds in this method is manually created in the second method, and then a qualifier RSP% is manually edited in the first method, an error message will appear and the qualifier(s) will be removed.
Temporary Solution:
If qualifiers need to be edited, first close all other open methods which contain compounds with the same name, RT, and signal.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Swap qualifier to target with EIC extraction windows does not work as expected if target and qualifier Retention Times are different
Problem:
If a non-zero EIC extraction window is set in the processing method, and a qualifier exists on a compound which has a retention time different enough from the target retention time that the EIC/SIM extraction range is different on the qualifier signal and the target signal, when Swap qualifier to target is used and the data is reprocessed, the qualifier RSP% cannot be calculated. This affects both SIM and Scan mass spec data.
Temporary Solution:
If this circumstance arises, do not use Swap qualifier to target. Instead, delete the compound and recreate it in the processing method with the appropriate signals for target and qualifier. Alternatively, remove the EIC extraction window from the method (set it to zero).
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Adding qualifiers after performing Swap qualifier to target can result in incorrect qualifier RSP% calculations
Problem:
If qualifiers exist on a compound, and one is swapped to with the target using the Swap qualifier to target right-click command in the processing method, and then additional qualifiers are added, those newly added qualifiers will have their qualifier RSP%'s calculated using the original target values, not the new target values.
Temporary Solution:
Do not add additional qualifiers after swapping a qualifier to target. Delete the compound and recreate it.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
CEMS data imported from ChemStation may not function as expected in Data Analysis
Problem:
Importing CEMS data which was acquired in ChemStation into OpenLab CDS is not supported. Some Data Analysis features may not function as expected with CEMS data imported from ChemStation.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Missing blank can trigger crash
Problem:
If a specific blank is specified in the blank subtraction section of the processing method and that blank cannot be found, under certain conditions, a crash may occur when right-clicking the navigation tree. This issue occurs only when first loading a result set which has a missing blank already specified. This typically occurs if a result set is imported into another CDS environment in which the result set which contains the specified blank does not exist.
Temporary Solution:
To avoid this issue, specify a blank which exists in the current system and reprocess the result set from the ribbon bar at the top of the Data Analysis software immediately upon loading the result set.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Unexpected error occurred after importing *.cdf files exported with OpenLab CDS 2.x
Problem:
Unexpected error occurred after importing *.cdf files when they were exported with AIA export plugin in OpenLab CDS 2.8 or earlier and contain Chinese characters.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03. The issue in the post-processing plugin is fixed in OpenLab v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
DA API: Exceptions when accessing advanced ChemStation integration parameters
Problem:
DA API: Exceptions when accessing advanced ChemStation integration parameters.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Adding compounds to SIM data imported from OpenLab ChemStation can result in a crash
Problem:
When adding compounds to the processing method from SIM data imported from OpenLab ChemStation, if the compound is added by right-clicking an ion in the spectrum and selecting Add ion as compound/qualifier to method, a duplicate SIM may be extracted under certain conditions. If this occurs, trying to navigate to the duplicate SIM chromatogram can lead to a crash. This issue only affects LCMS SIM data which was acquired in OpenLab ChemStation and imported into OpenLab CDS v2.8.
Temporary Solution:
Add compounds from the SIM chromatogram(s), rather than from a spectrum.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
The sample name of the data exported by AIA is incorrect
Problem:
The sample name is incorrect after importing *.cdf files if the data was exported with AIA export plugin in OpenLab CDS 2.8 or earlier and contain Chinese characters.
Temporary Solution:
Sample names can be modified after import.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03. The issue in the post-processing plugin is fixed in OpenLab v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
Loading processing method is slow if output path for post-processing plugin is long
Problem:
Loading processing method is slow if it contains a long output path for post-processing plugin.
Temporary Solution:
Either specify a local path instead of a network path (but the path should exist on all machines where the process is done, i.e. Clients and AICs) or define a network path with a limited number of characters (for example: \\networkshare\Export)
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03, and OpenLab CDS v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
Spectra extracted over a range are not re-associated with their chromatographic peak when undoing a manual integration event
Problem:
Spectra manually extracted over a range are not re-associated with their chromatographic peak when undoing a manual integration event, such as splitting a peak or removing a peak.
Temporary Solution:
Remove and re-extract the spectrum after integration has been adjusted appropriately to re-link the spectrum to its chromatographic peak.
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Intermittent processing error
Problem:
On a result set with many injections, randomly, an injection can be flagged with: Injection Processed (with errors)
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Changing retention time of a compound in one method will change it in another method as well
Problem:
If in a result set, injections have different processing methods linked, where all have the same compounds defined, it can happen that changing the retention time for a compound in one method will change the retention time in the other processing methods as well.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Shoulder has slightly too small peak area when using Gaussian baseline
Problem:
When using the ChemStation integrator in OpenLAb CDS v2.8 with Gaussian baseline for shoulder detection, it might occur that the peak area is slightly too small.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 01
Keyword: Data Analysis
One-line Description:
Wrong user recorded in Activity Log after unlocking DA with another user
Problem:
When a user unlocks the Data Analysis session of another user, all loaded data are closed. In the Activity log, the entry which indicates who is responsible for closing files points to the wrong user.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in a future release
Keyword: Data Analysis
One-line Description:
Simple chart in reporting has only linear trending line
Problem:
On the advanced tab of the simple chart item in reporting, there is only an option to select a linear curve as trending line.
Temporary Solution:
n/a
Fix Information:
Starting with OpenLab CDS v2.8 Update 01 there will be an option to select a polynomial (2nd order) trending line.
Keyword: Data Analysis
One-line Description:
DA API request for MS spectrum fails if spectral smoothing is enabled
Problem:
DA API request for profile MS spectrum fails if spectral smoothing is enabled in the processing method.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 01.
Keyword: Data Analysis
One-line Description:
Compound units are not available in DA API
Problem:
Compound units are not available in DA API.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 01.
Keyword: Data Analysis
One-line Description:
Unexpected error occurred when printing sequence audit trail.
Problem:
An unexpected error occurred on Data Analysis when printing sequence audit trail.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 02, and OpenLab CDS v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
Custom Calculation Editor stops working when a new file gets created
Problem:
If a new file in the custom calculation editor gets created while a server switch on a multiserver solution happens, the CC editor stops working with an unexpected error.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 01.
Keyword: Data Analysis
One-line Description:
DA API returns error 500 for all requests
Problem:
DA API returns error 500 for all requests
Temporary Solution:
This might be caused by some other process blocking the ports. Running the following commands as administrator might solve the issue: net stop hns net start hns
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Calculate sensitivity does not refresh as expected
Problem:
When the users are clicking on calculate sensitivity for selected or all compounds, the values are updated in the background, but not updated in the user interface.
Temporary Solution:
Saving the result set, closing it, and reopening it will display the updated values.
Fix Information:
This issue has been resolved in OpenLab CDS v2.8 Update 02.
Keyword: Data Analysis
One-line Description:
Crash when reprocessing data when injection selected for Blank Subtraction cannot be found
Problem:
If Blank Subtraction is enabled and a specific blank is selected in the processing method (as opposed to Using blanks defined in the sequence), if the specific blank is no longer available, Data Analysis may crash in certain scenarios. One example is if the data is migrated from one project to another, the path to the specified blank is no longer valid so the blank cannot be found. In some cases it is not possible to select another blank or resolve the situation before the crash occurs.
Temporary Solution:
Selecting Use blanks defined in the sequence instead of a specific blank will avoid this crash. Blank samples which are not to be subtracted may be set to a different sample type, such as Spike.
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
If a CC Display Name contains ">" it is displayed as ">" in Injection Results and CC report
Problem:
If a CC Display Name contains ">" it is displayed as ">" in Injection Results and CC report when using Custom Calculation Files created in OpenLab CDS v2.7 on an OpenLab CDS v2.8 systen.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
DA API handles Custom Fields case-sensitive but DA does not.
Problem:
Data Analysis API handles Custom Fields case-sensitive, but Data Analysis does not.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
DA API session host stops running the API Server instance after 30 minutes of inactivity
Problem:
DA API session host stops running the API Server instance after 30 minutes of inactivity.
Temporary Solution:
n/a
Fix Information:
In OpenLab CDS v2.8 Update 01 the time-out is set to 24h.
Keyword: Data Analysis
One-line Description:
DA API does not clear history calibration points if clear calibration is set.
Problem:
DA API does not clear history calibration points if clear calibration is set as run type.
Temporary Solution:
n/a
Fix Information:
This issue has been resolved in OpenLab CDS v2.8 Update 02.
Keyword: Data Analysis
One-line Description:
An intermediate version of a result set can be locked/signed when clicking cancel
Problem:
An intermediate version of a result set can be locked/signed when clicking cancel.
Temporary Solution:
Closing the result set leads to a warning : 'You do not have permission to save the result set method. All method and result changes will be discarded'. In the end, the sign/lock is discarded.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Entering a target mass in the sample sequence table of >3000 will be rejected
Problem:
Entering a target mass in the sample sequence table of >3000 will be rejected. There is a work around of using the formula but this may be impractical for larger more complex samples.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Unexpected error after loading a processing method from 2.7 with post processing plugin
Problem:
Unexpected error after loading a processing method from 2.7 with post-processing plugin. This can happen if the output path is pointing to a drive that does not exist on the PC.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Numeric compound custom field reverts to original value when changed in injection list
Problem:
Numeric compound custom field reverts to original value when changed in injection list of new created result set.
Temporary Solution:
Changing the value again will keep the new value.
Fix Information:
This issue got fixed in OpenLab CDS v2.8 Update 03, and OpenLab CDS v2.7 Update 08.
Keyword: Data Analysis
One-line Description:
Result set not locked for user with lower signature level
Problem:
A result set is not locked for a user with a lower signature level after data has been locked by a user with a higher signature level.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Data Analysis crashes upon clicking on "Up" arrow to browse outside of Methods folder in "Open Method" window.
Problem:
Data analysis crashes with the following actions: 1. Click on "Open Method" and select a processimg method 2. Pick and choose a version of interest from version's dropdown list 3. Click "Up" arrow to try to browse outside of "Methods" folder
Temporary Solution:
n/a
Fix Information:
The issue is fixed in OpenLab CDS v2.8 Update 02.
Keyword: Data Analysis
One-line Description:
Missing blank can trigger crash
Problem:
If a specific blank is specified in the blank subtraction section of the processing method and that blank cannot be found, under certain conditions, a crash may occur when right-clicking the navigation tree. This issue occurs only when first loading a result set which has a missing blank already specified. This typically occurs if a result set is imported into another CDS environment in which the result set which contains the specified blank does not exist.
Temporary Solution:
To avoid this issue, specify a blank which exists in the current system and reprocess the result set from the ribbon bar at the top of the Data Analysis software immediately upon loading the result set.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
The Data Analysis application does not start and error message is shown
Problem:
The Data Analysis application does not start with no error message, The Windows event log shows a .Net error ------------------------------ Application: Agilent.OpenLab.DataAnalysis.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.IOException at System.IO.__Error.WinIOError(Int32, System.String) at System.IO.DriveInfo.get_AvailableFreeSpace() at Agilent.OpenLab.DataAnalysis.App.DumpStartupInfo() ------------------------------ This happens when a drive is available on the computer, where the currently logged in operating system user does not have read access.
Temporary Solution:
Before opening the OpenLab Control Panel, make sure to unmap any drive where the operating system user does not have ready access to.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Cannot start Data Analysis from Acquisition
Problem:
"Cannot open DA, please make sure Agilent OpenLab Data Analysis Service is running." appears when trying to start Data Analysis from Acquisition. In the logs, the error Unable to register in DA Rest Services is written.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
Switching rows in the compound table can cause a Data Analysis crash in certain scenarios
Problem:
Switching between row types in the Compound Table, where one row has an MS spectrum associated with its peak, can sometimes cause Data Analysis to crash.
Temporary Solution:
n/a
Fix Information:
This issue has been resolved in OpenLab CDS v2.8 Update 03.
Keyword: Data Analysis
One-line Description:
LC/MS Sample Purity calculation omits neutral losses if neutral loss cannot result from target formula - but still lists the neutral loss in the Sample Purity results table
Problem:
When using the LC/MS Sample Purity workflow, if the target(s) are input as chemical formula(s) (instead of numerical values) and neutral losses are specified in the processing method, OpenLab CDS will verify that the atoms in the neutral loss's chemical formula occur in the target formula(s). If the neutral loss atoms do not occur in the target chemical formula, the neutral loss will not be included in the Sample Purity calculation. For example, if the chemical formula entered in the target field is C6H14, and the neutral loss specified is H2O, because there is no oxygen present in the target formula, a neutral loss of water is not possible and the neutral loss is not included in the Sample Purity calculation. However, if the target formula is C6H12O6, a neutral loss of water would be included in the Sample Purity calculation, because there is at least one oxygen atom and 2 hydrogen atoms present in that formula. This behavior is all as intended. However, the Adducts column in the Sample Purity results table still lists the neutral loss, regardless of whether the neutral loss is not being used in the calculation - which can lead to confusion about which values are being used in the Sample Purity calculation.
Temporary Solution:
If this behavior is not desired, the target(s) can be listed as numeric values, rather than chemical formulas. If a numeric value is used, OpenLab CDS will always use the specified neutral loss in its Sample Purity calculations.
Fix Information:
This issue (neutral loss being listed regard less of whether it is used in the calculation or not) will be resolved in a future release.
Keyword: GC Driver
One-line Description:
Run on GC hung in processing state when performing a snapshot
Problem:
When running a method with no signal selected to collect data on an Agilent GC, after a snapshot is performed on this run, the run will get stuck at processing state, and the all the pending runs will not start. To get out of this state, you have to restart your workstation or AIC.
Temporary Solution:
n/a
Fix Information:
This is fixed in OpenLab CDS version 2.3.
Keyword: GC/MS Driver
One-line Description:
Setting source temperature as a Timed Event does not change the setpoint on the Dashboard
Problem:
When you set up a method with a Timed Event that changes the MS source temperature, the temperature changes at the appropriate time. However, the setpoint field on the Dashboard does not reflect the change.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Selecting a SIM or Scan time segment line highlights the entire row
Problem:
When a SIM or Scan time segment line is selected, the entire row is highlighted which makes it difficult to see which fields are editable.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Starting EI 5977A Tune does not wake up a sleeping 7890B GC after it was in sleep mode.
Problem:
While running a GC/MS system with communications established. Create Sleep, Wake, and conditioning methods. Put GC to sleep. While asleep, start an Autotune. This does not wake up the GC.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
While in Vented, Venting or Pumping down and network connection is lost, on re-connection the UserInterface state goes to Idle.
Problem:
The Tune UserInterface state should go to the previous state upon re-connection to the instrument due to network disconnection. But if the previous state is no longer valid, it should go to the new corresponding state.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Manual Tune Scan plot does not show all of the information
Problem:
In Manual Tune set Acquisition Mode to Scan and set the scan range and scan speed. Turned on the cal valve and selected Start acquiring data. The values Low, High, Step, Sample, Threshold, Peaks, Base, Abundance and Total Ion should be displayed on the top and Mass, Abund, Rel Abund, and Iso Mass should be displayed on the bottom.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Prepare to Vent disappears from MSD LUI
Problem:
With a 5977A and a 7890B with DCOMM, selected Prepare to Vent from the MSD LCP. GC loaded the Vent method and vent completes. MSD LCP shows Vent complete, can turn off MSD power. Then select Pump down from the Maintenance menu of the LCP. Pumpdown started and complete. GC and MSD showed ready. While in the Maintenance menu of the MSD LCP, Prepare to Vent item is missing; need to reboot to recover missing task.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Vacuum fault not clearing on turbo pump without Lcomm, 5977B and 7890B system.
Problem:
Able to see fault 'Error' when performing Vent/Pump Down operations.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Manual Tune profile plot does not show all the information
Problem:
In the Mnaual Tune selected Profile. Used the default settings of masses 69, 219 and 502. Set Windows +/- to 6 and started acquiring data. Visually seeing the masses and the correct window. On the right the plots should be summarized and "normalized". Also the values of Mass, Abundance, Rel Abundance and PW50 should be displayed on the bottom.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Signals acquired in "SIM" mode or "SIM and Scan" mode can drop out below the baseline
Problem:
In OpenLAB CDS 2.0, when you acquire in "SIM" mode or "SIM and Scan" mode, the signals can drop out below the baseline (upside down peaks below the baseline). These drop out signals may interfere with integration.
Temporary Solution:
n/a
Fix Information:
This defect was resolved in OpenLAB 2 GCMS Driver A.01.01.
Keyword: GC/MS Driver
One-line Description:
Unable to close Acquisition if connection is lost while tuning or in Tune Control
Problem:
If the connection to server or instrument is lost while tuning or in Tune Control, the user cannot close Acquisition.
Temporary Solution:
n/a
Fix Information:
This issue fixed in GC/MS driver v1.2 which is included in OpenLab CDS v2.3.
Keyword: GC/MS Driver
One-line Description:
Filament selection is not updated when changing methods
Problem:
If a user specifies two different methods in a sequence which use different filaments (ie, Method A uses Filament 1 and Method B uses Filament 2) the filament selection was not being changed when the load method action occurs for Method B.
Temporary Solution:
n/a
Fix Information:
This defect is resolved in GC/MS Driver 1.4 released as part of OpenLab 2.5.
Keyword: GC/MS Driver
One-line Description:
It is possible to acquire data with un-tuned tune files.
Problem:
Selecting a tune file that has never been tuned should prevent the user from acquiring data until the tune file is modified in manual tune or a full autotuned is performed. This was not occurring and has been fixed in GC/MS Driver 1.4.
Temporary Solution:
n/a
Fix Information:
This defect is resolved in GC/MS Driver 1.4 released as part of OpenLab 2.5.
Keyword: GC/MS Driver
One-line Description:
Tuning and Tune related activities are not recorded in activity log
Problem:
When a tune is performed, this action is not recorded in the system activity log.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in GCMS driver v1.3 which is included with OpenLab CDS v2.4.
Keyword: GC/MS Driver
One-line Description:
GC/MS method update change from 'Version 100' to 'Version 101'
Problem:
In OpenLab CDS with GC/MS driver 1.2, loading a method that was previously saved with GC/MS driver v1.1 resulted in the following pop up warning: Inconsistencies: Method update change from 'Version 100' to 'Version 101'
Temporary Solution:
n/a
Fix Information:
This issue is fixed in GC/MS driver v1.3 which is included with OpenLab CDS v2.4. The pop up warning message is now changed to: Inconsistencies: The method has been updated to be compatible with current version of the software.
Keyword: GC/MS Driver
One-line Description:
Data file is collected but cannot be opened in Data Analysis
Problem:
At the end of the chromatographic run, it is possible for a data record to be saved with a retention time that is very close to 0 minutes. This will prevent the data file from being opened in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This defect is fixed in GCMS driver v1.3 which is included with OpenLab CDS v2.4.
Keyword: GC/MS Driver
One-line Description:
AcquisitionServer.exe process does not close when Close Connection is used
Problem:
In OpenLab CDS v2.2 and v2.3 with GC/MS driver v1.2, when the Close Connection button is used, the process AcquisitionServer.exe does not close the GC/MS instrument connection and must be manually killed using Windows Task Manager.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in GC/MS driver v1.3.54 which is included with OpenLab CDS v2.4.
Keyword: GC/MS Driver
One-line Description:
Acquisition Method Report does not show exact MSD model configured
Problem:
The Acquisition Method Report from OpenLab CDS v2.3 with GC/MS driver v1.2 and earlier shows "Agilent 597x MSD" instead of the exact MSD model "Agilent 5977 MSD" that is configured.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in GC/MS driver v1.3 which is included in OpenLab CDS v2.4.
Keyword: GC/MS Driver
One-line Description:
GC/MS autotune using a saved atune file results in manual tune report template
Problem:
In OpenLab CDS v2.2 with GC/MS driver v1.2, when a saved atune file is used to perform auto tune, the tune report looks like a manual tune report displaying "Tune Parameter Report" in the title instead of "Autotune Report". The content however displays the correct tune type as "Atune".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in GC/MS driver v1.3 which is included with OpenLab CDS v2.4.
Keyword: GC/MS Driver
One-line Description:
Discrepancy in "Run time" value user entered in Acquisition UI vs displayed in the Acquisition Method Report
Problem:
In OpenLab CDS v2.3 and earlier with GC/MS driver v1.2 and earlier, if the user enters "21.25" in the Run time field, the Acquisition UI shows "21.3" but the Acquisition Method Report shows "21.25".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in GC/MS driver v1.3 which is included with OpenLab CDS v2.4. Both the Acquisition UI and Acquisition Method Report now display the Run time value with one decimal place, regardless of how many decimal places the user enters.
Keyword: GC/MS Driver
One-line Description:
Acquisition Method Report shows generic "Detector EMV Override" label in SIM Table
Problem:
In OpenLab CDS v2.3 with GC/MS driver v1.1 and earlier, the Acquisition Method Report shows generic "Detector EMV Override" label in the SIM Table Row instead of the exact EM mode override like "Gain Factor Override", "Delta EMV Override", or "EM Volts Override".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in GC/MS driver v1.3 which is included with OpenLab CDS v2.4.
Keyword: GC/MS Driver
One-line Description:
Autotune report always shows the default masses for PFTBA even if the selected masses are changed
Problem:
Selected autotune mass(es) in Custom Tune panel are totally ignored in the autotune. The autotune report always show default masses for PFTBA.
Temporary Solution:
This is fixed in GC/MS driver v1.3.54, released as part of OpenLab CDS v2.4.
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Switch Filament options should not be shown for CI GCMS configurations
Problem:
The CI source only has one filament, and so any "switch filament" options shown while a CI source is configured are invalid and should not be used. These options will be removed in the GC/MS driver v1.3.
Temporary Solution:
n/a
Fix Information:
This defect is resolved in GC/MS driver v1.3 released as part of OpenLab CDS v2.4.
Keyword: GC/MS Driver
One-line Description:
MS stays in a not-ready status following autotune if using JetClean in Acquire & Clean mode
Problem:
Following a successful autotune or tune evaluation the MS will not return to a ready state until the acquisition client is closed and the connection to the instrument is closed. This only occurs when JetClean is being used in Acquire and Clean mode.
Temporary Solution:
n/a
Fix Information:
This defect is resolved in GC/MS Driver 1.4.16, released as part of OpenLab CDS v2.5.
Keyword: GC/MS Driver
One-line Description:
PCI autotune fails to complete on some instruments after an initial successful autotune
Problem:
After an initial successful autotune, subsequent PCI autotunes fail to complete on some instruments. The PCI tune algorithm used for OpenLab CDS v2.4 and earlier was based on the algorithm used by the Agilent 7000 series Tandem Quadrupole MS rather than the 5975 or 5977 Single Quadrupole MS. Differences in these two algorithms have been shown to cause problems completing positive CI autotune with OpenLab CDS.
Temporary Solution:
n/a
Fix Information:
This defect is resolved in GC/MS Driver v1.4.16, released as part of OpenLab CDS v2.5. The PCI tune algorithm has been re-written to match what is used for MassHunter GC/MS Data Acquisition with 5975 and 5977 SQ instruments.
Keyword: GC/MS Driver
One-line Description:
Aborting bakeout during equilibration may cause the timing problems
Problem:
If a bakeout is aborted during the final temperature equilibration and then resumed it will cause misleading timing information to be displayed.
Temporary Solution:
n/a
Fix Information:
This defect is resolved in GC/MS Driver 1.4 released as part of OpenLab 2.5.
Keyword: GC/MS Driver
One-line Description:
Autotune icons are grayed out after clicking "Cancel" in Delete Tune File dialog
Problem:
In the "Delete Tune File" dialog, if you click "Cancel" to exit the dialog and return to the "Autotune" UI, all icons are grayed out, except "Release Tune Control" button and "Delete Tune" button.
Temporary Solution:
n/a
Fix Information:
This is fixed in GC/MS driver v1.4.16, released as part of OpenLab CDS v2.5.
Keyword: GC/MS Driver
One-line Description:
User created tune files cannot be deleted if a default tune file is currently loaded
Problem:
When a default tune file, such as "atune," is currently loaded it is not possible to delete other user-created tune files.
Temporary Solution:
Load a user-created tune file and then delete the necessary tune files.
Fix Information:
This defect is resolved in GC/MS Driver v1.4.16, released as part of OpenLab CDS v2.5
Keyword: GC/MS Driver
One-line Description:
No warning message after method is loaded with invalid tune file
Problem:
If a method is loaded and references a tune file that has been deleted, no warning message appears and consequently the method can be saved with invalid (non-existing) tune file.
Temporary Solution:
n/a
Fix Information:
This defect is resolved with GC/MS Driver v1.4.16, released as part of OpenLab CDS v2.5.
Keyword: GC/MS Driver
One-line Description:
Actual values for bakeout and equilibrium time are incorrect
Problem:
The “actual” time displayed during bake out always count down from 3 hours, regardless of the duration specified. The correct duration is used, but the countdown displays an incorrect value.
Temporary Solution:
This is fixed in GC/MS driver v1.4.16, released as part of OpenLab CDS v2.5.
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Vacuum Control: If the acquisition client is closed during vent and then reconnected, the time elapsed value is lost
Problem:
When venting, the vacuum status window will display the time elapsed since the vent process was initiated. If the acquisition client is closed and reopened this time elapsed value will be cleared.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Vent: Turbo speed may not be accurate below 3%
Problem:
When venting, the turbo speed readback can be inaccurate between 0-3%. Rather than showing a speed of 0.1% the display should show a speed of "----"
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Tune Report PDF may not display in some situations
Problem:
If the acquisition client PC is low on available resources (CPU, memory, etc), then in some cases the PDF viewer will not be launched to display the Tune Report following a successful autotune.
Temporary Solution:
If this occurs, freeing up resources and re-triggering the display of the tune report manually will work.
Fix Information:
This is resolved in GC/MS driver v1.4.16, released as part of CDS OpenLab v2.5.
Keyword: GC/MS Driver
One-line Description:
Cannot release Tune Control
Problem:
If the GC goes into a fault state, such as inlet pressure shut down, while the acquisition client has tune control, releasing tune control is not possible until the tune control request times out due to inactivity.
Temporary Solution:
n/a
Fix Information:
This is fixed in GC/MS driver v1.4.16, released as part of OpenLab CDS v2.5.
Keyword: GC/MS Driver
One-line Description:
Using "Generate Report" in PCI mode the calibrant valve is not opened
Problem:
When operating in PCI mode, if the user runs the "Generate Report" function the PFDTD valve does not open and the resulting report is invalid.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Custom Tune: Correct masses will not be displayed in report if changed
Problem:
If the masses used for custom tune are changed (ie, changing 502 to 414) the right mass (414) would be used to perform the autotuned but the incorrect mass (502) would be shown on the tune report
Temporary Solution:
n/a
Fix Information:
This is fixed in GC/MS driver v1.4.16 that released with OpenLab CDS v2.5.
Keyword: GC/MS Driver
One-line Description:
Custom Tune: Using masses that are fewer than 100 amu apart will abort with error
Problem:
When using Custom Tune and tuning masses are chosen that are less than 100 amu apart, the tune will abort with an error message. Until this problem is resolved avoid using ions that are within 100 amu of each other.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: GC/MS Driver
One-line Description:
Acquisition can't be closed during GC-MSD venting
Problem:
While a GC-MSD is venting, the Acquisition client can't be shut down. This is confusing in a Client/Server environment as the user is forced to have two Acquisition windows opened in order to work on another instrument while the MSD is venting.
Temporary Solution:
n/a
Fix Information:
This is fixed in GC/MS driver v1.4.16, released as part of OpenLab CDS v2.5.
Keyword: Headspace
One-line Description:
Cannot get 7697 Comm setup in OpenLab CDS 2.2.0.600; Connection always makes the HS's GC IP revert to previous setpoint
Problem:
Set up communications between a 9000 and a 7697 via both keypads. Enable comm on the 9000 LUI, 9000 GC 130.30.246.38 with FW A.01.04.205 to 7697 HS 130.30.246.214. Follow GC from the 7697. From OpenLab CDS . 2.2.0.600 with HS A.01.07.3.18065, configure the two instruments. Get Config for both after LUI setup. Open an online session, and as soon as it makes connections, the 7697 LUi shows the GC's IP revert to 130.30.246.251. Inst Status always then shows HS Comm as Off.
Temporary Solution:
n/a
Fix Information:
The problem is fixed in B.01.07.3.
Keyword: Headspace
One-line Description:
Sequence aborts with "address may not be null" error
Problem:
when “No injection” lines are included in the sequence, the system aborts immediately (as soon as you click “Run” sequence) throwing an “address may not be null” error message. This behavior has been observed after upgrading the core OpenLAB software to 2.4. It can be reproduced with driver B.01.09 – driver B.01.07.3 does NOT give the error."
Temporary Solution:
n/a
Fix Information:
Fixed in revision B.01.10.
Keyword: Installation
One-line Description:
Data Store server synchronization fails if the computer hostname contains an underscore.
Problem:
Data Store server synchronization fails if the computer hostname contains an underscore.
Temporary Solution:
An underscore "_" should not be used in the computer hostname.
Fix Information:
n/a
Keyword: Installation
One-line Description:
Old icon displayed for links after upgrading your Data Store server to rev. 2.0
Problem:
After upgrading your Data Store server to rev. 2.0. the links created in the OpenLAB Control Panel will still show the previous application icon. Newly created links will show the new icon.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Instrument Control
One-line Description:
OpenLAB CDS crashes after power cycling the Waters Acquity instrument
Problem:
After power cycling a Waters Acquity it is possible to launch the instrument again within OpenLAB CDS and to execute a run or sequence, but because the Waters driver is not restarted the instrument is not connected properly with the driver and this can lead to OpenLAN CDS crashing.
Temporary Solution:
Workaround: After power cycling the Waters Acquity instrument, it is necessary to reboot the AIC. If this is not practicable, it is necessary to terminate the following Acquity processes manually in the Windows Task Manager on the AIC. First delete the ACQUITYServer.exe*32 (red framed). After this delete all the other Acquity processes (blue framed). During the launch of the instrument the processes are restarted and the instrument should work without crashing.
Fix Information:
n/a
Keyword: LC/MS Driver
One-line Description:
Changes to Manual Tune parameters have no respond in spectrum display windows LC/Single Quad
Problem:
Changes to Manual Tune parameters have no respond in spectrum display windows on all 61xxC Single Quad LC/MS. When making changes to the width gain/offset, mass axis/offset, or ion optics voltages, the spectrum display windows have no affect to the tune peaks.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS v2.4
Keyword: LC/MS Driver
One-line Description:
Charging voltage displayed as Nozzle Voltage in the check tune report for MultiMode Source
Problem:
The Charging voltage displayed as Nozzle Voltage in the check tune report for MultiMode Source.
Temporary Solution:
n/a
Fix Information:
Fixes in LC/MS Driver 2.3
Keyword: LC/MS Driver
One-line Description:
AJS source Sheath Gas Temp & Sheath Gas Flow parameters not validating in the Method Override
Problem:
If the user overrides either the sheath gas temp or sheath gas flow in the sequence method override, the system will not validate this against the allowable ranges for the other parameter. The override parameters that cannot be achieved, the firmware will prevent unsafe conditions and the system will remain "not ready". Sequence override parameters have a single validation range and no way to check validation of another parameter. Users who use the sequence override conditions should be aware of the conditions they are using and the affect they have on the system; relationship between the Sheath Gas Temp and Sheath Gas Flow.
Temporary Solution:
Both parameters need to changed at same time. Flow : Temp 7.5, 400.0 6.5, 350.0 5.5, 300.0 4.5, 250.0 3.5, 200.0 2.5, 150.0 0.0, 20.0
Fix Information:
N/A- The information will be included in the Help file
Keyword: LC/MS Driver
One-line Description:
Single Quad UI always display "Not Ready" state when the instrument in "Standby"
Problem:
Single Quad UI always display "Not Ready" when you put the instrument in" Standby" or turn off the device button because the "Standby" the Drying Gas Flow is 3.0 L/min. If the current method has a Drying Gas Flow settings greater than 3.0 L/min, then the UI always "Not Ready" when users put the Single Quad in Standby.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS v2.4
Keyword: LC/MS Driver
One-line Description:
Cannot close OpenLab CDS Acquisition if connection to server is lost during LC SQ tune check
Problem:
If the Acquisition client loses connection to the server while LC SQ tune check (evaluation) is running, an error "Acquisition has stopped working" occurs and clicking "Close the program" from the error message does not close the program. The program also cannot be closed by clicking X from top right corner of the window.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in LC/MS driver v2.2 which is included in OpenLab CDS v2.4.
Keyword: LC/MS Driver
One-line Description:
Missing Data Point crossed the chromatographic peak on G6135C SQ
Problem:
There is error on the MADLY calculation on LC/MS firmware 2.14 with OpenLab CDS 2.3. The issue is that multiple SIM’s with less than 20ms dwell time methods which cause data points missing crossed the chromatographic peak on LC/MSD XT G6135C model.
Temporary Solution:
n/a
Fix Information:
Upgrade to LC/MS Firmware 2.18. The LC/MS Firmware 2.18 is included in OpenLab CDS 2.4 media.
Keyword: LC/MS Driver
One-line Description:
'Review Tune Report' dialog may freeze UI
Problem:
When LC/MSD, LC/MSD XT, and 6100C Series instrument is configured and user right clicks on device image to open 'Review tune report window and leaves it open for a long time without clicking the 'Take' or 'Release' buttons or while 'Review Tune Report’ dialog is open and the instrument control is released and then taken control by user, it may freeze UI.
Temporary Solution:
N/A
Fix Information:
Users should close the ‘Review Tune Report’ dialog before Taking or Releasing instrument control. Also, ‘Review Tune Report’ dialog should not be left open for extended period.
Keyword: LC/MS Driver
One-line Description:
APG remote triggering LC shutdown
Problem:
If hardware error occurs during a method , instrument will trigger APG Remote shutdown.
Temporary Solution:
n/a
Fix Information:
ESW 6.72.38
Keyword: LC/MS Driver
One-line Description:
Abundance change with dwell time when changing detector gain factor
Problem:
On LC/MSD iQ, when running method with multiple gain factors, changing dwell time will change the abundance response. This is likely due to insufficient inter-measurement delay when EMV changes.
Temporary Solution:
n/a
Fix Information:
LC/MS Driver 2.4.452 / ESW 6.72.28
Keyword: LC/MS Driver
One-line Description:
Shutdown method leaves LCMSD iQ actively scanning and not "Off"
Problem:
With OpenLab CDS Acquisition 2.4 - using the shutdown feature on the LC/MSD iQ will remain in the "On" position, actively acquiring spectra and maintaining high voltage even after the LC stack has gone into standby/shutdown.
Temporary Solution:
n/a
Fix Information:
LC/MS Driver 2.4.452
Keyword: LC/MS Driver
One-line Description:
Getting prompted to save method when no change is made in the method
Problem:
Getting prompted to save method when no change is made in the method on LC/MSD iQ system.
Temporary Solution:
n/a
Fix Information:
LC/MS Driver 2.4.452
Keyword: LC/MS Driver
One-line Description:
Divert valve may not switch to waste during hardware fault
Problem:
Divert valve may not switch to waste during hardware fault
Temporary Solution:
n/a
Fix Information:
LC/MS Driver 2.452 / ESW 6.72.28
Keyword: LC/MS Driver
One-line Description:
SQ online signal is missing after windows restart
Problem:
SQ online signal is missing after windows restart
Temporary Solution:
n/a
Fix Information:
LC/MS 2.4.452
Keyword: LC/MS Driver
One-line Description:
Autotune report results are incorrect on FWHM
Problem:
Autotune report results for incorrect tolerance on Full Width Half Mass (FWHM) G613XC LC/SQ models
Temporary Solution:
n/a
Fix Information:
LC/MS Driver 2.4.452 and Firmware 2.19
Keyword: LC/MS Driver
One-line Description:
Heaters faults cannot be cleared on LC/MSD iQ
Problem:
Unable to clear heaters faults on the UI with LC/MSD iQ
Temporary Solution:
n/a
Fix Information:
Driver 2.4.452/ESW 6.72.28
Keyword: LC/MS Driver
One-line Description:
Embedded Software (ESW) crash during autotune
Problem:
During autotune, if the webpage is refreshed at certain time, the Embedded Software (ESW) could crash.
Temporary Solution:
n/a
Fix Information:
LC/MS Driver 2.4.452/ ESW 6.72.28
Keyword: LC/MS Driver
One-line Description:
AIC installation was cancelled during install of LCMS driver, which caused it to roll back. After relaunching installer, LCMS driver install failed
Problem:
While installing an OpenLab CDS system with ECM XT as the back end and with AIC configured as the instrument controller, the installation was cancelled during install of LCMS driver. This results in the installer to roll back the installation. After relaunching installer, LCMS driver install failed to install.
Temporary Solution:
If this occurs, delete the C:\Program Files (x86)\Agilent Technologies\OpenLAB Acquisition\LCMS\Firmware directory and all its contents. Then, restart the installation process for OpenLab CDS.
Fix Information:
n/a
Keyword: LC/MS Driver
One-line Description:
Unstable spray warning in EMF
Problem:
Reset unstable spray counter at beginning of tune procedure.
Temporary Solution:
n/a
Fix Information:
ESW 6.72.38
Keyword: LC/MS Driver
One-line Description:
Applying LogAmp calibration coefficients
Problem:
The instrument should apply the Log Amp coefficients consistently to achieve a baseline of ~40 (instead of ~600)
Temporary Solution:
n/a
Fix Information:
ESW 6.74.3
Keyword: LC/MS Driver
One-line Description:
Mismatch between gain factor in acquisition method and gain displayed in DA
Problem:
Mismatch between gain factor in acquisition method and gain displayed in DA with OpenLab CDS 2.4 and LC/MS Driver 2.2.2260.
Temporary Solution:
n/a
Fix Information:
2.4.468.1 Driver in SR1
Keyword: LC/MS Driver
One-line Description:
Quad resolution during SIM mode (Wide & Widest).
Problem:
Quad resolution for Wide & Widest is not functional during SIM mode acquisition.
Temporary Solution:
n/a
Fix Information:
ESW 6.74.3
Keyword: LC/MS Driver
One-line Description:
New EM Horn caused estimate Gain to jump around with low abundance
Problem:
The new EM Horn caused estimate Gain to jump around with low abundance and missed target abundance.
Temporary Solution:
n/a
Fix Information:
Fixes in LC/MS 2.4 Driver and ESW 6.74.3
Keyword: LC/MS Driver
One-line Description:
527627 - Mass shifted issues on 400ms dwell time in Acquisition
Problem:
527627 - Mass shifted issues on 400ms dwell time in Acquisition. Users can't select 5K or 10K FastScan tune files to make the adjustment for 400ms dwell.
Temporary Solution:
n/a
Fix Information:
2.4.468.1 Driver in SR1
Keyword: LC/MS Driver
One-line Description:
Running Sequence with LC/MSD gets stuck in Not Ready
Problem:
When a method has a Dry Gas Temp @ 275C and another harsh Dry Gas Temp @ 350C. It takes longer to heat up setpoint. The Digital Signal Processor (DSP) in the SmartCard did not set to next method temp settings and sometime when running the alternative methods in the sequence. The driver already expect the next method temp settings, therefore, the system never gets ready in the sequence run sometime.
Temporary Solution:
n/a
Fix Information:
Fixed with LC/MS Driver 2.5 and Firmware 2.22.0
Keyword: LC/MS Driver
One-line Description:
Checktune fails when FastScan is checked
Problem:
Checktune fails when FastScan is checked because the Fastscan feature is only supported with Autotune.
Temporary Solution:
n/a
Fix Information:
Fixes in LC/MS 3.0 Driver
Keyword: LC/MS Driver
One-line Description:
Checktune Icon grayed out
Problem:
When dual polarity fastcan autotuning is completed on 61XXX LC/SQ the Checktune Icon grayed out. LC/MS Driver 3.0
Temporary Solution:
Users need to load a standard atune.tune files.
Fix Information:
fixed is future release.
Keyword: Localization
One-line Description:
Support of automatic Russian localization in OpenLab CDS v2.5 Update installer
Problem:
OpenLab CDS v2.5 Update 01 installer does not have Russian localization.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 02.
Keyword: Localization
One-line Description:
Concentration calculation formula is not reported correctly on Chinese version of OpenLab CDS 2.
Problem:
When concentration calculation is set to Amount * Multipliers * Dilution factor in the processing method, on the method report the formula will be shown as Amount * Multipliers / Dilution factor instead. This occurs only on the Chinese version of OpenLab CDS 2.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Localization
One-line Description:
Regional settings are not used in custom calculator implicit type conversions
Problem:
When accessing a custom field value in a custom calculation using CurrentSample.GetCustomField("Weight") the regional settings of the client PC are ignored, the "." is always used as a decimal separator. This can lead to incorrect values.
Temporary Solution:
CurrentSample.GetCustomField("Weight") returns a string. The workaround is to convert the string into a number using Val(string): Val(CurrentSample.GetCustomField("Weight")) The conversion will take the regional setting into account.
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Localization,Report Template Design
One-line Description:
Composite group saved with special character in the name
Problem:
In Intelligent Reporting, composite groups can be saved to facilitate further report design. These composite groups are saved in the data backend with the name the user typed in the reporting editor. Such composite group name must not contain any special character when using OpenLab CDS ECM 3.x as data backend. In the case special character are used, the composite groups will not be visible in the report editor.
Temporary Solution:
n/a
Fix Information:
Composite groups must be renamed without any special character.
Keyword: Performance
One-line Description:
Cannot start Data Analysis because it is bocked during "Initializing modules" step
Problem:
After importing ChemStation data three times and switching to back to Data Selection, Data Analysis freezes during the "Loading tree" state. If you end Data Analysis from Task Manager and then re-start Data Analysis, the program is frozen during the "Initializing modules" state.
Temporary Solution:
The workaround is to either 1) deactivate the proxy or 2) configure an exclusion for the Content Management (DataStore) server IP address in the proxy exceptions.
Fix Information:
n/a
Keyword: Performance
One-line Description:
WorkArea is not cleaned up on shutdown
Problem:
It has been observed that after a couple of workflow cycles (acquiring runs, doing data analysis, closing OpenLab CDS), the WorkArea that resides in C:\ProgramData\Agilent\SecureFileSystem folder is growing in size and not getting cleaned up on shutdown.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword: Performance
One-line Description:
New domain users can't access content management to save methods or any other file
Problem:
It has been observed in rare occasions that after adding new domain users or after editing roles and privileges of existing users, these users can't access the content management to save files or that new permissions are not taken. The alfresco.log file , usually located in C:\Program Files (x86)\Agilent Technologies\OpenLAB Data Store\tomcat\logs, will show the following error(s): " ERROR [org.quartz.core.JobRunShell] Job DEFAULT.ldapPeopleJobDetail threw an unhandled Exception: org.springframework.dao.DataIntegrityViolationException: No property value exists for ID <ID Number> " This issue is caused by the DEFAULT.ldapPeopleJobDetail and the propTablesCleanupJobDetail jobs running at the same time and leaving incomplete entries in two tables. These incomplete entries will prevent further automatic or manual synchronization with the content management database.
Temporary Solution:
As a temporary solution you can perform the following steps: 1. Delete the orphaned ID's in the datastore tables. These IDs are safe to delete as they do not contain any values/properties related to existing Chromatographic results or files. Use the Alfresco log to get the affected ID's and run the following SQL commands to remove them: DELETE FROM alf_prop_unique_ctx WHERE prop1_id = <ID> DELETE FROM alf_prop_root WHERE id = <ID> 2. Reconfigure the propcleaner job as implemented in version 2.3 to avoid the 2 jobs to run at the same time a) Edit the file C:\Program Files (x86)\Agilent Technologies\OpenLAB Data Store\tomcat\shared\classes\alfresco-global.properties b) Add the following 4 lines at the end of the file # Scheduled job to clean up unused properties from the alf_prop_xxx tables. # Default setting of "0 0 3 ? * SAT" is to run every Saturday at 3am. # Changed to run every Saturday at 3:03 am to avoid conflicting with OLSS sync that runs every 5 minutes. attributes.propcleaner.cronExpression=0 3 3 ? * SAT Note: There is a space after each character and after ? c) Restart AlfrescoTomcat Service
Fix Information:
This issue is resolved with OpenLab Server v2.3 and OpenLab ECM XT 2.3 by changing the schedule of the propTablesCleanupJobDetail job.
Keyword: Performance
One-line Description:
Internal server error when searching the System Activity Log
Problem:
An "Internal server error - timeout expired" error message can occur when searching the System Activity Log with a user and/or description filter. This occurs more frequently with large Activity Logs and when the system is busy with a high load on the database. This occurs because user and description filters are full text queries of the database which are less efficient than other filters. When the query takes too long, the software aborts the operation and displays the error. The error does not indicate any data integrity issue. CDS versions 2.1, 2.2, 2.3, and 2.4 are affected. As a temporary mitigation, perform routine database server maintenance including an update of database statistics and indexes. See the Guide for Administrators. This problem is corrected from OpenLab CDS 2.5 onwards.
Temporary Solution:
As a temporary mitigation, perform routine database server maintenance including an update of database statistics and indexes. See the Guide for Administrators.
Fix Information:
This problem is corrected in the 2.5 and 2.6 releases of OpenLab CDS.
Keyword: Performance
One-line Description:
Processing slowness
Problem:
For large sequences (500+) the reprocessing can get very slow for every additional line.
Temporary Solution:
n/a
Fix Information:
This is fixed in OpenLab CDS 2.4 Update 4 and OpenLab CDS 2.5.
Keyword: Performance
One-line Description:
SQL Server Database - 100% CPU Usage
Problem:
On heavily used OpenLab Server or ECM XT using Microsoft SQL Server 2014 or newer, the CPU can go to 100% making the system very slow and unusable. With Microsoft SQL Server 2014, Microsoft introduced a new mechanism to plan and execute queries and due to the new Cardinality Estimator (CE), certain type of queries slows down due to plan regression. Plan regression happens when SQL Server starts to use a sub-optimal plan to execute a query. This behavior impacts the CPU (or Memory) resources of the system.
Temporary Solution:
While the recommended weekly maintenance plan to update database statistics and rebuild indexes works for the majority of the OpenLab Server or ECM XT implementations, systems with many instruments and user sessions running concurrently or systems with high throughput instruments may need to increase the frequency of the “Update Statistics” maintenance plan to keep the SQL Server statistics up to date such that the plan regression does not occur. Queries involving the alf_prop_value and alf_prop_string_value tables will show plan regression as they are widely used by applications integrating with OpenLab Server or ECM XT such as OpenLab CDS Acquisition or OpenLab CDS Data Analysis. To bring back performance to normal 1. Review the currently implemented maintenance plan(s) on the SQL Server. 2. Check if the maintenance plan(s) is/are set as per our recommendation and adjust as needed. 3. Check when was the last time maintenance plan(s) got executed. If the 100% CPU on the SQL Server continues to appear: 4. Create an additional maintenance plan to update the statistics and rebuild the index [optional] of the alf_prop_value and alf_prop_string_value tables 5. Start with a twice a week schedule for the new plan and then to daily as the load to the system increases. Example(s): A > Weekly General Maintenance Plan scheduled to run on Sundays. B > Intermediate Maintenance plan for the alf_prop_value and alf_prop_string_value tables Day S M T W T F S S Plan A B B A Day S M T W T F S S Plan A B B B B B B A The other solution is to upgrade to Microsoft SQL Server 2017 Enterprise Edition or Microsoft SQL Server 2019 Enterprise edition and enable the Automatic Tuning feature. Upgrading Microsoft SQL Server may require an upgrade of the OpenLab Server or ECM XT application (see the Extra Information section for details) In response to the performance degradation observed with Microsoft SQL Server 2014 and 2016, Microsoft introduced a new feature in Microsoft SQL Server 2017 called Automatic Tuning that addresses plan regression automatically. The Automatic Tuning feature is only available with the Enterprise Edition. To enable Automatic Tuning on Microsoft SQL Server 2017 Enterprise Edition or Microsoft SQL Server 2019 Enterprise edition, run the following 3 statements: DBCC FREEPROCCACHE ALTER DATABASE [DataStore] SET QUERY_STORE = ON ( OPERATION_MODE = READ_WRITE, CLEANUP_POLICY = ( STALE_QUERY_THRESHOLD_DAYS = 90 ), DATA_FLUSH_INTERVAL_SECONDS = 900, QUERY_CAPTURE_MODE = AUTO, MAX_STORAGE_SIZE_MB = 1000, INTERVAL_LENGTH_MINUTES = 60, SIZE_BASED_CLEANUP_MODE = AUTO, MAX_PLANS_PER_QUERY = 200, WAIT_STATS_CAPTURE_MODE = ON ); ALTER DATABASE [DataStore] SET AUTOMATIC_TUNING ( FORCE_LAST_GOOD_PLAN = ON ); The weekly general maintenance as instructed in the OpenLab ECM XT Administration guide is still needed to update statistics and check index fragmentation. Additional Information: OpenLab Server / SQL Server Compatibility 2014 2016 2017 2019 v2.3 Y Y v2.4 Y Y Y v2.5 Y Y Y Y Microsoft Documentation: Additional Information on Database Statistics, Automatic Tuning and the Query Store database can be found at the following links: • https://docs.microsoft.com/en-us/sql/relational-databases/automatic-tuning/automatic-tuning?view=sql-server-ver15 • https://docs.microsoft.com/en-us/sql/relational-databases/statistics/statistics?view=sql-server-ver15 • https://docs.microsoft.com/en-us/sql/relational-databases/performance/best-practice-with-the-query-store?view=sql-server-ver15
Fix Information:
Upgrade SQL Server to 2017 Enterprise version and enable auto tuning
Keyword: Performance
One-line Description:
Performance issues in Data Analysis due to network interruptions during reprocessing
Problem:
Interruptions in the network connection during reprocessing data in Data Analysis might result in performance issues on a system with ECM 3.x as backend. Once the network connection is back, it might need some time until Data Analysis performs as expected.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Performance
One-line Description:
C:\ProgramData\Agilent\SecureFileSystem is growing significantly
Problem:
The folder C:\ProgramData\Agilent\SecureFileSystem contains the secure workarea for OpenLab products. When OpenLab ECM 3.X is used as a storage backend and the data is stored in SSIZIP format the cleanup process of temporary files within the workarea might fail. This leads to unlimited growth of this folder.
Temporary Solution:
n/a
Fix Information:
The issue is fixed in the following releases: OpenLab CDS 2.5 Update 05 OpenLab CDS 2.4 Update 10
Keyword: Performance
One-line Description:
Many log files created, opening Diagnostics node in OLCP is slow
Problem:
When selecting the Administration -> Diagnostics node in OLCP the application seems to freeze for a few minutes. This is caused be the high number of log files that are located in C:\programdata\agilent\logfiles
Temporary Solution:
Create a script that deletes all files in the folder C:\programdata\agilent\logfiles that are older than one month. Run this script each time the computer is started.
Fix Information:
n/a
Keyword: Performance
One-line Description:
Custom Calculation takes very long to be executed
Problem:
Using (Peak_Area - intercept )/ slope in Custom Calculation takes much longer than (Peak_Area - CurrentSequence.GetDoubleCC("intercept") )/ CurrentSequence.GetDoubleCC("slope") Slow expression: Question would be why this is faster than the below (42 secs on my machine):
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7
Keyword: Performance
One-line Description:
Active Directory query searches the entire forest and causes login slowness.
Problem:
In a multi domain environment, Active Directory queries are searching the entire AD Forest causing a slow login.
Temporary Solution:
n/a
Fix Information:
The application is now searching in the user domain first. A fix for this issue is available in OpenLab CDS v2.5 Update 08 and OpenLab CDS 2.6.
Keyword: Performance
One-line Description:
Control Panel Lab-At-A-Glance display of instruments is slow.
Problem:
In environments with many instruments, displaying the list of instruments can be very slow. The issue is caused by a permission check done for every instrument location and instrument for the connected user in the OpenLab Control Panel. This issue is affecting OpenLab CDS v2.4 and v2.5.
Temporary Solution:
n/a
Fix Information:
This issue is fixed with OpenLab CDS v2.7 and OpenLab CDS v2.5 update 08.
Keyword: Performance
One-line Description:
Control Panel freezes when many users launch Acquisition and Data Analysis at the same time in a client server system.
Problem:
When many users are launching Acquisition and Data Analysis sessions at once, the OpenLab Server / ECM XT Server performance can slow as the requests are processed. The user experiences slow performance or freezing of the Control Panel. The underlying cause of this performance symptom is that the Apache HTTPD employed by the Reverse Proxy server is configured by default to support 64 ThreadsPerChild/Sessions. Because of this, high-traffic Servers can slow-down or become unresponsive. To verify whether this is the cause of a system’s poor performance, review the error.log file located by default in C:\Program Files (x86)\Agilent Technologies\OpenLab Reverse Proxy\Apache24\logs for entries similar to those below: [Thu Nov 18 23:24:45.624673 2021] [mpm_winnt:error] [pid 26544:tid 2884] AH00326: Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting [Fri Nov 19 00:12:52.828373 2021] [mpm_winnt:notice] [pid 26488:tid 604] AH00422: Parent: Received shutdown signal -- Shutting down the server
Temporary Solution:
Please contact Agilent Support for Service Note D0015693 which contains detailed instructions on how to resolve this issue using a powershell script.
Fix Information:
n/a
Keyword: Performance
One-line Description:
SQL Parameter xact abort prevents Data from being uploaded
Problem:
SQL Server has a variety of settings to optimize the transaction behaviour of the Database. It turns out that if the parameter xact abort is checked in the SQL Server configuration a Data Upload to the ECM-XT/OpenLab Server is not possible anymore
Temporary Solution:
Recommendation is to set the xact abort value back to the default setting (not checked).
Fix Information:
The reason is that the Application needs to manage the transaction and do multiple updates within a single transaction, and by turning XACT_ABORT on, it hands the transaction management over to the database, which causes the error.
Keyword: Performance
One-line Description:
Improvements to address archive problems
Problem:
Archive tasks can take a long time to complete and consume a lot of memory, which can negatively impact system performance.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.5 Update 11 and OpenLab ECM XT 2.5 Update 06, as well as OpenLab CDS 2.7 and OpenLab ECM XT 2.7
Keyword: Performance
One-line Description:
Excessive logins can cause com.agilent.datastore.cache file to grow and impact performance
Problem:
Excessive logins to the web interface of content management by automated processes can cause the file C:\Program Files (x86)\Agilent Technologies\OpenLAB Data Store\tomcat\temp\com.agilent.datastore.cache to grow. This will affect startup performance of of the content management system.
Temporary Solution:
n/a
Fix Information:
No fix planned
Keyword: Performance
One-line Description:
Slow performance when blank subtracted signal gets manually integrated
Problem:
Slow performance when blank subtracted signal gets manually integrated with ECM 3.x backend.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS 2.7 Update 01 and OpenLab CDS v2.6 Update 08.
Keyword: Performance
One-line Description:
Slow performance when loading projects tab in Control Panel
Problem:
Slow performance when loading high amount of projects in Control Panel project tab
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 01.
Keyword: Performance
One-line Description:
Sample Scheduler Acquisition can get slower over the time with CDS 2.5, 2.6, 2.7
Problem:
Sample Scheduler uses the CDS Acquisition API which gets slower over the time depending on the number of connections made over the API. With a new connection to the instrument, a user change, or change of the CDS project, another registry entry gets written by the Diagnostics Dashboard under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Agilent\Diagnostics. With the growing amount of registry entries, the Acquisition API may get remarkable slower, depending on the overall system performance.
Temporary Solution:
Excessive registry entries created by the Acquisition API can be cleaned up by running following PowerShell script with Administrator privileges: $agenteCount = (get-process Agilent.OpenLAB.Acquisition.AcquisitionAgente* | measure-object).count if ($agenteCount) { Write-Host "Please first close your $agenteCount Agilent.OpenLAB.Acquisition.AcquisitionAgente process(es)" exit; } gci -path HKLM:\SOFTWARE\WOW6432Node\Agilent\Diagnostics\ | %{get-itemproperty -path $_.pspath} | ?{$_.application.Contains("AcquisitionAgente-")} | %{"Cleaning $($_.pspath)";remove-item -path $_.pspath }
Fix Information:
The problem will not occur in CDS 2.8 due to a change in the architecture. Fixes are planned in Updates for CDS 2.5, 2.6 and 2.7.
Keyword: Performance
One-line Description:
Duration of project creation is extremely long
Problem:
Creating a project in system that has a significant amount of projects (1000 or more) is seeing a significant performance degradation such that the creation can take several minutes.
Temporary Solution:
None
Fix Information:
This is fixed in CDS 2.5 Update 03 and higher
Keyword: Performance
One-line Description:
High CPU Load with ActivityLog disabled(SharedServicesHost/ApacheHTTPServer)
Problem:
High CPU Load with ActivityLog disabled(SharedServicesHost/ApacheHTTPServer)
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 01.
Keyword: Performance
One-line Description:
Unable to open method, sequence, and result files in Data Analysis
Problem:
It was observed on an OpenLab CDS client/server system where the CDS clients were installed on laptops that some larger result sets could not be opened in Data Analysis after they were acquired. Attempting to open one of these result sets would trigger an error message stating that the .acaml file has an invalid or missing checksum.
Temporary Solution:
n/a
Fix Information:
This issue is fixed OpenLab ECM XT 2.6 Update 06 / OpenLab CDS 2.6 Update 09 and in OpenLab Server 2.7 Update 06 / OpenLab CDS 2.7 Update 06.
Keyword: Performance
One-line Description:
OutOfDate is not reset after first instrument's data is read (multi-instrument)
Problem:
On OpenLab CDS AICs with multiple instruments configured, there is the possibility that instrument replication for failover will fail for all instruments if there is an error in the first instrument's replication.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab Server 2.8, OpenLab CDS v2.8, OpenLab Server 2.7 Update 04 and OpenLab CDS 2.7 Update 04.
Keyword: Performance
One-line Description:
Loading Sequence from result set takes >1 minute for Browse box to appear
Problem:
In OpenLab CDS Acquisition when using OpenLab ECM 3.x as the configured storage type, it can take over one minute for the Browse window to be displayed when attempting to load a sequence from a result set.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab Server 2.8, OpenLab CDS v2.8, OpenLab Server 2.7 Update 04 and OpenLab CDS 2.7 Update 04.
Keyword: Performance
One-line Description:
OpenLab Shared Services Crashes frequently
Problem:
On systems with large numbers of entries in the System Activity Log, instabilities in OpenLab Shared Services and the OpenLab Control Panel could lead to the system crashing. This would cause all user sessions to disconnect and for any currently running or queued samples to be acquired in Failover mode.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab Server 2.8, OpenLab CDS v2.8, OpenLab Server 2.7 Update 04 and OpenLab CDS 2.7 Update 04.
Keyword: Performance
One-line Description:
Unable to process result sets with big ACAML files from Terminal Server
Problem:
It was observed on systems using thin CDS clients installed on a Terminal Service that large .acaml files (~200MB) can get stuck in the File Upload Queue when reprocessing result sets with the error message: "A system error occurred while uploading a file. Please contact the system administrator."
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.6 Update 11, OpenLab ECM XT 2.6 Update 08, OpenLab CDS 2.7 Update 06, and OpenLab Server 2.7 Update 06.
Keyword: Performance
One-line Description:
Unable to load a single run from DA search results
Problem:
OpenLab CDS Acquisition provides users the option to save Sequence results as separate single injections. When attempting to load a single injection result acquired in this manner from search results in the Data Selection view of OpenLab CDS Data Analysis, the following error may be triggered: "Error loading data: Could not find a part of the path..."
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS 2.8 Update 03 (only affects Workstation Plus systems) and OpenLab Server 2.8 Update 03.
Keyword: Performance
One-line Description:
Data will not open with a ' or ˚ character in the path
Problem:
When attempting to load data in OpenLab CDS Data Analysis with a ' or ˚ character in the result set folder name or path, the following error will occur: "Error loading data: Download failed because storage location is not accessible."
Temporary Solution:
Remove the ' or ˚ character from the result set folder.
Fix Information:
This issue is resolved in OpenLab CDS 2.8 Update 03 (only affects Workstation Plus systems) and OpenLab Server 2.8 Update 03.
Keyword: Performance
One-line Description:
Activity Log indexing paused when HDD space is low
Problem:
Activity Log indexing is suspended when the application server's primary disk reaches 95% capacity. No new logs will be shown in the Control Panel. However, activity logs are still written to the database.
Temporary Solution:
n/a
Fix Information:
Resolve the low disk space issue and indexing will resume. Starting in OpenLab CDS 2.8 Update 03 and OpenLab Server 2.8 Update 03, the following error message will be displayed in the Administration>System Activity Log page of the Control Panel when indexing has been suspended: "Unable to retrieve activity logs. This is likely due to the OpenSearch Index server reaching 95% disk consumption. Please free up space to allow the retrieval of activity logs."
Keyword: Performance
One-line Description:
Leading/trailing spaces trigger an "Import data failed" error when importing data in DA
Problem:
When using OpenLab ECM 3.x as a backend, an "Import data failed" error can occur when importing a .olax result set in OpenLab CDS Data Analysis containing files with either a leading or trailing space.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab Server 2.7 Update 08 and OpenLab CDS 2.7 Update 08.
Keyword: Performance
One-line Description:
OpenLab v2.8 cannot be uninstalled after installing Update 02
Problem:
After installing OpenLab CDS 2.8 Update 02 or OpenLab Server 2.8 Update 02, uninstalling the application will fail when attempting to remove the Agilent OpenLab SDMS Action Service.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.8 Update 03 and OpenLab Server 2.8 Update 03.
Keyword: Performance
One-line Description:
OpenLab Server 2.8 Update 03 is not backward compatible with older clients
Problem:
After installing OpenLab Server 2.8 Update 03 on an OpenLab Server / ECM XT 2.8 server, all clients/AICs/networked workstations not running on OpenLab CDS 2.8 Update 03 or OpenLab Client Services 2.8 Update 03 are unable to connect to the storage provider.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab Server 2.8 Update 04 and OpenLab CDS 2.8 Update 04.
Keyword: Performance,Roles and Privileges
One-line Description:
New domain users can't access content management to save methods or any other file
Problem:
New domain users can't access content management to save methods or any other file and Synchronize in OpenLab Control Panel fails.
Temporary Solution:
As a temporary solution you can perform the following steps: 1. Delete the orphaned ID's in the datastore tables. These IDs are safe to delete as they do not contain any values/properties related to existing Chromatographic results or files. Use the Alfresco log to get the affected ID's and run the following SQL commands to remove them: DELETE FROM alf_prop_unique_ctx WHERE prop1_id = <ID> DELETE FROM alf_prop_root WHERE id = <ID> 2. Reconfigure the propcleaner job as implemented in version 2.3 to avoid the 2 jobs to run at the same time a) Edit the file C:\Program Files (x86)\Agilent Technologies\OpenLAB Data Store\tomcat\shared\classes\alfresco-global.properties b) Add the following 4 lines at the end of the file # Scheduled job to clean up unused properties from the alf_prop_xxx tables. # Default setting of "0 0 3 ? * SAT" is to run every Saturday at 3am. # Changed to run every Saturday at 3:03 am to avoid conflicting with OLSS sync that runs every 5 minutes. attributes.propcleaner.cronExpression=0 3 3 ? * SAT Note: There is a space after each character and after ? c) Restart AlfrescoTomcat Service
Fix Information:
The application has a job to clean obsolete property values in the database (Prop Cleaner Job) and one to synchronize users from LDAP to the Content Management (User Sync Job). The Orphan Property ID issue occurs when the Prop Cleaner Job runs at the same time as (or within close time proximity of) the User Sync Job, resulting in deletion of property values that should not have been deleted and causing dangling references inside the database that prevents the application from doing further user synchronizations. This issue affects the following Products and Versions: OpenLab CDS v2.2, v2.3 and v2.4 OpenLab Server v2.2, v2.3 and v2.4 OpenLab ECM XT v2.2, v2.3, and v2.4
Keyword: Project Configuration
One-line Description:
Insufficient validation when configuring a project's folder path
Problem:
When creating a Project in the Control Panel, the Project folder path can be set to the system's configured root Storage path. When this is done, it is impossible to launch OpenLab CDS Acquisition or Data Analysis for this project and no new projects can be created.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS 2.8 Update 03 (only affects Workstation Plus systems) and OpenLab Server 2.8 Update 03. If a user attempts to configure a project's folder path as the root storage path, an error message stating that the project folder is not allowed will be displayed.
Keyword: Report Generation
One-line Description:
Report generation to .doc file format containing the method information may lead to a very long report containing blank spaces
Problem:
The export to .doc file format when generating the report containing the (acquisition or processing) method information can be long and contain blank spaces.
Temporary Solution:
This issue is fixed in OpenLAB CDS 2.1
Fix Information:
There is no temporary fix
Keyword: Report Generation
One-line Description:
Trend Micro OfficeScan will prevent OpenLAB CDS to report instrument traces
Problem:
When using Trend Micro OfficeScan, using a report template that reports the instrument traces, the OpenLAB CDS v2.x will close triggered by the anti-virus services. This will be correctly logged in the Trend Micro OfficeScan logs.
Temporary Solution:
Do not use Trend Micro OfficeScan on the PC that reports the instrument traces.
Fix Information:
N/A
Keyword: Report Generation
One-line Description:
Blank spaces may be seen in CDS 2.1 on report printout
Problem:
Blank spaces may be seen in CDS 2.1 on report templates that uses filters in report template. Blank spaces can be seen in the area where the report item is filtering on a specific or several value.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLAB CDS v2.2. All blank spaces observed previously will be gone.
Keyword: Report Generation
One-line Description:
Overlapping library search spectra plot when saving the report as doc and xls file formats
Problem:
Spectra from the MS library search results will appear not properly scaled when printing or saving a report to XLS or DOCX. The spectra will be under-sized on the left side of the page layout This affects only the report template of NIST library search results.
Temporary Solution:
Use PDF, or manually resize the spectra in the XLS or DOCX output files.
Fix Information:
This will be fixed in CDS 2.2
Keyword: Report Generation
One-line Description:
Report template migration to OpenLAB CDS 2.1
Problem:
The below issue is specific to report template migration from any Intelligent Reporting revision (including OpenLAB CDS 2.0) to OpenLAB CDS 2.1 Intelligent Reporting. This is related to the previously published issue below: "No report generated when the expressions are not completed or correct" In the case an expression as described in the above publication was edited in the original report template, such as: =Sequence_Description = "SST01" If the sequence description does not contain anything, the report generation will fail, and no report will be generated. This is a known issue of OpenLAB CDS 2.1 and will be fixed in OpenLAB CDS 2.2. The report template will remain functional if the sequence description contains a value.
Temporary Solution:
Change the corresponding expressions using conversion functions: " =CStr(Sequence_Description) = "SST01" " Conversion functions are recommended to evaluate the result of an expected value with the value captured during the analysis. Examples: CSt() converts any type of value to string Val() converts any type of values to double
Fix Information:
This issue is fixed in OpenLAB CDS v2.2.
Keyword: Report Generation
One-line Description:
EIC may disappear when using the option "report only selected signals"
Problem:
When using the new OpenLAB CDS v2.2 feature "report selected signals", the EIC signal results may disappear in certain circumstances. This happens in case the injection or all injections had been reprocessed, and the report generated without changing of injection line.
Temporary Solution:
Change of injection in the injection selection tree, and then come back to the desired injection line. The report will show EIC results.
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword: Report Generation
One-line Description:
Incorrect value displayed in Reporting for compound custom parameter containing blank spaces
Problem:
If the compound custom parameter value has blank spaces, then in Reporting the blank spaces appears as "&esdp;&esdp;".
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword: Report Generation
One-line Description:
Certain report generation steps will lead to report the previous version of the result set
Problem:
This note applies for report manually generated from the reporting tab in Data Analysis after a change of the results by reprocessing the injections (without saving the results). In this manual workflow, if the results were not saved in data analysis before switching to the reporting tab, the previous result set version will appear in the report generation (as a preview, as a report saved, or printed report). This does not apply for unattended report generation from acquisition or Data Analysis (with a processing method linked to the results, and having a report selected in the method report section).
Temporary Solution:
Save the results in the Data Analysis tab before switching to the Reporting tab for manual report generation, or consider using the unattended report generation from Acquisition or Data Analysis
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword: Report Generation
One-line Description:
Theoretical plates USP not reporting the correct value for Chinese/Japanese/Portuguese CDS versions
Problem:
The Theoretical plates USP field used in a report template does not show the correct value for localized CDS versions. This is due to a mismatch between the reporting field and the actual injection file results.
Temporary Solution:
Not available from customer ends. In case of urgent need, contacting the local Agilent support center can help in resolving the issue.
Fix Information:
This will be fixed in OpenLAB CDS v2.3
Keyword: Report Generation
One-line Description:
Misleading data file directory path for results moved from one project to another
Problem:
This issue refers to result set that had been manually moved from one project to another. Different location paths for injections belonging to the same result set will be reported when using the reporting field "injection data file directory": The first acquired injection will show the actual data path directory from the project where it had been moved to. All further injections will show the data path directory from the acquisition project (initial location when acquired). Note: the data file directory is an information written in the result set data files only after reprocessing the related data. If no reprocessing had been performed after the result set had been moved from the initial project location to a new project, the data file directory reported will be the initial project directory for all injections.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.3.
Keyword: Report Generation
One-line Description:
With some result sets the chromatogram peak drawing may fail
Problem:
The below described issue is closely linked to integration events and relates to chromatogram drawing, with a low issue reproducibility probability. In some cases, the detector raw data points may be missed in report generation. For concerned data, the issue will be always reproducible. As results, the chromatogram would look as following: - Baseline time windows (chromatogram areas without any integrated peak) would remain blank without signal trace drawn. - Peak would be seen as flat lines at the signal baseline height.
Temporary Solution:
Solution 1 in Data Processing: Change the Integration parameters of the processing method. We have observed the problem with the EZChrom integrator. Adjusting the peak width value can solve the issue. Solution 2 in reporting: Concerned data can be reported by editing the report template. In the reporting tab in Data Analysis, select the editor layout, and load the desired report template. Right-click in the chromatogram plot report item, and click on "Properties". In the "Peak Labels" tab, scroll down to the "Peak Markers" section, and uncheck the checkbox "Show Baseline". Once done, click "ok" in the properties dialog window, save the report template, and generate the report for the data that was affected by this issue.
Fix Information:
This is issue is affecting OpenLab CDS v2.3 and earlier revisions. It will be fixed in OpenLab CD v2.4.
Keyword: Report Generation
One-line Description:
Report template file path is missing when generating reports in Reporting View
Problem:
Reports generated in the Reporting view of OpenLab Data Analysis will display only the name of the report template in the footer. The full path is missing. Reports printed with the "Print All" function in Data Processing view show the full path of the report template in the footer.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5
Keyword: Report Generation
One-line Description:
Report not generated when copied to Windows file system with ECM 3.x back end
Problem:
It might be that a report in a sequence with a processing method with the setting copy reports to folder "Windows File System" will not be generated.
Temporary Solution:
Use UNC path and ensure the selected path exists on all machines used to process data with this method, including instrument controllers.
Fix Information:
n/a
Keyword: Report Generation
One-line Description:
Reporting spectra legend in reporting
Problem:
When extracting UV or MS spectra as defined in Data Analysis processing method, the legends will show "Corrected" above the spectra. This labels may be misleading especially when using background subtraction. The "Corrected" annotation only means the spectra is not a simple extraction from the raw data, but the spectra extraction based on the processing method settings.
Temporary Solution:
n/a
Fix Information:
The spectra legend will be modified in OpenLab CDS v2.5 and future software version. When using background subtraction, the legend will be: "Subtracted". If no background subtraction is used, the legend will not show any annotation.
Keyword: Report Generation
One-line Description:
Report printout may show more method set points if reloaded
Problem:
Report generation after processing and reprocessing will show the following method set points for chromatogram smoothing: "Smoothing algorithm", "Number of points", Number of passes" If the results are closed and reopened, the method information report will only show the following set point: "Smoothing algorithm" without more details As this may affect results documentation and results documentation review, this known problem report entry can be used to document the deviance.
Temporary Solution:
n/a
Fix Information:
The method reporting will be modified in OpenLab CDS v2.5 to show results consistency in both scenarios described above.
Keyword: Report Generation
One-line Description:
Empty fields in the report of imported OpenLAb CDS EZChrom Edition data in OpenLab CDS
Problem:
If OpenLAb CDS EZChrom Edition data gets imported into OpenLab CDS some information will not be on the report. Following data cannot be reportet at the moment: •Instrument Name •Sample Description •Injection Volume •Sample Amount •Vial Number •Acq method version •Acq software •Product Name •Software Build •Software Version
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 Update 08.
Keyword: Report Generation
One-line Description:
Timed group calibration correlation factor not printed in reports
Problem:
The calibration correlation factor is not printed in reports for timed groups even if this factor can be observed in Data Analysis calibration curve statistics.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in OpenLab CDS v2.5 and future releases.
Keyword: Report Generation
One-line Description:
Specific report generation workflow can lead to print previous results version
Problem:
This issue relates to report generation using the print button in the reporting tab. It does not apply to unattended report generation from Acquisition, Data Analysis, or save as buttons in the reporting tab. Workflow leading to print the previous report version: - The results are reprocessed and saved in Data Analysis, generating a first results version. - The report is manually generated in the "Reporting" tab, using the refresh button. - In "Data Processing" tab, the results are reprocessed and saved a second time. - The first results version would be printed If the report is generated using the print button in the "Report Preview" window, and without refreshing the report preview.
Temporary Solution:
To see the newly created results version, the report must be refreshed in the reporting tab before using the print button.
Fix Information:
This is issue will be fixed in OpenLab CDS v2.5.
Keyword: Report Generation
One-line Description:
Quantified point may be not be drawn correctly using log/log calibration curve
Problem:
This issue only relates to quantified point drawing on calibration curve plot using a log/log calibration type. In the case the amount logarithm is greater than 0, points may not be drawn correctly on the calibration plot.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in OpenLab CDS v2.3 update 11, OpenLab CDS v2.4 Update 07, OpenLab CDS v2.5 and later versions.
Keyword: Report Generation
One-line Description:
Reporting matrix not correctly exported to csv report output
Problem:
Reporting matrix snippet contain multiple column or row headers. If this type of data can be exported to excel, CSV export of matrices will result of a misleading cell alignment due to the mentioned header configuration. Opening the csv file in excel will show cell content not belonging to the proper column.
Temporary Solution:
If use of matrix, all formats excluding csv format should be used for report output. If csv report output is needed, a table should be used to export results.
Fix Information:
This will be fix in a future release by adding new matrix snippet.
Keyword: Report Generation
One-line Description:
Printing, locking and signing of unsaved data if two users load the same result set and modifying it
Problem:
In case a result set gets loaded by 2 users at the same time and user 1 is generating a new version (processing and saving the data) user 2 can print unsaved data of the previous version. User 1 and User 2 are loading the same result set (version A). User 1 processes and saves data. This generates a new version of the result set (version B) User 2 has still version A of the result set loaded. After processing this data user 2 wants to print the result set. A message informs the user that the unsaved data cannot be printed and asks if user 2 wants to save the data. If user 2 saves the data OpenLab CDS detects a new version (version B from user 1) and is asking user 2 if the never version should be overwritten. If user 2 cancels this message the data is not saved but will be printed. Same is for locking and signing.
Temporary Solution:
Avoid loading and modifying the same result set by different users at the same time
Fix Information:
This is fixed in OpenLab CDS 2.5
Keyword: Report Generation
One-line Description:
Cannot preview report for ion chromatogram snippets or default templates on Chinese and Portuguese systems
Problem:
It is not possible to preview report for ion chromatogram snippets or default templates on Chinese and Portuguese OpenLab CDS v2.4 systems. This issue does not occur in OpenLab CDS v2.5.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 Update 07.
Keyword: Report Generation
One-line Description:
Shimazu GC column oven temperature not reported
Problem:
In OpenLab CDS v2.4 and further releases, the column oven temperature is not reported with Schimadzu GC instruments.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Report Generation
One-line Description:
It is not possible to preview report using the default template "Purity_Flow.rdl" on Chinese and Portuguese OpenLab CDS v2.4
Problem:
Error occurs when user previews the report using the default template "Purity_Flow.rdl". This happens only on localized OpenLab CDS v2.4 (Both Chinese and Portuguese).
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 Update 08.
Keyword: Report Generation
One-line Description:
Report will not be generated when using default processing method "GC/LC Norm Percent"
Problem:
The default processing method "GC/LC Norm Percent" has preselected reports in the injection report section. NormAmount.rdl and NormAmount_Letter.rdl are preselected and will be stored as file. These are default report templates. If the default report templates are not imported the method will not find the preselected templates and cannot create a report.
Temporary Solution:
Import the default report templates before using the GC/LC Norm Percent method. Or select another report when creating a processing method based on this default method.
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 4
Keyword: Report Generation
One-line Description:
Unattended Processing Client throws an exception when it cannot find the report template specified in the processing method and the run will be aborted
Problem:
Unattended Processing Client throws an exception when it cannot find the report template specified in the processing method and the run will be aborted. This will be reported as an hardware error.
Temporary Solution:
Ensure the report template which is specified in the processing method is available in the report templates folder.
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Report Generation
One-line Description:
A failed automated printout error is logged in category "Configuration" and not "Instrument"
Problem:
When a printout during acquisition fails and entry is made to the OpenLab System activity log. The category for this event is "Configuration". This event will not show up in the pre-filtered activity log for each instrument.
Temporary Solution:
When troubleshooting problems always check the System activity log and not the pre-filtered instrument log.
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Report Generation
One-line Description:
MS profile spectra not correctly labelled
Problem:
MS Spectra are reported in the spectra plots with too many ion peak labels for data acquired in profile mode.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 09.
Keyword: Report Generation
One-line Description:
Performance of report generation decrease with added pressure plot
Problem:
Adding a pressure plot to the report might result in an increase of time to generate the report.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and OpenLab CDS v2.5 Update 11.
Keyword: Report Generation
One-line Description:
Summary calculation update for calibration curves
Problem:
Summary calibration curve results, such as residual are saved per compound in the processing method (master method or result set method) and results. This issue relates to cases where calibration curve results and summaries were performed with a calibration averaging results per level, and used later on in another result set with calibration with individual points. In such cases, the calibration curves, determination and correlation coefficients will be correctly computed, and all resulting unknown calibration results will be accurate. However, the residual standard deviation will appear incorrect in report printouts. This is due to persisting calibration level standard deviation results in the method and results.
Temporary Solution:
Persisting results saved for the average per level would need to be cleared from the calibration curves summary: - Using bracketing modes, clear calibration at level or clear all calibration in the injection list. - Compound expected signal can be changed to delete the previous calibrations. - Deleting and adding affected compound to processing method will also clear all results from method and results. Note. data needs to be reprocessed to update methods and results.
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Report Generation
One-line Description:
Calibration curve not reported
Problem:
Calibration curves having the origin set to connected in Data Analysis are not reported in OpenLab CDS v2.5. This issue only impact reporting, and does not change the calibration results.
Temporary Solution:
All other calibration curve origin types can be correctly reported.
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Report Generation
One-line Description:
Reprocessing with custom calculation enabled fails with an exception
Problem:
In case of duplicated Intelligent Reporting custom assembly functions present in the OpenLab reporting binaries. the reprocessing of any data file with a method that included a custom calculation does always fail with an error: An unexpected error occurred during processing of 'CustomCalculationTransformation" Index was outside the bounds of the array. This is caused when two custom assemblies (DLL's) located in C:\Program Files (x86)\Agilent Technologies\OpenLab Data Analysis\bin\Reporting\IntelligentReporter\ Define the same function twice.
Temporary Solution:
Ensure no two custom assemblies dll's define the same function twice. Specifically do not keep older versions of Dll's in the custom dll directory of the Intelligent reporter.
Fix Information:
n/a
Keyword: Report Generation
One-line Description:
Mass Abundance value in Report Spectra incorrectly shown as two decimal value
Problem:
Mass Abundance value in Report Spectra incorrectly shown as two decimal value
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 08.
Keyword: Report Generation
One-line Description:
Cannot report Peak_tail_Factor and Asymmetry 10 Perc when in Russian
Problem:
Cannot report Peak_tail_Factor and Asymmetry 10 Perc when in Russian.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 Update 08.
Keyword: Report Generation
One-line Description:
Error occurred during report rendering due to ‘&’ special character in data file name
Problem:
An error occurred during report rendering. The report cannot be processed.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in: OpenLab CDS v2.7 OpenLab CDS v2.6 Update 01 OpenLab CDS v2.5 Update 08 OpenLab CDS v2.4 Update 11 OpenLab CDS v2.3 Update 13
Keyword: Report Generation
One-line Description:
Sometimes when using the contour plot 2D item on reporting an exception occurs
Problem:
Sometimes when using the contour plot 2D snippet an exception will be raised on the preview.
Temporary Solution:
n/a
Fix Information:
This issue is fixed on OpenLab CDS 2.7.
Keyword: Report Generation
One-line Description:
Corrected expected retention time fields for 2DLC are not available in reporting
Problem:
A "corrected expected retention time field for 2DLC" is not available in reporting, neither under "Peak", nor "Compound", but existing in the injection result.
Temporary Solution:
n/a
Fix Information:
With OpenLab CDS 2.7 a field "Corr Exp Ret Time" will be available on the reporting section.
Keyword: Report Generation
One-line Description:
2DLC: do not display lost cuts in chromatograms
Problem:
The Chromatograms report items used by the 2DLC addon is showing cut annotations. These cut annotations should not be displayed for "lost cuts".
Temporary Solution:
n/a
Fix Information:
Fixed with OpenLab CDS v2.6 Update 02
Keyword: Report Generation
One-line Description:
Incorrect translation in CHS Data Dictionary
Problem:
Incorrect translation in CHS data dictionary for COMPOUND_EXPECTEDRETTIME2D which has a whitespace within the translation.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS v2.6 Update 02
Keyword: Report Generation
One-line Description:
Values of deactivated fields are listed on the Method Report
Problem:
Values of deactivated fields like Manual Factor or Ref. Correction might be listed on the Method Report.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Report Generation
One-line Description:
MS profile spectra not correctly labelled
Problem:
MS Spectra are reported in the spectra plots with too many ion peak labels for data acquired in profile mode.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Report Generation
One-line Description:
An issue occurs when a custom parameter and a variable are used in same expression at the same time
Problem:
When an expression contains both, a custom parameter and a variable, there is nothing in the expression editor except the "=" entry on reloading the template and editing the expression. The template itself is unaffected and will generate reports as expected.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Report Generation
One-line Description:
Show 2DLC cut annotations not working
Problem:
The 2DLC cuts are not shown, even the checkbox on "show 2DLC cut annotations" is checked.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed on OpenLab CDS 2.7.
Keyword: Report Generation
One-line Description:
Report templates cannot be used on Chinese system
Problem:
Generating a report with following report templates might have issues on Chinese systems: 1. GCMS_Unknown_Analysis_Long 2. GCMS_Unknown_Analysis_Long_Letter 3. MS_Quantitative_Long.rdl 4. MS_Quantitative_Long_Letter.rdl 5. MS_Quantitative_Short.rdl 6. MS_Quantitative_Short_Letter.rdl
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS v2.6 Update 02 and OpenLab CDS v2.7.
Keyword: Report Generation
One-line Description:
No result set version is printed on injection reports automatically generated during acquisition
Problem:
In OpenLab CDS 2.3 and 2.4, no result set version will be printed on injection reports that are automatically generated during acquisition.
Temporary Solution:
N/A
Fix Information:
This issue is resolved in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 11.
Keyword: Report Generation
One-line Description:
Difference in Date an Time between pre-viewed PDF report and saved PDF report
Problem:
If a report gets saved as PDF after previewing it in reporting, the Date and Time stamp is different from the previewed report.
Temporary Solution:
n/a
Fix Information:
When a report gets saved as PDF, it gets regenerated, so it automatically gets a new time stamp.
Keyword: Report Generation
One-line Description:
Search result limitation not working as expected using multiple libraries
Problem:
On searching through different libraries with the goal to find the 3 closest matches, limiting the search results to 1 result on the Library Search results, e.g. using "Hit table.rdl", search returns the number of hitson each library, but not the number of search results.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Report Generation
One-line Description:
Using the Single Acquisition Method Parameter snippet, many 1220 parameters are reported as unavailable
Problem:
When using the "Single Acquisition Method Parameter_ snippet", many "G4290B parameters" are reported as unavailable on the report preview. For data acquired using a 1220 Infinity II LC system, only few acquisition parameters can be reported using the "Single Acquisition Method Parameter_ snippet".
Temporary Solution:
n/a
Fix Information:
Issue has been fixed on OpenLab CDS v2.7 and OpenLab CDS 2.6 Update 05.
Keyword: Report Generation
One-line Description:
Slow performance when saving a sequence summary report with ECM 3.x integration
Problem:
When a user loads a result set, going to to "Reporting", selecting a canned reporting template, it takes long time for the "Save as" dialog to come up on clicking "save as .xlsx".
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.7, OpenLab CDS 2.6 Update 05 and OpenLab CDS 2.5 Update 09.
Keyword: Report Generation
One-line Description:
Adverse scale marking causes poor readability
Problem:
In certain report template configurations the X axis scaling becomes 0.25 minutes, which causes poor readability.
Temporary Solution:
A workaround is to re-scale the chromatogram window on the editor. By shrinking it a bit, the interval will be adjusted. Another possibility would be to adjust the interval itself.
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Report Generation
One-line Description:
Scaled response value of a timed group is listed on a report as area
Problem:
The scaled response value of a time group (which is displayed in DA in the corresponding column) will be shown as an area along with the areas of other compounds on the report.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Report Generation
One-line Description:
An error occurs when a generated pdf report is opened using Acrobat Reader
Problem:
Opening a pdf report, generated from a before created new report template using Acrobat Reader (Acrobat DC 2021.011.20039) shows an error message in some cases: "An error exists on this page. Acrobat may not display the page correctly"
Temporary Solution:
Using Microsoft Edge or Google Chrome for opening the pdf generated, does not show the error seen on Acrobat Reader (Acrobat DC 2021.011.20039).
Fix Information:
This issue is fixed in OpenLab CDS v2.8 and OpenLab CDS 2.7 Update 01.
Keyword: Report Generation
One-line Description:
"EngineFormatNumber" issue shows up using the reporting editor
Problem:
This issue showed up on editing very complex intelligent reports after migrating them from OpenLab EZChrom to OpenLab CDS 2.6 The technical reason is, that on VB.net the format number expression can have up to 4 parameters. Some of them are optional. In the given issue, some of those parameters are given as expressions. But the template editor, when opening the template, could not parse the complete expression (since it was expecting to have a different parameter type, than an expreession).
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 07.
Keyword: Report Generation
One-line Description:
Some default Document Templates failed to open if system language is Japanese
Problem:
Some default Document Templates failed to open if system language is Japanese
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.7 and OpenLab CDS v2.6 Update 09.
Keyword: Report Generation
One-line Description:
MS Spectrum from UV/GC peak snippet sometimes displays No spectra available
Problem:
In the MS Spectrum from UV/GC peak snippet, if a MS signal name has been saved to the template under the MS TIC Signal for Spectrum Extraction setting, the template will only display a spectrum from that signal. If this template is saved and used on another injection which does not contain that signal, no spectrum is displayed.
Temporary Solution:
Delete the snippet and readd it. Do not select any signal from the drop-down list under MS TIC Signal for Spectrum Extraction in the newly added snippet; the report will default back to the using first TIC of the current data file.
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 02.
Keyword: Report Generation
One-line Description:
Report cannot be previewed
Problem:
In case an expression is used to set the number of digits based on the context, it might lead to an error when previewing the report.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02, and OpenLab CDS v2.6 Update 08.
Keyword: Report Generation
One-line Description:
MS Spectra sometimes not reported as expected with positive/negative switching data
Problem:
In CDS 2.7 and earlier, there are two options for Peak Spectra Selection on the MS Spectrum snippet: Custom - Peak Apex (uncorrected) or Same As Data Analysis. If Custom - Peak Apex (uncorrected) is selected, and the report is run on positive/negative switching data, in some cases the integrated peak will be on the positive signal, but the spectrum on the report is extracted from the negative signal (or peak can be on the negative signal and the spectrum is extracted from the positive signal). If Same as Data Analysis is selected, the correct spectra are reported, but the peak labeling is not working as expected.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 11.
Keyword: Report Generation
One-line Description:
MS Library Search snippet can display the incorrect spectrum under certain conditions
Problem:
In CDS 2.7 and earlier, only library search results from automatically extracted spectra can be reported in Intelligent Reporting. Manually extracted spectra can be extracted and viewed in data processing but will not be reported. However, if one of those manually extracted spectra is located inside the boundaries of an integrated peak with library search results, and a specific sequence of processing, manual extractions, and reprocessing is followed, the MS library search snippet may display the manually extracted spectrum on the report, instead of the automatically extracted one. The library search results (peak retention time, library match score and hit information, library spectrum) will still be the results pertaining to the automatically extracted spectrum.
Temporary Solution:
Remove any manually extracted MS spectra which are within the integrated area of the peak for which the automatically extracted spectrum is to be reported before generating the report.
Fix Information:
This issue got fixed in OpenLab CDS v2.7 Update 02 and OpenLab CDS v2.6 Update 09.
Keyword: Report Generation
One-line Description:
Rendering process hangs and consumes memory until it reached system limits
Problem:
If a single table row exceeds the available space on a page, the rendering process hangs and memory consumption rises until it reached the system limits.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 03.
Keyword: Report Generation
One-line Description:
Peak labels cannot be changed to no label in chromatography properties
Problem:
Peak labels cannot be changed to No Label in chromatography properties.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8.
Keyword: Report Generation
One-line Description:
Aggregators return wrong values if visibility of table is controlled by an expression
Problem:
Aggregators return wrong values if visibility of table is controlled by an expression
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Report Generation
One-line Description:
Reports generated automatically when the ASR post-processing plugin is enabled show rendering issues for Max WL and Total WL UV chromatograms
Problem:
Reports which are generated in an unattended automatic workflow during data acquisition while the ASR post-processing plugin is enabled in the processing method may show rendering issues on Max WL and Total WL UV chromatograms.
Temporary Solution:
Regenerate reports from Data Analysis or disable ASR post-processing plugin if not needed.
Fix Information:
This issue is resolved in CDS 2.7 Update 03 and CDS 2.6 Update 10.
Keyword: Report Generation
One-line Description:
Rendering MS Spectra in Overlaid mode increases rendering time
Problem:
Rendering MS Spectra in Overlaid mode increases rendering time
Temporary Solution:
Setting the option "n-largest peak filter (1-255)" to 100 on the MS Spectra Plot.
Fix Information:
n/a
Keyword: Report Generation
One-line Description:
Ions may be mislabeled in deconvolution snippet graphics
Problem:
In the deconvolution report snippets, when an ion is associated with two or more ion sets, it can be displayed in the graphics with only one label or with an incorrect label. It will be labeled correctly in the detail table, and in Data Analysis.
Temporary Solution:
Print the detailed data as a table, then all components can be seen in the report.
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 02.
Keyword: Report Generation
One-line Description:
Arbitrary profile MS spectra in data imported from ChemStation are not displayed in the report
Problem:
Arbitrary profile MS spectra in data imported from ChemStation are not displayed in the report.
Temporary Solution:
n/a
Fix Information:
The issue is resolved in OpenLab CDS v2.8 Update 02.
Keyword: Report Generation
One-line Description:
Arbitrary spectra are not associated with a peak if integration is added after the spectrum has been manually extracted
Problem:
If a spectrum is extracted manually before a peak is integrated, or if the peak's integration is removed and reperformed once the spectrum already exists, the spectrum becomes an arbitrary spectrum for reporting purposes. The spectrum does not revert back to manual if the integration is added after the spectrum has already been manually extracted.
Temporary Solution:
To re-associate an existing spectrum with a peak, re-extract the spectrum once the peak is integrated.
Fix Information:
The issue is resolved in OpenLab CDS v2.8 Update 02.
Keyword: Report Generation
One-line Description:
Wrong peak type on report if peak baseline code' is 'VV G'
Problem:
ChemStation Integrator sets wrong 'Peak Type' when 'Peak Baseline Code' is 'VV G'. Peak type is set to unknown instead of Gaussian.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 01.
Keyword: Report Generation
One-line Description:
Sequence line numbers greater than 9 are not properly displayed for Japanese OpenLab CDS sequence reports
Problem:
When printing a sequence report in the localized Japanese version of OpenLab CDS, line numbers not shown for numbers greater than 9. The number 1 is shown instead.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 02.
Keyword: Report Generation
One-line Description:
'Not all available columns are visible' appears for MS Sample Purity Results
Problem:
'Not all available columns are visible' appears for MS Sample Purity Results
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Report Generation
One-line Description:
Chart snippets using non-rounded numbers for y-axis labels
Problem:
Chart snippets are using very precise numbers for y-axis labels (for example: 62258.826), instead of the more conventional 62255, 62260, et cetera.
Temporary Solution:
n/a
Fix Information:
This issue has been resolved in OpenLab CDS v2.8 Update 02.
Keyword: Report Generation
One-line Description:
Compound custom fields set as type Numeric which contain no value are being displayed in reports with an error
Problem:
Compound custom fields set as type Numeric which contain no value are being displayed in reports with an error.
Temporary Solution:
n/a
Fix Information:
This issue has been resolved in OpenLab CDS v2.8 Update 02.
Keyword: Report Generation
One-line Description:
Reporting the execution time in body adds the time offset
Problem:
If you copy the expression =String.Format("Printed: {0}",ExecutionTime) to print the execution time from the footer to the body, a wrong time will be shown in the report. It will add the time offset to the output.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLab CDS v2.8 Update 02.
Keyword: Report Generation
One-line Description:
Summary calculation settings are not kept if custom calculation results are used as column values
Problem:
The summary calculation settings of compound properties are not kept if custom calculation results are used as column values. If the column value contains CCR/CFE parameters (e.g. =CCR(Compound_CustomCalculationResults,"<CC field>") the settings for summary calculations will change after saving and re-opening the report template.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in a future release.
Keyword: Report Generation
One-line Description:
Overridden column parameters are not reported
Problem:
In some cases, the overridden column parameters are not getting reported.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Report Template Design
One-line Description:
Error seen in Intelligent Report header (#error) if any related data field is used in an expression
Problem:
This note is about Intelligent Reporting template design In the reporting editor, the report header could not used related injection data information such as "Sequence Name", "Sample name", "Vial location", or any information or results that are contained in the data file. If the drag and drop functionality is used to placed one of this information inside the report template header, the editor will show that this is not allowed. But if a text field is added and edited with an expression like "=Sequence_Name". The report generated from this template will lead to an error message during the report generation.
Temporary Solution:
Such information cannot be displayed in any report header
Fix Information:
Will be announced in a separate note when this functionality will be available
Keyword: Report Template Design
One-line Description:
Intelligent Reporting - Stacked Chromatograms do not display the time axis in reports
Problem:
If a chromatogram display is set to show multiple chromatograms in a stacked display, the time axis is no longer displayed. Due to the 3D perspective effect that the sacked mode induces, the time axis is no longer displayed.
Temporary Solution:
The time can be displayed on the peak level by using the peak label functionality.
Fix Information:
n/a
Keyword: Report Template Design
One-line Description:
Intelligent Reporting - Square brackets cannot be used in filter expressions
Problem:
Intelligent reporting use Visual Basic expression in the report template edition. This note is related to the limitations of this language expressions. When a reporting item is filtered on a specific expression such as Sample_Name like "Standard [1]", the filter will provide the desired effect to hide or show this specific sample name. All expression using text condition with "[1]" will not be functional.
Temporary Solution:
Replace the all square brackets "[]" by round brackets "()".
Fix Information:
n/a
Keyword: Report Template Design
One-line Description:
Missing syntax warning: Variables extended by a unique key need to be enclosed in brackets if used in mutiplications or divisions
Problem:
When a variable extended by a unique key is used in an expression with multiplication or division, the variable must be enclosed in brackets. Not including the brackets will not be flagged by syntax checking but the report will not render.
Temporary Solution:
Enclose the variable in brackets
Fix Information:
This limitation is fixed in OpenLAB CDS 2.1
Keyword: Report Template Design
One-line Description:
.NET Framework 4.6.1 update not compatible with OpenLAB CDS 2.0
Problem:
The .NET Framework 4.6.1 can affect the Intelligent Reporter editor functionality on OpenLAB CDS 2.0. The reporting item properties may not be accessible in the template editor. This does not affect the report generation. All report templates that were previously edited before installation of the .NET framework windows update will remain functional.
Temporary Solution:
The windows update installation of the .NET framework 4.6.1 can be temporary blocked by following the procedure: https://support.microsoft.com/en-us/kb/3133990 . If the update was already installed, refer to the following Microsoft support page to uninstall the .NET Framework 4.6.1 update: https://support.microsoft.com/en-us/kb/3102436
Fix Information:
This issue is fixed in OpenLAB CDS 2.1
Keyword: Report Template Design
One-line Description:
Report design with MS spectra plots
Problem:
The below note describes behaviors that can be observed reporting MS spectra. When the number of spectra is important and leads to several pages of spectra reported, the following can be observed: - Page header or footer overlap - Blank page - Missing spectra This relates to all MS spectra plot items.
Temporary Solution:
In order to correctly report the MS spectra, the page layout must be considered. We recommend to use in this case a group and repeating approach. To create a group, right-click on the spectra plot item in the report editor, and select "group". The group repeating criteria must be then edited in the spectra plot properties, such as to repeat on Peak_ID (unknown peak) or Compound_ID (expected identified compound) for example. And the size of of the spectra plot considering the group repeating can be adjusted to report a certain number of spectra per page.
Fix Information:
n/a
Keyword: Report Template Design
One-line Description:
No report generated when the expressions are not completed or correct
Problem:
The below issue is specific to OpenLAB CDS 2.1. When a report is edited in the report template editor, every fields that refer to an analysis result is evaluated from the result set during the report generation. Expressions like: " =Sequence_Description " will be read from the result set currently loaded, and will return the value which was used for the sequence description during acquisition. In OpenLAB CDS 2.1, as well as all revision of Intelligent reporting for all OpenLAB CDS revisions, when such expressions are miss-typed, Such as " =Seuence_Description " An error message will appear during the report generation, because the analysis result called "Seuence_Description" does not exist in the result set. This message is usually pointing to the expression which had been incorrectly typed : "System.ApplicationException Report code could not be compiled. 1. Message: 'Seuence_Description' is not declared." The message can be difficult to read at the first read because it mentions different application services involved in the report generation, but for expression error, the first lines are the most important to identify the error. However, in the case of an expression evaluating the result of a specific analysis results such as: " =Sequence_Description = "SST01" " Where the actual value of the current result set sequence description is compared to "SST01". In this report generation, 2 important things will be evaluated: 1. Does the name of the sequence description is a string (is it a text value)? 2. Does this text is equal to "SST01"? If these two tests will be successful, the result of this expression will be : True If the 2nd point is not matched, the result will be: False If the 1st point is not matched, the report will not be generated, and the report previewer will remain without any preview. For example, if no Sequence Description was entered during the acquisition, there is no value in the analysis results (No number or no text) In that case the type of this value is "no type" and is compared to a text. And the evaluation of this result cannot proceed. This last point is specific to OpenLAB CDS 2.1 and will be changed in a future revision to return in this specific case: False The point developed above is important for any filters of evaluation of a result value.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLAB CDS v2.2
Keyword: Report Template Design
One-line Description:
Intelligent reporting composite groups having misleading names in the report template folders
Problem:
Composite groups saved and used in report edition have a an constituent name and history in the content management. When a new composite group is created in report edition, all existing composite groups are sorted, by name (from 0.ircg to n.ircg), and uploaded to the content management. This may lead to inconsistent names and history in the data back-end in the case on composite group have been deleted or moved to another project.
Temporary Solution:
n/a
Fix Information:
Will be fixed in CDS 2.2. The name given in the report editor will be used to name the *.ircg file.
Keyword: Report Template Design
One-line Description:
Error editing Intelligent Report templates migrated from OpenLAB CDS ChemStation or EZChrom
Problem:
The below affects all OpenLAB CDS 2.x revisions and updates. If a report template is migrated from OpenLAB CDS ChemStation or EZChrom edition to OpenLAB CDS 2.x, you may encounter an error while generating the newly updated and saved template. This is migration step error. This occurs only after report template modification with report templates coming from ChemStation or EZChrom, and only after modifying anything (filter, labels expression) in the chromatogram reporting item. The report template editor is corrupting expressions in the Chromatogram report item
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLAB CDS v2.2.
Keyword: Report Template Design
One-line Description:
Chromatogram custom signal axis scalling
Problem:
Some data may show reports without detector signal trace when applying custom signal scaling in the chromatogram plot of a report template such as, 0 to 6 mAU, pa or counts. The affected data are the data having a signal drop from 0 to a high value (solvent peaks in GC, LC for example).
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLAB CDS v2.2 and OpenLAB CDS 2v.1 SR1 HF3.
Keyword: Report Template Design
One-line Description:
Report parameters as boolean in report editor must only have "Default Value"
Problem:
For report parameters of type boolean, you can only have True or False results. Therefore, you must have only one default value entered for this report parameter. In the case some values had been selected in the "Available values" section, an error message will appear in the report parameter window. This error message prevents to edit the report parameter any further.
Temporary Solution:
Do not enter any "available value".
Fix Information:
This issue is resolved in OpenLAB CDS v2.3.
Keyword: Report Template Design
One-line Description:
Single Data Analysis method parameter values may not be accessible for expected compounds
Problem:
The report of single data analysis value may not be accessible for expected compounds. This affects only the report item: "Single Data Analysis Method Parameter" under the "Method information" section in the reporting items tree.
Temporary Solution:
Use the following reporting item: "Single Data Analysis Method Table Row" or the "Data Analysis Method Information Multi Column" And filtering these items on the following method content: Method parameters / Compound parameters / Expected compounds
Fix Information:
This will be fixed in a further software release.
Keyword: Report Template Design
One-line Description:
Filtering report item with the same data field containing several values
Problem:
This applies to filtering the results in the report items properties. When the results must filter a data field with several values such as: Filter 1 =Sample_Name like "xxx" Filter 2 =Sample_Name like "yyy" The filters properties will automatically filter the report as following: Filter 1 =Sample_Name like "xxx" And Filter 2 =Sample_Name like "yyy" Which is not the expected behaviors.
Temporary Solution:
The filter expression must be edited in one filter expression: Filter 1 =Sample_Name like "xxx" OR Sample_Name like "yyy" Usual visual basic logical operators can be used in the report expressions.
Fix Information:
N/A
Keyword: Report Template Design
One-line Description:
Variables saved in the table summary calculation must be used after the table
Problem:
When a variable is saved in the column table under the summary calculation tab, the variable will not be accessible inside the table. During a report generation, the report content is drawn from the top left to the bottom right of the report template. Therefore, variables saved using this workflow must be used after the table.
Temporary Solution:
the variables used in a table must be defined and saved before the table.
Fix Information:
This relates to a necessary report generation design and will not be fix in further software release.
Keyword: Report Template Design
One-line Description:
Report missing peaks with other peak types (identified and part of groups)
Problem:
In OpenLab CDS v2.2, a checkbox was introduced to remove duplicate peaks. This checkbox is unfortunately not compatible with missing compounds reporting. This checkbox was originally used to report peaks that belongs to several peak types such as identified peaks which belong to groups (Timed or Named groups).
Temporary Solution:
Report missing compounds in a separated table.
Fix Information:
This behavior will change in OpenLab CDS v2.4. An addition table, called "Compound And Group Results" will be added for that use case. It will also improve the group reporting.
Keyword: Report Template Design
One-line Description:
Migration of ChemStation Report template to OpenLab CDS v2.x
Problem:
In ChemStation, there are fields specific to the Chromatographic Data System backend Integration. For example OpenLab ECM 3.x information such as: - Storage operator - Storage Path - Storage Server - Storage target Path - Storage Version These fields will not be reportable in OpenLab CDS v2.x. Data backend location / version and other information are saved in the corresponding sample and injection fields (result set version, data file directory,...).
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Report Template Design
One-line Description:
Diagnostic data such as column information, module temperatures are not available in reporting
Problem:
Diagnostic data is coming from LC and CE drivers and allow the users to report diverse module actual and set-points. Few example: Sampler: Injection needle, Temperatures at ru start and end. Column compartment: Temperatures, pressures, column information, number of injections. This information is available for data acquired from OpenLab CDS v2.4 and later. This can be seen in reports using, in the report editor, the "Advanced Run Information" reporting item or also with single fields using the "Diagnostic Data". However, the field will remain empty using the "Diagnostic Data" field. This has been identified, and fixed in OpenLab CDS v2.4 update 03 and further releases.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Report Template Design
One-line Description:
Migration of report template containing multi-line expressions
Problem:
In OpenLab ChemStation or EZChrom Intelligent Reporting editor, it was possible to create new lines in the expressions to have better syntax overview with multi-lines. Expression like: =If(Compound_Amount > 0,True,False) Could be written as following: =If(Compound_Amount > 0 ,True ,False) From OpenLab CDS v2.1 and OpenLab CDS ChemStation Edition C.01.10, reporting expression capabilities were improved to support additional visual basic expressions. Unfortunately, the expression above would not be understood during report generation using this new report rendering service, as in visual basic such expressions should be written as following: =If(Compound_Amount > 0, True, False) Or using the character "_" to define anew line: =If(Compound_Amount > 0 _ ,True _ ,False) See Microsoft article - Statements in Visual Basic: https://docs.microsoft.com/en-us/dotnet/visual-basic/programming-guide/language-features/statements Report template migration using multi-line expressions must be therefore attentively investigated. If the report was successfully generating reports before the revisions mentioned above, end of statement errors during report generation would be one symptom a report contains untranslated multi-line expression : "Message: error BC30198: ')' expected" : When the parenthesis are placed in different lines. "'If' operator requires either two or three operands."
Temporary Solution:
Report templates containing multi-line expression must be edited to comply with the Microsoft visual basic statements reference.
Fix Information:
n/a
Keyword: Report Template Design
One-line Description:
Report document template failing with error
Problem:
Document template is a functionality in reporting editor to print a pdf which would document all the template details such as: - Report template version. - Layout and detailed positions of the report items. - Description and expression used in the different report items. - Report audit trails and history. - Software used for edition. Report templates including a calibration curve plot snippet will not be able to be documented using the "Document Template". The generation of the document will fail with the following error: "Failed to document the template. Please check the connection to the server".
Temporary Solution:
n/a
Fix Information:
This issue was observed in OpenLab CDS v2.3. This is fixed in OpenLab CDS v2.4 and future software versions.
Keyword: Report Template Design
One-line Description:
Edition of custom variable, custom parameter or method override parameter expression may lead to corruption
Problem:
This issue is related to report template edition. It applies to expression containing an operator ("*", "/", "+", "-" or such as "like") and a custom variable, custom parameter or any method override parameter. The report generation may lead to error if such expression is edited in the expression editor (by clicking "fx" in the value properties). It occurs because the report editor inserts extra fields like in the expression when expression is displayed in the expression editor.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in OpenLab CDS v2.4 Update 06.
Keyword: Report Template Design
One-line Description:
Custom parameter expression error in OpenLab CDS 2.4 Update 03
Problem:
In OpenLab CDS v2.4 update 03, report generation will show errors if any custom parameter expression is updated in the expression editor (by clicking "fx" in the field value properties dialog). It applies to compound or sample custom parameters, and only in OpenLab CDS 2.4 Update 03.
Temporary Solution:
n/a
Fix Information:
This issue will be fixed in OpenLab CDS v2.4 Update 06 and higher revision.
Keyword: Report Template Design
One-line Description:
Reporting method information snippets are duplicated in summary report outputs
Problem:
When a method information report item is used in a sequence summary or cross sequence summary report template, such as Acquisition method information or Data Analysis method information snippets, the method description will be duplicated in the report printout as many times as there are injections selected for the report generation. This is due to a group repeat configuration embedded in the reporting snippet. This snippet will repeat based on method ID, which is different for each injection, even if the method name and version is identical at each injection.
Temporary Solution:
This internal grouping can be removed in the rdl file using a text editor.
Fix Information:
This issue is fixed in OpenLab CDS v2.6.
Keyword: Report Template Design
One-line Description:
Formatting option is not available for MS peak purity ion table
Problem:
Formatting option is not available for MS peak purity ion table.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 and OpenLab CDS v2.4 Update 08.
Keyword: Report Template Design
One-line Description:
Error in editing compound summary matrix
Problem:
The Data Analysis may crash in certain conditions when editing the sorting field of compound summary matrix in the report editor.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6
Keyword: Report Template Design
One-line Description:
Matrix report item becomes uneditable
Problem:
In reporting, some matrix report items may encounter issues when editing the summary calculations. This is issue occurs when the user is unselecting all summary calculations in the matrix properties. If after removing all calculations, user reselects one summary calculation and validate the matrix properties change, the matrix will become uneditable.
Temporary Solution:
This issue occurs with specific user workflow as described above.
Fix Information:
Fixed in OpenLab CDS v2.6.
Keyword: Report Template Design
One-line Description:
Expressions not correctly appearing in report editor
Problem:
From OpenLab CDS V2.5, some expressions will appear differently in the report editor and report template documentation than the expressions originally edited and saved in the report template file. This issue is due to an incorrect translation between visual basic expressions saved in the template file and the simplified expressions seen in the report editor.
Temporary Solution:
It occurs occasionally with some expressions. In such cases, to be able to see the correct expression in the report editor, the affected expression can be rewritten with additional surrounding parentheses. Example: =IIF(LEN(Compound_Name)<1,"Unknown",Compound_Name) Can be rewritten as following to prevent miss translation: =(IIF(LEN(Compound_Name)<1,"Unknown",Compound_Name))
Fix Information:
This issue is fixed in OpenLab CDS v2.6 and in OpenLab CDS v2.5 update 07.
Keyword: Report Template Design
One-line Description:
Error when loading report preview "AsyncHelpers.Run threw an exception"
Problem:
When loading a report template the error message "AsyncHelpers.Run threw an exception" is shown and the template can not be edited. The template did work before and no changes were done. This is often caused by non alphanumeric characters that are interpreted incorrectly by the report Template editor.
Temporary Solution:
As a workaround these characters can be defined as variables in the code section of the Report Template Parameters. For example the "(" definition would be public dim open_bracket as String = "(" In the report template this variable can be used in the following way: the value =If(InStr("(",Sample_Name)>0,"Yes","No") that causes the problem becomes =If(InStr(code.open_bracket,Sample_Name)>0,"Yes","No")
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Report Template Design
One-line Description:
Sorting Chromatogram in Intelligent Report not working
Problem:
Sorting Chromatogram in Intelligent Report is not working on Japanese system.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 04.
Keyword: Report Template Design
One-line Description:
Expression for visibility is not kept in case of using an if statement.
Problem:
It is possible to write an if statement into the expression field for the visibility properties of a report item. Once the properties dialogue gets closed and reopened, the expression is gone and the ratio button "true" is selected.
Temporary Solution:
Instead of using an if statement, write the condition directly as an expression.
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Report Template Design
One-line Description:
Filtering issues when compound name includes "["
Problem:
If the compound name includes a characters "[" and the filtering is based on the compound name, the compound might not appear on the report.
Temporary Solution:
Use filtering expression =Compound_Name like "*[[]*".
Fix Information:
n/a
Keyword: Report Templates
One-line Description:
Sequence Summary Extended template in Excel format not reporting the acquisition or processing method information correctly
Problem:
When exporting the sequence summary report to Excel, the Excel cells may be collapse when loading the generated excel file
Temporary Solution:
Manually resize the cells in Excel
Fix Information:
This issue is fixed in OpenLAB CDS 2.1
Keyword: Report Templates
One-line Description:
Generating a report to word file format may generate a report containing not aligned report items
Problem:
If the report is generated with a word document file format, it can happen that report items from the report would not be aligned anymore to the rest of the items.
Temporary Solution:
Modify the report and slightly move the items which are not aligned in the word file format. Generate the report and see if the alignment to the other reporting items is correct.
Fix Information:
This issue is fixed in OpenLAB CDS 2.1
Keyword: Report Templates
One-line Description:
Export to excel does not export the report header logo
Problem:
In OpenLab CDS ChemStation Edition C.01.10 and OpenLab CDS v2.1, the report services performing report generation have been changed. As the previously used rendering engine was no longer supported, this had been changed to another rendering engine. This change implies different behaviors in certain areas with positive or negative impacts on the report outputs. This issue relates to report export to excel. In OpenLab CDS ChemStation Edition C.01.09 and previous revisions, the report header logo was exported to the excel file. With the new rendering engine, the logo will no longer be exported. To export the report logo to the different excel sheets, the logo must be placed at the beginning of the report body. As page breaks trigger new excel sheets in the exported file, a logo must also be placed after any report page break to place a logo on the corresponding excel sheet.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Report Templates
One-line Description:
The selection of RSD summary calculation is not saved with the report template
Problem:
After user has selected to calculate RSD with a label to the summary calculation and saved the report template, the RSD summary calculation remains unchecked with wrong a label upon reloading the saved report template.
Temporary Solution:
n/a
Fix Information:
Agilent has identified the issue and a fix is provided in the following releases: OpenLab CDS v2.5 OpenLab CDS v2.4 Update 07
Keyword: Report Templates
One-line Description:
MS qualifier results not correctly reported
Problem:
The below issue concerns OpenLab CDS v2.5 update 3 and further updates. In OpenLab CDS v2.5 update 3, a change in the qualifer ion feature has been introduced. This change allows to quantify compounds having missing qualifer. As a consequence of this change, MS_Quantitative_Long report templates do not reflect correct qualifier status in the quantification details pages. All compounds with or without missing and failing qualifier will be flagged as "pass" overall qualifier status. However, the summary table is not impacted with the described change and will successfully report missing or failing qualifier.
Temporary Solution:
To report correct results in the OpenLab CDS v2.5 update 3 and further release updates, fields would need to be modified as temporary fix. In the reporting editor, the "Overall peak qualifier(s)" fields and chromatogram color filling under the fields would need to be updated. To modify these report items, right-click on the concerned fields or chromatogram plot, and select "properties". "Overall peak qualifier(s)" fields updates to perform: left field value remains the same: ="Overall peak qualifier(s):" left field conditional formatting must be changed from: = (Peak_CalibRole = 1 ) and (Compound_Type = 5 ) To: =Max(CDbl(if(Peak_CalibRole=1, Compound_Missing_Qualifiers like "", Peak_Qualifier_Passed))) = 0 Right field value must be changed from: =iif(Compound_Type=5,"Fail","Pass") To: =If(Max(CDbl(if(Peak_CalibRole=1, Compound_Missing_Qualifiers like "", Peak_Qualifier_Passed))) = -1,"Pass","Fail") Right field conditional formatting must be changed from: = (Peak_CalibRole = 1 ) and (Compound_Type = 5 ) To: =Max(CDbl(if(Peak_CalibRole=1, Compound_Missing_Qualifiers like "", Peak_Qualifier_Passed))) = 0 Chromatogram peak filling update to perform: In the chromatogram properties, select the "Peak Labels" section, and in the bottom of the list edit the "Peak Filling" from "Use Color:" to "None".
Fix Information:
Fixed in OpenLab CDS v2.6.
Keyword: Report Templates
One-line Description:
"Template version" is named "Template Version of content management" in report template document
Problem:
The template version shown in document template generated in the Data Analysis report editor is not matching the version seen in Content Management version of the template RDL file. This version corresponds to the template version from the report editor. The text "Template Version of content management" is misleading. The version number is not tracked by the external data storage. There can be a mismatch between these two version numbers as there is no technical correlation between them.
Temporary Solution:
OpenLab Content Management version number can be ignored for all OpenLab CDS related purposes.
Fix Information:
This issue is fixed in OpenLab CDS v2.7. Correct wording ("Template Version") will be used.
Keyword: Report Templates
One-line Description:
Document template failing for Calibration and Stability report templates
Problem:
The document templates is used to document template design, formulas and audit trails. This documentation is failing to be generated for the Calibration.rdl and Stability_Report.rdl report templates delivered with OpenLab CDS v2.x.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 update 08 and OpenLab CDS v2.6 Update 02.
Keyword: Report Templates
One-line Description:
Adding a Signal to Noise S/N column to report results in error with Russian version
Problem:
Adding a Signal to Noise S/N column to report results in error with Russian version
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.5 update 08.
Keyword: Report Templates
One-line Description:
Mistranslations in snippet and default templates
Problem:
Following report templates might show a mistranslation on Russian systems: MS_SamplePurity.rdl MS_SamplePurity_Letter.rdl Qualitative_Long.rdl Qualitative_Long_Letter.rdl Qualitative_nBiggestPeaks.rdl Qualitative_nBiggestPeaks_Letter.rdl Qualitative_Short.rdl Qualitative_Short_Letter.rdl OLIR_Snippet_MSSamplePurityPerSignal.rdl
Temporary Solution:
n/a
Fix Information:
Issue is fixed in OpenLab CDS v2.6 Update 02
Keyword: Report Templates
One-line Description:
Not possible to generate the template documentation because of "Failed to document the template"
Problem:
If the"System Suitability Report" custom Composite Group is included, it is not possible to generate the template documentation because of "Failed to document the template".
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.7, OpenLab CDS 2.6 Update 05 and OpenLab CDS 2.5 Update 09
Keyword: Report Templates
One-line Description:
The audit trail table of a report template is not properly printed
Problem:
When saving a report template multiple times, the audit trail table of this report template is not properly rendered, hence some of the entries may not be visible.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.6, OpenLab CDS v2.5 Update 08, and OpenLab CDS v2.4 Update 11.
Keyword: Report Templates
One-line Description:
Report template from OpenLab CDS 2.1 gets unusable in OpenLab CDS 2.5
Problem:
Modifying a report template in OpenLab CDS 2.5 which got created in OpenLab CDS 2.1 could lead to an unusable report template. The issue seems to happen on templates where aggregators have been defined. After modifying the report (i.e. adding a text field) the preview cannot be generated as an error occurs during the rendering.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS 2.5 Update 11
Keyword: Report Templates
One-line Description:
Reporting Spectrum legend text is not matching with Data Analysis view
Problem:
The spectrum legend text in reporting view is not matching with spectrum legend text shown in Data Analysis Spectrum window.
Temporary Solution:
n/a
Fix Information:
This issue got resolved in OpenLab CDS v2.8.
Keyword: Report Templates
One-line Description:
Modifying report template stability_report.rdl will cause report rendering issues.
Problem:
After modification of the stability_report.rdl report template, it is not possible to generate a report out of it. There will be an error and the rendering process stops.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8, OpenLab CDS v2.7 Update 03 and OpenLab CDS v2.6 Update 09.
Keyword: Report Templates
One-line Description:
Field label and value not shown if field is placed in the header or footer of the report template
Problem:
Field label and value not shown if field is placed in the header or footer of the report template.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.7 Update 06.
Keyword: Report Templates
One-line Description:
Report template documentation can't be generated
Problem:
In specific instances the report template documentation can't be generated. An error "Error Document Template - "Failed to document the template : Please check the connection to the server"" is shown.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Report Templates
One-line Description:
Selected summary calculations changed after re-opening the column properties
Problem:
Selected summary calculations changed after re-opening the column properties. It can happen instead of RSD the standard deviation is then selected as summary calculation.
Temporary Solution:
n/a
Fix Information:
This issue got fixed in OpenLab CDS v2.8 and OpenLab CDS v2.7 Update 06.
Keyword: Report Templates
One-line Description:
Intelligent Report Footer hides values of peak table when table continues to next page
Problem:
Intelligent Report Footer hides values of peak table when table continues to next page.
Temporary Solution:
This issue occurs if a column in the table is hidden. Unhide the column as a workaround.
Fix Information:
This issue is fixed in OpenLab CDS v2.8 Update 03.
Keyword: Reports
One-line Description:
Description on unsaved entries is incomplete in Audit Trail dialog
Problem:
The description for entries currently in editing mode (and not yet saved) is incomplete. The PDF Export and Print buttons are enabled in Audit Trail dialog containing unsaved entries.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS 2.2. The "Review", "PDF Export", and "Print" buttons are enabled only when all entries in the Audit Trail dialog are saved.
Keyword: Reports
One-line Description:
Non-identified peaks may be missing in reports with non-Agilent instruments data
Problem:
For data acquired from non-Agilent instruments (such as Waters Acquity UPLC), the non identified peaks may be missing in the reports. This only affects non-Agilent instruments, and report templates including tables with non-identified peak reporting.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 06.
Keyword: Reports
One-line Description:
"Delete" entry in the audit trail raises an audit concern
Problem:
With OpenLab CDS and a G7129A ALS sampler, a change to the instrument method from the default Flush Port to Wash Vial records the following entries in the audit trail: * Added Needle Wash Location with value <vial location> * Added Wash Cycles with value <value> * Deleted Wash Time with value 3 s * Changed Needle Wash Location from Flush Port to Wash Vial The entry for Deleted Wash Time refers to the wash time in the Flush Port mode which does not apply to the Wash Vial mode. Since this value does not apply, it is deleted from the method.
Temporary Solution:
Agilent recommends users recognize that, when changing the ALS wash mode from Flush Port to Wash Vial, the Wash Time value no longer applies and is deleted from the method. Refer to the Wash Needle topic in the OpenLab Help & Learning documentation.
Fix Information:
No fix planned.
Keyword: Reports
One-line Description:
Tune Report: The autotune report does not include instrument name
Problem:
Autotune reports will contain the instrument IP address and serial number, but do not contain the configured instrument name.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Roles and Privileges
One-line Description:
User with empty password cannot unlock Acquisition or Data Analysis
Problem:
When Acquisition or Data Analysis UI is locked out, a user who was created without a login password cannot unlock the UI.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 11.
Keyword: Roles and Privileges
One-line Description:
Users can delete their own data without deletion permission via web client
Problem:
Users who have only "read" and "write" permission (Edit content of project) in OpenLab CDS 2.3 with content management can delete their own generated data via content managment web client.
Temporary Solution:
For workstation plus and client/server system, we recommend restricting user access to content management client by removing the permission "Access content using web client" from the users.
Fix Information:
This issue is fixed in OpenLab CDS v2.4 and OpenLab CDS v2.3 Update 05.
Keyword: Roles and Privileges
One-line Description:
Folder move requires Everything role
Problem:
Only users that have the role Everything are able to move a folder.
Temporary Solution:
N/A
Fix Information:
This Problem is solved in Version 2.6 where new Delete Content of Project permission are introduced which provides ability to delete and move content associated with projects
Keyword: Roles and Privileges
One-line Description:
Users added to a domain group can't access content management
Problem:
After an OpenLab system is moved to a new domain, users that are added to domain groups can't access content management. The alfreso.log file shows the error ---------------- [org.alfresco.repo.security.sync.ChainingUserRegistrySynchronizer] User authenticated but failed to sync with user registry com.agilent.datastore.olss.service.ServerDownException: Not Found {"error":"The object was not found.","errorCode":"ObjectNotFound"} ---------------- This will be the case if the old domain is no longer available.
Temporary Solution:
As a workaround, manually cleanup the table ExternalUsers of the OLSharedServices database. Remove all entries for users of the old domain.
Fix Information:
n/a
Keyword: Roles and Privileges,User Interface
One-line Description:
Orphan Property ID leading to sync failure
Problem:
The application has a job to clean obsolete property values in the database (Prop Cleaner Job) and one to synchronize users from LDAP to the Content Management (User Sync Job). The Orphan Property ID issue occurs when the Prop Cleaner Job runs at the same time as (or within close time proximity of) the User Sync Job, resulting in deletion of property values that should not have been deleted and causing dangling references inside the database that prevents the application from doing further user synchronizations. This issue affects the following Products and Versions: OpenLab CDS v2.2, v2.3 and v2.4 OpenLab Server v2.2, v2.3 and v2.4 OpenLab ECM XT v2.2, v2.3, and v2.4
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab Server v2.5 and OpenLab ECM XT v2.5 This fix is also available in the following Software Updates: - OpenLabCDS v2.4 Update 04 and ECM XT 2.4 Update 01 - OpenLab CDS v2.3 Update 10 and ECM XT 2.3 Update 03 - OpenLan CDS v2.2 Update 07 and ECM XT 2.2 Update 01
Keyword: User Interface
One-line Description:
Chinese, Japanese, or Russian file names corrupted after download as a compressed zip
Problem:
File names are corrupted after you decompress a .zip file in Windows 7 using the windows 7 decompression tool. The issue is not observed when using other decompression tools. The problem has been acknowledged by Microsoft and an hot fix is available. See http://support.microsoft.com/kb/2704299 for more information
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: User Interface
One-line Description:
SIM table is disabled if the last method loaded was SIM
Problem:
If the last method loaded was SIM, then when Acquisition is launched the SIM table is disabled.
Temporary Solution:
Changing "Acquisition type" to Scan and then back to SIM enables the SIM table.
Fix Information:
This issue is fixed in GC/MS driver v1.2 for OpenLab CDS.
Keyword: User Interface
One-line Description:
Copy paste a row in the SIM table causes the acquisition Client to crash
Problem:
If you copy paste a row in the SIM table, the acquisition Client will crash.
Temporary Solution:
n/a
Fix Information:
This issue will be resolved in a future release of GC/MS driver for OpenLAB CDS.
Keyword: User Interface
One-line Description:
Cannot unlock session locked by user from different domain
Problem:
If Acquisition or Data Analysis session is locked by a user from one domain, it cannot be unlocked by another user from a different domain because the "Domain" field is not available in the login window.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS 2.2. The "Domain" field is available in the login window.
Keyword: User Interface
One-line Description:
Archive Offline feature has been removed in OpenLAB Server 2.1
Problem:
The Archive Offline feature introduced in OpenLAB Data Store 2.0 got removed in 2.1. Archive Offline should not be used in OpenLAB Data Store 2.0 since there is no De-Archive option for it.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: User Interface
One-line Description:
One UIB II channel is acquired but two signals are displayed in Data Analysis
Problem:
Only one UIB II signal channel is acquired, however, in Data Analysis the chromatogram displays two signals. The extra signal is the instrument trace that has the same name.
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS v2.2. Only one signal is displayed for each injection.
Keyword: User Interface
One-line Description:
Search cannot handle Metadata which contains a µ
Problem:
When a document containing a µ symbol is uploaded, searching the document with a string using that symbol ( e.g. >5µl ) will not return any hit.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: User Interface
One-line Description:
EI tune evaluation report displays incorrect limit for 502/69 ratio
Problem:
The EI tune evaluation report displays "Ratio of 502 to 69 should be > 2%" but should actually say > 2.4%.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: User Interface
One-line Description:
Not able to filter system activity log based on Time
Problem:
Form OpenLAB Control Panel, system activity log does not allow to enter time information in the filter, only date is allowed. This happens in v2.2.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: User Interface
One-line Description:
PDFs Which Include Localized Characters Can Appear Garbled in Web UI Previews
Problem:
PDFs containing localized characters can appear garbled when viewed through the Web UI preview screens.
Temporary Solution:
n/a
Fix Information:
The PDFs can be downloaded and viewed through any PDF reader application. They will show up correctly.
Keyword: User Interface
One-line Description:
First time login to the Content Management Web UI can take up to 60s
Problem:
After a reboot of the server or a restart of the services, login in to the Content Management Web UI can take up to 60 seconds. This is mainly caused by the Access Control List and permissions checks on repository objects required to build the dashboard.
Temporary Solution:
n/a
Fix Information:
No fix planned for this issue.
Keyword: User Interface
One-line Description:
Activity Log Not Viewable in Chrome 67 or later (ECM XT 2.2, 2.3)
Problem:
Using Chrome 67 or later to view the Activity Log in ECM XT 2.2 or ECM XT 2.3 is not possible. UI elements are not rendered.
Temporary Solution:
For ECM XT 2.2 or ECM XT 2.3 - if the customer needs to view the Activity Log, please use Internet Explorer or Edge.
Fix Information:
Fixed in Version 2.4
Keyword: User Interface
One-line Description:
Time displayed in QualA does not match local time if DST is not set correctly
Problem:
If Daylight Saving Time is set incorrectly (i.e., DST is set to ON when for the specific region it should be OFF OR it is set to ON when it should be OFF), then current time in QualA is shown differently from the local time. The difference is 1 hour.
Temporary Solution:
Set the Daylight Saving Time to the value that is appropriate for the region.
Fix Information:
n/a
Keyword: User Interface
One-line Description:
No Tree in DA after CDS 2.3 Update 06 installation with CM
Problem:
After installing OpenLab CDS 2.3 Update 06 with Content Management, the Data Selection tree in Data Analysis is not visible.
Temporary Solution:
n/a
Fix Information:
This issue is fixed in OpenLab CDS v2.3 Update 07.
Keyword: User Interface
One-line Description:
The information of the modified person on the folder is incorrect in the Datastore WebPage
Problem:
In the Datastore Web-Page the user who has a Folder created is displayed as the modified User, even if other users have modified the Content of the Folder (added Files).
Temporary Solution:
n/a
Fix Information:
The Issue is fixed in OpenLab Server 2.1.
Keyword: User Interface
One-line Description:
Pagination disappears when search returns more than 250 results
Problem:
The pagination on the search results page disappears when more that 250 hits are found.
Temporary Solution:
n/a
Fix Information:
The Search User Interface as been redesigned in version 2.4, pagination is no longer displayed. User needs to keep scrolling down to see the search results
Keyword: User Interface
One-line Description:
Incorrect rendering of MS Office documents in preview
Problem:
MS Office documents previews are not showing up correctly.
Temporary Solution:
n/a
Fix Information:
No Fix planned for this issue, As a workaround, download the files and view in their native office applications.
Keyword: User Interface
One-line Description:
Storage System Test cannot be executed after changing account on ECM 3.x
Problem:
In an Environment OpenLab CDS 2.5 together with ECM 3.x as the Authentication Provider the QualA Storage System test will fail after the switch to another ECM Account. The reason is the missing QualA privilege's in the new ECM Account.
Temporary Solution:
Workaround: Run PrivilegeCreatorTool.exe with administrator credentials and execute the test again. Command: C:\Program Files (x86)\Agilent Technologies\QualA_ Agilent.Ca.PrivilegeCreatorTool.exe <username> <password> <domain>
Fix Information:
The Issue is fixed in QualA 3.4
Keyword: User Interface
One-line Description:
Switching from domain to internal authentication can break security and storage tests
Problem:
In the case parameters for the security (or storage) test have been entered, saved and synced to the QualA Central Management server, switching to internal authentication provider creates a situation where security (or storage) test will always fail after this switch.
Temporary Solution:
n/a
Fix Information:
The Issue is fixed in QualA 3.4
Keyword: User Interface
One-line Description:
Backup Utility is failing fail at verification step due to exhausting connections to the MS SQL server
Problem:
If you use the Backup Utility for OpenLab 2.6 with an SQL Database Engine, the Verification at the end of the Backup will fail if the Number unique files in Content Management exceeds 5000+ Files and the default verification setting is at 10%.
Temporary Solution:
n/a
Fix Information:
This Problem will be fixed in an upcoming OpenLab 2.6 update
Keyword: User Interface
One-line Description:
After running the server configuration utility, the Instrument service is not started
Problem:
After running the server configuration utility, the Instrument service is not re-started. This will prevent starting an instrument in the OpenLab Control Panel.
Temporary Solution:
Manually restart the Agilent OpenLab Instrument Service.
Fix Information:
n/a
Keyword: User Interface
One-line Description:
Error message occurs if server name in Storage Locations contains dot on Content Paths page
Problem:
When running Step 4 of an installation or the Server Configuration Utility, the below error will display when validating the information provided on the Content Paths page if a dot (.) character is included in one of the specified Content Storage Locations and/or Archive Storage Locations: “Storage locations with incorrect path format detected. Please edit the storage locations. Use the following patterns below: C:\location\ \\server\location”
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: User Interface
One-line Description:
OpenLab Server Update 10 installed on an AIC without warning message
Problem:
OpenLab Server update 10 could be installed on an AIC without any warning message.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: User Interface
One-line Description:
"modified" timestamp after sequence has been archived triggered by filtering for PDF
Problem:
It has been observed that if you Filter for .pdf Reports in an archived Sequence some sequences display a "Modify by ...." date/time subsequent to the "archived" date/time. The Activity log and version history correctly state that no changes have been committed after the sequence has been archived.
Temporary Solution:
n/a
Fix Information:
The Problem will be fixed in OpenLab CDS 2.7 and OpenLAB ECM-XT 2.7
Keyword: User Interface
One-line Description:
Japanese Language Files are not included in Content Management Security Update 01
Problem:
With the release of Content Management Security Update for OpenLab CDS 2.6 or OpenLab ECM XT 2.6 some language related Files (Japanese) are not included in the underlying Product (Hyland Alfresco). Users might see a "Failed to load plugin" warning on the left-hand side when accessing specific Pages in the Content manager WEB-UI. The Functionality of the software is not affected
Temporary Solution:
n/a
Fix Information:
This problem is fixed in OpenLab CDS v2.6 Update 07 / OpenLab ECM XT v2.6 Update 04 and in OpenLab Server / ECM XT v2.7.
Keyword: User Interface
One-line Description:
Installation of Cary-UV server plugin removes Security and storage test.
Problem:
After the installation of the Cary-UV Server plug-in the OpenLab Security Test and the OpenLab storage System Test are no longer available.
Temporary Solution:
As a workaround these tests can be run from a Client or an AIC. Technically this would be equivalent to running it on the server. This Problem will be fixed in Version 2.8
Fix Information:
The Installation of Cary UV Software in a Networked Workstation Mode connected to a Central ECM-XT or OpenLab Server requires the installation of the Cary-UV Server plug-in on the Server. After the installation the Test services related OpenLab Security Test and the OpenLab storage System Test are no longer available on the Server
Keyword: User Interface
One-line Description:
Test Services Workflow test is not compatible with Cary UV Instrument Controller
Problem:
After the installation of the Cary-UV Server plug-in the Workflow test will not execute when running Test Services on an AIC.
Temporary Solution:
As a workaround, the Cary UV Instrument Controller can be removed from OpenLab Control Panel. This will not have any impact on Cary UV.
Fix Information:
n/a
Keyword: User Interface , Audit Trail
One-line Description:
Activity Log not displayed in web browser when using Chrome 5.1
Problem:
Google Chrome version 51.0.2704.63(64-bit) will not display the Activity log in Data Store Browser
Temporary Solution:
n/a
Fix Information:
Update Chrome to 51.0.2704.103 or newer
Keyword: Virtualization
One-line Description:
Lost connection when launching an instrument from an RDS Remote Desktop
Problem:
Launching an instrument gives the error “Lost connection” when using OpenLab CDS 2.5 with OpenLab ECM 3.6 and a Remote Desktop Services (RDS) client. This occurs because the ECM API is not initialized from an RDS client. Note this issue only occurs with OpenLab ECM 3.5 or 3.6. It does not occur in systems configured with OpenLab Server or OpenLab ECM XT.
Temporary Solution:
Whenever the RDS server is restarted, manually initialize the ECM API as follows: 1. Open a Remote Desktop window to the RDS server 2. In File Explorer, go to C:\Windows\Program Files (x86)\Agilent Technologies\ECM API\2.2.0.0 3. Launch Agilent.ECMAPI.ECMAPI32BitHost.exe 4. Launch Task Manager, go to the Details tab, and verify Agilent.ECMAPI.ECMAPI32BitHost.exe is running
Fix Information:
Agilent will provide an application that can be installed on the RDS server and published so that the ECM API is initialized automatically.
Keyword: Workflow
One-line Description:
Processing Method Role issue
Problem:
In OpenLAB CDS 2.0 and OpenLAB CDS 2.1, if a user has all "Processing Method" privileges exception for "Save result set method", the following cannot be performed: - Link data to an existing processing method - Reprocess data
Temporary Solution:
n/a
Fix Information:
This issue is resolved in OpenLAB CDS v2.2.
Keyword: Workflow
One-line Description:
Data acquisition is interrupted on GCMS SQ when system is in failover mode
Problem:
Data acquisition on GCMS SQ is interrupted when the system goes into failover mode.
Temporary Solution:
n/a
Fix Information:
This issue is fix is in OpenLab CDS v2.5, OpenLab CDS v2.4 Update 07, and OpenLab CDS v2.3 Update 12.
Keyword: Workflow
One-line Description:
Data collection Service does not start after upgrade
Problem:
After the Upgrade of an OpenLab Server from 2.3 to 2.5 with external SQL DB the Data Collection Service could not be started anymore after the upgrade is finished.
Temporary Solution:
A repair of the Data Collection Service will solve the issue. Navigate in the Windows Control Panel to Programs and Features and execute a repair on "Agilent OpenLab Data Collection Service". A reboot will be required after the repair.
Fix Information:
Resolved in OpenLab CDS v2.6.
Keyword: Workflow
One-line Description:
Minimum required Windows 10 version is different in SPT and the requirements guide for v2.6
Problem:
The minimum required Windows version is different in SPT and the requirements guide.
Temporary Solution:
The correct minimum Windows version for Client, AIC, workstation and networked workstation is documented in the OpenLab CDS 2.6 Requirements guide.
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Workflow
One-line Description:
OpenLab v2.6 Update 01 can be uninstalled on a workstation file system
Problem:
OpenLab v2.6 Update 01 can be uninstalled on a workstation file system.
Temporary Solution:
n/a
Fix Information:
Fixed in OpenLab CDS v2.6 Update 02
Keyword: Workflow
One-line Description:
Port 8006 is not tested by SPT
Problem:
The system preparation tool does not verify that port 8006 is available and not blocked by a firewall on the OpenLab Server. Port 8006 is required by the alfrescoTomcat service. Installation will fail at step 4 with the error: SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8006]: 05-Oct-2021 11:17:57.164 SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8006]: java.net.BindException: Address already in use: NET_Bind at java.base/java.net.PlainSocketImpl.bind0(Native Method) at java.base/java.net.PlainSocketImpl.socketBind(PlainSocketImpl.java:132) at java.base/java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:436) in the alfrescotomcat-stderr log file
Temporary Solution:
Verify port 8006 is available on the OpenLab Server
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Workflow
One-line Description:
Installation fails at the reverse proxy step due to port 5443 being used by another program
Problem:
In OpenLab CDS 2.6, port 5443 needs to be available at time of deployment for reverse proxy installation.
Temporary Solution:
Disable the program that uses port 5443 at the time of deployment. At the Step 4 installation step, the proxy is reconfigured and removes this dependency making port 5443 available for another program.
Fix Information:
This issue is fixed in OpenLab CDS v2.7.
Keyword: Workflow
One-line Description:
System preparation sometimes hangs at the Tcp Port Sharing and Activation step
Problem:
During System Preparation, the Tcp Port Sharing and Activation remains in a running status without completing.
Temporary Solution:
Cancel the system preparation step and re-start the installation. A message is shown to reboot the machine. After rebooting and restarting the installation, it completes.
Fix Information:
This issue got resolved in OpenLab CDS v2.8.