Posted by Scott on February 16, 2011
There is a bug in the IIS 7 user interface which prevents setting the idleTimeout property of an application pool when both the time (“Regular Time Interval (minutes)”) property and idleTimeout properties are set to zero.
A quick trip to the command line and the appcmd interface can solve the problem. The following command will set the idleTimeout property to 10 minutes.
appcmd set apppool "Application Pool Name" /processModel.idleTimeout:0.00:10:00
When properly executed, the command will output the following:
APPPOOL object "Application Pool Name" changed
Posted by Scott on September 28, 2010
The title says it all. Get patching. Hit up the security bulletin for downloads.
Reference
Posted by Scott on September 21, 2010
The Microsoft SharePoint team has released specific guidance for a workaround for the recently announced ASP.NET vulnerability (Security Advisory 2416728). With a slight modification, this guidance will also apply to SharePoint 2007.
For SharePoint 2010, the relevant web.config entry will look like:
<customerrors defaultredirect="/_layouts/error2.aspx" mode="On" redirectmode="ResponseRewrite"></customerrors>
While for SharePoint 2007, the web.config entry will read:
<customerrors defaultredirect="/_layouts/error2.aspx" mode="On"></customerrors>
Posted by Scott on August 21, 2009
One of my pain points as a SharePoint “administrator” is having to deal with deployments of solution packages to my environment without the best change management. This means that I often see packages making their way in to the environment without any thought given to keeping the package in case it needs to be reapplied at a later time (Note: I’m not the only one who controls what goes into the environment).
The solution? I whipped up a Windows application so download one, several, or all of the solution packages currently stored in the farm configuration database.
I have posted the application to CodePlex @ http://spsolutiondownloader.codeplex.com/.
The application must be run in the context of a Farm Administrator (i.e. right-click, Run As…) on a server in the farm for which you wish to download the solution package(s) from and requires the .NET Framework 3.5.
I would love some feedback from the community as to whether or not this useful. I have some other little apps in mind I could put together with the proper motivation.
