Archive

Archive for the ‘SharePoint’ Category

SharePoint Page Layouts and Site Templates “The object specified does not belong to a list.”

SharePoint Version: SharePoint 2010, SharePoint 2013

Ever try and update the available page layouts for a site and get the following error:

 

“The object specified does not belong to a list.”

 

The chances are some page layout got deleted or corrupt and is blowing up this page. The following PowerShell will set the site so all page layouts are available and can get you past this issue.

 

<#
Reset site to use all page layouts
#>

param
(
    #required params
    [string]$webName  = $(throw "webName parameter not specified"),
    [string]$resetsubsites  = $(throw "resetsubsites parameter not specified")
)

if (-not (Get-PSSnapin -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue))
{
    Add-PSSnapin Microsoft.SharePoint.PowerShell
}
 
$web = Get-SPWeb $webName;
 
if ([Microsoft.SharePoint.Publishing.PublishingWeb]::IsPublishingWeb($web))
{
    $spPub = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web)
    $spPub.IsAllowingAllPageLayouts # check to see if it is already set
    $spPub.AllowAllPageLayouts($false) #Set it to allow all page layouts
    $spPub.Update()
}
else
{
    Write-Host $webName is not a publishing web.
}
 
$web.Dispose();

Categories: SharePoint Tags: ,

SharePoint 2013 Search – Display Error: The display template has an error…

 

Another silly one… If you are testing search while directly on the server, you may see the following issue:

Display Error: The display template had an error. You can correct it by fixing the template or by changing the display template used in either the Web Part properties or Result Types.

Automation server can’t create object (CoreRender: ~sitecollection/_catalogs/masterpage/Display Templates/Search/Item_CommonItem_Body.js)

SNAGHTML6dcdf049[4]

 

A simple fix is to add the url of the site to the Local Intranet zone or Trusted Sites zone in Internet Explorer.

SNAGHTML6dd2b710

 

From Internet Options, select the Security tab, select Local Intranet zone (or trusted sites zone). Click Sites, and add the site under Advanced.

Categories: SharePoint Tags:

User Profile Service stuck on starting

SharePoint Version: 2013

Build: (DEC CU)

There are many blogs out there dealing with this issue, as it’s not a new issue at all. However, I’m adding it here for my own record as I run in to it more than I would like. For the most part it’s related to permissions and the service will eventually return to stopped mode. However, there are situations where it truly is stuck on Starting.

If you find that the service is stuck on starting after trying various things like restarting the server, and waiting for days on end, then try the following script (replace <SERVERNAME> with the name of the server where the service instance is stuck on):

 

$n = Get-SPServiceInstance –Server <SERVERNAME>| ?{$_.TypeName -eq "User Profile Synchronization Service"}

Stop-SPServiceInstance $n.ID

Once the service instance stops, you can attempt to start it again from the services on server page.

Categories: SharePoint Tags:

SharePoint 2013 Enterprise Search Center as a subsite

August 22, 2013 Leave a comment

Lets say you have a publishing site. and lets say you want to create a search center as a sub site. You might go to Site content page and click New subsite. And then you might look under the Enterprise tab for the enterprise search center template.

 

SNAGHTML65dcfae

It’s not there. 

To get the Enterprise search center template, you need to activate the site collection feature:

SharePoint Server Standard Site Collection features

SNAGHTML65ffca7

Once that’s activated, then you can create an enterprise search center as a subsite.

SNAGHTML6611593

Categories: SharePoint Tags:

Installing and configuring SharePoint 2013

April 10, 2013 Leave a comment

There are many guides on configuring SharePoint manually, automated with PowerShell, and so on.  And here’s another one Smile. This is not a fully detailed blog (easy reading), but rather to have you take pause and get the basics ready before mounting that iso.

Installing SharePoint is one thing, but before you jump straight in, we want to plan for:

  • Service accounts
  • SQL configuration
  • Local server configuration
  • Patch management

If you are doing a production install, then you will want to do full architecture planning for hardware requirements,  capacity planning, load balancing, service continuity, etc. We’ll keep that for another post Winking smile.

 

Getting ready…

I see time and again users jumping straight into SharePoint install by mounding the iso, and clicking Install SharePoint. Even if you are setting up a test or developer environment, it is worth doing right.

Before we get started in mounting the iso, we want get a few things taken care of first. We need a few service accounts, we need to do some SQL configuration, and we need to get our SharePoint server(s) ready.

 

