Поставщик tcp ошибка времени ожидания 258

  • Remove From My Forums

  • Question

  • Hi

         Users complain that when their jobs connect to SQL Server, they get below error message.  They connect using SSMS or client applications.  If they continuously try connecting, it connects without errors.

    [SQL Native Client]TCP Provider: Timeout error [258].
    [SQL Native Client]Login timeout expired
    [SQL Native Client]Unable to complete login process due to delay in login
    response

         When I checked error log, I found below messages. 

    2010-02-24 21:32:00.670 Logon        Login failed for user ». The user is not associated with a trusted SQL Server connection. [CLIENT: 111.111.111.10]
    2010-02-24 21:32:00.820 Logon        Error: 17806, Severity: 20, State: 2.
    2010-02-24 21:32:00.820 Logon        SSPI handshake failed with error code 0x80090311 while establishing a connection with integrated security; the connection has been closed. [CLIENT: 111.111.111.10]

         Could some one look into this issue and help/suggest?

    Thanks In Advance

    Vicky

    Thanks

Answers

  • Dan

        Thanks for your reply.  The above mentioned resolution was work around and now its been permanently fixed by Modifying hosts file for the problem server to have static entry to their domain controllers.  I am not sure on what was the actual issue.

    Thanks

    Thanks

    • Marked as answer by

      Wednesday, March 17, 2010 3:54 AM

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

  • Question

  • I’ve received this error twice over 2 days in the SQL Agent error log during off-hours from a server which has not had any changes to it in the last few months (once at 3:32AM and the next day at 3:46AM.  I’ve been able to tie it to log-shipping backup jobs (all of which run under the SQL Service domain account) which run every minute.  It seems to be only momentary, as the next attempt a minute later is successful.

    I get the same set of messages for each database for the same time which look like this:

    Date  07.03.2008 3:31:51 AM
    Log  SQL Agent (Current — 10.03.2008 6:15:00 PM)

    Message
    [298] SQLServer Error: 258, TCP Provider: Timeout error [258]. [SQLSTATE 08001]

    Date  07.03.2008 3:31:52 AM
    Log  SQL Agent (Current — 10.03.2008 6:15:00 PM)

    Message
    [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]

    Date  07.03.2008 3:31:52 AM
    Log  SQL Agent (Current — 10.03.2008 6:15:00 PM)

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

    Date  07.03.2008 3:31:52 AM
    Log  SQL Agent (Current — 10.03.2008 6:15:00 PM)

    Message
    [382] Logon to server ‘(local)’ failed (SubSystemStepHistoryLogger)

    I can’t find any documentation on these errors on the web or MSDN site.  Can I chalk this up to possibly «winking» connection to our domain controller?  We’ve never had these messages before, and our LAN department swears that there have been no upgrades to the network or domain controller servers recently.

Answers

  • Sunrise,

    I had almost a similar experience this week.We got a STELLENT content software which is using SQL 2K as backend.

    There were other databases hosted in this SQL box and one of my colleague restedted the SQL service (planned restart) and Stellent and some of the applications weren’t connecting.

    When we restarted the server, everything works fine. We again restarted DB services to figure out the root cause. Stellent down after SQL service restart. Raised a ticket with Oracle who bought Stellent and wasn’t helpful.

    Finally after 2 days we found out the problem.

    The TCP\IP wasn’t listening for SQL Server when the service is restarted. But will listen when the machine is rebooted which we can’t do much as there is one more instance and some other DB applications.

    So we disabled TCP and reenabled after service restart and everything worked like a charm.

    Now we know the immediate workaround for this issue if happen again. Smile

    Hope this would help you troubleshoot and resolve this issue.

    Please let us know if this helped you resolve your issue.

    thx,

    Jose Mathew

    If this post helped you resolve your issue, please mark ‘answered’

Источник

Содержание

  1. Появляется сообщение об ошибке времени ожидания при подключении к экземпляру SQL Server 2012, который работает под управлением Windows Server 2012
  2. Симптомы
  3. Решение
  4. Причина
  5. Статус
  6. Ms sql server error 258
  7. Answered by:
  8. Question
  9. Answers
  10. All replies
  11. Ms sql server error 258
  12. Вопрос
  13. Ответы
  14. Все ответы

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

Симптомы

При попытке войти в систему или подключиться к экземпляру 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 .

Статус

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

Источник

Ms sql server error 258

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

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!

Answers

Please read the following article:

Hope this helps.

  • Proposed as answer by Raul Garcia — MS Microsoft employee Tuesday, March 22, 2016 6:51 PM
  • Marked as answer by Lydia Zhang Microsoft 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 Zhang Microsoft contingent staff Thursday, March 31, 2016 7:02 AM

I will surmise that the problem is specific to the one person, otherwise users would be complaining.

My first thought is to check is connectivity, make sure he is on a network that can actually reach the SQL server. At the risk of sounding like a network guy, can he ping the server? Can he at least make an RDP connection to the point of being prompted for credentials? (Successful logon is a moot point as long as he is prompted).

There is always the standard Windows question of how long has it been since the affected client machine (not the SQL server) has been rebooted, if it has been a while reboot.

Please read the following article:

Hope this helps.

  • Proposed as answer by Raul Garcia — MS Microsoft employee Tuesday, March 22, 2016 6:51 PM
  • Marked as answer by Lydia Zhang Microsoft 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 Zhang Microsoft contingent staff Thursday, March 31, 2016 7:02 AM

select * from sys.messages
where message_id = 258 and language_id = 1033

Cannot call methods on %ls.

make sure below check list is passed.

1) ping the server from your client machine. (this will make sure network connection is ok)

2) tcp/ip is enables

3) if you are using different port make sure your client is including that number in the connection string

4) finally on your SQL server make sure remote connection are allowed.

select * from sys.messages
where message_id = 258 and language_id = 1033

Cannot call methods on %ls.

Enric, 258 is an OS error message. You can’t get an error message from SQL Server if you cannot connect to it. 🙂

what clever am I, sorry, this error is previous to SQL

Oddly, I see this happening more often than I’d expect. I did notice that a PING to the server name came back with the IPv6 address rather than the IPv4 address. I don’t expect that would be the case with everyone, but I have the Windows 2016 Business Essentials setup as my domain controller and it may have been upgraded from previous versions. I am still getting accustomed to differences.

That said, at this point, there is a continuous Error 258 returned. I tried changing the hosts file to reflect the IPv4 rather than the IPv6 (which worked), but the timeout still occurs. I suspect there is an issue with certificates that may be beyond my ability to understand at this point. I will persist here and discover some other method.

The SQL Browser is running meaning the first one should have worked since it is all within the domain. In the calling application D:Program FilesMicrosoft SQL ServerMSSQL14.HALLORANMSSQLBinnsqlservr.exe is a firewall exception and in the destination server, the port is open in the inbound rules.

I am thinking the remote timeout being too short is nonsense — Ping is 3ms — but I’ll try that too.

Different than what the others have here — my database engine service is running on a group Managed Service Account that has domain and SPN capability across three servers running SQL Server Enterprise or Developer — whichever is preferred. The SPN’s will need to be checked. Possibly that is also the issue. One of the SPN requirements is to create the SPN only from the server itself (and I keep saying server but these instances are actually running on Windows 10 v1809 machines).

So much to check now. What happened to those good old days? When life was so much easier.

Источник

Ms sql server error 258

Вопрос

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!

Ответы

Please read the following article:

Hope this helps.

  • Предложено в качестве ответа Raul Garcia — MS Microsoft employee 22 марта 2016 г. 18:51
  • Помечено в качестве ответа Lydia Zhang Microsoft contingent staff 31 марта 2016 г. 7:02

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.

  • Предложено в качестве ответа Naomi N 23 марта 2016 г. 22:20
  • Помечено в качестве ответа Lydia Zhang Microsoft contingent staff 31 марта 2016 г. 7:02

Все ответы

I will surmise that the problem is specific to the one person, otherwise users would be complaining.

My first thought is to check is connectivity, make sure he is on a network that can actually reach the SQL server. At the risk of sounding like a network guy, can he ping the server? Can he at least make an RDP connection to the point of being prompted for credentials? (Successful logon is a moot point as long as he is prompted).

There is always the standard Windows question of how long has it been since the affected client machine (not the SQL server) has been rebooted, if it has been a while reboot.

Please read the following article:

Hope this helps.

  • Предложено в качестве ответа Raul Garcia — MS Microsoft employee 22 марта 2016 г. 18:51
  • Помечено в качестве ответа Lydia Zhang Microsoft contingent staff 31 марта 2016 г. 7:02

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.

  • Предложено в качестве ответа Naomi N 23 марта 2016 г. 22:20
  • Помечено в качестве ответа Lydia Zhang Microsoft contingent staff 31 марта 2016 г. 7:02

select * from sys.messages
where message_id = 258 and language_id = 1033

Cannot call methods on %ls.

make sure below check list is passed.

1) ping the server from your client machine. (this will make sure network connection is ok)

2) tcp/ip is enables

3) if you are using different port make sure your client is including that number in the connection string

4) finally on your SQL server make sure remote connection are allowed.

select * from sys.messages
where message_id = 258 and language_id = 1033

Cannot call methods on %ls.

Enric, 258 is an OS error message. You can’t get an error message from SQL Server if you cannot connect to it. 🙂

what clever am I, sorry, this error is previous to SQL

Oddly, I see this happening more often than I’d expect. I did notice that a PING to the server name came back with the IPv6 address rather than the IPv4 address. I don’t expect that would be the case with everyone, but I have the Windows 2016 Business Essentials setup as my domain controller and it may have been upgraded from previous versions. I am still getting accustomed to differences.

That said, at this point, there is a continuous Error 258 returned. I tried changing the hosts file to reflect the IPv4 rather than the IPv6 (which worked), but the timeout still occurs. I suspect there is an issue with certificates that may be beyond my ability to understand at this point. I will persist here and discover some other method.

The SQL Browser is running meaning the first one should have worked since it is all within the domain. In the calling application D:Program FilesMicrosoft SQL ServerMSSQL14.HALLORANMSSQLBinnsqlservr.exe is a firewall exception and in the destination server, the port is open in the inbound rules.

I am thinking the remote timeout being too short is nonsense — Ping is 3ms — but I’ll try that too.

Different than what the others have here — my database engine service is running on a group Managed Service Account that has domain and SPN capability across three servers running SQL Server Enterprise or Developer — whichever is preferred. The SPN’s will need to be checked. Possibly that is also the issue. One of the SPN requirements is to create the SPN only from the server itself (and I keep saying server but these instances are actually running on Windows 10 v1809 machines).

So much to check now. What happened to those good old days? When life was so much easier.

Источник

Have same problem here:
Anyway to fix this

18/03/2022 07:22:34 - Error - Qi.TnNew.Core.Interfaces.IGlobalExceptionHandlerError: On url: http://study.hanoi.edu.vn/huong-dan-thi/on-tap-thcs-mon-tieng-anh-9-e-so-18-302 | 1173060 System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (258): Unknown error 258 at System.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__126_0(Task1 result) at System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location --- at Dapper.SqlMapper.QueryRowAsync[T](IDbConnection cnn, Row row, Type effectiveType, CommandDefinition command) in /_/Dapper/SqlMapper.Async.cs:line 473 at Qi.TnNew.Infrastructure.Data.TestDetailsLogData.GetRawTestDetailsByKey(String key) in /src/src/Qi.TnNew.Infrastructure/Data/TestDetailsLogData.cs:line 34 at Qi.TnNew.Core.Services.ExamService.CacheGetRawTestDetailsAsync(String detailsLogKey) in /src/src/Qi.TnNew.Core/Services/ExamService.cs:line 504 at Qi.TnNew.Core.Services.ExamService.CreateTestDetailsAsync(Int64 examId, Int64 userId, String detailsLogKey) in /src/src/Qi.TnNew.Core/Services/ExamService.cs:line 520 at Qi.TnNew.Core.Services.ExamService.CreateTestDetailForUserAsync(Int64 examId, Int64 userId, String detailsLogKey) in /src/src/Qi.TnNew.Core/Services/ExamService.cs:line 176 at Qi.TnNew.Web.Controllers.HomeController.<TestGuide>g__TakeAnExamAsync|24_1(Int64 userId, Int64 examId, String examTypeCode) in /src/src/Qi.TnNew.Web/Controllers/HomeController.cs:line 514 at Qi.TnNew.Web.Controllers.HomeController.TestGuide(Int64 id) in /src/src/Qi.TnNew.Web/Controllers/HomeController.cs:line 515 at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Logged|17_1(ResourceInvoker invoker) at Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult) at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Builder.Extensions.MapWhenMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Qi.TnNew.Web.Startup.<>c.<b__8_1>d.MoveNext() in /src/src/Qi.TnNew.Web/Startup.cs:line 177 — End of stack trace from previous location — at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task) ClientConnectionId:017c41d4-d10b-445b-b356-9197e1814fd0 Error Number:-2,State:0,Class:11`

Источник
  • 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)

Источник

При попытке подключиться к базе данных SQL с удаленного компьютера с помощью MS Management Studio с именем сервера [ XX.XXX.XXX.XXX, 1433\MyServerName ] и аутентификацией SQL появляется следующее сообщение:

Не удается подключиться к XX.XXX.XXX.XXX, 1433\MyServerName.

ДОПОЛНИТЕЛЬНАЯ ИНФОРМАЦИЯ: При установлении соединения с SQL Server произошла ошибка, связанная с сетью или конкретным экземпляром. Сервер не найден или не был доступен. Проверьте правильность имени экземпляра и настройте SQL Server для удаленного подключения. (поставщик: поставщик TCP, ошибка: 0 — время ожидания приостановлено.) (Microsoft SQL Server, ошибка: 258)

Ожидаемая операция ожидания

Я сделал следующее:

    Допустимое удаленное подключение в окне «Свойства сервера» в SQL Management Studio Настроенный серверный компьютер с статическими IPv4/DNS-адресами. Включено TCP/IP в SQL Configuration Manager (в конфигурации сети SQL Server) В свойствах TCP/IP настроено [Protocol → Listen All → No] и установите IP [1-8] на порт TCP 1433 и IPAll на 1433 (динамические порты TCP остаются пустыми) Установить правила входящего/исходящего подключения (Domain, public, private) в брандмауэре Windows для портов TCP 1433, UDP 1434 (не должно различаться, поскольку порт указан), исполняемые файлы службы: sqlbrowser.exe в C:\Program Files (x86 )\Microsoft SQL Server\90\Shared (не используется, я думаю, потому что указан порт) и sqlservr.exe в C:\Program Files\Microsoft SQL Server\MSSQL13.MyServerName\MSSQL\Binn Установите действия NAT на серверном маршрутизаторе для портов 1433 (TCP), 1434 (UDP) (опять же, не имеет значения) на локальный адрес IPv4 сервера и порты 1433, 1434 соответственно. Убедитесь, что служба SQL запущена, порты открыты и прослушиваются на серверной машине.

Я могу подключиться к базе данных на серверной машине с использованием учетных данных Windows или Sql с именем компьютера или локальным IPv4 на компьютере.

Интересно, когда >telnet XX.XXX.XXX.XXX 1433, требуется провал 10-12 секунд (невозможно открыть соединение с хостом, на порте 1433: соединение не удалось), но я вижу 2 пакеты, поступающие на маршрутизатор. То же самое с логином с использованием SQL Manager — пакеты поступают на маршрутизатор, но либо серверная машина отказывается (не разрешает?) Соединение, либо даже не добирается до машины.

Цените свои предложения.

Используемые версии:

    MS SQL Server 2016 Express, MS SQL Management Studio 17, SQL Server 2016 Configuration Manager, Windows 10 Pro.

Источник

Понравилась статья? Поделить с друзьями:
  • Поставить роспись лексическая ошибка
  • Поставить пьесу лексическая ошибка
  • Поставить проблему речевая ошибка
  • Поставить под угрозу срыва ошибка лексическая
  • Поставить мировой рекорд лексическая ошибка