You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a POD (podman on Redhat) with 2 SQL express instances.
One runs on port 1434 and the other 1435.
Although DAC is disabled (see messages) it still tries to start it. The second instance will file because instance 1 has 1431 already in use.
Can I somehow prevent this?
Hard disable DAC in mssql.conf?
Steer the DAC port, so it doesn't try to listen on the same port on the second instance?
2024-12-09 19:49:17.32 spid40s Server is listening on [ 0.0.0.0 <ipv4> 1435] accept sockets 1.
2024-12-09 19:49:17.32 spid40s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2024-12-09 19:49:20.92 spid55s Attribute synchronization initialized
2024-12-09 19:49:20.92 spid55s Attribute synchronization manager initialized
2024-12-09 19:52:17.35 spid40s Error: 26024, Severity: 16, State: 1.
2024-12-09 19:52:17.35 spid40s Server failed to listen on ::1 <ipv6> 1431. Error: 0x2742. To proceed, notify your system administrator.
2024-12-09 19:52:17.35 spid40s Failed to create the named pipe server at \\.\pipe\XdbPkgLauncherPipe. ErrorCode: 0x00002742.
2024-12-09 19:52:17.36 spid40s InitializeXdbPkgLauncher failed. ErrorCode: 0x80072742.
The text was updated successfully, but these errors were encountered:
I have a POD (podman on Redhat) with 2 SQL express instances.
One runs on port 1434 and the other 1435.
Although DAC is disabled (see messages) it still tries to start it. The second instance will file because instance 1 has 1431 already in use.
Can I somehow prevent this?
The text was updated successfully, but these errors were encountered: