Software Status Bulletin

Chemlaunch     Chemlaunch

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: CL Issue

KPR#:9 Agilent LC Diagnostic is working different in Citrix Environment

Keyword: CL-Citrix Client

KPR#:5 Open new method function leads to invalid directory
KPR#:10 Not reachable instrument marked as connected (blue Light)
KPR#:11 “Window Content” flickering when moving the logbook

Keyword: CL-Communication

KPR#:8 IO Library Suite 15.0 cannot be installed on Windows 2003 Server

Keyword: CL-UI

KPR#:7 ChemStation running in ChemLaunch does not fit into the Monitor Screen Window

Keyword: CS Issue

KPR#:17 ChemStation.ini file could not be located in a Terminal Server Environment

Keyword: Citrix

KPR#:4 Open new sequence table leads to invalid directory

Keyword: 

One-line Description:

Different handling for Online and offline Queue Management in ChemLaunch/ChemStation environment

Problem:

In case of an ECM System failure, ChemStation queues all data on the Hard disk in a secure environment and an automatic upload of this data is triggered as soon as the ECM Server is available again. Within a plain ChemStation environment, a queue is present per instrument and the instruments queue can be accessed and managed via the online or offline ChemStation session. 
In a ChemLaunch environment, it is not possible to manage an online data queue in the offline system and vice versa.

Temporary Solution:

The ChemLaunch/ChemStation set up is slightly different to a plain ChemStation/OpenLAB option installation. Due to these differences, the permitted user/ administrator needs to logon:
- to the online session to manage the queue of the online session ,
- to the offline session to manage the queue of the offline session

Fix Information:

n/a

Keyword: 

One-line Description:

An Admin shadowing the instrument can access all ChemStation settings without trace

Problem:

If the Admin shadows the instrument, he is able to execute methods and sequences. These actions will not be traced in any chemstation ogbook, because the current logged on user is still user X in the ChemStation, ECM and ChemLaunch.

Temporary Solution:

This is the nature of how Shadowing works. The ChemLaunch log shows that when an Admin user is shadowing a specific instrument. 

In validated environment, the Shadow instrument function should be turned off in ChemLaunch for customers with conflict policies. Uncheck the Shadow Instrument checkbox from ChemLaunch Configuration Editor in the Global Options.

Fix Information:

n/a

Keyword: 

One-line Description:

Tracking not correct documented in case of taking over an instrument

Problem:

In a ChemLaunch environment the following Admin Task is present: Instrument Take over. In case of taking over an instrument, note that the following tracking mechanisms are not reflecting the current "take over": 
- User X is not notified that instrument A is taken over; the instrument A simply vanish from the   ChemLaunch tab.
 - Admin 1 can execute and edit the current instrument session, upload data etc. , using the logon of User X
-  In the ChemLaunch tab, the admin is traced to took over the instrument, but not in the instrument usage report

Temporary Solution:

This is the nature of how Takeover function works. The ChemLaunch log shows that when an Admin user is taking over a specific instrument. In validated environment, the Takeover function can be disabled from the ChemLaunch Configuration Editor.

Fix Information:

n/a

Keyword: 

One-line Description:

Autostart macro fail for LCMS offline system

Problem:

Starting the LCMS offline ChemStation, the system might come up with an error message box: “autostart macro fail”.

Temporary Solution:

Press “Yes” on the error message to continue the start up of the offline ChemStation. The error message has no further influence on the running offline instrument.

Fix Information:

Fixed with ChemLaunch Rev C.01.06 SP1

Keyword: 

One-line Description:

Background window is redrawn while dragging

Problem:

In ChemStation/ChemLaunch the background window is redrawn while dragging, even if in the Windows settings the "show content while dragging" is disabled. For pure ChemStation, the disabling of the Microsoft function “show window content while dragging” function solves the issue. In a ChemLaunch environment the problem remains

Temporary Solution:

n/a

Fix Information:

This issue is addressed using ChemLaunch with Citrix XenApp version 5.0.
Make sure that “show content while dragging” is not enabled for the ChemLaunch domain accounts  (e.g. CLAdmin and CLUser)

Keyword: 

One-line Description:

Shadow Instrument possible with alerting the user to be monitored

Problem:

If an Admin shadows an instrument, the user will not be alerted, that the Admin is shadowing his instrument.

Temporary Solution:

This is the nature of how Shadowing works. The ChemLaunch log shows that when an Admin user is shadowing a specific instrument. 
In validated environment, the Shadow instrument function should be turned off in ChemLaunch for customers with conflict policies. Uncheck the Shadow Instrument checkbox from ChemLaunch Configuration Editor in the Global Options

Fix Information:

n/a

Keyword: 

One-line Description:

ChemStation.ini file could not be located in a Terminal Server Environment

Problem:

ChemStation rev. B.04.02 SP1 cannot be operated in a Terminal Server environment because the path information to the chemstation.ini file is not adjusted to the terminal server specific settings.

Temporary Solution:

N/A

Fix Information:

A terminal_server_user_path_patch is available for ChemStation revisions B.04.02 SP1, DSP3, and Hotfix 2.

Keyword: 

One-line Description:

Occasionally ChemStation does not launch in ChemLaunch environment

Problem:

With ChemStation B.04.02 SP1 it may happen that ChemLaunch administrators may not be able to start a ChemStation instance while ChemLaunch users can do so.
During the startup the instance terminates and leaves a  .NET Runtime 2.0 error in the Event viewer logbook.

Temporary Solution:

N/A

Fix Information:

