SQL Server Instance Failure or Not starting SQL Server

Error:- Can not Connect to instance(name) or instance failure or Windows could not start the SQL Server(MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 10048

Solution:

In this case, have looked into Event Viewer then you can see the four error message related to sql server instance then look into the first error occurred i.e highlighted one. then the reason, we found ipv6 and TCP Port related issues. For this kind of error we should look into the SQL Network configuration.

Go to windows and find the sql server configuration manager and follow the below steps and check if there is any tcp port mention like '1433' then delete it and leave it blank or assign some different port except 1433 then click on apply and ok.

Note- if you have more then one instance and you assign same port for all, like 1433 then whichever instance started first that only occupied that port and remaining instance would not start.

Once you rectify the above error. Go to windows and find the sql server configuration manager and click on SQL Server Services and Right panel you can see your SQL server instance and Right click on it then click on start. Now we can see SQL server started.

Successfully connected to SQL server instance with SSMS tool.

Conclusion:

Not starting SQL server is one of the major issues for DBA. there are several reason to occurs that but That's also one of the reason to occurs. that is also one of the way to fix that issues.