This article covers common issues encountered during automated data import from Waters Empower CDS into Katalyst, along with recommended solutions.
Issue 1: Injections Run in Empower Do Not Appear in Katalyst
Description:
A chromatographic run finishes in Waters Empower, but the resulting chromatograms or spectra do not appear in the designated Katalyst experiment well.
-
To diagnose this, check the instrument file share (
\\<Server>\<Share>\Instruments\):Scenario A: No file was created in either the
\Scanor\Failedfolder (Empower import/export issue).Scenario B: A
.spectrusfile exists in the\Instruments\Failedfolder (Katalyst ingestion (uploading) issue).
Scenario A: The injection was never scanned or exported from Empower
No .spectrus file generated on disk.
The automated scanner only extracts injections that match the expected Katalyst naming pattern (KAT*) and reside within configured project paths according to the Empower Instrument configuration in the Instruments Record Set in Spectrus DB.
Solutions:
Check Sample Name Syntax: The Sample Name in Empower must follow the exact Katalyst pattern:
KAT<ExperimentID>-<Plate>-<Well>-<A1>*(e.g.,KAT1263-1-A1-A1). Any missing hyphen, typo, or extra space causes the scanner to ignore the sample.Verify Project Scope: Ensure the injection was acquired inside an Empower project folder that is explicitly selected in the Katalyst Instrument configuration.
Check Duplicate / Re-run Status: If re-running an existing sample name, Katalyst skips it because its ID is already registered in the database. Contact your administrator to clear the cached injection ID.
Check ScanEmpower logs in Common logs
\Logs\<YYYY-MM-DD>\ScanEmpower*.logon the Automation Server installed along with Empower client.
Scenario B: The file was exported, but uploading into Katalyst failed
A .spectrus file is present in \Instruments\Failed.
The Empower Add-on successfully exported the analytical dataset to .spectrus format, but Katalyst's upload task (UploadWellLC) rejected the file when attempting to attach it to the experiment well.
Solutions:
Check Experiment Status: Confirm that the target experiment in Katalyst is in an active, editable state (not finalized, locked, or archived) and that the well coordinate exists and is not empty (the wells must contain at least one material).
Inspect Chemical Structures & Formulas: Verify that all compounds and materials assigned to the well have valid chemical formulas in the experiment layout. An invalid Molecular formula or illegal character (e.g. dot or whitespace in MF) will cause the backend data parser to abort data uploading.
Re-upload via the
\ScanFolder: Once the experiment issue in Katalyst is corrected (or if the failure was caused by a transient network timeout or some other issues that have been already resolved), move the.spectrusfile from\Failedback into\Scanto immediately re-trigger data upload and processing.Check Upload logs in Common logs
\Logs\<YYYY-MM-DD>\UploadWell*.logon the Automation Server
Issue 2: Re-run or Updated Injections Are Not reflected in Katalyst
Description:
A sample was re-injected or re-integrated in Empower, but Katalyst continues to display the old data (or skips the new injection entirely).
Solutions:
Understand Duplicate Protection: Katalyst records imported injection IDs in its database to prevent repeated data uploading. The scanner automatically ignores injections it has previously processed.
Request an Injection ID Reset (Support-Assisted): Contact your Katalyst administrator; Signals Support can assist them through a support ticket to clear the cached injection ID(s) so the next scan re-imports the updated injections.
Issue 3: Empower Projects Missing in Instrument Setup
Description:
When configuring an Empower instrument in Katalyst, clicking Refresh Empower Projects yields an empty list or fails to display specific project folders.
Solutions:
Check Service Account Project Access: In Empower Configuration Manager, verify that the Katalyst service account belongs to a User Group with explicit access to the missing projects.
Verify User Type Privileges: Ensure the service account's User Type includes Browse Project, Open Project, and Export Data privileges.
Enable Sub-Project Inheritance: If using nested folders, ensure project access rights are inherited down the folder tree.
Issue 4: Connection or Authentication Failure to Empower
Description:
The automated import task (ScanEmpower) or instrument configuration refresh fails to establish a session with Waters Empower. The scan aborts before any projects can be browsed or samples evaluated..
Depending on the underlying cause, the Millennium Toolkit COM API reports one of two primary error codes:
Case A (Database Configuration):
0x80040208— Invalid Database identifier or misconfigured connection string.Case B (Authentication & Lockout):
0x80040207— Invalid password or account locked out due to failed attempts.
Case A: Database Configuration Error (0x80040208: Invalid Database)
Check ScanEmpower or GetEmpowerProjects logs in Common logs
\Logs\<YYYY-MM-DD>\*.logon the Automation Server installed along with Empower client.Key Log Indicators:
[f] Katalyst.Launch.exe : ScanEmpower : Exception Message: A user-supplied component or subscriber raised an exception (0x80040208) source: Interop.MillenniumToolkit target site: Void Login(System.String, System.String, System.String, System.String) at MillenniumToolkit.ITkProject8.Login(String Database, String ProjectName, String UserName, String Password) at Katalyst.Core.Empower.EmpowerBrowser..ctor(...) class name: ITkProject8 method name: Login while: Invalid Database
Solutions:
Verify Database Identifier: In the Instrument settings, ensure the database name exactly matches the Oracle TNS/Service alias.
Match the Empower Client Login Dropdown: If the AS machine connects to multiple Empower databases, open the Waters Empower Client GUI directly on that machine and inspect the Database dropdown at login. Enter the exact alias shown there (case-sensitive) into the Katalyst instrument record.
Check for Trailing Whitespace: Ensure the Database value does not contain trailing spaces, tabs, or newline characters (
\r,\n) inadvertently introduced when copy-pasting.
Case B: Invalid Password / Account Lockout (0x80040207: Invalid password)
The service account password configured in Katalyst is incorrect, has expired, or the account has been locked out after multiple consecutive failed automated login attempts (triggered by automated scan tasks running every 10–15 minutes).
Check ScanEmpower or GetEmpowerProjects logs in Common logs
\Logs\<YYYY-MM-DD>\*.logon the Automation Server installed along with Empower client.Key Log Indicators:
[f] Katalyst.Launch.exe : ScanEmpower : Exception Message: The owner SID on a per-user subscription doesn't exist (0x80040207) source: Interop.MillenniumToolkit target site: Void Login(System.String, System.String, System.String, System.String) at MillenniumToolkit.ITkProject8.Login(String Database, String ProjectName, String UserName, String Password) at Katalyst.Core.Empower.EmpowerBrowser..ctor(EmpowerSettings settings, String projectName, ScriptContext phantomContext) class name: ITkProject8 method name: Login while: Invalid password.
Solutions:
-
Test Login via Empower Client GUI:
Log onto the Automation Server and open the Waters Empower Client GUI. Attempt to log in using the exact service account username and password configured for Katalyst:-
If login fails with an invalid password error this might indicate:
The password was changed or entered incorrectly in the Katalyst Instrument record. Update the credentials in the
Instrumentsrecord set.The account is locked: Automated scanning with an out-of-date password exceeded the maximum allowed failed attempts.
-
-
Unlock Account via Empower IT Support:
If the account is locked, contact your internal Empower System Administrator / IT Support to:Check the account status in Waters Empower Configuration Manager (
User Management).Unlock the service account.
Reset/confirm the password (ensure password expiration policy exemptions are applied if appropriate for service accounts).
Update Katalyst Credentials Promptly:
Immediately update the password in the Katalyst Instrument record before the next scheduled scan runs, preventing the service account from locking again.
If the issue persists, contact your internal support team and provide a detailed description of the problem along with any relevant screenshots. In addition, please collect and share the log files described in the corresponding article with Revvity Support for further investigation.
Comments
0 comments
Article is closed for comments.