The defect is fixed in ChemStation B.04.03 and the Terminal Server Mutex Handling Patch for ChemStation B.04.02 SP1.

Keyword: 

One-line Description:

Unexpected ChemStation PDF printer shutdown

Problem:

When one of the ChemStation instances running in a ChemLaunch environment is closed, also the ChemStation PDF printer will be terminated for all ChemStation instances. PDF reports are no longer created for the instances that are still running.

Temporary Solution:

n/a

Fix Information:

This defect is fixed in the Terminal Server Patch collection 2

Keyword: Citrix

One-line Description:

Open new sequence table leads to invalid directory

Problem:

Creating a new sequence using the Method and Run Control View Menu Sequence/New Sequence, a message appears “:invalid or non existent directory for system variable seqpath$”

Temporary Solution:

Use the ChemStation Explorer to load the default sequence template directly from the Sequence folder.

Fix Information:

Fixed with ChemStation rev B.04.01 SP1

Keyword: CL Issue

One-line Description:

Agilent LC Diagnostic is working different in Citrix Environment

Problem:

The Agilent LC Diagnostics tool will work different in a ChemLaunch environment:
Executing the application directly from the Server and communicate with the instrument, the session is working and the resulting data are written to the default path in Program files, Agilent, LC diagnostic -- to the various directories documented in the LC Diagnostic tool. Executing the application from out a ChemStation session in ChemLaunch environment, the ChemStation will close and the LC Diagnostic tool will start, but the start up is interrupted and the tool vanishes without notification.

Temporary Solution:

Starting with ChemStation B.04.01 and ChemLaunch C.01.06, it is not possible to execute the LC Diagnostic Tool from a ChemStation within a ChemLaunch environment. The LC Diagnostic tool needs to be executed separately. The LC Diagnostic tool has been added to the ChemLaunch Admin view. The resulting LC Diagnostic files, e.g. like a solvent calibration file (*.svl) for a binary pump system, need to be manually copied to the correct location in ChemStation: In a ChemLaunch environment, this is ChemServ/ device/localinst/localinst/ .

Fix Information:

n/a

Keyword: CL-Citrix Client

One-line Description:

Open new method function leads to invalid directory

Problem:

Creating a new sequence using the Method and Run Control View Menu Method/New Method, a message appears “:invalid or non existent directory for system variable methpath$”

Temporary Solution:

Use the ChemStation Explorer to load the default method directly from the method folder.

Fix Information:

Fixed with the Chemstation rev B.04.01 SP1

Keyword: CL-Citrix Client

One-line Description:

Not reachable instrument marked as connected (blue Light)

Problem:

If an Instrument is used by an other controller than ChemLaunch/ChemStation, the symbol for the instrument in question shows a “connected” state in the ChemLaunch environment, mentioning the User ID of the current logged session user. Starting the ChemStation all modules for that instrument are not accessible (grey) because already connected by another controller

Temporary Solution:

ChemLaunch has no way to determine which other application might access the same instrument. It is user's responsibility to ensure that the instruments in ChemLaunch are not being allocated to other application

Fix Information:

n/a

Keyword: CL-Citrix Client

One-line Description:

“Window Content” flickering when moving the logbook

Problem:

Moving an e.g. instrument logbook, or sequence logbook, the content of the window holding the information is flickering – this flickering can affect the data review.

Temporary Solution:

This issue is addressed with using ChemLaunch with Citrix XenApp version 5.0.

Please note, that for ChemLaunch/ChemStation B.04.01/OpenLAB Option Adv. Presentation Server 4.5 is supported. (Feb. 2009) In a plain ChemLaunch/ChemStation B.04.01 Citrix XenApp verion 5.0 is supported.

Fix Information:

Make sure that “show content while dragging” is not enabled for the ChemLaunch domain accounts  (e.g. CLAdmin and CLUser)

Keyword: CL-Communication

One-line Description:

IO Library Suite 15.0 cannot be installed on Windows 2003 Server

Problem:

Currently LC/MS ChemStation uses the IO Library Suite 15.0 to set up the communication for SICL/LAN. It is not possible to install the IO Lib Suite 15.0 on Windows 2003, the operating system is checked and the installation is denied.

Temporary Solution:

Instead of the IO Library Suite 15.0 use the Agilent Library IO Library. M.01.01. Contact your local Agilent Representative

Fix Information:

n/a

Keyword: CL-UI

One-line Description:

ChemStation running in ChemLaunch does not fit into the Monitor Screen Window

Problem:

Depending on the monitor used for running ChemStation in ChemLaunch Environment, following issue is reported: Running ChemStation B.04.01 in a ChemLaunch Environment, using screen resolution 1280x1024 it might happens that certain parts of the ChemStation graphical interface on the right hand site are cut off. This is due to the ChemLaunch Neighborhood and the ChemStation Explorer

Temporary Solution:

1. The client workstation screen resolution is recommended to have at least one level higher than ChemStation's requirement. For example, if ChemStation's requirement is 1280x1024 then ChemLaunch will require 1440x900 or higher.
2. Widescreen monitor for the client workstation is highly recommended.

Fix Information:

n/a

Keyword: CS Issue

One-line Description:

ChemStation.ini file could not be located in a Terminal Server Environment

Problem:

ChemStation rev. B.04.03, B.04.03 DSP cannot be operated in a Terminal Server environment because the path information to the chemstation.ini file is not adjusted to the terminal server specific settings.

Temporary Solution:

n/a

Fix Information:

Fix Note: A terminal_server_user_path_patch is available for ChemStation 
Revisions B.04.03 [16] and B.04.02 DSP1 [52].