Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 13402561
KB4532432 - Mssql-conf tool fails if IPV6 is disabled on the Linux system - Microsoft Support
Last update date:
6/2/2022
Affected products:
SQL Server in VM - Linux
SQL Server 2017 Developer Linux
SQL Server 2017 Enterprise Core Linux
SQL Server 2017 Enterprise Linux
SQL Server 2017 Standard Linux
Affected releases:
build lower than 15.0.4033.1
Fixed releases:
15.0.4033.1
Description:
Symptoms
Assume that you try to install Microsoft SQL Server 2019 on a Linux operating system such as Redhat or Ubuntu. If IPv6 is disabled at the OS kernel level, and you try to configure SQL Server by using the "sudo /opt/mssql/bin/mssql-conf setup" command, you receive the following messages in the Linux console and SQL Server error log. Additionally, the configuration may fail. Linux console: The licensing PID was successfully processed. The new edition is [Enterprise Evaluation Edition]. ForceFlush is enabled for this instance. ForceFlush feature is enabled for log durability. Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG in /var/opt/mssql/log for more information. SQL Server error log: DateTimeAndSpid Clearing tempdb database. DateTimeAndS pid [2]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1. DateTimeAndS pid Starting up database 'tempdb'. DateTimeAndS pid The tempdb database has 1 data file(s). DateTimeAndS pid The Service Broker endpoint is in disabled or stopped state. DateTimeAndS pid The Database Mirroring endpoint is in disabled or stopped state. DateTimeAndS pid Service Broker manager has started. DateTimeAndS pid Database 'msdb' running the upgrade step from version VersionNum to version VersionNum. DateTimeAndS pid Database 'msdb' running the upgrade step from version VersionNum to version VersionNum. DateTimeAndS pid Error: 26024, Severity: 16, State: 1. DateTimeAndS pid Server failed to listen on 'any' <ipv6> 1433. Error: 0x2742. To proceed, notify your system administrator. DateTimeAndS pid Error: 17182, Severity: 16, State: 1. DateTimeAndS pid TDSSNIClient initialization failed with error 0x2742, status code 0xa. Reason: Unable to initialize the TCP/IP listener. A socket operation encountered a dead network. DateTimeAndS pid Error: 17182, Severity: 16, State: 1. DateTimeAndS pid TDSSNIClient initialization failed with error 0x2742, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. A socket operation encountered a dead network. DateTimeAndS pid Error: 39002, Severity: 16, State: 1. DateTimeAndS pid SQL failed to boot extensibility for error code 0x80070005. DateTimeAndS pid Error: 17826, Severity: 18, State: 3. DateTimeAndS pid Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. DateTimeAndS pid Error: 17120, Severity: 16, State: 1. DateTimeAndS pid SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 4 for SQL Server 2019 Cumulative Update 20 for SQL Server 2017
Workaround
To work around the issue, run the following command: sudo MSSQL_IP_ADDRESS=0.0.0.0 /opt/mssql/bin/mssql-conf setup
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminologythat Microsoft uses to describe software updates.
