Wildcard Inclusion Used to Create Personal Sites Does Not Exist

If you are leveraging Personal Sites in SharePoint 2013 you may run into an error with the non-interactive timer job used to create Personal Sites as a background task.  The timer job calls into the UserProfile Service application to create the Personal Site using the CreatePersonalSite() method, nothing special there.  However, in this method, the…

5

SharePoint 2013 Maintenance Window Notifications

SharePoint 2013 introduced a new class called SPMaintenanceWindow.  SPMaintenanceWindow encapsulates a maintenance window message you can post to end users at the content database level.  The maintenance window message is somewhat limited by the fact that you can not compose your own custom message on the status bar.  The functionality does allow you to do…

16

SharePoint Portal Server 2003 Assembly Types and Corresponding Type Ids

Posting this for reference for folks upgrading SharePoint 2003/2007/2010/2013. Some of these Type Ids may show up as “Unknown Type” in a Missing server file or server configuration issues in a MOSS 2007 PreUpgradeCheck report or in a SharePoint 2010 upgrade log file. Having these IDs in a searchable format on the internet can be…

0

SharePoint 2007 Assembly Types and Corresponding Type Ids

Posting this for reference for folks upgrading SharePoint 2003/2007/2010/2013. Some of these Type Ids may show up as “Unknown Type” in a Missing server file or server configuration issues in a MOSS 2007 PreUpgradeCheck report or in a SharePoint 2010 upgrade log file. Having these IDs in a searchable format on the internet can be…

0

WSS 2003 Assembly Types and Corresponding Type Ids

Posting this for reference for folks upgrading SharePoint 2003/2007/2010/2013.  Some of these Type Ids may show up as “Unknown Type” in a Missing server file or server configuration issues in a MOSS 2007 PreUpgradeCheck report or in a SharePoint 2010 upgrade log file.  Having these IDs in a searchable format on the internet can be…

0

Upgrading SharePoint 2010 to the December 2012 CU or Later

10/9/2013: The August 2013 CU Refresh (7106.5002) and later CUs will no longer flag this issue as an “upgrade blocker” during PSConfig in SharePoint 2010.  It is still HIGLY recommended that you run Test-SPContentDatabase in SharePoint 2010 before upgrading to SharePoint 2013, having a wide list will cause the content database upgrade to fail. The…

0

SharePoint Patch Reference

SharePoint Foundation 2013 Release Version KB Download RTM 15.0.4420.1017 n/a n/a March 2013 CU 15.0.4481.1005 276800 April 2013 CU 15.0.4505.1002 275199 June 2013 CU 15.0.4517.1003 2817346 MS13-067 15.0.TBD 2817315 August 2013 CU 15.0.4535.1003 281751 October 2013 CU 15.0.4551.1001 282567 December 2013 CU 15.0.4551.1508 284996 Service Pack 1 15.0.4569.1000 281743 Service Pack 1 (Refresh) 15.0.4569.1000 288055…

7

Find the Workflow Service URL for a SharePoint 2013 Farm

In case anyone needs to find the registered workflow service address for a SharePoint 2013 farm, here’s a short PowerShell snippet to list the details. [Void][System.Reflection.Assembly]::loadwithpartialname("Microsoft.SharePoint.WorkflowServicesBase") $web = Get-SPSite -Limit 1 -WarningAction SilentlyContinue | Get-SPWeb $wfm = New-Object Microsoft.SharePoint.WorkflowServices.WorkflowServicesManager($web) $wfm | SELECT * or (added on 5/13/2013) $wfProxy = Get-SPWorkflowServiceApplicationProxy $wfProxy.GetWorkflowServiceAddress((Get-SPSite -Limit 1 -WarningAction SilentlyContinue))…

0

PartialChain: A certificate chain could not be built to a trusted root authority.

If you received this error message on a SharePoint 2013 farm, you can use the steps below to resolve the issue:   Obtain the “SharePoint Root Authority” certificate as a physical (.cer) file $rootCert = (Get-SPCertificateAuthority).RootCertificate $rootCert.Export("Cert") | Set-Content C:\SPRootAuthority.cer -Encoding byte Import the “SharePoint Root Authority” certificate to the Trusted Root Certification store on…

1

Set-SPEnterpriseSearchQueryTopology With a Custom Path

If you hit this error message below, it is likely due to your custom index location path having a trailing backslash.  For a custom index path, you need to specify the path as DRIVE:\folder_name and not DRIVE:\folder_name\. Set-SPEnterpriseSearchQueryTopology : Topology activation was aborted because of System.ComponentModel.Win32Exception: The filename, directory name, or volume label syntax is…

1