Software Status Bulletin

Bioanalyzer     

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

KPR#:506404 Security Pack - Archiving of files "in use"
KPR#:702523 Security Pack - Inability to De-archive Archived Data
KPR#:1084332 Security Pack - 2100 Guest can change password

Keyword: Backup and Restore

KPR#:149 Migration of the Secured Area does not include "Users & Roles" information

Keyword: Compliance,Logbook

KPR#:506427 Security Pack - Comments entered into "Signature" dialog are overwritten in the logbook
KPR#:506439 Security Pack - No audit logging if finalized data is printed as report
KPR#:506449 Security Pack - Failed logon attempts during startup not found in logbook
KPR#:551016 Previous SystemFileLogs Viewer not updating correctly
KPR#:798071 Audit Trail shows error after migration of Secured Area
KPR#:1246522 Time stamps in log books now displayed in UTC

Keyword: Data Acquisition

KPR#:506416 Issue with error handling: "Error 559 - Optical Signal too high (1605h)"

Keyword: Data Evaluation

KPR#:157 Manual integration button is greyed out (DNA or Protein assay)
KPR#:175 Risk of data file corruption related to extensive audit trail size and manual integration of peaks.
KPR#:506417 "Manual Integration" feature not working as intended in version B.02.10
KPR#:506418 Security Pack - "Manual Integration" remains enabled after data was finalized
KPR#:506429 Security Pack - Approval drop-down selection list not scaling in "Chip Summary" table
KPR#:615118 Incorrect information in General Analysis Settings of High Sensitivity Protein 250 Assay
KPR#:957348 Limited functionality of right-click pop-up menus in B.02.12 SW revision
KPR#:964063 RNA fragments cannot be deleted in B.02.12 SW revision
KPR#:1088442 Manual Integration can also be used in All Samples view
KPR#:1155169 rRNA fragments can be deleted
KPR#:1155171 Only one border of a fragment or region can be modified at a time
KPR#:1155476 Result flagging occasionally reverts back

Keyword: Data Handling (import & export

KPR#:156 Risk of truncated file names after export into CDF format
KPR#:164 RNA data export to CSV format might not contain section "Overall Results" (RIN) if a region was added (DV200)
KPR#:168 Additional character in log book time zone stamps after method import

Keyword: Logbook

KPR#:962789 Inserting USB creates System Log Book entry
KPR#:1206458 The system log files are incorrectly named and described in the 2100 Expert Software User's Guide

Keyword: Other

KPR#:506413 Two 2100 Expert SW entries in Programs/Apps & Features upon upgrade to B.02.10
KPR#:506433 Security Pack - Uninstallation can cause .NET Framework corruption
KPR#:1098949 Expert SW cannot be installed and/or used with a non-English OS

Keyword: Performance

KPR#:513487 Security Pack - Installation might take several minutes (B.02.11)
KPR#:962439 Gel image preview in lower panel flickers in full screen mode in B.02.12 SW revision

Keyword: Print Out

KPR#:150 Security Pack - Time stamp changes when exporting "Signature Log" or "Audit Trail" table as text file
KPR#:152 Security Pack - Column Header Mismatch when exporting "Signature Log" or "Audit Trail"
KPR#:154 Security Pack - "Previous System Logbook Viewer" - No export, find or print functionality
KPR#:170 Possibility of artifacts during PDF printing
KPR#:181 Copyright statement on PDF reports of the 2100 Expert Software
KPR#:487856 Error occurs when printing data reports in specific sequence
KPR#:506425 Security Pack - "Date modified" incorrect on intermediate versions and their respective PDF reports
KPR#:506428 Security Pack - Printed reports generated directly after workflow finalization are incorrect
KPR#:506431 Security Pack - Printed reports (PDF or HTML) can miss column headers in logbook section
KPR#:797592 Overall result can be cut off from pdf report of Verification files

Keyword: Usability

KPR#:155 Microsoft Windows monitor DPI scaling can cause user interface issues
KPR#:158 Software does not support high resolution
KPR#:163 Application can false indicate changes to a data file (pencil symbol)
KPR#:165 Result flagging after "Assay Import" requires user interface update
KPR#:166 Hardware Diagnostics: Electrode/Diode Test can fail if run as individual test
KPR#:167 2100 Expert application launch requires more than 2 minutes
KPR#:169 Usage of forbidden characters in sample names
KPR#:171 UTC timestamps are not corrected for summertime offsets
KPR#:172 Auxiliary installation of EMET fails on Windows 10 version 1709 or higher
KPR#:487813 Issues with other applications after uninstallation of 2100 Expert Software
KPR#:506410 Intermittent Runtime Errors
KPR#:506414 "Help" button not working in help menu dialogs
KPR#:506415 Security Pack - Cannot switch users/roles due to message "Changes are not saved by user [...]"
KPR#:506419 Security Pack - Some exports and image save dialogs do not allow to determine a file name
KPR#:506426 Instrument not reconnecting to COM-port automatically
KPR#:506432 Incompatibility of the 2100 Expert software with third party access management solutions.
KPR#:506440 Security Pack - Application fails to start with unexpected error 87
KPR#:506441 Software not able to start due to "Automation error"
KPR#:506446 Data preview in "Open File" context not working
KPR#:963531 Saving assay file from demo file can create empty file
KPR#:1045419 Migration of Secured Area will fail if Secured Area is too large
KPR#:1058573 Wrong information for display settings in System Help
KPR#:1073574 Changing AIA/ANDI/netCDF Interchange Format setting cannot be saved
KPR#:1094303 Changes to the Chip Summary of a run file cannot be saved occasionally
KPR#:1094642 Security Pack - Error message when closing Method file
KPR#:1119867 Export of the Result Tables is incorrect
KPR#:1138077 Scaling for single sample is defective
KPR#:1166976 Multiple entries cannot be copied and pasted into the Chip Summary simultaneously
KPR#:1300178 Change in 'Color' value formatting in Results Table Export

Keyword: User Interface

KPR#:506411 Security Pack: Aborted validation by the user can cause mouse pointer issue
KPR#:963627 Icons "Gel Color" and "Scaling Mode" missing in quick menu
KPR#:1155474 Region Type visible in Smear Regions setpoint menu

Keyword: Users Guide/On-Line Help

KPR#:151 Access to 2100 Expert Help is limited with active Security Pack for Windows 10 64-bit in version B.02.09

Keyword: Vulnerabilities

KPR#:153 2100 Expert Vulnerability: ActiveX
KPR#:159 2100 Expert Vulnerability: VB6 OLE
KPR#:160 2100 Expert Vulnerability: Known third party vulnerabilities
KPR#:161 2100 Expert Vulnerability: MSXML 4 Risk
KPR#:506442 Logbook comment can be used to execute any .exe file.
KPR#:587910 The release of B.02.12 changes the Active X controls. Other software might not work as expected anymore.

Keyword: Administration

One-line Description:

Security Pack - Archiving of files "in use"

Problem:

During the archiving procedure, the operator might encounter a message that not all files were archived. Normally all files that are still open in the "Data Context" of 2100 Expert software cannot be archived.

In addition, files that were opened during this session - but closed - can also not be archived in this session.

Temporary Solution:

Note down the files that could not be archived and restart the software. Repeat the archiving process for the unsuccessful files.

Fix Information:

This issue is fixed in B.02.12

Keyword: Administration

One-line Description:

Security Pack - Inability to De-archive Archived Data

Problem:

Data can be archived from the Secured Area. However, the de-archiving function does not work. It is not possible to move data from the right to the left side of the screen, and no action is triggered when the start button is pressed. This issue was first identified in the B.02.11 (SR1) version of the 2100 Expert Software.

Temporary Solution:

Data can be imported through the "Import - Export" function of the software. When importing data, the files are not moved as with archiving, but copied.

Fix Information:

This issue is fixed in B.02.12

Keyword: Administration

One-line Description:

Security Pack - 2100 Guest can change password

Problem:

The 2100 guest user can change the password for the user account when they are in the data context, although this should not be possible.

Temporary Solution:

N/A

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Backup and Restore

One-line Description:

Migration of the Secured Area does not include "Users & Roles" information

Problem:

Customers that have to migrate their Security Pack installation (or the Secured Area directory) between PCs, encounter an issue that their previous user and roles information was not migrated if using 2100 Expert Software B.02.08(SR3) or lower.

Temporary Solution:

An external tool is provided for customers that upgrade from B.02.08 to B.02.09 to export the Users & Roles information upfront. A migration note was created that describes the process in detail.

https://www.agilent.com/en/support/backup-migration-for-security-pack-g2949ca

Fix Information:

The defect was resolved with release of 2100 Expert Software version B.02.09. This is a defect that is related to the uninstallation process, hence customers upgrading from B.02.08 require the external tool as described in "Temporary Fix".

With B.02.09 or higher, a backup of "User & Roles" settings is created automatically upon uninstallation of the software. By default in the directory "C:\SecuredArea.bak"

Keyword: Compliance,Logbook

One-line Description:

Security Pack - Comments entered into "Signature" dialog are overwritten in the logbook

Problem:

Users can currently provide comments along with their electronic signatures during a "Workflow" approval.
Due to the design of the software, the user provided comments are overwritten by hyperlinks to a PDF report of the data file for the just signed workflow level.

This can be reviewed in the data file "Logbook" under the subtype "Signatures" in column "Comments".

Temporary Solution:

After each workflow level approval, the user must also save the data file.
This will trigger the save dialogue and the user comments should also be copied into its comment filed, as these comments will be correctly transferred to the data file logbook.

Fix Information:

This issue is fixed in B.02.11 (SR1)

Keyword: Compliance,Logbook

One-line Description:

Security Pack - No audit logging if finalized data is printed as report

Problem:

It is not logged correctly in the audit trail when the operator creates a report from a finalized version of a data file.

Temporary Solution:

N/A

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Compliance,Logbook

One-line Description:

Security Pack - Failed logon attempts during startup not found in logbook

Problem:

During startup, the 2100 Expert software does not log failed logon attempts in the system logbook / audit trail. After a failed logon event, a warning message popup is displayed to the user.

Temporary Solution:

N/A

Fix Information:

2100 Expert utilizes windows authentication as user management (UAC). As consequence all logon attempts (pass or fail) are logged by the operating system and can be reviewed in the "Windows Event Viewer" under "Windows Log -> Security".

Keyword: Compliance,Logbook

One-line Description:

Previous SystemFileLogs Viewer not updating correctly

Problem:

When opening a SystemFileLogs file with the System Log Viewer, the file is not loaded. Only the file name in the navigation bar updates, but not the actual log entries.

Temporary Solution:

Close the System Log Viewer and re-open it by clicking on "Open previous System Log Books", then the file gets correctly loaded.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Compliance,Logbook

One-line Description:

Audit Trail shows error after migration of Secured Area

Problem:

After migrating an existing Security Pack backup (SecuredArea.bak file) during the installation process of the Security Pack, the Audit Trail shows the error message "System File has been manipulated!".

Temporary Solution:

There is no fix as such. This error message is to be expected, as technical information is merged in the System File during the migration process. 

Fix Information:

N/A

Keyword: Compliance,Logbook

One-line Description:

Time stamps in log books now displayed in UTC

Problem:

Starting with version B.02.12, the time stamps in the software’s log books (System Log Book and Data File Log Book) are displayed in Coordinated Universal Time (UTC). 
In previous versions, time stamps were displayed in local time.

Temporary Solution:

The change to UTC time stamps aligns with ISO 8601 standards, as required by unified compliance guidelines for audit trails.
The local time zone is displayed in a neighboring column as a reference.

Fix Information:

N/A

Keyword: Data Acquisition

One-line Description:

Issue with error handling: "Error 559 - Optical Signal too high (1605h)"

Problem:

If the detector system of the 2100 Bioanalyzer reaches a certain fluorescence threshold, an error is reported by the firmware (code 1605h).
This firmware warning is incorrectly classified as "Error" within the data analysis software and is rather considered to be of type "Information".

Temporary Solution:

N/A

Fix Information:

N/A

Keyword: Data Evaluation

One-line Description:

Manual integration button is greyed out (DNA or Protein assay)

Problem:

In rare circumstances, manual integration may not be possible for an individual data file that was not finalized correctly and thus manual integration remains deactivated.
The collected data is correct but an internal process has not finished on time.

Temporary Solution:

None

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Data Evaluation

One-line Description:

Risk of data file corruption related to extensive audit trail size and manual integration of peaks.

Problem:

The 2100 Expert software B.02.08(SR3) was found to be unstable handling data files with large audit trails, typically caused by manual integration of many samples or peaks. With active Security Pack, all data points were stored in the audit trail with each implemented change to the data file itself.

Error message 0x8004043C occurs in combination with corrupt data files (0kb). The data cannot be recovered from the corrupt files.

Temporary Solution:

A temporary fix was implemented with version B.02.09. In case a data file was corrupted, the software would create a temporary backup file of the previous version and display a meaningful message to the operator. The operator was requested to immediately secure the temporary backup file.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Data Evaluation

One-line Description:

"Manual Integration" feature not working as intended in version B.02.10

Problem:

Changes implemented with 2100 Expert Software Version B.02.10 have resulted in reports of "jumping peaks" when using the "Manual Integration" feature.

Peak start and end points for adjacent peaks cannot overlap as this may result in a mix up of already existing and manually integrated peaks.

Temporary Solution:

As a work-around, when using "Manual Integration" users should prevent integration start or end points that are placed on the same data point or overlap. To accomplish this task, it is recommended to activate "View Datapoints" in the menu bar for electropherograms.

Fix Information:

This issue is fixed in B.02.11 (SR1)

Keyword: Data Evaluation

One-line Description:

Security Pack - "Manual Integration" remains enabled after data was finalized

Problem:

The feature "Manual Integration" remains active even after the data file was finalized in the workflow.
Both "Standard" and "Advanced Operator" can make modifications to the peak start and end points.

Action of change is logged in the audit trail with date and time. However, the values for peak time are not correctly logged in the audit trail details.

Temporary Solution:

N/A

Fix Information:

This issue is fixed in B.02.12

Keyword: Data Evaluation

One-line Description:

Security Pack - Approval drop-down selection list not scaling in "Chip Summary" table

Problem:

The approval selection overlay is incorrectly displayed if the screen resolution is not at 1024 x 768 pixel.
Every other resolution will tear this specific pop-up field and expand it incorrectly in Y-axis direction across the screen.

With a typical (and maximal specified screen resolution) of 1920 x 1200 pixels, the selection list item text is not visible to the end user.

Temporary Solution:

Sample approval can also be done directly from the respective sample electropherogram.
Alternatively, the 2100 Expert software application window size must be decreased to 1024 x 768 pixel.

Fix Information:

This issue is fixed in B.02.12

Keyword: Data Evaluation

One-line Description:

Incorrect information in General Analysis Settings of High Sensitivity Protein 250 Assay

Problem:

The General Analysis Settings for the High Sensitivity Protein 250 Assay state that the lower marker is used for quantification. This is incorrect. The ladder is used for quantification in the High Sensitivity Protein 250 Assay.
The General Analysis Settings can be found in the Assay Properties tab of a data file and in the PDF report if Assay Details is selected in the printing menu.

Temporary Solution:

N/A

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Data Evaluation

One-line Description:

Limited functionality of right-click pop-up menus in B.02.12 SW revision

Problem:

Some features missing or non functional when using right-click pop-up menus.
These features include:
- Manually Set Lower Marker
- Manually Set Upper Marker
- Exclude Peak
- Scale to Selected Peak
- Calibrate Protein

Temporary Solution:

None

Fix Information:

This issue is fixed in B.02.12 (SR1)

Keyword: Data Evaluation

One-line Description:

RNA fragments cannot be deleted in B.02.12 SW revision

Problem:

Deletion of RNA fragments is not possible using
- right-click pop-up menu
- fragment table below electropherogram
- fragment table in setpoints explorer.
There is no workaround to delete RNA fragments in B.02.12 revision.

Temporary Solution:

None

Fix Information:

This issue is fixed in B.02.12 (SR1)

Keyword: Data Evaluation

One-line Description:

Manual Integration can also be used in All Samples view

Problem:

The Manual Integration can also be used in the ‘All Samples’ view. However, it is not intended to be used in this view and could potentially cause a software crash.

Temporary Solution:

Do not use Manual Integration in All Samples view. Only use it in single sample view.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Data Evaluation

One-line Description:

rRNA fragments can be deleted

Problem:

When a fragment is added in the All Samples view of a total RNA file and then directly deleted, all rRNA fragments are deleted.

Temporary Solution:

Avoid adding and directly deleting a fragment.
Pressing Default in the setpoints menu will bring back the original rRNA fragments that are automatically added by the software but will also revert all previously made custom settings.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Data Evaluation

One-line Description:

Only one border of a fragment or region can be modified at a time

Problem:

When the start and end points of a fragment or region are modified simultaneously, only the first point will be successfully changed; the other retains the old value.

Temporary Solution:

Modify one border at a time.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Data Evaluation

One-line Description:

Result flagging occasionally reverts back

Problem:

After successfully changing the result flagging, it sometimes reverts back to old values. Although the result flagging tab shows the new values, they cannot be applied again as they have already been applied.

Temporary Solution:

Make any change in the Result Flagging and apply. Revert the change and apply again.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Data Handling (import & export

One-line Description:

Risk of truncated file names after export into CDF format

Problem:

The export script for CDF files may truncate the file name at the first occurrence of a "." dot character.
This may lead to truncation of longer file names in CDF exported files. This also applies to automatic export functionality.

Temporary Solution:

Do not use a dot (".") as a character in the data file name.

Fix Information:

This issue is fixed in B.02.10.

Keyword: Data Handling (import & export

One-line Description:

RNA data export to CSV format might not contain section "Overall Results" (RIN)  if a region was added (DV200)

Problem:

If a region is added to an RNA assay file and smear analysis is active within the "SetPoint Explorer", the export of data into CSV format does not contain the section "Overall Results", which typically contains the RIN value for the sample.

Temporary Solution:

none

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Data Handling (import & export

One-line Description:

Additional character in log book time zone stamps after method import

Problem:

In few cases the time zone information in a log book entry (System, Signature, Audit) can contain an additional character after a method file has been imported.

A normal time zone like ( - 7:00 GMT) would be displayed as ( - - 7:00 GMT) with a double offset character.

Temporary Solution:

none

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Logbook

One-line Description:

Inserting USB creates System Log Book entry

Problem:

Inserting a USB stick causes the software to incorrectly detect an instrument connection. It logs the error message: "Instrument error occurred. Error occurred while reading from COM port" in the System Log Book.

Temporary Solution:

N/A

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Logbook

One-line Description:

The system log files are incorrectly named and described in the 2100 Expert Software User's Guide

Problem:

In the 2100 Expert Software User's Guide on page 223 the system log files are incorrectly named and described. The guide incorrectly states that the system log book is saved in SystemFile.xml and refers to the log file as SystemLogs.xml. The correct file name and location differ based on the installation type.

Temporary Solution:

a.	For non-Security Pack installations, the system log book is saved at: config/SystemFileLogs.xml 
b.	For Security Pack installations, the system log book is saved at: SecuredArea/System/SystemFileLogs.xml

In general, it is recommended to back up your data on a regular basis, like described in the 2100 Expert Software User's Guide on page 168. The system log files should be included in this backup.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Other

One-line Description:

Two 2100 Expert SW entries in Programs/Apps & Features upon upgrade to B.02.10

Problem:

When the 2100 Expert SW is upgraded to B.02.10, two 2100 Expert SW entries in the Programs/Apps & Features are present (older and newer revision of the SW). Only the newer SW revision can be uninstalled. The older revision can't be removed from the list, because it is not physically there anymore. 

Temporary Solution:

N/A

Fix Information:

This was fixed in B.02.11(SR1) revision

Keyword: Other

One-line Description:

Security Pack - Uninstallation can cause .NET Framework corruption

Problem:

A known problem exists in version B.02.10 that can occur after uninstallation of the 2100 Expert software with Security Pack.
During the uninstallation, a mandatory .NET Framework file can be deleted or corrupted.
As a consequence, third party software that requires .NET Framework might not function correctly any longer.
It was reported that this issue can result in "Unexpected Termination" error of such software.

Temporary Solution:

o Copy the "machine.config" file from the x64 directory:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config

o Create a backup of the existing file (x86), then replace by above copied file:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config

Fix Information:

This issue is fixed in B.02.11 (SR1)

Keyword: Other

One-line Description:

Expert SW cannot be installed and/or used with a non-English OS

Problem:

If the Install Language of the Windows Operation System is not English (United States), the 2100 Expert software cannot be installed and/or used correctly. For example, when attempting to install the software on a system with a non-English Install Language the Command Prompt might run into an infinite loop during installation. 

Temporary Solution:

Agilent only supports an installation on a Windows Operation System with English (United States) as Install Language.

Fix Information:

N/A

Keyword: Performance

One-line Description:

Security Pack - Installation might take several minutes (B.02.11)

Problem:

With version B.02.11 of the 2100 Expert software, a new mechanism was introduced that is modifying filesystem based permissions for the generic 2100  System user profile.

As a consequence Windows/Temp security settings are modified during installation. This step can take several minutes depending on this directory size.

Temporary Solution:

Consider to reduce the Windows "Temp" directory size before attempting to install the Security Pack license key.

Fix Information:

N/A

Keyword: Performance

One-line Description:

Gel image preview in lower panel flickers in full screen mode in B.02.12 SW revision

Problem:

n/a

Temporary Solution:

Exit full screen mode and enlarge SW window by dragging one of its corners.

Fix Information:

This issue is fixed in B.02.12 (SR1)

Keyword: Print Out

One-line Description:

Security Pack - Time stamp changes when exporting "Signature Log" or  "Audit Trail" table as text file

Problem:

When exporting a signature or audit trail table (by right click) to a text file, the time stamp is calculated with the time zone offset.  This can create a mismatch between the exported file and the on-screen time stamps in the logbooks.

Temporary Solution:

The temporary workaround is to only export the audit trail as HTML file. This will correct the time stamp but can cause a column header offset on older software revisions.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Print Out

One-line Description:

Security Pack - Column Header Mismatch when exporting "Signature Log" or "Audit Trail"

Problem:

When exporting a signature or audit trail table (by right click) to a text file, the time stamp is calculated with the time zone offset.  This can create a mismatch between the exported file and the on-screen time stamps in the logbooks.

Temporary Solution:

A temporary workaround is to export the audit trail as HTML file which will correct the time stamp but can cause a column header offset on older software revisions.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Print Out

One-line Description:

Security Pack - "Previous System Logbook Viewer" - No export, find or print functionality

Problem:

The 2100 Expert Software has a logbook that holds signatures and audit trailsin XML format (SystemFilesLogs.xml). Once the file size of the logbook becomes to big, it is saved with a timestamp as a so-called "previous system logbook".
These previous logbook files can be accessed via the 2100 Expert Software and will open in a separate windows.

Within the external pop-up window, the right-click menu items like "Print", "Find" and "Export" will open a subsequent input screen that cannot be edited by the user.

Temporary Solution:

none

Fix Information:

With 2100 Expert Software version B.02.10, the previous system file logbooks can be exported via the right click menu. The exported XML files can then be opened with a third party application like the Internet Explorer for searching and printing.

Keyword: Print Out

One-line Description:

Possibility of artifacts during PDF printing

Problem:

In very rare situations, exclusively when software errors occurred upfront, a generated PDF report can contain incorrect information merged from a second opened data file.

Temporary Solution:

Pay attention to software runtime error messages and contact the technical support team for assistance to clear general 2100 Expert software errors.

An alternative work-around would be to only have one data file opened during PDF printing.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Print Out

One-line Description:

Copyright statement on PDF reports of the 2100 Expert Software

Problem:

All print-outs and PDF reports contain a copyright statement on each page, preventing end-users to copy and reuse figures without permission.
Below is Agilent's response to any requests for permission to re-print PDF reports generated with the 2100 Expert Software.

Temporary Solution:

You have Agilent Technologies full permission to print and copy any PDF document generated with the 2100 Expert Software.
Consent for re-printing or copying only partial information (like figures) is conditioned upon including the source acknowledgement with each figure, with the year date being the year date shown on the original publication from which the figure was copied:

© Agilent Technologies <year date>
Reproduced with Permission, Courtesy of Agilent Technologies

Fix Information:

N/A

Keyword: Print Out

One-line Description:

Error occurs when printing data reports in specific sequence

Problem:

An issue has occurred that causes a specific error message while attempting to print a PDF report.
"Error -2147221504 (ifcFile.Samples.Exists(12=False)"

This error occurred if two different assays with different total available samples were run.
In a scenario where first a 12 sample assay (e.g. DNA1000), then a 11 sample assay (e.g. HS DNA1000), the software will not be able to print a report from the later data file.

Temporary Solution:

Close and re-load the problematic data file(s) before printing the reports.
Alternatively, you can stop the analysis with the "Stop" button and switch to the "Gel View". Afterwards re-activate the analysis to be able to print the selected data report.

Fix Information:

This issue is fixed in B.02.12 SW revision

Keyword: Print Out

One-line Description:

Security Pack - "Date modified" incorrect on intermediate versions and their respective PDF reports

Problem:

When more than one version of a data file exists, as soon as a new version is created, all previous versions do not display the correct “date modified” in the chip summary when the version is re-loaded and subsequently printed to PDF.

The issue originates from an incorrect “indexing” of timestamps in a hidden table. This only occurs once a new version of a data file is present. The correct date modified can always be seen from the latest version of the data (.XAD) file.

The timestamps for signatures in the PDF report generated from the latest version will be correct, including the signature logbook timestamps.
This issue does not have any impact on the raw data or acquired data from the instrument.

Temporary Solution:

Only create PDF reports from the latest version available.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Print Out

One-line Description:

Security Pack - Printed reports generated directly after workflow finalization are incorrect

Problem:

When a report (PDF / HTML) is manually and directly printed after the last workflow step was finalized, the report contains incomplete audit trail and signature log information. The last actions of data file finalization are not yet transmitted into the data file log book.

Automatically generated PDF reports after signing off a workflow level also do not contain the latest signatures in the report.

Temporary Solution:

Load the "Log book" once after finalization of the workflow and before printing a report manually to force log book entry transmission.

Alternatively, the data file can be closed and re-opened before printing a report after finalization of the data.

Fix Information:

This issue is fixed in B.02.11 (SR1)

Keyword: Print Out

One-line Description:

Security Pack - Printed reports (PDF or HTML) can miss column headers in logbook section

Problem:

If a PDF or HTML report is not directly generated while the logbook is selected, the print-out might miss column headers for run log, signature log or audit trail information.

Temporary Solution:

Any PDF or HTML reports must be printed from the 2100 Expert software while the logbook is selected and displayed.

Fix Information:

This issue is fixed in B.02.11 (SR1)

Keyword: Print Out

One-line Description:

Overall result can be cut off from pdf report of Verification files

Problem:

If the file name of a Verification file (.xvd) is too long, the overall result can be cut off from the pdf report.

Temporary Solution:

Do not add more characters to the file name of a verification file than suggested by default.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Microsoft Windows monitor DPI scaling can cause user interface issues

Problem:

Modern displays support high resolutions and often are set to 125% text zooming (DPI scaling).
The zooming can cause temporary user interface distortions within the 2100 Expert Software.

Temporary Solution:

Please reset DPI scaling / zoom within your operating system to "100%"

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Software does not support high resolution

Problem:

If the application window is enlarged to more than 1920*1200 pixels, the user interface might crash with diverse error messages.

Temporary Solution:

A warning message was implemented in version B.02.10 if wrong settings are detected at application launch.
Affected users should reduce the screen resolution to a supported ratio.

Alternatively, do not maximize the application window. Do not exceed window size of 1920*1200 pixels.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Application can false indicate changes to a data file (pencil symbol)

Problem:

The 2100 Expert software indicates unsaved changes to data files (for example changes of user input fields like "Sample Name") with a small pencil symbol in the tab overview.
The symbol should be removed once the data file has been saved or if the focus is switched to a second data file.

When switching between data files, the pencil symbol will remain displayed, while no changes were actually made to the second (active) data file.

Temporary Solution:

No direct action required. 
Data files are correctly saved by any save action (system or user), even if the pencil symbol is still displayed on a tab. In case the data was not yet saved, users will correctly be prompted to save the data before the application is closed.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Result flagging after "Assay Import" requires user interface update

Problem:

If assay set points are loaded into an existing data file, a situation can occur in which the result flagging rules are not immediately updated. This can result in the impression that colors and rule sets were not correctly applied to the data.

Temporary Solution:

Saving the data file and then updating the interface by switching to another tab will invoke an update the user interface and subsequently the correct result flagging will be displayed.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Hardware Diagnostics: Electrode/Diode Test can fail if run as individual test

Problem:

All 2100 Expert Software versions are affected.

Due to a software based initialization issue with the "Electrode/Diode Test", this test might fail with false negative results if it is run as individual test.

Temporary Solution:

As work-around please run at least the "HV Stability Test" upfront of the "Electrode/Diode Test", or run all hardware diagnostics tests in sequence.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

2100 Expert application launch requires more than 2 minutes

Problem:

In rare circumstances, the 2100 Expert Software requires several minutes to launch.
This issue may occur on computers that were connected to the Internet or Ethernet and subsequently taken offline. In such a scenario, the operating system attempts to contact an online service to verify 2100 Expert Software file certificates.

Temporary Solution:

As a work-around, the "Certificate Revocation Timeout" within the group policy settings should be adjusted to allow a faster timeout response for files that cannot be verified by the online services.

A dedicated support document is available from Agilent Support.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Usage of forbidden characters in sample names

Problem:

Forbidden characters in Sample name (e.g. " @ \ % , ...) can be entered as sample name using the Copy/Paste function.
Using such forbidden characters can result in diverse errors during your chip run.

Temporary Solution:

Do not copy or paste any forbidden characters into the "Sample Name" fields.

Fix Information:

This issue is fixed in B.02.10.

Keyword: Usability

One-line Description:

UTC timestamps are not corrected for summertime offsets

Problem:

We identified a general problem with the conversion from summertime to UTC within the 2100 Expert Software.
Data file timestamps are managed in UTC format software internally. Conversion from the local time into UTC might be incorrect if the operator is located in a time zone with active summertime offset.

Consequently, an incorrect offset in timestamps (also applies to timestamps in data file exports) is possible.

Temporary Solution:

None

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Auxiliary installation of EMET fails on Windows 10 version 1709 or higher

Problem:

During installation of the 2100 Expert Software, you will be asked to install the Microsoft tool "EMET" for mitigation against software vulnerabilities.

With the release of Windows 10 version 1709, the EMET tool was made obsolete by Microsoft and its functionality was embedded into the Microsoft Defender tool as "Exploit Guard".

This eventually leads to a warning message during 2100 Expert setup, that EMET cannot be installed on your system.

Temporary Solution:

n/a

Fix Information:

Ensure Microsoft Defender "Exploit Guard" is activated and update your Windows operating system to the most recent version.

Keyword: Usability

One-line Description:

Issues with other applications after uninstallation of 2100 Expert Software

Problem:

An issue was discovered with version B.02.11 related "Install Shield". Uninstallation of 2100 Expert can cause other applications , which are using .NET Framework as well, to fail. The symptoms can be diverse and range from "Unhandled Exception" errors to programs just not launching without any errors being displayed.

We are currently aware that this can affected Microsoft Office applications getting stuck in the loading screen. A temporary solution can be provided once the issues was discovered.

Temporary Solution:

As a work-around the missing .NET "machine.config" file, can be copied from the x64 directory:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config
   
and replace the corrupted or missing file in the x86 related directory:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config

Fix Information:

This issue is fixed in B.02.11 (SR1)

Keyword: Usability

One-line Description:

Intermittent Runtime Errors

Problem:

In rare circumstances, "Runtime Errors" may occur where a user issues multiple concurrent requests within the software. Due to the architecture of the 2100 Expert software, requests should be sequentially issued rather than in parallel.

Temporary Solution:

Allow more time between issuing software actions. Avoid issuing requests while the software is busy (refer to the status bar indicator).

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

"Help" button not working in help menu dialogs

Problem:

The link between the button "Help" in the help menu dialogs is not correctly linked with the embedded software help content. The button will remain inactive or no correct help pages will be launched.

Temporary Solution:

Open the software help content from the menu bar "Help" -> "Contents and Index".
In the help windows, navigate to the entry "License Administration Utility".

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Security Pack - Cannot switch users/roles due to message "Changes are not saved by user [...]"

Problem:

Operator cannot switch users or their roles due to unsaved changes.
This situation only occurs if the samples were approved in the "Chip Summary" overview tab and the operator also switched tabs (e.g. to "General Properties") before workflow approval.

Temporary Solution:

Insert or change the "Chip Comment" or any other field to invoke a "Save" action.
Alternatively, evaluate samples from the electropherogram tab instead of the chip summary tab.

Fix Information:

This issue is fixed in B.02.12

Keyword: Usability

One-line Description:

Security Pack - Some exports and image save dialogs do not allow to determine a file name

Problem:

When using the "Save Electropherogram" or the Export of the Chip Summary feature Security Pack users cannot determine or change the default file name. In the pop-up dialogue it is forbidden for the users to input any filename of choice.

Temporary Solution:

Users can paste in a file name from the clipboard.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Instrument not reconnecting to COM-port automatically

Problem:

With release of version B.02.10, some users reported problems with instruments not reconnecting automatically.
After a software restart, the correct and previous COM-ports should remain selected in the "Instrument context" menu.

A known issue prevents seamless reconnection to the instrument.

Temporary Solution:

Select the correct COM-Port for the instrument in the "Instrument context" menu.

Fix Information:

This issue is fixed in B.02.12

Keyword: Usability

One-line Description:

Incompatibility of the 2100 Expert software with third party access management solutions.

Problem:

The 2100 Expert software cannot be used in combination with Entra ID (formerly: Azure AD). The user will be prompted with the Error messages "Object variable or With block variable not set", "Application failed to load! Reason: No current role id available" and for B.02.12 (SR1) and newer "The specified account <account name> is not a user account. Entra ID is not supported. To resolve this issue, use local user accounts." when launching the software.

Temporary Solution:

The situation can be resolved by reinstalling the software from a local Administrator profile that was created on the specific PC Windows operating system.
Please do not use a domain embedded administrator profile to prevent this issue.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Security Pack - Application fails to start with unexpected error 87

Problem:

In rare situations the 2100 Expert software with Security Pack fails to start.
A specific error message is displayed to the users:
"Method failed with unexpected error code 87"

This problem is related to a corruption of printers in the PC and a script of 2100 Expert software to make all users printers available.
2100 Expert with Security Pack tries to copy specific registry keys from the currently logged on user to the generic software user (2100System).

Temporary Solution:

Please contact Agilent support for assistance if required.
You can temporary fix the situation by removing the printers from the operating system registry.

1. Browse to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers
2. There might be some printers starting with cryptic names (e.g. S-1-5-21-....).
3. Delete any of these cryptic printers & delete any of the printers referring to them.
4. Restart the computer.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Software not able to start due to "Automation error"

Problem:

Few users of version B.02.08 reported an issue when starting the application.
An error occurred with description: "Automation error - The remote procedure call failed".

Temporary Solution:

N/A

Fix Information:

This issue is fixed in B.02.09

Keyword: Usability

One-line Description:

Data preview in "Open File" context not working

Problem:

In version B.02.11 an issue was found that prevents display of preview data in the "Open File" dialog box.
In the past it was possible to preview the chip summary and the electropherogram data.

Temporary Solution:

Open the file to load its content.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Saving assay file from demo file can create empty file

Problem:

Saving an assay file (.xsy) from a demo file creates an empty file if the file name is not changed. The user is notified that a test file must be saved under a different name if a test file is to be created from a demo file.

Temporary Solution:

Make sure to change the file name when saving an assay file created from a demo file. The empty assay file can be deleted.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Migration of Secured Area will fail if Secured Area is too large

Problem:

When migrating an existing Security Pack backup (SecuredArea.bak file) during the installation process of the Security Pack, the migration can fail if the Secured Area is too large and contains too many files. User gets the error message: "Migration failed: Exception of type 'System.OutOfMemoryException' was thrown."

Temporary Solution:

Files can be migrated manually. Log in with a Windows user with local Admin rights. Copy all files in the SecuredArea.bak into the SecuredArea (path: C:\Program Files (x86)\Agilent\2100 bioanalyzer\2100 expert).
Note: Do not open the SecuredArea folder when copying files manually! Open the 2100 expert folder and copy the files to the SecuredArea folder using drag-and-drop.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Wrong information for display settings in System Help

Problem:

The 2100 Bioanalyzer System Help of the 2100 Expert software contains incorrect information on the display settings. 

Temporary Solution:

The correct information on the display settings can be found in the readme file of the 2100 Expert software:
Resolution of 1280 x 1024 pixels.
Settings exceeding 1890 x 1280 pixels are not supported.
Scaling of the size of text, apps and other items should be set to 100%.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Changing AIA/ANDI/netCDF Interchange Format setting cannot be saved

Problem:

Changing (activating or deactivating) the "AIA/ANDI/netCDF Interchange Format" in System Wide Settings > Auto Export cannot be saved. This defect is also present in earlier software versions.
If this setting is active, a .cdf file is created for each analyzed sample. Otherwise, this has no effect on any other function.

Temporary Solution:

A workaround exists when no Security Pack is installed: A change to the "AIA/ANDI/netCDF Interchange Format" setting can be saved if another setting is changed at the same time.
When Security Pack is installed, no workaround exists.

Fix Information:

This problem is being addressed in a future version.

Keyword: Usability

One-line Description:

Changes to the Chip Summary of a run file cannot be saved occasionally 

Problem:

Occasionally, the Save icon is grayed out after changes are made to the Chip Summary in a run file, preventing the changes from being saved.

Temporary Solution:

After making additional changes to another field in the Chip Summary, the file can be saved.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Security Pack - Error message when closing Method file

Problem:

Up to two error messages can show up when closing a Method file. This only happens very occasionally and the Method file closes after pressing OK. This error has no impact on the Method files or any other functionality of the software.

Temporary Solution:

N/A

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Export of the Result Tables is incorrect 

Problem:

When exporting the Result Tables of a data file into a .csv-file via the Export function, the generated file is not containing the correct information. This is true for the Auto Export and the manual export function via File > Export in the Data context.

Temporary Solution:

The data can be copied directly from the Peak Table of a sample to the clipboard, or a .csv file with the correct information of the individual sample can be created by right-clicking in the Peak Table.

Fix Information:

This issue is fixed in B.02.12 (SR2)

Keyword: Usability

One-line Description:

Scaling for single sample is defective

Problem:

When the Selected Scale is applied in single sample view, the EPG is scaled to the lower marker since version B.02.12. In previous versions, the EPG was scaled to the highest peak. For all RNA-assays, the function does not work. An error message is shown: "Failed to handle context menu selection. [...]".

Temporary Solution:

N/A

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Multiple entries cannot be copied and pasted into the Chip Summary simultaneously

Problem:

It is no longer possible to copy and paste multiple entries (e.g., sample names) into the Chip Summary simultaneously.

Temporary Solution:

Multiple entries can be imported into the Chip Summary from a *.csv, *.txt, *.xad, or *.xsy file by right-clicking in the Chip Summary and selecting Import. Alternatively, each entry can be copied and pasted individually.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Usability

One-line Description:

Change in 'Color' value formatting in Results Table Export

Problem:

Starting with version B.02.12 (SR2), the 'Color' value in the Results Table Export is formatted as a numerical value using a comma (",") as the digit grouping symbol.
In previous versions, no digit grouping symbol was used. As a result, Laboratory Information Management Systems (LIMS) configured to analyze exports from earlier versions may have problems interpreting the new format.

Temporary Solution:

LIMS configurations must be updated to accommodate the new format of the Results Table Export.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: User Interface

One-line Description:

Security Pack: Aborted validation by the user can cause mouse pointer issue

Problem:

If a user aborts a validation, the mouse pointer can stay in a "loading" state.
The status bar in the bottom of the application window will not complete to 100% after the run was aborted.
This issue does not affect correct logging in the system logbook or saving of the validation report.

Temporary Solution:

N/A

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: User Interface

One-line Description:

Icons "Gel Color" and "Scaling Mode" missing in quick menu

Problem:

In the Gel tab of a run file, the icons for "Gel Color" and "Scaling Mode" are missing from the quick menu.

Temporary Solution:

The options "Gel Color" and "Scaling Mode" are available through the "Gel" menu.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: User Interface

One-line Description:

Region Type visible in Smear Regions setpoint menu

Problem:

Since version B.02.12, a Region Type column is shown in the Smear Regions setpoint menu. This is a bug, and the Region Type column should not be displayed.

Temporary Solution:

You can ignore the Region Type column.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Users Guide/On-Line Help

One-line Description:

Access to 2100 Expert Help is limited with active Security Pack for Windows 10 64-bit in version B.02.09

Problem:

The 2100 Expert Software (B.02.09) "Help" cannot be accessed directly via the "Help" menu for Security Pack users with Windows 10 64-bit operating systems.
This also affects the feature to call the help directly up via the "F1" button.

Temporary Solution:

A shortcut to the corresponding help file will be placed on the desktop of each user during setupand should beused to access the 2100 Expert Software Help.

Fix Information:

This issue is fixed in B.02.10.

Keyword: Vulnerabilities

One-line Description:

2100 Expert Vulnerability: ActiveX

Problem:

The 2100 Expert Software is susceptible to third-party exploits due to security vulnerabilities reducing the system’s information assurance.
This affects all computers that have 2100 Expert Software installed (instrument control and/or data analysis only).

After a thorough assessment, it has been determined that such vulnerabilities do not pose significant risk when the following mitigation steps are taken. Please contact your IT department immediately and make them aware of this situation.

Temporary Solution:

• Check the network configuration. The 2100 Expert Software shall be installed on a PC that is part of a closed, physically separated network. Alternatively, the PC shall be removed from the network connection. 
• Keep your Windows operating system and applications up-to-date and ensure that the latest security updates are installed.
• When updating, please refer to the readme for information about compatibility of the software with operating systems. The readme can be found on agilent.com.
• Install and maintain a virus scanner and firewall. Improve security protection on your PC. If Windows Defender is used, default settings should be applied.
• Update to the latest 2100 Expert Software release.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Vulnerabilities

One-line Description:

2100 Expert Vulnerability: VB6 OLE

Problem:

The 2100 Expert Software is susceptible to third-party exploits due to security vulnerabilities reducing the system’s information assurance.
This affects all computers that have 2100 Expert Software installed (instrument control and/or data analysis only).

After a thorough assessment, it has been determined that such vulnerabilities do not pose significant risk when the following mitigation steps are taken. Please contact your IT department immediately and make them aware of this situation.

Temporary Solution:

• Check the network configuration. The 2100 Expert Software shall be installed on a PC that is part of a closed, physically separated network. Alternatively, the PC shall be removed from the network connection. 
• Keep your Windows operating system and applications up-to-date and ensure that the latest security updates are installed.
• When updating, please refer to the readme for information about compatibility of the software with operating systems. The readme can be found on agilent.com.
• Install and maintain a virus scanner and firewall. Improve security protection on your PC. If Windows Defender is used, default settings should be applied.
• Update to the latest 2100 Expert Software release.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Vulnerabilities

One-line Description:

2100 Expert Vulnerability: Known third party vulnerabilities

Problem:

The 2100 Expert Software is susceptible to third-party exploits due to security vulnerabilities reducing the system’s information assurance.
This affects all computers that have 2100 Expert Software installed (instrument control and/or data analysis only).

After a thorough assessment, it has been determined that such vulnerabilities do not pose significant risk when the following mitigation steps are taken. Please contact your IT department immediately and make them aware of this situation.

Temporary Solution:

• Check the network configuration. The 2100 Expert Software shall be installed on a PC that is part of a closed, physically separated network. Alternatively, the PC shall be removed from the network connection. 
• Keep your Windows operating system and applications up-to-date and ensure that the latest security updates are installed.
• When updating, please refer to the readme for information about compatibility of the software with operating systems. The readme can be found on agilent.com.
• Install and maintain a virus scanner and firewall. Improve security protection on your PC. If Windows Defender is used, default settings should be applied.
• Update to the latest 2100 Expert Software release.

Fix Information:

This known problem is temporarily not planned to be fixed in a future version.

Keyword: Vulnerabilities

One-line Description:

2100 Expert Vulnerability: MSXML 4 Risk

Problem:

The 2100 Expert Software is susceptible to third-party exploits due to security vulnerabilities reducing the system’s information assurance.
This affects all computers that have 2100 Expert Software installed (instrument control and/or data analysis only).

After a thorough assessment, it has been determined that such vulnerabilities do not pose significant risk when the following mitigation steps are taken. Please contact your IT department immediately and make them aware of this situation.

Temporary Solution:

• Check the network configuration. The 2100 Expert Software shall be installed on a PC that is part of a closed, physically separated network. Alternatively, the PC shall be removed from the network connection. 
• Keep your Windows operating system and applications up-to-date and ensure that the latest security updates are installed.
• When updating, please refer to the readme for information about compatibility of the software with operating systems. The readme can be found on agilent.com.
• Install and maintain a virus scanner and firewall. Improve security protection on your PC. If Windows Defender is used, default settings should be applied.
• Update to the latest 2100 Expert Software release.

Fix Information:

This vulnerability is fixed in version B.02.11 or higher.
MSXML 4 was replaced by MSXML 6.

Keyword: Vulnerabilities

One-line Description:

Logbook comment can be used to execute any .exe file.

Problem:

This defect allows any .exe file to be executed in the context of the 2100 Expert software without using a console, explorer or task manager.
This defect affects both Security Pack and non-Security Pack, whereby any .exe file is executed in an elevated state with Security Pack.

Temporary Solution:

Do not leave the software unattended. For Security Pack, set an appropriate "lockout" time value in the "System Context" menu. Keep your individual passwords private.

Fix Information:

This issue is fixed in B.02.11 (SR1)

Keyword: Vulnerabilities

One-line Description:

The release of B.02.12 changes the Active X controls. Other software might not work as expected anymore. 

Problem:

The fix of the Active X components could render third party software non-functional. The reinstallation of a third-party software reintroducing the Active X components makes the system vulnerable again. This risk occurs always and is severe, if a third-party software using these components is installed/reinstalled, but it happens only with third party software using Active X components.

Temporary Solution:

Users won't install any third-party software on the computer. In case of third-party software installation, make sure that it does not contain Active X components.

Fix Information:

N/A