{"id":64,"date":"2018-01-11T09:19:36","date_gmt":"2018-01-11T09:19:36","guid":{"rendered":"http:\/\/4us2use.at\/?p=64"},"modified":"2018-03-09T12:15:41","modified_gmt":"2018-03-09T12:15:41","slug":"timeouts-when-creating-new-service-application-on-sharepoint","status":"publish","type":"post","link":"http:\/\/4us2use.at\/?p=64","title":{"rendered":"Timeouts when creating new service application on SharePoint"},"content":{"rendered":"<p>Problem Description:<\/p>\n<p>Error: &#8220;Timeout Expired. The timeout period elapsed prior to completion of the operation or the<br \/>\nserver is not responding.\u200b&#8221;<\/p>\n<p>This can be caused due too many rows in the SharePoint_Config DB in table dbo.TimerJobHistory<\/p>\n<p>You can check on SQL with the following code:<\/p>\n<p>SELECT CONVERT(bigint, rows)<br \/>\nFROM sysindexes<br \/>\nWHERE id = OBJECT_ID(&#8216;dbo.TimerJobHistory&#8217;)<br \/>\nAND indid &lt; 2<\/p>\n<p>The root problem is a general SP 2013 &#8220;beature&#8221;.<br \/>\nThe job &#8220;Delete Job History&#8221; is scheduled weekly but has a timeout. That causes, that ususally a lower number of entries is purged after a week than new entries created during the week on a large farm.<\/p>\n<p>Resolution:<\/p>\n<p>\u200bSet the job schedule to 1 minute until you reached a lower and stable number of rows.<br \/>\nAfter that change the job to run daily.<\/p>\n<span id=\"post-ratings-64\" class=\"post-ratings\" data-nonce=\"0b1ca6c259\"><img id=\"rating_64_1\" src=\"http:\/\/4us2use.at\/wp-content\/plugins\/wp-postratings\/images\/stars\/rating_off.gif\" alt=\"1 Star\" title=\"1 Star\" onmouseover=\"current_rating(64, 1, '1 Star');\" onmouseout=\"ratings_off(0, 0, 0);\" onclick=\"rate_post();\" onkeypress=\"rate_post();\" style=\"cursor: pointer; border: 0px;\" \/><img id=\"rating_64_2\" src=\"http:\/\/4us2use.at\/wp-content\/plugins\/wp-postratings\/images\/stars\/rating_off.gif\" alt=\"2 Stars\" title=\"2 Stars\" onmouseover=\"current_rating(64, 2, '2 Stars');\" onmouseout=\"ratings_off(0, 0, 0);\" onclick=\"rate_post();\" onkeypress=\"rate_post();\" style=\"cursor: pointer; border: 0px;\" \/><img id=\"rating_64_3\" src=\"http:\/\/4us2use.at\/wp-content\/plugins\/wp-postratings\/images\/stars\/rating_off.gif\" alt=\"3 Stars\" title=\"3 Stars\" onmouseover=\"current_rating(64, 3, '3 Stars');\" onmouseout=\"ratings_off(0, 0, 0);\" onclick=\"rate_post();\" onkeypress=\"rate_post();\" style=\"cursor: pointer; border: 0px;\" \/><img id=\"rating_64_4\" src=\"http:\/\/4us2use.at\/wp-content\/plugins\/wp-postratings\/images\/stars\/rating_off.gif\" alt=\"4 Stars\" title=\"4 Stars\" onmouseover=\"current_rating(64, 4, '4 Stars');\" onmouseout=\"ratings_off(0, 0, 0);\" onclick=\"rate_post();\" onkeypress=\"rate_post();\" style=\"cursor: pointer; border: 0px;\" \/><img id=\"rating_64_5\" src=\"http:\/\/4us2use.at\/wp-content\/plugins\/wp-postratings\/images\/stars\/rating_off.gif\" alt=\"5 Stars\" title=\"5 Stars\" onmouseover=\"current_rating(64, 5, '5 Stars');\" onmouseout=\"ratings_off(0, 0, 0);\" onclick=\"rate_post();\" onkeypress=\"rate_post();\" style=\"cursor: pointer; border: 0px;\" \/> (No Ratings Yet)<br \/><span class=\"post-ratings-text\" id=\"ratings_64_text\"><\/span><\/span><span id=\"post-ratings-64-loading\" class=\"post-ratings-loading\"><img src=\"http:\/\/4us2use.at\/wp-content\/plugins\/wp-postratings\/images\/loading.gif\" width=\"16\" height=\"16\" class=\"post-ratings-image\" \/>Loading...<\/span>\n","protected":false},"excerpt":{"rendered":"<p>Problem Description: Error: &#8220;Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.\u200b&#8221; This can be caused due too many rows in the SharePoint_Config DB in table dbo.TimerJobHistory You can check on SQL with the following code: SELECT CONVERT(bigint, rows) FROM sysindexes WHERE id = OBJECT_ID(&#8216;dbo.TimerJobHistory&#8217;) AND &hellip; <\/p>\n<p class=\"link-more\"><a href=\"http:\/\/4us2use.at\/?p=64\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Timeouts when creating new service application on SharePoint&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[],"_links":{"self":[{"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/posts\/64"}],"collection":[{"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/4us2use.at\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=64"}],"version-history":[{"count":2,"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/posts\/64\/revisions"}],"predecessor-version":[{"id":150,"href":"http:\/\/4us2use.at\/index.php?rest_route=\/wp\/v2\/posts\/64\/revisions\/150"}],"wp:attachment":[{"href":"http:\/\/4us2use.at\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=64"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/4us2use.at\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=64"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/4us2use.at\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=64"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}