Hardware Requirements

TechNet has a post on hardware requirements that should be reviewed. While these are good minimums, I typically increase their recommended memory allocation by at least 50%.

If you are building out a dev/personal environment, you want to give it 8Gb if you can, and 60-80Gb for OS drive.

For SQL, again if it’s a dev environment, you can get away with 4Gb, but for a production you want to start at 24Gb.

If you are planning to install SQL on the same server as SharePoint then you would need to account for this in your memory allocation.  I would never recommend that you do this, unless it is a very simple kick-the-tires situation.

 

Service Accounts

I have another blog on recommended service accounts for SharePoint, so no need to get into the details here.  To get our installation complete and farm configured we are going to need at least the following:

  • Farm account
  • Install account
  • SQL service account

SQL Configuration

To get our SQL server ready for SharePoint, we need to do the following:

  • Set permissions
  • Set max degree of parallelism
    Setting SQL permissions

SNAGHTML11db222d

    After installing SQL and setting it up using the sql service account, we need to give our SharePoint install account permissions to:
  • Create database
  • manage permissions

    Set Max degree of parallelism

      See this post on setting this property.

     

     

    SNAGHTML2ee89340Configure Firewall

    In order to allow the SharePoint server to connect to SQL, you may need to configure the windows firewall to allow the connection. SQL connections are made over port 1433.

     

    Preparing the SharePoint servers

    So we have our service accounts and SQL server setup, all we need is to prep our SharePoint servers and we are good to go.

    To get our SharePoint servers ready we need to:

    • Set local permissions
    • Install utility software
    • Install prerequisites
      Set local permissions

    Tempting as it might be to just use the domain administrator account to install SharePoint, do not. Now is the time to start getting into the habit of using dedicated functional accounts.

    Give your install account local admin permissions so it can logon and do the SharePoint install.

    Install Utility Software

    This is not a requirement, but there are a few utilities I like to install:

    If you have any other recommendations, please let me know in the comments!

    Installing the prerequisites SNAGHTML10aa4f7d

    SharePoint needs a bunch of installs on the server before we can actually lay down the SharePoint bits. Luckily, the prerequisites installer provided with the SharePoint iso takes care of installing and configuring them all.

    Mount the SharePoint iso and start autoplay. Click Install software prerequisites to get them installed.

     

    SNAGHTML10b444a5Once the prerequisites are installed, we can proceed with SharePoint by clicking Install SharePoint server.

    You will likely have to restart the server after the prerequisites. If you are mounting the iso from another file share, you should make sure that the mount point is re-established so the prerequisite installer can continue. If it cannot find the mount point, it will throw an error on restart. If that happens, simple remount the iso then run the following command from the root folder of the mounted drive:

    prerequisiteinstaller.exe /continue

     

    Install SharePoint Server

    Ok, you made it. You are ready to install SharePoint!!

    Back at the SharePoint 2013 splash, click Install SharePoint Server to get rolling.

    SNAGHTML10d17324

    [Should determine target file location before installing]

    After SharePoint is installed, we are then ready to configure.  When the installer opens the Run Configuration Wizard page,

    Configure SharePoint

     

    SNAGHTML10e4351c

    Rather than use the SharePoint configuration wizard, we will use PowerShell to configure the farm. In the past, I have run a custom script to configure the farm to Central Admin (and then separate scripts to configure services).  There are many blogs out there covering that topics, but I recently discovered  AutoSPInstaller (thanks Jody Finch Smile). I have yet to try it, but it looks promising!

     

      Patch Management

      After getting everything installed and configured, check your windows updates.  At time of writing, the March PU (public update) was available for download.  See TechNet for more details.

    Review

    So, to recap… before getting stuck into your install, you need to:

    • Plan and provision your service accounts
    • Get your servers ready
    • Get SQL ready
    • Install and configure
    • Get your updates on

    Good luck!

    Categories: SharePoint Tags:

    Adding the last modified date on a publishing page

    February 6, 2013 Leave a comment

     

    A comment requirement for corporations is to display the modified date of a publishing page on the actual page itself.  The way we do this is to add a placeholder on the master page that we populate in the page layout.

    To add the field, use the following code:

    <SharePointWebControls:DateTimeField id="pageContentUpdate" FieldName="Modified" runat="server"/>

    I highlighted the field type DateTimeField, because you can actually display the field using the standard FieldValue type as follows:

    <SharePointWebControls:FieldValue id="pageContentUpdate" FieldName="Modified" runat="server"/>

    This worked great, until I realized the time displayed on the page layout was 5 hours behind the actual modified date Disappointed smile.

    Categories: SharePoint Tags:

    SharePoint 2013 Farm setup–and we are off!

    September 16, 2012 Leave a comment

    Applies to: SharePoint Server 2013

    Like many other SharePointies, I’ve decided to setup a lab environment so I can play around with the new features first hand. 

    Lucky, my mate Andrew Connell has an excellent guide on getting setup for a development environment.  This takes you through the process from end-to-end. 

    I already have a Hyper-V environment and a dedicated SQL server, so I could skip stright to installing SharePoint.

    I created a new vm using Windows Server 2012 as the OS.  I still don’t get why MS do not include buttons instead of requiring the mouse to be in specific location of the bottom left/right corner.  The majority of admins remote to their servers, so this is nothing but a pain.  Anyways, enough about that, Microsoft probably spent millions over this very topic, so I’ll just suffer until popular demand forces them to add them in an a service pack Smile.

    Configuration

    My plan is to follow best practices and use an install account and a farm account to get started.  The install account has dbcreator and security admin roles in SQL.

    After successfully running the pre-config and getting all the required roles and bits in place, I ran the installer. All is good so far. Next I get to configure SharePoint 2013.  For 2010, I would skip to using PowerShell at this point, but I want to see what the config wizard does for SharePoint 2013.

    Oh look, you can define your Config database name.  how novel!  I do that, and provide the rest of the configuration values and of I go.

    Configuration Failed

    An exception of type Microsoft.SharePoint.SPException was thrown… This SQL Server instance does not have the required “max degree of parallelism” setting of 1.  Database provisioning operations will continue to fail if “max degree of parallelism” is not set to 1 or the current account does not have permissions to change the setting.

    See my other post on this issue and how to get over it.

    The configuration wizard takes several minutes to run (more than 10 for me).  Yay.  Configuration completed without error.  Lets see what databases it created:

    Configuration database: SP2013_Config

    Admin contnet db: SharePoint_AdminContent_93725166-c75a-4e48-8bae-445bab7ffad7

    Ugh. Again with the GUIDs.  Ok, back to Central Admin. 

    First Question: Do I want to sign up for the customer experience Improvement Program.  No. 

    Second Question: How do you want to configure your SharePoint farm? Wizard or manually?

    Again, I’d normally do this with PowerShell, but I want ot see how te wizard does, so wizard it is.

    SNAGHTML15ee6e01

     

    The following services are configurable using the wizard:

    • Access Services 2010
    • Access Services
    • App Management Service
    • Business Data Connectivity Service
    • Excel Application Service
    • Lotus Notes Connector
    • Machine Translation Service
    • Managed Metadata Service
    • PerformancePoint Service Application
    • PowerPoint Conversion Service Application
    • Search Service Application
    • Secure Store Service
    • State Service
    • Usage and Health Data Collection
    • User Profile Service Application
    • Visio Graphics Service
    • Word Automation Services
    • Work Management Service Application

    I also specify a dedicated services application account.  Though the services wizard only allows you to specify one service account, in a production environment, I would use several.

    Other than Access, BDC, Lotus notes Connector, Machine Translation, PerformancePoint, PowerPoint conversion, and Word Conversion, I am going to have the wizard create the rest.

    I click Next and get this:

    SNAGHTML15f75dfa

    SharePoint 2013 is now working on it and is sorry to keep us waiting. Disappointed smile

    Glad to see the following hasn’t changed from 2010.  My buddy James Sturges crack us every time he sees this.

    SNAGHTML15f94a8a

    It take a while for the wizard to complete.  But you will know it’s working as you watch several database with GUIDs in the name get created.  Lovely.

     

    Eventually, you are asked to create a site collection.  I’m going to go ahead and create one at the root site. I’m going to use the 2013 experience and use the publishing portal template.

    SNAGHTML160df357

     

    After the site collection wizard is complete, I am brought back to Central Admin home page.

    I browse to the new site collection to make sure it’s up…

    SNAGHTML1618c0c3

    Success!!

     

    Ok, that’s it for the Farm configuration.  ‘til the next SharePoint 2013 post…

    Categories: SharePoint

    SQL Server instance does not have the required “max degree of parallelism” setting of 1

    September 16, 2012 2 comments

    Applies to: SharePoint Server 2013

    When setting up a SharePoint 2013 lab, I ran into the following error while running the configuration wizard:

    An exception of type Microsoft.SharePoint.SPException was thrown… This SQL Server instance does not have the required “max degree of parallelism” setting of 1. Database provisioning operations will continue to fail if “max degree of parallelism” is not set to 1 or the current account does not have permissions to change the setting.

    Ok then. So what is “max degree of parallelism” that has SharePoint all bent out of shape? Well, according to Mat Stephen:

    This option sets the maximum number of processors SQL Server can use for one query. If SQL Server has to bring back a lot of data (lots of rows) for a query it sometimes makes sense to break the query down into a number of smaller queries, each query returning a subset of the total rows. This way SQL Server can make use of more than processor and hence on multi processor boxes it can potentially return a lot of rows more quickly, for a given query, than it can on a single processor box.

    The default value of 0 will allow SQL to use all of the processors for parallelism. Setting this value to 1 will basically disable parallel planning, with only one processor being used.

    Ok, so lets’ set it to 1 and get back to business.

    From SQL server management Studio, right click your server in Object Explorer and click Properties. Under the Advanced group modify the property “Max Degree of Parallelism”.

    SNAGHTML15d1d4fc_thumb[1]

    Because the database was already created, I will need to delete and re-create it and run the config wizard again.

    Note: Were I using a highly privileged account (like farm, or domain admin) I would not have come across this error as SharePoint would simply have changed the value for me without me knowing. This is why I follow least privilege practices even in my lab.

    Setting this to 1 got made SharePoint happy and the configuration continued normally.

    Categories: SharePoint

    Maintaining a hybrid licensing model in a single farm

    September 13, 2012 Leave a comment

    Applies to: SharePoint 2010

    When installing SharePoint, one of the first things you have to do is enter a license key.  For most companies this is not even a consideration, it’s either a standard license or an enterprise license. 

    Check out the Microsoft SharePoint 2010 feature matrix to see what enterprise gets you.

    So, what if you want to deploy a hybrid model and have some users on standard and some users on enterprise?  Well it gets tricky.  For large companies this is a situation that is not as uncommon as you might think. 

    Once you active the enterprise license, you cannot revert your farm to a standard license.  With that in mind, how do you maintain both sets of licenses?

    I won’t get into the details of licensing and cost – that’s for you to work out with your Microsoft account manager Smile. I will however touch on how can you govern it technically.

    So how are enterprise features implemented?

    Sites

    A Site collection feature called SharePoint Server Enterprise Site Collection features will enable all the additional features that comes with Enterprise for that site collection.

    SNAGHTML5a2d8bf

    By default this is disabled, unless you chose to have it enabled through Central Admin (Upgrade and Migration > Enable Enterprise Features).

    Service Applications

    Enterprise includes several service applications including excel services, access services, etc.  Web applications that are associated with these services can put them to use. See the feature matrix for all the services that are included.

    So how to make the most of a hybrid deployment and stay in compliance?

    Well this is where it gets tricky.  There are several configurations you can consider, but you also need the support and compliance of your site owners.

    Technical Governance

    Web Applications – To maintain a hybrid license model, you need to do so at the web application level.  Target your features per web application.  i.e. A web application can have standard features or enterprise features.  By doing so you can restrict the service applications available.

    Proxy Groups – Separate your service applications into proxy groups.  do not mix features that are enterprise with standard in the same group.  Apply the proxy groups to the web applications accordingly.

    Site Collections – Do not enable the site collection feature to automatically enable enterprise features.  Enable this only for sites that need it.

    Policy Governance

    Technical governance will only get you so far, users are smart and can often find ways around your limitations. 

    Site Collection Administrators – Consider restricting the SA admins to the IT group.  Educate your admins on licensing and feature enabling.  If you do give over SA admin to your users, ensure they know that if they go outside their license, it may be revoked.  Or if they really need the enterprise features, they provide a case for it.

    And of course there’s always custom solutions to ensure enterprise features are never enabled.

    Brian Edwards has a great article that gets into much more detail.  You should check it out.

    Categories: SharePoint
    Follow

    Get every new post delivered to your Inbox.

    Join 38 other followers