Меню

Microsoft sql server ошибка 258

  • Remove From My Forums

  • Question

  • Hi Everyone,

    Please check the below screenshot once, One of my client getting this error he was unable to connect to the server.

    As I checked TCPIP protocol was enabled and i’m able to access the server as well but the guy getting below error message.

    Please suggest me how to troubleshoot this issue..Thanks in advance!

    Regards

    V

    DBA

Answers

    • Proposed as answer by

      Tuesday, March 22, 2016 6:51 PM

    • Marked as answer by
      Lydia ZhangMicrosoft contingent staff
      Thursday, March 31, 2016 7:02 AM

  • Windows authentication or SQL authentication?

    The message as such is the standard message when the instance cannot be reached. However, error 258 is unusual in this context. And it is not an SQL Server error, it’s an OS error; NET HELPMSG 258 says
    The wait operation timed out.

    This could possibly indicate that you are arriving somewhere, but no one is actually listening. That is, the port is open but the process is busy with something else. (And that is necessarily not an SQL Server process.)

    Try connecting by IP-address and port number in case there is some DNS problem.

    • Proposed as answer by
      Naomi N
      Wednesday, March 23, 2016 10:20 PM
    • Marked as answer by
      Lydia ZhangMicrosoft contingent staff
      Thursday, March 31, 2016 7:02 AM

Источник

SQL Server 2012 Enterprise SQL Server 2012 Developer SQL Server 2012 Express SQL Server 2012 Standard SQL Server 2012 Web Еще…Меньше

Симптомы

При попытке войти в систему или подключиться к экземпляру Microsoft SQL Server 2012 устанавливается в Windows Server 2012, может появиться одно из следующих сообщений об ошибке тайм-аута:

  • Сообщение об ошибке 1

    [SQLSTATE 01000] (Сообщение 0) SQLState = 08001, NativeError = [SQLSTATE 01000] 258 ошибки (сообщение 0) = поставщик TCP [Microsoft] [SQL Server собственного клиента 11.0]: [258] ошибка истечения времени ожидания. [SQLSTATE 01000] (Сообщение 0) SQLState = 08001, NativeError = [SQLSTATE 01000] 258 ошибки (сообщение 0) = [Microsoft] [SQL Server собственного клиента 11.0] не удается завершить процесс входа в систему из-за задержки в ответ перед входом [SQLSTATE 01000] (сообщение 0) SQLState = S1T00 NativeError = 0 [SQLSTATE 01000] Ошибка (сообщение 0) = [Microsoft] [SQL Server собственного клиента 11.0] время ожидания входа истекло [SQLSTATE 01000] (сообщение 0)

  • Сообщение об ошибке 2

    <Штамп времени> -! [165] Ошибка ODBC: 0, время ожидания входа истекло [SQLSTATE HYT00]
    <Штамп времени> -! [298] Ошибка SQLServer: 258, не удается завершить процесс входа в систему из-за задержки в ответ перед входом [SQLSTATE 08001]
    <Штамп времени> -! [382] Ошибка входа с сервера «<Имя_базы_данных>» (SubSystemStepHistoryLogger)
    <Штамп времени> -! [298] Ошибка SQLServer: 258, поставщик TCP: [258] ошибка истечения времени ожидания. [SQLSTATE 08001]

Решение

Для решения этой проблемы попытайтесь сначала применить следующих обновлений Windows Server 2012 в Microsoft Knowledge Base:

2779768 Windows Server 2012 и Windows 8 накопительный пакет обновления: Декабрь 2012 г.

Причина

Эта проблема может возникнуть из-за блокировки поток, который вызывает AcceptEX вызовов в режиме ядра (драйвер AFD.sys) в Windows Server 2012. Записывать трассировку сетевого монитора, может оказаться, что некоторые сетевые пакеты достигают сервера. Однако из-за изменений, диспетчер ввода-вывода, вызов GetQueuedCompletionStatus не удается обнаружить сеть данные, полученные и в результате задержки операции сетевого приложения (в данном случае приложением является SQL Server).

Примечание. Windows Server 2012 вносит изменение в диспетчер ввода-вывода, и это изменение влияет на поведение вызова AcceptEX .

Статус

Корпорация Майкрософт подтверждает, что это проблема продуктов Майкрософт, перечисленных в разделе «Относится к».

Нужна дополнительная помощь?

Источник

I get the following message when trying to connect to SQL database from a remote machine using MS Management Studio with Server Name [ XX.XXX.XXX.XXX,1433MyServerName ] and SQL authentication:

Cannot connect to XX.XXX.XXX.XXX,1433MyServerName.

ADDITIONAL INFORMATION:
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: TCP Provider, error: 0 — The wait operation timed out.) (Microsoft SQL Server, Error: 258)

The wait operation timed out

I have done the following:

  • Allowed remote connection in Server Properties window in SQL Management Studio
  • Configured server machine to have static IPv4/DNS addresses.
  • Enabled TCP/IP in SQL Configuration Manager (in SQL Server Network Configuration)
  • In TCP/IP properties, adjusted [ Protocol -> Listen All -> No ] & set IP[1-8] to TCP port 1433 and IPAll port to 1433 (TCP dynamic ports left blank)
  • Set Inbound/Outbound enable connection (Domain, public, private) rules in Windows Firewall for ports TCP 1433, UDP 1434 (should make no difference, since port is specified), service executables: sqlbrowser.exe in C:Program Files (x86)Microsoft SQL Server90Shared (not used I think because port is specified) and sqlservr.exe in C:Program FilesMicrosoft SQL ServerMSSQL13.MyServerName MSSQLBinn
  • Set NAT actions in server-side router for ports 1433 (TCP), 1434 (UDP) (again, should not matter) to server’s local IPv4 address and ports 1433, 1434 accordingly.
  • Made sure SQL service is running, ports are open and listening on server machine.

I can connect to the database on server machine using Windows or Sql credentials with either PC name, or machine’s local IPv4.

Interesting thing is, when >telnet XX.XXX.XXX.XXX 1433 is run, it takes about 10-12 seconds to fail (Could not open connection to the host, on port 1433: Connect failed), but I can see the 2 packets coming to the router itself. Same with the login using SQL Manager — packets come to the router, but either server machine refuses (doesn’t resolve?) the connection, or it doesn’t even get to the machine.

Appreciate your suggestions.

Versions used:

  • MS SQL Server 2016 Express, MS SQL Management Studio 17, SQL Server 2016 Configuration Manager, Windows 10 Pro.
Источник
  • Remove From My Forums

  • Question

  • Hi Experrts,

    we are receiving below error since 1 week, 

    The below error logging in SQL AGENT LOG.

    [298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001]

    Thanks in advance.

Answers

  • Hello,

    Is that instance a SQL Server 2012 instance? If that is the case, please read the following article:

    http://support.microsoft.com/kb/2919863/en-us

    Could you share the output of the following query with us?

    select
    top 40 *

    from
    sys.dm_os_wait_stats

    order
    by wait_time_ms
    desc

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Proposed as answer by

      Tuesday, July 22, 2014 7:07 PM

    • Marked as answer by
      vijay_1234
      Tuesday, July 29, 2014 6:32 AM

  • Some times, we can see this error message ([298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001]) from remote logins.

    Please connect to the SQL server from local machine and try to increase remote login time and let me know if it working or not.

    Note that «remote logins» here refers to connect to linked servers. So far, Vijay has not said anything about linked servers. As far as I understand, the problem is that SQL Server Agent reports this error, and it seems clear that it is connecting
    to the local server.

    It is not easy to troubleshoot with this miniscule of information, but I would guess that the job is owned by a domain user? The problem may be related to veruify that user in the AD.

    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    • Marked as answer by
      vijay_1234
      Tuesday, July 29, 2014 6:32 AM

Источник
  • Remove From My Forums

  • Question

  • Hi Experrts,

    we are receiving below error since 1 week, 

    The below error logging in SQL AGENT LOG.

    [298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001]

    Thanks in advance.

Answers

  • Hello,

    Is that instance a SQL Server 2012 instance? If that is the case, please read the following article:

    http://support.microsoft.com/kb/2919863/en-us

    Could you share the output of the following query with us?

    select
    top 40 *

    from
    sys.dm_os_wait_stats

    order
    by wait_time_ms
    desc

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Proposed as answer by

      Tuesday, July 22, 2014 7:07 PM

    • Marked as answer by
      vijay_1234
      Tuesday, July 29, 2014 6:32 AM

  • Some times, we can see this error message ([298] SQLServer Error: 258, Unable to complete login process due to delay in login response [SQLSTATE 08001]) from remote logins.

    Please connect to the SQL server from local machine and try to increase remote login time and let me know if it working or not.

    Note that «remote logins» here refers to connect to linked servers. So far, Vijay has not said anything about linked servers. As far as I understand, the problem is that SQL Server Agent reports this error, and it seems clear that it is connecting
    to the local server.

    It is not easy to troubleshoot with this miniscule of information, but I would guess that the job is owned by a domain user? The problem may be related to veruify that user in the AD.

    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    • Marked as answer by
      vijay_1234
      Tuesday, July 29, 2014 6:32 AM

Источник

SQL Server Error : 258 Details

SQL Server Error: 258
Severity: 15
Event Logged or not: No
Description:
Cannot call methods on %ls.
Severity 15 Description:
Indicates syntax errors in the Transact-SQL command.

Cannot connect to Server, 1433InstanceName.

ADDITIONAL INFORMATION: 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: TCP Provider, error: 0 – The wait operation timed out.) (Microsoft SQL Server, Error: 258)

The wait operation timed out

Solution for Resolving the Error

  1.  Check that ping the target server from the computer the package is running on? If not, the server may be down or there may be routing or DNS issues
  2. Try a telnet session to the server using the port number? If not, SQL Server may not be running
  3. Make sure spelling of the server and instance name is correctly typed?
  4. Make sure the target server have TCP enabled in SQL Server Configuration Manager?
  5. Try connect to the server from anywhere else?
  6. Make Sure SQL Server Browser running on the target computer, or make sure you did supply the port number in the connection string?

Alternate Solutions

  1. Restarting SQL Server Service(non production instances only)

  • To Restart, Start or Stop the SQL Server instance by right click on sql server instance in SSMS or in SQL. You may need to open SSMS as administrator to start, stop the instance.

db-mail4

  • Other ways for restarting SQL server Service

  1. Running SQL Configuration manager from Start menu to restart services
  2. From Services in Windows server
  3. Running Command prompt Cmd using net start and net stop

SQL Server Error Code and solution summary

SQL Server Error: 258
Severity: 15
Event Logged or not: No
Description:
Cannot call methods on %ls.

Make sure SQL Server is running and reachable. TCP enabled etc..

Источник

September 1, 2015 by Sameer

Possible Root Cause: Unstable Network connectivity to database server or problems with a server in the route

Steps Taken To Confirm Root Cause: 

Setup traceroute at regular intervals using the batch file below

@ECHO OFF

set SERVER=DBServerName.domainname.com

set INTERVAL=60

:TRACEINTERVAL

tracert %SERVER% >> C:DBServerNametracert.txt

timeout %INTERVAL%

GOTO TRACEINTERVAL

In my case, no issues were found, was able to connect to DBServerName continously. This would indicate there are no network connectivity issues.

Possible Root Cause: Issues connecting to Active Directory Server

Steps Taken To Confirm Root Cause: Tried connecting via a SQL id using SSMS & SQLCMD encountered the same issue.

Possible Root Cause: DNS Problems

Steps Taken To Confirm Root Cause: Tried connecting via IP, still encountered the same issue

Possible Root Cause: Issues connectiving via IPv4 or IPv6 address

Steps Taken To Confirm Root Cause:

Checked TCP/IP properties in configuration manager on database server; server was listening to all IP’s.

Tried connecting manually using the IPv4 addresses as well as IPv6 addresses; Encountered the same error in both, so issue was not related to this cause.

C:UserssameerDesktop>sqlcmd -S DBServerName.domainname.com -E

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : TCP Provider: Timeout error [258].

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Login timeout expired.

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Unable to complete login process due to delay in prelogin response.

C:UserssameerDesktop>sqlcmd -S fe40::d0f8:6600:8b2:625b%14 -E

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Named Pipes Provider: Could not open a connection to SQL Server [53]. .

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : Login timeout expired.

Sqlcmd: Error: Microsoft SQL Server Native Client 11.0 : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

Possible Root Cause: TCP/IP Port Exhaustion

Steps Taken To Confirm Root Cause:n netstat -ao on the database server while connecting to it from a client server. Consistently observed a TCP connection was being established between both servers, even when the SQL error message was occuring. This means the TCP connection is fine, and there is no TCP/IP port exhaustion.

 Possible Root Cause: Resource Constraints on DBServerName server can cause login denials

Steps Taken To Confirm Root Cause:Checked RAM, CPU usage on the database server; CPU was under 10% and RAM was around 60%

Possible Root Cause: AntiVirus software running on database server

Steps Taken To Confirm Root Cause:

Trend Micro was running on the database server. Removing this fixed the issue

Источник

@MarvinNorway we’re using 4.1.0 of SqlClient and Functions V4, deployed to Linux app service , still get this error — what kind of app is yours?
Microsoft.Data.SqlClient.SqlException: at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniError (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.TdsParserStateObject.TryReadByte (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.TdsParser.TryRun (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.TdsParser.Run (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.RunParser (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinuedOnSuccess (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5) at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServer (Microsoft.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5)

Источник

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Microsoft sql server ошибка 229
  • Microsoft sql server ошибка 223

    • ➤