Fixes a communication link error that occurs when you use datetime2 fields while accessing a database in SQL Server 2017.

When you try to connect SQL Server 2017 for Linux on a distribution that has OpenSSL 1.1 configured and OpenSSL 1.0 is not installed, you may receive a connection error message that resembles the following:

Find solutions for errors when you run the Xbox connection test.

To mitigate this issue, implement one of the following solutions listed in order of preference: Enable support for Extend Master Secret (EMS) extensions when performing TLS connections on both the client and the server operating system.

Check the Xbox services, games, and apps for any service outages.

In this situation, you can't start correctly or connect to a shared instance of SqlLocalDB. This problem is fixed in the following cumulative updates for SQL Server: Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

If you’re using an Ethernet connection and can’t connect to the internet, there are a few things you can try to try to fix the problem and get connected. If you are using a Windows 11 device, start by running the automated Network and Internet troubleshooter in the Get Help app.

Check your settings again to make sure the UPnP message is gone. If UPnP still isn’t working, or isn’t supported on your gateway/router, you can also try using the router’s DMZ, Port Forwarding, or Port Triggering features. For more help, see: Did this resolve the issue? Still need help?

Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.

When you send an email and receive a delivery failure message, there could be several reasons. We've listed the most common error messages below, along with suggested resolutions.