Software Status Bulletin

OpenLAB ECM Intelligent Reporter     G4635AA

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

KPR#:290 Amount for uncalibrated peaks is not reported on
KPR#:344 Installation of ChemStation B.04.01 SP1 with OLIR A.01.01 results in a failure to initialize the ECM API from OLIR

Keyword: ChemStation , OpenLAB ECM

KPR#:344 Installation of ChemStation B.04.01 SP1 with OLIR A.01.01 results in a failure to initialize the ECM API from OLIR

Keyword: Client

KPR#:161 Message about invalid login information is misleading
KPR#:538 OLIR uses UTC for date/time values
KPR#:624 PDF Report destination path is not kept for the following report
KPR#:625 Incorrect base line position displayed with ICM instrument data

Keyword: Client Querying

KPR#:156 Querying for a date using condition "greater (>)" works as "greater equal (>=)"
KPR#:169 Querying for the field "Sequence.Operator (Acq.)" not possible
KPR#:171 Querying for the field "Sequence.Acquisition Date" not possible
KPR#:271 Querying for the File Upload User requires a wildcard (*) after the user name
KPR#:297 MS SQL Server: Querying for date items retrieves no results
KPR#:617 "Object reference not set to an instance of an object" error when running DB query
KPR#:635 Query execution error due to request channel time out

Keyword: Client Report Rendering

KPR#:245 Report rendering fails with an error "ORA-01008: not all variables bound"
KPR#:250 Report template does not respond to selection made with the filter
KPR#:413 De-installation of Extensions for Reporting Services
KPR#:619 OLIR PDF report may show empty pages and black rectangles
KPR#:620 Slow database performance with increasing numbers of projects and users
KPR#:640 Reported injection volume shows negative value
KPR#:653 Calculating the standard deviation of identical numbers may return NaN
KPR#:655 Incorrect position of integration baseline
KPR#:657 Changes in report templates are not immediately shown on report printouts
KPR#:659 Rendering error when using a template containing a large result matrix
KPR#:676 Slow rendering performance on large result databases

Keyword: Help

KPR#:343 ACAML Database 1.1 -> 1.2 Migration Issue: Purity, 3PointPurity will be lost.

Keyword: Installation

KPR#:242 Sync Service update: Installation of ECM API and Report Server Extensions fails
KPR#:342 Installing OLIR on ECM 3.3.2 replaces the ECM 3.3.2 help, ECM client IQ fails
KPR#:626 Service Configuration error caused by long password or account names
KPR#:638 Error during installation: "Cannot connect to the datasource AcamlDB"
KPR#:639 Rev. A.01.01 Database migration will fail when executed from A.02.01 SP1 CD
KPR#:643 Database IQ tool ignores instance name selection
KPR#:660 Software installation media does not provide OpenLAB Shared Services installation
KPR#:663 Database creation fails in case of missing write permissions
KPR#:669 OpenLAB ECM Intelligent Reporter rev. A.02.04 Database IQ fails with warning

Keyword: OL FT Services

KPR#:623 Certain GC signals cannot be reported with Intelligent Reporter rev. A.02.01
KPR#:648 Slow data synchronization of OpenLAB CDS EZChrom Data and OpenLAB ICM data
KPR#:654 Chromatograms are not shown correctly in case of added or overwritten injections

Keyword: OpenLAB ECM

KPR#:344 Installation of ChemStation B.04.01 SP1 with OLIR A.01.01 results in a failure to initialize the ECM API from OLIR
KPR#:252 Renaming of an LCDF Path is not propagated to the Reporting Defaults
KPR#:618 PDF Report name is limited to 111 characters

Keyword: OpenLAB ICM

KPR#:256 OpenLAB ICM Residuals, Cal curve scale, ISTD Units, NormConc Units not reported
KPR#:274 ACQ Method not present for OpenLAB ICM data files
KPR#:667 Peak lables for undetected compounds data cannot be hidden
KPR#:650 ACAML result files generated by OpenLAB ICM contain wrong injection time and injection modification time stamp formats

Keyword: OpenLAB ICM , Report Template Design

KPR#:667 Peak lables for undetected compounds data cannot be hidden

Keyword: OpenLAB ICM , Report Templates

KPR#:650 ACAML result files generated by OpenLAB ICM contain wrong injection time and injection modification time stamp formats

Keyword: Report Template Design

KPR#:667 Peak lables for undetected compounds data cannot be hidden
KPR#:47 ChemStation and ChemStore DiagnosticData xml field have different names
KPR#:120 SQL Server: COLLATE suffix automatically appended to text attributes
KPR#:235 Display the revision number of the RDL template in the report
KPR#:641 Query designer of BI Studio 2005 does not support SQL 2008
KPR#:662 Filter definition does not always allow usage of OR operators
KPR#:664 Unknown error when saving a report template
KPR#:666 Peak labels are hidden in case the peak apex exceed the response axis range
KPR#:668 Reporting time format does not offer an option of (dd/mm/yyyy and time)

Keyword: Report Templates

KPR#:650 ACAML result files generated by OpenLAB ICM contain wrong injection time and injection modification time stamp formats
KPR#:248 For reports with long lists, the printout/ pdf contains empty pages
KPR#:325 MS SQL Server: report template PeaksAndCompounds_A4.rdl cannot be opened
KPR#:645 Column utilization report does not distinct injections
KPR#:658 Customized chromatogram or axis lables may not display correclty
KPR#:672 OpenLAB ECM Intelligent Reporter Does not Save User Name and Machine Name in Report Template Audit Trail

Keyword: SQL Server

KPR#:652 Rendering of large reports (>100 runs) causes a client time-out

Keyword: 

One-line Description:

Changing the template in OLIR leads to 2 times review report parameter window

Problem:

After applying certain filter on data when user will load a template and then select another template from "Recent Templates” section, user may observe 
"Review report parameters" dialogue twice.

Temporary Solution:

Each template version has a unique identifier, the recent or favourites to that specific identifier/version which was used unchanged last. So, it is not shown the last opened. Since, it is misunderstood by user, so no temporary fix is applicable here.

Fix Information:

n/a

Keyword: 

One-line Description:

OLIR client / BI Studio under Citrix: printing can cause memory corruption

Problem:

OLIR Client and Business Intelligence Studio use the Microsoft Report Viewer Control from which printing a report in a Citrix session can cause a memory corruption and subsequent crash of the application.

Temporary Solution:

Workaround or compatibility checks unavailable

Fix Information:

No fix planned.

Keyword: 

One-line Description:

Table repetition header may be visible for invisible tables

Problem:

The table repetition header appears visible for invisible tables in cases where the table repetition has been added after making the table invisible.

Temporary Solution:

- right click the table in the template editor
- go to properties > Advanced
- check the “visible” box
- press “Apply”
- un- check the “visible” box
- press “OK”

Fix Information:

There is currently no fix planned

Keyword: 

One-line Description:

Missing delete option for out-dated signal data

Problem:

In order to generate chromatographic and spectral data in OpenLAB ECM Intelligent Reporter outputs, copies of the raw information need to be available in a slightly compressed format. The ACAML tables of the ECM database act as a cache to keep this information as long as the data does not get archived by the ECM data retention mechanism.
Depending on the data retention period in ECM, the amount of data stored in the ACAML tables can lead to substantial data base growth and performance drop. The growth rate and database size are influenced by
•	The number of instruments connected to OpenLAB
•	The workload
•	The data retention period/archiving intervals
•	The analytical technique or detector types: LC or CE - Diode Array Detectors or Fluorescence Detectors may produce spectral information that outgrow a plain chromatogram by a magnitude
ECM data retention periods are typically set far too high to keep the ACAML Signal data file at a decent size and revision A.02.01 does not offer any tools to delete cached data on demand.

Temporary Solution:

n/a

Fix Information:

The A.02.01 Service Pack 1 provides additional means to manage the data retention in the ACAML tables. The updated Synchronization Service allows disabling the extraction and storage of chromatograms or spectra or both.  If none of the report templates in use displays spectral information, the data doesn’t need to be stored in the cache in the first place. The same can be applied to chromatograms, too.
In addition to the new Synchronization Service a new Signal Data Retention tool provides means to delete cached, but unused spectra and/or chromatograms based on age, storage location or project or combinations of these parameters. DB Administrators can set up maintenance plans and define individual retention times for analysis results and the related chromatograms and spectra.

Keyword: 

One-line Description:

Reporter client does not support '/' character in location/cabinet/drawer/folder name

Problem:

Reporter client does not support '/' character in location/cabinet/drawer/folder name:
When opening a report template from a L/C/D/F location containing a forward slash, the following error appears:
The specified item does not exist. Parameter name: id

Temporary Solution:

Remove '/' characters from L/C/D/F names.

Fix Information:

There is currently no fix planned.

Keyword: 

One-line Description:

Distored chromatogram on report preview and print out

Problem:

Using OpenLAB Intelligence Reporter rev. A.02.01 it happened on one occasion that the ChemStation chromatogram displayed on the report is distored and flat baseline was twisted like a stair.
The integrator's baseline position remained in the correct position.

Temporary Solution:

N/A

Fix Information:

The defect is fixed in OpenLAB Intelligence Reporter rev. A.02.01 Service Pack 1.
This Service Pack is available  in the Agilent Lab Informatics customer care portal on http://www.ccportal.chem.agilent.com/PortalHome/

Keyword: 

One-line Description:

User with no edit permissions can change import folder settings

Problem:

The following defect affects OpenLAB Intelligent Reporter rev. A.01.01 and A.02.01 with or without SP1:
Users with no EDIT but VIEW permissions can change the Import folder settings of the reporting defaults.
The user gets a warning concerning insufficient priviledges, but the changes are submitted in the background.

Temporary Solution:

To reduce the likelihood of error occurrence, it is recommended to assign each location or cabinet to a reporting project.
As soon as it is assigned to a certain project, it cannot be assigned to a 2nd one and the assignment does also not happen in the background.

Fix Information:

n/a

Keyword: 

One-line Description:

Sporadic Synchronization service failure:  Root element is missing

Problem:

Under certain circumstances it may happen that the ACAML result file generated by the CDS systems ChemStation B.04.0x or OpenLAB ICM 3.3.2 are empty and show a size of 0 kB.
This result file is required by the OpenLAB Intelligence reporter to populate the result database and the affected results are not available for reporting.

This failure will get noticed on the File Transfer server where the OpenLAB Intelligence Reporter's Synchronization service shows a failure:
Root element missing

The likelihood of this error appearance increases with the number of peaks per run and the number of runs per sequence. GC chromatograms typically contain more peaks compared to LC chromatograms and GC data is more often affected.

Temporary Solution:

The failed synchronization job needs to be deleted from the synchronization queue.
Reprocessing the affected sequence triggers the generation of a new ACAML file.

Fix Information:

OpenLAB Intelligence Reporter Hotfix 2 for ChemStation B.04.02 and ICM 3.3.2 and Hotfix 6 
for ChemStation B.04.01 are available on the OpenLAB Intelligence Reporter patch download 
area accessible through the Agilent Lab Informatics Customer Care Portal
 (http://www.ccportal.chem.agilent.com/PortalHome/).

Keyword: 

One-line Description:

ChemStation Method files causing numerous warning messages in sync service

Problem:

The upload of ChemStation method files (..M.SSIZIP) to ECM causes numerous warning messages in the OpenLAB ECM Synchronization Service event viewer.
In the print out of the event log file, the error messages appear like:
Warning	4/23/2010 2:09:13 
AM	Synchronization job finished with errors 
(JobID=XYZ, AccountName=XYZ, FileID={CCCF26B2-C20C-407C-9CA1-D89056C17A81}, 
Filename=XYZ.m.general.ssizip, FileRevNumber=0, 
FileCachePath=\\\CyberLABTempData\CyberLABData\4AFAD312D2044A2985B21039C08C9981\XYZ.M.General.SSIZip, 
Action=Import): 
ACAML data imported with errors: Empty file

Temporary Solution:

These warning messages can be safely ignored.

Fix Information:

This defect is fixed in OpenLAB ECM Intelligent Reporter rev. A.02.02.

A hot fix 6 is available for A.02.01 SP1 systems on
the OpenLAB Intelligence Reporter patch download
area accessible through the Agilent Lab Informatics Customer Care Portal
(http://www.ccportal.chem.agilent.com/PortalHome/)

Keyword: 

One-line Description:

Sporadically a wrong result revision number appears on a report

Problem:

It has been reported that the result version numbering may show a gap of one run.
The likelihood of such a incident seems to be very low and the problem seems to be related to the fact that one results set got uploaded to 2 different folders within a short time frame.
When loading a result set to a different folder a new ECM audit trail starts 
and the OLIR version counting starts again with 0.
Under the error condition, a new version was uploaded to the original folder and version counting was also taking the version in the other folder into account.  As a consequence, the version counting made a jump of 2 revisions.

This error is not reproducible and the error conditions are not clear.

Temporary Solution:

Print out this Known Problem Report (KPR) and refer to the KPR# in the approval comment of the affected result set.

Fix Information:

There is currently no fix planned.

Keyword: 

One-line Description:

Additional signals reported with non-matching calibration table

Problem:

Whenever a ChemStation data file was processes with a non-matching calibration table the additional signal appears in the ACAML file. 

As there is no raw data associated with this signal, in the OLIR report, there are no peaks reported for this additional signal. In the ACAML data and the OLIR report, there may appear two DAD1A signals, which reflects the setup of the ChemStation DA method.

Temporary Solution:

Added note in online help file – "If a ChemStation data file was processed with a non-matching calibration table, the report may show an empty calibration curve. This happens if the signal details are configured, but no data was recorded for this signal."

Fix Information:

This defect is fixed in OLIR_A.02.01.

Keyword: 

One-line Description:

Have UV-spectra use snippet `spectraplot` -> report

Problem:

When user makes a preview of a report template that contains the ‘Spectra Plot’ snippet from the ‘Spectra’ node of the RTE tree browser, the result of that rendered Spectra doesn’t show the expected result.

Temporary Solution:

In such case user needs to create a filter to eliminate the null peaks.

Fix Information:

No fix planned.

Keyword: 

One-line Description:

Compliance protocol A.01.03 does not consider sorting of chromatograms

Problem:

The OpenLAB Intelligence Reporter Operational Qualification (OQ) Attachment Protocol rev. A.01.03 does not consider sorting of chromatograms.
If a single signal plot gets added to sequence summary report template the default sorting order is ascending by injection ID.
The injection ID is an internal, database specific ID that neither reflects the order of sample injection nor being comparable with the IDs used in another database.

Hence, the order of chromatograms printed on the example report OQTest_Report.pdf is not necessarily the same if compared to the report being generated on the database to be qualified.

Temporary Solution:

To overcome this problem on productive used report templates, it is recommended to sort the chromatograms by e.g. injection time or define nested and sorted groups, based on e.g. sample type, injection time, etc.

Fix Information:

This issue is addressed with the latest version of the Universal Software Qualification (USQ) tool of the ACE tool.

Keyword: 

One-line Description:

GC 6850 signal data causes synchronization failure

Problem:

OpenLAB Intelligence Reporter A.02.01: 
GC 6850  signal data collected with ChemStation B.04.0x causes the OpenLAB ECM synchronization serviced fail on extracting the signal.
The jobs do not get processed and reports cannot be generated.

Temporary Solution:

If report templates do not contain chromatograms or spectra plots, the extraction of chromatograms and spectra can be turned off in the Synchronization Service Configuration Panel located on the File Transfer Server.
This is a global setting and affects all instrument data.

Fix Information:

This defect is fixed in OpenLAB ECM Intelligent Reporter rev. A.02.02.

A hot fix 7 is available for A.02.01 SP1 systems in the Electronic Software and License Delivery portal at https://agilent.subscribenet.com.

Keyword: 

One-line Description:

Launching Reporter Client out of B.04.xx ChemStation will not create reports

Problem:

The B.04.xx ChemStation software allows to automatically launch the Reporter Client at the end of a sequence run in order to create a summary report.
OpenLAB Intelligent Reporter A.02.02 no longer supports this operation mode.

Temporary Solution:

n/a

Fix Information:

B.04.xx ChemStation software users need to use revision OpenLAB Intelligent Reporter A.02.01 SP1.

Keyword: 

One-line Description:

Sync Service Error - The file contains more sample values than expected

Problem:

The Synchronization Service of OpenLAB Intelligence Reporter A.02.01 or A.02.01 SP1 may fail with error
"The file contains more sample values than expected. This may indicate a corruption or an error in the data file.Parameter name: numberOfSamples" 
and the data is not available for reporting.

This defect affects all chromatograms collected with GC 68x0 instruments controlled by RC.Net drivers. Classical instrument drivers do not cause this error.

If chromatograms are excluded from the synchronization process (rev. A.02.01 SP1), the error is not observed.

Temporary Solution:

n/a

Fix Information:

This defect is fixed in rev. A.02.02 as well as by the updates provided with Hotfix 5 for rev. A.02.01 SP1.
This Hotfix is available through the Labinformatics support portal at
www.agilent-labinformatics.com/support/
Search the Knowledge Database for "Hotfixes".

Keyword: 

One-line Description:

GC/MSD data files causing numerous warning messages in sync service

Problem:

The upload of GC/MSD ChemStation's data files (..D.SSIZIP) to ECM causes
numerous warning messages in the OpenLAB ECM Synchronization Service 
event viewer.
In the print out of the event log file, the error messages appear like:
Warning 4/23/2010 2:09:13 
AM Synchronization job finished with errors 
(JobID=XYZ, AccountName=XYZ, FileID={CCCF26B2-C20C-407C-9CA1-D89056C17A81}, 
Filename=XYZ.d.ssizip, FileRevNumber=0, 
FileCachePath=\\\CyberLABTempData\CyberLABData\
4AFAD3039C08C9981\XYZ.D.SSIZip, Action=Import): 
ACAML data imported with errors: Empty file

Temporary Solution:

ChemStation for GC/MSD does currently not an ACAML result file and reporting 
of GC/MSD data is not supported by OpenLAB Intelligence reporter A.02.01.
These warning messages can be safely ignored.

Fix Information:

This defect is fixed in OpenLAB ECM Intelligent Reporter rev. A.02.02.

A hot fix 6 is available for A.02.01 SP1 systems on
the OpenLAB Intelligence Reporter patch download
area accessible through the Agilent Lab Informatics Customer Care Portal
(http://www.ccportal.chem.agilent.com/PortalHome/).

Keyword: 

One-line Description:

Large detector response axis scales show zeros only

Problem:

For signal data with high detector response scales, e.g. originated from OpenLAB CDS EZChrom, the y-axis values cannot be displayed and only zeros are shown.

Temporary Solution:

N/A

Fix Information:

With OpenLAB ECM Intelligent Reporter the number format changes to scientific if the axis scale exceeds a range where the number can no longer be displayed correctly.
For OpenLAB CDS EZChrom data, a conversion factor is shown to translate detector responses to e.g. mAU shown in EZChrom standard reports.

Keyword: 

One-line Description:

OpenLAB CDS instrument shortcuts are no longer working after installation of OpenLAB ECM Intelligent Reporter Client

Problem:

After installing an OpenLAB ECM Intelligent Reporter Client A.02.03 on top of OpenLAB CDS A..01.03, the instrument shortcuts on the workstation's desktop can no longer be used to start the instruments.

The user  will see a lengthy error message starting like:
"An error occurred while initializing module Intelligent Reporter. Could not resolve instance of IExtension Service"

Temporary Solution:

There are 2 workarounds available:
A)  Use the OpenLAB Control Panel to start the on-line or off-line instruments.
or
B) In case of a centralized  OpenLAB Shared Services Server you could:
Use "Change/Modify" feature of the Windows "Add/Remove Programs" feature to remove the  "OpenLAB Control Panel Plugin" of the OpenLAB ECM Intelligent Reporter Client.
After un-installing the plugin, the program icons can be used as usual, but the Intelligent Reporter Client can only be started from the Windows "Start" menu. Report project management is also no longer possible on such a modified client.
For report project management, it is recommended to use a dedicated reporter client that has the  "OpenLAB Control Panel Plugin" installed.

Fix Information:

This defect is fixed in revision A.02.04 of OpenLAB ECM Intelligent Reporter.

Keyword: 

One-line Description:

SQL server: Migration to A.02.04 shows inaccurate information in log file

Problem:

When updating a SQL server hosted ECM database server from Intelligent Reporter rev. A.02.0x to A.02.04 the migration log file says the DatabaseCleanUp has been installed and it is disabled.

This logfile message is also shown in cases where the Data Retention Tools for rev. A.02.0x have been installed previously and where the associated SQL server agent jobs are enabled.

Temporary Solution:

The message in the migration logfile can be ignored, if data retention policies have been implemented before migrating the database schema.
Use the Microsoft SQL server management console to check the definition and run status of previously installed data retention policies.

Fix Information:

There is no fix planned.

Keyword: 

One-line Description:

Adding new data fields to older templates causes rendering error

Problem:

Adding newly introduced fields to an existing OLIR A.02.03 template may cause rendering errors if the fields are not added on the correct format.

Temporary Solution:

e.g. INJECTION_DAMETHOD_IDVER needs to be written in the template as 

[INJECTION_DAMETHOD_IDVER]  (For SQL Server templates - it should be enclosed in square brackets) or 
"INJECTION_DAMETHOD_IDVER" (For Oracle templates - it should be enclosed in double quotes)

Fix Information:

There is currently no fix planned

Keyword: 

One-line Description:

Non-exisitng GC signals cause failure of the ECM synchronization service

Problem:

In cases where GC detectors are turned off (e.g. back detector), but signals are supposed to be saved, an empty window with no baseline is shown in the ChemStation Data Analysis view.

If data gets uploaded to ECM, the ECM synchronization service will fail with error message:
Synchronization job failed (JobID=XXX, AccountName=XYZ, FileID=XYZ, Filename=XYZ, FileRevNumber=0, FileCachePath=XYZ\______.SSIzip, Action=Import): Value cannot be null.
Parameter name: signalName at Agilent.XSR.AcamlSyncServiceLib.SignalImport.SignalRawDataCollection.get_Item(String signalName)

Temporary Solution:

The error is caused by a non-existing signal caused by a turned off-back detector.

Recommended workflow:
- Do not save signals from a detector that is turned off

Note: Saving raw data files while the detector is turned off unnecessarily consumes disk space.

Fix Information:

There is currently no fix planned.

Keyword: 

One-line Description:

Misspelled expression in template editor of ECM IR A.02.04

Problem:

The report template editor of ECM IR rev. A.02.04 used some mis-formulated expressions in the report items listed below.  The syntax is correct, but the returning number or text string might not be the expected one.

Expression starting with  "=First(choose(..."  , should be written "=choose(First(..." to return meaningful results in case of enumerated report items that are translated into a text string.

The following report items need to corrected to return meaningful results:

LIST:
fields/ Sample_type
fields/ Sequence_Type
fields/ Compound_Type
fields/ Compound_QuantitationType
fields/ CalibCurve_Origin
fields/ CalibCurve_Type
fields/ Peak_Type
fields/ Peak_CalibRole

snippet/ Sequence Table -> the field Sample_type  ( here the expression is w/o First: "=choose(##...
snippet/ Sample Info Short -> the field Sample_type  ( here the expression is w/o First: "=choose(##...
snippet/ Sample Info Long -> the field Sample_type  ( here the expression is w/o First: "=choose(##...

Temporary Solution:

Use the expression editor of the report template editor to change the syntax.

Fix Information:

There is currently no fix planned.

Keyword: ChemStation

One-line Description:

Amount for uncalibrated peaks is not reported on

Problem:

For ChemStation data, the amount for uncalibrated peaks calculated with a given response factor cannot yet be reported on in OpenLAB Intelligence Reporter.

Temporary Solution:

This issue is related to the ACAML file created by ChemStation. ChemStation rev. B.04.01 will write this information into the ACAML file and it will be reportable in OpenLAB Intelligence Reporter.

Fix Information:

n/a

Keyword: ChemStation , OpenLAB ECM

One-line Description:

Installation of ChemStation B.04.01 SP1 with OLIR A.01.01 results in a failure to initialize the ECM API from OLIR

Problem:

When installing OpenLAB Intelligence Reporter A.01.01 with ChemStation B.04.01 SP1, the ECM API object fails to initialize correctly.

After the ECMAPI 1.0.22.0 is installed directly or by ChemStation B.04.01 SP1 (or by another Agilent application), the OpenLAB Intelligence Reporter Client 
fails when logging in into the ECM system with the following error message: "The connection to the ECM system could not be established. Please make sure you can connect to the ECM system using your web browser and that all required ECM extension components are installed on this computer. The ECM API object failed to initialize correctly, ECMCode = -9, ECMMessage = The ECM API object failed to initialize correctly"

OpenLAB Intelligence Reporter A.01.01 uses ECM API 1.0.18.0, whereas ChemStation B.04.01 SP1 uses ECM API 1.0.22.0. However, multiple versions of the ECM API cannot coexist in a process.

Temporary Solution:

n/a

Fix Information:

This problem is fixed by hotfix OLIR_A.01.01_HF02 "Installation of ChemStation B.04.01 SP1 with OLIR A.01.01 results in a failure to initialize the ECM API from OLIR". The hotfix is available for customers to download from the Agilent Life Sciences and Chemical Analysis external web site (http://www.chem.agilent.com) at Home > Technical Support > Downloads and Utilities > Status Bulletins and Patches > OpenLAB Intelligence Reporter Software.

Keyword: Client

One-line Description:

Message about invalid login information is misleading

Problem:

When working with OpenLAB ECM Workgroup, logging in to OpenLAB ECM from the OpenLAB Intelligence Reporter Client may result in an error message indicating that invalid login information was supplied, although the user credentials were correct.

Temporary Solution:

Close the OpenLAB Intelligence Reporter Client, then try logging in again.

Fix Information:

n/a

Keyword: Client

One-line Description:

OLIR uses UTC for date/time values

Problem:

While exporting data  to ACAML files, Chemstation and ICM convert date/time values to UTC format and thus all date/time values shown in the OLIR client are off by the time difference between local time and UTC

Temporary Solution:

User should use System.TimeZone
.CurrentTimeZone.ToLocalTime function for an expression which has date/time type of field(s).

Fix Information:

This defect is fixed in OLIR_A.02.01.

Keyword: Client

One-line Description:

PDF Report destination path is not kept for the following report

Problem:

When a report is rendered and saved back to ECM the FILE SAVE dialog always opens at the root of the ECM content tree. If the user selects a specific path in the ECM this path is not kept. Next time the root is shown again.

Temporary Solution:

N/A

Fix Information:

With rev. A.02.01 SP1 the FILE SAVE dialog keeps the path selection of the last SAVE action.

Keyword: Client

One-line Description:

Incorrect base line position displayed with ICM instrument data

Problem:

It has been reported that chromatograms recorded with OpenLAB ICM may not always show a correct baseline position.
This problems affects all non-Agilent detectors controlled by OpenLAB ICM. Agilent LC and GC detectors are less impacted.

The problem is caused by different scaling of raw data, depending on detector type.

Temporary Solution:

N/A

Fix Information:

With rev. A.02.01 SP1 the Open LAB Intelligent Reporter does no longer imitate the scaling for various detector, but displays the raw data.
This results in correct position of the baseline but potentially large numbers on the y-axis.

Keyword: Client Querying

One-line Description:

Querying for a date using condition "greater (>)" works as "greater equal (>=)"

Problem:

In OpenLAB Intelligence Reporter Client, when filtering on a date (e.g., Injection.Acquisition Date), the condition greater than (>) behaves identically to the condition greater equal (>=). Users need to be aware of this when filtering on a date.

Temporary Solution:

n/a

Fix Information:

This will be addressed with a "how to" example in the online help of the next revision of OpenLAB Intelligence Reporter.

Keyword: Client Querying

One-line Description:

Querying for the field "Sequence.Operator (Acq.)" not possible

Problem:

In the OpenLAB Intelligence Reporter Client, the fields "Sequence.Operator (Acq.)" and "Sample.Operator (Acq.) cannot be queried for ChemStation data as ChemStation does not supply these values

Temporary Solution:

The acquisition name / date and result (reprocessing) name / date can be queried using the filters for injections (e.g., "Injection.Acquisition Operator"). This also selects the related samples or sequences.

Fix Information:

n/a

Keyword: Client Querying

One-line Description:

Querying for the field "Sequence.Acquisition Date" not possible

Problem:

In the OpenLAB Intelligence Reporter Client, the fields "Sequence.Acquisition Date" and "Sample.Acquisition Date" cannot be queried for ChemStation data as ChemStation does not supply these values.

Temporary Solution:

The acquisition name / date and result (reprocessing) name / date can be queried using the filters for injections (e.g., "Injection.Acquisition Date"). This also selects the related samples or sequences.

Fix Information:

n/a

Keyword: Client Querying

One-line Description:

Querying for the File Upload User requires a wildcard (*) after the user name

Problem:

Querying for "File.Upload User" in OpenLAB Intelligence Reporter with the term "File.Upload User" = "Lastname,Firstname" does not retrieve any results. This is so because the "File.Upload User" has the format "Lastname,Firstname (Domain\username)".

Temporary Solution:

When querying for the "File.Upload User", include the wildcard "*" after the name of the upload user. For example, query for "File.Upload User" = "Smith,Mary*".

Fix Information:

n/a

Keyword: Client Querying

One-line Description:

MS SQL Server: Querying for date items retrieves no results

Problem:

On a system with an MS SQL Server database, querying for a specific date retrieves no results. For example, querying for "File.Upload Date = today" retrieves no results. This is the case whenever a specific date. e.g., "today", "yesterday", or "2/1/2008" is defined as the date to be queried for.

Temporary Solution:

When querying for dates use "greater" or "less" operators. E.g., use filters like greater than "today", or filters like greater than "yesterday" AND less than "today".

Fix Information:

n/a

Keyword: Client Querying

One-line Description:

"Object reference not set to an instance of an object" error when running DB query

Problem:

Under certain circumstances some users of OLIR may face an "Object reference not set to an instance of an object" error when running a DB query.
In addition users may notice that the status bar shows "Updating project list ..."  information for 30 seconds before the error occurs. After startup of the Intelligence Reporter Client the "Projects" menu does not show any of the projects assigned to the logged-in user.

Temporary Solution:

The problem is caused by having the root location defined as the default template or filter path. This may happen under the following conditions:

- When setting up new reporting defaults, the user opens the dialog to set a new default template or filter path. If the user changes his mind and press O.K. instead of Cancel, the display does not show any path selected, but internally the root location is selected. 
- If a user likes to remove the default template or filter path there is no other choice than selecting the root location and press o.k. 

The only way to remove the default path from existing reporting defaults is to delete the reporting defaults and re-create them again.

The recommended way to set-up a new project:  
Have at least a “Location” defined as a template and filter path for each and every project.

Fix Information:

A fix is considered for the next Service Release.

Keyword: Client Querying

One-line Description:

Query execution error due to request channel time out

Problem:

On large OpenLAB ECM Intelligent Reporter systems users may experience performance issues during report generation.
After a 90 sec wait-time a warning message is displayed:
"The request channel timed out while waiting for a reply after 00:01:30. Increase the time-out value passed to the call to request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer time out."

This time out problem has been reported only for SQL server 2005 based databases, so far.

The problem is caused by malformed database view causing numerous redundant SQL requests. On larger databases this is causing a bad performance of database query execution.

Temporary Solution:

Reduce the number of records in the OLIR related database tables by using the ECM archiving capabilities.
Note: Archived ECM data cannot be reported by the OpenLAB ECM Intelligent Reporter until the data gets re-synchronized again.

Fix Information:

A Performance Tune #1 script is available to recreate the malformed database view, causing significant reduction of redundant queries.

A tuning script for rev. A.02.01 SP1 is available for download on the OpenLAB Intelligence Reporter patch download area accessible through the Agilent Lab Informatics Customer Care Portal
 (http://www.ccportal.chem.agilent.com/PortalHome/).

Keyword: Client Report Rendering

One-line Description:

Report rendering fails with an error "ORA-01008: not all variables bound"

Problem:

If a report template with a single value parameter (e.g. SequenceID) is used to render a report, a selection of multiple value for this parameter (e.g. two sequences), report rendering fails with an error "ORA-01008: not all variables bound".

Verification: 
Make sure Remote Errors are enabled on the Report Server (http://msdn2.microsoft.com/en-us/library/aa337165.aspx)
Open the client and choose a report template with a single value parameter (e.g. SequenceID).
Select multiple result rows so that there are multiple value for this parameter (e.g. two sequences).
Preview the report results in the error described above.

Temporary Solution:

Make sure not to select multiple values for single value parameters.

Fix Information:

n/a

Keyword: Client Report Rendering

One-line Description:

Report template does not respond to selection made with the filter

Problem:

In the OpenLAB Intelligence Reporter Client, on the "Results" tab, it is possible to apply filters to the data (e.g., the [Name(Result)] does not contain "Standard L2"). These filters apply to the data in the "Results" tab and make the data review in the "Results" tab easier. However, the selections made using filters do not affect the selection of results that are displayed in the report.

Temporary Solution:

Deselect the samples that are not to be included in the report manually.

Fix Information:

n/a

Keyword: Client Report Rendering

One-line Description:

De-installation of Extensions for Reporting Services

Problem:

The installation of SQL Server 2005 or Reporting Services hotfixes or service packs can overwrite the OpenLAB extensions' registration in the report server's configuration files. 

In the OpenLAB Intelligence Reporter Client this results in empty reports. Data from the ACAML DB can be retrieved in a query. however, when trying to render the report, the report is empty. 

In the Sync Service Monitor, testing the Reporting Server results in the message "No OpenLAB Extensions are installed on the Reporting Server."  To test the Reporting Server, in the Sync Service Monitor, on the "Reporter Client Configuration" tab, open the "Reporting Server" tab. Clicking the “Test Reporting Server” Test brings up the message “Reporting Server Test succeeded!". However in the detailed output in the lower right-hand side of the tab the message "No OpenLAB Extensions are installed on the Reporting Server." is seen.

Temporary Solution:

After SQL Server 2005 or Reporting Services hotfixes or service packs have been applied applied to the report server, repair Agilent OpenLAB Extensions for Reporting Services on the Server. 

To do so, from "Control Panel" access "Add or Remove Programs". In the "Add or Remove Programs" window, find the "Agilent OpenLAB Extensions for Reporting Services" and click on the link "Click here for support information". In the "Support Info" dialog, click the "Repair" button. If the "Agilent OpenLAB Extensions for Reporting Services" are not installed or the problem is not fixed by repairing the "Agilent OpenLAB Extensions for Reporting Services", install "Extensions for SQL Server 2005 Reporting Services" from the OpenLAB Intelligence Reporter Installation CD-ROM (see also Service Note G4635AA-007).

Fix Information:

n/a

Keyword: Client Report Rendering

One-line Description:

OLIR PDF report may show empty pages and black rectangles

Problem:

Some OLIR reporting templates generate blank pages and/or black rectangles on the PDF reports exported to ECM. 
PDF reports printed with other PDF prtiners do not show the black rectangles.

This is a problem of the PDF renderer in Microsoft SQL Server 2005 Reporting Services and Microsoft Report Viewer 2008.
A table with a solid border and a hidden column is rendered incorrectly, a border-colored rectangle shows to the right of the table unless the shown columns fill the page width.

Temporary Solution:

1. To remove empty pages
- Reduce the width of the report body
- Calculate the maximum width by subtracting the left and right margins from the page width

2. To remove the black boxes next to the report details
- Set the BorderStyle of table1 to None

Fix Information:

This problem has been reported to Microsoft: https://connect.microsoft.com/SQLServer/feedback/details/531206/ssrs-2005-pdf-renderer-shows-hidden-table-column-filled-with-border-color
However, this is not a bindng service request and a fix for the 2005 version of Reporting Services is unlikely.

Keyword: Client Report Rendering

One-line Description:

Slow database performance with increasing numbers of projects and users

Problem:

With increasing the number of projects and users the performance of report generation drops significantly.

Temporary Solution:

N/A

Fix Information:

Rev. A.02.01 of OpenLAB Intelligence reporter introduces improvements in database view definitions resulting in significant performance improvements in cases of many reporting projects and ECM users.
A Hot Fix 01 for rev. A.02.01 adds additional performance improvments in the
mentioned area.

Hot Fixes 03 and 04 for rev. A.01.01 adds the equivalent database tuning level.

HF03 consists of a SQL script to specifically recompile the 
COMPOUNDSBYPEAKS view in the ACAML schema of an Oracle database.

This HF03 got obsoleted and replaced by HF04 which works on a much broader set of
table views and can be applied to Oracle as well as SQL server databases.
The script set of HF04 recompiles the views:

 ACAML.COMPOUNDSBYPEAKS
 ACAML.COMPOUNDSBYINJECTIONS
 ACAML.COLUMNSBYINSTRUMENT
 ACAML.COLUMNS 
 ACAML.COMPOUNDS
 ACAML.COMPOUNDSBYINSTRUMENTS
 ACAML.INJECTIONS
 ACAML.METHODS
 ACAML.SAMPLES
 ACAML.SEQUENCEINJECTIONS
 ACAML.SEQUENCES
 ACAML.STUDIES

Keyword: Client Report Rendering

One-line Description:

Reported injection volume shows negative value

Problem:

In case of ChemStation data, the reported value for injection volume might be a negative value. Negative values have specific meaning in the ChemStation application.

Temporary Solution:

n/a

Fix Information:

The following expression can be used in the report template if all the reported data was generated with the ChemStation application:

Iif(First(Fields!INJECTION_VOLUME.Value)>0, FormatNumber(First(Fields!INJECTION_VOLUME.Value),3,True,False,False), choose(First(Fields!INJECTION_VOLUME.Value)+5,"external","Inj. program","manually", "No injector"))

Keyword: Client Report Rendering

One-line Description:

Calculating the standard deviation of identical numbers may return NaN

Problem:

When calculating the standard deviation or relative standard deviation of multiple identical numbers, the calculation may return "NaN" rather than 0.

The problem is caused by the small delta derived from the rounded result of the average calculation and the individual values. Summing up these small numbers may result in a floating point exception.

Temporary Solution:

Do not apply standard deviation calculations to series of identical  values.

Fix Information:

There is currently no fix planned.

Keyword: Client Report Rendering

One-line Description:

Incorrect position of integration baseline

Problem:

The baseline positions of OpenLAB CDS EZChrom data reported with OpenLAB ECM Intelligent Reporter A.02.03 are drawn incorrectly.
This defect does not affect the calculated resutls and reported numbers, but affects the graphics only.
In the majority of cases the deviation from the correct position cannot be seen on report print outs or PDF reports.  The defect only gets visible in cases where the response axis is zoomed for detailed display of the baseline or in cases where the signal shows a high off-set.

Temporary Solution:

N/A

Fix Information:

This defect is fixed with OpenLAB ECM Intelligent Reporter A.02.03 Hotfix 3.

Keyword: Client Report Rendering

One-line Description:

Changes in report templates are not immediately shown on report printouts

Problem:

Changes in report templates are not immediately  shown on the printout if the user does not preview the report and save the template first.

Temporary Solution:

Always preview the report printout after applying changes to the template.
Or save and reload the template from disk, if a preview should be avoided.

Fix Information:

There is no fix planned.

Keyword: Client Report Rendering

One-line Description:

Rendering error when using a template containing a large result matrix

Problem:

A template having a matrix inside a list may show a rendering error - The value 'x' is invalid. Valid values are between '0' and 'x'
This error occurs when there is large data used for rendering and due to this the matrix data spans across multiple pages.

Temporary Solution:

For large result matrices it is recommended to print the results to PDF files, rather than paper.
The paper format should adjusted to display large matrices on a single page.

Fix Information:

There is currently no fix planned.

Keyword: Client Report Rendering

One-line Description:

Slow rendering performance on large result databases

Problem:

The Intelligent Reporting features of OpenLAB ECM Intelligent Reporter allow two tools for report template development. While usage of Microsoft® Business Intelligence Studio® offers all the flexibility of the underlying technology, the usage of the OpenLAB ECM Intelligent Report Template Editor (RTE) is not only limited to expert users, but advanced report templates can easily be generated with the help of drag and drop functions.
The Report Template Editor (RTE) offers huge flexibility in respect to the data items that can be displayed on a report. However, the price of offering this flexibility and ease-to-use concept is the performance of report generation on large OpenLAB ECM databases.

Temporary Solution:

The article
http://www.chem.agilent.com/Library/usercontributedsoftware/Public/performance%20tuning%20of%20intelligent%20reporter%20templates.pdf
describes new possibilities to do performance tuning RTE generated templates using a simple text editor like Microsoft® Notepad.

Fix Information:

Report templates generated with the template editor of revision A.02.05 automatically add the injection time range optimization described in the mentioned article. To take advantage of the performance improvements templates generated with earlier versions of this software can be updated by grouping all report items and saving the template as a composite group.  This composite group can be added to new a template initiated from revision A.02.05.

Keyword: Help

One-line Description:

ACAML Database 1.1 -> 1.2 Migration Issue: Purity, 3PointPurity will be lost.

Problem:

In ACAML 1.1 the Purity (COMPOUND_PURITY)  and ThreePointPurity(COMPOUND_THREEPOINTPURITY), 
 both columns are located under an injection compound. In ACAML 1.2 these columns are moved down to the peak level (PEAK_PURITY and PEAK_THREEPOINTPURITY). 
Since each injection compound can have multiple peaks assigned and it is unpredictable, to which peaks these values have to be assigned during migration. So, to avoid invalid assignment by a "guess approach", these both values would not be copied.

Temporary Solution:

N/A

Fix Information:

Note is added in Designer manual on page no 12 at section “Peak purity”

Keyword: Installation

One-line Description:

Sync Service update: Installation of ECM API and Report Server Extensions fails

Problem:

When an existing installation of the Sync Service is updated by a newer package, the installer deletes the ECM API and Report Server Extensions, but doesn't install it again with the new version. If the current Sync Service package is deinstalled first, the installation of the new version will succeed.

Temporary Solution:

Uninstall the Sync Service before installing a newer version.

Fix Information:

n/a

Keyword: Installation

One-line Description:

Installing OLIR on ECM 3.3.2 replaces the ECM 3.3.2 help, ECM client IQ fails

Problem:

n/a

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Installation

One-line Description:

Service Configuration error caused by long password or account names

Problem:

The following error message has been reported from OpenLAB Intelligence Reporter rev. A.01.01 as well as rev. A.02.01 systems, in combination with an Oracle 10g database:

The Synchronization Service test or ECM logon failes with 
ORA-6502: PL/SQL numeric or value error: character string buffer too small

The error is caused by a long account names and/or long user group names in an active directory environment. 
Users with shorter account names with no spaces did not show the same error.

Temporary Solution:

n/a

Fix Information:

The issue is potentially caused by NT group names > 100 chars.
With rev. A.02.01 SP1 the NT group name can be handled up to 300 chars long.
A Hot Fix #5 for rev. A.01.01 is available, too.

Keyword: Installation

One-line Description:

Error during installation: "Cannot connect to the datasource AcamlDB"

Problem:

During installation, in the Synchronization Service configuration application, after setting database information and the reporting services virtual directory, the test for the report server might fail with a message indicating it cannot connect to the datasource "AcamlDB".

Temporary Solution:

n/a

Fix Information:

The error occurs because the firewall software on the database server is blocking connections to the database system.

You need to consult the documentation for your database system how to configure the firewall for inbound connections.

For example, when Microsoft windows firewall is used, for SQL Server 2005, consider adding a firewall rule for the sqlservr.exe program, e.g. %PROGRAM FILES%\Microsoft SQL Server\MSSQL.1\Binn\sqlservr.exe. 

For Oracle, add a rule to open port 1521.

You should consider restricting the source address range to the subnet used by your system's servers and designer clients.

Keyword: Installation

One-line Description:

Rev. A.01.01 Database migration will fail when executed from A.02.01 SP1 CD

Problem:

The database migration of a OpenLAB Intelligence Reporter revision update
from rev. A.01.01 to A.02.01 SP1 will fail if executed with the script set
provided with the rev. A.02.01 SP1 installation media.

The A.01.01 to A.02.01 migration scripts refer to scripts in the installation 
folder that had been updated to rev. A.02.01 SP1.
When executing the script the A.02.01 SP1 revision information is written
to the database. As a consequence the A.02.01 to A.02.01 SP1 migration will not start, as the revision information is already set to SP1.

Temporary Solution:

n/a

Fix Information:

Please use the A.01.01 to A.02.01 migration scripts form the A.02.01 installation media.

Keyword: Installation

One-line Description:

Database IQ tool ignores instance name selection

Problem:

The database IQ tool asks the operator to enter a DB instance name when connecting to a SQL server database.
Due to a defect in the software, this selection is ignored and in case of multiple instances the IQ tool connects to the default instance.
If no instance name is entered it also connects to the default instance.

Temporary Solution:

n/a

Fix Information:

The ECM 3.4.1 installation does no longer support the setup of multiple ECM instances and the DB IQ of OpenLAB ECM Intelligent Reporter does no longer allow selecting a DB instance.

Keyword: Installation

One-line Description:

Software installation media does not provide OpenLAB Shared Services installation

Problem:

The OpenLAB ECM Intelligent Reporter installation media does not provide installation files for the required  OpenLAB Shared Services.
The installation files are provided along with the OpenLAB CDS installation media.

In cases where OpenLAB ECM Intelligent Reporter is going to be installed in a pure ChemStation B.04.03  or Waters Empower environment, the installation media for OpenLAB Shared Services is missing.

Temporary Solution:

n/a

Fix Information:

Please contact support for a free OpenLAB Shared Services installation DVD.

Keyword: Installation

One-line Description:

Database creation fails in case of missing write permissions

Problem:

On certain occasions the creation of SQL server database files fails with error message:
Msg 5133, Level 16, State 1, Server , Line 2
Directory lookup for the file "D:\ECM\ECMDatabase\ACAMLtables\ACAML_DATA.ndf" failed with the operating system error 5(Access is denied.)

This might be cause by missing priviledges of user NETWORK SERVICE on the installation directory,

Temporary Solution:

N/A

Fix Information:

Add user NETWORK SERVICE with write permission to the installation folder users group.

Keyword: Installation

One-line Description:

OpenLAB ECM Intelligent Reporter rev. A.02.04 Database IQ fails with warning

Problem:

The A.02.04 Database IQ fails with warnings if ECM Intelligent Report gets installed on top of ECM 3.4.1 SP1 with HF7 or higher. 
ECM 3.4.1 HF7 introduces a minor change of the database field properties of the file_name field. 

The following warnings are expected and tolerated:

Warning: View 'COLUMNS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'COLUMNSBYINSTRUMENT' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'COMPOUNDS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'COMPOUNDSANDPEAKS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'COMPOUNDSBYINJECTIONS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'COMPOUNDSBYINSTRUMENTS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'COMPOUNDSBYPEAKS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'INJECTIONS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'INSTRUMENTMODULES' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'INSTRUMENTS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'METHODS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'SAMPLES' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'SEQUENCEINJECTIONS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'SEQUENCES' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'SIGNALS' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'STUDIES' column 'FILE_NAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'VB_DBFILESINVENTORY' column 'ECM_FILENAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'VB_FILES' column 'ECM_FILENAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'VB_FILES_PS' column 'ECM_FILENAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'VB_INJCOMPOUND' column 'ECM_FILENAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'VB_INJECTION' column 'ECM_FILENAME' nullable mismatch - reference: 'False' / current: 'True'.
Warning: View 'VB_SIGNALIMPORTFAILED' column 'ECM_FILENAME' nullable mismatch - reference: 'False' / current: 'True'.

Temporary Solution:

Print a copy of the KPR article and attach it to the Installation Qualification protocol.

Fix Information:

This defect is planned to be fixed in the next minor release.

Keyword: OL FT Services

One-line Description:

Certain GC signals cannot be reported with Intelligent Reporter rev. A.02.01

Problem:

It has been found that certain Agilent GC 7890 signals, like TCD, TST,FID3 or FID4 cannot be extracted with the signal data reader of revision A.02.01.
As a consequence the chromatograms cannot be displayed on the report.

Temporary Solution:

N/A

Fix Information:

This defect is fixed with revision A.02.01 Service Pack 1.

Keyword: OL FT Services

One-line Description:

Slow data synchronization of OpenLAB CDS EZChrom Data and OpenLAB ICM data

Problem:

The synchronization of OpenLAB EZChrom signal data with Intelligent Reporter database tables may take a considerable amount of time, dependent  on various conditions:
- software revisions in use
- amount of data to be synchronized, increasing with 
     - number of runs per sequence 
     - number of signals per run
     - run time 
     - detector sampling rate
-  data selected for extraction and reporting: 
    -  results only vs. 
    -  results and chromatograms vs.
   -   results, chromatograms and spectra
- File transfer server or Database server performance:
       In case of synchronizing chromatography raw data, the write 
        processes on the server hard disks may become the rate determining step

Overall, potential performance get multiplied by the number of result versions/ reprocessing cycles, as chromatography raw data gets synchronized and stored multiple times.

Temporary Solution:

Reduce the amount of data to be synchronized, by
   - cutting large sequences into smaller units, if suitable
   - reduce the number of detector signals,  if suitable
   - reduce the detector sampling rate,  if suitable
   - consider usage of intelligent reporting of OpenLAB CDS for single run and 
     single sequence summary reports in combination with using OpenLAB Intelligent Reporter 
     results and chart reporting only.
If the server hardware is suspected as the limiting factor:
  File transfer server:   
   - consider adding an additional fast harddisk and move the Windows \temp directory to this new directory
  Database server:   
   - consider adding additional fast, mirrored harddisks and move the ACAML signal data file to these new drives
   - move transaction log files to separate drives
   - perform regular database maintenance: rebuilding indexes, reduce fragmentation, check database filling level, 
     archive data that is not needed permanently

Fix Information:

The extraction of 3D-signal data got significantly improved by a new signal reader component introduced OpenLAB ECM Intelligent Reporter rev. A.02.02. The performance increase is in the magnitude of factor 10.
Rev. A.02.01 Hotfix 09 applies this component to rev. A.02.01 systems.

This defect is fixed in OpenLAB ECM Intelligent Reporter rev. A.02.02.

Keyword: OL FT Services

One-line Description:

Chromatograms are not shown correctly in case of added or overwritten injections

Problem:

The following defect affects 

OpenLAB ECM Intelligent Reporter rev. A.02.03 in combination with OpenLAB CDS EZChrom
and
OpenLAB Intelligence Reporter rev. A.02.01 SP1 with Hotfix7:

In cases where injection got added to a higher ECM version of a result set 
(e.g. after resuming a partial sequence acquisition) or in cases where an injection 
gets repeated with overwriting the previously acquired raw data file, the 
chromatograms do not appear correctly on the Intelligent Report.
In the first case, the added chromatograms are not shown at all, in the latter 
case, the chromatogram of the original injection is shown for higher ECM file versions.

Temporary Solution:

Do not use partial sequence acquisition and overwriting of raw data in combination with OpenLAB ECM Intelligent Reporter.

Fix Information:

This defect is fixed in OpenLAB ECM Intelligent Reporter A.02.04, A.02.03 HF3 and A.02.01 HF9,
respectively, and needs applied to all systems using OpenLAB CDS EZChrom or 
OpenLAB ICM.

Note: Additional hash sum calculations on the raw data file will cause higher processing
times of the Synchronization queue on the ECM File transfer server.

Keyword: OpenLAB ECM

One-line Description:

Renaming of an LCDF Path is not propagated to the Reporting Defaults

Problem:

Renaming a location, cabinet, drawer or folder in an ECM LCDF path is not reflected in the Reporting Defaults folders, even after a Refresh.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: OpenLAB ECM

One-line Description:

PDF Report name is limited to 111 characters

Problem:

Printing a report to PDF causes an application error if the PDF file name contains 111 or more characters. The file could not be uploaded to the ECM system.

The following error message is shown:
Unable to upload .  Cannot upload file with name exceeding 111 characters (error -999).
ECMCode = -999
ECMMessage = Unable to upload .  Cannot upload file with name exceeding 111 characters (error -999).

Temporary Solution:

Do not exceed the 111 character limit for PDF reports.

Fix Information:

There is currently no fix planned.

Keyword: OpenLAB ICM

One-line Description:

OpenLAB ICM Residuals, Cal curve scale, ISTD Units, NormConc Units not reported

Problem:

OpenLAB ICM Residuals and Cal curve scale are not reported on. Units are reported for ESTD amounts, but not ISTD amounts or NormConc. As there is only one Unit field in OpenLAB ICM, but three different result values for ESTD, ISTD and NormConc, there will be only a unit string in reports when ESTD amount is calculated.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: OpenLAB ICM

One-line Description:

ACQ Method not present for OpenLAB ICM data files

Problem:

ChemStation provides information on the Aquisition Method in the field Injection_ACQmethodname and information on the Data Analysis Method in the field Injection_DAmethodname. OpenLAB ICM has one method for both acquisition and data analysis. The information on this method is provided in the field Injection_DAmethodname. Hence, the field Injection_ACQmethodname is not populated for OpenLAB ICM data. 

Users need to be aware that if OpenLAB ICM sequence data have been reprocessed with a method different from the initially used method, this is not reported on.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: OpenLAB ICM , Report Template Design

One-line Description:

Peak lables for undetected compounds data cannot be hidden

Problem:

In case of ACAML result files generated by OpenLAB ICM the peak lables for undetected compounds cannot be hidden.
The expected retention time and compound names are shown at the position where the compound peak is expected.

Temporary Solution:

The peak lables for peaks with no peak area or peak height can be suppressed by using the expression editor of the peak labelling function.

To show retention time of detected peaks only, use:
=iif(Peak_Area>0,Round(Peak_RetentionTime,3),"")

To show names of detected compounds only, use:
=iif(Peak_Area>0,Compound_Name,"")

Fix Information:

The defect is fixed in OpenLAB CDS EZChrom.
OpenLAB Intelligence Reporter A.02.01 HF09 provides a customised composite group including a single signal plot report component using the necessary filter conditions to suppress peak labels for undetected compounds.
The composite group can be used to develop new or rework existing templates.

Keyword: OpenLAB ICM , Report Templates

One-line Description:

ACAML result files generated by OpenLAB ICM contain wrong injection time and injection modification time stamp formats

Problem:

The following defect may impact users of OpenLAB Intelligence Reporter A.02.01 in combination with OpenLAB ICM. It affects all report templates generated with the Report Template Editor. Templates developed with Microsoft Business Intelligence studio are less likely impacted as the time stamp formats get defined during the report template development process.

ACAML result files generated by OpenLAB ICM contain wrong time stamp formats on data fields
  -   injection time and 
  -   injection modification time 

The time stamps are labeled as being UTC (coordinated universal time), but in fact they are local time stamps.

If the report template makes use of the UTC time stamp correction, which is the default setting for templates generated with the Report Template Editor, the affected time stamps get adopted to the local time zone, although it is not necessary in this case.

Example:
- The lab operates in time zone UTC-8 (US, Pacific Time)
- The injection was performed at 14:00 local time / 22:00 UTC
- The injection time gets saved as 14:00 UTC
- The report shows Injection time: 6:00 AM, due to the UTC correction

Temporary Solution:

A post-mortem repair of affected time stamps is not possible.
Therefor it is recommended to the change time stamp formatting in the report templates.

To change the time stamp formatting in the report template file (*.rdl):

1.	Open the RDL Template file with  a Text Editor (e.g. Notepad)

2.	Press Ctrl + F to open the FIND function

3.	Search for the String "System.TimeZone.CurrentTimeZone.ToLocalTime"

4.	If the search identifies an expression verify that the time stamp appears with a wrong local time on the report. 
                     (if expression contains INJECTION_ACQUIREDDATE.Value or INJECTION_LASTMODIFIEDDATE.Value)
                     If yes, continue with step 5. Else, continue with step 6.

5.	Delete the string from the expression 

Before:
=System.TimeZone.CurrentTimeZone.ToLocalTime(First(Fields!INJECTION_ACQUIREDDATE.Value))
After:
=(First(Fields!INJECTION_ACQUIREDDATE.Value))

6.	Press F3 to find the next string "System.TimeZone.CurrentTimeZone.ToLocalTime"

7.	If no further hit is found continue with step 8. Else, proceed with step 4.

8.	Save the changes to the RDL file.  Ensure that the file type of the save dialog is set to All Files (*.*)

This procedure needs to be repeated on all affected report templates.

Fix Information:

Hotfix OLIR_A.02.01_HF10 introduces customized report items and updated built-in snippets that suppress the UTC/Local time conversion.
Using the customized composite groups and updated snippets, ensures the correct display of injection and modification time stamps for data acquired with OpenLAB ICM.

Note: Report Templates generated on such an updated Reporter Client should not be used for OpenLAB CDS EZChrom or ChemStation data. The formatting of the affected time stamps need to be re-adjusted before usage.

Keyword: Report Template Design

One-line Description:

ChemStation and ChemStore DiagnosticData xml field have different names

Problem:

The DiagnosticData xml field in ACAML DB has different names for the various (name,value) CustomField elements depending on which application generated the ACAML file. 

For example, the ACAML files created by the ACAML generator from data stored in ChemStore have names like "BegPumpPres" or "EndPumpPres". The same values are named "StartPressure" and "StopPressure" when the ACAML file was created by the ChemStation ACAML generator. Template Designers need to be aware of this when using data from the DiagnosticData xml field in the creation of report templates.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Report Template Design

One-line Description:

SQL Server: COLLATE suffix automatically appended to text attributes

Problem:

On an OpenLAB installation with a Microsoft SQL Server database, in some instances in Microsoft BI Studio query designer "COLLATE" suffixes are automatically appended to text type attributes. This in turn automatically creates "Exprx" alias names for the attributes which may invalidate the name settings in the report template.

Temporary Solution:

In Microsoft BI Studio, on the "Data" tab, use the option "Generic Query Designer".

Fix Information:

This problem is fixed by hotfix OLIR_A.01.01_HF01_SQLServer "Microsoft Query Designer adds COLLATE suffixes to report queries" The hotfix is available for customers to download from the Agilent Life Sciences and Chemical Analysis external web site (http://www.chem.agilent.com) at Home > Technical Support > Downloads and Utilities > Status Bulletins and Patches > OpenLAB Intelligence Reporter Software.

Keyword: Report Template Design

One-line Description:

Display the revision number of  the RDL template in the report

Problem:

Request to display the revision number of the RDL template used as field in the ACAML views, so that it can be displayed in the report.

Temporary Solution:

Template Designers should place a revision number in the Report Header if they need it.

Fix Information:

A "ReportTemplateRevision" report parameter is added to the report template, reflecting the ECM version number of the template.

Keyword: Report Template Design

One-line Description:

Query designer of BI Studio 2005 does not support SQL 2008

Problem:

When designing report templates with Microsoft BI Studio 2005, you may encounter problems if the database is SQL 2008.
I.e. creating a new dataset against a SQL server 2008 will fail with the error message “This server version is not supported. You must have Microsoft SQL Server 2005 Beta 2 or later.”

This is an known issue from Microsoft. Microsoft provides a patch for Visual Studio 2005 SP1 that allows to connect to SQL server 2008 “VS80sp1-KB954961-X86-INTL.exe” , downloadable from 
http://www.microsoft.com/DownLoads/en/details.aspx?FamilyID=e1109aef-1aa2-408d-aa0f-9df094f993bf&displaylang=en
Although this patch will not run on BI Studio 2005, it is only supporting the standard and above flavors of Visual Studio.

Temporary Solution:

Workaround 1: Install Standard Edition of Visual Studio 2005
Workaround 2: Do not use the generic query designer and edit the query manually like shown below:

SELECT  * 
FROM  ACAML.COMPOUNDSANDPEAKS
WHERE SEQUENCE_IDVER='THE GUID'

Note : The correct guid for the sequence(s) can be retrieved from the OLIR client

Fix Information:

This defect is fixed in rev. A.02.03

Keyword: Report Template Design

One-line Description:

Filter definition does not always allow usage of OR operators

Problem:

The usage of OR operators in report filter conditions is only allowed when combining several different report parameters to one filter expression.
In cases where a report parameter may fulfill multiple filter conditions (e.g. Instrument Name = Instrument A or Instrument B), the report template editor does not allow using an OR operator.

This is a limitation due to the definition of the operators available for filtering in report rendering (Microsoft Reporting Services). http://msdn.microsoft.com/en-us/library/ms154029(v=sql.90).aspx.  In particular, there is no "OR" at all.

Temporary Solution:

The exception is the "IN" operator, which allows a FilterExpression to be compared against a list of FilterValues. 
The desired filtering may also be achieved by using wildcards (*) in combination with a CONTAINS condition.
For number, the usage of > and < conditions could be used to achieve the desired filtering.

For external report parameters (e.g. filtering for multiple sample types) the following JOIN statement could be used in the expression editor of the filter:
[=Join(Report_Parameter_0, " ").Contains(Sample_Type   1)    = True]   =  "True"

Fix Information:

There is currently no fix possible.

Keyword: Report Template Design

One-line Description:

Unknown error when saving a report template

Problem:

Sporadically users may encounter error messages like "An error occurred saving the report template" and "The file was not found in the specified location" when saving a new report template to OpenLAB ECM.
Despite the error message the template is correctly saved in OpenLAB ECM.

This problem is caused by an internal ECM time-out.

Temporary Solution:

N/A

Fix Information:

This defect is considered to be fixed in a future release of OpenLAB ECM.

Keyword: Report Template Design

One-line Description:

Peak labels are hidden in case the peak apex exceed the response axis range

Problem:

In OpenLAB Intelligence Reporter A.02.01 the chromatogram's peak labels are hidden in case the peak apex exceed the response axis range.
This causes an inconvenience in identifying integrated peaks.

Temporary Solution:

In order to show all peak labels it is recommended to scale the response axis to highest or e.g. 2nd highest peak.
If additional information concerning the baseline construction should be shown, it is recommended to add a second chromatogram plot, scaled to the e.g. 10th largest peak.
Having an overview and detailed view of the chromatogram underneath each other offers advanced reviewing capabilities.

Fix Information:

The labeling of large, exceeding peaks has been add as a new feature to rev. A.02.03 of OpenLAB ECM Intelligent Reporter.
The functionality is also available after installing A.02.01 SP1 HF10.

Keyword: Report Template Design

One-line Description:

Reporting time format does not offer an option of (dd/mm/yyyy and time)

Problem:

The various time stamp formats offered by the Report Template Editor does not offer the combination of dd/mm/yyyy plus time stamp.

Temporary Solution:

The format of the time stamps can be modified by using Microsoft Business Intelligence Studio or simple a text editor, like Microsoft Notepad.

- open the report temaplte file (*.RDL)
- search the string "toString"
- Modify the following section like
      ToString("MM/dd/yyyy HH:mm:ss")
 to e.g.
     ToString("dd/mm/yyyy HH:mm:ss")

- save the RDL file and validate the changes.

Note:  The Report Template Editor cannot interpret the time stamp format correctly and will show an error filed in the editor window.  However, the time stamp format is correctly applied on the reports.

Fix Information:

RTE Support of the (dd/mm/yyyy and time) time stamp format is considered for a future relaese.

Keyword: Report Templates

One-line Description:

For reports with long lists, the printout/ pdf contains empty pages

Problem:

For reports containing long lists (e.g. a sequence list), the printout/ pdf of the report may contain empty pages.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: Report Templates

One-line Description:

MS SQL Server: report template PeaksAndCompounds_A4.rdl cannot be opened

Problem:

On an installation with a Microsoft SQL Server database, opening the report template PeaksAndCompounds_A4.rdl (to be found under \UCL Report Templates\SQLServer\General on the OpenLAB Intelligence Reporter Installation CD ROM) in the OpenLAB Intelligence Reporter Client results in an error message "An error has occurred during report processing. Query execution failed for data set 'Dataset 1'. Must declare the scalar variable "@SampleID"."

In the report template PeaksAndCompounds_A4.rdl (for MS SQL Server) the query parameter SampleID is not correctly referenced (with an initial "@"). It is referenced as ":SampleID", but should be "@SampleID".

Temporary Solution:

Open the report template PeaksAndCompounds_A4.rdl (for MS SQL Server) in an xml editor and exchange the statement "QueryParameter Name=":SampleID"" to "QueryParameter Name="@SampleID"".

Fix Information:

This defect is fixed in rev. A.02.01.

Keyword: Report Templates

One-line Description:

Column utilization report does not distinct injections

Problem:

The column and instrument utilization report templates or rev. A.02.01 and earlier do not always report correct numbers.
Under the following circumstances, individual injections get counted multiple times:
- branching of identical data sets across multiple ECM folders 
- ChemStation data acquired with a LC column selection valves counts 1 injection per for all installed columns

Temporary Solution:

- Avoid branching of results sets in ECM.
- Consider the impact of LC solvent selection valves on column utilization report results

Fix Information:

The column usage report templates of rev. A.02.02 defines injection counts based on instrument names, injection time and injection operator.
LC column selection valves operated with ChemStation B.04.03 or higher flag the column in use and provide this information to OpenLAB Intelligent reporter.

Keyword: Report Templates

One-line Description:

Customized chromatogram or axis lables may not display correclty

Problem:

The correct syntax for using the and "&" function requires a blank space in front and behind the ampersand sign.
Example: An expression like 
=FieldName&”Response” needs to be written like 
=FieldName & ”Response”
if it is used as a label in a chromatogram plot.

Expressions like  =Str(FieldName)&”Response” are not supported in reporting service and it results in an  “#Error” in preview.

Temporary Solution:

Use a blank space in front and behind the ampersand sign.

Fix Information:

There is currently no fix planned.

Keyword: Report Templates

One-line Description:

OpenLAB ECM Intelligent Reporter Does not Save User Name and Machine Name in Report Template Audit Trail

Problem:

In the template audit trail for OpenLAB ECM Intelligent Reporter, modifications made to the template are recorded but the user name and machine name are blank.

Temporary Solution:

As changed tempaltes cannot be used for report printing, any report template needs to be saved to ECM by the editor.  The user name and upload machine can be traced back by reviewing the ECM audit trail.

Fix Information:

This defect is fixed in rev. A.02.05 of OpenLAB ECM Intelligent Reporter.

Keyword: SQL Server

One-line Description:

Rendering of large reports (>100 runs) causes a client time-out

Problem:

Rendering of large reports (e.g. > 100 runs) may take a significant amount of time and may even lead to a time out error on the Report Client.
The likelyhood increases with the age and size of the database  and decreases with the server power and level of server distribution.  See also KPR# 635.

SQL server Database sizing, monitoring and maintenance is a database administrator's task. However, there are application specific details that are worthwhile to monitor on a regular base.
The following articles are recommended readings. Ideally, way before experiencing performance problems.

- InstallationAndConfigurationGuide, Database maintenance

- The following article contains plenty of information how to find the bottleneck in SQL 2005 databases: http://technet.microsoft.com/en-us/library/cc966540.aspx
In the first place we can suspect the I/O system slowing down the system. Especially the write process on ACAML_signal.ndf needs special attention if the synchronization of chromatograms (and spectra) are selected in the synchronization service configuration.

- If the database is full, the tables and data files get extended over and over again. The process of file extension is time consuming and adds additional fragmentation to the database.
The DB fill level can be checked according to http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/d15a0e69-f40a-4ab1-96d6-fd6723c4c9b5

- Measure database fragmentation according to http://blog.sqlauthority.com/2010/01/12/sql-server-fragmentation-detect-fragmentation-and-eliminate-fragmentation/

- Monitor OLIR specific measures over time: http://knowledgecenter.scs.agilent.com/forum/viewtopic.php?f=8&t=338&sid=761bbbf7d55a27534ee709b6c62253ad

- Rebuild table indexes on a regular base

Temporary Solution:

n/a

Fix Information:

The product release A.02.04 and the Hot Fix releases A.02.01 HF08, A.02.02 HF01 and A.02.01 HF01 introduce new tools that offer additional data retention management possibilities.
These tools do not make use of the ECM archiving process and also include possibilities to re-synchronize data on a ECM folder or even single file level.

The usage of the tools is recommended for all SQL server hosted ECM databases with OpenLAB ECM Intelligent Reporter.
A tech note describes how to do additional performance tuning on larger systems:
http://www.chem.agilent.com/Library/usercontributedsoftware/Public/performance%20tuning%20of%20intelligent%20reporter%20templates.pdf