Results 1 to 14 of 14

Thread: -2147467259 Timeout expired

  1. 08-19-2003, 02:22 PM #1
    Ads
    Ads is offline Registered User
    Join Date
    Oct 2002
    Posts
    123

    -2147467259 Timeout expired

    One of my developers is getting the following error on his client machines:

    Microsoft OLE DB Provider for SQL Server:-2147467259 Timeout expired

    He says that there has been no changes in his application & I know that there has been no changes on the database, still suddenly we start getting this error.
    We are on SQL 7.0. I searched the knowldege base but did not find any particular article on this kind of problem. Any clue what might be happening or how I can check for this?
    Also, I ran a trace for the same… & it doesn’t show me any timeouts there. Is there a particular parameter that I have to trace on?

    Thanks!
    Reply With Quote Reply With Quote
  2. 08-19-2003, 02:33 PM #2
    rmiao
    rmiao is offline Registered User
    Join Date
    Sep 2002
    Posts
    5,938
    Seems it happened when app tries to connect to sql. How does the app connect to sql server? Any network issue there?
    Reply With Quote Reply With Quote
  3. 08-19-2003, 02:36 PM #3
    MAK's Avatar
    MAK
    MAK is offline Registered User
    Join Date
    Sep 2002
    Location
    Fantasy
    Posts
    4,254
    1. see whether Network admins changed the NIC cards and left to default setting instead of full duplex (on his machine)
    2. try to ping the server from his machine.
    3. if application uses native connection then add your database server name in the client network utility
    My Site:http://www.mssqlengineering.com
    My Book:http://www.wiley.com/WileyCDA/WileyT...470477288.html
    Reply With Quote Reply With Quote
  4. 08-19-2003, 02:50 PM #4
    Ads
    Ads is offline Registered User
    Join Date
    Oct 2002
    Posts
    123
    The problem looks intermittent. They get timeout errors & then if they try again a couple of time, they are able to connect & commit… I am still trying to fing out all the answers to your questions…. Thanks for the prompt response!
    Reply With Quote Reply With Quote
  5. 08-19-2003, 02:59 PM #5
    Ads
    Ads is offline Registered User
    Join Date
    Oct 2002
    Posts
    123
    The problem looks intermittent. They get timeout errors & then if they try again a couple of time, they are able to connect & commit… I am still trying to fing out all the answers to your questions…. Thanks for the prompt response!
    Reply With Quote Reply With Quote
  6. 08-19-2003, 03:00 PM #6
    MAK's Avatar
    MAK
    MAK is offline Registered User
    Join Date
    Sep 2002
    Location
    Fantasy
    Posts
    4,254
    if it is happening for a group of people or many users then check your database maintenece job (reindex).

    make sure it runs many times in a week and also increase the time out option in the frontend.
    My Site:http://www.mssqlengineering.com
    My Book:http://www.wiley.com/WileyCDA/WileyT...470477288.html
    Reply With Quote Reply With Quote
  7. 08-19-2003, 03:01 PM #7
    MAK's Avatar
    MAK
    MAK is offline Registered User
    Join Date
    Sep 2002
    Location
    Fantasy
    Posts
    4,254
    what front end it is? VB or ASP or delphi or ms-acsess??
    My Site:http://www.mssqlengineering.com
    My Book:http://www.wiley.com/WileyCDA/WileyT...470477288.html
    Reply With Quote Reply With Quote
  8. 08-19-2003, 03:14 PM #8
    Ads
    Ads is offline Registered User
    Join Date
    Oct 2002
    Posts
    123
    Yes it is happening for a group of people. My reindexing job runs every Sunday. I can run that again & see if that helps.
    There are no network problems reported.
    They are using an OLE DB connection string in their application…
    Reply With Quote Reply With Quote
  9. 08-19-2003, 03:15 PM #9
    Ads
    Ads is offline Registered User
    Join Date
    Oct 2002
    Posts
    123
    VB front end
    Reply With Quote Reply With Quote
  10. 08-19-2003, 03:34 PM #10
    rmiao
    rmiao is offline Registered User
    Join Date
    Sep 2002
    Posts
    5,938
    Try increase the time out value in OLE DB connection string.
    Reply With Quote Reply With Quote
  11. 08-19-2003, 03:39 PM #11
    BMan111
    BMan111 is offline Registered User
    Join Date
    Jun 2003
    Location
    Bloomington, IN, USA
    Posts
    116
    Try increase the time out value in OLE DB connection string.
    didnt mak already make that sudgestion? or are the two of you talking about two completly different intervels that happen to control the same thing?


    Brandon
    Reply With Quote Reply With Quote
  12. 12-03-2003, 01:32 PM #12
    Ads
    Ads is offline Registered User
    Join Date
    Oct 2002
    Posts
    123
    i need help again.. for some time the client was not getting timeouts... now it has started again...
    the timeout parameter is already set to 90 secs!
    in the meantime i have also been running a trace trapping all exeptions & errors....at about the time the client sees a timeout,
    I get an Exception in my trace. It doesnt give me any more information except saying Exception.... is there another parameter that
    I can trace for?
    It looks like
    any thoughts/help is appreciated.
    Reply With Quote Reply With Quote
  13. 12-03-2003, 05:19 PM #13
    rmiao
    rmiao is offline Registered User
    Join Date
    Sep 2002
    Posts
    5,938
    Any error in sql server log around that time?
    Reply With Quote Reply With Quote
  14. 12-04-2003, 11:52 AM #14
    Ads
    Ads is offline Registered User
    Join Date
    Oct 2002
    Posts
    123
    no - nothing in sql server error log or the event log...
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules