Software Status Bulletin

2100 Bioanalyzer Software      G2946CA

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: Data Evaluation

changed assay ( setting) is not updated with first run
KPR#:106
Stars SCR#:  n/a

Runtime error occurs when a region is deleted from generic demo data file
KPR#:108
Stars SCR#:  n/a

log/linear change in x-Axis for cell assay not possible
KPR#:109
Stars SCR#:  n/a

Archiving of the last used method failed
KPR#:124
Stars SCR#:  n/a

Regions in cell assay not adjustable
KPR#:125
Stars SCR#:  n/a

RIN value depends on user interference with baseline calulation
KPR#:126
Stars SCR#:  n/a

LM detection for RIN algorithm invisible for user
KPR#:128
Stars SCR#:  n/a

Faulty reanalysis of older DNA or Protein files upon reload with SW Rev B.02.06
KPR#:130
Stars SCR#:  n/a

Result Flagging for RNA files does not work
KPR#:131
Stars SCR#:  n/a

Keyword: Data Handling ( import & export

cell assay setpointa import to existing file not executed
KPR#:111
Stars SCR#:  n/a

archiving an open method (extension .xsy) failed
KPR#:114
Stars SCR#:  n/a

Keyword: Print Out

Option "Print the selected heading & all subtopics" under Help-print not working
KPR#:98
Stars SCR#:  n/a

wrong path selected for print to file
KPR#:113
Stars SCR#:  n/a

Keyword: Usability

Report in signature log shows previous action
KPR#:105
Stars SCR#:  n/a

error while starting application
KPR#:110
Stars SCR#:  n/a

SecPack Docu: Users & Role description is not consitent with UI
KPR#:129
Stars SCR#:  n/a

Keyword: Data Evaluation

One-line Description:
changed assay ( setting) is not updated with first run

Problem:

Changing a parameter (e.g. sample treshold)and saving it while a assay is running the re-started assay does not contain the saved changes.

Problem Cause:

When a assay is loaded and then changed it takes effect always with the second run.

Temporary Solution:

After changing setpoints in assay/method context, save file. Switch to instrument context and once again select/open the modified assay file.

Fix Information:

n/a

Keyword: Data Evaluation

One-line Description:
Runtime error occurs when a region is deleted from generic demo data file

Problem:

1]Load a Generic(Demo) data file in Data context. 2]Click on Sample1--> Dotplot tab 3]Click on Dotplot--> insert region 4]Select region and click Dotplot--> insert region in all dot plots -- Click 'Yes' or'No' in copy region box 5] click dotplot-->grid view. -- select the inserted region in sample1 and delete it A Message box which is showing: A runtime error occurs.Followed by a second message box.

Problem Cause:

This problem always happens in Grid View Mode

Temporary Solution:

Do not use grid view mode

Fix Information:

n/a

Keyword: Data Evaluation

One-line Description:
log/linear change in x-Axis for cell assay not possible

Problem:

log/linear change in x-Axis for cell assay not possible from setpoint explorer in assay properties.

Problem Cause:

new settings are not saved

Temporary Solution:

Save changes and re-open it

Fix Information:

n/a

Keyword: Data Evaluation

One-line Description:
Archiving of the last used method failed

Problem:

Security Pack: The last used method in Instrument context will not be archived.

Problem Cause:

Due to the reason that the method is still active the archiving of that method fails

Temporary Solution:

Never archive a last used method. Workaround: close application -> log on as one with rights to run a sample -> select a method witch will not be archived -> make a run till completed -> close application -> log on again as admin for archiving the method which should be archived

Fix Information:

n/a

Keyword: Data Evaluation

One-line Description:
Regions in cell assay not adjustable

Problem:

Regions in cell assay (demo file and customer file) are not adjustable. Already highlighting the region is impossible, the same counts for dot blots.

Problem Cause:

This happens in Expert SW which is already running for a while, freshly installed obviously does not show the effect.

Temporary Solution:

Workaround is the replacement of a file. Please contact your Agilent Support Center.

Fix Information:

n/a

Keyword: Data Evaluation

One-line Description:
RIN value depends on user interference with baseline calulation

Problem:

In electropherogram view baseline settings can be changed (green dashed line) - in setpoint explorer not. In setpoint explorer baseline correction can be swiched on/off.

Problem Cause:

RIN value under B.02.02 SI 236 and higher should be independend from any user input to the software.

Temporary Solution:

Import the setpoints from the B.02.03 assays to show the correct RIN values.

Fix Information:

completely fixed with B.02.06

Keyword: Data Evaluation

One-line Description:
LM detection for RIN algorithm invisible for user

Problem:

RIN values for samples lanes with questionable lower marker detection deviate from expectations.

Problem Cause:

The LM chosen by the RIN-algorithm is invisible for user. In case of deviation for the LM detection from the standard LM detection a rational explanation for unexpected RIN-results cannot be found by the user.

Temporary Solution:

Rerun samples to achieve proper runs with unambiguous LM peaks.

Fix Information:

Fixed in B.02.06

Keyword: Data Evaluation

One-line Description:
Faulty reanalysis of older DNA or Protein files upon reload with SW Rev B.02.06

Problem:

An improper reanalysis of DNA or Protein files recorded with 2100 Expert software versions B.02.05 and below happens on reanalysis which takes place on any reopening of older files with the latest 2100 Expert version B.02.06. 1.) DNA peak concentration reported from B.02.06 deviate from initial results of the DNA 1000, DNA 7500 and DNA 1200 assay. 2.) Protein concentration from the Protein 230 and 80 assay might be affected under certain circumstances as well. This issue occurs if the upper marker is relatively small in comparison to the lower marker. Wrong detection of the upper marker takes place. Since the upper marker is used as internal quantification standard the sample peak concentrations are calculated wrong as well.

Problem Cause:

During migration of older files certain setpoints are not transferred properly.

Temporary Solution:

Do not use quantitative results from older files after reopening in revision B.02.06.

Fix Information:

A patch to correct this issue within B.02.06 will be available on our web pages.

Keyword: Data Evaluation

One-line Description:
Result Flagging for RNA files does not work

Problem:

For the 2100 Expert version B.02.06 the result flagging of RNA Nano and Pico assays is not functional. On opening of older files with existing flagging the result flagging will be erased.

Problem Cause:

Result flagging functionality is disabled in data analysis.

Temporary Solution:

n/a

Fix Information:

A patch to correct this issue within B.02.06 will be available on our web pages.

Keyword: Data Handling ( import & export

One-line Description:
cell assay setpointa import to existing file not executed

Problem:

cell assay import of setpoints through assay properties to existing file is not done.

Problem Cause:

The changes are not active before the file is saved

Temporary Solution:

The new settings get applied when the user saves the file

Fix Information:

n/a

Keyword: Data Handling ( import & export

One-line Description:
archiving an open method (extension .xsy) failed

Problem:

A method which is still listed (means open)in Instrument view is not archived. All other methods are archived.

Problem Cause:

A method which is still open can not be archived.

Temporary Solution:

Workaround: close application -> log on as an advanced operator -> select a method witch will not be archived -> make a run till completed -> close application ->log on again as admin for archiving the method

Fix Information:

n/a

Keyword: Print Out

One-line Description:
Option "Print the selected heading & all subtopics" under Help-print not working

Problem:

Printing from the Help Desk using the "Print" button from the tool bar and having "Print the selected heading and all subtopics" options checked an message shows up "The selected topics must be printed individually" and does not print.

Problem Cause:

Bug in the Microsoft Help workshop

Temporary Solution:

In order to print choose the option "Print the selected topic".

Fix Information:

n/a

Keyword: Print Out

One-line Description:
wrong path selected for print to file

Problem:

If the results of a data should be saved to DESKTOP a new folder c:\Documents and Settings\2100System.....\desktop is generated

Problem Cause:

Security pack application uses its 2100system accounts desktop. Therefore the file can be found there.

Temporary Solution:

Use a known path to store the data

Fix Information:

n/a

Keyword: Usability

One-line Description:
Report in signature log shows previous action

Problem:

The report generated when finalizing a workflow level does not include the "Approve workflow" (finalized workflow level) actions in audit trail and signature log sections of report. It actually contains everything BEFORE the approval takes place.

Problem Cause:

The Report is generated before the approval has been signed and before that action is saved. This is implemented by design.

Temporary Solution:

Workaround: print report manually.

Fix Information:

n/a

Keyword: Usability

One-line Description:
error while starting application

Problem:

Start 2100expert: error appeared (file missing or invalid: AgtXYGraphActiveX.ocx)

Problem Cause:

The problem is with the registration of AgtXYGraph.ocx. The registration path follows the windows 8.3 file naming convention. Some special Windows XP environments seem to have a problem with that.

Temporary Solution:

Execute following command in the 2100 expert installation bin folder: regsvr32 AgtXYGraphActiveX.ocx

Fix Information:

n/a

Keyword: Usability

One-line Description:
SecPack Docu: Users & Role description is not consitent with UI

Problem:

Description of Users and Role is not correct in the documentation provided in the 2100 Expert Help. 1.) Correct is "Advanced OP: can Import/Export files in the system context" In the Help-documentation a checkmark in an definition table is missing. 2.) The correct Role name is "Validation Operator". In the Help-documentation this role is named Verification. 3.) Correct is "Validation Operator: can open data files". In the Help-documentation a checkmark in an definition table is missing. 4.) Correct is "Validation Operator: can open method files". In the Help-documentation a checkmark is missing. 5.) Correct is " Unlock Operator: can open data files". In the Help-documentation a checkmark in an definition table is missing. 6.) Correct is " Unlock Operator: can open method files". In the Help-documentation a checkmark in an definition table is missing.

Problem Cause:

Content of Help-documentation associated with the Security Pack is not in accordance with product definition and thus not in accordance with the Compliance Operational Qualification tests.

Temporary Solution:

The Compliance Operational Qualification tests use correct naming and test for access rights. No correction needed here. The documentation will be corrected with the next update of the 2100Expert Help files.

Fix Information:

n/a