Login Failed – Error: 18456, Severity: 14, State: 38

Reason: Failed to Open the Explicitly Specified Database

Fix Error “Failed to Open the Explicitly Specified Database”

The error log is saying “Failed to Open the Explicitly Specified Database“, it means either your have specified wrong database in your connection string or your login does not have access to the specified database. You can validate below options to isolate this issue.

• Check whether you have specified correct database in your connection string or not
• If you are using correct database then whether the login you are using to establish database connection has access to this specified database or not.
• Correct if you find something in any of the above two options.
• Check login properties whether it is using correct database as default database configuration or not. If correct database is defined then login has access to that database or not. I will explain about this step in below section as well.
• You should also check whether number of connections to the database is exhausted or not. Review your maximum number of connections setting.
• Ensure your database is not set to AUTO CLOSE setting or not inaccessible. Database should be online and healthy state to accept connections.
• Make sure you have a trust between both machines, database server and the machine from where you are trying to connect. I would suggest you to read below article as well where i have explained various steps to troubleshoot SQL Server connection issues.

Read more articles on SQL error 18456 and connection issues:

• How to Fix SQL Server Error 18456: A Comprehensive Guide
• How to fix SQL Server error 53 – Not able to open database connection
• Fix SQL Server error 18456 – Login failed for user

Let’s learn how to check default database settings for a SQL Server login and a user mapping for any database to the login.

Check Login Properties

The solution to fix this issue can also come by reviewing the properties of this login. Launch its properties window and change the default database to the correct one if this setting is showing wrong database. Sometimes, we drop the databases from the SQL Server instances but never update other objects. If this login is not showing any database and it is showing blank then click at its drop-down to choose your desired database as the default database for this login. Click on Ok button to apply that change. You will stop getting this issue after making this change.

You can open login properties windows by right click at the identified login and then choose properties from dropdown options.

Sometimes, you have chosen the default database as “master” but your login doesn’t have connect permission on master database so ensure you have at least connect permission on the database which you are choosing as the default database for your login. You can click at “User Mapping” tab from left side pane of the login properties window. You will get all databases in top side of right side pane and level of access in bottom side pane. Click at your database from right side pane along with its level of permission which you want to assign. Click at Ok button to apply this change.

Have a look at below screenshot to understand default database of a login and from where you can access User Mapping tab to provide appropriate access to your database. Your login should have access to both databases, the one mentioned as default database for your login and the specified database in connection strings.

You can fix SQL error “Failed to Open the Explicitly Specified Database” by following above steps. Write your feedback if you have fixed this issue by other way. I will update this article accordingly with credits.

The post Fix SQL Error 18456: failed to open the explicitly specified database appeared first on Techyaz.com.

A transport-level error has occured when receiving results from the server. (provider: TCP Provider, error: 0 – The semaphore timeout period has expired.) (Microsoft SQL Server, Error:121)

This was an intermittent issue and when we were executing the script from other server it was not throwing any issue. I did some research on this and found out that this error came because of unstable network connectivity.

SQL Server Error 121 The Semaphore Timeout Period Has Expired – Root Cause

There are various parameters that can affect network connectivity like network adaptors, packet drop, configured packet size etc. So i would suggest first you should connect to your network team and ask them to look into this issue. If network team has not found anything then you need to check application level network configurations at your level.

You should ask some questions to your network resource like whether any network packet drop being observed or not, or is there any NIC card issue etc. Let’s assume you have already reached out to network team and they haven’t found anything. I would suggest you to look into below options at your level to make sure everything is in place and not misconfigured.

• Check TCP\IP settings
• Ensure you have appropriate network packet size configured in SQL Server
• Make sure you have properly configured TCP Chimney Offload
• Validate you don’t have Network Interface Card (NIC) driver issue, you can get it checked with your network team

Solution

I have already described high level areas where you need to look in in above section. Let’s discuss them further here.

Check TCP\IP settings

You should open SQL Server configuration manager and check whether TCP configuration is properly done or not. Make sure to review all settings in SQL Server Network configuration settings. You should also read below article about this settings which causes a network error.

• Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol

Review Network Packet Size

You should also review network packet size configuration in SQL Server. This could be one of the possible reason for this issue. Ideally we should not change the default value of this setting and keep it as it is until you have a specific requirement to change network packet size. Read below article to understand and learn network packet size in SQL Server and also step by step process about how to change the network packet size to your desired value.

• How to Change Network Packet Size Configuration in SQL Server

TCP Chimney Offload

This settings is very important if we have network related connectivity issue. TCP Chimney Offload is a networking technology that helps transfer the workload from the CPU to a network adapter during network data transfer. It can be enabled or disabled in the following two locations:

• The operating system
• The advanced properties page of the network adapter

TCP Chimney Offload will work only if it is enabled in both locations. By default, TCP Chimney Offload is disabled in both these locations. However, OEM installations may enable TCP Chimney Offload in the operating system, in the network adapter, or in both the operating system and the network adapter.

Validate Network related Driver Issues

You should speak to your network resource and Windows OS platform resource and validate all drivers at OS layer and network layer should be up to date and they should not have any issue. Make sure to update the drivers if you found any issue any of these layer.

I hope you can fix your issue by following above steps mentioned in this article. Comment us how you have fixed this issue, the semaphore timeout period has expired.) (Microsoft SQL Server, Error:121)

Related Articles

• SQL Server Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server.
• Fix Error 1418: The server network address cannot be reached or does not exist.
• Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol
• SQL Server Native Client Error 50000: A network error occurred while attempting to read from the file

The post Fix SQL Server Error 121 – The Semaphore Timeout Period Has Expired appeared first on Techyaz.com.

• Mixed Mode ( Windows +SQL Server login )
• Windows Mode (Only Windows)

Mixed mode provides two ways to establish database connections. One is using SQL Server logins at SQL Server layer and another one is using Windows domain user authenticated using active directory and whose login is created and mapped on SQL Server instance.

Windows Mode has only one way to establish database connections and that is using windows domain accounts. We must map windows accounts on SQL Server first before making any database connections. This mode doesn’t provide access to SQL Server logins.

Read More to Grow:

• SQL Server Interview Questions & Answers on Indexes
• How to Prepare for a Job Interview?
• SQL Server Alwayson Interview Questions & Answers
• SQL Server Replication Interview Questions & Answers

Why Windows Authentication Mode is More Secure in SQL Server?

Windows mode is secure than Mixed mode authentication because mixed mode has SQL Server authentication which cannot use Kerberos security protocol. Windows account needs to be authenticated to domain active directory every time you establish a database connection. Also, Windows provides additional password policies that are not available for SQL Server logins and that is why Microsoft always recommends to use Windows authentication mode wherever it’s possible.

One more risk with Mixed mode is the encrypted SQL Server Authentication login password must be passed over the network at the time of the connection. Some applications that connect automatically will store the password at the client. These are additional attack points.

Change Authentication Mode in SQL Server

You can configure authentication mode in SQL Server during installing it to your system. SQL Server installation windows will allow you to choose any one of above given authentication modes. If you will choose mixed authentication mode then you need to provide sa password as per windows password policy. You can also change existing authentication mode setting to another one as per your business need.

Let’s assume you have installed SQL Server with Mixed authentication mode and now you have to change it to Windows Authentication mode. This section will explain step by step process to change SQL Server authentication mode.

We can set or change authentication mode in SQL Server either using SQL Server management studio or using T-SQL statements.

Using SQL Server Management Studio

1. Launch SQL Server Management Studio, connect to your target SQL Server instance.
2. In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.
3. On the Security page, under Server authentication, you can see both authentication modes. Select any as per your need and then click OK.
4. This change will require SQL Server service restart. A popup window will appear to ask you to restart the service when you will click at OK button in above step.
5. In Object Explorer, right-click your server, and then click Restart. If SQL Server Agent is running, it must also be restarted.

You have changed your authentication mode from Mixed mode to Windows using SQL Server Management Studio.

If you are changing authentication mode from Windows to Mixed mode then make sure to enable SQL Server login sa account. This account gets disabled during windows authentication mode to secure your SQL Server instance as sa is generic SQL Server login as it can be targeted by hackers to access your instance. Below are the steps to enable this account:

1. In Object Explorer, expand Security, expand Logins, right-click sa, and then click Properties.
2. On the General page, you might have to create and confirm a password for the sa login.
3. On the Status page, in the Login section, click Enabled, and then click OK.

Using T-SQL Statement

Microsoft has provided an extended stored procedure to chnage authenication mode in SQL Server using T-SQL statement. This extended stored procedure chnages windows registry entries so be careful while changing authentication mode in SQL Server using T-SQL statements. Make sure to take a backup of windows registry before executing this script.

USE [master]
GO
EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\MSSQLServer\MSSQLServer',
N'LoginMode', REG_DWORD, 1
GO

Above command has again changed authenticating mode from mixed to windows.

If you are doing other way around then make sure to enable sa login as i suggested above. You can also use below T-SQL statement to enable sa account.

ALTER LOGIN sa ENABLE ;
GO
ALTER LOGIN sa WITH PASSWORD = 'STRONG-PASSWORD' ;
GO

Here, i have explained how to change SQL Server authentication mode from Windows to Mixed mode or vice versa. Please comment us if you have any feedback on this article.

Related Articles:

• Fix SQL Server Error 18456: Login failed for user ‘User_Name’.
• How to Change SQL Server Instance Name?
• Create a Logon Trigger to Restrict sysadmin logins to connect to SQL Server for given Time Interval
• Fix Error 18452: Login failed. The login is from an untrusted domain

The post How to Change Authentication Mode in SQL Server? appeared first on Techyaz.com.

VIEW SERVER STATE Permission

This is high level server-level privilege which must not be granted to everybody. Only administrators must have privilege to use view server state permission but we can assign this permission to some users who want to see server level state of your SQL Server instance. Once you will grant this access to any login, he can see result of all DMVs.

Solution – ( Microsoft SQL Server, Error 300 )

We got SQL Server error 300 ( VIEW SERVER STATE permission was denied ) because the login you are using to execute the script doesn’t have this permission. To fix this issue we will grant view server state permission to the login name. This section will explain how to grant view server state permission to a login.

Grant VIEW SERVER STATE Permission

We can assign this permission either using GUI in SQL Server Management Studio or we can simply execute a T-SQL command to get this done. I will explain both ways to assign this permission.

Using GUI in SQL Server Management Studio

Follow below steps to do it using GUI.

1. Launch SQL Server Management Studio.
2. Connect to the SQL Server Instance.
3. Navigate to Security folder then expand Logins
4. Right Click at your login name and choose Properties
5. Click at Securables tab from left side pane.
6. In the bottom pane, scroll to the bottom and click at Grant option for View Server State value.
7. Now click on apply to close the window. You can now ask your user to test the script again. This time it will work.

Using T-SQL statement in SQL Server Management Studio

1. Launch SQL Server Management Studio. Connect to the SQL Server Instance.
2. Open New Query window
3. Run below T-SQL statement

USE master
GO
GRANT VIEW SERVER STATE TO "LoginName"

Once you execute above command, you will have view server state permission on your login name. You can resolve SQL Server error 300 VIEW SERVER STATE permission was denied on object ‘server’, database ‘master issue by following above steps given in this article.

Revoke VIEW SERVER STATE Permission

If you have identified anyone who must not have this permission then you can go ahead and revoke his access post getting proper approvals. Make sure that identified login does not have any business justification before revoking his access. Once you have decided to go ahead to remove view server state permission then you should run below T-SQL statement to get this done. Below steps will tell you how to revoke view server state permission of any login.

USE master

REVOKE VIEW SERVER STATE TO “LoginName”

GO

View SERVER STATE permission has been revoked for identified login post successful execution of above statement.

I hope you like this article. Please follow our facebook page and Twitter handle to get latest updates.

Read More:

• SQL Server AlwaysON Interview Questions & Answers
• SQL Server DBA Interview Questions & Answers
• Understanding Enhanced Database Failover in Always on Availability Group
• SQL Server Replication Interview Questions & Answers

The post Fix:VIEW SERVER STATE permission was denied on object ‘server’, database ‘master’ appeared first on Techyaz.com.

Msg 5184, Level 16, State 2, Line 1
Cannot use file ‘I:\Path\Techyaz.mdf’ for clustered server.
Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.

Msg 1802, Level 16, State 1, Line 1
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

While troubleshooting this error we came to know that the storage or LUN on which we have placed the database files are not added to cluster group. It means disk is not visible in failover cluster manager.

Solution – Error 5184

We performed below steps to fix this issue.

1. Added the storage on which databases files are placed as shared storage in the failover cluster manager.
2. Launch SQL Server properties window in Failover Cluster Manager.
3. Added all newly added disks in Dependencies tab.
4. Attached the database again.

Here i will explain above steps in detail with screenshots.

• We were attaching a database using T-SQL statement on one of the SQL Server cluster instance. While executing the command we get error 5184. Error details are given in below screenshot.

• As error suggests that “Either the disk resource containing the file is not present in the cluster group” so I checked cluster group for the disk and found that database files storage was not showing in failover cluster manager.
• Next step was to add these storage disks to the cluster group. Launch failover cluster manager. Click at Roles tab from left side pane. You can see SQL Server as role in right side pane. Right click at the SQL Server role and click at “Add Storage” option. You can see this in below screenshot.

• Once you will click at “Add Storage” option you will get below window to add the identified disks to cluster group. You can see I have selected all required disks in below screenshot. You can choose your disks where your database files are placed.

• Once you click at OK button post selecting all respective check boxes in above step, you will see all your storage disks in failover cluster manager under storage tab.
• Now again click at the SQL Server role and then go to “Resources” tab from down side pane where you can see SQL Server and all resources that are aligned for the SQL Server role. Here, right click at SQL Server and click at Properties tab as shown in below screenshot.

• Once you get SQL Server properties windows in failover cluster manager, next you should click at dependencies tab. Here, you need to insert one row for each disk system that you have added in above steps. Once you will insert dependencies for all newly added disks then it will look like below screenshot. Now click at OK button to apply this change.

• Now again go to SQL Server query window and run the T-SQL command to  attach the database. This time you will successfully attach the database to the clustered SQL Server instance.

Let me know if this article helped you to fix your issue. You can follow our facebook page and Twitter handle to get latest updates.

Read More:

• Upgrade or Patch SQL Server Failover Cluster Instance Running with Availability Group
• How to Change Failover Mode of Availability Replica in AOAG?
• How to Prepare for a Job Interview?
• SQL Server DBA Interview Questions & Answers

The post SQL Server Error 5184: Cannot use file ‘I:\Path\Techyaz.mdf’ for clustered server appeared first on Techyaz.com.

• If you have changed database server name then we should change SQL Server Instance name as well.
• If you have cloned a database server from DBSERVER1 to DBSERVER2. Here, SQL Server installed on DBSERVER1 will be copied with same name to DBSERVER2. You need to change the SQL Server instance name on DBSERVER2.
• Naming convention is not met.

Please keep in mind that we cannot change complete name of SQL Server named instance. Suppose you have installed a named instance SERVERNAME\DBInstance1 on your server. If you want to rename this named instance then we can only change first part of this name i.e. SERVERNAME. You cannot change DBInstance1 so your named instance will look like DBSERVERNAME\DBInstance1 post name change.

Impact of Changing SQL Server Instance Name

We need to plan carefully before renaming any SQL Server Instance. Below is the list of possible impacts that you should go through while renaming SQL Server Instance name.

• Those domain users who are accessing or connecting to the SQL Server Instance as part of Windows group will not be able to connect to renamed instance of SQL Server. Make sure to update the Windows group to specify the new computer name to establish connectivity to the SQL Server instance.
• You would not be able to access reporting services after renaming the instance name. You should follow steps mentioned in attached article to rename SQL Server instance that is running with reporting services.
• If you have database mirroring on the SQL Server instance then you need to drop the mirroring and then reconfigure it post renaming the SQL Server Instance.
• Renaming SQL Server instance name does not support if your instance has replication, except when you use log shipping with replication.
• You can change the name of SQL Server instance on secondary server in log shipping if the primary server is permanently lost.
• If you have linked server configurations then it will be affected by the computer renaming operation. Use sp_addlinkedserveror sp_setnetname to update computer name references.

Rename SQL Server Instance

SQL Server instance name along with other system metadata stores in sys.servers system object. We need to update details in system metadata to reflect new name. Also i would suggest to not change SQL Server Instance name directly on your production server.

Suppose you have installed default instance of SQL Server in your database server. If you have changed the name of your database server then you need to update the name of default SQL Server instance as well in sys.servers system table. First, we need to drop the existing SQL Server instance name then we will add new name as per our choice. Follow below steps to change SQL Server instance name.

--Drop existing name
sp_dropserver [old_Instance_name]; 
GO 

--Update New name
sp_addserver [new_Instance_name], local; 
GO

If you have installed a named instance on your database server then you can run below command to change SQL Server Instance name.

sp_dropserver [old_name\instancename]; 
GO 

sp_addserver [new_name\instancename], local; 
GO

Note: Make sure to restart SQL Server services post running above commands to reflect these changes.

You can verify the changes by running below commands or by querying sys.servers system table. If you have not restarted SQL Server services then you might be getting older SQL Server instance name. So restart SQL Server service to apply new changes.

SELECT @@SERVERNAME

If you have remote logins on your database server then you might get error 15190 while running sp_dropserver command. Read below article to fix this issue and then proceed with the instance name change.

• Fix Error 15190: There are still remote logins for the server

I hope you like this article. Please follow our Facebook and on Twitter handle to get latest updates.

Read More:

• Configure Reporting Services After Renaming SQL Server Instance Name
• How to Find When SQL Server was Installed on your database server?
• What should be best value for fill factor in SQL Server?
• Find all trace profilers running on SQL Server Instance
• How to Move a Table to Another Filegroup?

The post How to Change SQL Server Instance Name? appeared first on Techyaz.com.

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe) (Microsoft SQL Server, Error: 233)

You can see the screenshot of this error that I had received while making a database connection.

SQL Server Error 233 No process is on the other end of the pipe – Root Cause

Above SQL error 233 suggests the provider name as Shared Memory Provider. We know Shared Memory is a protocol used in SQL Server along with TCP/IP and Named pipe. We decided to check the settings and values for all protocols in SQL Server Configuration Manager.

I launched SQL Server Configuration manager and expanded SQL Server Network Protocols from left side pane. Here, you can see an option “Protocols for MSSQLSERVER”.  MSSQLSERVER is the name of SQL Server Instance as default instance has been installed there. If you have named instance installed on your machine then you might get “Protocols for <INSTANCENAME>.

Now click on this option “Protocols for MSSQLSERVER”, you can see all three protocols used in SQL Server in right side pane as shown in below image.

Here we can see Shared Memory protocol is set as Enabled but Named Pipes is set as Disabled that should be enabled to make successful database connection. This was the main reason for getting this error. Keep reading this article to fix this issue in next section.

I have also written another aspect of SQL Server Error 233 in below article. You might get this error if your SQL Server Instance has exceeded the total number of user connections set in server configurations. Have a look at this article as well.

• Fix SQL Server Error 233: User Connections Server Configuration option in SQL Server

Solution

We get error 233 ( SQL Server no process is on the other end of the pipe )because SQL Server client cannot connect to the server. This error could occur because the server is not configured to accept remote connections. To fix this issue, we will use the SQL Server Configuration Manager tool to allow SQL Server to accept remote connections. Here, in our case one of the protocol Named Pipe was disabled that’s why we were getting error. We will go ahead and fix this issue by enable the Named Pipe protocol. You might get this issue due to any protocol being disabled.

Make sure to enable Shared Memory, TCP/IP and Named Pipe protocols. Launch SQL Server Configuration Manager. Expand SQL Server Network Configuration from left side pane and click on Protocols for MSSQLSERVER. MSSQLSERVER is SQL Server Instance name. Now you will see all protocols in to right side pane. Right click on given protocols that is disabled and select Enable button to enable that protocols.

Named Pipe protocol was disabled in my case so I have launched Properties window of this protocol and selected Enabled option as Yes from dropdown as shown in below screenshot. Now click on Apply and Ok button to apply this change on SQL Server. It will ask you to restart the SQL Server service to apply these changes in to effect. Restart SQL Server services from SQL Server Configuration manager. Once services will come online, try to connect to your SQL Server instance, this time you will not face error 233 and you will be able to make successful database connection.

If you are still facing same issue ( no process is on the other end of the pipe )then you can also check “Allow Remote Connections” settings for this SQL Server instance. This setting must be enabled to connect to databases remotely. Connect to SQL Server Instance in SSMS locally on database server. Right click on SQL Server instance name in SSMS and choose Properties. You will get Server properties window. Click on Connections from left side pane and tick the check box on Allow remote connections to this server option from right side pane.

I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Read More Articles on SQL Server Connection Issues:

• Fix SQL Server Network Interfaces Error 28: Server doesn’t support requested protocol
• Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server
• Fix Error 53: Could not open a connection on SQL Server
• Fix Error 4064: Cannot open user default database
• Error 233: How to set the user connections server configuration option in SQL Server

The post Fix SQL Server Error 233: No process is on the other end of the pipe appeared first on Techyaz.com.

You can also get below error similar to error 53 under below details.

An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

Root Cause

Microsoft SQL Server Error 53 looks very much like the Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server at first look. Like SQL Server error 40, here also SQL Server client cannot connect to the SQL Server Instance. This error could occur because either the client cannot resolve the name of the server or the name of the server is incorrect.

You might get this issue due to other reasons as well although main reason is the wrong server name or port name. I have given all those possible reasons behind the Microsoft SQL Server error 53 in below points.

1. Wrong SQL Server Instance name while establishing database connection.
2. Entering wrong port no can be one of the reason for SQL Server error 53.
3. SQL Server Instance is not accessible due to firewall or any reason.
4. Telnet port 1433 or port no on which SQL Server is running. These ports might be blocked.
5. TCP/IP or Named Pipes protocol is disabled in SQL Server Configuration Manager.
6. Remote Connection is disabled for this SQL Server Instance.
7. SQL Server Browser service is stopped.

Solution

We need to check and validate multiple factors to rectify Microsoft SQL Server error 53. Check all factors given in below step by step points to fix all possibilities for this error.

1. Sometimes, we enter wrong server details by mistake. Make sure to enter correct SQL Server instance name while making database connection otherwise you will face sql error 53.
2. Try to connect using ip address and port number instead of putting server name in connection string.
3. Make sure SQL Server services are running fine and its accessible.
4. Check firewall details. Firewall should open between your client machine and database server. Port 1433 and 1434 should be enabled. Telnet both ports to make sure ports are open.
5. Make sure to enable TCP/IP and Named Pipes. Launch SQL Server Configuration Manager. Expand SQL Server Network Configuration from left side pane and click on Protocols for MSSQLSERVER. MSSQLSERVER is SQL Server Instance name. Now you will see all protocols in to right side pane. Right click on given protocols and select Enable button to enable both protocols.
6. Check TCP/IP name resolution, you can use the ping command in the Windows operating system. You can also right-click on TCP/IP and select Properties in SQL Server Configuration Manager. Verify that, under IP2, the IP Address is set to the computer’s IP address on the local subnet. Scroll down to IPAll. Make sure that TCP Dynamic Ports is blank. Make sure that TCP Port is set to 1433 or your identified port no.
7. Remote connection must be enabled to connect to databases remotely. Connect to SQL Server Instance in SSMS. Right click on SQL Server instance name in SSMS and choose Properties. You will get Server properties window. Click on Connections from left side pane and tick the check box on Allow remote connections to this server option from right side pane.
8. SQL browser service should not be stopped if your security policy allows it. If you have disabled this service to apply hardening then make sure to pass port no along with SQL Server instance name/IP while making database connection.

You can fix SQL error 53 by applying above solutions on your SQL Server instance. I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

Related Articles:

• Fix Error 28 – Server doesn’t support requested protocol
• Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server
• Error 4064: Cannot open user default database. Login failed.
• Fix Login Drop issue Error 15138 and Error 3729

The post Fix SQL Server Error 53: Could not open a connection on SQL Server appeared first on Techyaz.com.

The error details are given below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error:40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

Below is the screenshot of above Microsoft SQL Server error 40.

Sometimes, we get same error under below error text.

An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

Microsoft SQL Server Error 40 – Root Cause

We get SQL error 40 because SQL Server did not respond to the client request. This issue occurs due to multiple reasons. I have given all those possible reasons behind Microsoft SQL Server error 40 in below points.

1. Server is probably not started and shutdown.
2. SQL Server Service is down.
3. SQL Server Instance is not accessible due to firewall or any reason.
4. Telnet port 1433 or port no on which SQL Server is running. These ports might be blocked.
5. TCP/IP or Named Pipes protocol is disabled in SQL Server Configuration Manager.
6. Remote Connection is disabled for this SQL Server Instance.
7. SQL Server browser service is stopped.
8. Wrong SQL Server Instance name while establishing database connection

Solution

We need to check and validate multiple factors to rectify Microsoft SQL Server error 40. Check all factors given in below step by step points to fix all possibilities for this error.

1. Make sure that database server is up and running fine.
2. Make sure SQL Server services are running fine and its accessible.
3. Check firewall details. Firewall should open between your client machine and database server.
4. Port 1433 and 1434 should be enabled. Telnet both ports to make sure ports are open.
5. Make sure to enable TCP/IP and Named Pipes protocols. Launch SQL Server Configuration Manager. Expand SQL Server Network Configuration from left side pane and click on Protocols for MSSQLSERVER. MSSQLSERVER is SQL Server Instance name. Now you will see all protocols in to right side pane. Right click on given protocols and select Enable button to enable both protocols.
6. Remote connection must be enabled to connect to databases remotely. Connect to SQL Server Instance in SSMS. Right click on SQL Server instance name in SSMS and choose Properties. You will get Server properties window. Click on Connections from left side pane and tick the check box on Allow remote connections to this server option from right side pane.
7. SQL browser service should not be stopped if your security policy allows it. If you have disabled this service to apply hardening then make sure to pass port no along with SQL Server instance name while making database connection.
8. Sometimes, we enter wrong server details. Make sure to enter correct SQL Server instance name while making database connection.

Related Articles

• Fix Error 28 – Server doesn’t support requested protocol
• Fix Error 233: How to set user connections server configuration in SQL Server?
• Error 4064: Cannot open user default database. Login failed.

Here, I have given different solutions to fix sql error 40 in SQL Server. I hope you like this article. Please follow our Facebook and Twitter handle to get latest updates.

The post SQL Server Error 40: A network-related or instance-specific error occurred while establishing a connection to SQL Server. appeared first on Techyaz.com.

Cannot Connect to ‘SERVERNAME’.
Login failed for user ‘username’. (Microsoft SQL Server, Error: 18456)

SQL Server Error 18456 – Login failed 

Initially, I thought login failed SQL error 18456 was reported because user might have entered wrong password, but when I tried it with correct password, it displayed same error again. Read this article to fix this error.

When I received same MSSQL error 18456 even after entering correct login id and password then we have decided to check the server authentication mode configured for this instance. Here we got the answer because this SQL Server instance was configured to run in only Windows Authentication mode, that is why SQL Server database engine was not allowing us to login using SQL Server login that comes in to Mixed authentication mode.

As we know there are two types of authentication mode in SQL Server.

1. Windows Authentication Mode
2. SQL Server and Windows Authentication Mode (Mixed Authentication Mode)

Only windows login accounts can connect to SQL Server if your instance is configured in Windows Authentication mode but when Mixed Authentication mode is configured you can connect using windows and SQL Server logins both way.

Solution

So, to fix this SQL Server error 18456 ( Login failed error 18456 ), we have two options:

1. Either Change Server Authentication mode of this SQL Server Instance to Mixed mode (SQL Server and Windows Authentication Mode)
2. Or, always use windows login or Domain login account to connect to SQL Server Instance.

You can also read the below articles which is a comprehensive guide to fix this error 18456:

• How to Fix SQL Server Error 18456: A Comprehensive Guide
• Fix SQL Error 18456: failed to open the explicitly specified database

Now, let’s come back to this specific issue. Here, we have decided to change the Server Authentication mode from Windows Authentication to Mixed mode authentication. Below are the steps:

1. Right click on SQL Server Instance name in SSMS and choose properties.
2. Select Security from left side pane.
3. You can see Server Authentication mode is set to Windows Authentication mode in below screenshot.
   
4. Change this to SQL Server and Windows Authentication mode that is second option in above screenshot and click on OK button.
5. Restart SQL Server and SQL Server Agent services to apply the changes to database engine.
6. Now you would be able to login to your SQL Server Instance using SQL logins as well.

Here, i have shown you how to fix a SQL Server error 18456 by changing its authentication mode. Read more articles in related section given below.

Related Articles

• Fix Error 15170: Login owns one or more Agent Jobs
• Fix Login failed Error 4064: Cannot open user default database
• How to fix error 28 – Server doesn’t support requested protocol
• Fix Error 18452: Login Failed

I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

The post Fix SQL Server Error 18456: Login failed for user ‘User_Name’. appeared first on Techyaz.com.

Microsoft SQL Server Error 28

This is very common error that most of the people have gone through. Microsoft SQL Server Error 28 details are given below:

Sometime you might get same error as below description.

Root Cause

Generally, we get SQL Network Interfaces Error 28 while connecting to SQL Server instance either using SQL Server Management studio or using any other way. There might be several reasons behind generating Microsoft SQL Server Error 28. I have tried to capture all such reasons in below points..

• A specified SQL Server instance name is not valid. Wrong SQL Server Instance Name can lead to generate Microsoft SQL Server Error 28.
• Remote access is not enabled for your SQL Server instance.
• The firewall on the server has refused the connection because ports used by SQLBROWSER.EXE and SQLSERVR.EXE is still blocked.
• The SQL Server Browser service (sqlbrowser) is not started.

Solution

We need to check and validate multiple factors to fix Microsoft SQL Server error 28. Check all factors given in below step by step points to fix all possibilities for this SQL error 28.

• Validate whether server on which SQL Server is hosted is reachable from your client machine or not. Run ping and telnet to make sure server connectivity.
• Make sure SQL Server is running fine on your server. Check SQL Server services.
• Firewall ports 1433 for SQL Server and 1434 for SQL Server Browser services should be opened.
• Verify correct SQL Server Instance name. Check the spelling of the SQL Server instance name that is specified in the connection string.
• Make sure to enter full SQL Server Instance name in case you have named instance like SERVERNAME\SQL2017.
• Make sure that the SQL Server Browser service is started on the server.
• Enable Remote connection for your SQL Server Instance. Most of the people face Microsoft SQL Server error 28 because remote connection was disabled on the SQL Server Instance. Use the SQL Server Configuration Manager tool to enable SQL Server to accept remote connections over the TCP or named pipes protocols. Below steps you can follow to enable remote connections.

1. Launch SQL Server Configuration Manager. Expand SQL Server Network Configuration from left side pane and then click Protocols for InstanceName. If your server has default instance then it will look like “Protocols for MSSQLSERVER”
2. You can see all three protocols in right side pane. Shared Memory, Named Pipes and TCP/IP.
3. Make sure to enable Named Pipes and TCP/IP. Right-click at the protocol name and then click Enable. The icon for the protocol will change to show that the protocol is enabled.
4. You need to restart the SQL Server services to bring the changes into effect so restart your SQL Server services.

Related Articles

• Fix SQL Server Error 40: A Network related or Instance specific Error Occurred while establishing a connection to SQL Server
• How to Fix SQL Server Error 53: Could Not Open a Connection on SQL Server?
• Fix Error 4064: Cannot open user default database
• SAP Connectivity Issue After AlwaysON Automatic failover
• Fix Error 976: Cannot connect to Secondary Replica of AOAG

Here, i have shown you how to fix sql error 28. I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.

The post Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol appeared first on Techyaz.com.