This error kept our team occupied for some time before finding a solution.
A custom application on SharePoint copies some documents form one library to another after a button is pushed on a form button. When the button is pushed the application behaves as expected and the files are copied. For some reason now, the operation fails if the number of files being copied is quite a lot.
We were originally thinking about a timeout issue, an upload limit issue or the antivirus software interfering. After investigating all of these cases, we were unable to find a solution. A lot of research and some days later, we went back in to the problem before calling PSS and I found the solution on a blog post
You need to define the executionTimeout parameter in the web.config file of the web application where the custom application is running. This parameter is not there by default. From what I have read out there, it seems that if this parameter is not defined, then a default value is assumed of 110 seconds
<httpRuntime executionTimeout=“200“ maxRequestLength=“51200“/>
Source for execution timeout:
for my first day at work, I want to start of by wishing you all a Happy 2010.
May all your wishes come true and of course may you all enjoy the new and fun stuff in SharePoint 2010.
For myself, 2009 has been a great year with a lot of changes:
– I quit my job at BT to become a freelance IT Consultant, which was quite a big change
– I became a licenced firefighter next to my paramedics licence at the local fire department in my home town?
– I had the luck of being asked by Microsoft to do a mini project for them again, which is always a great learning experience [:D]
I hope I can continue to bring some great content to this blog this year.
It is with deepest regret that we have to announce the death of Patrick Tisseghem, co-founder of U2U. Patrick suddenly passed away on Wednesday 3 September 2008 around 18 hours in Gothenburg Sweden due to a heart failure. Our sympathy and thoughts go out to his wife Linda, their daughters Anahi and Laura, and to his family. We are all deeply saddened by this tragic loss. We remember him as caring father as well as a driven and warm hearted colleague and friend. We miss you Patrick.
Just wanted you all to know that I will be trading in my position at for a position at
As of July 16th 2008, i will no longer be be working at Siemens IT solutions and Services, where I have enjoyed working for the last 7 years. I will start a new challenge at BT in Diegem, Belgium as a Technology Lead Consultant for Microsoft products, such as Sharepoint, OCS and Exchange.
I am very eager to start and can’t wait until half of July.
This change does not mean the end of this blog, on the contrary.
So stay tuned for more news soon,.
I was recently asked to investigate an issue with importing an Excel sheet into a new SharePoint List. After trying to duplicate the problem on my lab environment I got a different error caused by my Excel 2007. After searching the web for a solution, I came across a blog post, describing the issue and giving a valid solution. The solution works and I advise you to use it when you encounter the problem J
For your convenience, I will copy the complete article in this post (you never know when blogs disappear rightJ )
Have you tried importing a Excel 2007 spreadsheet into SharePoint Service v3 and are getting a Method Post Error? Thanks to an open SharePoint forum, someone posted the fix.
I take no credit for this fix. My SharePoint hosting company is www.frontpages-web-hosting.com and on their forum is a post by Bradley Elder (Thanks Bradley!) I was able to easily apply the change mentioned in his post and can now import a spreadsheet from Excel 2007 to SharePoint Services v3.
Here is his post below:
Importing lists from Excel 2007 returns a Method ‘Post’ of object ‘IOWSPostData’ failed dialog. Again, not really a problem with WSS 3.0 but rather the result of a failed Application.SharePointVersion() call in the Excel Add-In which results in Excel attempting to use the IOWSPostData.Post() method to publish the Excel range which is used with SharePoint Team Services 1.0. By forcing the version lookup result variable to 2 or greater, Excel will use SOAP to communicate with WSS 3.0 and the publish request will be successful. To make this change, open the Excel Add-In EXPTOOWS.XLA locate in C:\Program Files\Microsoft Office\Office12\1033 by default. Press Alt+F11 to display the Visual Basic code editor and search (Ctrl+F) for the line lVer = Application.SharePointVersion(URL). Comment out that line with a single quote and add the line lVer=2 so your Intialize() method should now look like this:
Sub Initialize(List, Title, URL, QuickLaunch)
strQuickLaunch = QuickLaunch
aTarget(iPublishURL) = URL
aTarget(iPublishListName) = List
aTarget(iPublishListDesc) = Title
‘lVer = Application.SharePointVersion(URL)
lVer = 2
Andrea Kalli Virtual Trainer and Assistant, LLC