R E L E A S E N O T E S Waters and “THE SCIENCE OF WHAT’S POSSIBLE.” are registered trademarks of Waters Corporation. All other trademarks are the sole property of their respective owners. Copyright 2014 Waters Corporation Page 1 of 51 *716004166* *Rev.A* Waters Empower 3 Service Release 2 Waters ® Empower ® 3 Service Release 2 (SR2) corrects various software defects. These release notes contain the following important information for installing and using Empower 3 Service Release 2 software. Unless superseded, all previous release notes and product support information apply to this software release. Table of Contents Table of Contents ....................................................................................................................... 1 GxP compliance requirements .................................................................................................... 4 System and software requirements ............................................................................................ 4 Before you install Empower 3 SR2 software ............................................................................... 4 Install Empower 3 Service Release 2.......................................................................................... 5 After installing Empower 3 Service Release 2 ................................................................................. 5 Install Empower 3 SR2 on a single computer ................................................................................. 5 Install Empower 3 SR2 on multiple computers using the PsExec utility .............................................. 6 Install Empower 3 SR2 on multiple Citrix servers ........................................................................... 9 Verify the Empower 3 Service Release 2 installation ................................................................ 10 Enhancements added to this release ........................................................................................ 10 Issues fixed in this release ....................................................................................................... 11 Issues fixed in Empower 3 SR2 ...................................................................................................12 Issues fixed in Impurity Processing .............................................................................................13 Issues fixed in Agilent GC Instrument Control ...............................................................................13 Issues fixed in Empower Toolkit ..................................................................................................14
51
Embed
Waters Empower 3 Service 2 Release Notes · 2014-07-02 · After installing Empower 3 Service Release 2, when you log into Empower, the software automatically updates your projects.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
R E L E A S E N O T E S
Waters and “THE SCIENCE OF WHAT’S POSSIBLE.” are registered trademarks of Waters Corporation. All other trademarks are the sole property of their respective owners.
Copyright 2014 Waters Corporation
Page 1 of 51
*716004166* *Rev.A*
Waters Empower 3 Service Release 2
Waters® Empower® 3 Service Release 2 (SR2) corrects various software defects.
These release notes contain the following important information for installing and using Empower 3 Service Release 2 software.
Unless superseded, all previous release notes and product support information apply to this software release.
Table of Contents Table of Contents ....................................................................................................................... 1
GxP compliance requirements When you install Empower software for the first time, or when you uninstall it, you must qualify the software so that it meets GxP compliance requirements.
Recommendation: Whenever you install or uninstall software in a GxP environment, follow your organization’s management-approved, standard operating procedures for changing software.
System and software requirements Empower 3 SR2 software supports Windows® 7 Professional or Enterprise, Windows XP Professional, and Windows Server 2008 R2, with Service Pack 1. Specifically, it supports these platforms and operating systems:
Platform Operating systems
Personal workstation Windows 7 Professional or Enterprise with Service Pack 1, 64-bit
Client or LAC/E32 ™ module • Windows 7 Professional or Enterprise with Service Pack 1, 64-
bit, or
• Windows XP Professional with Service Pack 3, 32-bit
Database server
• Windows Server 2008 R2, Enterprise edition with Service Pack 1, 64-bit (Oracle RDBMS 11.2.0.2.0 with Patchset 15)
• Windows Server 2008 R2, Standard edition with Service Pack 1, 64-bit (Oracle RDBMS 11.2.0.2.0 with Patchset 15)
• Oracle Solaris 10 (8/11), patched to 9/11 (Oracle RDBMS 11.2.0.2.3)
• Red Hat Enterprise Linux 6.2 (Oracle RDBMS 11.2.0.3.6)
RAC server
• Oracle Enterprise Edition for Windows, 64-bit, version 11.2.0.2, Patch Set 11
• Oracle Enterprise Edition for Solaris and Red Hat, version 11.2.0.3.6
Citrix® Server XenApp™ 6.5 Windows 2008 R2, Standard and Enterprise, 64-bit
Data Guard server Windows 2008 R2, Enterprise, 64-bit
Before you install Empower 3 SR2 software Back up all Empower projects, library information, and databases before installing this software.
716004166, Rev A
Page 5 of 51
Install Empower 3 Service Release 2 You can install Empower 3 Service Release 2 by downloading it from the Waters Website or from the installation media.
Restriction: You cannot roll back or remove an Empower 3 Service Release 2 installation.
Requirement: You must have local administrator privileges to install Empower 3 SR2. Note that the Domain Administrator account might not have local administrator account privileges.
After installing Empower 3 Service Release 2 After installing Empower 3 Service Release 2, when you log into Empower, the software automatically updates your projects. The time required for the update to SR2 corresponds to the number of projects.
You can install Empower 3 Service Release 2 in the following ways, depending on your system configuration:
Computer configuration Installation process
Single computer running a supported Windows operating system
• Installation wizard • Command line interface (silent installation)
Multiple computers: Clients, LAC/E32, or Citrix servers
Install Empower 3 SR2 on a single computer You can install Empower 3 SR2 on a single computer using the Installation Wizard or using the command line interface.
To install Empower 3 SR2 using the Installation Wizard:
1. In Windows Explorer, browse to the folder containing the Empower3SR2Setup.exe file that you downloaded from the Waters Website, and double-click it.
Alternative: Insert the installation media into the media drive. In Windows Explorer, browse to the media drive, and then double-click Empower3SR2Setup.exe.
2. Follow all the prompts to complete the installation.
Recommendation: If you have problems installing Empower 3 SR2 due to a Verify Files issue, contact your local Waters Support organization.
3. After the installation finishes, restart the computer.
4. Log into the computer.
5. Log into Empower.
6. If the computer is in a client/server environment, when prompted to update the database, enter the password EMPOWER3CSUPDATE, one word in all uppercase letters.
Result: Empower 3 Service Release 2 does not update the currently installed version of Oracle. It updates only the database tables that Empower software uses.
Important: In a client/server environment, wait several minutes before logging into Oracle Enterprise Manager.
716004166, Rev A
Page 6 of 51
To install Empower 3 SR2 on a single computer using the command line interface (silent install):
1. In a command prompt window, if required, change to the directory that contains the file Empower3SR2Setup.exe.
2. At the command prompt, type the following command along with the required command line options, and any other options you want to use, as listed in the following tables.
Example network file location: M58_103153\c\SR2logs
3. After the installation finishes, restart the computer.
4. Log into the computer.
5. Log into Empower.
6. If the computer is in a client/server environment, when prompted to update the database, enter the password EMPOWER3CSUPDATE (one word, all uppercase letters).
Result: Empower 3 Service Release 2 does not update the currently installed version of Oracle. It updates only the database tables that Empower software uses.
Important: In a client/server environment, wait several minutes before logging into Oracle Enterprise Manager.
Required command line options:
Option Description
/s Run the installation in silent mode.
/v Passes one or more command line options to notification services.msi. When including multiple command line options, enclose them in quotation marks. Rule: Do not include a space between the /v and the command line option.
/qn Installs the software without displaying the user interface.
Install Empower 3 SR2 on multiple computers using the PsExec utility When installing Empower 3 SR2 on multiple computers (push installation), use the PsExec utility and the Waters command line interface and options according to the account you use to install the software. You can enter the commands in a command window at the system prompt.
Rule:
• You must use a domain account to run Empower3SR2Setup.exe and specify the –u and –p options. Ensure that the domain account is added as a local administrator on each machine. Log in as the local domain administrator on each machine when performing the push installation.
• Use a batch file to execute the push install.
716004166, Rev A
Page 7 of 51
Requirement:
• Ensure that each drive and folder containing media to be pushed allows a domain user full control permissions.
• Create a batch file containing the SR2 upgrade push install options.
To install Empower 3 SR2 on multiple client computers using the PsExec utility:
1. From the following Website, download the currently available version of the PsExec utility onto the system from which you plan to install Empower 3 SR2 onto other computers, into any folder:
http://technet.microsoft.com
2. Create a text file, and within it, enter the name or IP address of each client computer on a separate line, and then save the file.
3. Create a batch file containing the SR2 upgrade push install options:
5. After the installation finishes, restart the computer.
6. Log into the computer as a local admin user.
7. Log into Empower.
8. If the computer is in a client/server environment, when prompted to update the database, enter the password EMPOWER3CSUPDATE, one word in all uppercase letters.
Result: Empower 3 Service Release 2 does not update the currently installed version of Oracle. It updates only the database tables that Empower software uses.
Important: In a client/server environment, wait several minutes before logging into Oracle Enterprise Manager.
PsExec command line options: Required
-d Do not wait for the process to finish (non-interactive)
Yes
-u Specifies username for login Yes
-p Specifies password for user name Yes
716004166, Rev A
Page 8 of 51
PsExec command line options: Required
-h If the target system is Vista or higher, has the process run with the account's elevated token, if available.
Yes
Waters command line interface options and variables:
Variable Substitute this value Required
PATH_A Path to the Empower 3 SR2 media Yes
File Name of the text file (filename.txt) Yes
PATH_B A network share Yes
PATH_C Path to the text file containing the client computer names
Yes
PATH_D Path to location of batch file Yes
<language> L1033 for English L1041 for Japanese L1042 for Korean L2052 for Chinese Example command line to install the Japanese version of Empower 3 SR2: Empower3SR2Setup.exe /s /L1041
No
WAT_LOG_FILE_NETWORK_LOCATION=<share_ name>
The name of a network share in which to create the installation log file. Resulting log file name for a successful installation: computername_datetime_empower3.log Resulting log file name for an unsuccessful installation: ERR_computername_datetime_empower3.log If the network share is inaccessible for any reason, the log file is created in the local Windows folder.
No
WAT_RESTART=<value> Enter Yes or No to specify whether to reboot the system.
No
716004166, Rev A
Page 9 of 51
Install Empower 3 SR2 on multiple Citrix servers When installing Empower 3 SR2 on multiple Citrix servers, use the PsExec utility and the Waters command line interface and options. You enter the commands in a command window at the system prompt.
Requirement: Confirm that the default admin$ share is enabled on all Citrix servers on which you plan to install Empower 3 SR2.
To install Empower 3 SR2 on multiple Citrix servers:
1. From the following Website, download the currently available version of the PsExec utility onto the Citrix server, into any folder:
http://technet.microsoft.com
Requirement: You must have administrator privileges on each Citrix server.
2. In any text editor, create a text file (filename.txt), and within it, enter the name or IP address of each Citrix server on a separate line, and then save the file.
3. To set the mode to install, in any text editor, create a batch file, for example, PushCitrix.bat, and within it, enter the following options:
• For “PATH_C”, specify a valid path to the text file containing the Citrix server names
• For “PATH_D”, specify a valid path to the location of the batch file
5. After the installation finishes, restart the host computer.
6. Log onto each Citrix server.
7. Log into Empower.
8. When prompted to update the database, enter the password EMPOWER3CSUPDATE (one word, all uppercase letters).
Result: Empower 3 Service Release 2 does not update the currently installed version of Oracle. It updates only the database tables that Empower software uses.
Important: After installing Empower 3 Service Release 2, when you log into Empower, the software automatically updates your projects. The time required for the update to SR2 corresponds to the number of projects.
Important: In a client/server environment, wait several minutes before logging into Oracle Enterprise Manager.
716004166, Rev A
Page 10 of 51
Verify the Empower 3 Service Release 2 installation You can verify that Empower 3 SR2 was installed by running a utility called Verify Files. Running Verify Files creates a checksum.txt file that maintains a record of all Empower options and service packs installed on an Empower computer. The checksum.txt file also verifies the integrity of disk files by comparing their current CRCs and sizes with original values recorded during installation of the base software and any installed option or service pack.
To verify your Empower installation:
Click Start > All Programs > Empower > Verify Files.
To view the checksum.txt file:
From Windows Explorer, click Empower > Script > Checksum.txt.
To confirm that Empower 3 SR2 is installed on the computer:
Click Start > All Programs > Empower > Installation Log to view the installation log, and search for lines similar to these:
[13:14:36]: Empower 3 Service Release 2 Installer Setup was initialized.
[13:16:48]: The Empower 3 Service Release 2 Installer has successfully completed installing Service Release 2 on this computer.
[13:16:48]: Empower 3 Service Release 2 Installer has completed.
=== Logging Stopped: 5-18-2014 13:16:48 ===
Enhancements added to this release The following table lists the enhancements added in Empower 3 Service Release 2. The PCS (Product Change System) numbers identify software issues that Waters personnel monitor within a system change request tracking tool.
Enhancements added in Empower 3 SR2:
PCS Number Description
45534
Empower can now calculate and report 'statistical moments' in Review and Report Publisher when the System Suitability option is enabled.
51184
There is a new result field, Maximum Impurities Threshold, that contains a copy of the Maximum Allowed Value, Maximum Impurity from the impurity tab of the processing method. There is also a new result field, Total Impurities Threshold that contains a copy of the Maximum Allowed Value, Total Impurities from the impurity tab of the processing method.
51185
A new processing method component field, Impurity RRF, is now used to adjust peak area values when calculating % Adjusted Area, Total Adjusted Area, % Area against Main Component, and %w/w if wValue is Area. Impurity RRF is also used to adjust the peak height values when calculating % w/w if wValue is Height.
716004166, Rev A
Page 11 of 51
Enhancements added in Empower 3 SR2:
PCS Number Description
51545, 52516 Email service is now available on Empower Personal.
52644 The Open Access interface has been renamed Walk-Up. All references to Open Access in the user interface and online help have been changed to Walk-Up.
Issues fixed in this release The following tables contain lists of the software problems fixed in Empower 3 Service Release 2. The PCS (Product Change System) numbers identify software issues that Waters personnel monitor within a system change request tracking tool.
• General issues fixed in Empower 2 SR2
• Impurity processing
• Agilent GC instrument control
• Empower Toolkit
• Review and Processing
• Data Analysis and Processing
• Run samples
• Configuration manager
• Preview and Reporting
• Mass Spec capabilities
• Audit Trail and Result Audit Viewer
• Compare
• Method Validation Manager (MVM)
• Quickstart
• Empower online information system
• Installation
716004166, Rev A
Page 12 of 51
Issues fixed in Empower 3 SR2
Issues fixed in Empower 3 SR2:
PCS Number Description
44296, 49503, and 51805
The InstrumentServer Directory is currently shared to Everyone. Follow these instructions to change InstrumentServer share permission on both XP and Windows 7 operating systems: 1. Start Windows Explorer, right-click Empower\InstrumentServer, and then
select Properties. 2. On the InstrumentServer Properties dialog, select the Sharing tab.
Note: • On XP systems, if "Do not share this folder" is selected, click "Share this
folder". Then click the Permissions button. • On Windows 7 systems, click the Advanced Sharing button. Then, on the
Advanced Sharing dialog, click the Permissions button. 3. On the Permissions for InstrumentServer dialog, select the line for
"Everyone" and click the Remove button. 4. Click Add. 5. In the Select Users, Computers, Service Accounts, or Groups dialog, enter
"Domain Users" in the entry box. 6. Click the Check Names button. Confirm that the Domain Users name is
underlined. 7. Click OK. 8. Click OK on each remaining dialog to finish.
48957, 50054, 51533
Application startup and login time has been improved, as well as performance when using Verify Files in a WAN environment.
51511, 51512 The translations of the Analytics Number of Admin in System Summary and "Active" have been corrected.
51737 Manually changing the IP address in DHCP Configuration no longer causes the operating system to halt.
51761 Importing of NetCDF files is no longer limited to 18 files at one time.
51762 The IP address set via Waters DHCP Server Configuration wizard is now saved after the computer is rebooted.
51820 Removing and then reinstating the Tree View Method Set Editor Window no longer causes the method set information to disappear.
51821 Instrument method editor no longer displays PDA information for non-PDA instruments.
51915 The error, "Current method contains errors. Please fix before continuing.", no longer appears when you switch from Channel view to Instrument view in the Instrument method editor.
716004166, Rev A
Page 13 of 51
Issues fixed in Empower 3 SR2:
PCS Number Description
52221 Empower 3 FR2 Backup Project no longer produces errors.
52315, 52345 Background processing no longer exits unexpectedly when processing a sample set containing one or more blank channels when "European Pharmacopoeia" is selected in the Processing Method Editor's System Suitability Tab.
52577 Using spectrum review in QS Review to export to NIST no longer produces the error "C:\Empower\Nist\FILSPEC.FIL" contains an incorrect path.".
52614 Empower 3 Reserved Custom Fields are now stored in database correctly, no longer causing data loss when migrating data from earlier versions of Empower.
52773 Japanese dissolution calculations would not calculate due to an error. This has been fixed.
Issues fixed in Impurity Processing
Issues fixed in Impurity processing:
PCS Number Description
52670 Custom field processing during quantitation or calibration has been fixed so that the peak custom fields calculated using values from summary result custom fields are calculated correctly.
Issues fixed in Agilent GC Instrument Control
Issues fixed in Agilent GC Instrument Control:
PCS Number Description
49149 For 6890 - Empower 3 will now acquire two (2) GC channels from a single-tower injection when both channels are enabled in the instrument method.
51784 PC COM ports 3 and 4 on the Serial Ports tab of Empower Node Properties are now activated for serial instruments including the 6890 GC.
716004166, Rev A
Page 14 of 51
Issues fixed in Empower Toolkit
Issues fixed in Empower Toolkit:
PCS Number Description
48871 Toolkit no longer relies on a registry key to login to the database.
49082 A new Toolkit function similar to the Project.MessageCenter function will also specify what Category (General, Security, Processing, etc.) and the Severity of message (Inform, Warning, or Error) is being written to the Message Center.
49102 Toolkit will no longer allow individual or all messages in the message center to be purged without a password if the message center password protection is enabled.
50990 Corrected text in Toolkit Error Code 459.
51008 Users without a full name will now be able to view a report using Toolkit.
51233 The Empower 3 Toolkit has been updated with the functionality to resume or abort a paused Sample Set.
51363 The maximum login attempts of a Toolkit user is now tied to that user’s account.
52188 Toolkit Result Sign Off now properly releases allocated memory.
52314 Toolkit Viewers now properly release allocated memory.
52330 Accessing the Toolkit DBProjects Names property now properly releases allocated memory.
52332 The Toolkit Instrument.Connect function now properly releases allocated memory.
52333 The Toolkit Instrument.InstConfigs property now properly releases allocated memory.
52334 The Toolkit SampleSetMethod.Fetch() function now properly releases allocated memory.
52391 Accessing the Toolkit SampleSetMethod.FetchByTemplate function now properly releases allocated memory.
52609 Toolkit Project Copy now maintains System Policy Settings during the copy.
52611 Toolkit LoginX function now works with usertype in VB.Net.
716004166, Rev A
Page 15 of 51
Issues fixed in Review and Processing
Issues fixed in Review and Processing:
PCS Number Description
45438 Interactive System Suitability will now stop a Sample Set after the re-inject limit has been reached when limits are exceeded on a Summary Custom Field.
49608 Rounding differences for peak retention time values shown in the peak table and on the peak label in the chromatogram have been reconciled.
50465 The comment entered when creating a Processing Method using the Processing Method Wizard now appears in the audit trails.
51736 The new Empower FR2 “Purity” peak field is renamed to "Purity (Component)" and the “Purity” sample component field is renamed to “Purity (Vial).”
51802 Changes made in Processing Method Editor are now saved when exiting the Processing Method Editor.
51859, 51999
Background processing no longer exits unexpectedly when reprocessing a result set or result with “use existing integration” when the results were created by processing extracted PDA or MS 3D channels or derived 2D channels.
52023 Clear calibration command will now be applied to all systems in sample sets where multiple instrument systems were used.
52154 Values in “RRT” custom fields in projects created prior to Empower 3 Feature Release 2 are now maintained when the project is restored into Empower 3 Service Release 2.
52525 PDA 3D blank subtract from Agilent DAD channels can now be performed.
52700 Calibration IDs now update correctly when manual results are added.
Issues fixed in Data Analysis and Processing
Issues fixed in Analysis and Processing:
PCS Number Description
51287 In rare cases, when performing CODA, 3D blank subtract and baseline correction on 3D MS continuum data, small artifacts in displaying the spectra would occur. This has been corrected. Peak spectra from new results created by processing newly created CODA channels no longer display artifacts in Empower 3 SR2.
51466 QuickStart would exit unexpectedly if you viewed a method set that had more than one channel using the same processing method, and then switched to the processing method view and then to Browse Project. This has been fixed. Quickstart no longer exits unexpectedly if you switch directly from the View Method/Processing view to the Browse Project view.
716004166, Rev A
Page 16 of 51
Issues fixed in Run Samples
Issues fixed in Run samples:
PCS Number Description
44345 It is now possible to make a 2nd injection with a system containing a ZQ and 2998 detector.
45845, 50938 Save Preferences are now maintained when a minimized Run Samples Window is closed.
47442, 48896, 49039, and 52187
Utilizing Auto-addition delay is now possible with Ethernet control of the eAlliance.
48493 A user can now create an enumerated text custom field which also allows free-form text to be entered.
48945 Users can now save an instrument method if the needle wash mode is changed. The Save button and File > Save menu items are now enabled.
49130, 49317 Loading sample set methods with a large number of reporting lines was taking a long time to load the method into Run Samples. The loading time for the method has improved.
50811 The Data Start and Next Injection delay fields are now grayed out when non-inject functions are used.
51193 The Monitor and Setup buttons are no longer grayed out on Run Samples after running a Shutdown method.
52514 Walk-Up interface now allows a user to define plates, no longer preventing the use of the 1:A,1 nomenclature, which is necessary for vial positions in ACQUITY UPLC-based systems.
52650 Run Samples preferences are now saved in Empower-J, in the Pro interface.
53039 When using a 1525 connected via IEEE through a busLace, using the stop flow or change flow buttons would cause the instrument server to exit unexpectedly. This has been fixed.
716004166, Rev A
Page 17 of 51
Issues fixed in Configuration Manager
Issues fixed in Configuration Manager:
PCS Number Description
49153 Activating and deactivating multiple projects in the Global Project View window no longer causes the application to exit unexpectedly.
51214 UV and MS libraries can now be exported in the JCAMP format. In addition, channels, injections, sample sets, results sets, and results can be exported to JCAMP format.
51686 The full name of the user for LDAP authentication can now be taken from the ‘displayname’ field rather than the ‘cn’ field. The ‘cn’ field can have multiple values, including nicknames.
51695, 52370 The New > User > Local User menu option would disappear after configuring LDAP and logging out. This has been fixed. The Local User option now appears in the menu.
52880 In an LDAP configuration, users would not appear in the list of available LDAP users if the user was created with a UPN value that did not contain '@domain.com'. (For example, the name was entered as “user” only, and not entered as “[email protected]”.) This has been fixed. All LDAP users now appear in the “Select users from LDAP tree” list.
Issues fixed in Preview and Reporting
Issues fixed in Preview and Reporting:
PCS Number Description
42681, 51434, 52208
A landscape report no longer becomes portrait during export and signoff.
47651, 51418 Numbers are no longer truncated in tables in reports.
47885 When a result is generated through background processing, a new Method Set ID (Result) field will contain the ID of the method set used to process the result.
48451 For summary reports that contain duplicate sample results, the "Include Duplicate Results" option for the first table no longer affects the display of duplicates in subsequent tables.
51215 Unknown peaks named based on Relative Retention Time can now be grouped and reported in System Suitability reporting Summary Plots.
51594 When using LDAP user accounts and signing off reports, the username is no longer case sensitive.
52286 For environments installed on a German Windows operating system, Empower 3 no longer reports the “Printer not activated” error.
Issues fixed in Mass Spec Capabilities
Issues fixed in Mass Spec Capabilities for QDa support:
PCS Number Description
29505 A new novel MS library matching algorithm has been implemented for improved performance with both centroid and continuum data.
50320 The times where leading and tailing spectra are extracted are now displayed in the chromatogram in the Mass Analysis window.
52548 MS spectra are correctly extracted when the MS data collection time range differs from the data collected in the PDA channel.
Issues fixed in Audit Trail and Result Audit Viewer
Issues fixed in Audit Trail and Result Audit Viewer:
PCS Number Description
48840 Configuration Manager now warns users that if they have more than 10,000 audit trail entries and are exporting the audit trail in text mode, multiple export files will be required.
49165 Acquisition-related Audit Trail records will be stored in the correct project after users switch between projects to set up multiple acquisitions on the same system, while using the “Wait For User” feature.
50987 The Audit Trail message for the Toolkit error code 468 has been fixed, and now displays the correct message: “The user “User A” is logged on from more than one location.”
51716 In Result Audit Viewer, selecting "Match All" in Find now obeys the "Highlighted data" font selection the way “find each one individually” does.
51717 Pressing F1 was not launching Help in Result Audit Viewer. This has been fixed. F1 now displays help for the main Result Audit Viewer dialog, the main Results table, and the tabs in the table.
51829 Sample History details visible in Alter Sample are now visible in the Results Audit Viewer.
716004166, Rev A
Page 19 of 51
Issues fixed in Compare
Issues fixed in Compare:
PCS Number Description
50864 Table and plot properties are now saved by Save Preferences in the Compare window.
Issues fixed in Method Validation Manager (MVM)
Issues fixed in Method Validation Manager (MVM):
PCS Number Description
46648 Intercept t-Ratio calculation no longer returns a negative value.
51153 In the MVM Manager the user can now change the system precision criteria in a Read Only Study.
51462, 52274 During Specificity testing, the main component is no longer incorrectly faulted for Relative Resolution and Absolute Value of Relative Resolution in the Relative Peaks Table if the values are blank if the new “Ignore empty field” checkbox is checked. An “Ignore empty field” checkbox has been added to absolute and relative criteria settings.
52275 Ignoring missing peaks is now possible when processing MVM specificity results. Processing error code MV87 was added to the validation result. To avoid seeing this error, check the box, "Do Not Fault if Missing", when you add the criterion for a component type.
Issues fixed in QuickStart
Issues fixed in QuickStart:
PCS Number Description
49276, 51424 Users now require proper privileges to save a method set in QuickStart.
51538 When switching from one project to another project, the sample set method editor now opens and closes properly.
51540 In the browse project view in QuickStart, the tabs for Peaks, View Filters, Custom Calculations and Audit Trails are now visible.
716004166, Rev A
Page 20 of 51
Issues fixed in Empower Online Information System
Issues fixed in Empower Online Information System:
PCS Number Description
51459 F1 key now opens the correct help topic in Project Properties > Browse for Parent > Select Project.
51513, 51514 Empower 3 System Administration Help translation missing content has been fixed.
51739 Added information to Data Acquisition help that the ability to modify dissolution parameters is disabled for data from the current Dissolution Default project or data created by a sample set method template.
52077 Fixed the Reporting link in Empower Basics help. (Empower Basics > Getting Started with Empower > What’s new in this release of Empower. Then click Reporting link on the first page.)
52413 Added information to Data Acquisition help about default amounts and how to enter values. Updated the text in the “Default Amounts tab” topic and a table in the “Creating Processing methods” topic.
52469 Searching for the phrase "Getting Started Guide" in English Help brought up generic templates. This issue has been fixed for English help in Empower 3 SR2.
Issues fixed for installation
Issues fixed for installation:
PCS Number Description
51602 Empower DCOM Exceptions are no longer restricted to the subnet.
716004166, Rev A
Page 21 of 51
Known software issues in this release
General issues or behaviors CODA processing and MS 3D baseline subtraction can take a significant amount of time, enough so that it may seem as though the system is hung. Wait a sufficient amount of time for the process to finish.
Known issues with assigned PCS numbers The following tables describe known software issues and workarounds for Empower 3 Service Release 2. The PCS (Product Change System) numbers identify software issues that Waters personnel monitor within a system change request tracking tool.
• Data analysis and processing
• Review and processing
• Compare
• Method Validation Manager (MVM)
• Run Samples
• System configuration and project management
• Installation, administration, and instrument control software
• Reporting
• Empower software application components
• Empower Toolkit
Known issues in Data Analysis and Processing
Known issues in data analysis and processing:
PCS Number Description
52883 If MS 3D Channels are brought into Review and processed to create a CODA and/or MS 3D baseline subtracted MS 3D channel, Apply Method set fails if this processed MS 3D channel is the selected channel in the 3D channel table in Review. Apply Method set works correctly when a Sample set or injection is brought into Review.
716004166, Rev A
Page 22 of 51
Known issues in data analysis and processing:
PCS Number Description
52893 When a channel with a non-constant data rate is integrated using the Traditional integration algorithm, the Zeroth Moment does not equal the Area. If this same channel is integrated using the ApexTrack integration algorithm, the Zeroth Moment equals the Area. The reason for this difference is that the Traditional Peak Area is calculated using the average time interval between all the data points, while the Peak Moments and the ApexTrack Peak Area are calculated using the actual time interval between points.
Known issues in Review and Processing
Known issues in review and processing:
PCS Number Description
53111 In Review, when modifying a processing method in the Processing Method editor, if a “Save Processing Method” message appears and Review opens a “Save As” dialog to force the saving of the processing method under a new name, you might see multiple characters when you enter the new name or a comment. Workaround: To avoid seeing multiple characters added to the new name, after performing any operation that would change a processing method that is currently being edited, perform a manual "Save As" operation before the automatic display of the "Save As" dialog.
53181 Results that have already been processed using a processing method without 3D MS Processing cannot be reprocessed using a processing method with 3D MS Processing enabled. Workaround: Process the injection or channel using the processing method with 3D MS Processing enabled.
53183 When both PDA and MS 3D channels are brought into Review, the "next 3D channel" button works intermittently. Workaround: Click the channel of interest in the 3D channel tab.
53219 The method set is not automatically applied for a PDA 3D channel. Workaround: To ensure the method set is applied to the channel of interest, click “Apply method set” after opening the method set.
716004166, Rev A
Page 23 of 51
Known issues in review and processing:
PCS Number Description
53223 After changing the precision in the mass label in the chromatogram properties to a value greater than 3, the expected mass and Base Peak masses in the table in Review may display only the figures after the decimal place. Workaround: Change the column width in the column properties.
Known issues in Compare
Known issues in Compare:
PCS Number Description
53363 When deleting a selection in a table using the File > Delete menu in the Compare Window, other data may no longer be visible. Workaround: Use the Delete key on the keyboard when deleting from the Compare Window.
53365 When in the Compare window, faulted values in the Peak Table are not formatted as faulted values, as set in the properties.
53381 When viewing data in the Compare window, unexpected behavior can result if the data being viewed is from different projects. The window title and status field in the lower right hand corner may not update to display information for the selected data item. Only custom fields common to all the projects will display in the Peak table and other tables.
Known issues in Method Validation Manager (MVM)
Known issues in Method Validation Manager:
PCS Number Description
53230 In Method Validation Manager, it is sometimes necessary to expand the Column width to see both the criteria and the relative criteria in the data tab.
716004166, Rev A
Page 24 of 51
Known issues in Run Samples
Known issues in Run Samples:
PCS Number Description
48075
When running in a virtual environment and there is high memory usage, injection time stamps may be inaccurate. Workaround: Reconfigure the virtual server to disable "synchronize guest time with host", and execute a manual command to force time synchronization with domain controllers.
51061 For systems that include a 2414 detector, when you initiate a sample set that contains a Purge Detector function, and then close the Run Samples window, the sample set pauses after the Purge Detector function completes. The sample set run resumes when you reopen Run Samples.
52680 It has been found that there are instances where the positioning of windows (such as Instrument Method, Time Remaining, etc.) within the Run Samples dialog are not maintained when the dialog is closed and then reopened. Upon reopening, the windows are moved back to their default position along the left edge of the Run Samples dialog. This is independent of Empower “Save Preferences”, as these window position preferences are maintained by the operating system. It is already known that positional preferences are not maintained when a window is minimized and then closed from the minimized state, but this issue has been seen when normally sized windows are closed. This issue does not occur on all machines. It has been observed on machines running the Windows Basic theme. If you see this issue, change the Windows theme to something other than Basic.
Known issues in system configuration and project management
Known issues in system configuration and project management:
PCS Number Description
51443, 52555 When you use the View As > Audit Records function, Empower displays the selected data in the Audit Trails tab. You can return to the original data tab by clicking View As Previous. However, after you return to the original data tab, you cannot return to the Audit Trails tab by clicking View As Next. If you click View As Next, Empower logs an OCI_INVALID_HANDLE message in the Message Center, and displays the message: "No rows found. You may want to change the conditions specified in the current view filter." Workaround: Click OK to close the error message. Click View As Previous to return to original data tab, select the desired data, and then click View As > Audit Records.
716004166, Rev A
Page 25 of 51
Known issues in system configuration and project management:
PCS Number Description
52978 When connected to a Solaris database server and attempting to restore a project, Configuration Manager can exit unexpectedly. Workaround: When configuring a Solaris database server, configure the settings as follows: Oracle processes: 1500 Sessions: 1700 Open cursors: 3000
Known issues for installation, upgrade, administration, and instrument control software
Known issues for installation, upgrade, administration, and instrument control software:
PCS Number Description
48053
When creating an instrument method for a system containing a 2695, the sparge reservoir fields are unavailable until the method is saved and reopened.
52210
After installing Empower 3 FR2, the Windows Application and Services logs sometimes display messages indicating that attempts to update registry entries were denied. These messages are an artifact of the installation utility, and should be disregarded.
716004166, Rev A
Page 26 of 51
Known issues for installation, upgrade, administration, and instrument control software:
PCS Number Description
52457
When push installing Empower 3 Feature Release 2 and Empower 3 Service Release 2 from a Windows 7 Operating System to a Windows XP system, you must use a batch file, utilizing a domain user account. (The domain user is a local administrator on the host machine and all destination machines.) To push install from a Windows 7 system to a Windows XP system: 1. Create a batch file, such as Push.bat, with the following values:
2. Enter the following command: PSExec @<PATH_A>\File –u <DOMAIN\USERNAME> -p <DOMAIN PASSWORD> -h –d CMD /c <PATH_TO_BATCH>install.bat
Where:
• PATH_A is the path to the text file which contains the clients • File is the name of the text file (such as STARTPC.txt). Ensure the text
file contains the client machine name, or the client IP address.
52552
The busLace card will not boot after 2998 is upgraded with Driver Pack 4. The problem is caused when upgrading the 2998 to Driver Pack 4 using the installed ZQ driver. Workaround: After upgrading the 2998 with a new driver, uninstall the ZQ driver and then reinstall the ZQ driver.
52583
Empower 3 SR2 Personal cannot be uninstalled using the Empower 3 FR2 kit after you restart the computer. You can only initiate the uninstallation process after you turn off the WatersEmailService. Workaround: Before you uninstall Empower 3 SR2, run the batch file "Remove_Email_Service.bat", from the .\Empower (root) folder, using administrative privileges.
52613 Before installing or removing any instrument driver (or drivers), execute the "Stop_Email_Service.bat" batch file from the Empower root directory, with Administrator privilege. If you do not run this batch file to stop the Email Service, the Instrument Driver Deployment Manager will prevent driver installation or removal because it will detect a running Empower process.
716004166, Rev A
Page 27 of 51
Known issues for installation, upgrade, administration, and instrument control software:
PCS Number Description
52671
In the Empower 3 Installation, Configuration, and Upgrade Guide, the version of the PsExec utility is incorrect. The information on pages 190, 195, and 213 of the installation guide instructs users to download and install version 1.98 of PsExec. This version is no longer available. Users should download the latest version of PsExec, from the URL in the installation instructions on pages 7 and 9 of this release notes document.
52709 Before removing Empower 3 FR2, execute the "Remove_TestExecute.bat" batch file from the Empower root directory, with Administrator privilege. If you do not run this batch file to remove TestExecute, then uninstalling Empower 3 FR2 will not remove the TestExecute program, and you will need to use the Add/Remove Programs utility to remove TestExecute.
53452 After installing Personal versions of Empower-Japanese, Empower-Chinese, or Empower-Korean, the installation log will report that “NewFeature1” has been installed rather than reporting that “Waters Email Service” has been installed. The installation is successful and the Waters Email Service functionality is not affected.
Known issues in Reporting
Known issues in Reporting:
PCS Number Description
52927 When you print an instrument method for an ACQUITY UPLC system that includes a BSM controlled by the ACQUITY driver installed from ACQUITY Driver Pack 4 (DP4), Empower displays the message "Unable to load instrument setup information for the ACQ-BSM.". Workaround: View the instrument method parameters in the instrument method editor or by selecting Method properties > Method differences.
53218 When reporting the Peak Ratio Table, although you can select Include Criteria in Reports from the report group properties, the criteria will not be included in the report. Workaround: To report criteria, use the generic Table report group.
716004166, Rev A
Page 28 of 51
Known issues in Empower software application components
Known issues in Empower application components:
PCS Number Description
52338 When you run Empower using Windows Remote Desktop or VMWare and you choose "Fit to Window" or "100%" scaling in QuickStart Preview, the X and Y axis may no longer be visible; however, the report prints correctly. This issue is not observed when running Empower natively.
Known issues in Empower Toolkit
Known issues in Empower Toolkit:
PCS Number Description
52533
In the ToolKit, Empower custom fields created with the same name are overwritten, even if the difference in the name is a space (for example Column Name and ColumnName). To avoid the ToolKit overwriting the name and only updating one of the fields, do not create custom fields with the same name as one that already exists in Empower that has a space between the parts of the name.
716004166, Rev A
Page 29 of 51
Known issues in Empower Toolkit:
PCS Number Description
52625
Toolkit query fails when conditions contain SQL keywords. When a search condition contains any words on the list of Oracle SQL reserved words, an Oracle error can occur. An example would be when a system name contains one of the Oracle SQL reserved keywords. Do not use Oracle SQL reserved keywords in a Toolkit query. The following is the list of current Oracle SQL reserved keywords: ACCESS, ADD, ALL, ALTER, AND, ANY, AS, ASC, AUDIT, BETWEEN, BY, CHAR, CHECK, CLUSTER, COLUMN, COMMENT, COMPRESS, CONNECT, CREATE, CURRENT, DATE, DECIMAL, DEFAULT, DELETE, DESC, DISTINCT, DROP, ELSE, EXCLUSIVE, EXISTS, FILE, FLOAT, FOR, FROM, GRANT, GROUP, HAVING, IDENTIFIED, IMMEDIATE, IN, INCREMENT, INDEX, INITIAL, INSERT, INTEGER, INTERSECT, INTO, IS, LEVEL, LIKE, LOCK, LONG, MAXEXTENTS, MINUS, MLSLABEL, MODE, MODIFY, NOAUDIT, NOCOMPRESS, NOT, NOWAIT, NULL, NUMBER, OF, OFFLINE, ON, ONLINE, OPTION, OR, ORDER, PCTFREE, PRIOR, PRIVILEGES, PUBLIC, RAW, RENAME, RESOURCE, REVOKE, ROW, ROWID, ROWNUM, ROWS, SELECT, SESSION, SET, SHARE, SIZE, SMALLINT, START, SUCCESSFUL, SYNONYM, SYSDATE, TABLE, THEN, TO, TRIGGER, UID, UNION, UNIQUE, UPDATE, USER, VALIDATE, VALUES, VARCHAR, VARCHAR2, VIEW, WHENEVER, WHERE, WITH You can create a project using one of the reserved words (unless it contains an illegal character), because Empower does not use the project name as an Oracle reference. Instead, Empower uses the schema name. For example, you can create a project named “access” because Oracle uses the Empower schema name rather than the project name. Refer to the Oracle® Database Programmer's Guide to the Oracle Precompilers for more information about 11g reserved words.
Program files modified in this release The following program files in the Empower\Bin directory contain updates to one or more source code files for this release:
File name Description
AutoArchive.exe The AutoArchive application
Cmgr.exe The Configuration Manager application
Compare.exe The Compare application
Empower.exe The main Empower application
ImmdSrvr.exe Contains immediate background processing reporting and exporting support
impexp.dll The Import/Export Library
InEditor.exe The Instrument Editor application
InstrumentServer.exe The Instrument Service application
Mil0.dll Contains base objects which implement database connection, security, user and user type objects, etc.
Mil1.dll Contains base objects which implement higher level objects such as methods, results, etc.
Mil2.dll Contains base objects which implement higher level objects including data processing, integration, calibration, etc.
Mil3.dll Contains objects which implement higher level objects such as reporting groups and display graphics
milp.dll Contains base objects which implement higher level objects including data processing, integration, calibration, etc.
MilTK.dll Contains basic Toolkit objects
msgcenter.exe The Message Center application
Open Access.exe The Open Access application
OQ.exe The Operations Qualification application
pmeditor.exe The Processing Method Editor application
ProcSrvr.exe The Processing Server application
project.exe The Project application
Quickset.exe The Run Samples application
716004166, Rev A
Page 31 of 51
File name Description
QuickStart.exe The QuickStart application
Report Publisher.exe The Report Publisher application
Review.exe The Review application
SetEmailDatabase.exe The Set E-Mail database application
ValidationManager.exe The Validation Manager application
ValidationReview.exe The Validation Review application
WatersEmailService.exe The Waters E-mail service
WatersService.exe The Waters Service
VerifyOpt.exe The Verify Options application
AnalyticsObjects.dll Contains objects for the Empower Analytics application
Unless noted below, there is no deviation in supported operating systems when Empower 3 is installed in a virtualized environment. Therefore, the following platforms and operating systems are supported by Empower 3 for native and virtual installations.
• Empower database server - Windows Server 2008 R2 Enterprise SP1, 64-bit
• Empower File server - Windows Server 2008 R2 Enterprise SP1, 64-bit
• Empower Clients - Windows 7 Professional or Enterprise, 64-bit; Windows XP Professional SP3, 32-bit
• Citrix® server (includes the Citrix server, license server, farm controller, and webserver) – Windows Server 2008 R2, Standard and Enterprise, 64-bit; XenApp™ Server 6.5
Exception: Acquisition Clients and/or LAC/E32 modules are not supported for use in a virtual environment.
VMware vCenter Server 5.0 for the vSphere 4.1 and 5.0 environments Windows Server 2008 R2 SP1, with hotfixes: