Software Status Bulletin

LC/MS Acquisition     LC/MS Acquisition

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: User Interface

KPR#:222689 Method MRU grayed out, after optimizer run stopped manually and immediately click on new or open button of acquisition method pane.
KPR#:532312 Method MRU grayed out, after optimizer run stopped manually and immediately click on new or open button of acquisition method pane.

Keyword: 

One-line Description:

SampleRunPane throws exception when large numeric value added in data file name with auto Increment enabled

Problem:

The user entered '1234567890123456789012345678901234567890123456789012345678901234567890123123456789012345678901234567.d' as data file name and had selected the Auto Increment check-box.  They then started the run.

This resulted in the following exception 'Value was either too large or too small for an Int32' to be displayed on the screen.  

The user also reported the same exception when the Sample Run pane when the user clicked on 'Run' button.  The run will not start in this case and no indication is given to user.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

MFC column does not work with Qual B.08.00 SP1

Problem:

MFC column does not work with Qual B.08.00 SP1

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Quant error when generating a report with ECM

Problem:

When running Quant in ECM the following error has been reported when generating reports: " Could not find part of the path d:\masshunter\.secure....\codes\resources"

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Antivirus exclusions might be required at customer location

Problem:

On workstations with certain Anti-virus software, the StudyEngine and LogConfigurationEditor's executables may be detected as malware. This mostly happens when Study Engine tries to delete Study cache files from local secure cache or when user tries to clear old log files Log Configuration Editor. 

Temporary Solution:

Allow exceptions for StudyEngine and LogConfigurationEditor's executables in Antivirus Software

Fix Information:

Keyword: 

One-line Description:

MassHunter fails to save the method with the correct instrument setpoints when a  semi-colon is in the Method name

Problem:

Masshunter will not save the method when a semi-colon is contained within the method name. 

Steps To Reproduce: 
 1. Start MassHunter Acquisition software. 
 2. Save a method with name as Acq;Method.m.  The method is saved.
 3. Save As same method with different name as AcqMethod.m.
 4. Reload Acq;Method.m.

The user observes that the QQQ set points are not getting saved for method, which is named with semicolon as one of the character.

NOTE: LC only configuration doesn't have this issue. 

Temporary Solution:

Do not use a semi-colon in the method name. 

Fix Information:

Keyword: 

One-line Description:

Re-optimization in Study Manager Optimizer when user specifies value for optimization

Problem:

When running a subsequent optimization study for compounds previously run by checking "re optimize compounds..." and entering 1 into the box, only some of the compounds will re-optimize when close to within 24 hours of the prior optimization.

Temporary Solution:

Wait additional time to re-optimize when using user specified values

Fix Information:

Keyword: 

One-line Description:

Manual tune does not allow acquisition to ECM

Problem:

From the manual tune Files tab, while entering an ECM data path into the acquire text box and acquiring results, a ".d" is automatically added on to the file name. This results in the error message "please enter a valid local path."

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Skyline Automation is not reporting sample numbers correctly in status bar.

Problem:

While Skyline is running, the Study manager status bar does not show correct sample numbers. It shows running -1 of 4 sample, for  0 of 4 sample.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

MassHunter Acquisition for LC/MS Crash is Seen After Worklist Completed with ECM 3.5

Problem:

the user started a 12 hour stress test with ECM 3.5.5.  All runs finished and after that MassHunter exception is seen.  After clicking OK, MassHunter Acquisition crashed.  No log book entries are seen.

Temporary Solution:

Investigations show that the defect originates in ECM 3.5.5.  This is not a defect with the MassHunter Acquisition software itself.  As such, there is no workaround is available at this time from MassHunter.

However, the defect has been fixed in ECM 3.6.  Please update to ECM 3.6 if this defect has been observed on the LC/MS system. 

Fix Information:

Keyword: 

One-line Description:

Time and m/z are same in spectrum RTP annotation

Problem:

Time and m/z are same in spectrum RTP annotation

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Running "DA Only" Worklist in ECM mode fails with error "data file ... acquired during locked mode"

Problem:

In ECM mode - all data files are acquired in 'Locked mode' such that they cannot be overwritten.

If a user running in ECM mode wants to run a 'DA Only' reprocessing - Acquisition will throw an error:

"The data file... was acquired during locked mode run and cannot be overwritten. Choose a different data file and restart the sample run."

Temporary Solution:

Instead of running the worklist in DA Only mode from within Acquisition - use the "DA Reprocessor" component installed with Acquisition to perform the same task. 

Fix Information:

Keyword: 

One-line Description:

Tune pane remains enabled, when sample run starts, before ISP shows run state for devices

Problem:

Tune pane remains enabled, when sample run starts, before ISP shows run state for devices

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Multiple messages displayed for Acq console, if restarted during optimizer run 

Problem:

If a restart of Acquisition happens while optimizer is running, duplicate messages are displayed for Optimizer and the online console, on run completion.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Offset value must be between 0 to 100%

Problem:

The Offset in Chromatogram tab accepts any number but when right clicking on the chromatogram plot the offset will accept value in between 0 to 100% only.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Access Denied error followed by Exception seen, on Online Acq console launch

Problem:

Access Denied error followed by Exception seen, on Online Acq console launch

Temporary Solution:

Launch Acquisition console a second time. 

Fix Information:

Keyword: 

One-line Description:

Logbook Viewer Crash

Problem:

Logbook Viewer may crash after changing the purge settings. Will not launch again until restarting PC

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

 Time segments not updating on DMRM run with Waste time segments 

Problem:

When running a DMRM run (on a simulator or real instrument), the 1st time segment is always displayed in teal. Any additional time segments are not highlighted as they are run.
This is a cosmetic issue.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

 Source and iFunnel Optimizer not supported for compliance 

Problem:

Source and iFunnel Optimizer will inherently create Quant batch, Quant method, and an Excel Quant reporter independent of the Quant user login information required for compliance.

Temporary Solution:

The Source and iFunnel Optimizer are not supported for Compliance and should not be used.

Fix Information:

Keyword: 

One-line Description:

  Misleading error message is displayed when user unchecks the trigger option in QQQ Acquisition tab.   

Problem:

With a triggered method, switching the triggering to "off" in order to run with only the primaries produces a display indicating there are errors in the method that need to be corrected.  However, the method can be saved and the error indicators is cleared.  The saved method will run without issue.

The indication of errors is benign but misleading; users may start editing their method when in fact there is nothing wrong with it.

Temporary Solution:

