loi garena auth in main server

This article helps you resolve various connectivity issues vĩ đại SQL server.

Bạn đang được xem: Sửa lỗi auth in main server

Bạn đang xem: loi garena auth in main server

Note

For a guided walk through experience of this article, see Solving Connectivity errors vĩ đại SQL Server.

Original product version: sumuoi.mobi SQL ServerOriginal KB number: 4009936

Prerequisite

To effectively use this troubleshooter, you may want vĩ đại gather the following information.

The complete text of the error message along with the error codes and whether the error is intermittent (happens only sometimes) or consistent (happens all the time).

Errorlogs from SQL Server from which you can note the following:

Fully qualified domain name name (FQDN) of the SQL Server machine or in case of clustered installations, the FQDN virtual name. If you are using a named instance, note down the instance name.

Note

You can tìm kiếm for “Server name is” string vĩ đại get this info in the errorlog.

Network libraries and ports the SQL instance is listening on. Example messages:

Named pipes: Server local connection provider is ready vĩ đại accept connection on . TCP/IP and port number: Server is listening on .

Application and System sự kiện logs from SQL Server and Client systems.

If the connections are failing from an application, the connection string from the phầm mềm. These are typically found in Web.config files for ASP.NET applications.

Checklist

Ensure SQL server is started and you see the following message in the SQL Server ErrorLog:

SQL Server is now ready for client connections. This is an informational message; no user action is required.

Verify basic connectivity over IP address and kiểm tra for any abnormalities: ping -a , ping -a . If you notice any issues, work with your network administrator vĩ đại fix the same.

Check if SQL is listening on appropriate protocols by reviewing the ErrorLog.

Check if you are able vĩ đại connect vĩ đại SQL Server from other client systems and different user logins. If you are able vĩ đại, then the issue could be specific vĩ đại the client or login that is experiencing the issue. Check the Windows sự kiện logs on problematic client for additional pointers. Also kiểm tra if network drivers are up vĩ đại date.

If you are experiencing login failures, ensure the user has a login at the server level and appropriate permissions vĩ đại connect vĩ đại the database that the user is trying vĩ đại connect vĩ đại.

A network-related or instance-specific error occurred while establishing a connection vĩ đại SQL Server

For more information about the relevant error, see the following Verify connection errors section.

Verify connection errors

The A network-related or instance-specific error occurred while establishing a connection vĩ đại SQL Server error represents one or more of the following error messages:

A network-related or instance-specific error occurred while establishing a connection vĩ đại SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured vĩ đại allow remote connections.

provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance SpecifiedSQL Server Native Client Data Link Error

: Login timeout expired: A network-related or instance-specific error has occurred while establishing a connection vĩ đại SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured vĩ đại allow remote connections. For more information see SQL Server Books Online.: SQL Server Network Interfaces: Error Locating Server/Instance Specified .A network-related or instance-specific error occurred while establishing a connection vĩ đại SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured vĩ đại allow remote connections.

provider: TCP Provider, error: 0A connection attempt failed because the connected các buổi tiệc nhỏ did not properly respond after a period of time, or established connection failed because connected host has failed vĩ đại respond.sumuoi.mobi SQL Server, Error: 10060A network-related or instance-specific error occurred while establishing a connection vĩ đại SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured vĩ đại allow remote connections.

provider: Named Pipes Provider, error:40 – Could not open a connection vĩ đại SQL Serversumuoi.mobi SQL Server, Error:53The network path was not found TCP Provider: No connection could be made because the target machine actively refused it. Login timeout expired A network-related or instance-specific error has occurred while establishing a connection vĩ đại SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured vĩ đại allow remote connections. For more information see SQL Server Books Online.You can start troubleshooting from this section: Common causes of various connection issues.

Common causes of various connection issues

Go through each of the causes that is applicable vĩ đại your instance below and for each of the applicable causes, try the corresponding resolutions.

Cause 1: Incorrect server name being specified in the connection string or in the server name dialog box

To confirm:

Ensure the server name you are specifying the application matches what you have in the error log.

Cause 2: Incorrect alias on the client machine

Aliases are typically used in environments when you need vĩ đại connect vĩ đại SQL Server with an alternate name or when there are name resolution issues in the network. An incorrect alias on the client machine can cause the connections from your applications vĩ đại go vĩ đại the wrong server resulting in failure.

Things vĩ đại try:

Open SQL Server Client Network Utility by typing cliconfg.exe in your Run command.

Check if there are any aliases defined for the server you are trying vĩ đại connect vĩ đại.

If present, tự the following:

Click on Edit and rename the Server alias. (for example, if your server name is MySQL, rename it as MySQL_test) and retry the connection. If the connection works, it is an indication that you had an incorrect alias, probably from an old configuration that is no longer needed. If you continue vĩ đại experience the error, rename the alias back vĩ đại its original name and proceed vĩ đại the next step.

Check the Connection parameters for the alias and ensure they are correct. Some of the common scenarios that can cause problems with connectivity are:

Incorrect IP address for the Server name parameter. Ensure this IP address matches the entry in the SQL ErrorLog tệp tin.

Incorrect Server name in the Server name parameter. For example though your Server alias points the correct server name, if the Server name parameter has incorrect value, connections will fail.

If you are using a named pipes alias, ensure the pipe name has correct format.

For connecting vĩ đại mặc định instance named Mydefaultinstance, the pipe name should be \MydefaultinstancepipesqlqueryFor connecting vĩ đại a named instance MySQLNamed, the pipe name should be \MySQLpipeMSSQL$NamedsqlqueryCause 3(Default instance): Firewall(s) between the client and server blocking the port SQL Server instance is listening on

Default instance: A mặc định instance typically runs on port 1433. Some installations also use a non-standard port (other than vãn 1433) for running SQL instances. The firewall may be blocking either of them.

Things vĩ đại try:

Try appending th
e port number of SQL Server vĩ đại the server name using the format , portnumber and see if that works. For example, if your SQL instance name is MySQLDefaultinstance and it is running on port 2000, specify the server name as MySQLServer, 2000 and see if that works. If it does work it is an indication the firewall is blocking the port.

Cause 4(Named instance): SQL Browser is not started

Client applications connecting vĩ đại a named instance of SQL Server use the SQL Browser service on the system where SQL is running vĩ đại enumerate the port that SQL is listening on. If the browser service is not started, the connections would fail.

Things vĩ đại try:

On the system running your SQL Server instance, either use the SQL Server Configuration manager or the Services applet in Control panel and start the SQL Browser Service if it is not already started. For more information, see How to: Start and Stop the SQL Server Browser Service

Cause 5(Named instance): UDP Port 1434 used by SQL browser is blocked on the network

If your SQL instance is a named instance, it may have either been configured vĩ đại use dynamic ports or a static port. In either case, the underlying network libraries query SQL Browser service running on your SQL Server machine via UDP port 1434 vĩ đại enumerate the port number for the named instance. If a firewall between the client and the server blocks this UDP port, the client library cannot determine the port (a requirement for connection) and the connection fails.

To Confirm:

Xem thêm: phía dưới hoang đường

Method 1:

Note down the port your SQL instance is listening on from the SQL Server Errorlog.Try connecting vĩ đại the named instance using the port number appended vĩ đại the server name using the format , portnumber and see if that works. If it does work it is an indication the firewall is blocking the port UDP port 1434. For example, if your SQL instance name is MySQLNamedinstance and it is running on port 3000, specify the server name as MySQLNamedinstance, 3000 and see if that works. If it does work it could either mean that UDP port 1434 is blocked or the static port is blocked or both. To confirm if it is the UDP port or the static port using Portqry from Method 2 below.

Method 2:

Things vĩ đại try:

First determine if the SQL Server instance is listening on dynamic vs static port and use the procedure that is relevant vĩ đại your scenario. How vĩ đại tell if SQL is listening on Dynamic vs Static ports, move vĩ đại Tell if SQL is listening on Dynamic vs Static ports section.

If this does not resolve your issue, move vĩ đại Still having problems section.

Configuring firewalls

If you are using a custom firewall, work with your network administrator vĩ đại open up the necessary ports.

Below you can find some quick screenshots showing the required configuration of a Windows firewall for successful connections vĩ đại a mặc định instance and a named instance.

A mặc định instance of SQL Server listening on the mặc định port 1433 on Windows 2012 R2 server. In this scenario, you need vĩ đại ensure an exception is added vĩ đại TCP port 1433 in the Windows firewall.

Open Windows firewall on the system hosting SQL server mặc định instance and click New Rule under Inbound Rules.

Select the Port option and click Next.

In the next screen:

Select TCP as the protocol.

Select Specific local ports and specify the value as 1433 and click Next.

Xem thêm: Kiến Thức Chuyên Môn Tiếng Anh Là Gì, Chuyên Ngành Trong Tiếng Anh: Định Nghĩa, Ví Dụ

In the next screen, select Allow the connection and click Next.

In the next screen, select the option that best suits your environment and click Next.

In the next screen, give the name vĩ đại your rule and provide a clear mô tả tìm kiếm for future reference and click Finish.

Once done, you should see that rule is created and is enabled by mặc định.

Adding an exception for UDP port 1434 vĩ đại enable connections vĩ đại a named instance of SQL server:

Open Windows firewall on the system hosting SQL server mặc định instance and click New Rule under Inbound Rules.

Select the Port option and click Next.

In the next screen:

Select UDP as the protocol.

Select Specific local ports and specify the value as 1434 and click Next.

In the next screen, select Allow the connection and click Next.

In the next screen, select the option that best suits your environment and click Next.

In the next screen, give the name vĩ đại your rule and provide a clear mô tả tìm kiếm for future reference and click Finish.

Once done, you should see that rule is created and is enabled by mặc định.

If this does not resolve your issue, move vĩ đại Still having problems section.

Using PortqryUI tool with SQL Server

Download location: PortqryUI

Launch PortqryUI tool on your client machine. (the machine where you are having connection issues, for trang web apps, this could be the IIS server)Specify server name of the SQL Server instance or the SQL vitutal server name in the Destination IP or FQDN vĩ đại query.Select Query predefined service and select SQL Service in the dropdown list.Click Query and examine the output and use the following table for additional pointers.

Examples outputs:

Default instance on mặc định port: Working scenario

Default instance on mặc định port: Non-working scenario

Named instance: Working scenario: (Instance name: SQL năm trước, hostname: SQLCONNVM)

Named instance: Non – Working scenario: (Instance name: SQL năm trước, hostname: SQLCONNVM)

For more information, move vĩ đại Configuring firewalls section.

If this does not resolve your issue, move vĩ đại Still having problems section.

Tell if SQL is listening on Dynamic vs Static ports

In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, expand Protocols for , and then double-click TCP/IP.

In the TCP/IP Properties dialog box, on the IP Addresses tab, several IP addresses appear in the format IP1, IP2, up vĩ đại IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. (You will probably see both IP version 4 and IP version 6 addresses.) Right-click each address, and then click Properties vĩ đại identify the IP address that you want vĩ đại configure.

If the TCP Dynamic Ports dialog box contains 0, it indicates that the Database Engine is listening on dynamic ports. If it contains a specific number, it means the database instance is listening on a static port.

For more information, see Configure a Server vĩ đại Listen on a Specific TCP Port.

If this does not resolve your issue, move vĩ đại Still having problems section.

No connection could be made because the target machine actively refused it

For more information about the no connection error, move vĩ đại The full error message section.

The full error message

You may get an error that is similar vĩ đại the following:

TCP Provider: No connection could be made because the target machine actively refused it.Login timeout expired.A network-related or instance-specific error has occurred while establishing a connection vĩ đại SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured vĩ đại allow remote connections. For more information see SQL Server Books Online.You can start troubleshooting from this section: Common causes of various connection issues.

SQL Server does not exist or access denied

You can start troubleshooting from this section: Common causes of various connection issues.

PivotTable Operation Failed: We cannot locate a server vĩ đại load the workbook Data Model

You can start troubleshooting from this section: Common causes of various connection issues.

Cannot Generate SSPI context error message

Security Support Provider Interface (SSPI) is a phối of Windows APIs that allows for delegation and mutual authentication over any generic data transport layer, such as TCP/IP sockets. Therefore, SSPI allows for a computer that is running a Windows operating system vĩ đại securely delegate a user security token from one computer vĩ đại another over any transport layer that can transmit raw bytes of data.The Cannot generate SSPI context error is generated when SSPI uses Kerberos authentication vĩ đại delegate over TCP/IP and Kerberos authentication cannot complete the necessary operations vĩ đại successfully delegate the user security token vĩ đại the destination computer that is running SQL Server.

Xem thêm: đính hôn cùng bạn học

For additional information as vĩ đại why the Kerberos operations cannot be completed, move vĩ đại Troubleshooting authentication failures due vĩ đại Kerberos issues section vĩ đại review and implement the steps.

Troubleshooting authentication failures due vĩ đại Kerberos issues

Kerberos authentication failures can happen due vĩ đại a variety of reasons. The major causes and corresponding resolutions are highlighted below: