Software Status Bulletin

Walkup     

Preface
-------------------------
This Software Status Bulletin (SSB) documents all known problems in the software
product designated above. The SSB is derived from Known Problem Reports (KPR)
which result from user problems that have been classified as documentation
problems or software defects. When a KPR is written, an identifying number is
assigned to it, and the KPR is added to the next edition of the SSB.

User inputs that have been classified as Enhancement Requests are not documented
in the SSB. User problems that have been submitted, but that have not been
classified by the time the SSB is generated are not included in the SSB.

How to use the SSB
-------------------------
When you experience a problem with a product, first check this SSB to see if the
problem has been reported already, and if there is a temporary workaround
available for the problem, or if the problem has already been fixed by a new
revision. If the problem is not listed in this SSB then you may wish to report
it to the Response Center or to your field support representative.

To determine if your problem is documented in this SSB, first look in the
Keyword Index section of the SSB. Under each keyword is a listing of one-line
descriptions of related KPRs. If any of these sound like yours, locate the KPR
# in the Known Problem Reports section of the SSB, and read the full KPR. The
KPRs in the Known Problem Reports section are sorted by KPR #.

There are two sections in the SSB:
Keyword Index: This index is categorized by keyword. For each KPR there is a
brief description and a KPR #. A KPR may be associated with more than one
keyword.

Known Problem Reports: This section contains KPRs, with all the available
information relevant to the problem. KPRs in this section are sorted by KPR #.

Keyword Glossary

Keyword Index

Keyword: User Interface

KPR#:292808 Sample Information Pane Not Localized in Japanese

Keyword: 

One-line Description:

Walkup Help opened from the Walkup Console does not respond to user actions when user is in Sample Submission or Administration

Problem:

01. In the main UI, press F1.  "Active Samples View" is displayed.
02. Click "Submit Samples". The User Login Page is displayed.
03. Fill in user name and password, Press F1. "Sample Submission" help is displayed. (behind Walkup window)
04. Try to close the Help window. The window cannot be closed.
05. Cancel sample submission. The Main UI is displayed.  Try to close the help window .The window can now be closed.

Temporary Solution:

1. If the user is on "Sample Submission" or "Walkup Administration", then the user should go back to the main "Walkup Console".
2. Close the Help window.
3. Open "Sample Submission" or "Walkup Administration" window, as needed.
4. Open the Help window. The Help window will be accessible.

Fix Information:

n/a

Keyword: 

One-line Description:

In "Maintenance Mode," Help goes behind the watermark when Walkup console is clicked.

Problem:

1. Put instrument into maintenance mode
2. Press F1 to view Help
3. Try to move the Main UI. Help goes behind the watermark.
4. Press F1 again. Help is accessible.
5. When Help is behind watermark, it can also be accessed from the toolbar.

Temporary Solution:

Click Help -> View Help.

Fix Information:

n/a

Keyword: 

One-line Description:

"Object reference error" gets displayed if user tries to RDP into a machine which has a walkup login dialog box up.

Problem:

How to reproduce:

01. Launch walkup application from a machine. 
02. Login dialog box gets displayed. 
03. Now from another machine, use remote desktop protocol to remote into the Walkup machine,
04. Object reference error gets displayed.

Temporary Solution:

Log into Walkup before connecting via RDP.

Fix Information:

n/a

Keyword: 

One-line Description:

When Custom Queue sorting with method priority is used, vial samples do not get prioritized by method priority if plate samples are present in the queue.

Problem:

01. In Queue Logic, select Custom > Method Priority > Group Priority.
02. Verify & Save the settings.
03. Perform sample submission in the following order :
      3 samples from vial with Method which has priority set to " 5 "
      3 samples from plate with Method which has priority set to " 6 "
      3 samples from plate with Method which has priority set to " 7 "
      3 samples from vial with Method which has priority set to " 1 "
04. The samples from Method with priority " 1 " do not move to the top of the queue if the queue is not started.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

"Run about to end" message will display if the destination data storage volume is full

Problem:

Currently, WalkUp will not correctly report that the destination data volume is at capacity. Instead, it will report that the "run about to end" and the instrument will remain in an idle state.

Temporary Solution:

The administrator of the system should monitor the disk usage and delete files as needed.  It is also suggested that the administrator utilize the copy data file feature and enable the "Delete after copy" function. 

Fix Information:

n/a

Keyword: 

One-line Description:

Status.ini file does not show correct solvent channel information on Bin Pump with Solvent selection valve

Problem:

The Status.ini file currently always reports A2 as the solvent channel for any solvent drawn from the B, C, or D solvent channels on the binary pump.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Incorrect user reported on ASR report with OpenLAB ChemStation setup in Internal authentication mode

Problem:

If a OpenLAB ChemStation Walkup user is set to Internal authentication, and multiple users are configured, Walkup will generate ASR reports which will include the user who launched Walkup - not the user who submitted the sample.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

In MassHunter ASR Sample processed time dosen't get updated, it shows default time as "1/1/1970 12:00 AM".

Problem:

In regions and languages, format was set as English ( United States ). The MassHunter ASR report shows default processing time as "1/1/1970 12:00 AM" for every sample.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Exception message is thrown, if user starts Walkup Remote mode after upgrading Walkup from previous version.

Problem:

In a large lab configuration, if OLSS, ChemStation, and Walkup are all upgraded from previous revisions, it's possible to encounter an exception message on launch of walkup remote administration.

Temporary Solution:

Start the Walkup software on the instrument controlling PC first, then launch the remote administration. When launched in this order, the error is avoided.

Fix Information:

n/a

Keyword: 

One-line Description:

Unable to run samples on a custom well plate immediately after creating the custom well plate..

Problem:

After creating a custom well plate for an LC autosampler - one cannot immediate run samples.

Temporary Solution:

After creating the custom well plate, shutdown Walkup and ChemStation. Then re-start ChemStation then Walkup. The custom well plate will now work.

Fix Information:

n/a

Keyword: 

One-line Description:

When "Data File Transfer" is enabled in Walkup, the resulting data files are transferred to specified location on a background thread.

Problem:

When "Data File Transfer" is enabled in Walkup, the resulting data files are transferred to specified location on a background thread. For single sample submissions, this is done per file. However, when "Group Results by Job" is selected, this transfer is done only when the complete job is over. For a job with many samples or where the data files are of large size, the data file transfer activity will need time to finish. If in such scenario, user shuts down Walkup, the Walkup Console will go away immediately. However, the file transfer thread takes time to exit. This results in a situation where the Walkup console is visible and user cannot launch Walkup using "Walkup -> Start Software" menu in MassHunter or ChemStation console. This menu option gets enabled only when the data file transfer is complete.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Status.ini file does not show correct solvent channel information on Bin Pump with Solvent selection valve

Problem:

Configure a system with bin pump which has inbuilt SSV value.

Create data system methods with various solvent parameters.

Now assign this to Walkup method and also configure status notification settings.

Carryout sample runs, open the status.ini file.

In status.ini file B1& B2 solvent channels are not displayed and correspondingly the value are also not reflected.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Behavior is inconsistent between MassHunter and ChemStation for UV wavelength override feature of Walkup

Problem:

With ChemStation, if user doesn't select Wavelength check in data system method and carryout a sample run through Walkup with wavelength specified. Then wavelength Specified through Walkup is not used and data is not acquired against it. Where as, if we do the same use case with MassHunter data system, the data is acquired against specified wavelength. MassHunter data system plug-in, enables the setting in the data system method so that the Walkup-provided wavelength always get used.

Temporary Solution:

Known behavior. Fix not available.

Fix Information:

Known behavior. Fix not available.

Keyword: 

One-line Description:

Difference in behavior between Walkup running on MassHunter and on ChemStation - data file path length warning behavior

Problem:

A behavior mismatch has been discovered between MassHunter and ChemStation as it pertains to warning the user of data file + path lengths during sample submission. 

For Walkup with MassHunter if file name length exceeds 256 characters, the sample run will fail. No warning is given when the sample is being submitted.