After unchecking the trigger option, 'apply' the method to clear the misleading error message.

Fix Information:

Keyword: 

One-line Description:

Error occurs when switching from a Product Ion scan with fragmentor ramp to an MRM scan type.

Problem:

When editing a method with a fragmentor ramp, the method editor will crash if the user changes the scan type to MRM or any other scan type that does not allow fragmentor ramps.

Temporary Solution:

Delete all rows in the fragmentor ramp table before changing the scan type to MRM or other scan type that does not allow fragmentor ramps.

Fix Information:

Keyword: 

One-line Description:

 Tune file error is seen upon transferring method from 6460A instrument to 6495A instrument   

Problem:

The error message does not specify that the tune file specified in the method is for the wrong instrument model.

Temporary Solution:

Select a tune file for the correct model instrument in the QQQ tab of the Method Editor.

Fix Information:

Keyword: 

One-line Description:

When Quant is not installed, Drug Discovery Study gives "scriptinfo.xml" error.

Problem:

Error message is confusing. The error message should be clearly worded and easy for the user to understand. The message should alert customer that the Drug Discovery workflow would requires Quant to be installed in order for the software works correctly.

Temporary Solution:

Install Quant software before launch Drug Discovery study.

Fix Information:

Keyword: 

One-line Description:

Acquisition will crash if you try to load a tune file generated for a different model MS

Problem:

On a 6490 instrument, load a tune file for a 6495.

Click OK on the message box with title "MassHunter Tune" and message "Error: Tune File could not be loaded."

Observe the message box with title: "AgtQQQTuneSetpoints" and message "Run-time error '0'."

The tune pane is now covered in hash bars indicating the driver has crashed.  An exception occurs when exiting MassHunter.  Engine shutdown fails.

To recover, the user must use the 'Kill MassHunter Process' script and restart acquisition and all the engines.

In B.08.00, the first message box is displayed saying "Error: Tune File could not be loaded."  No further errors are observed.

 Same behavior is observed when loaded wrong model tune file in Method Editor, Series of errors are shown and mistake can not be correct. MH crashes with RPC server not available.To recover, the user must use the 'Kill MassHunter Process' script and restart acquisition and all the engines.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Sheath Gas Flow set point may be overridden if different Methods are used in a Worklist

Problem:

It can happen that a worklist with different methods that include disparate Sheath Gas Flow  set points will revert to the preceding Sheath Gas Flow set point when the new method is executed.  This is by design:

If the Actual Sheath Gas Temperature minus New Method Sheath Gas Temperature set point > 10 C AND the Actual Sheath Gas Flow minus New Method  Sheath Gas Flow set point > 0.3 L/min, then the New Method Sheath Gas Flow set point will be overridden with the Actual Value (from the preceding method).  This action does not overwrite the Method file parameter, but does overwrite the set point during the acquisition of the method.

Temporary Solution:

To prevent this issue from occurring, ensure that subsequent methods in a worklist include Sheath Gas Temperature set point values < 20 C from the preceding method, and/or Sheath Gas Flow set point values < 0.3 L/min from the preceding method.

Fix Information:

Keyword: 

One-line Description:

Polarity/Time segmented MRM methods will (intermittently) lose/distort the signal of the new Polarity/Time segment

Problem:

Polarity/Time segmented MRM methods will (intermittently) lose/distort the signal of the new Polarity/Time segment 

Temporary Solution:

Acquire a "dummy signal" of the original ion polarity within the new time segment, or acquire a "dummy time segment" of the effected polarity prior to the desired acquisition start time of the new ion polarity.

Fix Information:

Keyword: 

One-line Description:

Setting Fragmentor and Collision Energy values to maximum values may generate a Fragmentor Fault

Problem:

Setting both the Fragmentor and Collision Energy values to maximum values may generate a Fragmentor Fault

Temporary Solution:

Reduce the Fragmentor and/or Collision Energy values to value(s) low enough to prevent the Fragmentor Fault from occurring.

Fix Information:

Keyword: 

One-line Description:

6490/6495 - The Drying Gas Temperature setting in Source parameters is reset to default values after editing the MRM table and applying changes when starting from a new method

Problem:

The Drying Gas Temperature setting in Source parameters is reset to default values after editing the MRM table and applying changes when starting from a new method for the 6490 or 6495 QQQ.

Temporary Solution:

Save method changes to the Drying Gas Temperature Setting before editing the MRM table and applying changes.

Fix Information:

Keyword: 

One-line Description:

Error when Optimizer project is saved via Study Wizard

Problem:

Editing and saving an Optimizer project to the same name results in an error.

Temporary Solution:

Save modifications to an existing Optimizer project to a new file name.

Fix Information:

Keyword: 

One-line Description:

Disabling Dynamic Ramps in Manual Tune cannot be saved

Problem:

If a Dynamic Ramp parameter is disabled in Manual Tune, and these changes are saved to a Tune file, those changes will be lost when re-loading the tune file.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

QQQ Firmware version is missing from instrument configuration when viewed through the System Status graphic

Problem:

The firmware is shown as x.xx in instrument configuration when using the 'i' icon on the System Status graphic at the bottom of the instrument dashboard display.

Temporary Solution:

Use the File | Print | Instrument Configuration Report ... to generate an Instrument Configuration Report to display the QQQ Firmware version.
Also, this is a timing issue, and appears intermittently.  Closing MassHunter Acquisition and restarting it, then click the 'i' button to see the correct firmware version.

Fix Information:

Keyword: 

One-line Description:

Offline Method Editor may display message "There are errors in the method"

Problem:

Upon opening, the Offline Method Editor may display the message "There are errors in the method".  This message indicates there is a parameter mismatch between the present values and configured hardware.  Opening the Offline Method Editor includes default parameters for the ESI source, including 300 C drying gas.  This value exceeds the maximum allowed temperature for 6490 systems (290 C), which results in the error message being displayed.

Temporary Solution:

When using the Offline Method Editor, ensure the proper method is loaded, and the method matches the hardware configuration.  Update any method parameters that are not compatible with the hardware configuration.

Fix Information:

Keyword: 

One-line Description:

Gas temp does not adjust to setpoint after QQQ power cycle

Problem:

After the Mass Spectrometer is reset by cycling the power the instrument stays in idle because the set points cannot be reached. 

 

Temporary Solution:

Reload the method or restart MassHunter and the gas temp will equilibrate.

Fix Information:

Keyword: 

One-line Description:

User Must Enter Numerical Values to Predictable Range or Floating Range Text Boxes in Edit Chromatogram/Signal Plot

Problem:

The Edit Chromatogram / Signal Plots requires that numerical values are the only values that are accepted by predictable range / floating range text boxes. Abundance can only be in numbers.

However, the software allows the user to put in letters or non numerical symbols in these fields. 

Temporary Solution:

Do not put letters or non numerical symbols in these fields. 

Fix Information:

Keyword: 

One-line Description:

Capillary voltage read-backs differ from setpoints

Problem:

The Capillary voltage read-back displays the output voltage of the corresponding power supply.  This read-back value may differ from the setpoint (nominal) value by <5%, which is the expected tolerance of the power supply.

Temporary Solution:

The Capillary voltage read-back should be within <5% of the setpoint (nominal) voltage when the MS is On.  As the optimal Capillary voltage for an application is determined empirically, any discrepancy between the read-back and setpoint voltage will not impact data acquisition.  The Capillary voltage read-back is provided for system diagnostic purposes.

Fix Information:

Keyword: 

One-line Description:

(Optimizer) Error when running Optimization study with CTC-PAL configured

Problem:

An error may be experienced when running an Optimization study with CTC-PAL configured.  The error message "Device driver exception:: Error HRESULT E_FAIL has been returned from a call to COM component.  Template method my be invalid"
"Phase 1 Optimization failed"

These errors will be displayed in MassHunter Acquisition and/or Optimizer.

Temporary Solution:

This issue can occur if a Study with invalid vial positions are is executed when a CTC-PAL autosampler is configured.  For example, the vial position "Vial 1" is not recognized by the CTC-PAL instrument, which will result in this error being generated.

Fix Information:

Keyword: 

One-line Description:

 Audit Trail Viewer Crash after leaving Console running for extended period of time

Problem:

 Audit Trail Viewer Crash after leaving Console running for extended period of time

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Method Reports Missing Graph Title

Problem:

When generating a method report for certain QQQ Mixed Mode Method, some graphs do not have titles. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Optimizer database is removed by MassHunter uninstall

Problem:

When uninstalling MassHunter, the Optimizer database is removed.  

This defect was introduced in B.09.00

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

244207 - Invalid Checksum Error for Study When "Copy methods" Checkbox is Unchecked.

Problem:

Steps to recreate this issue:

The user submits a Worklist Only study in ECM Compliance as follows:
1. On the "Worklist Only" wizard page "Copy methods" checkbox is checked by default.
2. Click "Next" and go to the last page but do not click "Finish".
3. Click "Back" and go back to the first page.  
4. Uncheck "Copy methods" checkbox.
5. Submit and run the study.

The study fails with Invalid checksum error.

Temporary Solution:

There is one workaround available at this time:

Recreate the Study from default with the checkbox not selected.

Fix Information:

Keyword: 

One-line Description:

Changing sampler program and applying or saving method not possible during run.

Problem:

Changing sampler program and applying or saving method not possible during run.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

First Console launch fails after installation.

Problem:

On systems with no “house” Ethernet the LC may not connect the first time, but will on the second try.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

New method may show resolution error in 6490A instrument

Problem:

When loading a new method on a 6490A and the tune file is for unit resolution only, the new method will default to enhanced resolution. This causes a discrepancy as the tune file will only accept unit resolution

Temporary Solution:

The operator must change the resolution to unit before the method will save. 

Fix Information:

Keyword: 

One-line Description:

Opening dMRM data file when sample run is going on throws Qual exception.

Problem:

When dMRM sample run is going on and upon clicking on "View Data", Qual error is seen. Unable to open data file.

After sample run is completed, datafile opens fine.

Temporary Solution:

Wait until run is complete to open data files 

Fix Information:

Keyword: 

One-line Description:

ECM iis worker process recycles after 29 hours and acquisition needs to halt at this time

Problem:

Due to the Windows event log, IIS worker processes are recycled after 29 hours. This is done periodically in automated manner. And since study run was ongoing, it failed with data file upload error.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

"No Injection" sample position gives error on PAL 3 saying "Specified method is not known" and run does not happen

Problem:

"No Injection" as sample position is supported by CTC PAL2 for LCMS MassHunter

Temporary Solution:

Not used in StreamSelect. Workaround is to use Vial with blank run.

Fix Information:

Keyword: 

One-line Description:

Quant does not recompute checksum for a study

Problem:

When Quant processes samples in a study, the data files are modified. The checksum for the data files are re-computed, however the checksum for the stud is not re-computed. The checksum for the study is now no longer valid and editing or re-submitting the study fails in UMAT *user management and audit trail" mode.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Running long worklist causes loss in connection to ECM server 

Problem:

From Acq in compliance mode, a long worklist may result in a loss of network connection to the ECM server. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Auto Tune can crash on new MassHunter Acquisition Installation

Problem:

After a new installation or upgrade of MassHunter Acquisition the first Autotune can crash.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Audit trail incorrectly refers to MS2 Scan as "product ion" scan

Problem:

A defect has been observed in the audit trail report generator for Acquisition methods. When a change occurs to a method's scan parameters for scans of type "MS2 Scan" - the audit trail will incorrectly refer to this scan as a "Product Ion" scan. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Acquisition can hang or freeze on load screen if run on unsupported resolutions

Problem:

MassHunter Acquisition has been observed to hang on the splash screen on load if the screen resolution is higher than the supported resolutions for the LCMS QQQ and QTOF bundled monitors:

21.5 inch Monitor: 1920 x 1080 @ 60 Hz
24 Inch Monitor: 1920 x 1200 @60 Hz

Temporary Solution:

If Acquisition hangs at the splash screen - ensure that the monitors resolution is set to one of the supported resolutions listed above. In addition - be sure to set the DPI scaling to 100% in the windows display control panel. Use the keyword "DPI" to find this setting via Windows Search.

Fix Information:

Keyword: 

One-line Description:

Acquisition method audit trail fails to capture changes for "end mass" value of scan type "MS2 Scan"

Problem:

A defect has been observed in the audit trail report generator for Acquisition methods. When a change occurs to the "End Mass" value of the scan type "MS2 Scan" - that change is not captured in the audit trail.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Optimizer will not recognise methods using a Unit only Tune

Problem:

Optimizer will not recognize methods. Methods are flagged red but no useful description is provided

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Sample Group Import Mapping Not functional

Problem:

Currently - the sample group column cannot be populated when using an import map via study manager.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Signal plot settings are not saved

Problem:

Help file states that customizations made in signal plot remain after close Acquisition and opening it again. This is not the case.

Temporary Solution:

Customize signa plot each time Acquisition has been closed and launched again.

Fix Information:

Keyword: 

One-line Description:

"Another application may be using the clipboard" message when copying MRM transitions

Problem:

When copying MRM transitions in QQQ Acquisition Pane an error message stating "Anther application may be using the clipboard"

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Sampler Pretreatment displayed in Acquisition Method report when not used

Problem:

This can result in undesired results when recreating methods from a printed Acquisition Method report

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Adding or removing rows to acquisition scan segments table or  can resort the scan segment table and lead to confusion in the method's audit trail

Problem:

In Acquisition's method audit trail - changes to scan segments table can cause the sorting of the table to change in less-than-intuitive ways. This change to the table sort can cause unpredictable - but not incorrect - changes to the method's audit trail.

For example - consider a scan segment table with three rows - all with identical precursor masses. 

If a 4th row is added with a lower precursor mass - it will become first in the new table.

The audit trail will reflect that all 4 scan segments have been changed even though only one row was added to the table. This is because scan segment #1 changed to scan segment #2 once the new row was added (and became the new scan segment #1).

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

DA Reprocessor always fails validation of all DA methods

Problem:

A defect has been discovered in the DA Reprocessor version which is included/installed with QTOF Acquisition 10 (for 6456) and 10.1. This defect causes the software to always consider all data analysis only methods to be invalid - with an error "Info.xml is missing".

Temporary Solution:

A workaround is to use the "DA Method Override" column instead of the "Method" column to specify the data analysis method. Any acquisition method can be used in the "Method" column - and it will be ignored because the DA Reprocessor cannot perform acquisition activities. 

Fix Information:

Keyword: 

One-line Description:

Changes to dMRM RT, RT Delta, and Cell Accelerator Voltage not captured in method audit trail

Problem:

In both ECM mode and UMAT mode, TQ Acq 10 and prior does not capture changes to dMRM compound's RT, RT Delta, and Cell Accelerator Voltage. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Driver version displayed in LC Module list does not match the version displayed in Windows Add/Remove Programs

Problem:

For LC Driver 3.1 (build 3.1.23) - a defect was found where the driver version string displayed in the Module List (3.1.26) did not match the version displayed in the Windows Add/Remove program list (3.1.23).

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

SureMass Conversion failures when data file contains multiple spaces

Problem:

In QTOF Acq 10 and prior, a script was included to automatically convert Profile data into SureMass format as a post-method action. It was observed that if a data file name contained multiple spaces - the conversion would fail. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Hundreds of tiny logbooks uploaded to ECM archived logs location 

Problem:

A user has reported that QQQ Acquisition 10.0 with ECM 3.6 (running in ECM Compliance mode) was uploading many logbooks entries to different log files in the Archive logbook location on the ECM. It was noted that the user had set the Logbook "Purge Settings" value to "1 Day" the shortest possible setting. 

The expected behavior is when the purge settings is set to "1 Day" is that one new logbook is uploaded to the ECM server archive folder only once - and only when launching Acquisition. That logbook will contain log entries that are older than 24 hours. 

Temporary Solution:

It was found that when the user switched to the "1 Week" setting - the upload behavior returned to normal expected behavior. 

Fix Information:

Keyword: 

One-line Description:

NT User Validation Errors seen interrupting running worklists due to response failures from domain controller

Problem:

Users operating MassHunter Acquisition for LC/MS TQ version 10.x and prior in ECM mode have reported incidents where a running worklist would stop with an error "NT User Validation Failed". This error occurs when the ECM server attempts to perform an authentication with a domain controller, and the domain controller does not respond. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Activity Log will not record an error if worklist aborts because the system ran out of storage

Problem:

The activity log stored in Control Panel will not record an entry for the worklist aborting if the abort occurred because the system ran out of available disk space.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Acquisition generates excessive log files when Purge Logbook setting is set to 1 day

Problem:

When the TQ Acq 10 or prior Acquisition logbook purge time is set to 1 day - a defective behavior is observed where many many archived logbooks are being generated into the C:\MassHunter\Log\Acq\Archive directory.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Error icon appears next to the method path field when setting a DA method in the acquisition method

Problem:

An error icon will appear next to the DA method path after setting a DA method within the Acquisition method's DA parameters. This error flag can be ignored - the applied DA method is correctly linked to the Acquisition method.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Error seen when opening the "worklist run parameters"

Problem:

A rarely reproducible error message has been observed when opening the "Worklist Run Parameters" dialog in Acquisition. The error prevents the dialog from opening. Clicking "OK" will close the error.

Temporary Solution:

The error does not interrupt operations. You can close Acquisition and reopen to try opening the dialog again. 

Fix Information:

Keyword: 

One-line Description:

Content imported into OpenLab Server / ECM XT can take 2 minutes before appearing in data analysis applications

Problem:

When using the import tools to upload new data/content into the OpenLab Server / ECM XT environment - multiple databases have to be updated before that content is visible to the MassHunter applications. This process can take up to 2 minutes after the file has been completely uploaded. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Secure Project Directory is not supported with MassHunter Acquisition

Problem:

OpenLab Control Panel has an option to "secure project folder" which will set Windows NTFS permissions on the project path. Enabling this feature will break MassHunter acquisition in a variety of ways. Errors can be seen indicating that the "system cannot find the file specified" and/or "Failed to start MassHunter acquisition engine processes".

Temporary Solution:

Disabling the "secure project folder" and creating a new project will restore normal functionality. 

Fix Information:

Keyword: 

One-line Description:

MassHunter 11 (Acq, Quant, or BioConfirm) cannot co-reside with any other OLSS installing application

Problem:

MassHunter 11 (including Acquisition for TOF/QTOF, Quantitative Analysis, and BioConfirm) cannot co-reside on a client PC with any other application which installs OpenLab Shared Services (this includes ChemStation C.01.x.,  CDS 2.x, or EZChrom of any version).

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Error message - Current operation cannot be performed on multiple columns - unexpectedly seen in Worklist table

Problem:

An error has be seen when performing a fill down operation on the data file column which reads "Current operation cannot be performed on multiple columns" even when only one column is selected.

Temporary Solution:

Simply click into any single cell of the worklist then attempt the fill down operation again. 

Fix Information:

Keyword: 

One-line Description:

Content imported into OpenLab Server / ECM XT can take 2 minutes before appearing in data analysis applications

Problem:

When using the import tools to upload new data/content into the OpenLab Server / ECM XT environment - multiple databases have to be updated before that content is visible to the MassHunter applications. This process can take up to 2 minutes after the file has been completely uploaded. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

"An Error occured" message appears when configuring an instrument in OLCP

Problem:

A defect has been discovered in the MassHunter Acquisition 11 implementation of the OpenLab control panel which occurs when the "Configure Instrument" window is open for more than ~5 minutes. When the user clicks "OK" to confirm and apply the instrument configuration (IP addresses) - a popup message appears saying "Error, An error occurred" with no further information. Clicking the "Close" button to dismiss the error causes an identical error message to occur again. This process repeats approximately 10-15 times.

Temporary Solution:

As a workaround - simply click "Close" to dismiss the error message until the message no longer appears. This will take approximately 10-15 clicks to completely dismiss the message. Once completed - the system will indicate that the instruments were configured successfully and you can proceed to launch the instrument.  

Fix Information:

Keyword: 

One-line Description:

User must re-link imported DA methods after acquisition methods are imported into a new project location

Problem:

When importing a method which has a linked Da method, and that DA method is imported from one project to other project in the same compliance mode (workstation to workstation / networked workstation to networked workstation),aAn error is shown while saving\running that , "Da method path doesn't belong to the current project path. parametre name:StoragPath"

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Acquisition will no longer prompt to save layout when switching layouts, contexts, or closing the application

Problem:

A major user frustration has been the incessant prompts to save the application layout whenever switching between different layouts, contexts (tune/acquisition) or closing the application. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Importing older worklists may fail with error: unable to get UniqueNaming Node from worklist template

Problem:

The error: "unable to get UniqueNaming Node from worklist template" might be seen when importing wkl worklist files generated by older versions of LCMS QTOF acquisition (B.07 or prior). 

Temporary Solution:

As a workaround - this worklists can be loaded in QTOF Acq 10.1/10.0 - saved with a new name - then imported by QTOF Acq 11. 

Fix Information:

Keyword: 

One-line Description:

Method report for Ultivo should be generated to A2 paper

Problem:

The Ultivo acquisition method report has too many columns to fit into a single row of an A4 or 8.5" x 11" paper. The recommendation would be to generate the report to an A2 PDF so that everything can be displayed as a single row.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

With MassHunter Study Manager - additional login entries will appear in the activity log without an application name

Problem:

In Study Manager - whenever a user logs in through the OpenLab Shared Services login dialog, a separate login entry is added to the activity log by the OpenLab Shared Services platform without specifying the application in which that login screen was displayed - as a result, it is difficult to determine which application the user logged into. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

DA Reprocessor does not launch if instrument is not configured

Problem:

The DA Reprocessor does not launch if an instrument is not configured. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Analytical Column Setup button causes error on first click

Problem:

An error is observed when clicking on the "Analytical Column Setup" on a new install for the first time. Clicking "Ok" to dismiss the error - then clicking the button again will no longer lead to an error.

Temporary Solution:

Just click "OK" and ignore the error. It'll work the second time.

Fix Information:

Keyword: 

One-line Description:

Audit Trail defect causes method changes which were already "applied" to the LC to not be written to the method audit trail when the method is saved

Problem:

A defect has been discovered in the QTOF Acq 11.0 audit trail. This defect causes changes to the LC method (MS method parameters are not impacted) to NOT be captured in the method audit trail when the method is saved. The missing audit trail items occur when changes to the method are "applied" to the instrument (by clicking the "apply" checkbox icon next to the method selection dropdown menu) before the method is saved. 

If the "Apply" checkbox is not selected before the method is saved - then ALL changes are properly captured in the method audit trail when the method is saved.  

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

"Skipping overlapped injection" is logged as a warning to the system logbook

Problem:

In Acquisition 10.2 and prior, the message "Skipping Overlapped Injection because high throughput optimization is not enabled in sampler method" was logged as a warning. This is defective behavior - this is a method parameter, a setting choice shouldn't be logged as a warning.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Worklist cannot be loaded because data file path is not within project folder

Problem:

In MassHunter 11 - if a worklist throws the error "xxxx.d is outside the storage path D:\Projects\..." this indicates that the worklist contains references to paths which exist outside of the project path. This prevents the worklist from being opened - even to correct the path problem. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Configuring a 2D-LC Cluster causes the "add/modify/delete" columns dialog to not display anything under available columns

Problem:

A defect has been discovered in the "Add/Modify/Delete Column" settings with QTOF Acq 11.0 when configured with a 2D-LC cluster. Once the 2D-LC cluster is configured, the "available columns" pane to appear empty - preventing the user from adding columns to the worklist table. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Including a space character in data file path (including project name) breaks 2D-LC file splitter

Problem:

A defect has been discovered in the 2D-LC File splitter workflow where including a space character anywhere in the data file path will cause the Post-acquisition 2D-LC File splitter activity to crash with error:

Splitter: DA operation failed.

Temporary Solution:

Check that no space character exists anywhere in the data file path (particularly in the project name). If necessary, create a new project and copy methods/worklists/data files from the old project to the new project.

Fix Information:

Keyword: 

One-line Description:

Delete study permission governed by the person who launches study manager - not the user interacting with study manager

Problem:

In the TQ Acq 10.1 implementation of study manager - the "delete" study permission is only available to the Acq_Manager. The idea being that the user who can delete a pending study should be limited to the Acquisition manager. 

However - the check for this permission occurs against the user who launches Study Manager in the first place - not the user who is actively operating Study Manager.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Locked applications do not appear blurred when Windows OS thumbnail is enabled

Problem:

The Windows operating system's Taskbar Thumbnail feature allows a user to see the current state of any running application by hovering over the icon in the task bar. 

This preview defeats the blurring visual effect which MassHunter applies to locked application to obfuscate what could be sensitive data. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Issues with using keyboard shortcuts when filling out the sample position column in the worklist

Problem:

Users have noted that when using the "tab" key to navigate into the Sample Position field in the worklist - the first character typed into that field is not included in the entered text. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Switching worklists from dropdown in worklist table causes Activity Log to capture the wrong worklist name

Problem:

Simply loading one worklist, followed by another worklist - then running the second worklist causes the system logbook to report that you just ran the first worklist. 

For example - I created two worklists - 1Row.wkl containing 1 sample, and a 2Row.wkl with two samples.

I loaded 2Row.wkl (did not run it) then loaded 1Row.wkl then ran it.

The activity log reported that I ran 2Row.wkl

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Publish Format selection in Acq Method -> DA -> Quant -> tab is non-functional 

Problem:

In the MassHunter Acquisition method, under the DA section -> Quant - there exists a "Publish Format" selection which - in theory - allows the user to choose what final output is generated by the Quant reporting engine (PDF, CSV, etc). With Quant 11.1, this feature broke and will not be fixed. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Acquisition's lock screen remains on top above all other apps

Problem:

When the Acquisition lock screen is active - it is configured to sit on-top of all other applications, even when Acquisition is minimized. 

Temporary Solution:

Move the lock screen to the corner of you screen so as to avoid it.

Fix Information:

Keyword: 

One-line Description:

At symbol "@" appears in various actuals fields due to a localization issue in SFC driver

Problem:

A defect in the SFC driver causes the "at" symbol '@' to appear in multiple instrument parameters. This is caused by a fault in the localization of the strings associated with these SFC actuals - but it does not impact the accuracy of those values.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Loading invalid method in Acquisition yields unhelpful tooltip in worklist

Problem:

When you select a method in the Acquisition worklist - it checks to see if the appropriate info.xml is contained in that method. If it is missing - perhaps because the method is not an acquisition method but rather some other type of method (like a Quant reporting method) - the tooltip will simply read - "info.xml file does not exist in Acquisition method path". While this is not a particularly helpful message - it is accurate. 

Temporary Solution:

Make sure to select an appropriate Acquisition method in the acquisition worklist. 

Fix Information:

Keyword: 

One-line Description:

After deleting user defined column, worklist editing throws exception

Problem:

When deleting / removing user defined columns from the worklist table - further editing of the rows of that worklist may trigger a crash in the worklist table.

The crash will include the error message: "xxxxx is neither a DataColumn nor a DataRelation for table WorklistRow."

Here's an example workflow which will cause the crash: 

Create worklist with 3-4 samples
Add 3-4 user defined columns
Save worklist
Delete 2-3 user defined columns
Immediately click inside any cell of worklist

Temporary Solution:

The current workaround is to relaunch the UI where error is seen (e.g. Console \ Offline Worklist Editor \ DA Reprocessor), create a new worklist from default and do not add the columns intended to be deleted.

Fix Information:

Keyword: 

One-line Description:

Including a "." period character in a portion of the data file path causes the file to get stuck in the File Upload Queue - Networked Workstation

Problem:

A defect was found in the validation of data file paths which failed to ensure that no "." period characters are included in the data file path of any datafile in the worklist. Periods are illegal characters in ECM XT - so any file with a period in its path would get stuck in the File Upload Queue and have to be manually removed.

Temporary Solution:

Do not include "." period characters in your data file paths.

Fix Information:

Keyword: 

One-line Description:

Migration of .wkl worklists created in 10.x causes scripts to change position within the worklist

Problem:

A defect has been found in TQ Acq 12.0 which causes worklists created in 10.x which contain a script to change the position of the script in the worklist. Specifically - the script is seen jumping from the end of the worklist to the beginning. 

Temporary Solution:

Edit the worklist after it is imported to have script entries ordered correctly.

Fix Information:

Keyword: 

One-line Description:

Failed to retrieve permission 'Add script' for logged-in user

Problem:

In some circumstances, when a user opens the "Worklist run parameters" pane, an error message is encountered. The error reads: "Failed to retrieve permission 'add script' for logged-in user {username}".

This error should only be observed once.

Temporary Solution:

Close MassHunter Acquisition and click "close connection" in the OpenLab Control Panel. Reopen MassHunter and the error should not reoccur.

Fix Information:

Keyword: 

One-line Description:

Setting "Always use Default project" causes Acquisition to launch into the wrong project

Problem:

Have a system where you've previously opened Acquisition into a Project. I'll call it "Alpha".

In the OpenLab Control Panel - with all MH processes shutdown - create a new Project - I'll call it "Gamma".

In the instrument's view, edit an instrument and select the "Gamma" project in the "Default Project" field. Tick the setting "Always use Default Project."

Note that the Project field will now show "Gamma" as the selected project. 

Launch the instrument and observe that Acquisition launched into the "Alpha" project.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Hard to find 54-vial plate in "add multiple samples" workflow in Offline Worklist Editor

Problem:

Users have reported that it is too difficult to find the 54-vial plate option in the "add multiple samples" plate options in TQ Acq 12.0. 

Temporary Solution:

The plate is present - it's just in the PAL3 sampler section. 

Fix Information:

Keyword: 

One-line Description:

PAL 3 plate numbering in the "add multiple samples" dialog doesn't directly map to PAL3 method editor

Problem:

The plate numbering in the "Add multiple samples" dialog may not map to the same numbering used in the installed plates configured in the PAL 3 driver.  

Temporary Solution:

Once the samples are added to the worklist - correct the plate numbers in the worklist table manually. 

Fix Information:

Keyword: 

One-line Description:

Samples acquired out of order after "insert" and "Delete" edits to the worklist

Problem:

A user has reported that their TQ Acq 12 worklist was acquired out of order - and at no point did they use the "randomize" order functionality new to TQ 12. 

This occurred when one inserted and deleted rows from the worklist while not saving the worklist between those actions.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

File Splitter requires a 1D detector to work

Problem:

If a 2D-LC setup is used in which no 1D detector is configured, then the file splitter cannot work.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Changing the number of rows enabled during study submission leads to undesired outcomes in Study Manager

Problem:

During the worklist review stage of Study submission (in Study Manager) - changing the number of rows enabled causes two undesired outcomes:

1- the sample count shown in the pending studies tab is incorrect. It has not been updated for the change.

2- the activity log will record errors indicating: "could not find Worklist row for given Worklist row ID {GUID} 

Temporary Solution:

Simply ignore these undesired outcomes. 

Fix Information:

Keyword: 

One-line Description:

"View Data" button does not work if Project has space in the name

Problem:

In TQ Acq 12 and 12.1 - the "View Data" button should open a data file into Qual for review. However - if there is a space in the project path, this will fail with error.

Temporary Solution:

Open the data file in Qual directly - rather than using the "View Data" shortcut.

Fix Information:

Keyword: 

One-line Description:

Data fie Path length validation added in TQ Acq 12.0 and QTOF Acq 11.0 overly limiting

Problem:

In QTOF Acq 11 and TQ Acq 12.0 - a check was added to the worklist table which would prevent users from running samples if the path length specified for the data file name was too long. This was added to prevent a failure case which would occur when the path length specified by the user exceeded limits of the operating system. However - this limitation was found to be overly constraining and prevented previously working data file naming schemes used by customers. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Acquisition console crashes when using Japanese IME in Worklist Run Parameters Window

Problem:

A defect has been discovered in the Worklist Run Parameters that causes the Acquisition application to crash (close) without error when using the Japanese IME (Input Method Editor) in some situations. 

Temporary Solution:

As a workaround: Confirm the selected translation candidate by Enter key with each character input. Then input another Japanese word. 

Alternatively: Use the previous version of the Microsoft Japanese IME. 
1. Search "IME' on search box and select "日本語 IME 設定" (Japanese IME settings)
2. Click on "全般" (General)
3. Scroll down to the bottom in the 全般 window and switch from オフ(Off) to オン(On) for "以前のバージョンの Microsoft IME を使う" (Use Previous version Microsoft IME) under "互換性" (Compatibility)

Fix Information:

Keyword: 

One-line Description:

"Add multiple samples" dialog throws validation errors when sample name field contains colons and forward-backward slashes

Problem:

Colons and forward and backward slashes are valid characters for the sample name field. However, due to a defect in the "Add multiple samples" dialog, the software would throw a validation error if the sample name field contained either of these characters. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Data modified field not changing when modifying method in Acquisition

Problem:

A defect has been found in the File -> Open (method, worklist, etc) dialogues where the "Date Modified" column was not updating or reflecting changes made within the method. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Worklist run failed to start from first row in randomized worklist

Problem:

A defect has been found in the worklist table impacting worklists that have been extensively edited after being randomized. The defect causes acquisition to start from a random row of the worklist instead of the first row.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Worklist error occurs in DA reprocessor if Sample Audit trail is displayed for any data file in the DA Reprocessor worklist

Problem:

When a data file's sample audit trail is opened in an Audit Trail viewer- the sample audit trail cannot be modified by any other application. When running with the DA Reprocessor - the sample audit trail is updated. If the sample's audit trail is open in any other application (including the audit trail viewer in Acquisition) - the DA Reprocessor will fail when attempting to reprocess the sample in question. 

The error message seen may vary but one common error is: "Storage object is already disposed". 

Temporary Solution:

Close the audit trail for the sample and re-run the DA reprocessor.

Fix Information:

Keyword: 

One-line Description:

Worklists samples acquired out of order - not randomized

Problem:

A defect has been found in the worklist table where samples are not acquired in the displayed order. This issue is more frequent in worklists that have undergone extensive editing, such as adding, appending, inserting, randomizing, deleting, and reordering samples.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Acquisition method editor unloads method after sample run - leads users to think they cannot edit an existing method

Problem:

A defect was introduced in TQ Acq 12.0 and QTOF Acq 11.0 where the Acquisition method is unloaded from the method editor such that the software is no longer "editing" the method expected by the user. The method parameters are displayed - and changes can be made - but when the user clicks "Save" the software treats the save as a "Save as" action because it believes a new method is being created. If the user then selects the existing method on disk they believed they were editing - the software throws an error that a method cannot be overwritten. 

Temporary Solution:

One can simply re-load the method before making further edits. 

Fix Information:

Keyword: 

One-line Description:

"Index was outside the bounds of the array" error occurs when deleting rows of a randomized worklist

Problem:

It has been found that when deleting rows of a randomized worklist - the error "Index was outside the bounds of the array" may occur. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Unable to change default instrument configuration settings like pump pressure units

Problem:

A defect has been found in the Acquisition instrument configuration where settings changed from default by the user would be ignored by Acquistion on instrument launch. For example, if the user were to set the pump pressure unit from "Bar" to "PSI" - the UI would accept the setting change, but it would be ignored once acquisition launched - "Bar" would still be displayed. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Saving new worklist with full data file paths in data file name column causes the paths to disappear

Problem:

A defect was introduced in TQ Acq 12.1 which causes worklists that have a full data path defined in the "Data File" column to be replaced with just the data file name upon save.

Temporary Solution:

This issue does not occur if the worklist is saved FIRST before adding the data file paths. 

Fix Information:

Keyword: 

One-line Description:

Overlapped injection with wellplate autosamplers causes sample to be aspired twice, wasting sample volume

Problem:

A defect has been found in MassHunter Acq for LC/MS QTOF 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Scheduled tunes will not occur until Worklist Completion popup is acknowledged

Problem:

A defect was found in the scheduled tune functionality whereby scheduled tunes would not proceed unless and until the "Worklist Completed" popup was acknowledged and closed. This popup is displayed whenever a worklist is completed successfully. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

ResponseCheck sample type incorrectly removed from Acquisition Worklist sample type column

Problem:

The ResponseCheck sample type was incorrectly removed from TQ Acq 12.0 and 12.1 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Inserting a sample into the worklist table puts the new row into an unexpected location

Problem:

A defect has been identified in the worklist table. When inserting new rows (via right-click and selecting “insert sample”), the sample is placed in an unexpected row, either above or below the intended row.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Audit trail of method in Study reflects study version instead of source Acquisition method

Problem:

When creating a study where the methods used for that study are copied into the study container, the audit trail for those methods will indicate that they were copied from a method whose version does not exist. In fact, they are using the version of the study itself, rather than the source method. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Crash seen when launching Acquisition into project which had been duplicated in the Control Panel and then edited

Problem:

A defect was found in MassHunter Acquisition which caused the application to crash when launching into a project which had been duplicated from another project and then edited. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

In order to have "injection volume" "As Method" via CSV import, either leave entire column empty or use "-1" to indicate "as method"

Problem:

In order to get "as method" populated into the worklist table during a CSV -> Worklist import - use the token "-1" instead of the text "As method". 

Acquisition is expecting a numerical value for Inj Vol, and using "As method" as a text string will result in an error during import. 

Temporary Solution:

Use "-1" to signify "as method" for the injection volume column of an imported CSV sample list.

Fix Information:

Keyword: 

One-line Description:

User Defined Columns display name changed from previous "User Defined" to "Numeric" and "Text"

Problem:

A defect was introduced in QTOF Acq 11 and TQ Acq 12.0, causing the “User Defined” columns in the Add/Modify/Delete Columns dialog to be incorrectly renamed as “Numeric” and “Text” instead of “User Defined” and “User Defined X” (where X is an integer between 1 and 10). These columns must be named “User Defined” to ensure their contents map correctly into the Data Analysis applications.

Temporary Solution:

The user can simply edit the Display Name to ensure the column is properly labeled as "User Defined" and not "Numeric" or "Text". 

Fix Information:

Keyword: 

One-line Description:

Unable to import CSV with Sample Amount and Total Sample Amount populated

Problem:

A defect has been found which prevents the "Sample Amount" and "Total Sample Amount" values from properly being imported from a CSV or XLS into the Worklist table.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Error method on LC stack can cause a method change that does not get captured in the method's audit trail

Problem:

In the normal course - all changes to a method are documented in the method's audit trail. However - a defect has been uncovered which can lead to method changes which are not reflected in the method's audit trail. This occurs if a method is loaded on the instrument independently from Acquisition - for example if an error method is set on the LC stack. An error method is a method which is stored on the LC modules and is automatically loaded and applied whenever the instrument enters into an error state (leak detected, for example). When this occurs - the MassHunter method editor will immediately update to reflect the method changes that were applied to the LC stack. If the user then makes any changes in the Acquisition method, and then saves that method, only the changes that occurred by the user's direct action will be reflected in the audit trail. The changes which occurred because the LC stack loaded its error method will not be reflected in the method's audit trail. 

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

Intelligent Reflex method fields show method validation errors (red boxes) drawn around Quant methods after closing connection in Networked Workstation configuration

Problem:

In QTOF Acquisition 12.0 and later, as well as TQ Acquisition 12.0 and later, when operating in the Networked Workstation configuration, closing the instrument connection (including during a PC reboot) may cause the Acquisition method to show red validation errors around the Quant methods used in the Intelligent Reflex workflow upon relaunch.

Temporary Solution:

This issue does not affect worklist acquisition. You can continue to run or start your worklist using the existing methods, and everything will function correctly. If you wish to resolve the issue in the method editor, simply reselect the Quant methods in the browse dialogs.

Fix Information:

Keyword: 

One-line Description:

Worklist validation does not allow dilution factor values greater than 99,999.99

Problem:

A worklist validation check added in TQ Acq 12.1 and 12.2 prevents users from using dilution factors greater than 99,999.99. 

Temporary Solution:

The dilution factor can be corrected once the data is loaded in Quant. Quant supports dilution factors as large as 1E305. 

Fix Information:

Keyword: 

One-line Description:

Not possible to review audit trail of Worklist Template 

Problem:

A defect has been identified which prevents "reviewing" the audit trail of a Worklist Template. An error is thrown, "The audit trail for {WorklistTemplate} cannot be reviewed as it is either use or it needs to be reloaded to display newer entries. Reload the audit trail to continue with review."

Temporary Solution:

A suggested workaround is to remove any worklist templates that should not be used for routine operation out from the Project via Content Management. In this manner - routine operators will only be able to use templates that remain in the project structure.

Fix Information:

Keyword: 

One-line Description:

Red validation box does not get cleared when root data folder path is corrected

Problem:

In the worklist run parameters dialog, if the "root data folder" path is invalid - correcting the path by selecting the "..." browse button and picking a valid path does not immediately clear the red validation warning. 

Temporary Solution:

Simply click the "OK" at the bottom of the Worklist Run Parameters window will close the window if the path is valid - even if the red validation box is not cleared. 

Fix Information:

Keyword: 

One-line Description:

InstrumentStandby Script fails to turn TQ into standby mode

Problem:

A defect has been found in the InstrumentStandby script included with TQ Acq 12.2 and prior where the TQ is found to be pulled out of standby mode immediately after the script executes. This was caused by a timing flaw.

Temporary Solution:

n/a

Fix Information:

Keyword: 

One-line Description:

In DA Reprocessor, worklist containing intelligent reflex injctions may display injection volume "as method" while regular samples show actual injected volume

Problem:

In the DA Re-processor, when loading completed worklists - the "Injection Volume" shown should display the injection volume that was actually injected when the worklist was executed. In "As Method" cases, the actual injection volume information is found by looking up the content of the .d data file stored on the local file system or in Content Management (ECM XT). If the data file is missing, or otherwise cannot be found, the worklist will display "As Method" rather than the actual injection volume. 

A defect has been found in the look-up process for data files associated with injections automatically added by the Intelligent Reflex feature. The issue is caused by defective handling of the data file path string such that this look-up fails to find such samples. In these cases, the worklist table will simply display what was stored in the worklist itself - in this case, "As Method".

Temporary Solution:

As a workaround - the actual injection volumes injected for intelligent reflex samples can always be found by examining the individual data files in the various MassHunter data analysis applications. In MassHunter Qual, for example, you can view the actual injection volume in the Sample Information pane or in any printed report which includes the Injection volume parameter. In MassHunter Quant, the injection volume is a column that can be added in the Sample table. Similarly Quant includes the injection volume in many of the shipping Quant report templates. All of these will include the correct, actual injection volume for all samples.

Fix Information:

Keyword: 

One-line Description:

Not able to configure a single acquisition method to perform BOTH Iterative MS/MS and Blank Carryover - Second Pass quant method cannot be set

Problem:

A defect has been identified in the method validation logic when configuring an Acquisition method to run both Blank Carryover intelligent reflex and Iterative MS/MS simultaneously. When these workflows are enabled together, the system expects the "2nd Pass Quant Method" field to be set. However, the browser field is disabled, preventing selection of a method and ultimately blocking the method from being saved.

Temporary Solution:

There are two workarounds:

1.) Instead of using a single acquisition method to perform Iterative MS/MS AND the blank carryover workflow - set two separate methods. For example, use the "Save As" function to save the iterative MS/MS method as another name, then configure each method to perform ONLY Iterative MS/MS or Blank Carryover, not both. 

2.) Alternatively, to continue using a single Acquisition method, set the "Blank Carryover" workflow to "As Worklist". Then, define the blank carry over details in the worklist table itself, rather than as part of the Acquisition method. 

Fix Information:

Keyword: User Interface

One-line Description:

Method MRU grayed out, after optimizer run stopped manually and immediately click on new or open button of acquisition method pane.

Problem:

Method MRU grayed out, after optimizer run stopped manually and immediately click on new or open button of acquisition method pane.

Temporary Solution:

n/a

Fix Information:

Keyword: User Interface

One-line Description:

Method MRU grayed out, after optimizer run stopped manually and immediately click on new or open button of acquisition method pane.

Problem:

Method MRU grayed out, after optimizer run stopped manually and immediately click on new or open button of acquisition method pane.

Temporary Solution:

n/a

Fix Information: