Great article for fixing pre upgrade related issues: http://sharepointreporter.wordpress.com/2010/07/30/fix-pre-upgrade-check-errors/ One thing to add.  Use the query here to find the name of the pages that contain the offending webparts.  I thought deleting the page would make them go away, but I was wrong.  I had to recover the pages that I deleted from the recycle bin and then open them in web part maintenance view (appending "?contents=1" to the url and then delete the webparts from the page.   http://surfpointtech.com/2012/06/28/how-to-find-a-sharepoint-webpart-name-from-the-id-or-guid/  Here's the STSADM commands: STSADM -o preupgradecheck and this one to find the sites that the webparts live in: stsadm -o enumallwebs -includewebparts > i:tempwebparts.txt Better yet, use the SQL command above to get the actual page that the webpart lives in.  

SELECT DISTINCT D.SiteID, D.WebId, W.FullURL as WebURL, D.Id As DocumentId,                  D.DirName, D.LeafName, tp_ID As WebPartSK  FROM       dbo.Docs D WITH (nolock)   INNER JOIN dbo.Webs W WITH (nolock) ON D.WebID = W.Id  INNER JOIN dbo.WebParts WP WITH (nolock) ON D.Id = WP.tp_PageUrlID  WHERE WP.tp_ListId Is Null AND WP.tp_Type Is Null AND WP.tp_Flags Is Null        AND WP.tp_BaseViewID Is Null AND WP.tp_DisplayName Is Null         AND WP.tp_Version Is Null  AND WP.tp_WebPartTypeId='<your web parts id>'  Source for this query is Ryan's comment her: http://stackoverflow.com/questions/1498409/sharepoint-find-where-webpart-is-in-use    

Ran into some issues after running through the install: http://support.microsoft.com/kb/2293357 Search would still not pick up the content of the pdf, just the title. Had to add this registry key and start a full crawl and it worked: • Using Regedit on the server, navigate to \HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice Server14.0SearchSetupFilters • Right-click the Filters folder and select New Key. Enter “.pdf” for the key value. • Add the following values to this key: Default = Extension = pdf FileTypeBucket = 1 MimeTypes = application/pdf

These are some limits found in the 2007 version of SharePoint, specifically Windows SharePoint Services 3.0.   Site object Guidelines for acceptable performance Notes Scope of impact when performance degrades Site collection 50,000 per content database Total farm throughput degrades as the number of site collections increases. Farm Site collection 150,000 per Web application This limit is theoretical, and is dependent largely upon: Performance of the database server on which the configuration database resides. Performance of the Web servers in the farm. Network bandwidth between the Web servers and the database server. This is not a hard limit, and assumes a single database server. Your environment may not be able to host this many site collections per Web application. Distributing content databases across additional database servers can increase the effective limit of the number of site collections per Web application. You should perform testing to determine the actual effective limit [...]

If you have turned on Audit logging in SharePoint 2007, you will wake up some day with a nasty surprise of a bloated SQL server database.  The data is all being stored in the AuditData table in the content database. Luckily, there is an STSADM command for this, "stsadm -o trimauditlog" After some research, the general consensus is to not truncate the table directly, although no specific reason is ever given except "Not Supported." As I always prefer to use a standard API, I found that you must do this command in very small chunks or else you could lock up your SQL server and effectively crash your SharePoint installation (found out the hard way). I found 800,000 records to take approximately 15 minutes on a 2 Web Front end 1 Index Server, SQL Cluster type SharePoint farm.  To be safe, I wrote a PowerShell script to take care of [...]

Pull users and groups from a SP list that allows multiple users and groups. This is a follow up post from a previous post : http://surfpointtech.com/2011/09/12/how-to-pull-the-email-addresses-from-a-sharepoint-user-field-allow-multiple-users/ When examining a User field on a SharePoint list, you need to see whether the list setting allows for multiple users as well as both Users and Groups. The key to pulling both the groups and the users is to be able to test for a group as opposed to a user object.  In this case, I found that the fieldUser.User object is null for groups, but not for Users.  So, as you iterate through the fieldUser objects in the SPFieldUserValueCollection, you'll find a group when the fieldUser is not null, but the fieldUser.User object is null.  That way, you know you have a SPGroup at that point, and can loop through the users in the group. After that, you do the normal adding [...]

This one was a little hard to track down. How do you write directly to the SharePoint workflow history? It's easy enough to add a LogToHistory activity and set the HistoryDescription and HistoryOutcome, but what if you want to create those entries dynamically? After toying around with different ways of trying this, the answer was pretty easy: Here's the code sample: SPMember usermember = workflowProperties.OriginatorUser; SPWorkflow.CreateHistoryEvent(this.workflowProperties.List.ParentWeb, this.workflowId, 0, usermember, TimeSpan.MinValue, "Corp Legal Reviewed", "Status Change", string.Empty);

To pull the user information, you first have to convert the field into a SPFieldUser object, and then create a collection of the SPFieldUserValueCollection. Then, loop through the collection and pull the Email property of the SPFieldUserValue. code sample: ---------------------------------------------------------------------- string sFieldNameTo = "BU Legal To Email"; string sFieldNameCC = "BU Legal CC Email"; //Add To and CC based on multiple user field if (workflowProperties.Item[sFieldNameTo] != null) { SPFieldUser UsersColumn = (SPFieldUser)workflowProperties.Item.Fields.GetField(sFieldNameTo); SPFieldUserValueCollection Users = (SPFieldUserValueCollection)UsersColumn.GetFieldValue(workflowProperties.Item[sFieldNameTo].ToString()); foreach (SPFieldUserValue fieldUser in Users) { if (fieldUser.User.Email != null && fieldUser.User.Email != string.Empty) { mail.To.Add(fieldUser.User.Email); }// }// }// if (workflowProperties.Item[sFieldNameCC] != null) { SPFieldUser UsersColumn = (SPFieldUser)workflowProperties.Item.Fields.GetField(sFieldNameCC); SPFieldUserValueCollection Users = (SPFieldUserValueCollection)UsersColumn.GetFieldValue(workflowProperties.Item[sFieldNameCC].ToString()); foreach (SPFieldUserValue fieldUser in Users) { if (fieldUser.User.Email != null && fieldUser.User.Email != string.Empty) { mail.CC.Add(fieldUser.User.Email); }// }// }//   Updated 5/11/16 For CSOM use this: foreach (FieldUserValue userValue in item["MultiUser"]as FieldUserValue[]) { }//