For Walkup with ChemStation if file name + path exceeds 256 characters, a warning message is displayed during sample submission and user is restricted from submitting samples.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Multisampler 2ml vials can be submitted on 1H drawer height

Problem:

For Multisampler 2ml vials can be submitted on 1H drawer height
1. User can submit 2ml vials can be submitted on 1H drawer height for Multisampler.
2. Walkup hangs after the run starts.
3. There should be validation to prevent user from submitting 2ml vials on 1H drawer height

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

For events of type "Before Every Job" - overlap injection does not work

Problem:

When events of type "Before Every Job" are configured to run before any injection - the "Overlap Injection" feature does not work. Instead - the vial is not retrieved until the "Before Every Job" event has completed.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Calibrate QTOF on Wakeup is using the wrong calibrant bottle 

Problem:

Walkup can be configured to automatically calibrate the TOF when it is awakened from standby. However - it can be observed that the wrong calibration bottle is being opened by the CDS system (bottle A instead of bottle B).

Temporary Solution:

n/a

Fix Information:

This is now fixed in Walkup 4.0.

Keyword: 

One-line Description:

On OpenLab system, for blank runs, instrument dashboard shows sample position of previous sample

Problem:

Created a Acq method where for 'Pump' stop time is given and for 'Multisampler' 'AsPump/No Limit' is selected.
When this method is used in Acquisition Console or WalkUp and sample is submitted with no position, the dashboard displays the position of previous executed sample.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

ASR File Generator Extracting M+ ion EIC, ignoring M+H or other adducts

Problem:

Starting with ChemStation C.01.08 and continuing through C.01.09 - the ASR File Generator began ignoring the charge carrier/adduct settings in the sample purity options dialog. This led a defective behavior where the ASR report/file would always display the EIC of the M+ ion - instead of the M+1 ion more commonly required. 

Temporary Solution:

n/a

Fix Information:

Fixed in ASR B.02.04

Keyword: 

One-line Description:

Sample Purity Options dialog becomes read-only when ASR File Generator is installed

Problem:

Starting with ChemStation C.01.08, and in C.01.09 - once the ASR File Generator was installed - the user was no longer able to edit or save any of the settings in the Sample Purity Options dialog. This led to numerous defective behaviors including the inability to change the charge carriers used in Data Analysis. 

Temporary Solution:

n/a

Fix Information:

Fixed in ASR B.02.04

Keyword: 

One-line Description:

Walkup does not support SMTP servers with non-secured connections

Problem:

Walkup's built-in email functionality does not currently support non-secured SMTP server connections. All SMTP interaction must be authenticated with a user and password. 

Temporary Solution:

n/a

Fix Information:

WalkUp 4.0 now supports SMTP servers with non-secured connections.

Keyword: 

One-line Description:

ASR display incorrect vial locations with Multi-Sampler on A10, A11, A12, always display A1

Problem:

ASR display incorrect vial location with Multi-Sampler -any position greater than 10, (i.e. A10, A11, and A12) will display A1 vial location.

Temporary Solution:

n/a

Fix Information:

This defect was fixed with the release of ASR B.02.04.

Keyword: 

One-line Description:

Method name length can cause Walkup to fail to run sample

Problem:

There is also an issue with Walkup and ChemStation method name lengths. It is possible, for example - if the method name gets too long - Walkup will fail to run the methods.

Validation should be done to test the name length before allowing the admin to save.

Temporary Solution:

n/a

Fix Information:

WalkUp will not provide active validation feedback:

ChemStation method name validation: 62 characters
Warning message is displayed if user enter more than 62 characters while saving method

WalkUp method name validation: 40 characters
User is restricted from entering more than 40 characters.

ChemStation data file path validation: 160 characters
Warning message is displayed during sample submission in WalkUp and user is restricted from submitting samples.

Keyword: 

One-line Description:

Inclusion of custom columns in report is different between Qual B.08.00 and Qual 10.0

Problem:

With Qual 10.0, when PDF based reporting is selected, all the workflow columns are not mentioned in the reports.

Temporary Solution:

Qual 10.0 has two reporting options - Excel based reporting and PDF based reporting (default). 

When PDF based reporting is selected the custom\target columns added in workflow need to match following criteria so that such columns appear in report.
- For column type "Custom" - column name must start with "CU" or "cu" or "WK". Such first 3 columns will be included in report.
- For column type "Formula Confirmation" - column name must start with "MFC". Such first 3 columns will be included in report.
- For column type "Masses" - column name must start with "Mass". Such first 3 columns will be included in report.
- For column type "DAWorkflowQual" - column name must start with "DAWorkflowQual". Such first column will be included in report.

Fix Information:

None

Keyword: 

One-line Description:

Total Wavelength Chromatogram is not part of the ASR report

Problem:

The "DAD --> Generate Total Wavelength Chromatogram" menu generates the graph which can be seen in ChemStation. The same graph is not available in ASR report generated for the same data file.

Temporary Solution:

n/a

Fix Information:

Fixed in ASR B.02.04

Keyword: 

One-line Description:

WalkUp need to be restarted to continue the queue if instrument goes in error state because of any hardware related issues

Problem:

WalkUp need to be restarted to continue the queue if instrument goes in error state because of any hardware related issues. Error need to be cleared from Instrument Dashboard before clearing error from WalkUp administration and resuming the queue. But when WalkUp is running dashboard's access is disabled 

Issues can be - 1) Missing Vial 2) Instrument error (Leak or Bottle ran out of Solvent )

Temporary Solution:

1. Shut down WalkUp 
2. Take control for Acquisition Console. 
3. Clear the instrument errors from instrument dashboard.
4. Release the control. 
5. Launch WalkUp again to continue with sample submission and execution.

Fix Information:

n/a

Keyword: 

One-line Description:

Failed to get active samples error on initial Walkup login

Problem:

We know of one scenario where this error condition can occur.

When a user deletes an event with blank position and then resubmits it.

Temporary Solution:

n/a

Fix Information:

This issue is no longer relevant in WalkUp 4.0, as deleted events cannot be resubmitted. 

Keyword: 

One-line Description:

On Windows 10 system, the touch screen does not react appropriately to the touch gestures

Problem:

In older versions of Windows 10, it is observed that the touch gestures are not responded correctly. This is a knows issue with Windows 10. This issue is fixed with latest versions of Windows 10. WalkUp UI is tested with Windows 10 Version 1803 (OS Build 17134.619) and it works fine. The shipping machine should have at least this version/build of Windows 10.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

WalkUp System Stops Running Plates at Midnight When Using Delay Feature

Problem:

A user reported that they are using the "Delay running plate" feature.  They start running plates at 10 pm every night.  However, the method for each sample is long.  When the PC clock reaches midnight (12 am), the system stops running the plate. This is not the desired behavior. 

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

When individual tray/plate is cleared, the next fraction location/recovery location on the fraction collector device does not get reset

Problem:

Following behavior is observed when runs are taken from ChemStation directly or through Walkup:
In clustered configuration where one G1364F is configured as FC and other as RC, if we reset individual recovery containers then the UI is cleared of recovery but the next recovery location used is the same as that would have been calculated before the reset. At one point of time there won't be any next recovery location available and sample would fail.

Temporary Solution:

This issue is not observed if we do a "Reset All" when doing from ChemStation or select the checkbox in top row in "Clear Fraction Collector" UI. While working with Walkup, make sure to clear all plate/trays to avoid this issue.

Fix Information:

This issue is a known behavior of the LC driver A.02.18. Future release of the driver (A.02.19 or later) is expected to solve this issue. Walkup need not have any code changes to resolve this issue.

Keyword: 

One-line Description:

Automatic methods (like equilibration, or wakeup) methods have 20 characters appended to the method name when triggered - will throw an error if total method length is greater than 40 characters

Problem:

ChemStation supports ChemStation method name length up to 40 characters and sample name length up to 40 characters. When a sample is triggered by WalkUp system, in some cases, method name is used as part of sample name. For longer method names, the sample name could go beyond 40 characters resulting failure of the sample. In earlier releases, the error message wasn’t user friendly.

Note - when triggering dynamically submitted methods (for example, when running as an equilibration event or a wake-up method) WalkUp will append up to 20 characters to the original methods' name.

Temporary Solution:

Make sure that all Walkup method names and ChemStation method names are less than 20 characters.

Fix Information:

Validation has been added so that, for any reason if the sample name goes beyond 40 characters, the sample would be marked fail with user friendly message such as “Sample name length cannot be more than 40 characters”.

Keyword: 

One-line Description:

On Launch of WalkUp on OpenLAB CDS 2.4 - "Paused for error. Failed to get sample containers"

Problem:

It has been observed that occasionally, when WalkUp (installed with OpenLAB CDS) launches, the WalkUp sample/tray diagram will be empty or incorrect (showing a different plate configuration than what is displayed in OpenLAB). An error message is also noted in the status window which reads "Paused for error. Failed to get sample containers". 

Temporary Solution:

As a temporary workaround - To recover from this situation, do the following. Repeat more than once if it does not work on first attempt:

    Shutdown WalkUp.
    Close OpenLab Acq Console
    "Close Connection" from OLCP.
    Relaunch everything.
    Alternatively restart the machine.

Fix Information:

n/a

Keyword: 

One-line Description:

WalkUp on OpenLAB CDS 2.4 stops processing samples with no error

Problem:

It has been observed that occasionally, while WalkUp (installed with OpenLAB CDS) is running samples, the WalkUp sample queue stops with no error or warning. This has been observed after 1 sample has run successfully and after multiple samples have run successfully. 

When this error condition is observed, the WalkUp Queue status box will report "Running", while the OpenLAB CDS, Instrument, and Injector status boxes report "Ready". The WalkUp System status box reports "Starting run" or "Acquisition in Progress" but never proceeds. The system is otherwise perfectly responsive. 

No error is recorded in any logbook.

Temporary Solution:

As a temporary workaround - to recover from this situation, do the following. 

1.) Close WalkUp (with samples still pending in queue).
2.) Switch the instrument On/Off from the OpenLAB CDS instrument panel (perhaps 2-3 times).
3.) Relaunch WalkUp and resume the queue.

If this does not work, do the following. Repeat more than once if it does not work on first attempt:

1.) Shutdown WalkUp.
2.) Close OpenLab CDS.
3.) "Close Connection" from OpenLAB Control Panel.
4.) Relaunch OpenLAB CDS.
5.) Alternatively restart the LC instrument (not necessarily the MS).

Fix Information:

n/a

Keyword: 

One-line Description:

"Case" of user name cannot be changed once user is created

Problem:

In WalkUp Administration, when administrator tries to change the case of user name (e.g. from "Tom" to "TOM"), and tries to save it, no error/warning is given however data is not saved.

Temporary Solution:

Delete the existing user whose name is to be changed and create a new one.

Fix Information:

n/a

Keyword: 

One-line Description:

Target column can be removed from sample submission using a no-column workflow

Problem:

Some might be confused as to why a 'Target' column is displayed on page 2 of the WalkUp sample submission console. This field is reflecting the fact that the selected workflow has the potential to receive an input to be used by the Data System - even though it is optional.

Temporary Solution:

n/a

Fix Information:

If the "target" column is causing issues for a lab - simply configure a 'Workflow' in the WalkUp administration console with no rows defined in the table. If this is the only workflow - it will become the default and users will no longer see a 'Target' column during sample submission.

Keyword: 

One-line Description:

Only use Unicode encoded files to import non-Latin alphabet characters

Problem:

WalkUp supports non-Latin character sets like Chinese and Japanese when importing users or sample lists via CSV or TXT or XLSX or XLS. However - those files must be Unicode encoded text files - and not ANSI or other encoding formats because they do not support non-Latin alphabets. 

Temporary Solution:

n/a

Fix Information:

