We recently had a VERY strange issue with a client. This specifically was a disaster restore where the previous environment was poorly documented. Due to a total hardware failure new hardware was provisioned… and that’s where the fun begins.
We were able to get SharePoint installed and get Reporting Services fully configured in integrated mode but when we went to configure the SSP… nothing. Always stuck in provisioning.
As we drilled down into the issue we realized that NO timer jobs were working. Another symptom that we noticed is that the Timer Job status page was completely blank… no status could be reported on any timer jobs. Continue reading →
Office 2010 includes a new capability that gives users the power to create new or customize existing ribbon tabs and groups. Office 2007 included the ability to customize the quick access toolbar which we will also customize in this article so if you’re still stuck with Office 2007 for the next few months then you won’t be left out. Let’s take a look.
My custom tab ended up looking like the following
Let’s break it down group by group… Continue reading →
This has been around for a while but since I still get questions about it from clients I figured I would post an explanation that may be a little more visual that other explanations.
When you start customizing security on your SharePoint sites by breaking inheritance at different levels you may start to see your nice clean permission lists be infiltrated by “Limited Access”. MSDN explains the “Limited Access” permission level as:
Allows access to shared resources in the Web site so users can access an item within the site. Designed to be combined with fine-grained permissions to give users access to a specific list, document library, item, or document, without giving users access to the entire site. Cannot be customized or deleted.
Let’s look at a scenario: Continue reading →
Todd Carter over at todd-carter.com has posted his very in-depth findings regarding a pretty significant memory leak in SharePoint 2007. The problem lies around the HttpApplication object and ultimately around the SPHttpApplication object.
For each HttpApplication which is leaked a potential huge number of child references are too rooted and therefore leaked.
The memory leak has proven to be pretty significant for certain clients as you can see below…
After having the customer install the fix I have described here the process which would normally grow to 10 GB an hour and recycle never went above 2.5 GB! And even after taking all servers out of the load balancer and running the entire farm off one WFE the memory never went above 3.3 GB!!
To learn more read the whole post at Todd’s blog.
I always seem to leave out a step when configuring anonymous access for a SharePoint site so I’ve finally put together a full guide so I don’t leave out any steps in the future.
Deactivate Hidden Features
If you are getting “Access Denied” for lists and libraries then you probably for got this step. There is a hidden feature that secures the lists and libraries by default for all sites that have anonymous access enabled. If you have already enabled anonymous access prior to deactivating this feature then you will need to turn all anonymous access off and back on to refresh this functionality.
- For each site collection that requires anonymous access execute the following stsadm command.
stsadm -o deactivatefeature -url http://sitecollection -name ViewFormPagesLockDown
Continue reading →
While the MSDN article gives most of the properties that you can use when configuring your list definition it does miss a few. I’ve documented the missing properties that I’ve found below:
||Optional Boolean. TRUE to require documents to be checked out before they can be edited.
||Optional Boolean. TRUE to automatically send emails to the user when an item is assigned to them.
||Optional Integer. Specifies the number of major versions to retain when versioning is enabled.
||Optional Integer. Specifies the number of draft versions to retain for each major version when versioning is enabled.