Software Status Bulletin

UV VIS ChemStation     G1813AA

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

KPR#:211 Instrument keys don't work in Standard and Dissolution mode

Keyword: Access

KPR#:34 Instrument keys are active if the ChemStation is locked
KPR#:760 No exit and program termination for unauthorized users in Autostart mode

Keyword: Audit Trail

KPR#:35 Data are not saved, if a Dissolution run is aborted.
KPR#:154 Configured paths may unadvertedly changed to default value

Keyword: Data Acquisition

KPR#:759 Instrument buttons and Shortcut keys do not work for Operators

Keyword: Data Integrity

KPR#:6 Measure keys F4, F5, F6 are not disabled by the Security Pack

Keyword: ELECTRONIC SIGNATURE

KPR#:40 Full name is not used with domain login

Keyword: Graphics/Views

KPR#:748 Deleted spectra view does not show the deleted spectra

Keyword: Installation

KPR#:138 Installation of the Security Pack to an existing system leads to errors.

Keyword: Saving/Uploading

KPR#:42 Saving data fails after Installation of the Security Pack

Keyword: 

One-line Description:

Signatures not tracked in Standard mode

Problem:

When signing a result in Standard mode, the signature is not tracked with the results data file automatically.

Temporary Solution:

In addition to the signature issued, save the result again to file.

Fix Information:

Saving a result will pop up the sign dialog box too.

Keyword: 

One-line Description:

Clear Button deleting data in secure mode inappropriately

Problem:

In the Standard mode tasks the clear menu commands and the clear button on the toolbar are not locked automatically after the first data acquisition on operator level. This allows operators to remove their acquired data entirely from the target record.

Temporary Solution:

None

Fix Information:

fixed in code. works properly now.

Keyword: 

One-line Description:

Clear results does not clear "Deleted Data"

Problem:

Due to the 21 CFR part 11 requirements no raw data must be removed from a data record. This is handled by a special contained called "Deleted Data". Here raw data excluded from the calculation are stored. However, if an entire record (result) is cleared, this container must be emptied as well.

Temporary Solution:

none

Fix Information:

fixed in code.

Keyword: 

One-line Description:

Appending standards must not be offered for users with operator rights

Problem:

When loading a method for quantification in standard mode with the Security Pack installed, the ability to select appending of standard data must not be offered. The change of the calibration set is a change of the method and must not be available as an option. Here always eventually existing standards must be removed.

Temporary Solution:

n/a

Fix Information:

Fixed in code.

Keyword: 

One-line Description:

No Clear Results command available after loading of results data file

Problem:

Users with operator rights can load results for checking and reprinting. However, they are not offered to clear the loaded result.
Only when loading a second result, the Clear Results function is offered. However, in addition Clear Standards and Clear Samples functions are active.

Temporary Solution:

n/a

Fix Information:

Fixed in code.

Keyword: 

One-line Description:

Method setup dialog offered to users with operator rights

Problem:

If a user with operator rights in Standard mode loads a result file which requires a change of the task, he is asked whether or not to change the task. This must not be a choice to a user with operator rights. The task must be switched without any dialog and all existing data removed (clear results) before loading the new result.
In addition the method setup dialog is offered for changes. This must not be available.

Temporary Solution:

n/a

Fix Information:

Fixed.

Keyword: 

One-line Description:

User with operator rights can overwrite results on file

Problem:

If an operator in standard mode loads a result for review and deletes a standard he selected, he is asked to save the manipulated data when he loads the next result file. In this case he is even allowed to overwrite any existing result file.

Temporary Solution:

n/a

Fix Information:

Fixed.

Keyword: 

One-line Description:

Lamp on time warning does not appear

Problem:

When running a self test or performing verification the instrument should be in proper working conditions. One of these conditions is the lamp on time. A warning should be given if this condition is not met. This warning does not appear.

Temporary Solution:

n/a

Fix Information:

Fixed in code.

Keyword: 

One-line Description:

Hardware Button not allowing Security Pack Operator to Sample Advanced Mode

Problem:

When running Security Pack in Advanced Mode as Operator, Front Panel Hardware Sample button will not allow an operator to measure a sample.  The software button on the GUI will allow this.

Temporary Solution:

n/a

Fix Information:

Fixed in code B.04.02

Keyword: 

One-line Description:

Uv-Vis Autosampler Security Pack combination can cause crash

Problem:

The combination G1115, G1116 and G1813 running on B.04.01 on XP sp 3 with sipper and XY-autosampler  crashes Chemstation with a C++ error when selecting the XY-sampler as sampling unit.

From Peter Elinarsson:
"Installed the latest B.04.01 CS. If I install just general and advanced everything works fine. I can control both the XY-autosampler, UV-Vis itself and the pump. But when I install/add the security pack I’m not able to control the autosampler anymore. When trying to select the XY-sampler as sampling unit a C++-error appears. CS crashes completely and shuts down after this. If I just select sipper I can control both the pump and the UV-Vis w/o problem.

 During installation I observed one thing that I really don’t think should influence on this. It the part in the security Pack installation were you take ownership of files. On the customers computer it’s is not possible to add the ChemstationAdmin group to this do due to policies on their domain. you can see that it’s greyed out."

Temporary Solution:

n/a

Fix Information:

updated Gilson GSIO library to ver 2.0

Keyword: 

One-line Description:

Aborted Automation is not saved while in Security Pack

Problem:

Having security pack and aborting an automation in standard mode is not saving the results.

Temporary Solution:

n/a

Fix Information:

Fixed in code B.04.02

Keyword: 

One-line Description:

Operator is able to overwrite data in standard mode with security pack

Problem:

Operator is able to overwrite data in standard mode with security pack

Temporary Solution:

n/a

Fix Information:

Fixed in code B.04.02

Keyword: 

One-line Description:

Selection of XY Autosampler in Security Pack environment crashes ChemStation

Problem:

When the XY Autosampler is selected with UV-visible ChemStation B.04.01 on Windows 7 with the Security Pack G1813AA installed, the running ChemStation session crashes.

Temporary Solution:

n/a

Fix Information:

Update to Gilson GSIO library ver 2.0

Keyword: 8453 Control

One-line Description:

Instrument keys don't work in Standard and Dissolution mode

Problem:

If a key on the instrument is pressed in Standard or Dissolution Mode and 
if the Security Pack is installed, the error message: 'Undefined symbol:
zzavProcessAction' is displayed.

Temporary Solution:

None

Fix Information:

Fixed in Revision A.09.01.

Keyword: Access

One-line Description:

Instrument keys are active if the ChemStation is locked

Problem:

If a ChemStation session is locked, all operations of the instrument shall
be locked. But in that state the measurement keys on the instrument are
still activated and any measurement can be performed without a valid
login to the ChemStation.

Temporary Solution:

None

Fix Information:

Fixed in Revision A.09.01.

Keyword: Access

One-line Description:

No exit and program termination for unauthorized users in Autostart mode

Problem:

If the Autostart feature is checked, the application does not terminate automatically. Instead the logon dialog is displayed and a the exception of the ShutDownEvent as a box with OK button

Temporary Solution:

n/a

Fix Information:

Fixed in code.

Keyword: Audit Trail

One-line Description:

Data are not saved, if a Dissolution run is aborted.

Problem:

If a dissolution test is aborted prior to the programmed run time, the dissolution result file is not saved automatically. The dissolution result file
has to be saved manually.

Temporary Solution:

Save data using the file menu's save result command.

Fix Information:

Fixed in Revision A.09.01. If the dissolution run is aborted, the PostRun
sequence is automatically  executed. In addition the user is forced to
add the action "Save Dissolution Result" to the PostRun, in order to
be allowed to start the dissolution run.

Keyword: Audit Trail

One-line Description:

Configured paths may unadvertedly changed to default value

Problem:

During UV software startup if one or more of the win.ini configured paths (e.g. _DataPath$) is not available, the system will unadvertedly revert that path value to a default one. i.e. from _DataPath$=E:\HPCHEM\1\DATA to C:\HPCHEM\1\DATA, when the configured path doesn't exist and the default does.

Though this behaviour might be considered a "feature" of the software, actually the problem is that neither the user is warned, nor the event is reported anywhere, like the instrument logbook as it should be. So user might be working with adrive/path unexpected and unsuitable for backup, etc.

Only if the default path doesn't exist either, the software will ask the user if the _InstPath$ should be used instead, but in any case this won't apparently be reflected on the instrument logbook.

Although this is a common behavior of the UV-Vis ChemStation, it's reported as an issue of the G1813AA as this problem is particularly serious when the Security Pack is installed: the default path might not have the appropriate NTFS permissions set, and the security service might not work either, so the security of the system is broken.

Temporary Solution:

n/a

Fix Information:

Fixed in code B.04.02

Keyword: Data Acquisition

One-line Description:

Instrument buttons and Shortcut keys do not work for Operators

Problem:

When using shortcut keys or the buttons of the font panel of the instrument, they do not work properly for users with operator rights in the security pack installation.
In general all features should be available via the four accessibility options: menu commands, GUI buttons, shortcut keys and instrument buttons. 
The shortcut keys do not work at all and when pressing the instrument buttons a message is issued that this operation is "... not allowed".

Temporary Solution:

n/a

Fix Information:

Fixed in code.

Keyword: Data Integrity

One-line Description:

Measure keys F4, F5, F6 are not disabled by the Security Pack

Problem:

The measure keys F4 (Blank), F5 (Sample) and F6 (Standard) are still
active, even if the measurement should be disabled according to
the dynamic menu structure.

Temporary Solution:

Do not use the measure keys F4 to F6.

Fix Information:

Fixed in Revision A.09.01.

Keyword: ELECTRONIC SIGNATURE

One-line Description:

Full name is not used with domain login

Problem:

If a domain login account is used for the UV-Vis ChemStation,
the domain login name and not the full name is displayed in the
graphical user interface and used for sigantures.

Temporary Solution:

Patch available. Please contact Agilent Technologies.

Fix Information:

Fixed in revision A.10.01

Keyword: Graphics/Views

One-line Description:

Deleted spectra view does not show the deleted spectra

Problem:

When manually switching to the standards view in the UV-visible
ChemStation's Quantification task – while using the Security pack, the view was not properly updated. Rather than displaying the standards and a calibration
curve, “sample” data appeared with the "Processed Standard Spectra" window and the "Calibration Curve" window instead of “standard” and “calibration” data. Sometimes, when a Standard spectrum was acquired the two windows were just  left empty.

Temporary Solution:

None

Fix Information:

Problem fixed in code.

Keyword: Installation

One-line Description:

Installation of the Security Pack to an existing system leads to errors.

Problem:

If "Save Configuration" is selected, when closing the UV-Vis
ChemStation, the new customized configuration is saved in the files
Configon.reg or configof.reg.
If the Security Pack is installed on such an existing system, some
configuration registers of the Security Pack, e.g. Deleted Spectra,
are not available. If these features are used, red line error messages are
displayed.

Temporary Solution:

Delete the files Configon.reg and Configof.reg before installing
the Security Pack on an existing system. They are located in the
folder \hpchem\n\, where n is the instrument number (n=1,2,3,4).

Fix Information:

No fix planned.

Keyword: Saving/Uploading

One-line Description:

Saving data fails after Installation of the Security Pack

Problem:

If the ChemStation is installed using a path name non 16-bit MS-DOS
folder names, the saving of samples and standards fails after the
Security Pack is installed.

Temporary Solution:

Follow the 16 bit MS-DOS rules for the ChemStation directories, e.g.
max. 8 characters for folder and file names.

Fix Information:

Fixed in Revision A.09.01.