Provider timeout error 258



Provider timeout error 258

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

Answered by:

Question

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

Answers

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.

All replies

That error code, 0x80090311, is SEC_E_NO_AUTHENTICATING_AUTHORITY, from a Windows component called SSPI. Per their documentation here (http://msdn.microsoft.com/en-us/library/aa374705(VS.85).aspx), it means:

«The function failed. No authority could be contacted for authentication. This could be due to the following conditions:

  • The domain name of the authenticating party is incorrect.
  • The domain is unavailable.
  • The trust relationship has failed.»

If I’m understanding correctly those explanations, it probably means that either the SQL Server instance couldn’t contact the Domain Controller (maybe there is a bad network connection between them?) or there is some problem with the domain trusts between the client machine and the server machine.

However, I’m a little surprised to see the client giving a «login timeout» error when the server is throwing this error — I believe the server should immediately close the connection, in case of authentication failure. Are you sure that these client errors correspond 1-to-1 to the server error you have posted? If not, you might be able to resolve that specific client error just by increasing the Login Timeout (this can be controlled through the connection string).

Источник

Provider timeout error 258

Вопрос

Hopefully there is somebody that can help me.

When running the etl I’m getting the error: : Shared Memory Provider: Timeout error [258] ; followed by the message «Communication link failure».

What is special about this message that it happens on a SQL Execute task (random task) and the Timeout is after 2 minutes.

When executing the packages separatly it is working fine. The SQL Tasks that are failing are also quit heavy, but reasonable and takes between >2min and 10 — 15 min. Statements are stored procedures that puts an index on 3 mil. records or update statements.

I had a look to all my (SSIS-etl) timeouts and they have the default value 0, the «remote query timeout» of the server is set to 10 minutes. According to me, these are the only one that exists?

There are 2instances on the server each instance has 24GB allocated, the server has 64 in total. Also when the etl runs (that results in an error) no other etl is running on the 2 instances. I’m working with the oledb \sql server native client 11.0 provider: SQLNCLI11.1.

It is frustrating because I don’t have a clear error message. Maybe there or other places to look? I had a look on the application log & sql server log but it did not made me any wiser.

Any help is appriciated,

Читайте также:  Error data error cyclic redundancy check fix

Ответы

Does your package runs in 32-bit runtime mode? The 32-bit DTExec process can consume up to 2GB virtual memory. If possible, try to run the package in 64-bit runtime mode or break the existing package into several child packages, and use Execute Package Task to call the child packages in the parent package. When using child packages, set the ExecuteOutOfProcess option of each Execute Package Task to True so that each process can consume its own 2GB virtual memory.

If the issue persists, enable logging for the package, and post detailed error message for further analysis.

Mike Yin
TechNet Community Support

Все ответы

Can you change to SQLOLEDB.1 rather than SQLNCLI.1 and see if you have the same issue

PS, I tried it with SQLOLEDB.1 but I still receive the error message.

Something that I forgot to mention is that I’m using sql server 2012

This is a part of the sql error log at the same time of the error, I’m not sure if it’s related but you never know:

04/01/2014 20:00:21,spid14s,Unknown,last target outstanding: 358 avgWriteLatency 20
04/01/2014 20:00:21,spid14s,Unknown,average throughput: 5.08 MB/sec I/O saturation: 5995 context switches 14539
04/01/2014 20:00:21,spid14s,Unknown,FlushCache: cleaned up 72812 bufs with 3099 writes in 112026 ms (avoided 476 new dirty bufs) for db 9:0
04/01/2014 19:53:56,spid14s,Unknown,last target outstanding: 708 avgWriteLatency 33
04/01/2014 19:53:56,spid14s,Unknown,average throughput: 35.88 MB/sec I/O saturation: 25622 context switches 43694
04/01/2014 19:53:56,spid14s,Unknown,FlushCache: cleaned up 640748 bufs with 25437 writes in 139511 ms (avoided 59488 new dirty bufs) for db 9:0
04/01/2014 19:44:13,spid14s,Unknown,last target outstanding: 682 avgWriteLatency 75
04/01/2014 19:44:13,spid14s,Unknown,average throughput: 55.22 MB/sec I/O saturation: 24846 context switches 43655
04/01/2014 19:44:13,spid14s,Unknown,FlushCache: cleaned up 646031 bufs with 25310 writes in 91397 ms (avoided 118 new dirty bufs) for db 9:0
04/01/2014 18:34:03,spid14s,Unknown,last target outstanding: 194 avgWriteLatency 16
04/01/2014 18:34:03,spid14s,Unknown,average throughput: 9.68 MB/sec I/O saturation: 4396 context switches 8644
04/01/2014 18:34:03,spid14s,Unknown,FlushCache: cleaned up 78398 bufs with 3367 writes in 63280 ms (avoided 77538 new dirty bufs) for db 10:0

Источник

Provider timeout error 258

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

Answered by:

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

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

Читайте также:  Exception sqlstate 23000 integrity constraint violation

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.

Hope this would help you troubleshoot and resolve this issue.

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

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

All replies

It could be possible that the server is under heavier load during those times and so it is failing to respond within the timeout you provided. Do you have scheduled jobs running around those times, or is your network/server load any higher between 3 and 4 am?

With (local), it should go through the loopback device, which won’t need to do dns lookup or address resolution, or any of the other usual suspects for these kinds of failures. As you say, it may be the domain controller for NTLM authentication running slowly at that time or being down for some reason. It is hard to tell, with this one, why it might be happening. Do the server logs register anything about the connection attempts? It seems like it should definitely have gotten the prelogin/login packets — I wonder if there are log entries indicating something around those times?

No, the server logs don’t indicate any failed attempts. Only the messages indicated in my original post are shown.

Interestingly, I received exactly the same set of messages again last night, but that was during a known reboot of our domain controllers by our LAN department in order to apply some WSUS patches.

Just had log-shipping issues on our server this morning, and wanted to add that a burst of the [382] and [298] login failed messages appeared in our server Log File, same as indicated earlier in this thread. This is the first time we’ve seen these event log entries.

Our log shipping job runs every 5 minutes. Last night at 2:00am we ran a re-indexing job which caused the log shipping job to fail with insufficient disk space error on our local log shipping share due to huge transaction log. This first occurred at 3:35am . At 6:30 am, with the log shipping still enabled and still failing, we received the burst of logon failures. Everything else appeared normal on the server —no unusual load. Also, as with the thread’s earlier post, this server has been stable with log shipping running for over 6 mos.

Here’s a sample of our errors. Maybe this will shed some additional light.

They come in sets of four. I’m pasting them in chronological order, top to bottom.

Date 3/21/2008 6:30:35 AM
Log SQL Agent (Current — 3/21/2008 6:32:00 AM)

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

Date 3/21/2008 6:30:35 AM
Log SQL Agent (Current — 3/21/2008 6:32:00 AM)

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

Читайте также:  Pokemon masters error 10005

Date 3/21/2008 6:30:35 AM
Log SQL Agent (Current — 3/21/2008 6:32:00 AM)

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

Date 3/21/2008 6:30:35 AM
Log SQL Agent (Current — 3/21/2008 6:32:00 AM)

Message
[382] Logon to server ‘ELMSERVER8’ failed (ConnAttemptCachableOp)

The error you are getting is typically seen when a user connects succesfully and recieves an ack from the server, but then sends login credentials and does not complete the login process within a prespecified timeout. You are connecting over SM, so this is local and network issues can be ignored with the exception of the domain controller, who controls NTLM credential management and authentication. If you are using Integrated Authentication, your domain controller could be a culprit in this scenario. One general suggestion people offer for this issue is «lengthen the timeout», but I think that (at least in this case) this would not address your issue, as your job is running every 5 minutes. You may not be able to affort a 2 minute login timeout, and that doesn’t guarantee that you won’t see these issues, just lowers the probability of load-based issues causing failure. Is it possible to ping the domain controller on job failure to see if it is up and what its response time is like?

The ODBC error «Timeout expired» states that a query did not found to
return rows with the timeout period,
The cause for this could be that the query needed long time
to execute, because of large amounts of data to seek & Bad indexing.

It could also be a Lock issue with tables,
and that query was long-running. In fact it does not have to be a query
as such that was blocking, but a process holding locks reason behind
an earlier discarded query, which was not properly handled.
All this could have been started by some abnormal event like a
network problem. However, it is much more likely that there was
some unsuitable SQL statement.

After one week of researching on the Internet and talking with fellow Sys Admins here, none of us can figure out this issue. The issue is: We run a single server SharePoint site and that server’s got MS Sql Server 2005 on it. It is a Windows 2003 server with SP2. Since last Tuesday, our default web site would go down about every two to two-and-half hours and when trying to access the site would get a message stating «could not connect to configuration database.» When looking in error logs, it is not transparent except that on the server, we’ll see errors stating access is denied or there is no database available. After plugging in every SQL Log error code and many Event Log error codes, we cannot figure out the issue! When looking at the MSSQLSERVER, the SQLSERVER Agent services, they both still show they’re running, but when we restart the services, the site still isn’t accessible. We’ve talked to our Domain Admins to see if they’ve pushed anything to the domain controllers that out server authenticates throug (they did say they had pushed the latest Windows Server 2003 SP). Anyway, our only solution now is to re-boot the server every time the database cannot be accessed. Here’s what I’ve done so far:

NP, TCP/IP, and Shared Memory are enabled (and were before)

Service account does have access to the database and is not expired

I am new at this so if there’s any technical info required of me to clarify, please let me know and I will provide it. Thank you.

Источник

Оцените статью
toolgir.ru
Adblock
detector