Hopefully these operating instructions help you if the service exits with service error 10048 0x2740.
If the MSSQL service does not start and gives the following error, do the following:
1. Make sure remote connections are enabled on the server.
2. Check your TCP / IP settings and make sure the TCP / IP port is not in use by other applications.
3. Run netstat on the command line to check if port 1433 is listening, or simply run Telnet command to check if port 1433 is listening or not.
Telnet localhost 1433
4. If port 1433 is in use, it is likely that another instance of SQL is running on the server.
5. If two instances of SQL are running on the same server, you must use different ports; Example: 1434.
5. Use a different port and restart the SQL server. Should work
SQL Server service (SQLinstance1) ended with service error 10048 (0x2740).
Reason
This issue can occur for one of the following reasons:
- Another process is using TCP port 5718 and TCP port 5719. These two ports are required by the DPM Protection Agent service.
- TCP port 5718 and TCP port 5719 are not open to firewall applications or firewall devices on the computerweb site.
Decision:
The Windows team has already released hotfixes to resolve this issue. Several customers have already confirmed that these fixes fixed issues with this regression. The following tables list the hotfix knowledge articles that describe regression and the hotfix knowledge articles.
For Windows 7 / Server 2008 R2
For Windows Server 2012
For Windows 8.1 / Server 2012 R2
You can install one of the appropriate regression knowledgebases to troubleshoot SQL Service / Availability Group listeners not starting / going online due to ‘TCP port is already in use’. For example, if you have KB4338815 installed on your system, you can install KB4338831 or KB4345424 to fix the regression. The difference between the two is that KB4345424 only provides a regression fix, whereas KB4338831 contains all fixes from KB4338815 plus additional quality improvements as a preview next month This is a cumulative update package (including a fix for regression). …
In addition to the monthly rollup / security updates mentioned above, this regression was also introduced in updates for some versions of Windows 10 / Server 2016. Please note that updates for specific versions do not contain a corresponding patch. Therefore, there is only one applicable hotfix per assembly to resolve the regression shown in the following table.
