Software Status Bulletin

OpenLAB CDS     M8450AA

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

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

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

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

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

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

Keyword Glossary

Keyword Index

Keyword: Acquisition

KPR#:191693 Openlab EZChrom methods have to be direct under the projects method directory to get sheduled
KPR#:274873 With SQL query the Instrument Group is "Defined by LIMS"
KPR#:420338 Scheduler Acquisition Agents do not function and do not restart
KPR#:421791 Sample scheduler missing event from very short acq. methods
KPR#:422891 Sample Scheduler doesn't offer dual External injection when GC is configured with dual gas sampling valves only
KPR#:430672 Analysis gets stuck in state "in progress" in Sample Scheduler if no signal is saved
KPR#:435752 error "Instrument did not come online in 120 seconds" even the instrument is online
KPR#:447356 Sequence abort leads to sequence in error
KPR#:623210 Sequence can be scheduled twice if CDS Acquisition window gets opened during scheduling
KPR#:623251 Analysis in error status with error reported "instrument did not online in 120 seconds" when instrument is online and ready
KPR#:623556 Wrong error message can get reported with a sequence
KPR#:632134 When scheduling multiple instruments in parallel ICDS errors are possible
KPR#:710133 Running Sample scheduler acquisition agent crashes if Orchestrator is restarted
KPR#:732690 A sequence including non-readable characters send to acquisition via Api cannot be saved and run.
KPR#:741211 Communication error occurs while trying to reach Agilent.Scheduler.Agent
KPR#:964034 Analysis hanging in "in Progress" or "Submitted" state on a slow system with different connections.
KPR#:969325 API connection cannot be established when Acquisition Agente crashes at register Services step
KPR#:1067379 Previous message is not correctly cleared from Warning for a restarted sequence
KPR#:1124762 For sequence lines, except filter button remaining all action buttons are disabled if sequence is created via v3 route.
KPR#:1228894 Possible deadlock of the instrument connection when it gets interrupted

Keyword: Administration

KPR#:720429 OpenLab Server and OpenLab ECM XT v2.7 won't add user in a multi-forest domain

Keyword: Configuration

KPR#:170045 When changing the password of the EZChrom Instrument Service Account, manually change the Scheduler Agent service properties
KPR#:172871 Update OpenLAB Services Credentials does not work when opening Scheduler Configuration from Client shortcut
KPR#:177696 Auto-assign Instruments crashes Sample Scheduler Configuration
KPR#:180940 Injection Source can sometimes not be gathered on CDS 2.3
KPR#:195581 Unconfigured Sample Scheduler Agent causes Windows logs on CDS 2.3 AIC's
KPR#:205622 For client installation create / drop database rights are needed
KPR#:211945 Sample Scheduler Agents can show up a second time in the Scheduler Configuration Deployment tab
KPR#:228221 Sample Scheduler stops working after 100 days
KPR#:240560 Some validation check missing when creating instruments with wrong setup instrument groups
KPR#:276942 After AIC Update to CDS 2.4 Sample Scheduler Agents cannot get reconfigured
KPR#:281154 Instrument - Agent assignments can get lost in the Sample Scheduler configuration
KPR#:378077 LIMS notification for Oracle db fails
KPR#:385666 LIMS or Scheduler Agent or Web Interface installation with external database using Windows authentication rolls back
KPR#:390593 Installations of Agent and Client on new CDS 2.4 AIC are not configured
KPR#:396748 Sample Scheduler 2.4 does not work with CDS 2.4 and EZChrom A.04.09 in mixed environment on ECM 3 backend
KPR#:397779 CDS 2.5 Server update: could not stop Services if Sample Scheduler service is running
KPR#:398779 LIMS or Scheduler Agent or Web Interface installation wth external database using Windows authentication rolls back
KPR#:402061 Sample Scheduler 2.1, 2.2 and 2.3 are not compatible with CDS 2.5
KPR#:427168 Sample Scheduler Client crashes with user in OLSS which got deleted from Domain
KPR#:443116 Ezchrom result set cannot be loaded out of Sample Scheduler with ECM 3.6
KPR#:445111 Scheduler Acquisition Agent hangs when Instrument name upper/lower case changes
KPR#:445267 Installation against existing OLDR Scheduler Database fails with wrong password
KPR#:463160 With Project Setting: "Always use Default Project" the Acquisition Agent will most likely not start
KPR#:465015 The Database Migration to revision 2.5 does not migrate Analysis Variable 1
KPR#:480083 Scripted update installation fails on SQL with Windows authentication
KPR#:487608 Installation on EZChrom A.04.10 with OLDR does not work
KPR#:487609 Common projects of CDS 2.5 and EZChrom A. 04.10 are not supported in mixed mode
KPR#:504585 Sample Scheduler 2.6 for OpenLab requires the .NET framework 4.7.2, ASP.NET Core, and .NET Core 3.1
KPR#:508922 A instrument group with no lines can crash the LIMS agent or Scheduler Client
KPR#:513805 LIMS connection and Instrument groups information can get lost
KPR#:528538 Instrument agent cannot assign to instrument if instrument name end with a space
KPR#:533092 Restart Instructions in Configuration after saving are not complete
KPR#:533258 Sample Scheduler services may not start automatically on server or AIC after reboot
KPR#:553605 Using common database connection information is important at Scheduler Database install with MS-SQL
KPR#:564777 Sporadically an Autofill template cannot be deleted
KPR#:570835 The Scheduler Webserver can be installed on any server with the necessary CDS components
KPR#:572106 A second Scheduler Agent visible on AIC in error state
KPR#:584946 Windows authentication for SQL server for services running with specific logon user does not work after update.
KPR#:588637 Crash when trying to use Sample Scheduler Client on system with duplicated project names after 'OK' the warning
KPR#:597087 After activating sample scheduler 2.6 system ran out of instrument license
KPR#:597424 LIMS Agent crashes when having more than one LIMS with the same Processed folder
KPR#:623773 If instrument, user ids or project names are not unique they will be disabled
KPR#:642345 Sample Scheduler 2.5 Update 6 and 7 cannot be installed on upgraded system
KPR#:673752 Update installer switched used database from SQL to OLDR
KPR#:691618 Login to 2.6 web interface not possible after installation on system where 2.7 was installed
KPR#:695451 Sample Scheduler 2.6 update 4 installation fails on AIC and Client
KPR#:695795 Error message for duplicate projects and instruments when starting desktop applications
KPR#:700611 Client and Configuration do not open with error message: Error reading JToken from JsonReader...
KPR#:708428 Balance bridge crashes if no task younger than 3 days is available in LabX
KPR#:727102 With a non-CDS project as first one instrument not forced to use a dedicated project Sample Scheduler Acquisition Agents do not start
KPR#:981017 Duplicated instrument names lead to other instruments not appearing.
KPR#:985438 Enterprise: LIMS agent crashed because one of the orchestrator is not started
KPR#:986922 Error message during uninstallation that database is not reachable
KPR#:1043046 When .Net 3 and .Net 5 get removed according to ServiceNote_D0109719 Sample Scheduler stops working
KPR#:1051280 DB user not changed to 'OpenLabSchedulerDB270User' with CDS 2.8 Upgrade
KPR#:1052732 Webserver does not start after adding a second or third node on an enterprise system
KPR#:1052762 Database Migration Tool throws an exception, cannot find Agilent.OpenLab.Configuration.xml
KPR#:1054206 Database Migration Tool cannot connect to MS-SQL DB with Windows Authentication.
KPR#:1055921 After ECM XT or OpenLab Server upgrade services will logon with Local System and may not start or work as before
KPR#:1060145 Sample Scheduler Configuration does not open "Error reading JToken from JsonReader."
KPR#:1066974 Services cannot checkout license on scalable system
KPR#:1073588 Webserver service is not stopping / restarting after changing the password of OpenLabSchedulerDB270User.
KPR#:1081101 LIMS agent stops working if less LIMS licenses are available then XML connections
KPR#:1088254 referenced NuGet (NPGSQL) package has vulnerabilities
KPR#:1113665 ag-grid package 30.1.0 has a vulnerability
KPR#:1123761 With multiple XML Lims Connections configured, and not enough licenses for all connections, no XML connection works
KPR#:1126396 With duplicate usernames from different domains Sample Scheduler cannot work
KPR#:1136372 Installation of Sample Scheduler 2.8 Update 1 or Update 2 may roll back
KPR#:1172358 If LabX exceeds variable limit it leads to repeating errors in the webserverservice.log
KPR#:1178093 Balance Data Bridge throws exception with only CR LF in tasks.dat
KPR#:1186337 Sample Scheduler 2.7 update 2 installation may fail on actual Windows
KPR#:1216379 After DB migration another Default LIMS connection is present and cannot be deleted
KPR#:1278458 The Sample Scheduler Server topology is not functional

Keyword: Localization

KPR#:103423 The instrument error messages from the CDS to the Scheduler UI are not localized

Keyword: Performance

KPR#:221092 Internet Explorer reacts slow when opening web interface windows
KPR#:399193 When scrolling fast in about 6000 analyses the Web-Interface sometimes hangs
KPR#:555008 Sample Scheduler generates high load on SQL Server
KPR#:557499 Change Tracking in SQL Server database is set to 2 days
KPR#:726704 Sample Scheduler Acquisition can get slower over the time with CDS 2.5, 2.6, 2.7
KPR#:751284 Large Sequences coming from LIMS over SQL have Transfer Delay

Keyword: User Interface

KPR#:144633 Ended sequences can disappear from the review table
KPR#:168116 The Sample Scheduler Client has a minimum vertical graphic resolution of 800
KPR#:178556 Cannot change vial number in the Web Interface, Analysis view
KPR#:182802 Stop instrument button doesn't work for sequences
KPR#:191168 Sample Customer Parameters with type text get displayed as numbers if they contain a number
KPR#:204296 When the session is locked the username field of the unlock dialog is case sensitive
KPR#:206784 Changing fields with "tab" get stuck at "sample custom parameters"
KPR#:214966 Edit analysis - right cursor can select field on the left
KPR#:290197 Sample Scheduler client sometimes crashes when used with Sample Custom Parameters
KPR#:368819 In the Web Interface the Sequence line does not stay in focus
KPR#:432541 The Sequence Column Chooser in the Web shows problems with Internet Explorer
KPR#:450339 In Windows Client it is possible to edit other fields than Sign-off and LIMS Connection
KPR#:513261 Expanded sequence is not rendered correctly in the web interface
KPR#:524211 Services of configured sample scheduler does not start after upgrading CDS
KPR#:531131 Web Interface scrollbars may miss on Mac OS with Safari or Chrome
KPR#:535685 My Instrument view is empty if locked
KPR#:537158 Progress bar in the Web Interface may not vanish
KPR#:590715 My Instruments view case sensitive with regard to user name
KPR#:622449 In Sample Scheduler the error message can be displayed for the previous analysis
KPR#:702595 In Sample Scheduler- 2.6 Update 5, the user might see duplicate projects.
KPR#:1171821 After upgrade new Web features may not be shown, caused by browser cache
KPR#:1172892 With a non-CDS project as default project, a new analysis in the Web gives empty error
KPR#:1182419 Chrome on Android tablet may not have the ability to view pdfs inside the browser
KPR#:1197872 When an instrument is waiting for manual injection, the runtime gets started
KPR#:1206208 In column chooser Show/hide columns is not possible with the tapping
KPR#:1206672 Info icons are not aligned with highlighted cell lines
KPR#:1221892 With Safari 17 or below on iOS/MacOS at sequence creation no analysis lines get displayed

Keyword: Workflow

KPR#:124116 Autofill doesn't work for DataFile, ResultPath
KPR#:167960 Error message when CDS runs submitted through scheduler and audit trail is enabled
KPR#:173213 Analysis from LIMS for in Scheduler not configured instruments getting into Analysis Table
KPR#:176277 Merging analysis with <ID> token in sample name, causes new sample name to be cryptically
KPR#:220916 Sample Custom Parameter not added to sequence lines if adding sequence lines in sequence subwindow
KPR#:221513 The second signal of a dual analysis is not displayed in the review tab
KPR#:361573 In the manual of 2.3 the SampleCustomParameter for SQL is not correct explained
KPR#:381891 Manually created analysis can be signed of for LIMS is wrong documented in revision 2.4.
KPR#:417454 Sequence position is ignored when importing sequence via SQL
KPR#:419144 With UNC path saved as Result path in the Sample Scheduler Client the application may crash
KPR#:459661 When a sequence gets created in the Web Interface it cannot be scheduled without editing it
KPR#:485558 Project setting changes not reflected in active acquisition session
KPR#:609898 Sample Prep method of Sequence template is not applied to sequence during rollout
KPR#:722331 Domain accounts from LabX and Sample Scheduler are not matched
KPR#:750844 Sequence from LIMS over SQL cannot be created and stay as single runs because a run is in edition
KPR#:970848 Merged duals do not provide dual instrument groups in the Client
KPR#:1097274 Validation error when sequence template contains tokens
KPR#:1110928 Sequences created by the v3 API do not default the result field
KPR#:1171415 Not Available instrument state causes Balance Bridge data transfer to fail

Keyword: 

One-line Description:

Sample Scheduler 2.4 Agent cannot launch the instrument on CDS2.5 upgraded from CDS2.4

Problem:

Sample Scheduler Agent cannot launch the instrument on CDS2.5 upgraded from CDS2.4 and the restart of the Scheduler Agent failed. OpenLab CDS 2.4 still exist in the installed software after upgrade to OpenLab CDS 2.5. The CDS 2.5 without Sample Scheduler works without error. So the instrument can launch from OpenLab CDS Control Panel. 
But the instrument cannot be launched by an Sample Scheduler Agent.

Temporary Solution:

On a clean CDS 2.5 installation without OpenLab CDS 2.4 still exist in the installed software after upgrade to OpenLab CDS 2.5 there is no problem.

Fix Information:

This defect is fixed in Sample Scheduler 2.5

Keyword: 

One-line Description:

Sequence cannot be acquired because sequence set already exists

Problem:

It can happen that a with Sample Scheduler acquired and ended sequence cannot be resubmitted. This can happen when no timestamp is added to the result name like with the "DefaultResultName". 

Temporary Solution:

Workaround: Change both result name and result path

Fix Information:

A fix will be provided with Sample Scheduler 2.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:

Common projects of CDS 2.5 and EZChrom A. 04.10 are not supported in mixed mode

Problem:

Sample Scheduler does not support Common projects of CDS 2.5 and EZChrom A. 04.10 in mixed mode. In such a common project no methods can be selected in the Analysis Table for EZChrom  instruments. 

Temporary Solution:

n/a

Fix Information:

As long Common projects of CDS 2.5 and EZChrom A. 04.10 are not supported in mixed mode, no fix for Sample Scheduler is needed. 

Keyword: 

One-line Description:

Client crash when using filtering

Problem:

Filtering a large amount of analysis can cause intermittently a crash of the Client. 

Temporary Solution:

n/a

Fix Information:

A defect was fixed in Sample Scheduler 2.5 Update 5 when only lines are highlighted and no cells, and lines disappear when filtering which caused a Client crash. 

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:

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:

Sample scheduler client crashes for OS user that did not install sample scheduler

Problem:

The Sample scheduler client crashes during starting with the error message
---------------------
Application Dispatcher Unhandled Exception
Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "Agilent.Scheduler.Libraries.Database.DatabaseAccessor", name = "(none)".
Exception occurred while: Calling constructor Agilent.Scheduler.Libraries.Database.DatabaseAccessor(Agilent.Scheduler.Libraries.Database.IDatabaseSettings settings, Agilent.Scheduler.Libraries.Time.ITimeProvider timeProvider, Agilent.Scheduler.Libraries.Compliance.IAuditTrailIdentification auditTrailIdentifier).
Exception is: InvalidOperationException - An exception has been raised that is likely due to a transient failure.
-------------------------------
This is a problem that will only occur on a workstation. As a workstation installation is not supported, only a workaround is available.

Temporary Solution:

The workaround is to allow the local group "Users" read access to the file "C:\ProgramData\Agilent\Installation\configuration.xml". The way to do this is as follows on a PC with English OS. If you have a different language, you must replace "Users" in the line starting with "$accessRule =" with the appropriate group name in local language. For example "Benutzer" for a German OS.
1. Logon to the PC as a user that is a member of the local group Administrators
2. Open a PowerShell using "Run as Administrator"
3. Type the following commands:
$acl = Get-Acl "C:\ProgramData\Agilent\Installation\configuration.xml"
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule("Users", "Read", "Allow")
$acl.SetAccessRule($accessRule)
Set-Acl "C:\ProgramData\Agilent\Installation\configuration.xml" $acl

Fix Information:

There is no fix planned for Sample Scheduler or CDS as a Workstation Plus is not a supported configuration. 

Keyword: Acquisition

One-line Description:

Openlab EZChrom methods have to be direct under the projects method directory to get sheduled

Problem:

To schedule a run fails if the used Openlab EZChrom method is in a subfolder and not direct under the projects method directory 

Temporary Solution:

Use methods from the projects methods directory, not from a subfolder

Fix Information:

Fixed in Sample Scheduler for OpenLab revision 2.2 and in Update 1 for 2.1 which is the revision 2.1.1

Keyword: Acquisition

One-line Description:

With SQL query the Instrument Group is "Defined by LIMS"

Problem:

When analyses get created in the Sample Scheduler revision 2.2.0 via SQL query the instrument group is always filled with "Defined by LIMS". 
For this, the instrument cannot be adjusted for these analyses.

Temporary Solution:

n/a

Fix Information:

This issue is fixed in Sample Scheduler revision 2.3 and in Update 1 for Sample Scheduler revision 2.2.

Keyword: Acquisition

One-line Description:

Scheduler Acquisition Agents do not function and do not restart

Problem:

Sample Scheduler does not handle the error correctly where the analysis goes from validating in the CDS into error. This leads to a Scheduler Acquisition Agents which does not function and does not restart in the Sample Scheduler Configuration Deployment Tab. 

Temporary Solution:

PC restart helps to recover the services

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Acquisition

One-line Description:

Sample scheduler missing event from very short acq. methods

Problem:

When an analysis with a very short acquisition method like 0.1 min is scheduled the analysis can get stuck in state "in progress". This may happen e.g. with a shutdown method. 

Temporary Solution:

Use a method which exceeds the time which causes the problem

Fix Information:

Fixed in Sample Scheduler revision 2.5

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:

Analysis gets stuck in state "in progress" in Sample Scheduler if no signal is saved

Problem:

If an analysis is scheduled without saving a signal of the sample like in a shutdown method, the analysis stuck in state "in progress" in the sample scheduler even if it is ended in the acquisition.

Temporary Solution:

When some signal is saved on low data rate the method does not get stuck

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Acquisition

One-line Description:

error "Instrument did not come online in 120 seconds" even the instrument is online

Problem:

Analysis turns into error with the message "Instrument did not come online in 120 seconds" even the instrument is online. This happens when the instrument connection gets manually closed or the connection gets detected as lost.

Temporary Solution:

Restarting the Scheduler Agent in the deployment tab should recover the situation.

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Acquisition

One-line Description:

Sequence abort leads to sequence in error

Problem:

When a sequence gets aborted shortly after it was scheduled, it may lead to the sequence in error state with the "Error Information: Sequence: Unexpected error: There are no active runs to abort.."

Temporary Solution:

n/a

Fix Information:

Fixed with Sample Scheduler 2.6

Keyword: Acquisition

One-line Description:

 Sequence can be scheduled twice if CDS Acquisition window gets opened during scheduling

Problem:

If a sequence gets scheduled during the CDS Acquisition of the instrument window opens, it can happen that the sequence gets scheduled twice.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.5 Update 8 and Sample Scheduler 2.7

Keyword: Acquisition

One-line Description:

Analysis in error status with error reported "instrument did not online in 120 seconds" when instrument is online and ready

Problem:

When the Scheduler Acquisition Agent is running, has a connection to a CDS AcquisitionServer service and the connection to the Instrument get closed via the CDS Control Panel and reestablished by opening an Acquisition Client, then the Scheduler Acquisition Agent does not realize that the Acquisition Agent was terminated and will not reinitiate the connection. 
When in this state an analysis gets scheduled, the Scheduler Acquisition Agent waits for an instrument state change from the no more existing Acquisition Agent process and runs into timeout.

Temporary Solution:

Restart the Scheduler Agent (effects all Scheduler Acquisition Agents on this AIC) or:
Close the Connection in the Control Panel again and let the Scheduler Acquisition Agent reestablish the connection by itself when the next analysis is scheduled

Fix Information:

Fixed in Sample Scheduler 2.5 Update 8, Sample Scheduler 2.6 Update 4 and Sample Scheduler 2.7

Keyword: Acquisition

One-line Description:

Wrong error message can get reported with a sequence

Problem:

The error message from the previous sequence might be reported to the current line of the current sequence even when the current sequence does finish without error

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.5 Update 8 and Sample Scheduler 2.7

Keyword: Acquisition

One-line Description:

When scheduling multiple instruments in parallel ICDS errors are possible 

Problem:

When scheduling multiple instruments in parallel on the same Instrument Controller, ICDS errors may occur for some runs. 

Temporary Solution:

If analysis on the same instrument controller get scheduled with some time delay in between and not at once this is unlikely to happen

Fix Information:

Fixed in Sample Scheduler 2.7 and in Sample Scheduler 2.5 Update 10

Keyword: Acquisition

One-line Description:

Running Sample scheduler acquisition agent crashes if Orchestrator is restarted

Problem:

A running Sample scheduler acquisition agent crashes if the Orchestrator is restarted. The analyses which ended during the Orchestrator is stopped get into error state in Sample Scheduler.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8

Keyword: Acquisition

One-line Description:

A sequence including non-readable characters send to acquisition via Api cannot be saved and run.

Problem:

When submitting a sequence to the acquisition via the acquisition Api, some characters, at least in the barcode field lead to acquisition not being able to save the sequence and thereby not be able to run it. This can e.g. with the use of the balance bridge transferring the information over Sample Scheduler to the acquisition. 
Some barcode reader default settings might insert non readable characters.

Temporary Solution:

Prevent the transfer of non-readable characters to acquisition.

Fix Information:

The problem is documented in the user info of Sample Scheduler 2.8. 
This is not planned to be fixed by software changes in Sample Scheduler or Balance Bridge for LabX.

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:

Analysis hanging in "in Progress" or "Submitted" state on a slow system with different connections.

Problem:

Analysis can hang in "in Progress" or "Submitted" state on a slow system with different connections when a concurrency issue happens at cleaning up the connections. 

Temporary Solution:

Delete hanging Analysis from Sample Scheduler and restart the Scheduler Agent

Fix Information:

Fixed in Sample Scheduler 2.7 Update 1

Keyword: Acquisition

One-line Description:

API connection cannot be established when Acquisition Agente crashes at register Services step

Problem:

When Sample Scheduler tries to establish an acquisition API connection the acquisition agente process, it starts and crashes immediately at the register service step. Then the API connection cannot be established from Sample Scheduler and the information flow with CDS Acquisition stops. 

Temporary Solution:

Reboot the AIC

Fix Information:

Fixed in Update 1 for Sample Scheduler 2.7

Keyword: Acquisition

One-line Description:

Previous message is not correctly cleared from Warning for a restarted sequence

Problem:

When a failed sequence gets restarted, the previous error message is not cleared and is shown in addition in the error information.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 Update 2

Keyword: Acquisition

One-line Description:

For sequence lines, except filter button remaining all action buttons are disabled if sequence is created via v3 route.

Problem:

For sequence lines, except filter button remaining, all action buttons are disabled if sequence is created via v3 Rest API route which gets used by SLIMS.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 Update 2

Keyword: Acquisition

One-line Description:

Possible deadlock of the instrument connection when it gets interrupted

Problem:

There is a possible deadlock of the instrument connection when it gets interrupted. After the expiration of the 10min grace period for the recovery of the connection the sample scheduler waits on the last created connection for state change and ignores every other event.

Temporary Solution:

Restart the corresponding Sample Scheduler Agent

Fix Information:

Fixed in Sample Scheduler 2.9, and Sample Scheduler 2.8 Update 4

Keyword: Administration

One-line Description:

OpenLab Server and OpenLab ECM XT v2.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 with OpenLab Server 2.8 and OpenLab Server 2.7 Update 01.

Keyword: Configuration

One-line Description:

When changing the password of the EZChrom Instrument Service Account, manually change the Scheduler Agent service properties

Problem:

On systems with OpenLAB CDS EZChrom based Scheduler Agents, the password of the Scheduler Agent service user has to be modified manually under properties/Log on after changing the password of the EZChrom Instrument Service Account. 

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Configuration

One-line Description:

Update OpenLAB Services Credentials does not work when opening Scheduler Configuration from Client shortcut

Problem:

When opening the Sample Scheduler Configuration from the shortcut in the Scheduler Client the "Update OpenLAB Services Credentials" button does not work as expected. User gets an error message that "User is not Authenticated." 

Temporary Solution:

For "Update OpenLAB Services Credentials" open the Sample Scheduler Configuration from the Windows Start menu.

Fix Information:

Fixed in Sample Scheduler revision 2.1

Keyword: Configuration

One-line Description:

Auto-assign Instruments crashes Sample Scheduler Configuration

Problem:

When a instrument gets created in the OpenLab Control Panel with open Sample Scheduler Configuration, and no 'Refresh' was done before 'Auto-assign Instruments' the Sample Scheduler Configuration crashes with the error: 'An unexpected error occurred, the application will terminate. Sequence contains no matching element'
The application terminates without saving the edited parameters. 

Temporary Solution:

Just before 'Auto-assign Instruments' do a 'Refresh'

Fix Information:

Fixed in Sample Scheduler revision 2.2

Keyword: Configuration

One-line Description:

Injection Source can sometimes not be gathered on CDS 2.3

Problem:

With new configured instruments the Injection Source can sometimes not be gathered on CDS 2.3.

Temporary Solution:

n/a

Fix Information:

The problem is fixed in Sample Scheduler revision 2.2

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:

For client installation create / drop database rights are needed

Problem:

For the installation of the Sample Scheduler clients a check enforces that the user has create / drop database rights. For the installation of the client software this is not necessary and the check should be removed. 

Temporary Solution:

Install with a user that has the drop / create database rights, after completing installation change the database credentials with the database reconfiguration utility.

Fix Information:

Fixed in Sample Scheduler for OpenLab revision 2.2 and in Update 1 for revision 2.1

Keyword: Configuration

One-line Description:

Sample Scheduler Agents can show up a second time in the Scheduler Configuration Deployment tab

Problem:

In a Sample Scheduler System with PC's with Scheduler Agents on EZChrom the Agent can show up a second time in the Scheduler Configuration Deployment tab. This can happen when the EZChrom was not detected by Sample Scheduler for example when it was uninstalled for a repair. When EZChrom is not detected, CDS 2 will get defined as default CDS, which creates a second database entry with the new CDS.

Temporary Solution:

n/a

Fix Information:

The problem is fixed in Sample Scheduler revision 2.2

Keyword: Configuration

One-line Description:

Sample Scheduler stops working after 100 days

Problem:

The Sample Scheduler for OpenLab stops working after 100 days, when the OpenLab service credentials do not get changed or reapplied in between 100 days. At initial configuration or when the OpenLab CDS service credentials get changed or reapplied, a authentication ticket gets issued which expires after 100 days. the OpenLab service credentials can get changed or reapplied in the Sample Scheduler Configuration in the Maintenance tab. 

Temporary Solution:

Update the OpenLab Service credentials in the Sample Scheduler Configuration under Maintenance and restart the services before 100 days.

Fix Information:

Fixed in Sample Scheduler for OpenLab revision 2.2

Keyword: Configuration

One-line Description:

Some validation check missing when creating instruments with wrong setup instrument groups

Problem:

With an invalid configuration of an instrument group in the sample scheduler configuration (E.g. by using projects which are restricted) there is no validation either in the configuration nor in the client. With applying autofill of the instrument group with the invalid configuration to an analysis this will be filled up without evaluation. It would not be possible to set up same analysis manually because the verification will not allow to create this analysis.

Temporary Solution:

Correct the instrument group configuration to prevent such problem

Fix Information:

A fix is planned for a later revision of Sample Scheduler

Keyword: Configuration

One-line Description:

After AIC Update to CDS 2.4 Sample Scheduler Agents cannot get reconfigured

Problem:

After updating OpenLab CDS 2 AIC's to version 2.4 it is not possible to reconfigure the Sample Scheduler Agent installation when a Sample Scheduler Agent revision below 2.2 was installed before. When Sample Scheduler revision 2.2 is already installed before CDS 2.4 update this installation stays functional. 

Temporary Solution:

Do either of:
- Uninstall Sample Scheduler revision 2.1 or 2.0 before CDS AIC Update to 2.4 and update the Sample Scheduler components on all non AIC's to revision 2.2. Then the Scheduler Agent which gets installed by CDS 2.4 on the AIC can be remote configured with the Sample Scheduler Configuration utility. 
- Uninstall the Sample Scheduler Agent installation after updating the AIC to CDS 2.4 with a Sample Scheduler version below 2.2 installed, then install the necessary version of the needed Sample Scheduler components. 
- if Sample Scheduler will not be used, no action is needed

Fix Information:

A fix is planned for the OpenLab CDS 2.5 installer. The Sample Scheduler revision 2.3 includes the fix, but the OpenLab CDS 2.4 media will use the faulty Sample Scheduler revision 2.2 installer in case of an upgrade of an existing Sample Scheduler installation which is default on CDS AIC's since CDS 2.3.

Keyword: Configuration

One-line Description:

Instrument - Agent assignments can get lost in the Sample Scheduler configuration

Problem:

When someone saves changes in the Instrument Management tab of the Sample Scheduler configuration which does not have the rights to see all instruments, the Instrument - Agent assignments of the instruments not visible for this user will get lost. 

Temporary Solution:

Grant all administrators access to all instrument

Fix Information:

A fix is included in Sample Scheduler revision 2.3

Keyword: Configuration

One-line Description:

LIMS notification for Oracle db fails

Problem:

When a LIMS use a oracle db and Sample Scheduler is configured to use the System.Data.OracleClient the LIMS notification command throws a illegal variable exception. 

Temporary Solution:

Use ORACLE db Integration over ODBC with the 32-bit oracle instantclient and the ODBC driver. Configure ODBC Data Sources (32bit). Change to the Tab System DSN. Add and select the Oracle instantclient. Enter the Information for the Oracle db connection. Enter the TNS name from the tnsnames.ora file. 
Configure Sample Scheduler to use Database Provider: System.Data.ODBC
Connection String
dsn=[datasourcename from ODBC data sources]; Uid=[userName]; Pwd[Password];
Note no blanks between data source name and ; and before and after =
LIMS Notification: Oracle uses “:” instead “@” as marker for variables and the names are cases sensitive.

Fix Information:

A fix is planned in Sample Scheduler for OpenLab revision 2.4

Keyword: Configuration

One-line Description:

LIMS or Scheduler Agent or Web Interface installation with external database using Windows authentication rolls back

Problem:

The Sample Scheduler installation of the LIMS Agent, the Scheduler Agent or the Web Interface rolls back when an external MS SQL database server with Windows authentication is used. The services try to connect with the local system account to the database and this fails. 

Temporary Solution:

There is a work around for this initial installation problem using the scripted installation described in the installation manual, where the account for the LIMS Agent, the Scheduler Agent and the Web Interface can be selected with the optional parameters: SERVICE_LOGON_FULLY_QUALIFIED_NAME and SERVICE_LOGON_PASSWORD. This user needs the right to logon as a service. The example script in the installation manual which is written for PowerShell (`"<credentials>`") needs to be modified if used for command prompt ("<credentials>"). 

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Configuration

One-line Description:

Installations of Agent and Client on new CDS 2.4 AIC are not configured

Problem:

When installing a Scheduler Agent and a Scheduler Client on an CDS 2.4 AIC, the preinstalled 2.3 Scheduler Agent gets updated to 2.4 and an 2.4 Scheduler Client gets installed. Both installations will stay unconfigured if the preinstalled Scheduler Agent was not configured before. 

Temporary Solution:

Configure the installation with the Database Reconfiguration Tool.

Fix Information:

Fixed in Sample Scheduler revision 2.5, with showing a message that it is necessary to configure the installation with the Database Reconfiguration Tool.

Keyword: Configuration

One-line Description:

Sample Scheduler 2.4 does not work with CDS 2.4 and EZChrom A.04.09 in mixed environment on ECM 3 backend

Problem:

Sample Scheduler 2.4 does not work with CDS 2.4 and EZChrom A.04.09 in mixed environment on ECM 3 backend. When opening a Sample Scheduler Client or Configuration an exception occurs and the software does not start. 

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Configuration

One-line Description:

CDS 2.5 Server update: could not stop Services if Sample Scheduler service is running

Problem:

When a CDS system with Sample Scheduler gets updated to CDS 2.5, the CDS server installation may stop in "Step 4 - Configure OpenLab COntent Management" during the step "stop services". The Sample Scheduler LIMS agent e.g. is not stopped by the CDS server update installer.

Temporary Solution:

Stop all Sample Scheduler relates services with the name: "Agilent..." before Server update

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Configuration

One-line Description:

LIMS or Scheduler Agent or Web Interface installation wth external database using Windows authentication rolls back

Problem:

The Sample Scheduler installation of the LIMS Agent, the Scheduler Agent or the Web Interface rolls back when an external MS SQL database server with Windows authentication is used. The services try to connect with the local system account to the database and this fails. 

Temporary Solution:

There is a work around for this initial installation problem using the scripted installation described in the installation manual, where the account for the LIMS Agent, the Scheduler Agent and the Web Interface can be selected with the optional parameters: SERVICE_LOGON_FULLY_QUALIFIED_NAME and SERVICE_LOGON_PASSWORD. This user needs the right to logon as a service. The example script in the installation manual which is written for PowerShell (`"<credentials>`") needs to be modified if used for command prompt ("<credentials>"). 

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Configuration

One-line Description:

Sample Scheduler 2.1, 2.2 and 2.3 are not compatible with CDS 2.5

Problem:

When Sample Scheduler revision 2.1, 2.2 or 2.3 are connecting to a CDS 2.5 backend or Shared Services Server the application will crash. A typical error message which can appear is: An unexpected error occurred, the application will terminate. For use with CDS 2.5 components Sample Scheduler 2.4 or above revision is needed. 

Temporary Solution:

n/a

Fix Information:

The compatibility statement is fixed in Sample Scheduler revision 2.5
The functionality works with Sample Scheduler 2.4

Keyword: Configuration

One-line Description:

Sample Scheduler Client crashes with user in OLSS which got deleted from Domain

Problem:

When a Domain user is added to the users in Shared Services and then gets deleted from the domain the Sample Scheduler Client does not open but terminates unexpectedly. 

Temporary Solution:

Remove the user or group which got deleted from the Domain in the Shared Services Control Panel. 

Fix Information:

Fixed in Sample Scheduler 2.5.
The Sample Scheduler does not crash any more but behaves very slow. 

Keyword: Configuration

One-line Description:

Ezchrom result set cannot be loaded out of Sample Scheduler with ECM 3.6

Problem:

An Ezchrom result set cannot be loaded in EZChrom out of Sample Scheduler with ECM 3.6 backend in the result review. 

Temporary Solution:

n/a

Fix Information:

A fix for the EZChrom ATK has to be provided by EZChrom A.04.09 Update 07

Keyword: Configuration

One-line Description:

Scheduler Acquisition Agent hangs when Instrument name upper/lower case changes

Problem:

When a Instrument name gets changed from upper to lower cases or vice versa in the OpenLab Control Panel the corresponding Sample Scheduler Acquisition Agent is no more operational, but OpenLab CDS 2 Acquisition works as before. The error message in the Scheduler Acquisition log is not helpful in this case. 

Temporary Solution:

Delete the instrument configuration in the OpenLab Control Panel, reboot the Scheduler Agent PC, configure the instrument in the OpenLab Control Panel and then in Sample Scheduler

Fix Information:

Fixed in Sample Scheduler revision 2.5 with improved error message in the logs and to recover the Scheduler Configuration Instrument Management needs to be saved with the new name and the corresponding agents need to be restarted

Keyword: Configuration

One-line Description:

Installation against existing OLDR Scheduler Database fails with wrong password

Problem:

At installation of the Sample Scheduler with OLDR database a password has to be specified. This password needs to be used at Sample Scheduler LIMS Agent reinstallation when the database content should be reused with the existing experiments and configuration. There is no warning if the OLDR password does not match at reinstallation. Only recreating the database is possible with a different password. Without recreating the database and wrong password the installation ends prematurely and rolls back. 

Temporary Solution:

Keep the password for the Sample Scheduler OLDR database created at installation to be used at reinstallation. 
Only recreating the database is possible with a different password. 

Fix Information:

A fix will be provided with Sample Scheduler 2.6

Keyword: Configuration

One-line Description:

With Project Setting: "Always use Default Project" the Acquisition Agent will most likely not start

Problem:

When a instrument has the Project Setting: "Always use Default Project" in the Control Panel, the Scheduler Acquisition Agent will most likely not start. The corresponding Scheduler Agent may stop with error: "Could not get communication pipe to instrument agent...".

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.5 Update 1 and Sample Scheduler 2.6

Keyword: Configuration

One-line Description:

The Database Migration to revision 2.5 does not migrate Analysis Variable 1

Problem:

When migrating the Scheduler DB to revision 2.5, the Analysis Variable 1 will not be migrated.

Temporary Solution:

If not all Analysis Variables are used, the value of the Analysis Variable 1 which does not get migrated can be written into another Analysis Variable e.g. no. 5. before migration of the templates. 
The  Analysis Variables  2 to 5 get migrated. 
After migration the values of the Analysis Variable 1 can be updated with the correct value. Example: 
UPDATE [OpenLabSchedulerDB250].[openlabscheduler].[Experiments]
  set AnalysisVariable1 = AnalysisVariable5 

Fix Information:

An updated DB Migration Tool with the fix for that is delivered with Sample Scheduler 2.5 Update 1 and Sample Scheduler 2.6

Keyword: Configuration

One-line Description:

Scripted update installation fails on SQL with Windows authentication 

Problem:

Scripted or silent update installation of sample scheduler versions 2.1, 2.2, 2.3 fails when using Microsoft SQL with Windows authentication as Sample Scheduler database.

Temporary Solution:

n/a

Fix Information:

A fix will be provided with Sample Scheduler 2.6

Keyword: Configuration

One-line Description:

Installation on EZChrom A.04.10 with OLDR does not work

Problem:

Sample Scheduler installation on EZChrom is not supported with OLDR, neither mixed mode nor plain EZChrom.

Temporary Solution:

n/a

Fix Information:

Use Microsoft SQL as database for Sample Scheduler installation. This will be documented in the Sample Scheduler Installation Instructions of Sample Scheduler 2.6

Keyword: Configuration

One-line Description:

Common projects of CDS 2.5 and EZChrom A. 04.10 are not supported in mixed mode

Problem:

Sample Scheduler does not support Common projects of CDS 2.5 and EZChrom A. 04.10 in mixed mode. In such a common project no methods can be selected in the Analysis Table for EZChrom  instruments. 

Temporary Solution:

n/a

Fix Information:

As long Common projects of CDS 2.5 and EZChrom A. 04.10 are not supported in mixed mode, no fix for Sample Scheduler is needed. 

Keyword: Configuration

One-line Description:

Sample Scheduler 2.6 for OpenLab requires the .NET framework 4.7.2, ASP.NET Core, and .NET Core 3.1

Problem:

Sample Scheduler for OpenLab2.6 requires the .NET framework 4.7.2, ASP.NET Core, and .NET Core 3.1. The version for the .NET Core Runtime needs to be the same or higher as the version of the ASP.NET Core Runtime.
NOTE
For localized versions of Sample Scheduler for OpenLab, install the .NET framework language pack corresponding to the version of the .NET framework.

Temporary Solution:

This .NET software is not provided with the separate Sample Scheduler installer. It can be downloaded from Microsoft and is included in the CDS 2.6 installation software. 
The executables from the CDS 2.6 media are under \Setup\redist\DotnetCore

Fix Information:

n/a

Keyword: Configuration

One-line Description:

A instrument group with no lines can crash the LIMS agent or Scheduler Client

Problem:

When a instrument group gets configured with no instrument lines, using this instrument group from LIMS will crash the LIMS agent, using it with add analysis will crash the Scheduler Client. Error message of the client: "An unexpected error occurred, the application will terminate
Sequence contains no elements"

Temporary Solution:

Avoid instrument groups with no instrument group lines

Fix Information:

A fix is provided in Sample Scheduler 2.6 and 2.5 Update 2

Keyword: Configuration

One-line Description:

LIMS connection and Instrument groups information can get lost

Problem:

In the Sample Scheduler configuration the Instrument groups information in revision 2.4 or 2.5 and the LIMS connections information in revision 2.5 can get lost. When the Instrument groups or LIMS tab is unselected under Windows and the Configuration gets closed, this setting will be saved for the next session of the user. When the Configuration gets opened by this user the next time, the unselected tabs do not get loaded and the cached database fields stay empty. At any saving of the Configuration the empty database fields can overwrite the existing database values and this part of the Configuration gets lost. 

Temporary Solution:

Do not leave Sample Scheduler with the Instrument groups or LIMS tab unselected under Windows, or do not unselect this at all.

Fix Information:

A fix is provided in Sample Scheduler 2.6 and 2.5 Update 2

Keyword: Configuration

One-line Description:

Instrument agent cannot assign to instrument if instrument name end with a space

Problem:

If the instrument name end with a space, it cannot be assigned to a Sample Scheduler agent. The Sample Scheduler agent computer name goes back to blank. 

Temporary Solution:

Don't use instrument names with a space at the end of the name

Fix Information:

A fix will be provided in OpenLab Shared Services Server 3.6 which will correspond to CDS 2.7

Keyword: Configuration

One-line Description:

Restart Instructions in Configuration after saving are not complete

Problem:

After saving changes in the Sample Scheduler Configuration often a message pops up to restart certain Sample Scheduler components. This message might be incomplete. Sometimes it is in addition necessary to restart the Web Interface. A refresh of the Web client does not always solve the issue.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Configuration

One-line Description:

Sample Scheduler services may not start automatically on server or AIC after reboot

Problem:

After reboot of server or AIC, Sample Scheduler services may not startup automatically, even when this is their startup type. The services should start on manual request if all dependencies are available after reboot. 

Temporary Solution:

Easy workaround is to start these services manually. 
Increasing the services startup time may help: 
https://docs.microsoft.com/en-US/troubleshoot/windows-server/system-management-components/service-not-start-events-7000-7011-time-out-error
Or simply the startup setting "Automatic (Delayed Start)" for those services

Fix Information:

This cannot be fixed in Sample Scheduler. The usual means of Windows administration apply.

Keyword: Configuration

One-line Description:

Using common database connection information is important at Scheduler Database install with MS-SQL

Problem:

The "Scheduler Database" parameter for database access have to meet the database access requirements of all distributed Sample Scheduler components which need to access the database. It is not sufficient only to meet the needs of the local services which gets checked at installation. Otherwise services on other computers may not be able to start after installation, especially with MS-SQL database.

Temporary Solution:

The database access parameters can be adjusted after installation with the Agilent.Scheduler.Database.Access.Reconfiguration.exe tool which can be found in the Sample Scheduler installation directory under ...\bin. The default path is: C:\Program Files (x86)\Agilent Technologies\Sample Scheduler for OpenLab\Bin 

Fix Information:

The need for common database access parameters should be documented in the installation & configuration guide of revision 2.7. 

Keyword: Configuration

One-line Description:

Sporadically an Autofill template cannot be deleted

Problem:

In rear cases it happened that an Autofill template cannot be deleted. For example when it went as "In Progress" into the database with a race condition. 

Temporary Solution:

The autofill template can be removed from the Sample Scheduler database Analysis Table by qualified personal. 

Fix Information:

Fixed in Sample Scheduler 2.7

Keyword: Configuration

One-line Description:

The Scheduler Webserver can be installed on any server with the necessary CDS components

Problem:

In the Sample Scheduler for OpenLab Installation and Configuration Guide for revision 2.6 is written on page 22: Scheduler webserver must be installed on that server in the OpenLab system that manages Shared Services. 
This information is wrong. The Scheduler Webserver can be installed on any compatible server with Shared Services client or server components.

Temporary Solution:

The Scheduler Webserver can be installed on any compatible server with Shared Services client or server components.

Fix Information:

The installation instruction will be corrected in the next revision manual.

Keyword: Configuration

One-line Description:

A second Scheduler Agent visible on AIC in error state

Problem:

After some time of intensive operation, it can happen in seldom cases that for a few AIC's a second inactive Sample Scheduler Agent is shown in the Scheduler Configuration in the Deployment Tab. They show normally an error state. 

Temporary Solution:

When the active Sample Scheduler agent service is stopped both records for the Scheduler Agents of this AIC can be removed from the Sample Scheduler Database in the table 'AgentInstances' by qualified personal. After start of the Scheduler service a new entry will be generated in the database and the Deployment Tab will be cleaned up from the faulty entry. 
Contact Agilent before this risky operation on the database. 
The faulty entry does not prevent proper Sample Scheduler operation. 

Fix Information:

Partially fixed in Sample Scheduler 2.7. It prevents running 2 Scheduler agents on the same computer simultaneously. 

Keyword: Configuration

One-line Description:

Windows authentication for SQL server for services running with specific logon user does not work after update.

Problem:

When applying Sample Scheduler 2.5 Update 6 on a system with windows authentication for SQL server and services running with specific logon user, the system does no more work after the update. 

Temporary Solution:

The workaround is to start the update installer via command line and provide the service logon credentials e.g. 
C:\<filepath>>Sample.Scheduler.Patch.2.5.6.msp SERVICE_LOGON_FULLY_QUALIFIED_NAME="domain/username" SERVICE_LOGON_PASSWORD="password" /q

Fix Information:

The workaround is part of the Update installation instruction.

Keyword: Configuration

One-line Description:

Crash when trying to use Sample Scheduler Client on system with duplicated project names after 'OK' the warning

Problem:

When having OLSS server with multiple projects with the same name (possible via project groups), Sample Scheduler Client crashes after the warning was acknowledged with 'OK'. Using the Sample Scheduler Client  interface is no more possible until this configuration changes.

Temporary Solution:

Don't use multiple projects with the same name

Fix Information:

Fixed in Sample Scheduler 2.6 Update 3 and in Sample Scheduler 2.7

Keyword: Configuration

One-line Description:

After activating sample scheduler 2.6 system ran out of instrument license

Problem:

When there are multiple configurations of the same instruments in the CDS Control Panel, the Sample Scheduler instrument auto configuration will assign agents for all instruments at activation of Sample Scheduler 2.6 and tries to open a instrument connection which consumes a CDS instrument license. 
With more instruments configured than Instrument licenses are available, this can lead to a unusable or partial unusable Sample Scheduler installation. 

Temporary Solution:

After Sample Scheduler activation open the Sample Scheduler Configuration and clear in the Instrument Management tab the auto assigned Agent Computer Name of the duplicate Instrument Configurations

Fix Information:

Fixed as feasible in Sample Scheduler 2.7 with the possibility to uncheck the checkbox "Instruments are assigned automatically" at activation and assign instruments afterwards in the Sample Scheduler Configuration

Keyword: Configuration

One-line Description:

LIMS Agent crashes when having more than one LIMS with the same Processed folder

Problem:

It can happen that the LIMS Agent crashes if more than 1 LIMS is defined with the same processed folder in the Sample Scheduler Configuration in the LIMS tab.

Temporary Solution:

Configure different processed folders for different LIMS

Fix Information:

Fixed in Sample Scheduler 2.7

Keyword: Configuration

One-line Description:

If instrument, user ids or project names are not unique they will be disabled

Problem:

At Sample Scheduler application startup, a message may appear stating: "Sample Scheduler has detected the following instrument, user ids or project names that are not unique and will be disabled..." The architecture of Sample Scheduler until revision 2.7 does not allow duplicate project, duplicate user ids or duplicate instrument names. They will be disabled.

Temporary Solution:

Change the CDS configuration to no duplicate projects, duplicate user ids or duplicate instrument names.

Fix Information:

A fix is planned for Sample Scheduler 2.8. 
There will be no fix before 2.8 for the duplicate projects to be used. 
There is a fix in Sample Scheduler 2.6 Update 5 to configure the error message to be suppressed but duplicate project configurations can still cause problems in Sample Scheduler. 

Keyword: Configuration

One-line Description:

Sample Scheduler 2.5 Update 6 and 7 cannot be installed on upgraded system

Problem:

Sample Scheduler 2.5 Update 6 and 7 where not directly installable where Sample Scheduler 2.5 was installed as an upgrade over a previous installation. 

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.5 Update 8

Keyword: Configuration

One-line Description:

Update installer switched used database from SQL to OLDR

Problem:

With Sample Scheduler 2.6 Update 1 to Update 3 database is switched from SQL to OLDR. Credentials to access the database are not available in the registry. So services could not start.

Temporary Solution:

n/a

Fix Information:

Fixed in Update 4 for Sample Scheduler for OpenLab revision 2.6 

Keyword: Configuration

One-line Description:

Login to 2.6 web interface not possible after installation on system where 2.7 was installed

Problem:

After installation of Sample Scheduler 2.6 on system where Sample Scheduler 2.7 was installed, the login to the Sample Scheduler 2.6 web interface might be not possible. 

Temporary Solution:

After an additional reboot of the OLSS server the login to the Web interface for activation should be possible.

Fix Information:

n/a

Keyword: Configuration

One-line Description:

Sample Scheduler 2.6 update 4 installation fails on AIC and Client

Problem:

Due to a defect in the installer fails the Sample Scheduler 2.6 update 4 installation on AIC and Client.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.6 Update 5

Keyword: Configuration

One-line Description:

Error message for duplicate projects and instruments when starting desktop applications

Problem:

Showing the information that duplicate projects and instruments are in the system on start can now be turned off in the Sample Scheduler Configuration.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.6 Update 5

Keyword: Configuration

One-line Description:

Client and Configuration do not open with error message: Error reading JToken from JsonReader...

Problem:

Sample Scheduler Client and Configuration do not open with error message: Error reading JToken from JsonReader... This is caused by a crash in the Rest API of OLSS when domain users are listed under users in CP which are already 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:

Fixed in CDS 2.7 Update 6

Keyword: Configuration

One-line Description:

Balance bridge crashes if no task younger than 3 days is available in LabX

Problem:

Balance bridge version 1.0.0 crashes or creates Windows Application Event error logs if no new task is available for 3 days in LabX. 
The crash or error gets reported in the Windows event logs.

Temporary Solution:

The workaround is to start or restart the balance bridge service after a task not older than 3 days is available in LabX.

Fix Information:

A fix is planned for the next version of the balance bridge

Keyword: Configuration

One-line Description:

With a non-CDS project as first one instrument not forced to use a dedicated project Sample Scheduler Acquisition Agents do not start

Problem:

Sample Scheduler Acquisition Agent fails to query Acquisition for CDS parameters when the first project is a non-CDS project (e.g. a general one created on the ECM-XT CP) and the instrument is not forced to use a dedicated project (Always use default project). Sample Scheduler Acquisition Agents do not start in such case, they stay not responding and restart periodically.

Temporary Solution:

The non-CDS Project must not be the first one.

Fix Information:

Fixed in Sample Scheduler 2.8 and Sample Scheduler 2.7 Update 1.

Keyword: Configuration

One-line Description:

Duplicated instrument names lead to other instruments not appearing.

Problem:

Duplicated instrument names get ignored in Sample Scheduler, but this can lead to other instruments not appearing in the Instrument Management tab of the Sample Scheduler Configuration.

Temporary Solution:

Avoid duplicated instrument names.

Fix Information:

Fixed in Sample Scheduler 2.7 Update 1

Keyword: Configuration

One-line Description:

Enterprise: LIMS agent crashed because one of the orchestrator is not started

Problem:

In an Enterprise (scalable) system with 3 or more shared services servers, the LIMS agent crashes if one of the orchestrator services is not started.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 Update 1

Keyword: Configuration

One-line Description:

Error message during uninstallation that database is not reachable

Problem:

When Sample Scheduler gets uninstalled (interactive or silent), the uninstallation gets Stuck with Error Message "Could not connect to Database: Make sure the configured Database connection is working."

Temporary Solution:

If the user clicks on the error message OK box, the system continues with the uninstall and should finish successfully.

Fix Information:

Fixed in Sample Scheduler 2.9.

Keyword: Configuration

One-line Description:

When .Net 3 and .Net 5 get removed according to ServiceNote_D0109719 Sample Scheduler stops working

Problem:

When .Net 3 and .Net 5 get removed according to ServiceNote_D0109719 from a CDS 2.7 system, Sample Scheduler Agents do not start, and the Orchestrator provides errors.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.7 Update 2

Keyword: Configuration

One-line Description:

DB user not changed to 'OpenLabSchedulerDB270User' with CDS 2.8 Upgrade

Problem:

After upgrading older CDS to 2.8, when Sample Scheduler is installed on MS-SQL the DB user is not changed to 'OpenLabSchedulerDB270User'

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.9

Keyword: Configuration

One-line Description:

Webserver does not start after adding a second or third node on an enterprise system

Problem:

Every installation of Sample Scheduler with an OpenLab Server enterprise node resets the Sample Scheduler database user password to a random value. The value of the previously installed Sample Scheduler instances is not correct anymore, therefor the respective webserver does not start up

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 Update 1

Keyword: Configuration

One-line Description:

Database Migration Tool throws an exception, cannot find Agilent.OpenLab.Configuration.xml

Problem:

The installation manual states to run the DB Migration Tool according to the installation manual where your target Sample Scheduler
database is installed - this is nonsense when the database is on an external server. The correct statement is: "Follow this procedure on the OpenLab Server."

Temporary Solution:

Run the DB Migration Tool on the OpenLab Server.

Fix Information:

Fixed in Sample Scheduler 2.8.

Keyword: Configuration

One-line Description:

Database Migration Tool cannot connect to MS-SQL DB with Windows Authentication.

Problem:

The Database Migration Tool cannot connect to MS-SQL DB with Windows Authentication. Only internal users are possible.

Temporary Solution:

For the DB Migration after Sample Scheduler Upgrade configure an internal SQL user. This can be reverted after the Sample Scheduler database migration. 

Fix Information:

Fixed in Sample Scheduler 2.9

Keyword: Configuration

One-line Description:

After ECM XT or OpenLab Server upgrade services will logon with Local System and may not start or work as before

Problem:

When Sample Scheduler services are configured to logon with a domain account, after ECM XT or OpenLab Server upgrade, these services will logon with Local System and may not start or work correctly. 
To logon services as domain user is necessary with Windows authentication DB or for file operations over the network. 

Temporary Solution:

If a Sample Scheduler service is configured to run under a specific user (not the local system account) the services logons as this user must be re-established after the upgrade.

Fix Information:

This is documented in the Readme of Sample Scheduler 2.9.

Keyword: Configuration

One-line Description:

Sample Scheduler Configuration does not open "Error reading JToken from JsonReader."

Problem:

After a windows user which was Sample Scheduler user was deleted from domain the Sample Scheduler Configuration does not open with error message: "An unexpected error occured, the application will terminate. Error reading JToken from JsonReader. Path ", line 0, position 0.".

Temporary Solution:

Delete the user which was deleted from Domain in the Control Panel

Fix Information:

Fixed with OpenLabServer2.7_Update06 and OpenLab_CDS_2.7_Update_06

Keyword: Configuration

One-line Description:

Services cannot checkout license on scalable system

Problem:

No acquisition agent can check out a license nor the startup license. LIMS agents works and could checkout license.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 Update 1

Keyword: Configuration

One-line Description:

Webserver service is not stopping / restarting after changing the password of OpenLabSchedulerDB270User.

Problem:

In a scalable system Webserver service is not stopping / restarting after changing the password of OpenLabSchedulerDB270User. After saving the updated password on all the server machines, launch the Sample Scheduler Web UI for activation. Getting error ‘Could not access Sample Scheduler’.
From Services, the restart of the ‘Agilent Sample Scheduler Webserver’ service fails.

Temporary Solution:

After restarting all Server machines or terminating webserver service from Task Manager only webserver service will stop / restart normally and then after starting web service able to launch Sample Scheduler Web UI and activate.

Fix Information:

Fixed in Sample Scheduler 2.8 Update 1

Keyword: Configuration

One-line Description:

LIMS agent stops working if less LIMS licenses are available then XML connections

Problem:

The Sample Scheduler LIMS agent stops working if less LIMS licenses are available then XML connections. 

Temporary Solution:

Remove or disable the configured LIMS connections until the number matches with the number of licenses 

Fix Information:

Fixed in Sample Scheduler 2.9

Keyword: Configuration

One-line Description:

referenced NuGet (NPGSQL) package has vulnerabilities

Problem:

Visual studio shows nuget package 'Npgsql' 4.1.10 has a known high severity vulnerability.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 Update 2

Keyword: Configuration

One-line Description:

ag-grid package 30.1.0 has a vulnerability

Problem:

The ag-grid package 30.1.0 had a vulnerability and got replaced by a still supported but not vulnerable package

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 Update 2

Keyword: Configuration

One-line Description:

With multiple XML Lims Connections configured, and not enough licenses for all connections, no XML connection works

Problem:

In a system with multiple XML Lims Connections configured, and not enough licenses for all connections, no XML connection works and transfers XML commands into analyses. 

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.9, and Sample Scheduler 2.8 Update 2

Keyword: Configuration

One-line Description:

With duplicate usernames from different domains Sample Scheduler cannot work

Problem:

With duplicate usernames from different domains Sample Scheduler cannot work, like having the same username in ECM 3 Built-In domain and in the Windows domain. The symptoms of this problem are:
Error in Webserver log: An item with the same key has already been added.
Scheduler Agent services cannot be started.

Temporary Solution:

Depending on the configuration, there might be a possible point patch available on request. 

Fix Information:

n/a

Keyword: Configuration

One-line Description:

Installation of Sample Scheduler 2.8 Update 1 or Update 2 may roll back

Problem:

The installation of Sample Scheduler 2.8 Update 1 or Update 2 may roll back on late Windows versions. The Update will not get installed. This was seen e.g. on Windows Server 2022 and Windows 11 23H2. 

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 Update 3

Keyword: Configuration

One-line Description:

If LabX exceeds variable limit it leads to repeating errors in the webserverservice.log

Problem:

If LabX exceeds Sample Scheduler variable limit it leads to repeating errors in the webserverservice.log. The information to transfer hangs then in a processing loop and leads to application lagging issue with the OpenLab Control Panel, AQ, DA, and Sample Scheduler client, configuration. 

Temporary Solution:

Insert the IDs of the tasks causing the errors in 'processed.dat’ of Balance Bridge.

Fix Information:

A fix is planned for the next version of Balance Bridge for LabX.

Keyword: Configuration

One-line Description:

Balance Data Bridge throws exception with only CR LF in tasks.dat

Problem:

Balance Bridge throws exception with only CR LF in tasks.dat, and does not write logs any more into the folder C:\ProgramData\SampleSchedulerLabXBridge

Temporary Solution:

Edit the tasks.dat, make CR LF characters visible, they should only appear at the end of an entry, not at the beginning of a line.

Fix Information:

Fixed in Balance Data Bridge for LabX Update 1, available in SubscribeNet under the Sample Scheduler 2.8 for OpenLab node.

Keyword: Configuration

One-line Description:

Sample Scheduler 2.7 update 2 installation may fail on actual Windows

Problem:

Sample Scheduler 2.7 update 2 installation may fail on the latest windows versions.

Temporary Solution:

A workaround could be identified: If the update installation is done once and failed, a file named: dbinfo.txt is created in the appdata\local\Temp folder. This file needs to be copied to the following path: "C:\Windows\SystemTemp\DBInfo.txt"
In addition to that the temp and tmp folder path in the environment variables need to be synchronized between the user variables and the system variables so they all use the same path. 

Fix Information:

The plan is to fix it in the next update for Sample Scheduler 2.7.

Keyword: Configuration

One-line Description:

After DB migration another Default LIMS connection is present and cannot be deleted

Problem:

After DB migration another Default LIMS connection is present when no source system connection has the name Default, and it cannot be deleted.

Temporary Solution:

Workaround is to use the new LIMS connection, add all parameters of another LIMS connection, delete that connection, rename the new Default connection.

Fix Information:

Fixed in Sample Scheduler 2.9

Keyword: Configuration

One-line Description:

The Sample Scheduler Server topology is not functional

Problem:

In the Sample Scheduler installation manual, a Sample Scheduler Server is described as CDS Client installation on a server OS, were LIMS Agent and Web Interface get installed. Such Installation cannot be installed or is not functional. 
The Web Interface with the Orchestrator service has to be located on the OpenLab Server/ECM-XT. 

Temporary Solution:

The LIMS Agent can be deployed on the Scheduler Server, when it gets manually activated, but not the Web Interface.

Fix Information:

Fixed in Sample Scheduler 2.9

Keyword: Localization

One-line Description:

The instrument error messages from the CDS to the Scheduler UI are not localized

Problem:

The instrument error messages from the CDS to the Scheduler UI are not getting localized. In case of a acquisition error the part of the error message regarding the instrument error will be in English only.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler revision 2.1

Keyword: Performance

One-line Description:

Internet Explorer reacts slow when opening web interface windows

Problem:

when opening web interface windows the Microsoft Internet Explorer reacts slow compared to Google Chrome as web browser. 

Temporary Solution:

Use Google Chrome as web browser.
For using the IE in 64-bit mode please do the following steps:
- Enable Enhanced Protected Mode (Tools > Internet Options > Advanced)
- Enable Protected mode (Tools > Internet Options > Security)
- remove all add-ons which are limited to 32-bit architecture (Tools > Manage add-ons)
- restart browser

Fix Information:

This behavior cannot be fixed in the Sample Scheduler Web Interface. 

Keyword: Performance

One-line Description:

When scrolling fast in about 6000 analyses the Web-Interface sometimes hangs

Problem:

When scrolling in the Sample Scheduler Web Interface fast in a huge amount of analysis like about 6000 or more the UI sometimes hangs and sometimes the table stays empty

Temporary Solution:

It can help in this situation to click the up- and down-buttons of the scrollbar

Fix Information:

Fixed in Sample Scheduler 2.5

Keyword: Performance

One-line Description:

Sample Scheduler generates high load on SQL Server

Problem:

Sample Scheduler generates high load on SQL Server (through own calls to Database, high frequent calls to OLSS database).

Temporary Solution:

n/a

Fix Information:

Port improvements done in Sample Scheduler 2.6 Update 1.

Keyword: Performance

One-line Description:

Change Tracking in SQL Server database is set to 2 days

Problem:

The Change Tracking in the Sample Scheduler Microsoft SQL Server database is set to 2 days by SQL default. 
This can have an adverse impact on the performance of the system.
Change Tracking should be set to 2 minutes.

Temporary Solution:

Set Change Tracking in SQL Server for the sample scheduler database to 2 minutes. How to perform this change is documented in Service Note D0012486, available on the Field Portal.

Fix Information:

This problem will be fixed in Sample Scheduler 2.8

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:

Large Sequences coming from LIMS over SQL have Transfer Delay

Problem:

When large Sequences coming from LIMS over SQL, they have some Transfer Delay. Analyzing the behavior shows that the most time is spent on repetitive retrieving project Information in different parts of the validation process.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 and in Sample Scheduler 2.5 Update 10. 

Keyword: User Interface

One-line Description:

Ended sequences can disappear from the review table

Problem:

An ended sequences can disappear from the review table when a new sequence gets created in the Analysis table

Temporary Solution:

Reopen the Scheduler Client - no data is lost

Fix Information:

This problem is fixed in Sample Scheduler revision 2.1

Keyword: User Interface

One-line Description:

The Sample Scheduler Client has a minimum vertical graphic resolution of 800

Problem:

If the graphic resolution is below 800, the Sample Scheduler Client Interface is not fully visible.

Temporary Solution:

n/a

Fix Information:

A minimum vertical graphic resolution of 800 is recommended for the Sample scheduler Client interface as stated in the installation guide from revision 2.2 and in the Site Preparation Checklist

Keyword: User Interface

One-line Description:

Cannot change vial number in the Web Interface, Analysis view

Problem:

In the Web Interface Analysis view the vial number of an analysis seems to be editable but will not change permanently.

Temporary Solution:

The vial number can be edited in the Sample Scheduler client

Fix Information:

Fixed in Sample Scheduler revision 2.2 and in Update 1 for Sample Scheduler revision 2.1

Keyword: User Interface

One-line Description:

Stop instrument button doesn't work for sequences

Problem:

The "stop instrument" button in the Sample Scheduler client doesn't work for sequences in progress on a CDS 2.3 system.

Temporary Solution:

Workaround: In case of sequences first use the stop button for the sequence and then the Stop Instrument button

Fix Information:

This defect is fixed in Sample Scheduler revision 2.2 and in Sample Scheduler revision 2.1 with Update 1

Keyword: User Interface

One-line Description:

Sample Customer Parameters with type text get displayed as numbers if they contain a number

Problem:

When a Sample Customer Parameters with type text contains a number, 
it gets displayed as a number

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler for OpenLab revision 2.2 and in Update 1 for 2.1 which is the revision 2.1.1

Keyword: User Interface

One-line Description:

When the session is locked the username field of the unlock dialog is case sensitive

Problem:

When the session is locked the username field of the unlock dialog is case sensitive. In the login dialog this field is not case sensitive.

Temporary Solution:

Enter the username in case sensitive way

Fix Information:

This is fixed in Sample Scheduler revision 2.2 and in Update 1 for Sample Scheduler revision 2.1

Keyword: User Interface

One-line Description:

Changing fields with "tab" get stuck at "sample custom parameters"

Problem:

When editing an analysis and switch the parameter via "tab" button, the switching gets stuck at the sample custom parameter and it is not possible to change to any other field via "tab" anymore. 

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler for OpenLab revision 2.2 and in Update 1 for revision 2.1.

Keyword: User Interface

One-line Description:

Edit analysis - right cursor can select field on the left

Problem:

When editing an analysis and switch the parameter via cursor keys, the switching between the fields is confusing. If I press the right cursor button the sample custom parameter on the left side will be selected.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler for OpenLab revision 2.2

Keyword: User Interface

One-line Description:

Sample Scheduler client sometimes crashes when used with Sample Custom Parameters

Problem:

When using Sample Scheduler Client and having analysis lines with Sample Custom Parameters with filled values in the table, the Client sometimes hangs and then crashes

Temporary Solution:

n/a

Fix Information:

A fix is realized in OpenLab Sample Scheduler 2.3 

Keyword: User Interface

One-line Description:

In the Web Interface the Sequence line does not stay in focus

Problem:

When scrolling to a certain sequence line in the Web Interface viewing a Sequence in the Analysis view, the automatic refresh scrolls the view to the header of the sequence.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: User Interface

One-line Description:

The Sequence Column Chooser in the Web shows problems with Internet Explorer

Problem:

When using the Web Interface with Internet Explorer the Sequence Column Chooser shows problems with responsiveness, takes only the height of the sequence line table and appears condensed. 

Temporary Solution:

Use another supported web browser like Chrome. 

Fix Information:

It is not planned to fix the problem in Sample Scheduler as other browsers work well. 

Keyword: User Interface

One-line Description:

In Windows Client it is possible to edit other fields than Sign-off and LIMS Connection

Problem:

Editing of fields other then Sign-off and LIMS Connection is possible in the windows client review view. The selected field allows the user to change the value. This edited values other than Sign-off and LIMS Connection will not be reflected in the CDS results. 

Temporary Solution:

n/a

Fix Information:

A fix will be provided in Sample Scheduler 2.6

Keyword: User Interface

One-line Description:

Expanded sequence is not rendered correctly in the web interface

Problem:

In the Sample Scheduler web interface it can happen that a sequence is not rendered correctly after it got expanded

Temporary Solution:

After you collapse and expand the sequence, it should be rendered correctly

Fix Information:

n/a

Keyword: User Interface

One-line Description:

Services of configured sample scheduler does not start after upgrading CDS 

Problem:

After the upgrade of CDS is completed (step 4 of Server installer) usually no reboot is needed. The sample scheduler service are stopped because of their dependencies and the start service of the CDS installer does not start the sample scheduler services.

Temporary Solution:

After reboot of the server or manual services start Sample Scheduler should work 

Fix Information:

A fix will be provided in Sample Scheduler 2.6 with removing some dependencies of the Sample Scheduler service controller, Sample Scheduler Database Management agent and Sample Scheduler webserver

Keyword: User Interface

One-line Description:

Web Interface scrollbars may miss on Mac OS with Safari or Chrome

Problem:

The Web Interface should have scrollbars in some views like the Instruments or Analyses screen if not all content fits on the screen. On Mac OS with Safari or Chrome those scrollbars may miss. 

Temporary Solution:

n/a

Fix Information:

The problem cannot be fixed in Sample Scheduler.

Keyword: User Interface

One-line Description:

My Instrument view is empty if locked

Problem:

With locked screen the My Instruments view is empty

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.7

Keyword: User Interface

One-line Description:

Progress bar in the Web Interface may not vanish

Problem:

Sometimes the progress bar in the Web Interface does not vanish

Temporary Solution:

Press Ctrl-F5 or restart the browser

Fix Information:

Fixed in Sample Scheduler 2.7

Keyword: User Interface

One-line Description:

My Instruments view case sensitive with regard to user name

Problem:

The CDS and Sample Scheduler login screen is not case sensitive for the user name. But the My Instruments view of the Sample Scheduler Web Interface is case sensitive with regard to the user name. This leads to an empty My Instruments view in the Sample Scheduler Web Interface, when logged in with a user name that differs to the one in Control Panel in lower/upper case writing.

Temporary Solution:

Use the same upper / lower case writing for the user name at login as used in the Control Panel

Fix Information:

A fix is planned in Sample Scheduler 2.7

Keyword: User Interface

One-line Description:

In Sample Scheduler the error message can be displayed for the previous analysis

Problem:

Under circumstances the error message displayed in Sample Scheduler for a sequence line can be shown as the error message of the previous analysis, and not of the analysis where the error occurred

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.5 Update 8 and Sample Scheduler 2.7. A separate fix in the CDS Acquisition is needed in addition, which is planned for CDS 2.5 Update 10. Point Patch 1 for CDS 2.5 Update 9 includes only this separate fix. 

Keyword: User Interface

One-line Description:

In Sample Scheduler- 2.6 Update 5, the user might see duplicate projects.

Problem:

Duplicate projects cannot be used In Sample Scheduler. With version 2.6 Update 5, duplicate projects can show up with new analyses. 
When revisiting the drop-down menu, only not duplicate projects are listed. 

Temporary Solution:

Use the drop-down menu a second time or prevent Sample Scheduler from recognizing duplicate projects. 

Fix Information:

In Sample Scheduler 2.8 the feature to work with duplicate projects is implemented. In other versions before Sample Scheduler 2.6 Update 5 this is not seen as a problem. 

Keyword: User Interface

One-line Description:

After upgrade new Web features may not be shown, caused by browser cache

Problem:

After an upgrade of Sample Scheduler, it may give the impression that features are missing. 
The reason might be cashed browser objects used, from the version before. 

Temporary Solution:

Clear all browsing data of your browser!
That helps to see the new features!

Fix Information:

A fix is planned for a later version.

Keyword: User Interface

One-line Description:

With a non-CDS project as default project, a new analysis in the Web gives empty error

Problem:

With a project which is not a CDS project as default project in the Sample Scheduler Configuration, a new analysis in the Web Interface gives an empty error. 

Temporary Solution:

The non-CDS Project must not be the first one.

Fix Information:

Fixed in Sample Scheduler 2.9.

Keyword: User Interface

One-line Description:

Chrome on Android tablet may not have the ability to view pdfs inside the browser

Problem:

Chrome on Android tablet may not have the ability to view pdfs inside the browser on older Android versions. This affects the Sample Scheduler web interface which then cannot show the PDF report of analyses in the browser. 

Temporary Solution:

Try to download the PDF, maybe it can be viewed then, depending on installed apps and settings. 

Fix Information:

A fix might be found in an actual or later versions of Android and Chrome. 

Keyword: User Interface

One-line Description:

When an instrument is waiting for manual injection, the runtime gets started

Problem:

With Sample Scheduler 2.8 the runtime gets started when the instrument is waiting for manual injection. In older versions the instrument did start when the manual injection was triggered. 

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.9

Keyword: User Interface

One-line Description:

In column chooser Show/hide columns is not possible with the tapping

Problem:

In the Web Interface in the column chooser, Show/hide columns is not possible with the tapping on touch devices.

Temporary Solution:

With mouse click it works

Fix Information:

Fixed in Sample Scheduler 2.9.

Keyword: User Interface

One-line Description:

Info icons are not aligned with highlighted cell lines

Problem:

In Sample Scheduler Sequence view, if the sequence row has invalid cell and the sorting is applied, the info icons do not align with the invalid cell rows.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.9

Keyword: User Interface

One-line Description:

With Safari 17 or below on iOS/MacOS at sequence creation no analysis lines get displayed

Problem:

With Safari 17 or below on iOS/MacOS at sequence creation in the web interface no analysis lines get displayed in the upcoming dialog

Temporary Solution:

n/a

Fix Information:

Update the Safari browser to 18 or higher

Keyword: Workflow

One-line Description:

Autofill doesn't work for DataFile, ResultPath

Problem:

If a autofill template specifies a DataFile or ResultPath, matching commands are not supplemented by the values in the template

Temporary Solution:

n/a

Fix Information:

The problem is solved in Sample Scheduler revision 2.1

Keyword: Workflow

One-line Description:

Error message when CDS runs submitted through scheduler and audit trail is enabled

Problem:

When CDS 2.x analysis get scheduled in projects with the result set audit trail setting "prompt for reason when saving", the analysis can not be started and a error message appears.

Temporary Solution:

Do not configure CDS projects used with Sample Scheduler with the result set audit trail setting: "prompt for reason when saving" 

Fix Information:

n/a

Keyword: Workflow

One-line Description:

Analysis from LIMS for in Scheduler not configured instruments getting into Analysis Table

Problem:

If instruments are configured in the OpenLab Control Panel but no Sample Scheduler Agent Computer Name is configured in the Sample Scheduler Configuration, analysis coming from the LIMS over XML commands or SQL queries get posted in the Sample Scheduler Analysis Table. Those Analysis can get scheduled if they are in "Waiting" state and they can get copied. If they are in the "Scheduled" state they will stay in this state until a Sample Scheduler Agent gets assigned to this instrument or until intervention like deletion. 

Temporary Solution:

n/a

Fix Information:

A fix or design change is planned for a later release

Keyword: Workflow

One-line Description:

Merging analysis with <ID> token in sample name, causes new sample name to be cryptically

Problem:

When 2 analysis which have in their sample name an <ID> token get merged to a dual analysis, the new sample name becomes cryptically

Temporary Solution:

n/a

Fix Information:

This problem is fixed in Sample Scheduler revision 2.2

Keyword: Workflow

One-line Description:

Sample Custom Parameter not added to sequence lines if adding sequence lines in sequence subwindow

Problem:

When adding an analysis to a sequence in the Sample Scheduler Sequence Submenu, existing Sample Custom Parameters would not contain the default values from the project.

Temporary Solution:

When copying the sequence line an existing default value will get populated. 

Fix Information:

This defect is fixed in Sample Scheduler revision 2.2.

Keyword: Workflow

One-line Description:

The second signal of a dual analysis is not displayed in the review tab

Problem:

The second signal of a dual analysis is not displayed in the review tab

Temporary Solution:

The second signal can be opened and reviewed in Data Analysis

Fix Information:

The problem is fixed in Sample Scheduler revision 2.2

Keyword: Workflow

One-line Description:

In the manual of 2.3 the SampleCustomParameter for SQL is not correct explained

Problem:

In the Sample_Scheduler_for_OpenLab_Installation_Configuration_Guide_en.pdf the
 SampleCustomParameter for SQL is not correct explained. Instead of one variable, with CDS 2.4 and Sample Scheduler 2.3 two variables have to be filled to get it working:
SampleCustomParameterNName [N=1..20]
SampleCustomParameterNValue [N=1..20]

Temporary Solution:

Use the correct syntax for the SQL query according to this SSB entry with both variables with the type Varchar (null accepted): 
SampleCustomParameterNName [N=1..20]
SampleCustomParameterNValue [N=1..20]

Fix Information:

A fix will be provided in Sample Scheduler revision 2.4 Installation and Configuration manual

Keyword: Workflow

One-line Description:

Manually created analysis can be signed of for LIMS is wrong documented in revision 2.4.

Problem:

In the OpenLab Help and Learning section of Sample Scheduler revision 2.4  is wrong documented in the section "Use Sign-off for LIMS". The sentences: "Sign-off can only be used for analyses created by the LIMS. The Sign-off parameters are disabled for analyses you have created manually." are wrong for revision 2.4 but was valid for revision 2.3 and 2.2. 
Manually created analysis can be signed of for LIMS in Sample Scheduler revision 2.4. 

Temporary Solution:

n/a

Fix Information:

Fixed in the documentation of Sample Scheduler revision 2.5.

Keyword: Workflow

One-line Description:

Sequence position is ignored when importing sequence via SQL

Problem:

When importing a sequence via SQL, the sequence position is ignored, the lines are not order by it. The sequence is ordered by the order that of the lines returned by the query, not the sequence position.

Temporary Solution:

As workaround enhance the LIMS query with "Order By SequenceId, SequencePosition" to get the sequence positions in the Scheduler matching the provided sequence positions from LIMS.

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Workflow

One-line Description:

With UNC path saved as Result path in the Sample Scheduler Client the application may crash

Problem:

On a OpenLab EZChrom installation with filesystem the Sample Scheduler Client may crash when an UNC path is saved as Result path.

Temporary Solution:

Do not save unc path in Result path

Fix Information:

Fixed in Sample Scheduler revision 2.5

Keyword: Workflow

One-line Description:

When a sequence gets created in the Web Interface it cannot be scheduled without editing it

Problem:

When a sequence is newly created in the Web Interface with "Apply Sequence Template" it cannot be scheduled before it is edited. A error message will appear: "Operation cannot be executed. Sequence cannot be modified in this way". Sequence can be started in windows client.

Temporary Solution:

Edit the sequence once in the Web Interface or use the Scheduler client installation

Fix Information:

Fixed in Sample Scheduler 2.5 Update 1 and Sample Scheduler 2.6

Keyword: Workflow

One-line Description:

Project setting changes not reflected in active acquisition session

Problem:

Changes done for a project in the shared services control panel are not active for the acquisition agent session until it is restarted after the project changes.

Temporary Solution:

After project changes in the OpenLab Control Panel the Sample Scheduler Agents have to be restarted so that the changes become effective

Fix Information:

With Sample Scheduler 2.6 this behavior will be documented in the Sample Scheduler Installation and Configuration Guide, Chapter 13: Maintenance Operations> Change Project Settings in the Control Panel

Keyword: Workflow

One-line Description:

Sample Prep method of Sequence template is not applied to sequence during rollout

Problem:

When a Sample preparation method is define in a sequence template, the sample preparation actions will not be applied to the samples during sequence rollout

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.7

Keyword: Workflow

One-line Description:

Domain accounts from LabX and Sample Scheduler are not matched

Problem:

If a domain user from LabX is transferred to Sample Scheduler it will most likely not be matched with the domain accounts from OpenLab when those are used for Sample Scheduler authentication. 

Temporary Solution:

n/a

Fix Information:

Fixed in Balance Data Bridge for LabX version 1.1. 

Keyword: Workflow

One-line Description:

 Sequence from LIMS over SQL cannot be created and stay as single runs because a run is in edition

Problem:

When a sequence of large size through LIMS via SQL gets created, while this happens, sequence lines appearing some time as single analyses in the analyses table of the Client and the Web Interface until the process is complete. If any of those sequence lines before creation of the sequence gets edited, then the sequence cannot be created, and all analyses get displayed as single lines in the analysis table. 

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.8 and Sample Scheduler 2.5 Update 10.

Keyword: Workflow

One-line Description:

Merged duals do not provide dual instrument groups in the Client

Problem:

If 2 single injections get merged to a dual injection in the installed Client Interface, dual instrument groups are not available for the merged dual sample. Only single instrument groups are available. If those one is selected an error message "Invalid Parameters(s)" will show up. The problem gets resolved with restarting the Client Interface. The Web Interface does not show this problem.

Temporary Solution:

Use the Web Interface, or continue the work after the Client is restarted.

Fix Information:

Fixed in Sample Scheduler 2.7 Update 1 and Sample Scheduler 2.8.

Keyword: Workflow

One-line Description:

Validation error when sequence template contains tokens

Problem:

There is a Validation error which prevents saving when a sequence is generated from a sequence template which contains tokens.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.9, and Sample Scheduler 2.8 Update 2

Keyword: Workflow

One-line Description:

Sequences created by the v3 API do not default the result field

Problem:

Sequences created by the v3 API do not default the result field. This causes incomplete sequences. SLIMS uses the v3 REST API now, it used to work well in v2.

Temporary Solution:

n/a

Fix Information:

Fixed in Sample Scheduler 2.9, and Sample Scheduler 2.8 Update 2

Keyword: Workflow

One-line Description:

Not Available instrument state causes Balance Bridge data transfer to fail

Problem:

When the Balance Bridge for LabX rev. 1.1 reads the Not Available instrument state of Sample Scheduler 2.8, it causes the Balance Bridge data transfer to fail. 

Temporary Solution:

n/a

Fix Information:

A fix is planned for the next version of Balance Bridge for LabX.