Hi everyone,

  I have a application in which some processing of files is done. When the processing is carried, the same is interrupted by the error

   "Error:-2147217871 Timeout Expired"
My application is connected to the database on sql server 2000.
Please some one help me out with this. This is a client side exception and you people can imagine my position right now!!

Set CommandTimeout to a larger value.

Can you be more specific on this please?

If you are using ADO to connect to SQL Server, there is a property named CommandTimeout. Default is, I think, 30 seconds. Set this property to 300 for 5 minutes.

Thanks Peso.It has been very helpful for me!!:)

Also could you tell me where should i make these settings??
Please??

When you create your command object, set the obj.CommandTimeout to 300

Obj.CommantTimeOut = 300

HI
I have the following code for calling a Stored procedure, which is calculation intensive. Although I have increased all possible timeouts, it still gives me Timeout Expired -214721787 error

************************************************** ***********
    Set RS = New ADODB.Recordset
    Set cmd = New ADODB.Command

    'Init the ADO objects
    cmd.ActiveConnection = gsConnectionString
    cmd.CommandTimeout = 0
    cmd.CommandText = strSP
    cmd.CommandType = adCmdStoredProc

    'Create the stored proc parameters
    CreateParams cmd, varParams

    ' Execute the query for readonly
    RS.CursorLocation = adUseClient
    RS.CacheSize = 500
    RS.Open cmd, , adOpenForwardOnly, adLockReadOnly

    ' Disconnect the recordset
    Set cmd.ActiveConnection = Nothing
    Set cmd = Nothing
    Set RS.ActiveConnection = Nothing

    ' Return the disconnected recordset
    Set gdbrsRunSPReturnRS = RS
    Set RS = Nothing

************************************************** ***********

what can be done to resolve the issue?

You'll also get the timeout message if someone already has a lock on the SQL objects in the form of uncommitted updates or inserts. I also think that increasing the timeout to more than 30 seconds is just a band-aid for a much larger more serious problem. It could be transaction leaks (someone forgot to commit or rollback), poorly formed SQL, a bad database design, missing indexes, etc, etc. I'd start looking for what the actual cause of the timeout is because 30 seconds is more than anyone should have to wait in an app...

--Jeff Moden

Post the proc so folks can take a look at it...

--Jeff Moden