Posts

Showing posts with the label SharePoint 2010

SharePoint Event Receiver Manager (2007 & 2010)

Image
*** UPDATE 12/31/2017: This Project Was Migrated From CodePlex to GitHub *** A while back I started looking for a better way to manage event receivers on my SharePoint servers and one thing lead to another until it became my pet project outside of the office. Before I started writing code I found a few things here and there but none of them were particularly polished and they left me wanting more. I started a project, SharePoint Event Receiver Manager (2007 & 2010) , to continue evolving my tool and I've been gradually adding to it ever since. I invite you, if you have trouble getting a handle on your event receivers, to give it a try and pass it along. Releases: Version 2 (Stable) [Released: Nov 28 2011] SharePoint 2007 & 2010 Version 1 (Stable) [Released: Mar 28 2011] SharePoint 2007 & 2010 [Legacy] Update: This tool is now fully host...

Stuck in the Past! SharePoint Alerts Pointing to An Old URL After Migration?

I've run into this personally a couple of times and never really documented my own solution so that I had it for myself to reuse. If the URL for your SharePoint Farm ever changes, you're more than likely to start hearing from your users that the alert subscription emails they get still point to the old Farm URL. I've encountered this on SP 2007 and SP 2010 Farms. As it turns out, each Alert Subscription contains a hard-coded server root URL which is used when the alert email is generated to construct links. I wrote the PowerShell script below to loop through all Web Applications of the server and perform an update on all Alert Subscriptions. I like my scripts that need to be run on all sites to run through my whole farm rather than one site at a time. This script works on both SP 2007 and SP 2010. It will skip the Central Admin Web Application, your SSP, and MySite sites. $oldrooturl = "https://<url>" [System.Reflection.Assembly]::LoadWithPartialName(...

SharePoint Closed WebParts Slowing You Down? Migrating from SharePoint 2007 to 2010 and Can't Find an Easy Way to Resolve (preupgradecheck) Findings? PowerShell's Got Your Back!

Performance is a concern of every system administrator, unless you're an Information Assurance kind of guy and then you'd probably just assume see the server switched off (just a bit of a nudge). If SharePoint is your poison, watch out for Closed WebParts throughout your site. Closed WebParts are still attached to your page and are temporarily hidden, but they still load when the page loads. If there are a number of them, or any with Fatal Errors, you're unnecessarily impacting page load times and probably filling your logs with errors that are difficult to track down. Worse yet, if you plan a migration from SharePoint 2007 to 2010 and run the preupgradecheck STSADM command, you'll find yourself with a list of potential upgrade problems and no clear path to resolve them. The handy PowerShell script below can help with both. It will iterate through all of the web applications on your server and the pages at the root of each site (it doesn't look at pages in libr...

One or more field types are not installed properly. Go to List settings page to delete these fields. After Upgrading A SharePoint Site Collection From 2007 to 2010

SharePoint is a fickle beast, and moving from SharePoint 2007 to SharePoint 2010 has the potential to produce the expected problems. I recently moved a SharePoint 2007 site collection to SharePoint 2010 by importing the 2007 database on the 2010 farm. I was stumped for a bit on an error that was unspecific and didn't really tell me what the problem was: "One or more field types are not installed properly. Go to List settings page to delete these fields." This error was impacting the Pages library and popped up when any page in that library was loaded. No reference to a specific field type appeared in the actual error (even with custom errors disabled) and there was no reference to the specific field in the ULS logs. I went as far as to look at the exception site in code using .NET Reflector. Finally, I ran across the article below that directly identified the issue. The problem originated from one of the hidden lists in SharePoint that is used for the Publishing Inf...