System.Exception. Urgent!!

Posts   
 
    
lss
User
Posts: 25
Joined: 23-Dec-2008
# Posted on: 20-Apr-2009 16:51:48   

Hi,

I got a huge problem. This mornig we got this msg after the application has been working fine. Please help me with this.

System.Exception: Creation of new employee aborted. ---> SD.LLBLGen.Pro.ORMSupportClasses.ORMQueryExecutionException: An exception was caught during the execution of an action query: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.. Check InnerException, QueryExecuted and Parameters of this exception to examine the cause of this exception. at SD.LLBLGen.Pro.ORMSupportClasses.ActionQuery.Execute() at SD.LLBLGen.Pro.ORMSupportClasses.BatchActionQuery.Execute() at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.ExecuteActionQuery(IActionQuery queryToExecute) at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.PersistQueue(ArrayList queueToPersist, Boolean insertActions) at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave, IPredicateExpression updateRestriction, Boolean recurse) at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave) at App2.BLL.EmployeeUtility.CreateNewEmployee(String pmFName, String pmLName, String pmMI, String pmSSN) --- End of inner exception stack trace --- at App2.BLL.EmployeeUtility.CreateNewEmployee(String pmFName, String pmLName, String pmMI, String pmSSN) at App2.BLL.EmployeeUtility.CreateNewEmployee(String pmFName, String pmLName, String pmSSN) at page2.Page_Load(Object sender, EventArgs e)

Thanks

Seth avatar
Seth
User
Posts: 204
Joined: 25-Mar-2006
# Posted on: 20-Apr-2009 21:49:53   

Sounds like a server problem to me...

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 21-Apr-2009 04:27:40   

Timeouts will generally be caused by something in the database that you are trying to modify being locked by another transaction. You could update the CommandTimeout property of the DataAccessAdapter as described here but this is rarely the solution unless you genuinely have a long running query somewhere else which is locking the data.

Do you have any other users/application etc running against the same database - you need to investigate what is causing the lock.

David Elizondo | LLBLGen Support Team