One of the most famous errors related to SQL Server is about connecting to SQL Server itself. Here is how it goes, most of the time developers have worked with SQL Server and knows pretty much every error which they face during development language. However, hardly they install fresh SQL Server. As the installation of the SQL Server is a rare occasion unless you are DBA who is responsible for such an instance – the error faced during installations are pretty rare as well.
I have earlier written an article about this which describes how to resolve the errors which are related to SQL Server connection. Even though the step by step directions are pretty simple there are many first time IT Professional who are not able to figure out how to resolve this error. I have quickly built a video which is covering most of the solutions related to resolving the connection error.
In the Fix SQL Server Connection Error article following workarounds are described:
- SQL Server Services
- TCP/IP Settings
- Firewall Settings
- Enable Remote Connection
- Browser Services
- Firewall exception of sqlbrowser.exe
- Recreating Alias
Related Tips in SQL in Sixty Seconds:
- SQL SERVER – FIX : ERROR : (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: )
- SQL SERVER – Could not connect to TCP error code 10061: No connection could be made because the target machine actively refused it
- SQL SERVER – Connecting to Server Using Windows Authentication by SQLCMD
- SQL SERVER – Fix : Error: 15372 Failed to generate a ser instance od SQL Server due to a failure in starting the process for the user instance. The connection will be closed
- SQL SERVER – Dedicated Access Control for SQL Server Express Edition – An error occurred while obtaining the dedicated administrator connection (DAC) port.
- SQL SERVER – Fix : Error: 4064 – Cannot open user default database. Login failed. Login failed for user
What would you like to see in the next SQL in Sixty Seconds video?
Reference: Pinal Dave (http://blog.sqlauthority.com)