Always use UTF-8 (Unicode) encoded text files for importing non-Latin alphabets into WalkUp.

Keyword: 

One-line Description:

Error while using Remote Sample Submission

Problem:

An error message has been encountered during internal testing of the Rapid Sample Submission workflow. The error occurs when the user submits the same. The text of the error is: "Not enough context to add a new row. Either a row in this band or parent band has to be active to provide for enough context."

Temporary Solution:

Ignore the error message and click OK. Click Submit again and the submission will proceed without further error.

Fix Information:

n/a

Keyword: 

One-line Description:

"Object reference not set to an instance of an object" error seen while submitting samples on Custom plates.

Problem:

During sample submission – a user selects an imported/custom well plate from the drop down list and an error is immediately seen:
“Object reference not set to an instance of an object.” 

Temporary Solution:

The custom well plate can still be used in the underlying data system. But only standard pre-defined well plates can be used with WalkUp 4.0.

If the customer must use a custom well plate – WalkUp will need to be downgraded to revision C.03.02. 

Fix Information:

n/a

Keyword: 

One-line Description:

Custom plates similar to 15VialPlate are assigned to 2H multisampler drawers

Problem:

The 15VialPlate is tall enough that it can only fit into 3H drawers. However - WalkUp is unable to detect how tall it is given the dimensions defined in the well plates table. As such - WalkUp can assign a 15VialPlate submission to a 2H drawer in the multisampler. 

Temporary Solution:

n/a

Fix Information:

To permanently avoid this condition - one would fill their multisampler with ONLY 3H drawers - in which case an incompatible drawer could never be assigned.

Keyword: 

One-line Description:

G2260A Preparative ALS not properly recognized by WalkUp

Problem:

WalkUp currently does not properly recognize the G2260A Preparative ALS in the autosampler configuration. This prevents the autosampler from functioning with WalkUp. 

Temporary Solution:

Agilent has a workaround available which can be provided by contacting WalkUp product support. Please contact your Agilent support representative and have the issue escalated. 

Fix Information:

This has been fixed in WalkUp 4.1.

Keyword: 

One-line Description:

Removing fraction collector trays can cause WalkUp to collect fractions into already-filled positions

Problem:

A defective behavior has been discovered in MassHunter WalkUp 4.0 and ChemStation C.01.09 or C.01.10 with how fraction collector tray fill volumes are cleared when the FC’s trays are removed and reinserted into the fraction collector. This has led to cases where WalkUp will collect fractions into vessels that had already been filled during previous runs. 

An “Always Safe” tray clearing protocol is described here may help reduce the likelihood of this situation. However, one customer reports that even while following this protocol – they still run into issues

Temporary Solution:

n/a

Fix Information:

The “G1364x” fraction collector modules have a feature to support fraction “pooling” where fractions are collected into the same vessels as previous injections. To support this feature, there is some complex logic in the fraction collector firmware to handle the fill volumes of the fraction vessels whenever the fraction collector door is opened and closed. This logic is incompatible with WalkUp 4.0 as currently designed, which means fraction “Pooling” is not supported with WalkUp 4.0.

When the fraction collector door is closed, the fraction collector transport assembly scans the RFID on the FC tray. If the current tray has the same RFID serial number as the tray present before the door was opened – the FC will reload the fraction fill volumes “known” for that tray before the door was opened. As such, any “Clear tray” commands sent by the system before the door is closed will be “undone” by the FC’s restoration of the fill volumes. WalkUp was not aware of this and does not know that those fill volumes are being restored (while ChemStation does). This leads to a condition where WalkUp instructs the system to collect fractions into vessels that already contain liquid. 

The following “always safe” procedure will prevent WalkUp from collecting fractions in already filled vessels. WalkUp does not support fraction pooling. 

1.)    Before the tray is removed, a popup appears whenever the fraction collector door is opened and again when it is closed. When the popup is seen, click “same tray, with fractions”.

2.)    Once the tray is pulled out of the fraction collector, the user should remove all fractions from the tray. A fraction collector tray should always be placed in the fraction collector empty/clear of all fractions. 

3.)    Once the tray is inserted, and the door is closed, the fraction collector will scan the RFID on the tray. Again, the user should select “same tray, with fractions”. 

4.)    Finally, the WalkUp user should click the “Clear Fraction Collector Tray” in the WalkUp ribbon before the next sample run.  

Keyword: 

One-line Description:

Not possible to recover from leak condition from within WalkUp

Problem:

With WalkUp running, it is not possible to clear a leak from within WalkUp. One must click the 'On' button in the data system (CDS 2.4, ChemStation, or MassHunter) outside of WalkUp. 

Temporary Solution:

n/a

Fix Information:

Fixed in WalkUp 4.1 - clicking the "Instrument On" button in WalkUp will now clear errors as if clicking the "On" button in the driver pane. 

Keyword: 

One-line Description:

Dual wavelength VWD returns invalid error message when set wavelength is out of range

Problem:

There is a defect in the LC Driver 3.2 which returns an invalid error message to WalkUp when the user sets a wavelength which is outside the allowed range for the Dual-Wavelength VWD. The error message returned reports "@@success". It should read "wavelength is out of range".

Temporary Solution:

n/a

Fix Information:

This will be fixed in LC Driver version 3.3.

Keyword: 

One-line Description:

Removing Trays from G7129B Vial Autosampler Can Break WalkUp's sample queue

Problem:

The G7129B vial autosampler has the capability of sliding the vial trays out of the autosampler to allow for easier access when placing or removing vials. 

However - a defect has been discovered which causes WalkUp to remove already submitted samples from the sample queue when either tray is removed. 

Temporary Solution:

It is very important that when running with WalkUp - users may not move trays out of the autosampler. Vials can be added to the trays with the doors open - but the trays should not be pulled out of their home positions. 

The external vial tray can also be used to more conveniently add vials to the autosampler.

Fix Information:

n/a

Keyword: 

One-line Description:

BioConfirm Sequence Manager and other sample submission "Pop-outs" are not supported with WalkUp's "Secure Mode"

Problem:

WalkUp has a feature called "Secure Mode" which causes all UI interfaces to be disabled while WalkUp is running. This allows an administrator to contain lab users to only interact with the WalkUp application. However - due to a technical limitation, this mode also prevents users from interacting with the BioConfirm "Pop-Out" windows which let users select the protein sequences, modification profiles, and digest reagents to be used in a BioConfirm automation workflow.

Temporary Solution:

If running BioConfirm workflows with WalkUp - one must either disable "Secure Mode" in WalkUp - or shutdown WalkUp after data files have been acquired to process the data in BioConfirm interactively (instead of automatedly). 

Fix Information:

n/a

Keyword: 

One-line Description:

Do not use unresolved methods for samples submitted in WalkUp

Problem:

A user has found that when attempting to submit a sample using the Rapid Sample Submission interface in WalkUp applying a method which has not gone through method resolution on that instrument - unexpected errors are seen in the WalkUp UI like "Failed to validate UV Wavelength".

Temporary Solution:

n/a

Fix Information:

It is expected that all methods used for a Walkup sample submission have already gone through method validation on the LC/MS data system. 

Keyword: 

One-line Description:

Invalid tray configuration error with CDS 2.5 and WalkUp 4.1 - occurs only on first run

Problem:

A defect has been discovered in the CDS 2.5 interface which WalkUp 4.1 uses. This defect causes CDS to fail to set a sample tray on first run. Once the first sample fails - all subsequent runs finish successfully.

Temporary Solution:

One can resubmit the initial failed sample from the Administrators console -> Incomplete Samples Queue.

Fix Information:

n/a

Keyword: 

One-line Description:

Submitter online Help supported on Edge and Chrome only

Problem:

Submitter online Help supported on Edge and Chrome only.

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

WalkUp unable to submit samples on 16 x 150 tube containers in Openbed Fraction Collector

Problem:

A defect has been discovered in WalkUp 4.1 which causes the software to throw an error message when a sample submitter attempts to submit samples for any 16 x 150 tube containers on the Openbed Fraction Collector.

The error occurs when the user clicks the "Submit" button after selecting a 16 x 150 Tube Container "Container" on the first page of the Rapid Sample Submission console. 

The error reads "Sample tray is full of pending, incomplete, or completed samples. Please clear sampler tray." This message occurs even if the sampler tray is already cleared, even after re-clearing the tray after encountering this error.

This error does not occur with any other container type. For example,  30 x 150, 12 x 150, 16 x 100, and an SBS container with 15 vial plate all work as expected.

Temporary Solution:

As a workaround, the user could submit samples with any other container type. For example, 30 x 150, 12 x 150, 16 x 100, and an SBS container with 15 vial plate all work as expected.

Fix Information:

This defect requires code change in the WalkUp 4.1 application.

Keyword: 

One-line Description:

WalkUp method validation on .amx files throwing errors on CSV and PDF outputs missing

Problem:

When importing CDS 2.x methods, WalkUp's method validation process will throw error messages when email is configured to send PDF/CSV reports - that the amx files are missing these outputs. 

Temporary Solution:

n/a

Fix Information:

This has been fixed in WalkUp 4.2

Keyword: 

One-line Description:

Underscores cannot be used in sample name field with DA reprocessor

Problem:

Do not use "_" underscore characters in the sample name of any data files acquired via WalkUp or any other application. This character is an invalid value for the DA Reprocessor and will cause DA Reprocessor to fail with error. 

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

WalkUp 4.2 does not stay in the foreground with QTOF Acquisition 11

Problem:

While running samples with WalkUp 4.2 and QTOF Acquisition 11 - the Acquisition UI will continually jump in front of the WalkUp console whenever a sample run is completed. 

Temporary Solution:

As a workaround, you can enable "Secure Mode" or "Hide Data System" in the WalkUp administration console. 

Fix Information:

n/a

Keyword: 

One-line Description:

WalkUp Configuration Export fails to import into WalkUp 4.2

Problem:

WalkUp version 4.2 requires a specific block of information to be included in the UserGroup.xml (part of the WalkUp configuration export payload created from the Administrator -> Export feature) which is not included with the exports generated by WalkUp 4.1 and prior. 

Temporary Solution:

n/a

Fix Information:

This is fixed as of WalkUp 4.2 Update 01.

Keyword: 

One-line Description:

Only simple SMTP email sending supported by Walkup

Problem:

WalkUp uses SMTP (Simple Mail Transport Protocol) to relay emails and notifications. WalkUp cannot use Exchange or any complex authentication standards for email. 

The setting "Use Secure Connection" will enable SSL.

WalkUp only supports the SMTP Service Extension for Secure SMTP over Transport Layer Security as defined in RFC 3207. In this mode, the SMTP session begins on an unencrypted channel, then a STARTTLS command is issued by the client to the server to switch to secure communication using SSL. See RFC 3207 published by the Internet Engineering Task Force (IETF) for more information.

An alternate connection method is where an SSL session is established up front before any protocol commands are sent. This connection method is sometimes called SMTP/SSL, SMTP over SSL, or SMTPS and by default uses port 465. This alternate connection method using SSL is not currently supported. 

Temporary Solution:

n/a

Fix Information:

n/a

Keyword: 

One-line Description:

Rapid Sample Submission interface limited to 9 samples submitted at a time

Problem:

The Rapid Sample Submission interface does not allow a user to submit more than 9 samples at a time, even when the administrator has allowed the user to submit more than 9 samples.

Temporary Solution:

This is a limitation of the RSS interface. The current workaround is to use the "Standard" sample submission interface - which is set in the Administrator context -> Laboratory tab. 

Fix Information:

n/a

Keyword: User Interface

One-line Description:

Sample Information Pane Not Localized in Japanese

Problem:

The sample information which is displayed in the mouse-over popup of the tray diagram is not currently translated into Japanese. It will be displayed in English. 

Temporary Solution:

n/a

Fix Information:

This will be addressed in a future WalkUp release.