I am using an adapter

using (DataAccessAdapter adapter = new DataAccessAdapter()) {

I create a new entity and save it ... no problem.

I then call an actionProcedure and it times out. }

I have read where I can set adapter.CommandTimeOut = 120; and I do set this after the saveEntity and immediately prior to calling the actionProcedure

and in debugging the code I do see that the adaptor commandtimeout is set to 120 prior to executing the actionProcedure. However, the procedure times out after 30 seconds.

Am I missing something?

Here is a little more info SQL Server 2005 Dev Edition running on a laptop LLBLGen v2.x ASP.Net 2.0 / VS 2005

Are you sure you don't need to set the connection timeout? Please check this thread: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=5301

Please try to call this SP manually from the database tools, to see if it timeout or see how long it takes it to execute.

Saw the other thread, not sure what you want me to take from it ... I have no problem connecting to the database, it is the command that is timing out.

The manual execute takes 35 seconds in Sql Management tools.

Just to make sure, when you call the actionStoredProcedure, would you be able to see the SP call in the SQL Profiler?

I have a feeling the application is facing problems finding or accessing the specified SP.

the stored procedure is getting called ... as this SProc updates another table and it is getting through about 90 % of the list of things to process.

I have taken the call to the Sproc out of the Using ( DataAccessAdaptor...){} and made it a using a separate adaptor and it is now working. Any thoughts on why this is needed?

No idea. Would you please the exact non-working real code?

Any thoughts on why this is needed?

Have you checked for blocking in the database?

Here is a copy of the code ...

using (DataAccessAdapter adapter = new DataAccessAdapter()) { InvoiceEntity Invoice = new InvoiceEntity(); Invoice.IsNew = true; Invoice.Locked = 0; VSIMSMasterPage daMasterPage = (VSIMSMasterPage)this.Master; Invoice.YearId = YearID; Invoice.orgId = daMasterPage.CurUserOrg.OrgId; Invoice.InvoiceMonth = month; Invoice.InvoiceType = InvoiceType.District.ToString(); Invoice.Status = InvoiceStatus.New.ToString(); Invoice.CreatedBy = Page.User.Identity.Name; Invoice.ModifiedBy = null; adapter.SaveEntity(Invoice, true);

adapter.CommandTimeOut = 120;
ActionProcedures.InvoiceDataCollection(Invoice.InvoiceId);

}

and no there is no blocking issue within the db ...

I believe the command timeout can not be changed once the connection has been opened.

It gets opened when you do the SaveEntity. Try moving the CommandTimeout to the beginning, or at least before calling any methods on the adapter.

Since it is just a timeout, it shouldn't affect the save at all.

using (DataAccessAdapter adapter = new DataAccessAdapter()) {
    adapter.CommandTimeOut = 120;

    InvoiceEntity Invoice = new InvoiceEntity();
    Invoice.IsNew = true;
    Invoice.Locked = 0;
    VSIMSMasterPage daMasterPage = (VSIMSMasterPage)this.Master;
    Invoice.YearId = YearID;
    Invoice.orgId = daMasterPage.CurUserOrg.OrgId;
    Invoice.InvoiceMonth = month;
    Invoice.InvoiceType = InvoiceType.District.ToString();
    Invoice.Status = InvoiceStatus.New.ToString();
    Invoice.CreatedBy = Page.User.Identity.Name;
    Invoice.ModifiedBy = null;
    adapter.SaveEntity(Invoice, true);

    ActionProcedures.InvoiceDataCollection(Invoice.InvoiceId);
}

yup, thought about that as well and moved the change timeout to the top after the using ... same thing.

Try to keep the connection open as follows.

using (DataAccessAdapter adapter = new DataAccessAdapter(true)) { adapter.CommandTimeOut = 120;

InvoiceEntity Invoice = new InvoiceEntity();
Invoice.IsNew = true;
Invoice.Locked = 0;
VSIMSMasterPage daMasterPage = (VSIMSMasterPage)this.Master;
Invoice.YearId = YearID;
Invoice.orgId = daMasterPage.CurUserOrg.OrgId;
Invoice.InvoiceMonth = month;
Invoice.InvoiceType = InvoiceType.District.ToString();
Invoice.Status = InvoiceStatus.New.ToString();
Invoice.CreatedBy = Page.User.Identity.Name;
Invoice.ModifiedBy = null;
adapter.SaveEntity(Invoice, true);

ActionProcedures.InvoiceDataCollection(Invoice.InvoiceId);

}

nope ... same thing right at 30 seconds the sproc call is stopped.

You have to use the overload of the proc call method which accepts an adapter Otherwise it will create a new one and will of course use the default timeout. So set the timeout and then pass it to the overload:

using (DataAccessAdapter adapter = new DataAccessAdapter()) { adapter.CommandTimeOut = 120;

InvoiceEntity Invoice = new InvoiceEntity();
Invoice.IsNew = true;
Invoice.Locked = 0;
VSIMSMasterPage daMasterPage = (VSIMSMasterPage)this.Master;
Invoice.YearId = YearID;
Invoice.orgId = daMasterPage.CurUserOrg.OrgId;
Invoice.InvoiceMonth = month;
Invoice.InvoiceType = InvoiceType.District.ToString();
Invoice.Status = InvoiceStatus.New.ToString();
Invoice.CreatedBy = Page.User.Identity.Name;
Invoice.ModifiedBy = null;
adapter.SaveEntity(Invoice, true);

ActionProcedures.InvoiceDataCollection(Invoice.InvoiceId**, adapter**);

}

You can set the timeout whenever you like, it's not necessary to set it before the connection is opened, as this timeout is for commands, which are created on the fly. Setting it right after the using statement of course also uses this timeout for the SaveEntity call.

shear genius ... that was it and it makes sense ... I very much appreciate everyone's help.