Command Timeout for SP in Open Access Classic

Thread is closed for posting
2 posts, 0 answers
  1. devoas
    devoas avatar
    71 posts
    Member since:
    Dec 2009

    Posted 25 Nov 2015 Link to this post


     We are using Open Access Classic and having problem that Long running Store procedure throwing Request timeout  messages....In app.config we already set conTimeout = 720 but still after 2 mins it thru Request Timeout Message....

    We are using it in our projects...  and have following setting in app.config 

          <backendconfiguration id="mssqlConfiguration" backend="mssql">

    And while setting Object scope we have following Code: 

            string myconfig =
                     "<openaccess>" +
                     "<references>" +
                     "<reference assemblyname='" + AssemblyName.Trim() + "' />" +
                     "</references>" +
                     "<connections>" +
                         "<connection id='" + ConnectionID + "'>" +
                            "<databasename>" + Database + "</databasename>" +
                            "<servername>" + server + "</servername>" +
                            "<integratedSecurity>false</integratedSecurity>" +
                            "<user>" + UserID + "</user>" +
                            "<password>" + password + "</password>" +
                              "<backendconfigurationname>mssqlConfiguration</backendconfigurationname>" +
                        "</connection>" +
                    "</connections>" +
                XmlDocument xmlDoc = new XmlDocument();

                XmlDocument xmlDoc = new XmlDocument();

                return Telerik.OpenAccess.Database.Get(ConnectionID, xmlDoc.DocumentElement).GetObjectScope();


    Can you pls advise what is missing in this code.







  2. Thomas
    Thomas avatar
    590 posts

    Posted 27 Nov 2015 Link to this post

    To me, the configuration looks correct and you should be able to perform long running SQL when the server does not require locks to be held longer than 20seconds. Please check that this is not causing 
    the issue - even though 20 seconds is quite a long time for a database server to hold a lock.
    In addition you should set the testInterval to 720 too; that would mean we do not wake up so often to check for busy connections.

    Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.
Back to Top