Timeout Expired error even if the connection time out is 400 and command timeout is 0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • priravi
    New Member
    • May 2007
    • 11

    Timeout Expired error even if the connection time out is 400 and command timeout is 0

    Hi,

    I have a connection timeout of 400 and command timeout of 0 for a stored procedure . the stored procedure retrieves a long data and store it in dataset.

    I'm getting the "System.Data.Sq lClient.SqlExce ption: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." exception thrown on that stored procedure ... any ideas why it may happen . i'm using execute dataset
  • Shashi Sadasivan
    Recognized Expert Top Contributor
    • Aug 2007
    • 1435

    #2
    I have had a similar issue before
    But they network administrators couldnt find out where the data was being dropped and where it was going slow

    but the way i solved it was to turn connection pooling off.
    edit your connection string to turn pooling off.
    See how that goes

    Comment

    Working...