MSS DataServer broker fails to start via OEM or mssman with error 8304 when AdminServer is started with -requireusername

MSS DataServer broker (mssbroker1) fails to start through OpenEdge Management (OEM) or the mssman command-line utility with authentication errors "User not authenticated (8304)" and "Failed to verify user's password". The issue occurs when the AdminServer is started with the -requireusername parameter in the Windows registry. Starting the broker directly via _probrkr succeeds.

Oct 7, 2026
Knowledge

Title

URL Name

MSS-DataServer-broker-fails-to-start-via-OEM-or-mssman-with-error-8304-when-AdminServer-is-started-with-requireusername

Article Number

000306462

Environment

Product: OpenEdge Version:12.8.x OS: All supported platforms

Question/Problem Description

When attempting to start an MSS DataServer broker (e.g., mssbroker1) via OpenEdge Management (OEM) or using the mssman command-line utility, the broker fails immediately.

Symptom details:
- OpenEdge AdminServer and NameServer (NS1) start successfully.
- The MSS broker fails very early in the startup sequence.
- Neither broker log (.broker.log) nor server log (.server.log) files are generated.
- The broker never registers with the NameServer.
- Command line startup via mssman fails with: "User not authenticated (8304)".
- admserv.log reports: "Failed to verify user's password".
- Starting the broker directly using the standalone executable _probrkr works without issues.

Steps to Reproduce

1. Perform an interactive OpenEdge installation on Windows and check the "Require a Username and Password" option under the AdminServer Authorization Options dialog. 2. Confirm that -requireusername is present in the AdminServer StartupCmd registry key: HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\<version>\StartupCmd 3. Start the AdminServer service and NameServer. 4. Attempt to start the MSS DataServer broker (mssbroker1) through OpenEdge Management (OEM) or from a Proenv command prompt using: mssman -name mssbroker1 -start 5. Observe that the broker fails to start and error 8304 is returned.

Clarifying Information

- Successful startup using _probrkr confirms that _msssrv.exe, DataServer licensing, environment variables, and underlying SQL Server database connectivity are fully operational.
- The failure is isolated to the AdminServer / Unified Broker management and STAT plugin authentication path.
- The -requireusername switch is written to the AdminServer StartupCmd registry entry during installation when the administrator chooses to require authentication for AdminServer connections.

Error Message

From command-line (mssman): User not authenticated (8304) From admserv.log: Failed to verify user's password

Defect Number

OCTA-102275

Enhancement Number

Cause

This issue is caused by a defect in the AdminServer STAT plugin. When AdminServer is started with authentication-enforcing flags (-requireusername or -admingroup), the AdminServer broker startup mechanism fails to properly authenticate and validate credentials passed through OpenEdge Management (OEM) and Unified Broker management utilities (mssman, asbman), causing the broker startup request to be rejected with authentication failure 8304.

Resolution

Until the fix is available, use the workaround below.

Workaround

Use one of the following two workarounds to operate the DataServer broker:

Workaround 1: Start the broker directly using _probrkr (Recommended for immediate testing)
Bypass the AdminServer / Unified Broker layer and launch the broker directly from a Proenv command prompt:
_probrkr -S <port/service> -N TCP -H <hostname>

Workaround 2: Remove -requireusername from the AdminServer registry
If starting the broker via OpenEdge Management (OEM) or mssman is required:
1. Stop the OpenEdge AdminServer and OpenEdge Management services.
2. Open the Windows Registry Editor (regedit).
3. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\12.8\StartupCmd
(Adjust the version node if running on another version).
4. Edit the StartupCmd string value and remove the "-requireusername" flag.
5. Restart the OpenEdge AdminServer and OpenEdge Management.
6. Start mssbroker1 through OEM or mssman.

Notes

Keyword Phrase

mssbroker1, mssman, _probrkr, 8304, User not authenticated, Failed to verify user's password, -requireusername, -admingroup, AdminServer, OEM, OpenEdge Management, DataServer, MS SQL, ubroker.properties, OCTA-26541, OCTA-101420

Last Modified Date

10/16/2026 5:08 AM

MSS DataServer broker fails to start via OEM or mssman with error 8304 when AdminServer is started with -requireusername

Files(0)

Was this article helpful?

Was this article helpful?

MSS DataServer broker fails to start via OEM or mssman with error 8304 when AdminServer is started with -requireusername

Information

Related Articles