Software Status Bulletin

Agilent Lab Advisor     M8550A

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: Reports

KPR#:120087 Distorted font in reports under rare conditions

Keyword: 

One-line Description:

Inconsistent execution time between the Logs & Results screen and the test printout.

Problem:

In the Lab Advisor software two different times are used to track events and actions. Each LC module has its own clock and when printing a test result directly after execution it will use the module clock time. When storing the result it gets a time stamp from the PC clock which may differ.

Temporary Solution:

In the System Overview screen a warning will be given if the module clock and the PC clock are differing more than 24h. To make sure the report and the Logs & Result entry have the same time synchronize the module clocks to PC time (right click the module in System Overview and select "Sync Device Clocks With Controller Time") before running tests.

Fix Information:

n/a

Keyword: 

One-line Description:

Garbage characters in CSV file export.

Problem:

Garbage characters and cosmetic issues may occur in CSV file exported from the signal plot of the Instrument Control screen.

Temporary Solution:

n/a

Fix Information:

No Fix planned

Keyword: 

One-line Description:

Add Log Dialog: Number of Input Characters and Characters Left inconsistent

Problem:

In LA Logs & Results screen press "Add Log Entry". The Add Log Entry dialog pops up. 
Below the "Log:" text field you can see the number of characters left which you can enter into the field. 
In total the field allows 50 characters in case e.g. of English language.
In case of Japanese or Chinese installation this display might show an inconsistent number of characters left.  
Reason is that fonts using Unicode (Japanese or Chinese Characters) will consume more than one Byte per Character.

Temporary Solution:

Be aware that the display of left characters is not consistent in case of using Japanese/Chinese characters

Fix Information:

No fix planned

Keyword: 

One-line Description:

Communication may be lost in Instrument Control

Problem:

If switching back and forth to the Instrument Control screen, it may happen that the communication to the instrument is lost.

Temporary Solution:

Close the Lab Advisor software. Start the Lab Advisor and reconnect to the instrument.

Fix Information:

The defect is fixed in Lab Advisor version B.02.05

Keyword: 

One-line Description:

Firmware update information not shown in Logs & Results

Problem:

Whenever a firmware update is done in an LC module the date and time of the update is stored in the module. This is however not true if the update is to the same revision of the firmware as is already installed as the module ignores it and only stores information about the original update. In Logs & Results there will be no traces after this update.

Temporary Solution:

For complete history never install the same revision of firmware as is currently installed on a system again. Always up- or downgrad the firmware revision.

Fix Information:

No Fix planned

Keyword: 

One-line Description:

FLD intensity testing, the report has issues on Chinese system

Problem:

On a Chinese installation run the FLD intensity testing and print the report. The report shows font issues which makes the report partially unreadable. 

Patrially fixed the problem:
The Report now uses SimSun font for every textfield. However the "font rendering issue" can't be fixed by LabAdvisor code as it is a problem with Microsoft Reporting. 
See: https://connect.microsoft.com/SQLServer/feedback/details/482312/ssrs-report-font-rendering-issue

It looks a little bit better with SimSun font but does not fully solve the problem. 

When exporting the report to pdf, excel or word there are no font issues.

Temporary Solution:

Workaround for Viewing: Switch to "non" print preview by hitting the "Print Layout" button in the top action bar

Workaround for Printing: Export a PDF  and print the PDF

Fix Information:

No Fix planned

Keyword: 

One-line Description:

Startup time for reports too long

Problem:

time for startup and rendering of a 'System Report' with one offline LC module is sometimes too long under certainconditions: 
B.02.08 initial: 25 sec
B.02.08 second time: 15 sec

Performance profiling revealed that most of the time that goes on while Lab Advisor is starting the report printing dialog it is waiting for the operating system to deliver the current printer settings. How much time this actually is depends on which printer or printer driver is used. For example there might a range between seconds when using a PDF printer and about 12 seconds when using a specific printers.

Root cause is that asking for printer settings leads to a call of the printer driver and might lead to a network call to the printer itself.

Report printing depends on the printer settings. The LA code has to ask for the printer settings. Thus this can not be really solved in Lab Advisor.

Temporary Solution:

Here's the link to an article that recommends removing the domain part of a printer's port address (e.g. using "wadp1079" instead of "wadp1079.germany.agilent.com") in order to reduce the time consumed  when querying printer settings:

https://social.msdn.microsoft.com/Forums/vstudio/en-US/8fd2132a-63e8-498e-ab27-d95cdb45ba87/printersettings-are-very-slow

It is tested that this reduces the time it takes until the report viewer appears significantly.

Fix Information:

No fix planned

Keyword: 

One-line Description:

G4240A Chip Cube Valve Calibration procedures abort using Lab Advisor Version B.02.09

Problem:

Running the Chip Cube Valve Calibration tests (Inner Valve or Outer Valve) using Lab Advisor Version B.02.09, the test aborts after approximately 2 min within the test procedure step 6 - Calibration.
There are no further details provided why the test aborted and the overall test status is "Failed".

Lab Advisor version B.02.09 cannot be used to perform the Chip Cube Valve Calibration for the either valve rotors.

Temporary Solution:

As a workaround, perform the Chip Cube Valve Calibrations (Inner Valve and/or Outer Valve) using the previously released version of Lab Advisor (B.02.08 [178] SP1).

Fix Information:

The defect is fixed in Lab Advisor version B.02.10. 

Keyword: 

One-line Description:

Signal noise test fails but detector test passes for G7100A

Problem:

On edge cases where one of the signal segments of the signal 1 and 2 noise test is higher than the test limit Lab Advisor will display the signal 1 and 2 noise as failed while the average of all segments is below the limit. The overall test status is passed since only the average is decisive for the test result.

Temporary Solution:

Repeat the test

Fix Information:

The defect is fixed in Lab Advisor version 2.17

Keyword: 

One-line Description:

Incorrect signal amplitude for G7121A/B in the Wavelength Accuracy and Spectral Scan test

Problem:

In versions prior to 2.17 the resulting spectrum of a FLD scan in the Wavelength Accuracy and Spectral Scan test has the correct shape but the signal amplitude is too low. 

 

Fix: don´t divide by "number of samples" for G7121x

Temporary Solution:

N/A

Fix Information:

Updating Lab Advisor to version 2.17 or newer solves the issue.

Keyword: 

One-line Description:

Incorrect holmium oxide test result

Problem:

On some edge cases the holmium oxide test passes even when the signal to noise ratio is not sufficient, spurious peaks could be detected as valid, resulting in false positive results.

Temporary Solution:

N/A

Fix Information:

The defect is fixed in Lab Advisor version 2.18

Keyword: 

One-line Description:

Incorrect vial sequence during injector step test for  G1329A/B, G1313A, G1389A, G2260A, G4282A/B, G4303A, G1367A-E, G1377A, G4226A, G4304A and G5667A

Problem:

When performing the injector steps test with G1329A/B, G1313A, G1389A, G2260A, G4282A/B, G4303A, G1367A-E, G1377A, G4226A, G4304A and G5667A the sampler arm uses the incorrect sample position.

Temporary Solution:

N/A

Fix Information:

The defect is fixed in Lab Advisor version 2.19 SR1 

Keyword: 

One-line Description:

Permanently delete HW module leads to deletion of all result files

Problem:

Clicking on "Permanently delete HW module" removes all results from all systems in Lab Advisor instead of removing only the results from the chosen module.

Temporary Solution:

Avoid deleting HW modules or copy the Results folder from C:\ProgramData\Agilent Lab Advisor\AgilentLabAdvisorData\Results before deleting the HW module. After deleting the HW module copy the Results folder back.

Fix Information:

The defect is fixed in Lab Advisor version 2.19 SR2

Keyword: 

One-line Description:

G7115x/G7165x Holmium Oxide test sanity check to strict

Problem:

G7115x/G7165x Holmium Oxide has a sanity check to ensure the filter was correctly moved into the light path. In some cases this sanity check may be too strict and abort the test while the optic behavior is actually in specification.

Temporary Solution:

No temporary fix available.

Fix Information:

Lab Advisor 2.21 improves the sanity check

Keyword: 

One-line Description:

Data Import to new Lab Advisor installation might prevent Lab Advisor from starting

Problem:

When importing Lab Advisor data with many instruments, the Lab Advisor might no longer start after the import succeeded.
System Overview is limited to show 25 instruments, when more instruments are available "System Groups" must be activated in the settings.
In case of a fresh installation "System Groups" is turned off and when importing data from an installation with many system this may exceed the 25 system limit and makes the Lab Advisor stop working

Temporary Solution:

Enable the System Grouping before importing the data

Fix Information:

With Lab Advisor 2.21 the "System Groups" will automatically be enabled when required during the data import

Keyword: 

One-line Description:

Test results not shown in Logs & Results when PC goes to sleep while test not yet finalized

Problem:

When a diagnostic procedure (e.g. G7112B Elasticity Calibration) completed all steps but is not finalized (diagnostic UI remains open with buttons 'Back' and 'Print' shown), not test result is available in Logs & Results after the PC went into sleep or hibernating state.

Temporary Solution:

Deactivate PC standby/sleep mode or ensure the procedure is finalized by clicking 'Back' when the procedure completed all steps

Fix Information:

Fix will be investigated in next project

Keyword: 

One-line Description:

NT login not prevented when logged in user not mapped to AD groups

Problem:

When NT Authentication provider is enabled, users log into Lab Advisor with their current Windows NT user and receive the permissions based on a AD group to Lab Advisor permission mapping.
In case a NT user is not part of a mapped group, the NT user is not prevented to login

Temporary Solution:

No temporary fix required. However, those users without permission only have read access on certain information, but are not able to change data.

Fix Information:

With Lab Advisor 2.21 NT users not part of a mapped AD group won't be able to login any more

Keyword: 

One-line Description:

Audit Log App shows maximum of 5000 entries

Problem:

The Audit Log app limits the view to 5000 entries. Depending on the number of total entries, not all entries can be reviewed with the existing filters

Temporary Solution:

No temporary fix available

Fix Information:

With Lab Advisor 2.21 the Audit Log app allows to define a time range filter. By specifying a time range all entries can be reviewed.

Keyword: 

One-line Description:

FLD Wavelength Calibration aborts after manual reset of grating/wavelength calibration

Problem:

Lab Advisor 2.21 aborts the FLD Wavelength Calibration (G1321x/G7121x) with an error in the last step, when the grating/wavelength calibration on the module has been manually reset before, as recommended in the manual.

Temporary Solution:

Downgrade Lab Advisor to version 2.20

Fix Information:

Will be fixed in Lab Advisor 2.21 SR1

Keyword: Reports

One-line Description:

Distorted font in reports under rare conditions

Problem:

Report fonts may look distorted if the display aspect ratio is not 4:3 and the computer cannot detect the display device information. This typically happens if Lab Advisor is running in a virtual machine or via remote desktop.
The problem has been addressed with Microsoft but until now no resultion is available.

Temporary Solution:

- Select pdf as report format.
- Save the generated report pdf file to a temporary directory.
- Open the pdf file in Acrobat Reader and print it from there.

Fix Information:

No Fix planned