Software Status Bulletin
ICP-MS MassHunter (G7201A/B/C) G7201A/B/C
Known Problem Report as of Mar 14 2017 10:27AM
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
KPR#:6
Invalid filenames for samples in sample list.
KPR#:8
"Run User Script" doesn’t work
KPR#:9
Preemptive rinse time is not reflected to Estimated time for batch
KPR#:10
Snapshot function does not work between different Hard Disk Drives
KPR#:41
Total Acq Time is not displayed correctly
KPR#:142
MassHunter lock up when a data file is overwritten.
KPR#:225
Real Time display for Spectrum is not shown in Method Automation
KPR#:230
Invalid pulse limit is used at some masses under specific conditions
KPR#:259
TRA acquisition error caused by integration time settings
KPR#:285
TRA data acquisition is terminated because of an error
KPR#:1
Paused Batch is resumed automatically when user ends Batch or Sample List editing mode
KPR#:4
Change user while acquiring TRA data causes crash
KPR#:11
Truncation of Legend in Stability Graph
KPR#:33
“UNKNOWN” appears when AUX Heater is set to “ICPMS" from GC panel
KPR#:12
Probe rinse (std) is not used in startup and hardware settings.
KPR#:66
"About" screen may not display correctly
KPR#:27
Real time display of queue is not updated if acquisition time is too short.
KPR#:46
Printer paper size mismatch leads to Report footer (page number and printed date) not printing
KPR#:19
Warning about exchanging EM stops all remaining queued Hardware Tasks
KPR#:15
Total acquisition time is not updated when a tune mode is added or removed. Keyword: Acquisition One-line Description:
KPR#:3
Click and drag sample list block for currently acquiring batch causes crash
KPR#:5
Importing tune mode overwrites analyte names in a batch.
KPR#:16
Copy, export and print functions on “Monitor” tab do not work.
KPR#:17
Probe rinse does not work if its speed value has been pasted.
KPR#:21
Copying and pasting of
KPR#:24
A vial number must be set for Auto tune in Startup, when "Auto tune before batch" is selected
KPR#:25
Unintentional TRA acquisition in narrow-peak (half mass) mode.
KPR#:29
Correction equations are deleted when corrected mass is removed.
KPR#:31
An incorrect message is displayed when you try to print a batch sent to queue.
KPR#:34
Select “Acq Parameters” tab or “DA Method” tab of Batch before using “Import from Existing Batch” function
KPR#:37
"Rinse after batch" does not work with ISIS-DS and ISIS Hydride generation.
KPR#:43
Tune Step mismatch
KPR#:45
Tune check for EPA method doesn't work with more than 3 mass signals
KPR#:47
Software terminated by clicking Sample List after changing Lens Type
KPR#:49
Tune pane freeze when you touch this pane during mode transition of gas mode
KPR#:50
Sample name protocol
KPR#:55
Sample loop cannot be filled with a user defined rinse solution with ISIS
KPR#:58
Delete Correction Equation but some correction masses remain in the Batch
KPR#:62
Problem with selection of prohibited masses in cool or hot plasma
KPR#:67
Exception on editing sample list in Batch pane while that batch is running in queue
KPR#:77
Sensitivity Oxide Ratio of Diagnosis does not show real time plot
KPR#:79
Untranslated string exists in Configure Batch Acquisition dialog
KPR#:81
Error : Measured P/A factor value is out of range
KPR#:87
Error by clicking Ratio (Oxide)/Masses after deleting all masses for a tune mode
KPR#:88
Sensitivity of CalStd is too low in High Energy He mode.
KPR#:91
Default value of "Conc." in "Set Tune Criteria" dialog box should be "1 (ppb)".
KPR#:92
Arrow button in Edit Ion Database does not work as expected
KPR#:94
Menu item to Export Tune signal plot may become grayed out
KPR#:96
"Expand Files" does not work correctly for some folders.
KPR#:100
Calibration Level Increments for non-calibraiton standard sample types with Fill Down
KPR#:101
Fill Down in Sample List may cause slow response
KPR#:104
Interference equations don't function correctly
KPR#:117
Unnecessary elements information is displayed
KPR#:120
Exception observed when "QC configuration pane" is saved
KPR#:128
MassHunter will be terminated by editing a batch with "Pause at Batch End" On
KPR#:133
Drag and drop in process order changes order of selected samples
KPR#:139
MassHunter is terminated when you edit elements in the batch created from a Preset Method
KPR#:140
Slow sample log table edits
KPR#:143
MassHunter is terminated when you edit elements in the batch created from a Preset Method
KPR#:146
Slow sample log table edits
KPR#:154
Exception observed when "QC configuration pane" is saved
KPR#:158
"Dilution" and "Final WT or Vol" cannot be pasted in Sample List table.
KPR#:169
Entered dilution value can be revert to the previous value in the Sample List
KPR#:174
MassHunter is terminated when filldown of ISTD is double-clicked
KPR#:177
Some frame border lines of the QC parameter table may be truncated
KPR#:179
The order of the columns is not changed in Sample List table
KPR#:181
Enter masses to perform the PA factor
KPR#:184
MassHunter is terminated if filldown is performed from Single Quad to MS/MS row
KPR#:186
Some LC parameters may revert to default values
KPR#:189
Firmware error (1004 Execution Error) always occurs at gas mode changes
KPR#:190
Excluding elements in Sublist may not work in MS/MS mode
KPR#:192
In setting a new batch from existing batch, single click to select the batch does not populate the file name
KPR#:193
User tune tool bar cannot be recovered
KPR#:202
Pre-emptive rinse is not functioning correctly with certain conditions
KPR#:204
Incorrect units of 3rd and 4th Cell Gasses
KPR#:221
All Parameters with Batch Wide Parameters
KPR#:247
Batch for 8800 may become corrupt.
KPR#:248
An ISIS2 UI is displayed even when instrument is 7900 on which only ISIS3 can be used.
KPR#:269
0 volt energy descrimination on 8800 H2 mode
KPR#:273
Default setting of signal monitor
KPR#:274
Exception on importing sample list
KPR#:278
Method Wizard may fail if "Automatic" mode is selected
KPR#:279
Sample Table is Greyed out and uneditable when creating a batch
KPR#:280
QC sample types not showing up in sample table
KPR#:292
Exception on unchecking "Use Block List" button on sample table
KPR#:306
Batch cannot be saved because of a validation error
KPR#:320
Some method validation error messages are duplicated.
KPR#:323
Batch saved under a batch cannot be found by customer
KPR#:334
Cannot save a batch because of validation error
KPR#:341
MassHunter crashes when starting Auto Tune under specific condition
KPR#:347
Object reference error after editing sample table
KPR#:361
Wait time for Mass Jump was incorrect in sNP analysis with 2 isotopes
KPR#:363
When the last sample before moving the periodic block has the outlier for Dilute-and Re-run, auto dilution factor will be applied to the 1st sample on the periodic block.
KPR#:366
"+86" is applied as mass shift though Predefined Shift "+85 ((NH3)5)" is selected
KPR#:368
Signal drift in H2 mode of 8900
KPR#:7
‘User Validation and Reason’ for Data Analysis only shows when batch was created with User Access Control “on”.
KPR#:14
User Access Control Audit Trail Map (ATM) Configuration, Help, About is blank
KPR#:175
IQT fails with an invalid file
KPR#:201
Data transfer to OpenLAB ECM server may fail.
KPR#:214
Base revision number is incorrect in IQT report.
KPR#:216
IQT may fail if Excel 2013 is installed
KPR#:239
ATM configuration issue on upgrading software
KPR#:240
"DA Analyst Name" is not searched by search function of Data Store
KPR#:244
Operator name on full quant report is wrong
KPR#:251
User cannot logon to MassHunter if they do not have access rights to delete files or folders in the ECM system. (For G7201C)
KPR#:252
MassHunter should evaluate access rights for ECM, not only based on system wide access rights but also LCDF specific access rights. (For G7201C)
KPR#:253
User cannot logon to MassHunter if they do not have access rights to delete files or folders in the ECM system.(For G7201B)
KPR#:254
MassHunter should evaluate access rights for ECM, not only based on system wide access rights but also LCDF specific access rights.(For G7201B)
KPR#:256
Download Error of requeued batch
KPR#:267
When User changed value of Abundance of denominator, the action is shown in Audit trail incorrectly.
KPR#:268
Action of "Sample List/ Insert function" is not registered in audit trail.
KPR#:271
When User changed value of Abundance of denominator, the action is shown in Audit trail incorrectly.(For B.01.03)
KPR#:272
Action of "Sample List/ Insert function" is not registered in audit trail.(For B.01.03)
KPR#:281
Using Data Store, user can not import tunes to user tune from the batch whose name include a character "#"
KPR#:295
Operation in a batch is not reflected to uploaded audit trail file until it is saved twice
KPR#:303
Error message on adding a batch to queue
KPR#:304
Queue error after sequence finishes
KPR#:307
Operation in a batch is not reflected to uploaded audit trail file until it is saved twice
KPR#:315
Operation in a batch is not reflected to uploaded audit trail file until it is saved twice
KPR#:317
There is a case Operator level user can use MassHunter as an Administrator
KPR#:321
Using ECM integration, no warning for renamed batch
KPR#:325
Malfunction of checking out files with Data Store integration
KPR#:327
User can unlock MassHunter using wrong password
KPR#:328
Some operations may cause an unintended checkout of Lock file in Data Store file system
KPR#:329
"Configure Compliance Administrator" Window does not warn wrong password
KPR#:331
Uploading fails without error when database is full
KPR#:336
UAC for "To add/delete annotation" does not work
KPR#:338
Error on acquiring full spectrum in user tune with SDA integration.
KPR#:339
Batches may corrupt using database integration - caused by P/A Factor report
KPR#:340
Batches may corrupt using database integration - caused by "Save as"
KPR#:343
Batch files created by "Method Automation" feature is not executable
KPR#:344
MassHunter C.01.03 cannot open the batch that is created by MassHunter C.01.02
KPR#:345
Batches may corrupt using database integration - caused by LIMS output
KPR#:346
Data file is not uploaded with P/A Factor Adjustment option
KPR#:348
When database integration is in use, MassHunter may crash on acquiring full spectrum.
KPR#:349
Batches may corrupt using database integration - caused by Export Diagnosis Report
KPR#:351
Batches may corrupt using database integration - caused by Advanced Batch Tune
KPR#:364
Exceptions related to audit trail file access occur when UAC is ON and "Edit and Requeue" is executed
KPR#:365
Instrument control uses a lot of memory on ending editing mode when SDA is integrated and Protect Local Data is enable
KPR#:367
In SDA integration mode, DA stops responding and sequence is halted between 200 - 300 samples.
KPR#:369
Function of Lock UI Time could not work during startup task.
KPR#:370
Error message of "Another logon process is not completed" may be shown when Lock UI Time is set.
KPR#:372
Instrument Control crashes when UAC is on and a batch is requeued in Queue pane
KPR#:373
Unauthorized user may be able to access to protected data folder in the case of database integration
KPR#:374
SDA database access authority control is not recognized correctly when you log on to MassHunter
KPR#:44
Point-to-Point correction fails to create corrected data
KPR#:64
Incorrect scale for QC Stability chart
KPR#:72
Untranslated string in configure quick batch report dialog
KPR#:74
SQ Factor for Calcium on He mode was wrong.
KPR#:80
Check box is slow to react
KPR#:93
Many analytes in calibration table may cause an error to load batch
KPR#:97
Chromatography integration parameter change is not reflected in result for Global Parameters by single-click
KPR#:102
ISTD settings of deleted analyte may remain in DA
KPR#:112
Inconsistent CPS values between Batch and Spectrum panes
KPR#:113
System is suddenly closed when generating a S/N report
KPR#:114
Sorting Calib Level is out of order
KPR#:116
Array.Sort...error is displayed when changing sample type in the Batch-at-a-glance
KPR#:118
On-line DA is terminated when click on spectrum during on-line data acquisition
KPR#:122
Slow creation of TRA based csv file using Export for each sample and tabchart scripts
KPR#:125
Drift Check > Reslope is not functional in Intelligent Sequence
KPR#:132
Data Analysis will be aborted when reslope is executed with VIS
KPR#:135
Excel sheet for chart will not be created for LabQC in Chinese MassHunter
KPR#:144
Parameter change may not be reflected in Chromatogram Data Analysis.
KPR#:145
Parameter change may not be reflected in Chromatogram Data Analysis.
KPR#:148
CPS counts may be different from the actual spectrum data
KPR#:149
Isotope template may not be applied
KPR#:150
Overflow error might be occurred when stability graph is drawn
KPR#:153
On-line DA is terminated when click on spectrum during on-line data acquisition
KPR#:156
ISTD may not be selected in Calibration pane
KPR#:168
Mass bias correction may not be correct
KPR#:171
Some conc. RSD are displayed with too many digits in Batch-at-Glance
KPR#:172
Some conc. RSD are displayed with too many digits in Batch-at-Glance
KPR#:182
Slope of the converted calibration curve would be incorrect if you edit a calibration curve of "Standard Addition"
KPR#:188
Background Subtraction for SemiQuant may not work correctly
KPR#:191
"bkg" cannot be entered to level table in FullQuant pane in Chinese version.
KPR#:199
Imported dilution parameter could mislead Quantitation Results
KPR#:208
Autoscale doesn't work properly in mass pair spectrum window.
KPR#:218
Interference correction doesn't reflect to corrected SemiQuant factor
KPR#:226
X scale by XY Auto Scale is too wide
KPR#:235
Stability graph drawing issue
KPR#:245
Background subtraction failed when "Process Batch" was performed
KPR#:246
Slope of the converted calibration curve would be incorrect if you edit a calibration curve of "Standard Addition"
KPR#:250
There are cases that SQ outlier is not displayed
KPR#:286
Wrong RSD for response ratio is given when "Ratio to ISTD" is selected as a backgroud subtruction type.
KPR#:287
BEC is not printed in calibration report sometimes
KPR#:298
When user rejects on calibration pane, RSD of ratio may become incorrect
KPR#:300
Error in S/N reporting for Chromatographic Data
KPR#:301
Correction equation is not applied correctly to calibration samples
KPR#:302
CPS for washout blank is not displayed
KPR#:305
RSD for Calibration curve is displayed as infinity
KPR#:311
Wrong behavior of "Set Specific Value" for ISTD
KPR#:312
Correction equations are not applied correctly
KPR#:313
ISTD is not displayed on the tool bar of Calibration pane
KPR#:319
Ghost peaks are drawn on chromatogram in MS-MS mode
KPR#:332
Crash when pasting into DA "Spike Amount" Column
KPR#:333
Manual integration fails
KPR#:362
Dilute and Rerun might not be executed correctly as 2nd Action on Failure when prepFAST is used.
KPR#:170
LC is in a constant error status when plasma is off
KPR#:206
Injector program for LC is not usable
KPR#:210
On-line HELP may be slow to respond with LC-ICP-MS
KPR#:213
Injector program for LC is not available.
KPR#:231
GC Integration does not work unless the GC has an auto-sampler.
KPR#:241
GC-ICP-MS data acquisition may stop by solvent peak
KPR#:258
Back injector is not usable without ALS Tray
KPR#:296
MH SW terminated when the column information was modified
KPR#:326
LC method can become wrong
KPR#:337
LC Status screen become uncontrollable
KPR#:13
Entered value beyond acceptable range of cell gas is canceled.
KPR#:22
Position of LC Method dialog
KPR#:28
ISIS configuration in Hardware overrides alternative sample intro set in Startup/Hardware Setting
KPR#:39
Entering a flow setting for 3rd cell gas is rejected in Maintenance screen
KPR#:48
Firmware Error message is displayed after correction of the original problem
KPR#:52
New default limit value of "Change Fore Line Pump Oil" in EMF
KPR#:53
Performance Report results and Hardware Values are not updated.
KPR#:54
Peri-pump time is applied even with Laser Ablation system configured
KPR#:56
P/A factor setting fails when one or more signals go over analog limit value
KPR#:57
I-AS always moves the tray to the escape position before moving the probe
KPR#:59
EM tune fails when small diameter torch is used
KPR#:61
MassHunter does not recognize I-AS after changing sample introduction method
KPR#:65
Peri Pump may keep rotating after plasma off
KPR#:68
"Define Wellplate" button is not located correctly.
KPR#:70
Misleading error message when a non-existing vial number is selected
KPR#:71
Visualization for Performance report does not work when it is executed in hardware task
KPR#:75
Torch goes way off x/y axis at torch/plasma correction
KPR#:76
PA factor history may not be displayed correctly
KPR#:83
Method window for LC 1200 is not properly displayed
KPR#:90
"Load Mass List from Method" function does not consider prohibited masses
KPR#:99
Ion Lens Voltage value may be displayed with too many digits in Performance Report
KPR#:111
Plasma Correction for hot plasma may fail
KPR#:123
Fault in plasma correction for cool plasma
KPR#:124
Failure of plasma correction for cool plasma
KPR#:127
Plasma cannot be put off right after ignition.
KPR#:134
Hardware Diagnosis report may fail selected with Include Batch Tune Data and Batch Tune Report
KPR#:137
Deleting mass during P/A factor acquisition may cause a software internal error
KPR#:138
MassHunter is terminated when Performance Report is clicked during Startup
KPR#:151
Evacuation assist valve and H2 stop valve are not closed when closing the cell maintenance mode
KPR#:152
MassHunter is terminated when Performance Report is clicked during Startup.
KPR#:166
"PA Factor Out of Range" is displayed during calibration
KPR#:173
G4226A autosampler configuration screen is too restricted and also poorly laid out
KPR#:195
Cannot change Seat Capillary setting for 1200 LC Autosampler
KPR#:196
It takes time to open Performance Report
KPR#:211
Prohibit Masses in S-lens configuration
KPR#:220
B2 for CapLC pump doesn't function
KPR#:222
ALS drop down menu could give an error
KPR#:227
Auto Config for LC modules might not work
KPR#:228
ICP-MS goes offline if sample introduction is changed
KPR#:237
EM Autotune doesn't refer to EM Tune parameter
KPR#:238
Discriminator autotune behavior problem
KPR#:299
ISIS3 Tune/ISTD selection valve problem
KPR#:354
8900 standard model cannot control 4th gas flow in standby mode
KPR#:371
OctPole RF Matching will fail after turning on the instrument
KPR#:106
Data is not properly exported in LC/MS format
KPR#:129
LabQCAddin can't be occasionally installed at updating from G7201A A.01.01 to A.01.02.
KPR#:131
BatchLog.xml is only uploaded to ECM at the batch creation
KPR#:157
BatchLog.xml is only uploaded to ECM at the batch creation
KPR#:160
Instrument Control is terminated when Time Format is changed with empty Performance Report pane
KPR#:161
Instrument Control is terminated when Time Format is changed with empty Performance Report pane
KPR#:209
Incorrect descriptions in On-line HELP and Manual about Timing of Acq Batch Audit Trail
KPR#:242
The Batches for organic solvent do not contain one for the 7900
KPR#:262
Wrong description for file upload timing in online help
KPR#:263
Missing description for uploaded file and timing in online help
KPR#:277
Wrong tune parameters are send when LA is used
KPR#:288
Wrong LC parameter is printed by print method feature
KPR#:289
LC Injection volume can become wrong value
KPR#:290
After installation of B.01.03 patch3, system become completely unusable
KPR#:294
With HiP sampler, user cannot control thermostat from method
KPR#:30
Element buttons on “Set Sublist of Acq Elements” dialog box does not work properly.
KPR#:32
Removing task while Vial at End is running causes software freeze
KPR#:85
"Start Sample List Edit mode" button will be disabled if double click acquisition order table
KPR#:95
Batch log cannot be printed
KPR#:107
System suddenly terminated when editing sample table in Queue
KPR#:110
MassHunter does not respond when ending editing mode of sample table in Queue
KPR#:119
Red cross during editing sample list in Queue
KPR#:121
MassHunter A.01.02 Patch 003 crashed when Whole List was clicked.
KPR#:126
Data acquisition is freezed when click Add to Queue
KPR#:155
Error by editing batch in edit mode during sample acquisition
KPR#:159
Error is occurred when Auto/semi auto tune before batch is selected without opening a batch
KPR#:164
MassHunter is terminated with error message
KPR#:185
Edit Sample List may not function
KPR#:187
Changing "Independent P/A Factors" while sequence is running may cause an exception
KPR#:198
MassHunter may have no response when a large number of tasks are deleted in the Queue.
KPR#:200
“Start Sample List Editing Mode” in Queue Pane doesn’t work during data acquisition
KPR#:203
A batch acquisition may be suspended with status in process.
KPR#:205
No H2 gas flows in H2 tuning mode in certain condition
KPR#:207
Data Acquisition is stopped by the Object reference ... error
KPR#:232
Sequence error seen after overnight queue run
KPR#:233
Sequence error because of sub list setting
KPR#:236
"Ratio" setting problem in "Real time display"
KPR#:243
Sequence intermittently stops using ISIS3
KPR#:255
Error count of QC error action is not cleared after the QC error check passes
KPR#:260
Wrong behavior of pause function
KPR#:261
Error count of QC error action is not cleared after the QC error check passes (For B.01.03)
KPR#:275
MassHunter has no feature to count QC error by sample types + bottles
KPR#:291
Wrong behavior of sample table editing mode
KPR#:308
Using 8800, sequence stops in tune mode transition
KPR#:309
Using 7700, sequence stops in tune mode transition
KPR#:318
Edit and requeue is impossible because of the attached error
KPR#:322
Edit and requeue imports extra tune files from User tune
KPR#:324
Freeze when you open the InstrumentControl
KPR#:330
Wrong behavior of peripump program
KPR#:342
Using ISIS3, sequence is halted because of vial# error
KPR#:350
Edit sample table may malfunction
KPR#:353
Fail count of "Dilution and Re-Run" is not reset when an acquired sample is changed
KPR#:355
Preemptive rinse would cause malfunction on data acquisition
KPR#:357
Sequence would be terminated by an error when Sublist is in use
KPR#:358
During batch sequence is running, correction equation might not be applied correctly when the setting on calibration pane is modified and then an acquired data file is imported.
KPR#:359
Pre-emptive rinse is not functioning correctly with certain conditions
KPR#:375
Instrument Control of MassHunter may freeze
KPR#:51
'Report Generate' makes an error, when Sample Name is blank.
KPR#:60
QC items are incorrectly labeled
KPR#:69
Incorrect table header in tune report
KPR#:105
Some blank lines may be printed in tune report.
KPR#:108
System terminated when printing QuickBatch report
KPR#:115
Some last digits may be truncated in detail format of calibration curve report
KPR#:162
Graph may not be displayed in Noise Report
KPR#:163
Graph may not be displayed in Noise Report
KPR#:183
MassHunter cannot generate sample reports with Concentration Replicates, slope, y-intercept and Ratio Replicates.
KPR#:197
Average count is not printed on the report by printing current signal
KPR#:212
Calculation of Oxide ratio value in tune report is incorrect.
KPR#:215
Quick Batch report may not work with SDA, ECM, or Data Store integration in a specific condition
KPR#:229
Report Designer is not opened properly
KPR#:234
"Generate selected sample" always prints the last sample only
KPR#:249
Number format problem of response ratio in full quant report.
KPR#:257
Sample WT/Vol and Final WT/Vol cannot be printed in C.01.01
KPR#:264
PDF output feature prints wrong "Use gas" flag
KPR#:265
Printing of conc problem when it is below min conc.
KPR#:266
Actual RT for chromatographic analysis is not printed in reports
KPR#:270
PDF output feature prints wrong "Use gas" flag(For B.01.03)
KPR#:276
Formatting final conc is not possible in reports
KPR#:282
Using report designer, input information might be reflected correctly
KPR#:283
Report designer ends by an exception
KPR#:293
Wrong unit for parameters when methods are printed
KPR#:297
Cannot generate EPA tune report.
KPR#:310
Problem with "Print current signal"
KPR#:316
Cannot generate EPA tune report
KPR#:335
Malfunction with the printer HP LaserJet M506
KPR#:23
“Select Monitored Masses” dialog box is not displayed if too many masses for P/A factor are set.
KPR#:89
Cannot edit mass for doubly charged ion in Startup parameters
KPR#:98
Deleting Hardware Optimization and aborting Startup may cause an error
KPR#:176
The order of the items in Startup sequence is not carried out as expected.
KPR#:219
Cancel Pausing Queue does not work for Startup tasks
KPR#:284
Putting startup items into queue might became impossible because of an error
KPR#:314
An extra rinse inserted into startup task when using 7800 plus ISIS3
KPR#:20
Range values of real time display are wrong in case auto scaling is applied.
KPR#:36
System crashes when "Print Current Signal" is executed
KPR#:38
Denominator mass is not printed in the current signal report
KPR#:40
Resolution/Axis peak is not displayed at the correct location
KPR#:42
Tune parameters cannot be set
KPR#:63
Error message when switch cell gas mode again during transition
KPR#:73
Unused masses displayed in semi autotune for Deflect lens in gas modes
KPR#:78
Full Spectrum from Diagnosis will store wrong Tune Step Number of Previous Tune.
KPR#:82
Wrong mass displayed during semi Auto Tune in No Gas mode (x-lens)
KPR#:84
Tune report in Queue uses incorrect tune parameters
KPR#:86
Tune report error when deleting all masses in a tune mode
KPR#:103
"Firm Error" might occur on "Start Signal Monitor" in Resolution/Axis Pane
KPR#:109
High RSD% results in H2 tune mode
KPR#:130
"Tune Check" is not printed in Batch Log.
KPR#:136
Reported items in Tune Report may differ between "in Queue" and "in Batch pane".
KPR#:141
HMI Autotune may fail.
KPR#:147
HMI Autotune may fail
KPR#:167
MassHunter may be frozen when cancel semi auto tune with custom tune settings
KPR#:178
"Introduce Tune solution" is prompted with GC
KPR#:180
"Invalid tune parameter name is specified." is displayed by changing EM parameters
KPR#:194
Exception on importing tune modes to user tune
KPR#:224
Set Acq Parameter for Manual Sensitivity Tune could be disappeared
KPR#:352
MassHunter may crash when customer input Q2 value in “Set Acq Parameters for Sensitivity”.
KPR#:356
Cannot perform autotune for batch in TRA mode
KPR#:360
Q-pole parameters are not reflected to EPA mode tune report
KPR#:6 Product:ICP-MS MassHunter (G7201A/B/C) G7201A/B/C A.01.01
Invalid filenames for samples in sample list.
Problem:
Sample acquisition running in queue is stopped if some specific control terms are used as filenames for samples. The issue is caused if any of the following file names are used for filenames in the sample list: con, prn, aux, nul, clock$, com0, com1, com2, com3, com4, com5, com6, com7, com8, com9, lpt0, lpt1, lpt2, lpt3, lpt4, lpt5, lpt6, lpt7, lpt8 and lpt9.
Temporary Solution:
Do not set the listed filenames for any samples in sample list.
Fix Information:
This was fixed in A.01.02.
Keyword: Acquisition
One-line Description:
"Run User Script" doesn’t work
Problem:
Action “Run User Script”, that can be chosen as action on failure in QC Parameters, doesn’t work for now. Although batch log shows “Run User Script” in Action on Failure column when the action is triggered, it behaves like “Next Sample” (does not take error action, and continues to next sample).
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Acquisition
One-line Description:
Preemptive rinse time is not reflected to Estimated time for batch
Problem:
Estimated time for batch, shown in status bar while batch execution, doesn’t reflect the setting of preemptive rinse. This can lead the batch execution may finish sooner than estimated time when using preemptive rinse.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01.
Keyword: Acquisition
One-line Description:
Snapshot function does not work between different Hard Disk Drives
Problem:
Taking snapshot of TRA data when the acquired batch is located in the different drive from the drive where ICP-MS MassHunter is installed causes the error message shown and importing the sample data to the batch fails.
Temporary Solution:
This issue does not occur if the batch is located in the same drive as where ICP-MS MassHunter is installed
Fix Information:
This was fixed in A.01.02.
Keyword: Acquisition
One-line Description:
Total Acq Time is not displayed correctly
Problem:
Actual acquisition time for one sample is longer than displayed time at Total Acq Time on Acq Parameters tab in Batch.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Acquisition
One-line Description:
MassHunter lock up when a data file is overwritten.
Problem:
Rename a batch from Save as, which was performed before. Run it and remove or add an element from element table after the run. Then run it again. Data Analysis is locked up and you can't close it.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Acquisition
One-line Description:
Real Time display for Spectrum is not shown in Method Automation
Problem:
Real Time display is not displayed in Method Automation if acquisition mode is Spectrum. It is displayed for TRA.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
Invalid pulse limit is used at some masses under specific conditions
Problem:
An invalid pulse limit value is applied to specific masses satisfying the following conditions: - 20 points/mass measurement - The measurement is taken at an adjacent mass pair including: 13, 14, 15, 205~255 - The integration time between each of the mass pair is different An example is: measuring 205 amu and 206 amu with 20pts/mass, integration time 20 sec for 205 and 2 sec for 206. If the above conditions are met, the lower mass (205 in the above example) might be measured by analog detector only mode, even if it does not hit the pulse detector limitation (c.a. 1e+6 cps).
Temporary Solution:
Use the same integration time for both masses.
Fix Information:
n/a
Keyword: Acquisition
One-line Description:
TRA acquisition error caused by integration time settings
Problem:
Using TRA, acquisition fails with an error saying "AcqAnalysisType is out of range" when integration time is between 3ms and 10ms.
Temporary Solution:
None
Fix Information:
This was fixed in C.01.01.03.
Keyword: Acquisition
One-line Description:
TRA data acquisition is terminated because of an error
Problem:
TRA data acquisition is terminated after acquisition of so many samples, displaying "Retrieving COM class factory for component with CLSID {AB851A8E-65DB-11D5-993B-0060B0C344A9} failed due to the following error: 8007045a A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A)".
Error message / Exception: Retrieving COM class factory for component with CLSID {AB851A8E-65DB-11D5-993B-0060B0C344A9} failed due to the following error: 8007045a A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A)
Temporary Solution:
Restart MassHunter software at least once a day. No need to restart PC, just MassHunter.
Fix Information:
This was fixed in C.01.02
Keyword: Batch
One-line Description:
Paused Batch is resumed automatically when user ends Batch or Sample List editing mode
Problem:
When “End Editing Mode” button in Batch pane or “End Sample List Editing Mode” button in Queue pane is pressed while the batch execution is paused at “” function line, the batch is resumed from the pause in addition to ending editing mode.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: Batch
One-line Description:
Click and drag sample list block for currently acquiring batch causes crash
Problem:
MassHunter crashes when you try to click and drag a cell in the sequence flow table (i.e. to change the position or order of a sample flow block), if the batch being edited is being acquired in the Queue. The other operations you can apply in editing mode do not cause the crash.
Temporary Solution:
Do not click and drag any blocks in the sequence flow table during editing of the currently acquiring batch.
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Importing tune mode overwrites analyte names in a batch.
Problem:
When importing "Tune mode" from source batch to destination batch, the analyte names in destination batch are overwritten by the ones in source batch.
Temporary Solution:
When you create destination batch, use Create from Existing batch in creating the batch, and import necessary tune mode from source batch. After that, select acquisition mass by using Periodic table instead of mass scale.
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Copy, export and print functions on “Monitor” tab do not work.
Problem:
On “Monitor” tab, “Copy,” “Export Selected Area,” “Print” and “Print Preview” menus are always disabled, and “Export Table” menu does not work.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Probe rinse does not work if its speed value has been pasted.
Problem:
On “PeriPump/ISIS” tab, the pump speed settings of rinse and probe rinse, or probe rinse (sample) and (std), are linked. The identical pump speed is applied to both the two linked settings. However, the identical value is not applied and probe rinse does not work if you copy and paste a value to the linked settings.
Temporary Solution:
Type a value to the linked settings of pump speed, instead of using paste.
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Copying and pasting oflines in the sample list table does not work.
Problem:
In the sample list table, you cannot copy and pastelines, although sample lines can be copied and pasted correctly.
Temporary Solution:
Insert functions individually by using “Insert Function” menu, instead of pasting the lines.
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
A vial number must be set for Auto tune in Startup, when "Auto tune before batch" is selected
Problem:
When "Auto tune before batch" is selected in "Configure Batch Acquisition”, but no vial is setup for Auto tune (in Startup), batch validation does not report an error, but an error occurs when the batch is added to the Queue.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Unintentional TRA acquisition in narrow-peak (half mass) mode.
Problem:
Narrow-peak mode is a feature intended only for spectrum acquisition, but TRA acquisition can be performed in the mode unintentionally by the following steps: 1. Turn on advanced acquisition option by “Configure MassHunter” dialog box. 2. Create a batch. 3. Set acquisition mode to spectrum. 4. Change resolution from standard to narrow. 5. Change acquisition mode to TRA.
Temporary Solution:
Select the acquisition mode (TRA or Spectrum) BEFORE selecting narrow-peak mode. Alternatively, change resolution of every tune mode to standard before you change acquisition mode from spectrum to TRA.
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Correction equations are deleted when corrected mass is removed.
Problem:
When a corrected mass is deselected from “Select Elements on Periodic Table” dialog box, the correction equation related to the mass is also deleted after you close the dialog box. This means you should manually re-enter the correction equation if you want to select the corrected mass again as an acquired mass.
Temporary Solution:
Apply sublists to sample list to exclude the corrected masses from the acquired mass list on acq parameters tab if you want to keep their correction equations.
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
An incorrect message is displayed when you try to print a batch sent to queue.
Problem:
When you try to print a batch sent to queue, an incorrect message is displayed if you select a cell on “Acq Parameters” tab. The message (which can be ignored) is: “This batch is added to Queue. Please start editing mode to edit the batch.” The same message is displayed when you execute menus such as “New Batch Folder,” “Export,” “Page Setup,” “Print Preview” and “Clear Error Log.”
Temporary Solution:
Ignore the message. Print, print preview and new batch folder functions works without any problems except the display of the message.
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Select “Acq Parameters” tab or “DA Method” tab of Batch before using “Import from Existing Batch” function
Problem:
When editing a new Batch and using the “Import from Existing Batch” function, if the Sample List is imported from the existing Batch while the “Sample List” tab is selected in the new Batch, MassHunter will crash. MassHunter will also crash if the Acq Method is imported from the existing Batch while the “Tune” tab is selected in the new Batch.
Temporary Solution:
There are several workarounds for this issue: a) The normal way to create a new Batch and apply information from an existing Batch is to create the new Batch using the “Batch New, Create from Existing Batch” function. If this process is used, the error does not occur. b) A second way to create a new Batch and apply information from an existing Batch is to use the “File, Save Batch As…” function. If this process is used, the error does not occur. c) If any tab other than “Sample List” or “Tune, Resolution/Axis” is selected in the new Batch when information is imported from the existing Batch, the error does not occur.
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
"Rinse after batch" does not work with ISIS-DS and ISIS Hydride generation.
Problem:
"Rinse after batch" feature in "Configure batch acquisition" does not work in case of ISIS-DS and ISIS Hydride genegation. In case of other applications of ISIS and without ISIS, it is OK.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Tune Step mismatch
Problem:
When a previously used batch was saved as a different name and then edited by adding a new tune step, some elements are not run in the selected mode.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.01 Patch 001.
Keyword: Batch
One-line Description:
Tune check for EPA method doesn't work with more than 3 mass signals
Problem:
EPA method requires that instrument status is checked by more than 3 mass signals. MassHunter can't handle more than 3 mass signals. Tune check functionality for EPA method does not meet their requirements in MassHunter A.01.01.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.01 Patch 001.
Keyword: Batch
One-line Description:
Software terminated by clicking Sample List after changing Lens Type
Problem:
Change lens type in the Hardware view and close the batch without saving. Then go to the Batch, the Acq Method and click the Sample List Tab. ICP-MS MassHunter is closed with the error message: "ICP-MS MassHunter encountered a problem and needs to close".
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Tune pane freeze when you touch this pane during mode transition of gas mode
Problem:
Tune pane at the batch freeze and task bar prompt "Not responding" when you touch any section of tune pane during the mode transition from H2 mode to nogas or He mode to Nogas mode. The MassHunter is back to normal if you wait for while but some customer may close the application or reboot the PC when such error occurred.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Sample name protocol
Problem:
You can only place a maximum of 10 continuous numeric characters in the sample name, if you place 11 you get an error, when you say fill down. See attachment. example 2011031101 (this is OK) 20110311012 (this fails) 20110311A01234 (this is OK) Customers will use the date 20110311, then you only have 2 more numbers available in the current sequence.
Temporary Solution:
If you use more than 10 continuous numeric characters in the sample name, you would need an alphabetical letter to add more numeric characters as example above.
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Sample loop cannot be filled with a user defined rinse solution with ISIS
Problem:
Sample loop cannot be filled with a user defined rinse solution with ISIS. The standard ISIS discrete sampling program doesn't have the capability.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.01 Patch 002.
Keyword: Batch
One-line Description:
Delete Correction Equation but some correction masses remain in the Batch
Problem:
Delete Corrction Equation settings from the Batch but some of Acquisition Settings still remain in the Acquisition Parameter setting. There are still some elements with brackets ([ ]) in the selected element window.
Temporary Solution:
Remove integration time/mass(sec) of them from the Acq Param window.
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Problem with selection of prohibited masses in cool or hot plasma
Problem:
When prohibited masses are selected in cool plasma, MassHunter does not save the changes, but defaults back to the hot plasma settings. The prohibited masses selected in “cool” are ignored and selection of additional prohibited masses is not allowed even after selecting "cool" as the plasma mode.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Exception on editing sample list in Batch pane while that batch is running in queue
Problem:
Exception on editing sample list in the Batch pane while that batch is running in the Queue. If the sample list of a batch is edited in the Batch pane while that sequence is running in the Queue task, an exception is frequently thrown, if the user switches between sample blocks quickly by clicking block names in "Sequence flow".
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Sensitivity Oxide Ratio of Diagnosis does not show real time plot
Problem:
Sensitivity Oxide Ratio function in Diagnosis cannot show real time plot.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Untranslated string exists in Configure Batch Acquisition dialog
Problem:
batch task>tool bar>configure batch acquisition>set rinse after batch sampleintroprocess is untranslated both the title of the column and tool tip.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Error : Measured P/A factor value is out of range
Problem:
The error message appeared in running #1 CALSTD and then the sequence was stopped.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Batch
One-line Description:
Error by clicking Ratio (Oxide)/Masses after deleting all masses for a tune mode
Problem:
In Tune report settings, exception is thrown on clicking "Ratio(Oxide)/Masses" after deleting all masses for a tune mode.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 001.
Keyword: Batch
One-line Description:
Sensitivity of CalStd is too low in High Energy He mode.
Problem:
Sensitivity of CalStd is too low in High Energy He (HEHe) mode. This can happen when HEHe and He modes are present in the batch acquisition parameters.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 001.
Keyword: Batch
One-line Description:
Default value of "Conc." in "Set Tune Criteria" dialog box should be "1 (ppb)".
Problem:
Current value is "10 (ppb)", but Agilent tune solution is 1ppb. User needs to change this value in every batch, that is very troublesome.
Temporary Solution:
The default concentration for the standard used in “Set Tune Criteria” is "10 (ppb)", but Agilent tune solution is 1ppb.
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Arrow button in Edit Ion Database does not work as expected
Problem:
Up/Down arrow buttons in Edit Ion Database do not work as expected. When you click on up-arrow, the focus will move down and vice versa.
Temporary Solution:
Use opposite arrow button or select mass using the mouse.
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Menu item to Export Tune signal plot may become grayed out
Problem:
In Tune tab of the Acquisition Batch, the Export Graph item in the right-click context menu may become grayed out during signal monitor.
Temporary Solution:
If the export tune signal plot menu item becomes greyed out, click another tab or change the scan type to reactivate the menu item.
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
"Expand Files" does not work correctly for some folders.
Problem:
Some folders cannot be extracted correctly by the "Expand File" function after following procedure. *Main Menu-->Tools-->click "Expand Files" *Select compressed file that was made before by clicking "Archive Files". *When files are extracted to optional file, "Icpreport" and "Interfer" folders cannot be extracted .
Temporary Solution:
Use an external tool to archive the folders .
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Calibration Level Increments for non-calibraiton standard sample types with Fill Down
Problem:
In the Sample List the "Level" information for each sample increments with the Fill Down option regardless of the sample type being selected as Sample or Calibration. This function should only be default for a "Calibration" sample type. Additionally, the dropdown option within the "Level" cell becomes not available when selecting a calibration sample type.
Temporary Solution:
Use Fill Down in Level column only for “Calibration” sample type.
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Fill Down in Sample List may cause slow response
Problem:
When you perform Fill Down for many Sample List lines in which SubLists are selected, it may cause slow response because of calculation of estimated acquisition time.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Batch
One-line Description:
Interference equations don't function correctly
Problem:
When using correction equations the extra masses are not added automatically when a correction is “ticked” on. Eg tick on the V correction but mass 53 is not automatically added to the method if it doesn’t exist already. The same error occurs when deselecting existing corrections, the extra masses needed for the correction are not deleted automatically. This can lead to errors such as “Mass X is not selected in tune NoGas although it is used in a correction”.
Temporary Solution:
When using correction equations, make sure that all masses required for the corrections are added to/removed from the acquisition, when correction equations are selected/deselected.
Fix Information:
n/a
Keyword: Batch
One-line Description:
Unnecessary elements information is displayed
Problem:
In Ion Database of Japanese version, when you select He as element and click "show element information", other unnecessary element information (i.e. K, Ca, etc.) will also be displayed. On the other hand, Li and higher elements don't have any information displayed.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Batch
One-line Description:
Exception observed when "QC configuration pane" is saved
Problem:
In QC configuration pane, Add Sample Type with ISTD for Category. Assign it as ISTD of "Sample". Then delete the Sample and close QC configuration pane with saving. Exception will be observed.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004.
Keyword: Batch
One-line Description:
MassHunter will be terminated by editing a batch with "Pause at Batch End" On
Problem:
MassHunter will be terminated suddenly by editing a batch with "Pause at Batch End" On. This was reported from a user but we can't reproduce the problem at Agilent.
Temporary Solution:
n/a
Fix Information:
Waiting for reoccurence and further information to reproduce this.
Keyword: Batch
One-line Description:
Drag and drop in process order changes order of selected samples
Problem:
When multiple sample lines are selected for drag and drop in process sample order, the order of the selected lines changes when the samples are dropped. For example sample list contains samples 001 to 005. Select samples 004 and 005 and drag and drop to the start. Instead of the new order being 004, 005, 001, 002, 003, it becomes 005, 004, 001, 002, 003. Samples lines 004 and 005 are reversed from the original order. Also, there is no highlight to show where the selected lines will be inserted.
Temporary Solution:
There is a workaround. If you want to insert in the order 003, 004 and 005, please select the sample line in the order 005, 004, 003.
Fix Information:
This was fixed in B.01.02.
Keyword: Batch
One-line Description:
MassHunter is terminated when you edit elements in the batch created from a Preset Method
Problem:
A batch is created from a preset method. Add or remove some elements and edit the integration time for some elements in the batch. Remove a tune mode. Then edit/fill down integration time in a tune mode, then MassHunter is suddenly terminated.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 5.
Keyword: Batch
One-line Description:
Slow sample log table edits
Problem:
When User Access Control pack software is turned on, it takes a long time to add or delete lines in Sample Log Table in Batch.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 5.
Keyword: Batch
One-line Description:
MassHunter is terminated when you edit elements in the batch created from a Preset Method
Problem:
A batch is created from a preset method. Add or remove some elements and edit the integration time for some elements in the batch. Remove a tune mode. Then edit/fill down integration time in a tune mode, then MassHunter is suddenly terminated.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Batch
One-line Description:
Slow sample log table edits
Problem:
When User Access Control pack software is turned on, it takes a long time to add or delete lines in Sample Log Table in Batch
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Batch
One-line Description:
Exception observed when "QC configuration pane" is saved
Problem:
In QC configuration pane, Add Sample Type with ISTD for Category. Assign it as ISTD of "Sample". Then delete the Sample and close QC configuration pane with saving. Exception will be observed.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Batch
One-line Description:
"Dilution" and "Final WT or Vol" cannot be pasted in Sample List table.
Problem:
"Dilution" and "Final WT or Vol" cannot be pasted in Sample List table.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Batch
One-line Description:
Entered dilution value can be revert to the previous value in the Sample List
Problem:
When you enter a dilution value to the Dilution column in the Sample List, the value would be revert to the previous value only when you double click the cell. If the previous value is blank, it would be "1".
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Batch
One-line Description:
MassHunter is terminated when filldown of ISTD is double-clicked
Problem:
MassHunter is terminated when filldown of ISTD is double-clicked
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Batch
One-line Description:
Some frame border lines of the QC parameter table may be truncated
Problem:
When you print the QC parameter table, some frame border lines may be truncated.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
The order of the columns is not changed in Sample List table
Problem:
In the Sample List, right click and select "Configure Table columns" and "Add/Remove Columns" window is displayed. Change the order of table columns but it is not reflected in the Sample List.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Enter masses to perform the PA factor
Problem:
You might have the message, "Enter masses to perform the PA factor" when you run a batch with P/A factor adjustment turned on in the batch. This could happen in a batch with multi-tune mode settings.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02 Patch 1.
Keyword: Batch
One-line Description:
MassHunter is terminated if filldown is performed from Single Quad to MS/MS row
Problem:
In Acquisition table, when you filldown some lines from Single Quad row to MS/MS row in Single Quad tune mode column, MassHunter is terminated.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02 Patch 1.
Keyword: Batch
One-line Description:
Some LC parameters may revert to default values
Problem:
When you import from Existing Batch and run it, some LC parameters may revert to their default values. This happens if you use [File] > [Import from Existing batch].
Temporary Solution:
Use [File] > [New Batch] > [Existing Batch]
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Firmware error (1004 Execution Error) always occurs at gas mode changes
Problem:
Firmware error (1004 Execution Error) always occurs at gas mode changes. MassHunter is not stopped by the error but the message is just logged to error log. ICP-MS works correctly even the message is displayed.
Temporary Solution:
Neglect the error message.
Fix Information:
This will be fixed in a future revision.
Keyword: Batch
One-line Description:
Excluding elements in Sublist may not work in MS/MS mode
Problem:
When you uncheck "Set Sublist of Acq Elements" to exclude elements in MS/MS mode, the masses will be acquired. The function works fine in Single Quad mode.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Batch
One-line Description:
In setting a new batch from existing batch, single click to select the batch does not populate the file name
Problem:
When you create a new batch from Existing batch, single click doesn't select the batch.
Temporary Solution:
Double click or press open button to select the batch.
Fix Information:
This was fixed in C.01.01.
Keyword: Batch
One-line Description:
User tune tool bar cannot be recovered
Problem:
If Usertune is configured we see 2 toolbars under UserTune: The first one can be removed by right-click and de-selecting it and re-activated via Tools-Tool Bars-Task Settings. If the second toolbar is removed (also possible via right-click and de-selecting) You cannot re-activate it via Tools-Tool Bars-User Tune Settings.
Temporary Solution:
Delete the Application data which are located at: C:\Users\\AppData\Roaming\Agilent_Technologies,_Inc\IcpInstControl.exe\...
Fix Information:
n/a
Keyword: Batch
One-line Description:
Pre-emptive rinse is not functioning correctly with certain conditions
Problem:
This occurs in very limited range of "Start rinse before acquisition complete" in preemptive rinse parameter. It was only occured when the value is 44, 45, 46, or 47 sec with a tested batch file. It may results in wrong quantitation value. Because the defect cause change of peri pump speed while acquisition is going on.
Temporary Solution:
Adjust "Start rinse before acquisition complete" setting so that start of rinse step does not overlap with tune mode transition.
Fix Information:
This was fixed in B.01.03.
Keyword: Batch
One-line Description:
Incorrect units of 3rd and 4th Cell Gasses
Problem:
Units of 3rd and 4th gasses are displayed (and printed) as "mL/min" in Ramp cell gas result dialog box and its printing function. It should be "%".
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Batch
One-line Description:
All Parameters with Batch Wide Parameters
Problem:
If 'Batch Wide Parameters' are selected for parameters under Plasma, and then 'All Parameters' is switched off, the user cannot check 'All Parameters' without first deselecting the Batch Wide Parameters that were set.
Temporary Solution:
Deselect 'Batch Wide Parameters' before checking 'All Parameters'
Fix Information:
n/a
Keyword: Batch
One-line Description:
Batch for 8800 may become corrupt.
Problem:
Batch for 8800 may become corrupt. It results in software freeze after applying DA method or missing semi quant analyte in the batch table.
Temporary Solution:
Create a new batch in DA, import the samples. Need to input DA method again same as original one.
Fix Information:
n/a
Keyword: Batch
One-line Description:
An ISIS2 UI is displayed even when instrument is 7900 on which only ISIS3 can be used.
Problem:
Parameter for ISIS2 is displayed in "Set rinse after batch" dialog box even when instrument is 7900.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Batch
One-line Description:
0 volt energy descrimination on 8800 H2 mode
Problem:
When a batch is created from 8800 Preset method; Generic Method → General Purpose(8800), wrong value is applied for energy descrimination. Actually applied value become 0V while the dispalyed value on Tune screen shows 3V.
Temporary Solution:
Manually set the value on tune screen.
Fix Information:
This was fixed in C.01.01 Patch 4
Keyword: Batch
One-line Description:
Default setting of signal monitor
Problem:
The default settings of the signal monitor for the all masses are desired to be disable in the all preset methods. The signal monitor is carried out with TRA, and all the monitored masses are measured in both pulse and analog mode for a long 0.1sec during the first scan even if the signals are very high counts. That can shorten the EM life much.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Batch
One-line Description:
Exception on importing sample list
Problem:
When user try to import sample list from Excel file, application dies with the attached exception. Message of the exception says "1: 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine" . Error message / Exception: 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Batch
One-line Description:
Method Wizard may fail if "Automatic" mode is selected
Problem:
If "Automatic" mode is selected, method Wizard may fail displaying "Hardware Error". This happens when multiple reported masses are selected in semi qualt global parameters. Error message / Exception: The input sequence contains more than one element.
Temporary Solution:
Do not set multiple masses as reported mass.
Fix Information:
This was fixed in C.01.02
Keyword: Batch
One-line Description:
Sample Table is Greyed out and uneditable when creating a batch
Problem:
The sample table click buttons "use block list' and 'import sample table' are greyed out and no spreadsheet is shown in the window. Which does not allow the user to enter or edit sample table information.
Temporary Solution:
(1) Open any batch whose sample table is not empty. (2) Goto "Sample List" tab and turn off "Whole List" switch.
Fix Information:
This was fixed in C.01.02
Keyword: Batch
One-line Description:
QC sample types not showing up in sample table
Problem:
When a QC configuration is imported into a batch, replacing the existing QC configuration, the QC types from the original configuration only show up in the sample table for periodic QC when selecting the sample type for 'reset'.
Temporary Solution:
This can be fixed, but only by saving the batch (with the incorrect sample types in the 'Reset by' box) then exiting the software and re-entering the batch.
Fix Information:
This was fixed in C.01.02
Keyword: Batch
One-line Description:
Exception on unchecking "Use Block List" button on sample table
Problem:
Application may end abnormally by an exception on unchecking "Use Block List" button on sample table. Error message / Exception: An item with the same key has already been added.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Batch
One-line Description:
Batch cannot be saved because of a validation error
Problem:
ISIS3 does not require tune vial number. But method validation generates an error by mistake when the number is not specified. Then users cannot save the batch. Error message / Exception: "Auto/semi auto tune before batch" option is selected in "Configure Batch Acquisition" but no Tune Vial.
Temporary Solution:
Follow the steps. 1) Change Sample Introduction to General. 2) Set any tune vial# for Batch Task 3) Change Sample Introduction to "ISIS DS" again. 4) Save the batch. (The issue does not occur.)
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Batch
One-line Description:
Some method validation error messages are duplicated.
Problem:
When # of masses in a tune step become zero as a result of application of sub list, the method validation message for the situation is displayed in duplicate. Error message / Exception: There is no acquired masses in tune step [Tune step name] because specific masses are rejected by sublist
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Batch
One-line Description:
Batch saved under a batch cannot be found by customer
Problem:
If a batch is accidentally created under other batch, it is not accessible.
Temporary Solution:
Copy the batch to correct location.
Fix Information:
This was fixed in C.01.03
Keyword: Batch
One-line Description:
Cannot save a batch because of validation error
Problem:
When ISIS-DS is in use, software may wrongly display method validation error. User cannot save the batch because of the error. Error message / Exception: Specified vial position of Loop Wash in ‘Set Rinse After Batch’ dialog box does not match the current autosampler configuration.
Temporary Solution:
Do not use "Rinse After Batch". Do not select "Home" or "Rinse port " as Opt Loop Wash Vial#.
Fix Information:
This was fixed in C.01.03
Keyword: Batch
One-line Description:
MassHunter crashes when starting Auto Tune under specific condition
Problem:
MassHunter may crash when starting Auto Tune when Advanced Acquisition option is in use.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Batch
One-line Description:
Object reference error after editing sample table
Problem:
Object reference error after editing sample table. (1) Add the batch to queue. (2) While data acquisition of tune check report is going on, double click the batch in queue table to display sample table. (3) Start editing mode in queue pane. (4) Add some samples. (5) End editing mode. Then error “Object reference not set to an instance of an object” is generated.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch
Keyword: Batch
One-line Description:
Wait time for Mass Jump was incorrect in sNP analysis with 2 isotopes
Problem:
Wait time for Mass Jump was incorrect in sNP analysis with 2 isotopes.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Batch
One-line Description:
When the last sample before moving the periodic block has the outlier for Dilute-and Re-run, auto dilution factor will be applied to the 1st sample on the periodic block.
Problem:
When the last sample before moving the periodic block has the outlier for Dilute-and Re-run, auto dilution factor will be applied to the 1st sample on the periodic block.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Batch
One-line Description:
"+86" is applied as mass shift though Predefined Shift "+85 ((NH3)5)" is selected
Problem:
"+86" is applied as mass shift though Predefined Shift "+85 ((NH3)5)" is selected.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Batch
One-line Description:
Signal drift in H2 mode of 8900
Problem:
Signal drift occurs in H2 mode of 8900. The drift goes away when positive Axial Acceleration is applied.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Compliance
One-line Description:
Change user while acquiring TRA data causes crash
Problem:
Executing ‘Change User…’ function while acquiring TRA data causes ICP-MS MassHunter application to crash.
Temporary Solution:
Do not change user during acquisition when acquiring TRA data. Change user while acquiring Spectrum data does not cause the application to crash.
Fix Information:
This was fixed in A.01.02.
Keyword: Compliance
One-line Description:
‘User Validation and Reason’ for Data Analysis only shows when batch was created with User Access Control “on”.
Problem:
When a batch (analysis file) is created with User Access Control (UAC) switched off, and then UAC is turned on after the batch is created, even if Audit Trail Map (ATM) is configured so that ‘User Validation and Reason’ is required to an action, the user will not be asked ‘User Validation and Reason’ in Data Analysis. ‘User Validation and Reason’ is asked only for a batch which is created with UAC switched on.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: Compliance
One-line Description:
User Access Control Audit Trail Map (ATM) Configuration, Help, About is blank
Problem:
In Audit Trail Map (ATM) Configuration for User Access Control (UAC), when you select [Help] – [About Quantitative Analysis…], nothing is displayed.
Temporary Solution:
If you would like to check the software revision, open data analysis software or ICP-MS instrument Control software and click [Help] – [About…]
Fix Information:
This was fixed in B.01.02.
Keyword: Compliance
One-line Description:
IQT fails with an invalid file
Problem:
IQT fails to report invalid file due to "checksum mismatch". The reported file is "masshunter reporting icpms.config". This file is modified when a user change something in a report template. IQT should not check with checksum of this file.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Compliance
One-line Description:
Data transfer to OpenLAB ECM server may fail.
Problem:
During a batch running, data transfer to the OpenLAB ECM server may fail although the data is stored at a temporaly location. This could be happened by clearing folder path setting for ECM server in the User Access Control pack software. There are three possible cases: Case 1) User cancels Folder picker dialog form ECM API that will be called from 'Change User Access Control'. Case 2) User accepts empty of Folder Path text box by OK button of 'Change User Access Control' even if ECM Integration check box is checked. Case 3) User specify different server including capital size when logins to MH from the specified server name by 'Change User Access Control'.
Temporary Solution:
Avoid operations case1 to 3.
Fix Information:
This will be fixed in a future revision.
Keyword: Compliance
One-line Description:
Base revision number is incorrect in IQT report.
Problem:
C.01.01 is printed as base revision number in IQT report. The correct revision information is B.01.03 Build 393.8.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 1.
Keyword: Compliance
One-line Description:
IQT may fail if Excel 2013 is installed
Problem:
ICP-MS MassHunter B.01.02 with Patch 2 supports both Excel 2010 and Excel 2013. If Excel 2013 is installed, Installation Qualification Tool (IQT) may fail with following error: Required registry entries are not found, so the qualification has been ABORTED. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Common\InstallRoot
Temporary Solution:
This is a known issue with IQT reference file and has no impact on the installation or operation of ICP-MS MassHunter software.
Fix Information:
This will be fixed in a future patch.
Keyword: Compliance
One-line Description:
ATM configuration issue on upgrading software
Problem:
On upgrading MassHunter software to newer version, if new items have been included in the ATM configuration in the new software, the new items are not displayed in the ATM configuration list after upgrading software.
Temporary Solution:
Delete c:\Program Files (x86)\Agilent\ICPMH\Bin folder, between uninstallation of older one and installation of newer one.
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: Compliance
One-line Description:
"DA Analyst Name" is not searched by search function of Data Store
Problem:
"Analysis File"->"DA Analyst Name" is not searched by search function of Data Store
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Compliance
One-line Description:
Operator name on full quant report is wrong
Problem:
Operator name on full quant reports which are generated by CRE is wrong and it is always icpmhsuperuser in case of data store integration
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: Compliance
One-line Description:
User cannot logon to MassHunter if they do not have access rights to delete files or folders in the ECM system. (For G7201C)
Problem:
From MassHunter B.01.03, the software has been modified to check user access rights for the ECM database at the time of logging on to MassHunter. The purpose is to avoid the following case: If user has no access rights to upload, uploading fails at the timing when data has been acquired and the system tries to upload the data. This means the data exists in locally but does not exist in the server. This is a mismatch. To prevent such a case, the software has been modified to check rights to upload on logging on to MassHunter. But, in the case of ECM, not only uploading but also the rights listed below are checked. This is a problem because it includes rights to delete. This means that anyone who can logon to MassHunter has access rights to delete files and folders in the ECM system. Content: File - Add Content: File - Delete Content: Folder - Add Content: Folder - Delete Content: Folder - Edit
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Compliance
One-line Description:
MassHunter should evaluate access rights for ECM, not only based on system wide access rights but also LCDF specific access rights. (For G7201C)
Problem:
ECM system has two ways to grant access rights to users. One is system wide rights and the user gets access rights for any L/C/D/F layer. The other is L/C/D/F specific rights and the user gets access rights for specific L/C/D/F layers. MassHunter does not evaluate the latter kind of access rights, then such user cannot logon to the MassHunter software.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Compliance
One-line Description:
User cannot logon to MassHunter if they do not have access rights to delete files or folders in the ECM system.(For G7201B)
Problem:
From MassHunter B.01.03, the software has been modified to check user access rights for the ECM database at the time of logging on to MassHunter. The purpose is to avoid the following case: If user has no access rights to upload, uploading fails at the timing when data has been acquired and the system tries to upload the data. This means the data exists in locally but does not exist in the server. This is a mismatch. To prevent such a case, the software has been modified to check rights to upload on logging on to MassHunter. But, in the case of ECM, not only uploading but also the rights listed below are checked. This is a problem because it includes rights to delete. This means that anyone who can logon to MassHunter has access rights to delete files and folders in the ECM system. Content: File - Add Content: File - Delete Content: Folder - Add Content: Folder - Delete Content: Folder - Edit
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Compliance
One-line Description:
MassHunter should evaluate access rights for ECM, not only based on system wide access rights but also LCDF specific access rights.(For G7201B)
Problem:
ECM system has two ways to grant access rights to users. One is system wide rights and the user gets access rights for any L/C/D/F layer. The other is L/C/D/F specific rights and the user gets access rights for specific L/C/D/F layers. MassHunter does not evaluate the latter kind of access rights, then such user cannot logon to the MassHunter software.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Compliance
One-line Description:
Download Error of requeued batch
Problem:
Using Data Store, Batch that has been requeued cannot be downloaded from server.
Temporary Solution:
Use "save as" and manually add the batch to queue, instead of requeue function.
Fix Information:
Fixed by Data Store A.02.02. No change on MassHunter side.
Keyword: Compliance
One-line Description:
When User changed value of Abundance of denominator, the action is shown in Audit trail incorrectly.
Problem:
When User changed value of abundance of denominator to A from B on Isotope Ratio method table ,the action is shown in Audit trail as follows: Set abundance=A for denominator of analyte X (tun step=1 mass=XX); Previous Value =A It shoud show "Previous Value =B".
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 4
Keyword: Compliance
One-line Description:
Action of "Sample List/ Insert function" is not registered in audit trail.
Problem:
Action of "Sample List/ Insert function" is not registered in "C:\ICPMH\1\Data\*.b\Audittrail\acqbatch.instctrol.audit.xml".
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 4
Keyword: Compliance
One-line Description:
When User changed value of Abundance of denominator, the action is shown in Audit trail incorrectly.(For B.01.03)
Problem:
This is a copy of KPR #267(C.01.01) for B.01.03. When User changed value of abundance of denominator to A from B on Isotope Ratio method table ,the action is shown in Audit trail as follows: Set abundance=A for denominator of analyte X (tun step=1 mass=XX); Previous Value =A It shoud show "Previous Value =B".
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 4
Keyword: Compliance
One-line Description:
Action of "Sample List/ Insert function" is not registered in audit trail.(For B.01.03)
Problem:
This is a copy of KPR #268(C.01.01) for B.01.03. Action of "Sample List/ Insert function" is not registered in "C:\ICPMH\1\Data\*.b\Audittrail\acqbatch.instctrl.audit.xml".
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 4
Keyword: Compliance
One-line Description:
Using Data Store, user can not import tunes to user tune from the batch whose name include a character "#"
Problem:
Using Data Store, user can not import tunes to user tune from the batch whose name include a character "#".
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Compliance
One-line Description:
Operation in a batch is not reflected to uploaded audit trail file until it is saved twice
Problem:
Operation in a batch is not reflected to uploaded audit trail file until it is saved twice. (1) Operate something in DA (Operation A) (2) Save the batch, then analysis file and audit trail is uploaded. (3) Download the batch (4) Operate something in DA (Operation B) (5) Save the batch, then analysis file and audit trail is uploaded. (6) Download the batch (7) Audit trail in the batch downloaded at step(3) does not include Operation A (8) Audit trail in the batch downloaded at step(6) includes Operation A. But does not include Operation B.
Temporary Solution:
None
Fix Information:
This was fixed in B.01.03.05
Keyword: Compliance
One-line Description:
Error message on adding a batch to queue
Problem:
If Data Store integration is in use, error message "Could not access Data Store server or not found batch" may be displayed after a batch is added to queue. This occurs when batch is added to queue immediately after acquisition of the previous batch finished. Error message / Exception: Could not access to Data Store server or not find batch ’ [Name of the batch]’ Make sure server status and existence of batch ’ [Name of the batch]’ on server.
Temporary Solution:
Wait a while before adding to queue.
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Compliance
One-line Description:
Queue error after sequence finishes
Problem:
If Data Store integration is in use, a queue error message "Fail to upload to Database the path is not of a legal form" may displayed at the end of sequence run. Error message / Exception: Failed to upload to Database. The path is not a legal form.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Compliance
One-line Description:
Operation in a batch is not reflected to uploaded audit trail file until it is saved twice
Problem:
(1) Operate something in DA (Operation A) (2) Save the batch, then analysis file and audit trail is uploaded. (3) Download the batch (4) Operate something in DA (Operation B) (5) Save the batch, then analysis file and audit trail is uploaded. (6) Download the batch (7) Audit trail in the batch downloaded at step(3) does not include Operation A (8) Audit trail in the batch downloaded at step(6) includes Operation A. But does not include Operation B.
Temporary Solution:
Always save batches twice
Fix Information:
This was fixed in A.01.02 Patch 6
Keyword: Compliance
One-line Description:
Operation in a batch is not reflected to uploaded audit trail file until it is saved twice
Problem:
(1) Operate something in DA (Operation A) (2) Save the batch, then analysis file and audit trail is uploaded. (3) Download the batch (4) Operate something in DA (Operation B) (5) Save the batch, then analysis file and audit trail is uploaded. (6) Download the batch (7) Audit trail in the batch downloaded at step(3) does not include Operation A (8) Audit trail in the batch downloaded at step(6) includes Operation A. But does not include Operation B.
Temporary Solution:
Save the batch twice.
Fix Information:
This was fixed in C.01.03
Keyword: Compliance
One-line Description:
There is a case Operator level user can use MassHunter as an Administrator
Problem:
There is a case Operator level user can use MassHunter as an Administrator. (1) Logon to MassHunter as a member of ICPMHAdmin. (2) Wait until UI is locked by time-based lock. (3) Unlock software as a member of ICPMHOperators. (4) Currently logging on user is still the user of (1) and he can operate as an administrator
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Compliance
One-line Description:
Using ECM integration, no warning for renamed batch
Problem:
Using ECM integration, changing batch name through ECM web client is not supported. But if it has been done, software displays no warning.
Temporary Solution:
Prohibit the operation.
Fix Information:
This was fixed in C.01.03
Keyword: Compliance
One-line Description:
Malfunction of checking out files with Data Store integration
Problem:
Using Data Store, Agilent\ICPMH\1\_occupationlist.bin incidentally becomes corrupt, software malfunctions. Automated countermeasure to recover from such a situation is required.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Compliance
One-line Description:
User can unlock MassHunter using wrong password
Problem:
(1)Wait until MH is time-based locked. (2) Try to unlock MH using user ID of current user and wrong password. (3) No error is displayed and unlocking is successful.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Compliance
One-line Description:
Some operations may cause an unintended checkout of Lock file in Data Store file system
Problem:
Some operations may cause an unintended checkout of Lock file in Data Store file system
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Compliance
One-line Description:
"Configure Compliance Administrator" Window does not warn wrong password
Problem:
"Configure Compliance Administrator" Window does not warn, but completes the changing of the password when "New password" and "Confirm password" are different. Therefore, if a user mistypes the password he or she cannot logon forever as the icpmhsuperuser.
Temporary Solution:
Logon as another administrator and reset the password.
Fix Information:
This was fixed in C.01.03
Keyword: Compliance
One-line Description:
Uploading fails without error when database is full
Problem:
When database is full (or close to full) MassHunter generates no error (or warning). Then uploading fails without user's being aware.
Temporary Solution:
Check the usage periodically from SDAdministrator window
Fix Information:
n/a
Keyword: Compliance
One-line Description:
UAC for "To add/delete annotation" does not work
Problem:
Adding annotation is possible even after "To add/delete annotation does not work" is disabled for all three user groups in ATM configuration.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Compliance
One-line Description:
Error on acquiring full spectrum in user tune with SDA integration.
Problem:
When acquiring full spectrum in user tune with SDA integration, MassHunter ends abnormally.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
Batches may corrupt using database integration - caused by P/A Factor report
Problem:
When ECM or SDA integration is in use and system is in Protect Mode, batches may corrupt after specific operation. By following procedure, you cannot open the batch. (1) Create New Batch from Blank Template. (2) Add to queue (the batch). (3) Save and close the batch on Online DA. (4) Re-open the batch on DA. (5) Execute "Show PA Factor Report". (DA>Main Menu>Report) (6) Save and close the batch on DA, again. (7) Re-open 6's batch and MH shows message, "Could not open batch because falsification was found in batch".
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
Batches may corrupt using database integration - caused by "Save as"
Problem:
When ECM or SDA integration is in use and system is in Protect Mode, batches may corrupt after specific operation. By following procedure, you cannot open the batch. (1) Create New Batch from Blank Template. (2) Add to queue (the batch). (3) Save and close the batch on Online DA. (4) Re-open the batch on DA. (5) Execute "Save Batch Result As". (6) Save and close the Analysis File. (7) Try to open STEP3 or STEP5's "batch.bin.general.ssizip". MH shows an error message, "Could not open batch because falsification was found in batch".
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
Batch files created by "Method Automation" feature is not executable
Problem:
When ECM or SDA integration is in use and system is in Protect Mode, Batch files created by "Method Automation" feature is not executable, displaying a message "Opening a batch in Database Failed."
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
MassHunter C.01.03 cannot open the batch that is created by MassHunter C.01.02
Problem:
When ECM or SDA integration is in use, MassHunter C.01.03 cannot open the batch that is created by MassHunter C.01.02
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
Batches may corrupt using database integration - caused by LIMS output
Problem:
When ECM or SDA integration is in use and system is in Protect Mode, batches may corrupt after specific operation. By following procedure, you cannot open the batch. (1)At the time of Batch creation, put a check in the Export LIMS Data to Each Sample Folder of Worklist Action. (2)Add to Queue. (3)After completion of the measurement, Instrument Control and DA once Close. (4)When try to re-open the Batch, the message "could not open batch because falsification was found in batch" is displayed.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
Data file is not uploaded with P/A Factor Adjustment option
Problem:
Data file is not uploaded with P/A Factor Adjustment option (1) Create any batch. (2) Add any acquired mass. (3) Enable P/A Factor Adjustment. (4) Create sample table with some “CalStd”. (5) Perform data acquisition. (6) Samples in (4) is not uploaded. User cannot realize easily that data files are missing, because there is local cache. The customer used Delete local cache option, then they found the bug. Workaround is to use P/A Factor Adjustment in hardware pane. This is reproducible with C.01.03.
Temporary Solution:
Adjust P/A factor using Hardware pane.
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
When database integration is in use, MassHunter may crash on acquiring full spectrum.
Problem:
When database integration is in use, MassHunter may crash on acquiring full spectrum.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
Batches may corrupt using database integration - caused by Export Diagnosis Report
Problem:
When ECM or SDA integration is in use and system is in Protect Mode, batches may corrupt after specific operation. By following procedure, you cannot open the batch. (1) Open a batch named A.b. (2) Go Hardware>Mainframe > Diagnosis, Check Include Batch Tune Data and Browse A.b on server, finally Check "Batch - Sensitivity - Oxide Ratio Profile" (3) Execute "Export Diagnosis Report." and then Diagnosis Report is exported as a Zip file correctly. (4) Close A.b. (5) Try to Open A.b but fails to open it. If user does not open A.b at step-1, he/she can open A.b after step-3.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
Batches may corrupt using database integration - caused by Advanced Batch Tune
Problem:
When ECM or SDA integration is in use and system is in Protect Mode, batches may corrupt after specific operation. By following procedure, you cannot open the batch. (1) Use each of below Advanced Batch Tune functions. •Acquire Sensitivity - Oxide Profile •Auto RF Matching (2) Cannot open the batch.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Compliance
One-line Description:
Exceptions related to audit trail file access occur when UAC is ON and "Edit and Requeue" is executed
Problem:
Exceptions related to audit trail file access occur when UAC is ON and "Edit and Requeue" is executed. Error message / Exception: The process cannot access the file '[Batch file name]\AUDITTRAIL\acqbatch.instctrl.audit.xml' because it is being used by another process.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Compliance
One-line Description:
Instrument control uses a lot of memory on ending editing mode when SDA is integrated and Protect Local Data is enable
Problem:
Instrument control uses a lot of memory on ending editing mode when SDA is integrated and Protect Local Data is enable. Error message / Exception: Exception of type 'System.OutOfMemoryException' was thrown.;Could not open the batch because falsification was found in batch; Failed to open batch file. IO error while reading binary batch file
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Compliance
One-line Description:
In SDA integration mode, DA stops responding and sequence is halted between 200 - 300 samples.
Problem:
In SDA integration mode, DA stops responding and sequence is halted between 200 - 300 samples.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Compliance
One-line Description:
Function of Lock UI Time could not work during startup task.
Problem:
Function of Lock UI Time (Time-based lock) could not work during startup task.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Compliance
One-line Description:
Error message of "Another logon process is not completed" may be shown when Lock UI Time is set.
Problem:
Error message of "Another logon process is not completed" may be shown when Lock UI Time is set. Error message / Exception: Another logon process is not completed
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Compliance
One-line Description:
Instrument Control crashes when UAC is on and a batch is requeued in Queue pane
Problem:
Instrument control crashes when UAC is on and a batch is requeued in Queue pane Error message / Exception: Object reference not set to an instance of an object.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Compliance
One-line Description:
Unauthorized user may be able to access to protected data folder in the case of database integration
Problem:
Unauthorized user is able to access to protected data folder in the case of database integration (Content Management (Data Store) or ECM/SDA with protect mode).
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Compliance
One-line Description:
SDA database access authority control is not recognized correctly when you log on to MassHunter
Problem:
SDA database access authority control is not recognized correctly when you log on to MassHunter. This occurs in protect mode.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Data Analysis
One-line Description:
Truncation of Legend in Stability Graph
Problem:
In data analysis software, legend in stability graph might be truncated depending on the length of tune mode name.
Temporary Solution:
Drag the right margin of the stability graph (the vertical line just to the left side of Legend) towards the left (away from the legend). Area for legend will be enlarged and truncated strings will be displayed.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Point-to-Point correction fails to create corrected data
Problem:
Point-to-Point correction fails to create corrected data. This is observed with a sample data which is acquired by LC, for an example.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.01 Patch 001
Keyword: Data Analysis
One-line Description:
Incorrect scale for QC Stability chart
Problem:
When QC Check is enabled in QC stability graph, the vertical scale units change to "Conc". However the displayed scale is not changed.
Temporary Solution:
Change the “Conc” axis scale manually
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Untranslated string in configure quick batch report dialog
Problem:
launch DA> main menu> report> configure quick batch report in ISTD column, "ISTDRecoveryPercent" is untranslated.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Data Analysis
One-line Description:
SQ Factor for Calcium on He mode was wrong.
Problem:
SQ Factor for Ca on He mode, "10323" was wrong. Correct SQ Factor for Ca on He mode is "4511", base mass is "43".
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Data Analysis
One-line Description:
Check box is slow to react
Problem:
In Charts dialog box, there are two check boxes named "Display" and "Convert" in Data Analysis. Those check boxes are slow to react when clicking one of them.
Temporary Solution:
Wait a few seconds for checkbox status to update after clicking these checkboxes.
Fix Information:
This was fixed in B.01.01.
Keyword: Data Analysis
One-line Description:
Many analytes in calibration table may cause an error to load batch
Problem:
When there are a huge number of analytes in the calibration table, it will take a long time to load the batch in Data Analysis. This may cause an exception in Instrument Control.
Temporary Solution:
When the number of calibrated analytes is very big, divide the analytes between multiple DA batch files for data processing.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Chromatography integration parameter change is not reflected in result for Global Parameters by single-click
Problem:
Chromatography integration parameter change is not reflected in result until "Change Global Parameters" is clicked twice
Temporary Solution:
Click "Change Global Parameters" twice
Fix Information:
This was fixed in B.01.02.
Keyword: Data Analysis
One-line Description:
ISTD settings of deleted analyte may remain in DA
Problem:
Delete analyte list in DA and import another analyte list from a data file. ISTD settings of the deleted analyte may remain in DA.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Data Analysis
One-line Description:
Inconsistent CPS values between Batch and Spectrum panes
Problem:
There is an inconsistency with displayed CPS values between Batch pane and Spectrum pane.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Data Analysis
One-line Description:
System is suddenly closed when generating a S/N report
Problem:
Data Analysis system is suddenly closed if peak sum exists when a S/N report is generated.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Data Analysis
One-line Description:
Sorting Calib Level is out of order
Problem:
When you click the Level column to sort the calibration levels, the levels will be sorted incorrectly (i.e. 1, 10, 11, 12, ...19, 2, 20, 21, ...)
Temporary Solution:
Close and reopen the batch file.
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Data Analysis
One-line Description:
Array.Sort...error is displayed when changing sample type in the Batch-at-a-glance
Problem:
When you change a sample type in the Batch-at-a-glance, "Array.Sort..." error message may be displayed.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Data Analysis
One-line Description:
On-line DA is terminated when click on spectrum during on-line data acquisition
Problem:
During on-line data acquisition, the data is imported into DA batch. Display ion database which is used to select isotope template. If click on spectrum, the DA wil be terminated with an exception occured.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004.
Keyword: Data Analysis
One-line Description:
Slow creation of TRA based csv file using Export for each sample and tabchart scripts
Problem:
It will take a long time to create a csv file using either "tabchart" script or "export for each file" + "tabchart" script.
Temporary Solution:
n/a
Fix Information:
This is not a software defect. It is a PC hardware performance issue.
Keyword: Data Analysis
One-line Description:
Drift Check > Reslope is not functional in Intelligent Sequence
Problem:
In Intelligent Sequence, Drift Check > Reslope doesn't work if "VIS" is also set up.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004.
Keyword: Data Analysis
One-line Description:
Data Analysis will be aborted when reslope is executed with VIS
Problem:
Data Analysis will be aborted when reslope is executed with VIS in Intelligent Sequence.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Data Analysis
One-line Description:
Excel sheet for chart will not be created for LabQC in Chinese MassHunter
Problem:
This is observed only with Chinese version of MassHunter. When you update LabQC, table will be properly updated. However Excel sheet will not be created for chart.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 5.
Keyword: Data Analysis
One-line Description:
Parameter change may not be reflected in Chromatogram Data Analysis.
Problem:
Parameter change may not be reflected by clicking Change Global Parameter button in Chromatogram Data Analysis. This will be observed only when no peak is shown in the Integration Parameters Table.
Temporary Solution:
Click Change Global Parameter button twice.
Fix Information:
This was fixed in A.01.02 Patch 5.
Keyword: Data Analysis
One-line Description:
Parameter change may not be reflected in Chromatogram Data Analysis.
Problem:
Parameter change may not be reflected by clicking Change Global Parameter button in Chromatogram Data Analysis. This will be observed only when no peak is shown in the Integration Parameters Table.
Temporary Solution:
Click Change Global Parameter button twice.
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Data Analysis
One-line Description:
CPS counts may be different from the actual spectrum data
Problem:
CPS counts may be different from the actual spectrum data in Batch-At-Glance. This is observed with QQQ data. The data populated into tabulate format is OK.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Data Analysis
One-line Description:
Isotope template may not be applied
Problem:
Isotope pattern may not be applied to spectrum with higher than m/z 207.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Data Analysis
One-line Description:
Overflow error might be occurred when stability graph is drawn
Problem:
Overflow error migh be occurred when stability graph is drawn in Data Analysis.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 5.
Keyword: Data Analysis
One-line Description:
On-line DA is terminated when click on spectrum during on-line data acquisition
Problem:
During on-line data acquisition, the data is imported into DA batch. Display ion database which is used to select isotope template. If click on spectrum, the DA wil be terminated with an exception occured.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Data Analysis
One-line Description:
ISTD may not be selected in Calibration pane
Problem:
ISTD may not be selected in Calibration pane when both Single Quad and MS/MS acquisitions are enabled for a certain element in the Acquisition table.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Data Analysis
One-line Description:
Mass bias correction may not be correct
Problem:
For an example, if you define mass bias correction for 10B/11B, 10B, and 11B as IsoStd in a batch, Isotope ratio for 10/Total and 11/Total are incorrect.
Temporary Solution:
Import the IsoStd data to the batch again. Then you will have two lines for IsoStd. Set sample type of the first one to IsoStd, that of teh second one to sample. Then the correct ration will be calculated for 10B/Total and 11B/Total on the second one.
Fix Information:
This was fixed in B.01.02.
Keyword: Data Analysis
One-line Description:
Some conc. RSD are displayed with too many digits in Batch-at-Glance
Problem:
Some conc. RSD are displayed with too many digits in Batch-at-Glance.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Data Analysis
One-line Description:
Some conc. RSD are displayed with too many digits in Batch-at-Glance
Problem:
Some conc. RSD are displayed with too many digits in Batch-at-Glance
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Slope of the converted calibration curve would be incorrect if you edit a calibration curve of "Standard Addition"
Problem:
When you use "standard addition" and then quantitate unknown samples with converted calibration curve from "Standard Addition" to External Calibration". The slope of converted calibration curve is incorrect, so the quantitation result could be incorrect. This would occur if you chose "Blank Offset".
Temporary Solution:
When you exclude a level, you will need to enter a blank into the level in the calibration table. Do not use to reject the blue point in the calibration curve.
Fix Information:
This was fixed in B.01.02 Patch 1.
Keyword: Data Analysis
One-line Description:
Background Subtraction for SemiQuant may not work correctly
Problem:
Background subtraction for SemiQuant may not work if the batch is created from a "preset batch" in which the default settings for Qualitative data analysis remain.
Temporary Solution:
Set background subtraction mode to ‘Count Subtraction for All’ if it is ok to perform background subtraction for all masses. Or, in cases where the user wants to use ‘Count Subtraction except for ISTD’, go to the FQ analyte list, set ISTD/Analyte correctly in the analyte list, then uncheck ‘FullQuant Analysis’ as the data analysis method if the user doesn’t want to see ‘FullQuant’ tab in batch-at-a-glance.
Fix Information:
This was fixed in B.01.03.
Keyword: Data Analysis
One-line Description:
"bkg" cannot be entered to level table in FullQuant pane in Chinese version.
Problem:
"bkg" cannot be entered to level table in FullQuant pane in Data Analysis in Chinese version.
Temporary Solution:
Input "背景"(Chinese character stands for bkg) instead of "Bkg".
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Imported dilution parameter could mislead Quantitation Results
Problem:
When you create a btch by importing data analysis method parameters from other batch, existing dilution parameter could mislead quantitated results. If there is any value in "Final WT or Vol", "Sample WT or Vol". and "Dilution multiplier" in the original batch, these columns are hidden in the default view settings. User could misunderstand that there is no dilution factor for the batch however the hidden dilution factor will be affected to the quantitation results actually.
Temporary Solution:
Delete the value from "Final WT or Vol".
Fix Information:
This was fixed in A.01.02 Patch 7
Keyword: Data Analysis
One-line Description:
Autoscale doesn't work properly in mass pair spectrum window.
Problem:
Autoscale doesn't work properly in mass pair spectrum window.
Temporary Solution:
Adjust scale manually by right-drag on x axis or display "spectrum assistant "
Fix Information:
This was fixed in C.01.01.
Keyword: Data Analysis
One-line Description:
Interference correction doesn't reflect to corrected SemiQuant factor
Problem:
When Interference correction is used and Quick Scan mode is selected in DA method, the corrected SemiQuant factors aren't reflected to the interference corrections. CPS of SQSTD data are crrected by correction equations.
Temporary Solution:
Change the Analysis parameter in DA method from QuickScan Data to Main Data
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
X scale by XY Auto Scale is too wide
Problem:
X scale which is adjusted by 'XY Auto scale' in Analysis/Spectrum screen is too wide. X Auto Scale adjust x scale for 300amu. However XY Auto Scale adjust x sclae for 500amu.
Temporary Solution:
Manually adjust x scale as required
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Stability graph drawing issue
Problem:
When QC Stability graph is used for the standard QC feature, Upper/Lower limit value (red dotted line) is not displayed in the stability graph except for QC1. In case of QC1 it is OK.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Background subtraction failed when "Process Batch" was performed
Problem:
Background subtraction failed when "Process Batch" was performed, displaying a "Batch Analysis failed. Background Subtraction failed." Error message / Exception: Batch analysis failed. Background correction failed : Specified cast is not valid
Temporary Solution:
Check "Full quant analysis"check box in basic information of DA method
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Slope of the converted calibration curve would be incorrect if you edit a calibration curve of "Standard Addition"
Problem:
This occurs in very limited range of "Start rinse before acquisition complete" in preemptive rinse parameter.
Temporary Solution:
When you exclude a level, you will need to enter a blank into the level in the calibration table. Do not use to reject the blue point in the calibration curve.
Fix Information:
This was fixed in A.01.02 Patch 7
Keyword: Data Analysis
One-line Description:
There are cases that SQ outlier is not displayed
Problem:
Evaluation of SQ outlier for an element is not correctly carried out unless all isotopes of the element are set as reported mass.
Temporary Solution:
Select all isotopes.
Fix Information:
n/a
Keyword: Data Analysis
One-line Description:
Wrong RSD for response ratio is given when "Ratio to ISTD" is selected as a backgroud subtruction type.
Problem:
Wrong RSD for response ratio is given when "Ratio to ISTD" is selected as a backgroud subtruction type.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.05
Keyword: Data Analysis
One-line Description:
BEC is not printed in calibration report sometimes
Problem:
BEC is not printed in Print Calibration -> Detail, while BEC is actually displayed in calibration pane.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Data Analysis
One-line Description:
When user rejects on calibration pane, RSD of ratio may become incorrect
Problem:
When user rejects on calibration pane, RSD of ratio changed incorrect value. This occurs when "Count Subtraction for all" is selected as a background subtraction mode.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Data Analysis
One-line Description:
Error in S/N reporting for Chromatographic Data
Problem:
After selecting noise region and clicking "Process Batch", the value "Infinity" appears in the S/N column. Must click "Process Batch" a second time in order to display correct S/N value.
Temporary Solution:
Process batch twice if S/N indicates “Infinity”.
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Data Analysis
One-line Description:
Correction equation is not applied correctly to calibration samples
Problem:
After changing ISTD and processing a batch. Correction equation is not applied to CPS.
Temporary Solution:
Process batch twice if CPS become incorrect.
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Data Analysis
One-line Description:
CPS for washout blank is not displayed
Problem:
It is caused by the modification in MH4.2 that the result is displayed as empty when ISTD has zero CPS in any repetition. By the modification, CPS of analytes are also displayed as empty when ISTD has zero CPS. This is logically incorrect because CPS is not affected by ISTD. Software should be fixed to display CPS, in that case.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Data Analysis
One-line Description:
RSD for Calibration curve is displayed as infinity
Problem:
When a repetition data in calibration standard sample is rejected, RSD of the calibration level is displayed as infinity. Customers want to know how the RSD is improved by rejecting the abnormal repetition. But it is not possible.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Data Analysis
One-line Description:
Wrong behavior of "Set Specific Value" for ISTD
Problem:
ISTD concentrations set individually for each sample, using "Set Specific Value" feature, are lost after method is edited and applied to a batch in DA window.
Temporary Solution:
Edit the ISTD settings again to input correct values.
Fix Information:
This was fixed in B.01.03 Patch 6
Keyword: Data Analysis
One-line Description:
Correction equations are not applied correctly
Problem:
(1) Change ISTD(or other settings below) of element X while sequence is running (2) Process the batch (3) Wait until the next sample is acquired. (4) Correction is not applied to calibration table other than element X. Correction is applied to CPS of samples. Then conc. become strange.
Temporary Solution:
Process the batch again.
Fix Information:
This was fixed in C.01.02 Patch 2
Keyword: Data Analysis
One-line Description:
ISTD is not displayed on the tool bar of Calibration pane
Problem:
ISTD is not displayed on the tool bar of Calibration pane when a batch whose DA method has been set was opened in DA.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 2
Keyword: Data Analysis
One-line Description:
Ghost peaks are drawn on chromatogram in MS-MS mode
Problem:
Ghost peaks are drawn on chromatogram, based on base lines of peaks that are detected in another chromatogram. It happens when chromatograms are sharing same Q1 mass. For example, ghost peaks are drawn in (35->37) using baselines from(35->36) and vice versa.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Data Analysis
One-line Description:
Crash when pasting into DA "Spike Amount" Column
Problem:
When in DA, copying a concentration Level and pasting into the Spike Amount column causes MH to crash Error message / Exception: Object cannot be cast from DBNull to other types.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Data Analysis
One-line Description:
Manual integration fails
Problem:
When "Peak Sum" is in use, manual integration may fail displaying "Object reference error".
Temporary Solution:
Re-open batch, when you need to manually integrate PeakSum after you process batch.
Fix Information:
This was fixed in C.01.03
Keyword: Data Analysis
One-line Description:
Dilute and Rerun might not be executed correctly as 2nd Action on Failure when prepFAST is used.
Problem:
Dilute and Rerun might not be executed correctly as 2nd Action on Failure when prepFAST is used, because incorrect Proposed DF might be applied.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: External Device
One-line Description:
“UNKNOWN” appears when AUX Heater is set to “ICPMS" from GC panel
Problem:
When setting AUX Heater Type as ICPMS from GC panel, “UNKNOWN” appears on GC status in Hardware Task. But AUX Heater Type for ICPMS is actually setup.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: External Device
One-line Description:
LC is in a constant error status when plasma is off
Problem:
LC is in a constant error status when the plasma is off.
Temporary Solution:
Disconnect the Remote Start cable between ICP-MS and LC.
Fix Information:
This was fixed in B.01.02.
Keyword: External Device
One-line Description:
Injector program for LC is not usable
Problem:
LC injector program is not available to use.
Temporary Solution:
Do not use direct Control of LC but use injection program from the Instant Pilot or OpenLab ChemStation.
Fix Information:
n/a
Keyword: External Device
One-line Description:
On-line HELP may be slow to respond with LC-ICP-MS
Problem:
When LC is configured, on-line HELP may be slow to respond. MassHunter looks no response but it is actually working. If you click a few times in MassHunter during the waiting, MassHunter could be terminated.
Temporary Solution:
Wait for response without interrupting MassHunter internal tasks.
Fix Information:
n/a
Keyword: External Device
One-line Description:
Injector program for LC is not available.
Problem:
Injector program for LC is not available. There is no function to enable injector program for LC.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 1.
Keyword: External Device
One-line Description:
GC Integration does not work unless the GC has an auto-sampler.
Problem:
7890 cannot be controlled by MassHunter software unless the GC has an auto-sampler.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: External Device
One-line Description:
GC-ICP-MS data acquisition may stop by solvent peak
Problem:
Using GC-ICP-MS, once detector mode becomes over range because of solvent peak, EM stops taking data.
Temporary Solution:
to create a “solvent delay” using an initial tune step that does not contain any isotopes from the solvent.
Fix Information:
n/a
Keyword: External Device
One-line Description:
Back injector is not usable without ALS Tray
Problem:
In case ALS Tray is not used and GC has only tower part of the ALS, vial# is 101 for front injector and 201 for the back injector. But LC/GC vial column on sample table limits number to 150 at maximum. Then user cannot input 201.
Temporary Solution:
None
Fix Information:
This was fixed in C.01.01.03.
Keyword: External Device
One-line Description:
MH SW terminated when the column information was modified
Problem:
Clicking Catalog button for Column on GC7890 Column Tab will cause crash.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: External Device
One-line Description:
LC method can become wrong
Problem:
LC method can become wrong by the following procedure. (1) Logon as a user who has no access right to edit Acq Method. (2) Open a batch. (3) Save the batch as another name. (4) Run the batch, then I found acquisition never finish. (5) Give the user an access right to edit Acq Method. (6) Open the batch again. I found Acq time in LC method has been reset to "No Limit".
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: External Device
One-line Description:
LC Status screen become uncontrollable
Problem:
(1) Enable LC integration (2) Create any batch. (3) Status screen for LC become uncontrollable - Pressure, flow rate, and temperature are not updated with current ones. - Context menu -> Control... is not usable. Displaying the attached dialog. It occurs about 50% probability.
Temporary Solution:
Close and re-open Instrument control window.
Fix Information:
This was fixed in C.01.03
Keyword: Hardware
One-line Description:
Probe rinse (std) is not used in startup and hardware settings.
Problem:
The time setting of “Probe Rinse (Std)” on “PeriPump Setting” dialog box in startup and hardware settings is not actually used. Only the setting of “Probe Rinse (Sample)” is used.
Temporary Solution:
Temporary Solution: Use “Probe Rinse (Sample)” as probe rinse setting.
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
Entered value beyond acceptable range of cell gas is canceled.
Problem:
On the pane of collision/reaction cell gas maintenance, the entered value beyond acceptable range of cell gas is canceled. This means it is difficult to know the value range of cell gas from the graphical user interface.
Temporary Solution:
Temporary Solution: The acceptable ranges of cell gas values are: He Gas: 0.0 and 0.5-12.0 H2 Gas: 0.0 and 0.5-10.0 3rd Cell Gas: 0.0 and 5.0-100.0 (Including the boundary values)
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
Position of LC Method dialog
Problem:
When you open Method dialog from LC instrument status pane by using context menu, the dialog might be displayed beyond the left top corner of your display, so you might not be able to see the entire dialog.
Temporary Solution:
Enter [Alt]+[Space], then you will see system menu of the dialog. Select ‘Move’ from the system menu. Then you can move the dialog by using arrow keys.
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
ISIS configuration in Hardware overrides alternative sample intro set in Startup/Hardware Setting
Problem:
When ISIS is set as the Hardware configuration in the Hardware pane, setting alternative sample intro configuration in Startup is not applied. The ISIS config is still used for Startup Tasks, even though the ISIS parameters are not displayed. This means the ISIS pump does not stop rotating and the non-ISIS sample introduction type which is used for the Startup tasks or the hardware setting is not applied automatically. The different sample introduction type can only be set by changing it from ‘ISIS’ to another type in the ‘Hardware’ pane.
Temporary Solution:
The rotating of ISIS pump must be stopped manually with ‘ISIS Manual Operation’ dialog in order to stop it. The sample introduction type which is to be used for the Startup tasks or the standard setting should be set in ‘Hardware->Mainframe->Hardware Settings’ task.
Fix Information:
This was fixed in B.01.03.
Keyword: Hardware
One-line Description:
Entering a flow setting for 3rd cell gas is rejected in Maintenance screen
Problem:
In [Top] > [Hardware] > [Collision/Reaction Cell] > [Maintenance] when you enter a flow setting value to "Output" for "3rd Cell Gas Flow", "Enter a valid number" warning is displayed and only "OK" is available to exit. After exiting the warning, % of Input flow is not displayed correctly corresponding to the flow change.
Temporary Solution:
n/a
Fix Information:
It is not reproducible and waiting for a report of reoccrence.
Keyword: Hardware
One-line Description:
Firmware Error message is displayed after correction of the original problem
Problem:
When plasma goes off due to air leakage in sample introduction system, the "Firmware error occured while queling command 1213" error occurred which is normal. But after you fix the leakage problem and click "plasma on" this error displayed and abort plasma on sequence at the beginning. Same type of error also occurred when you forgot to close the cover and click "plasma on" The error message should clear after you fix the hardware issue.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
New default limit value of "Change Fore Line Pump Oil" in EMF
Problem:
The current default limit value of "Change Fore Line Pump Oil" in EMF is 4,320 hours (= 6 months). Edwards (pump supplier) suggests 3,000 hours to change pump oil in their manual. To keep consistency, the default value needs to be changed to 3,000 hours.
Temporary Solution:
Change the limit value to 3,000 hours.
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
Performance Report results and Hardware Values are not updated.
Problem:
Performance Report result and hardware values in Hardware pane are not properly updated with most recent run in Single View mode. The History View mode is updated properly.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
Peri-pump time is applied even with Laser Ablation system configured
Problem:
The sample introduction system is configured for laser, and the peri-pump option does not appear in the batch folder, yet the times from the peripump are still applied.
Temporary Solution:
Configure the system for peripump and set the times to '0' and keep this setting.
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
P/A factor setting fails when one or more signals go over analog limit value
Problem:
De-tune process in P/A factor setting fails when one or more signals are over Analog Limit value. The mass whose signals over the Analog Limit value should be rejected from the mass list for the de-tuned PA Factor tune acquisition.
Temporary Solution:
If see the error message, use lower concentration standard.
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
I-AS always moves the tray to the escape position before moving the probe
Problem:
I-AS always moves the tray to the escape position before moving the probe, this is even if you have not selected escape mode in the software.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
EM tune fails when small diameter torch is used
Problem:
EM Auto Setting fails when small diameter torch like 1.5mm or 1mm is used. The small diameter torches seem to reduce the 80amu signal to a level that is too low to execute EM voltage setting. Current preset plasma does not support small diameter torches, so the plasma condition will be different from when the standard torch is used.
Temporary Solution:
When the small diameter torch is used, Plasma Correction should be disabled and the other hardware settings should be executed with adjusted plasma setting.
Fix Information:
n/a
Keyword: Hardware
One-line Description:
MassHunter does not recognize I-AS after changing sample introduction method
Problem:
MassHunter does not recognize I-AS especially after changing sample introduction method (ie. I-AS > LC > I-AS, etc.). This is observed intermittently.
Temporary Solution:
In Hardware pane, right click on Autosampler icon and select Set Communication. Select appropriate COM Port. In many cases, the COM port setting is revert to COM1 after changing sample introduction method. If this does not work, try one of followings: - Mainframe > Set Communication > Use ALS turn off and on - Power cycle I-AS - Restart MassHunter software - Restart Windows
Fix Information:
It is not reproducible and waiting for a report of reoccurence.
Keyword: Hardware
One-line Description:
Peri Pump may keep rotating after plasma off
Problem:
When the Instrument Control window is closed during the Plasma Off sequence, the Peri Pump may keep rotating after Plasma Off.
Temporary Solution:
Allow Plasma Off sequence to complete before closing Instrument Control
Fix Information:
This was fixed in B.01.01.
Keyword: Hardware
One-line Description:
"Define Wellplate" button is not located correctly.
Problem:
In Wellplate LC autosampler configuration, "Define Wellplate" button is not located correctly.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Hardware
One-line Description:
Misleading error message when a non-existing vial number is selected
Problem:
When a non-existing vial number is selected for vial position, displayed message would lead misunderstanding.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Hardware
One-line Description:
Visualization for Performance report does not work when it is executed in hardware task
Problem:
When Performance Report is run in Hardware task, visualization is not displayed. The real-time visualization works correctly when Performance Report is run as a Startup task in Queue.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.
Keyword: Hardware
One-line Description:
Torch goes way off x/y axis at torch/plasma correction
Problem:
When Startup is run for torch/plasma correction etc., the torch could go way off axis (2 mm too high and 2 mm toward the back). This might happen when a signal used for optimization is too weak.
Temporary Solution:
Ensure signals used for torch position optimization are at high enough intensity to be used
Fix Information:
This was fixed in A.01.02.
Keyword: Hardware
One-line Description:
PA factor history may not be displayed correctly
Problem:
The PA factor history is not displayed correctly. When P/A Factor elements are not calibrated, they are removed from the P/A Factor calibration list, instead of being displayed and flagged with a comment like "Signal too low for Analog mode"
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: Hardware
One-line Description:
Method window for LC 1200 is not properly displayed
Problem:
SelIf LC 1200 binary pump is selected as sample introduction and instrument status pane is displayed, the method window location is incorrect when the user selects LC tab, then right clicks the LC status panel > select method.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Hardware
One-line Description:
"Load Mass List from Method" function does not consider prohibited masses
Problem:
"Load Mass List from Method" function for P/A factor in Hardware Task does not consider prohibited masses. "Select Mass" function always shows error message "The mass ** is prohibited to select". And Periodic table also cannot show prohibit mass.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Hardware
One-line Description:
Ion Lens Voltage value may be displayed with too many digits in Performance Report
Problem:
In History View of Performance Report, Ion Lens Voltage value may be displayed with too many digits.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Hardware
One-line Description:
Plasma Correction for hot plasma may fail
Problem:
Plasma Correction for hot plasma with s-lens may fail. Some system parameters need to be improved for better reliability in plasma correction for hot plasma.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Hardware
One-line Description:
Fault in plasma correction for cool plasma
Problem:
The plasma correction for cool plasma calculates S/B ratio of 59Co and 80ArAr, and the result is used as evaluation value of each sampling point. However if a samling data on 80amu is zero, the software makes the evaluation value zero. As a result, the plasma correction can no longer search for optimum point correctly. When a sampling data on 80amu is zero, the evaluation value should be infinite or very high value for the simplex method.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: Hardware
One-line Description:
Failure of plasma correction for cool plasma
Problem:
The plasma correction for cool plasma uses simplex method to decide optimum Makeup Gas, and the minimum sampling resolution is fixed at 0.01L/min. However in some cases the software continues to search optimum Makeup Gas deviding the sampling resolution into halves like 0.64, 0.60, 0.62, 0.61, 0.605, 0.6025, 0.60125, ... and the correction is never-ending. Sometimes it goes normally.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: Hardware
One-line Description:
Plasma cannot be put off right after ignition.
Problem:
Plasma cannot be put off if you try to turn off the plasma right after the ignition.
Temporary Solution:
Turn off instrument power switch if an emergency arises.
Fix Information:
This was fixed in C.01.01.
Keyword: Hardware
One-line Description:
Hardware Diagnosis report may fail selected with Include Batch Tune Data and Batch Tune Report
Problem:
In Hardware > Diagnosis, when you export both Batch Tune Data and Batch Tune Report selected, you will see "Hardware Error" and the export will be aborted.
Temporary Solution:
Select "Off" for one of either Batch Tune Data or Batch Tune Report.
Fix Information:
This will not be fixed.
Keyword: Hardware
One-line Description:
Deleting mass during P/A factor acquisition may cause a software internal error
Problem:
Deleting mass from the mass table on P/A factor table in Hardware Task may cause a software internal error. This will be observed during P/A factor acquisition. The error message would be: "This row has been removed from a table and does not have any data. BeginEdit() will allow creation of new data in this row"
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Hardware
One-line Description:
MassHunter is terminated when Performance Report is clicked during Startup
Problem:
MassHunter is terminated when Performance Report is clicked during Startup.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 5.
Keyword: Hardware
One-line Description:
Evacuation assist valve and H2 stop valve are not closed when closing the cell maintenance mode
Problem:
Evacuation assist valve and H2 stop valve are not closed when closing the cell maintenance mode. This could cause a damage to Electron Multiplier detector at plasma turned on.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Hardware
One-line Description:
MassHunter is terminated when Performance Report is clicked during Startup.
Problem:
MassHunter is terminated when Performance Report is clicked during Startup.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Hardware
One-line Description:
"PA Factor Out of Range" is displayed during calibration
Problem:
"PA Factor Out of Range" is displayed during calibration
Temporary Solution:
A workaround is to add a mass having somewhat different P/A factor as reference value from existing masses. This makes approximate caclulation more valid and prevents the error from ocurring
Fix Information:
This was fixed in B.01.02.
Keyword: Hardware
One-line Description:
G4226A autosampler configuration screen is too restricted and also poorly laid out
Problem:
The Instrument view of the HPLC G4226A autoasmpler is off the screen and cannot be seen even if teh windows are fully sized. Also information for the HPLC modules obscures information when the status window is made large
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Hardware
One-line Description:
Cannot change Seat Capillary setting for 1200 LC Autosampler
Problem:
It is unavailable to modify the Seat Capillary setting when the injection volume is changed to >100uL. When you change the setting, the message like “Update Modules or change sample introduction” is displayed. But the Seat Capillary setting goes back to default value (2.3uL) even if the “Update Modules” is done.
Temporary Solution:
Set by Instant Pilot or ChemStation.
Fix Information:
n/a
Keyword: Hardware
One-line Description:
It takes time to open Performance Report
Problem:
It takes some time to open Performance Report if there are a lot of previous Performance Report data.
Temporary Solution:
The Performance Report data is stored at: C:\agilent\ICPMH\1\PerformanceReport\PerformanceReport.xml When you manually rename it, MassHunter will automatically create a new file.
Fix Information:
This was fixed in A.01.02 Patch 7
Keyword: Hardware
One-line Description:
Prohibit Masses in S-lens configuration
Problem:
There are four modes available in the Set Prohibit Masses dialog box, No Gas-Hot Mode, No Gas-Cool Mode, H2 Gas Mode, and He Gas Mode. Only No Gas-Hot Mode or No Gas-Cool Mode can be used with S-lens configured system. In this case, even if you select either No Gas-Hot Mode or No Gas-Cool Mode, you can use any other gas mode for acquisition, i.e. He or H2 mode. Please ignore the Gas Mode descriptions in case of S-lens.
Temporary Solution:
Ignore the Gas Mode description in case of S-lens.
Fix Information:
n/a
Keyword: Hardware
One-line Description:
B2 for CapLC pump doesn't function
Problem:
B2 channel for CapLC pump doesn't function.
Temporary Solution:
Manually exchange bottle 1 and 2 of the solvents. Control LC from handheld controller or OpenLab ChemStation.
Fix Information:
This was fixed in C.01.01.
Keyword: Hardware
One-line Description:
ALS drop down menu could give an error
Problem:
If the system is rebooted, and no vial number was set, the drop down menu to 'goto', 'move' etc gives an error. The vial number has to be first set by clicking on the ALS icon, entering a value and then the drop downs may be used to select a vial and then move or goto.
Temporary Solution:
Set the vial number at first before clicking the drop down menu items, "Go to" or "Move"
Fix Information:
n/a
Keyword: Hardware
One-line Description:
Auto Config for LC modules might not work
Problem:
Auto Config for LC modules might not work to capture firmware version or serial number.
Temporary Solution:
Redo Auto Config for the LC module
Fix Information:
n/a
Keyword: Hardware
One-line Description:
ICP-MS goes offline if sample introduction is changed
Problem:
When you change sample introduction a few times between GC and PeriPump while opening a batch, you will get an error message and ICP-MS will go off-line. Error message / Exception: Failed to connect to LC/GC modules. Confirm following modules are connected and online:
Temporary Solution:
Re-configure ICP-MS as Online
Fix Information:
n/a
Keyword: Hardware
One-line Description:
EM Autotune doesn't refer to EM Tune parameter
Problem:
System parameter "EM Tune" can be set, but in actual behavior of the EM Autotune, the value is hard coded and the system parameter is never used.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: Hardware
One-line Description:
Discriminator autotune behavior problem
Problem:
Some noise counts may occur in the first scan point of discriminator autotune for 7700 and 8800.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: Hardware
One-line Description:
ISIS3 Tune/ISTD selection valve problem
Problem:
When configured with ISIS3 the Tune/ISTD selection valve does not switch to the appropriate Tune selection during "startup".
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Hardware
One-line Description:
8900 standard model cannot control 4th gas flow in standby mode
Problem:
In 8900 standard model, you cannot flow 4th gas in standby mode.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 2
Keyword: Hardware
One-line Description:
OctPole RF Matching will fail after turning on the instrument
Problem:
After turning on the instrument, OctPole matching will fail on user maintenance screen but succeed in engineer’s maintenance screen. Error message / Exception: OctPole RF Matching Failed. Cannot find FET's threshold
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Other
One-line Description:
"About" screen may not display correctly
Problem:
If the user enables user access control and then clicks “Configure ATM” in the user access control configuration dialog box, the “Help, About” screen contents cannot be displayed.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Other
One-line Description:
Data is not properly exported in LC/MS format
Problem:
When data is exported into LC/MS format, the first mass is exported properly but the rest are shown as 0.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Other
One-line Description:
LabQCAddin can't be occasionally installed at updating from G7201A A.01.01 to A.01.02.
Problem:
This has been reported only with Japanese version of MassHunter. In Japanese system, when you update existing G7201A A.01.01 to A.01.02, LabQCAddin cannot be occasionally installed after A.01.02 installation in some cases.
Temporary Solution:
Search and delete "icpl*" files under C:\Users\\AppData\Local\Apps\......\manifests\. This might allow you to install LabQCAddin.
Fix Information:
This is an issue of Microsft Windows.
Keyword: Other
One-line Description:
BatchLog.xml is only uploaded to ECM at the batch creation
Problem:
BatchLog.xml which is data used when batch log excel file is created are not uploaded to ECM at correct timings. The file is uploaded to ECM only when the batch is created. So the file is always almost empty.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004.
Keyword: Other
One-line Description:
BatchLog.xml is only uploaded to ECM at the batch creation
Problem:
BatchLog.xml which is data used when batch log excel file is created are not uploaded to ECM at correct timings. The file is uploaded to ECM only when the batch is created. So the file is always almost empty.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Other
One-line Description:
Instrument Control is terminated when Time Format is changed with empty Performance Report pane
Problem:
When you change Time Format from "sec" to "min", Instrument Control may be terminated. This will be observed when Performance Report pain is empty.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Other
One-line Description:
Instrument Control is terminated when Time Format is changed with empty Performance Report pane
Problem:
SSB Problem Description: When you change Time Format from "sec" to "min", Instrument Control may be terminated. This will be observed when Performance Report pain is empty.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Other
One-line Description:
Incorrect descriptions in On-line HELP and Manual about Timing of Acq Batch Audit Trail
Problem:
Some descriptions for "Upload Files and Timing" are not correct in On-line HELP (G7201B B.01.03) and User Access Control Pack software manual (G7207-9x004).
1. Timing of Acq Batch Audit Trail
The correct timings are followings:
*when saved
*when batch is closed
*when batch is created
*when batch is opened
*end editing batch in Batch task during acquisition
*open and close sample list in Queue
*end edting Mode in Queue task
2. Missing Information
QCTuneReport.xlsx will be uploaded to the Database when tune report is generated in EPA mode.
3. The file name of Acquired Data should be "*.D.general.ssizip" instead of "*.D.ssizip".
Temporary Solution:
n/a
Fix Information:
This will be fixed in a future revision.
Keyword: Other
One-line Description:
The Batches for organic solvent do not contain one for the 7900
Problem:
Batches for organic solvent do not contain a batch for the 7900. Then user cannot ignite plasma in organic mode.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: Other
One-line Description:
Wrong description for file upload timing in online help
Problem:
Both in online help of ICP-MS MassHunter and "MassHunter Workstation User Access Control Pack" manual, description for "Upload Files and Timing" is wrong. Acq Batch Audit Trail -> ECM/SDA -> Timing should be the below. when saved when batch is closed when batch is created when batch is opened end editing batch in Batch task during acquisition open and close sample list in Queue end editing Mode in Queue task
Temporary Solution:
None
Fix Information:
n/a
Keyword: Other
One-line Description:
Missing description for uploaded file and timing in online help
Problem:
Both in online help of ICP-MS MassHunter and "MassHunter Workstation User Access Control Pack" manual, description of "Upload Files and Timing" is missing for Excel files for QC Tune reports.
Temporary Solution:
None
Fix Information:
n/a
Keyword: Other
One-line Description:
Wrong tune parameters are send when LA is used
Problem:
When instrument become analysis mode, tune parameters for organic solvent is sent to instrment, insted of one for LA.(Laser Ablation)
Temporary Solution:
Use user tune feature. Then parameters in the user tune will be sent.
Fix Information:
This was fixed in C.01.02
Keyword: Other
One-line Description:
Wrong LC parameter is printed by print method feature
Problem:
Printed LC parameter in print method feature is not taken from Method but instrument. (1) Load batch A. (2) Send parameters to LC (3) Load batch B. (4) Print the method, then parameter in batch A is printed.
Temporary Solution:
Always send parameters to LC befere printing methods.
Fix Information:
This was fixed in C.01.02
Keyword: Other
One-line Description:
LC Injection volume can become wrong value
Problem:
Injection volume can become wrong value. Assume LC system has pump and ALS. (1) Load any batch with LC method. (2) Click send LC button. (3) Injection volume on LC is set to 5ul regardless the LC method.
Temporary Solution:
If ALS tab is LC method is clicked between (2) and (3), it does not happen.
Fix Information:
This was fixed in C.01.02
Keyword: Other
One-line Description:
After installation of B.01.03 patch3, system become completely unusable
Problem:
If patch 3 is installed on system with LC integration it becomes completely unusable.
Temporary Solution:
Uninstall MassHunter software, delete c:\Agilent\ICPMH, and Reinstall MassHunter + Parch3.
Fix Information:
This was fixed in B.01.03.05
Keyword: Other
One-line Description:
With HiP sampler, user cannot control thermostat from method
Problem:
When LC module G1367E has thermostat, it is impossible to turn on "Control thermostat from method" option. If a user turn it ON, it become automatically OFF after clicking "Update module".
Temporary Solution:
User can operate the thermostat from context menu in status pane -> LC1200-> each module.This might be a workaround.
Fix Information:
n/a
Keyword: Queue
One-line Description:
Real time display of queue is not updated if acquisition time is too short.
Problem:
Real time display of queue is not updated if acquisition time of a sample is less than about 0.5 second. Because of this issue, real time display keeps showing previous acquisition data.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: Queue
One-line Description:
Element buttons on “Set Sublist of Acq Elements” dialog box does not work properly.
Problem:
When you edit a sublist on “Set Sublist of Acq Elements” dialog box shown from sample list tab, element buttons in periodic table on the dialog do not work properly. Changes on the periodic table and isotope table under it should be applied to the checkboxes in “Acq” column of “Total Acquired Elements” table but this mechanism does not work in the current version of MassHunter.
Temporary Solution:
Use the checkboxes in “Acq” column of “Total Acquired Elements” table to edit a sublist.
Fix Information:
This was fixed in A.01.02.
Keyword: Queue
One-line Description:
Removing task while Vial at End is running causes software freeze
Problem:
When Vial at End is set and it’s running after the last queued task, removing the task while moving to the vial causes software freeze.
Temporary Solution:
Do not remove the last task while ALS is moving to the vial of Vial at End. Need to kill IcpInstControl.exe from Task manager in the case that the software becomes uncontrollable.
Fix Information:
This was fixed in A.01.02.
Keyword: Queue
One-line Description:
"Start Sample List Edit mode" button will be disabled if double click acquisition order table
Problem:
If the user double clicks the acquisition order table in “Sample List Edit” mode of Queue, the start sample list edit mode button will then become disabled when sample list editing is ended.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Queue
One-line Description:
Batch log cannot be printed
Problem:
In batch log table in Queue, there are two print menu items. When you click "Print", this will not print a batch log table but a sample list.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Queue
One-line Description:
System suddenly terminated when editing sample table in Queue
Problem:
Data Acquisition system is suddenly terminated when editing sample table in Queue during sample acquisition.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Queue
One-line Description:
MassHunter does not respond when ending editing mode of sample table in Queue
Problem:
MassHunter does not respond with a progress box kept open when ending editing mode of sample table in Queue while Whole List is opened.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Queue
One-line Description:
Red cross during editing sample list in Queue
Problem:
When edits sample list in Queue after adding batch files, error with red-cross will be observed right after the edit.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Queue
One-line Description:
MassHunter A.01.02 Patch 003 crashed when Whole List was clicked.
Problem:
Show Sample List tab in Batch or go to Queue. Click Whole List button on tool bar. MassHunter will not be launched any more.
Temporary Solution:
Avoid to use Whole List function. If MassHunter is not started, delete c:\Users\\AppData\Agilent_Technologies,_Inc folder. Then all the settings will be back to default and MassHunter will be started with Whole List = Off.
Fix Information:
This was fixed in A.01.02 Patch 004.
Keyword: Queue
One-line Description:
Data acquisition is freezed when click Add to Queue
Problem:
This is only observed if all time parameter settings are set as 0 for PeriPump.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Queue
One-line Description:
Error by editing batch in edit mode during sample acquisition
Problem:
During a sample acquisition, enter Edit mode and modify a parameter (i.e. sample name). An error may be observed.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Queue
One-line Description:
Error is occurred when Auto/semi auto tune before batch is selected without opening a batch
Problem:
Error is occured when a batch is performed with Auto/semi auto tune before batch selected in Queue without opening a batch in Batch task.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Queue
One-line Description:
MassHunter is terminated with error message
Problem:
When a Batch is added to Queue and Data Analysis is lanuched, an error message will be displayed and MassHunter will be terminated with red crosses.
Temporary Solution:
Close MassHunter and Delete Delete following file: C:\\admin\appdata........ICPInstControl.EXEとICPDataAnalisys.EXE
Fix Information:
It is not reproducible and waiting for a report of reoccrence. This migh be a third-party component issue.
Keyword: Queue
One-line Description:
Edit Sample List may not function
Problem:
Edit Sample List in Queue is grayed out and you cannot edit the sample during acquisition.
Temporary Solution:
Select a sample block in the Acquisition Order list first. Then select a sample line which is not grayed out.
Fix Information:
This will be fixed in a future revision.
Keyword: Queue
One-line Description:
Changing "Independent P/A Factors" while sequence is running may cause an exception
Problem:
Changing "Independent P/A Factors" while sequence is running may cause an exception
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Queue
One-line Description:
MassHunter may have no response when a large number of tasks are deleted in the Queue.
Problem:
MassHunter may have no response when a large number of tasks are deleted in the Queue. This could be observed if there are more than about 700 lines in the Queue. It may take more than 15 minutes to delete them.
Temporary Solution:
Wait till the completion of deleting lines.
Fix Information:
n/a
Keyword: Queue
One-line Description:
“Start Sample List Editing Mode” in Queue Pane doesn’t work during data acquisition
Problem:
n/a
Temporary Solution:
Click sequence block name in sample table of Queue,
Fix Information:
This was fixed in C.01.01.
Keyword: Queue
One-line Description:
A batch acquisition may be suspended with status in process.
Problem:
If you input a number to calibration level column but don't click return to enter in the On-line Data Analysis, the batch acquisition is suspended in the Instrument Control.
Temporary Solution:
Make sure to finish any editting to continue batch acquisition.
Fix Information:
This was fixed in C.01.01.
Keyword: Queue
One-line Description:
No H2 gas flows in H2 tuning mode in certain condition
Problem:
This issue has been submitted not by user nor application engineer, but manufacturing division. This occurs when following all conditions are satisfied.
(1) In case two batches are aquired in series.
(2) Tune mode of first batch is Nogas -> Gas mode
(3) Tune mode of second batch is Gas mode-> Nogas
(4) Rinse program of the first batch is extremely short.
Occurred with 0sec program. Did not occur with
5sec program.
(5) At the first sample of the second batch.
Temporary Solution:
Set any rinse program 5sec or longer.
Fix Information:
n/a
Keyword: Queue
One-line Description:
Data Acquisition is stopped by the Object reference ... error
Problem:
Sequence of Data Acquisition may be aborted by the Object reference...error. When you exit the Editing mode in Queue while P/A adjustment is running, the sequence may be aborted by "Object reference..." error.
Temporary Solution:
Avoid to finish editing mode while P/A factor adjustment is running.
Fix Information:
This will be fixed in a future revision.
Keyword: Queue
One-line Description:
Sequence error seen after overnight queue run
Problem:
When import calibration from existing batch is used, sequence stops during run intermittently.
Temporary Solution:
Not to display calibration table during sequence
Fix Information:
n/a
Keyword: Queue
One-line Description:
Sequence error because of sub list setting
Problem:
If no elements in sub list is acquired in the tune mode on which quick scan has been set, sequence stops by an error. Error message / Exception: Reboot the MassHunter PC and power cycle the 7700 ICP-MS.
Temporary Solution:
Add at least one element from the sub list to the tune the mode for which Quick scan has been selected.
Fix Information:
n/a
Keyword: Queue
One-line Description:
"Ratio" setting problem in "Real time display"
Problem:
Even when "Signal Ratios for Monitor Function" (Tools->Configure MassHunter) is unchecked, ratio settings in "Real time display" are not hidden. And if the ratio has been set, it does not work. It seems as if malfunctioning. They should be hidden.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: Queue
One-line Description:
Sequence intermittently stops using ISIS3
Problem:
A batch sequence intermittently stops when the batch contains ISIS3 settings.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: Queue
One-line Description:
Error count of QC error action is not cleared after the QC error check passes
Problem:
Error count of QC error action, (For 2nd AOF or 3rd AOF) is not cleared after the QC error check passes.
Temporary Solution:
None
Fix Information:
This was fixed in C.01.01.03.
Keyword: Queue
One-line Description:
Wrong behavior of pause function
Problem:
Pause function works in wrong way. Then sequence stops in unexpected way when following these steps. (1) Pause a sequence while it is running. (2) Stop the sequence by stop button on real time display. (3) Remove the sequence from queue. (4) Edit the sequence and save the batch. (5) Add the batch to queue, then the sequence is paused again as per (1) above.
Temporary Solution:
Not to stop sequence while it is paused.
Fix Information:
This was fixed in C.01.01.03.
Keyword: Queue
One-line Description:
Error count of QC error action is not cleared after the QC error check passes (For B.01.03)
Problem:
This is a copy of KPR #255(C.01.01) for B.01.03. Error count of QC error action, (For 2nd AOF or 3rd AOF) is not cleared after the QC error check passes.
Temporary Solution:
None
Fix Information:
This was fixed in B.01.03.03.
Keyword: Queue
One-line Description:
MassHunter has no feature to count QC error by sample types + bottles
Problem:
On using intelligent sequencing, ChemStation software had feature to count QC error by sample types + bottles. But MassHunter software can count only by sample types.
Temporary Solution:
Use independent sample types such as CCV1, CCV2 for each vial.
Fix Information:
n/a
Keyword: Queue
One-line Description:
Wrong behavior of sample table editing mode
Problem:
When a user starts editing of sample table with both of the following 2 conditions, the editing is started not as normal editing but as "edit and requeue". Then all samples get skip flag. On finish editing after that, system ends by an exception. (1) Start editing mode while tune report before batch is running. (2) Start editing mode in batch pane.
Temporary Solution:
As a workaround, if a user starts editing after finishing tune report, the error does not occur.
Fix Information:
This was fixed in C.01.02
Keyword: Queue
One-line Description:
Using 8800, sequence stops in tune mode transition
Problem:
Sequence stops while tune mode transition is going on (When "Transition to No gas" is displaying on status bar). No error message is displayed.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 6
Keyword: Queue
One-line Description:
Using 7700, sequence stops in tune mode transition
Problem:
Sequence stops while tune mode transition is going on (When "Transition to No gas" is displaying on status bar). No error message is displayed.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 6
Keyword: Queue
One-line Description:
Edit and requeue is impossible because of the attached error
Problem:
When "Edit and requeue" is executed, the error message "Device driver for ICP-MS/Auto sampler is not found. "is displayed after users click "Requeue". Error message / Exception: Could not find device driver for ICP-MS/Autosampler. Please uninstall and re-install MassHunter or contact customer support.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Queue
One-line Description:
Edit and requeue imports extra tune files from User tune
Problem:
Edit and requeue imports extra tune files from User tune regardless the tune mode selection in user tune.
Temporary Solution:
Remove the extra tune manually.
Fix Information:
This was fixed in C.01.03
Keyword: Queue
One-line Description:
Freeze when you open the InstrumentControl
Problem:
Following process causes InstrumentControl freeze. (1) Launch InstrumentControl and create Batch (2) Add batch to queue (3) Requeue current batch few times from batch task (4) Abort step 2 batch (5) Close InstrumentControl. (6) Open InstrumentControl. (InstrumentControl will freeze)
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Queue
One-line Description:
Wrong behavior of peripump program
Problem:
A part of post run rinse might be rarely skipped by an error.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Queue
One-line Description:
Using ISIS3, sequence is halted because of vial# error
Problem:
When a batch is added to queue, sequence is halted because of a vial# error. But the vial# error is not detected by method validation. This happens when vial# is empty while rinse time and ISIS pump speed is not empty in rinse program.
Temporary Solution:
If you do not intend to use a rinse step, set its rinse time and ISIS pump speed empty as well as vial#.
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Queue
One-line Description:
Edit sample table may malfunction
Problem:
First sample in a sequence could be skipped if user edits sample table while tune check report before batch is going on.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Queue
One-line Description:
Fail count of "Dilution and Re-Run" is not reset when an acquired sample is changed
Problem:
In standard QC, fail counts for “Dilution and Re-Run” cannot be reset even after criteria for a sample is pass.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 2
Keyword: Queue
One-line Description:
Preemptive rinse would cause malfunction on data acquisition
Problem:
Data acquisition might be done with improper condition if “Move to the next rinse step at acquisition complete” at pre-emptive rinse is set and acquisition time gets shorter than expectation by “Auto Integration Time Setting in Analog mode” at detector.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 2
Keyword: Queue
One-line Description:
Sequence would be terminated by an error when Sublist is in use
Problem:
A batch sequence might be terminated with an error by using both Sublist and P/A Factor Adjustment in QQQ. Error message / Exception: input string was not in a correct format
Temporary Solution:
Not to use P/A factor adjustment in batch or not to use sublist for Calibration samples.
Fix Information:
This was fixed in C.01.03 Patch 2
Keyword: Queue
One-line Description:
During batch sequence is running, correction equation might not be applied correctly when the setting on calibration pane is modified and then an acquired data file is imported.
Problem:
During batch sequence is running, correction equation might not be applied correctly when the setting on calibration pane is modified and then an acquired data file is imported.
Temporary Solution:
Process the batch twice.
Fix Information:
This was fixed in B.01.03 Patch 7
Keyword: Queue
One-line Description:
Pre-emptive rinse is not functioning correctly with certain conditions
Problem:
This occurs in very limited range of "Start rinse before acquisition complete" in preemptive rinse parameter. It was only occured when the value is 44, 45, 46, or 47 sec with a tested batch file. It may results in wrong quantitation value. Because the defect cause change of peri pump speed while acquisition is going on.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 7
Keyword: Queue
One-line Description:
Instrument Control of MassHunter may freeze
Problem:
Instrument Control of MassHunter may freeze because of dead lock with the following steps. 1) Create a new batch and set acq parameters -> Go to DA Method Tab -> enable Advanced Info then Add to Queue 2) After data acquisition, go to the batch task * and press "Requeue". (*The symptom occurs when the DA Method tab of previous batch is kept opened and then requeue is executed. )
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3
Keyword: Reports
One-line Description:
Printer paper size mismatch leads to Report footer (page number and printed date) not printing
Problem:
The footer of data analysis reports, tune report and printing current signal are not printed in case of their report templates are for A4 size paper.
Temporary Solution:
This issue occurs if "Letter" is set to "Tray 1 Size" and "Tray 2 Size". This printer configuration can be printed from "Information > Print Configuration" menu of the panel built on Printer itself (not Windows Control Panel). The resolution of this issue is to set "A4" to "Tray 1 Size" and "Tray 2 Size". The printer configuration can be changed from "Paper Handling" menu of the printer panel.
Fix Information:
This was fixed in A.01.02.
Keyword: Reports
One-line Description:
'Report Generate' makes an error, when Sample Name is blank.
Problem:
'Report Generate' makes an error, when Sample Name is blank.
Temporary Solution:
Make sure to put a sample name in each line
Fix Information:
This was fixed in A.01.02.
Keyword: Reports
One-line Description:
QC items are incorrectly labeled
Problem:
The field for the Pass/Fail flag for the Internal Standard check is swapped with the QC Check. This occurs for all report formats. "ISTDCheckPassFail" and "QCCheckPassFail" are coded the wrong way around.
Temporary Solution:
Replace position of "ISTDCheckPassFail" with position of "QCCheckPassFail" in report templates.
Fix Information:
It is not reproducible and waiting for a report of reoccrence.
Keyword: Reports
One-line Description:
Incorrect table header in tune report
Problem:
In a tune report, table header may not be displayed correctly. This could happen depending on number of report items, masses, and also printer page size selected.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Reports
One-line Description:
Some blank lines may be printed in tune report.
Problem:
When you print a tune report, some blank lines may be printed in the report.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.
Keyword: Reports
One-line Description:
System terminated when printing QuickBatch report
Problem:
Data Analysis system is terminated when printing QuickBatch report.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Reports
One-line Description:
Some last digits may be truncated in detail format of calibration curve report
Problem:
When you print the Calibration Curve report in detail format, some last digits of values may be truncated.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Reports
One-line Description:
Graph may not be displayed in Noise Report
Problem:
When you create a Signal to Noise Report in Chromatogram Batch, Graph may not be displayed in the Noise Report.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 7
Keyword: Reports
One-line Description:
Graph may not be displayed in Noise Report
Problem:
When you create a Signal to Noise Report in Chromatogram Batch, Graph may not be displaye in the Noise Report.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Reports
One-line Description:
MassHunter cannot generate sample reports with Concentration Replicates, slope, y-intercept and Ratio Replicates.
Problem:
MassHunter cannot generate sample reports with Concentration Replicates, slope, y-intercept and Ratio Replicates.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02 Patch 1.
Keyword: Reports
One-line Description:
Average count is not printed on the report by printing current signal
Problem:
This is only observed with single quad mode in 8800. Average count is not printed on the Printing Current Signal report.
Temporary Solution:
Use Tune report instead of the Printing Current Signal report.
Fix Information:
n/a
Keyword: Reports
One-line Description:
Calculation of Oxide ratio value in tune report is incorrect.
Problem:
Its numerator and denominator are reversed in the calculation of the ratio.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 1.
Keyword: Reports
One-line Description:
Quick Batch report may not work with SDA, ECM, or Data Store integration in a specific condition
Problem:
When MassHunter is configured with SDA, OpenLAB ECM, or OpenLAB Data Store, batch file that was created by a PC located in a different time zone cannot be stored. When you generate Quick Batch report with this configuration, MassHunter may be terminated or give an error. This is because that the batch cannot be stored at generating the report.
Temporary Solution:
Create a new batch and import data to the batch.
Fix Information:
This was fixed in C.01.01.
Keyword: Reports
One-line Description:
Report Designer is not opened properly
Problem:
When you open Report Designer, design canvas is grayed out. This is not a MassHunter defect. This is observed if Microsoft .Net Framework 4.5.1 is installed. The supported version of .Net is 4.5 for MassHunter 4.1 (G7201C C.01.01).
Temporary Solution:
Uninstall .Net 4.5.1 and use .Net 4.5 for C.01.01.
Fix Information:
n/a
Keyword: Reports
One-line Description:
"Generate selected sample" always prints the last sample only
Problem:
When you select some samples in Batch-at-a-Glance, then generate report with "Selected Samples", the report is generated only for the last sample.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 1
Keyword: Reports
One-line Description:
Number format problem of response ratio in full quant report.
Problem:
In full quant report, format of response ratio between analyte and ISTD is fixed to four digits after decimal point. This is a problem when count is low. When the value becomes around 0.0001, all values are printed as 0.0001 or 0.0000 and actually makes no sense.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Reports
One-line Description:
Sample WT/Vol and Final WT/Vol cannot be printed in C.01.01
Problem:
Quantitation report used until B.01.03 has a field PrepDilutionFactorFormula in which Sample WT/Vol, Final WT/Vol, and Multiplier is printed. But in C.01.01, the field is missing. Then user cannot print. The information normally should be available in sample analysis reports.
Temporary Solution:
None
Fix Information:
This was fixed in C.01.01.03.
Keyword: Reports
One-line Description:
PDF output feature prints wrong "Use gas" flag
Problem:
Using report option to output pdf of methods in data file, "Use gas" frag is printed wrong. It is printed "No" when gas is actually used. Using method printing feature from main menu, it is printed correctly.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 4
Keyword: Reports
One-line Description:
Printing of conc problem when it is below min conc.
Problem:
When calculated conc is below min conc, it is printed as empty in full quant reports by CRE. It should be printed like <30.000. In batch table it is displayed like <30.000.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 4
Keyword: Reports
One-line Description:
Actual RT for chromatographic analysis is not printed in reports
Problem:
Quantification Report cannot show the actual Detected Retention Time, but it shows expected Retention Time set in DA methods.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.01 Patch 4
Keyword: Reports
One-line Description:
PDF output feature prints wrong "Use gas" flag(For B.01.03)
Problem:
This is a copy of KPR #264(C.01.01) for B.01.03. Using report option to output pdf of methods in data file, "Use gas" frag is printed wrong. It is printed "No" when gas is actually used. Using method printing feature from main menu, it is printed correctly.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 4
Keyword: Reports
One-line Description:
Formatting final conc is not possible in reports
Problem:
Formatting final conc is not possible in reports
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Reports
One-line Description:
Using report designer, input information might be reflected correctly
Problem:
When too long formula is input in user defined columns, the formula is not reflected to templates after "Edit Table Properties" window is closed.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Reports
One-line Description:
Report designer ends by an exception
Problem:
Report designer ends by an exception, following procedure below. (1) Open custom property window and add any two userdefined column. (2) In the user defined 1 column, add any formula that refers to user defined 2. For example ISNULL(UserDefined_2,'a'). (3) Application ends by an exception. Error message / Exception: Cannot find column [The name of user defined column]
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Reports
One-line Description:
Wrong unit for parameters when methods are printed
Problem:
When acquisition method is printed, unit for EnergyDiscremination, Analog HV, and Pulse HV is printed as mV it should be V.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Reports
One-line Description:
Cannot generate EPA tune report.
Problem:
If you try to run EPA tune report in 8800, MH fails to generate report.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 1
Keyword: Reports
One-line Description:
Problem with "Print current signal"
Problem:
Makeup gas and Plate bias is not printed by "Print current signal"
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03 Patch 6
Keyword: Reports
One-line Description:
Cannot generate EPA tune report
Problem:
With 8800, tune reports are not generated in EPA mode. General mode is OK.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03
Keyword: Reports
One-line Description:
Malfunction with the printer HP LaserJet M506
Problem:
When HP LaserJet M506 is in use, print preview for Spike Recovery% Report - Precision or quick batch report is not displayed. Then you cannot print. Error message / Exception: A StartDocPrinter call was not issued
Temporary Solution:
Output the report as XPS file. And print the XPS file instead.
Fix Information:
This was fixed in C.01.03
Keyword: Start Up
One-line Description:
Warning about exchanging EM stops all remaining queued Hardware Tasks
Problem:
When EM optimization finishes successfully but Analog HV or Pulse HV exceeds certain value (Analog HV > 3300V or Pulse HV > 1800V), a warning message about exchanging the EM is shown. This warning is treated as a HW error and stops queue execution. This means that all remaining startup/hardware tasks after EM optimization may fail to run when using aged EM. Temporary Solution:
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Start Up
One-line Description:
“Select Monitored Masses” dialog box is not displayed if too many masses for P/A factor are set.
Problem:
If you set too many masses to P/A factor on startup or hardware settings, “Select Monitored Masses” dialog box is not displayed because “Monitored Masses” column gets too wide and its horizontal scrollbar blocks the dialog box.
Temporary Solution:
You can narrow the “Monitored Masses” column and show the dialog box by the following steps: 1. Double click the field containing the masses for P/A factor to enable changing the mass. 2. Type and set a mass to P/A factor. 3. Close MassHunter and restart it.
Fix Information:
This was fixed in A.01.02.
Keyword: Start Up
One-line Description:
Cannot edit mass for doubly charged ion in Startup parameters
Problem:
Cannot edit mass for doubly charged ion in Startup parameters in Japanese version.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 001.
Keyword: Start Up
One-line Description:
Deleting Hardware Optimization and aborting Startup may cause an error
Problem:
If some Hardware Optimization tasks are selected to run during Startup and these tasks are added to Queue, then all the tasks are deleted except for the first task ("Waiting for Warmup") then “Skip Warmup” is selected and the user clicks “Abort” in Realtime display, and selects "No" to Rinse, then an exception message will be shown.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Start Up
One-line Description:
The order of the items in Startup sequence is not carried out as expected.
Problem:
If you change the order of Startup items to be performed after adding them to the Queue, the order would not be changed as expected in the Queue.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Start Up
One-line Description:
Cancel Pausing Queue does not work for Startup tasks
Problem:
When you add Startup tasks to Queue and pause them, the task is paused after finihsing currently running task. It works for queued batches.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Start Up
One-line Description:
Putting startup items into queue might became impossible because of an error
Problem:
Putting startup items into queue became impossible because of an error that says "Failed to add Startup/Hardware tasks to Queue; Enter path for batch folder" Error message / Exception: Failed to add Startup/Hardware tasks to Queue; Enter path for batch folder
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02
Keyword: Start Up
One-line Description:
An extra rinse inserted into startup task when using 7800 plus ISIS3
Problem:
(1) Activate ICP-MS MassHunter for 7800. (2) Start ICP-MS instrument control. (3) Select ISIS3 and check Use ALS. (4) Set plasma on. (5) Add Torch Axis and EM to Queue and observe Tune/ISTD valve position and peristaltic pump rotation.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.02 Patch 2
Keyword: Tune
One-line Description:
Total acquisition time is not updated when a tune mode is added or removed.
Problem:
“Total Acq Time” displayed on “Acq Parameters” tab is not automatically updated when a tune mode is added or removed on “Tune” tab.
Temporary Solution:
Change a value of any field on “Acq Parameters” tab and then restore the field to the original value to update “Total Acq Time” after you add or remove a tune mode on “Tune” tab.
Fix Information:
This was fixed in A.01.02.
Keyword: Tune
One-line Description:
Range values of real time display are wrong in case auto scaling is applied.
Problem:
Auto scale function of tune tab and real time display of current sample acquisition in queue in timechart /TRA and Pre run Monitor mode sets range value for each mass automatically. This function is applied to plot area correctly but range values displayed in table area are incorrect.
Temporary Solution:
Turn off auto scaling and manually select the range value for each signal if you want to see correct range values.
Fix Information:
This was fixed in A.01.02.
Keyword: Tune
One-line Description:
System crashes when "Print Current Signal" is executed
Problem:
System crashes when "Print Current Signal" of tune tab is executed with monitored masses that have identical values. This issue is reproducibe in case a mass and numerator has the same value. For example, this issue occurs if mass 89 appears in two lines of monitored masses, or mass 70 and ratio 70/140 are set as monitored masses. The monitored masses for "Print Current Signal" is set by "Set Acq Parameters for Manual Sensitivity Tune" menu. In addition, clicking "Generate" button on "Generate Tune Report" dialog box causes another crash if the same masses are specified on the dialog box. (In this case, the same value of mass and ratio numerator does not reproduce the crash.)
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.01 Patch 001
Keyword: Tune
One-line Description:
Denominator mass is not printed in the current signal report
Problem:
Denominator mass is not printed in the current signal report. For example, current signal of "70/140" is printed just as "70". Also, "Count" field of the print does not have ratio value (the value of numerator count devided by denominator count) but only the count value of the numerator as well as "Average" and "RSD" fields that have only the numerator values.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.01 Patch 001.
Keyword: Tune
One-line Description:
Resolution/Axis peak is not displayed at the correct location
Problem:
Resolution/Axis peak is not displayed at the correct location if the first or second monitored mass for Resolution/Axis is blank.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02.
Keyword: Tune
One-line Description:
Tune parameters cannot be set
Problem:
When you click on Mass setting table in Batch > Acq Method > Tune, Tune parameters cannot be set (entering value to tune parameters, slide bar, radio buttons to select Plasma Mode, check boxes, renaming Tune mode tab...etc.).
Temporary Solution:
If you click the graph pane above the table, parameter settings would get back in available.
Fix Information:
This was fixed in A.01.02.
Keyword: Tune
One-line Description:
Error message when switch cell gas mode again during transition
Problem:
When the cell mode is changed quickly from "use cell gas" to "no cell gas" and back again within a few seconds, and monitor signals is selected, an error message is displayed. This occurs because the cell mode switch is activated during the transition from cell gas => no cell gas mode.
Temporary Solution:
Allow several seconds for transition delay before changing back from no cell gas to cell gas mode
Fix Information:
This was fixed in B.01.03.
Keyword: Tune
One-line Description:
Unused masses displayed in semi autotune for Deflect lens in gas modes
Problem:
Unused masses are displayed in semi autotune for Deflect lens in gas modes. This is a display issue, since the masses are not used for the tune.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: Tune
One-line Description:
Full Spectrum from Diagnosis will store wrong Tune Step Number of Previous Tune.
Problem:
Full Spectrum - Batch from Diagnosis will store wrong Tune Step Number of Previous Tune. Full Spectrum from Diagnosis will store Tune Step 1 as Previous Tune even if the specified batch has multi tune steps.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.
Keyword: Tune
One-line Description:
Wrong mass displayed during semi Auto Tune in No Gas mode (x-lens)
Problem:
Although Semi Auto Tune was excecuted with x-lens system (X-model), single mass for Cool Plasma mode was displayed on the screen. Although Semi Auto Tune was executed with x-lens system (7700x model), single mass for Cool Plasma mode was displayed on the screen. This phenomenon seemed to occur when plasma power was set to 800 W or less. Cool plasma mode should be available only with s-lens system (S-model).
Temporary Solution:
Do not set very low Forward Power with x-lens configuration
Fix Information:
This was fixed in B.01.01.
Keyword: Tune
One-line Description:
Tune report in Queue uses incorrect tune parameters
Problem:
When a batch which has Tune Report enabled is imported to Queue, the tune parameters in the batch should be used. However tune parameters will be used from the batch which is currently loaded.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01.
Keyword: Tune
One-line Description:
Tune report error when deleting all masses in a tune mode
Problem:
If you delete all masses in a tune mode and try to generate a tune report, a tune report error is shown.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 001.
Keyword: Tune
One-line Description:
"Firm Error" might occur on "Start Signal Monitor" in Resolution/Axis Pane
Problem:
"Firm Error" might occur on "Start Signal Monitor" in Resolution/Axis Pane .
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Tune
One-line Description:
High RSD% results in H2 tune mode
Problem:
RSD% is high in H2 tune mode. This is observed when setting up other gas modes, like No Gas and/or He.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 004 and B.01.01.
Keyword: Tune
One-line Description:
"Tune Check" is not printed in Batch Log.
Problem:
When "Tune check before batch" and "Print batch log at end" are selected, tune check will be performed in actual. The line of tune check will be printed in the printed batch log but description will be blank for Sample Type. This should be printed as "Tune Check".
Temporary Solution:
You can confirmed the selection of Tune Check on User Interface of MassHunter.
Fix Information:
This was fixed in B.01.02.
Keyword: Tune
One-line Description:
Reported items in Tune Report may differ between "in Queue" and "in Batch pane".
Problem:
Tune report can be generated either during a batch in Queue or batch pane. There may be different items reported between in Queue and in Batch pane. The parameter values themselves are correct.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Tune
One-line Description:
HMI Autotune may fail.
Problem:
HMI Autotune fails and finishes. This failure influences on preset condition of HMI-high.
Temporary Solution:
n/a
Fix Information:
This was fixed in A.01.02 Patch 5.
Keyword: Tune
One-line Description:
HMI Autotune may fail
Problem:
HMI Autotune fails and finishes This failure influences on preset condition of HMI-high.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.01 Patch 1.
Keyword: Tune
One-line Description:
MassHunter may be frozen when cancel semi auto tune with custom tune settings
Problem:
MassHunter may be frozen when cancel semi auto tune with custom tune settings
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.02.
Keyword: Tune
One-line Description:
"Introduce Tune solution" is prompted with GC
Problem:
When you start signal monitor in Tune with GC, "Introduce Tune solution" is propmpted.
Temporary Solution:
You can disable the message manually.
Fix Information:
This was fixed in C.01.01.
Keyword: Tune
One-line Description:
"Invalid tune parameter name is specified." is displayed by changing EM parameters
Problem:
The error message "Invalid tune parameter name is specified." is displayed when one of EM parameters is changed during signal monitor of user tune. The parameters causing this issue are Discriminator, Analog HV and Pulse HV in EM group of User Tune. The issue appears only in User Tune with the condition that signal monitor is running. The parameter change has no problems if signal monitor is not running in User Tune, or anytime in the Tune tab of Batch task.
Temporary Solution:
n/a
Fix Information:
This was fixed in B.01.03.
Keyword: Tune
One-line Description:
Exception on importing tune modes to user tune
Problem:
Exception on importing tune modes to user tune. (1) Import multiple tune modes to user tune from a batch (2) Delete some tune modes in user tune (3) Import from batch in (1) to restore tune modes deleted in (2). (4) Click "Send to ICP-MS" in user tune. Occures only when import option in (3) is "Add if Not Exist"
Temporary Solution:
Any one of below two. A. Close and re-open MassHunter between step (3) and (4) B. Select import option other than"Add if Not Exist" but "Replace All"(In case replacing all tune mode is acceptable)
Fix Information:
n/a
Keyword: Tune
One-line Description:
Set Acq Parameter for Manual Sensitivity Tune could be disappeared
Problem:
When double-clicking a cell in the 'Numerator' column to set parameters in User Tune, the 'Set Acq Parameter for Manual Sensitivity Tune' box is diappeared.
Temporary Solution:
n/a
Fix Information:
n/a
Keyword: Tune
One-line Description:
MassHunter may crash when customer input Q2 value in “Set Acq Parameters for Sensitivity”.
Problem:
MassHunter may crash when customer input Q2 value in “Set Acq Parameters for Sensitivity”.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 1
Keyword: Tune
One-line Description:
Cannot perform autotune for batch in TRA mode
Problem:
Exception occurs during auto tune in TRA mode. Error message / Exception: Object reference not set to an instance of an object.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 2
Keyword: Tune
One-line Description:
Q-pole parameters are not reflected to EPA mode tune report
Problem:
Q-pole parameters are not reflected to EPA mode tune report, although custome tune and enable override hardware setting are applied.
Temporary Solution:
n/a
Fix Information:
This was fixed in C.01.03 Patch 3