Troubleshooting SharePoint

13 Aug 2016

A few great SharePoint references

by Stacy Simpkins | posted in: PowerShell, SharePoint Administration, SharePoint Development, Troubleshooting | 0

I’m sorry that this week’s blog is just a list of my thoughts on a few really great tools that I had absolutely nothing to do with; but, love to use and am very thankful that these people have written … Read More

21 Feb 2016

Central Admin running with vanity URL and on SSL

by Stacy Simpkins | posted in: Performance, Security, SharePoint Development | 0

Running SharePoint sites on Secure Socket Layer (SSL) is critical to information security and SharePoint Central Administration is no exception. You can configure central admin to run on SSL by creating a CName record in DNS that resolves to your … Read More

15 Jan 2016

Getting Distributed Cache started on SharePoint 2016 Beta 2

by Stacy Simpkins | posted in: PowerShell, SharePoint Administration, SharePoint Development | 0

First of all I’d like to thank mvan for the post located here: http://www.sharepointconsultant.ch/2013/03/07/adding-a-local-sharepoint-2013-development-server-as-a-cache-host-to-appfabrics-cache-cluster/ please read this before continuing, as the following post assumes you’ve read mvan’s issue. The distributed cache would not start During a recent install of SharePoint … Read More

18 Jul 2015

Modify the view of SharePoint Discussion board.

by Stacy Simpkins | posted in: SharePoint Development, Troubleshooting | 1

NOTE: These instructions only apply to SharePoint farms that are Pre July 2014 CU, if you are working with a farm that is Post July 2014 CU please visit ChaddTalks for KT on creating modified view. If your farm … Read More

14 Jun 2015

Change the look of Central Admin

by Stacy Simpkins | posted in: SharePoint Development | 0

You can change the look of Central admin using one of the OOB themes by navigating to the Change the Look page that is normally under Look and Feel on the settings page (_layouts/Settings.aspx). There is one exception though, that … Read More

1 Nov 2014

HNSC is recommended best practice

by Stacy Simpkins | posted in: SharePoint Administration, SharePoint Development | 0

Straight from Microsoft – USE HOST NAMED SITE COLLECTIONS – recommended in SharePoint 2010 and preferred in SharePoint 2013 Main reason: Uses less resources, only uses one web application pool. Allows a seemingly unlimited number of vanity named site collections … Read More

4 Oct 2014

SPCommon.png image tattoo on my page – get it off

by Stacy Simpkins | posted in: SharePoint Development | 0

If you ever run into an issue where your site is showing the spcommon.png, as shown here: Follow these steps to remove it: Open the page in IE Press f12 click the image to see it larger Select the … Read More

31 May 2014

Creating Host Named Site Collections

by Stacy Simpkins | posted in: PowerShell, SharePoint Administration, SharePoint Development | 0

The following is based on the Exam Ref 70-331: Core Solutions of Microsoft SharePoint Server 2013 by Troy Lanphier. Check out Kirk Evan’s blog for more background behind HNSC – http://blogs.msdn.com/b/kaevans/archive/2012/03/27/what-every-sharepoint-admin-needs-to-know-about-host-named-site-collections.aspx

#Build a web application and place an empty site collection in it, a site collection with no site, e.g. pick site later or create with powershell as follows:

$applicationPool = "SharePoint - 443"

$ServiceAcct = "domain\content" #Account normally used when creating a web app via guie, atin

$svcacctmail = "content@domain"

$WebApp = "SharePoint HNSC Web Application"

$webAppURL = "https://ws2013app/"

$contentDB = "WSS_Content_TopSiteEmpty"

#If creating for SharePoint 2013, sent the claims authentication provider by calling the new-spauthenticationprovider cmdlet into a variable as: $Provider = New-spauthenticationprovider

#Create the example web application, as mentioned above, either with gui, and pick later, or

New-SPWebApplication -ApplicationPool $applicationPool -ApplicationPoolAccount $serviceAcct -Name $WebApp -Port 443 -databaseName $contentDB -securesocketslayer

#If doing for 2013

New-SPWebApplication -ApplicationPool $applicationPool -ApplicationPoolAccount $serviceAcct -Name $WebApp -Port 443 -AuthenticationProvider (New-SPAuthenticationProvider) -databaseName $contentDB -secureSocketsLayer

#If you get a pound sand message on first attempt to load the SP 2013 site, navigate to the settings page under <URL>/_layouts/15/settings.aspx and deactivate MDS

#Now that the web app is there, build the empty site collection

$primarySiteCollectionOwnerAcct = "domain\someName"

$PrimarySCOwnerEmail = "webcontent@domain"

New-SPSite -URL $webAppURL -OwnerAlias $primarySiteCollectionOwnerAcct -OwnerEmail $PrimarySCOwnerEmail

#Build some content databases

new-SPContentDatabase -Name $HNSC1DB -WebApplication $WebApp -WarningSiteCount 0 -MaxSiteCount 1

#Now build some HNSC's

$HNSC1Name = "Hockeytown Usa"

$HNSC1URL = "https://hockeytown.domain.com"

$HNSC1DB = "WSS_Content_HockeyTown"

New-SPSite -url $HNSC1URL -HostHeaderWebApplication $webAppURL -Name $HNSC1Name -ownerAlias $PrimarySiteCollectionOwnerAcct -owneremail $PrimarySCOwnerEmail -contentDatabase $HNSC1DB

$HNSC2Name = "Baseball city"

$HNSC2URL = "https://baseball.domain.com"

$HNSC2DB = "WSS_Content_HaveYouSeenMyBaseball"

New-SPSite -url $HNSC2URL -HostHeaderWebApplication $webAppURL -Name $HNSC2Name -ownerAlias $PrimarySiteCollectionOwnerAcct -owneremail $PrimarySCOwnerEmail -contentDatabase $HNSC2DB

#Build a web application and place an empty site collection in it, a site collection with no site, e.g. pick site later or create with powershell as follows:

$applicationPool = "SharePoint - 443"

$ServiceAcct = "domain\content" #Account normally used when creating a web app via guie, atin

$svcacctmail = "content@domain"

$WebApp = "SharePoint HNSC Web Application"

$webAppURL = "https://ws2013app/"

$contentDB = "WSS_Content_TopSiteEmpty"

#If creating for SharePoint 2013, sent the claims authentication provider by calling the new-spauthenticationprovider cmdlet into a variable as: $Provider = New-spauthenticationprovider

#Create the example web application, as mentioned above, either with gui, and pick later, or

New-SPWebApplication -ApplicationPool $applicationPool -ApplicationPoolAccount $serviceAcct -Name $WebApp -Port 443 -databaseName $contentDB -securesocketslayer

#If doing for 2013

New-SPWebApplication -ApplicationPool $applicationPool -ApplicationPoolAccount $serviceAcct -Name $WebApp -Port 443 -AuthenticationProvider (New-SPAuthenticationProvider) -databaseName $contentDB -secureSocketsLayer

#If you get a pound sand message on first attempt to load the SP 2013 site, navigate to the settings page under <URL>/_layouts/15/settings.aspx and deactivate MDS

#Now that the web app is there, build the empty site collection

$primarySiteCollectionOwnerAcct = "domain\someName"

$PrimarySCOwnerEmail = "webcontent@domain"

New-SPSite -URL $webAppURL -OwnerAlias $primarySiteCollectionOwnerAcct -OwnerEmail $PrimarySCOwnerEmail

#Build some content databases

new-SPContentDatabase -Name $HNSC1DB -WebApplication $WebApp -WarningSiteCount 0 -MaxSiteCount 1

#Now build some HNSC's

$HNSC1Name = "Hockeytown Usa"

$HNSC1URL = "https://hockeytown.domain.com"

$HNSC1DB = "WSS_Content_HockeyTown"

New-SPSite -url $HNSC1URL -HostHeaderWebApplication $webAppURL -Name $HNSC1Name -ownerAlias $PrimarySiteCollectionOwnerAcct -owneremail $PrimarySCOwnerEmail -contentDatabase $HNSC1DB

$HNSC2Name = "Baseball city"

$HNSC2URL = "https://baseball.domain.com"

$HNSC2DB = "WSS_Content_HaveYouSeenMyBaseball"

New-SPSite -url $HNSC2URL -HostHeaderWebApplication $webAppURL -Name $HNSC2Name -ownerAlias $PrimarySiteCollectionOwnerAcct -owneremail $PrimarySCOwnerEmail -contentDatabase $HNSC2DB

29 Mar 2014

Sometimes you have to be forceful

by Stacy Simpkins | posted in: PowerShell, SharePoint Development | 0

When a solution was not correctly removed from a farm, features will be left behind, because they were not deactivated and removed. In cases, where those features are not being altered, it is possible to re-deploy a solution using -force. … Read More

26 Oct 2013

A few Random development tricks – slighted trickery

by Stacy Simpkins | posted in: SharePoint Development | 0

CSS to block quicklaunch etc.

<style>
.ms-quicklaunch
{
display:none;
}
.ms-navframe
{
display: none;
}
.ms-globalTitleArea {
display: none;
}
</style>

<style>

.ms-quicklaunch

{

display:none;

}

.ms-navframe

{

display: none;

}

.ms-globalTitleArea {

display: none;

}

</style>

The following code is for a sharepoint redirect, just add it to a content editor web part

<meta http-equiv="refresh" content="10;url=http://MYSERVERNAME.com/Pages/default.aspx">

1	<meta http-equiv="refresh" content="10;url=http://MYSERVERNAME.com/Pages/default.aspx">

This code, below, taken from http://pathtosharepoint.com will ADD the quicklaunch using a CEWP

<!-- Load and display Quick Launch - iframe version -->
<!-- Questions and comments: Christophe@PathToSharePoint.com -->
<!-- Paste the URL of the source page below: -->

< iframe id="SourcePage" style="display:none;" src="http://[YourSite]/default.aspx" onload="DisplayQuickLaunch()"></iframe>
<script type="text/javascript">
function DisplayQuickLaunch()
{
var placeholder = document.getElementById("LeftNavigationAreaCell");
var quicklaunchmenu = null;
var SourcePage = document.getElementById("SourcePage");
try {
if(SourcePage.contentDocument)
// Firefox, Opera

{quicklaunchmenu = SourcePage.contentDocument.getElementById("LeftNavigationAreaCell") ;}
else if(SourcePage.contentWindow)
// Internet Explorer
{quicklaunchmenu = SourcePage.contentWindow.document.getElementById("LeftNavigationAreaCell") ;}
else if(SourcePage.document)
// Others?
{quicklaunchmenu = SourcePage.document.getElementById("LeftNavigationAreaCell") ;}
}
catch(err) { alert ("Loading failed");}
var allDescendants = quicklaunchmenu.getElementsByTagName("*");
for (i=0;i<allDescendants.length;i++) {
allDescendants[i].removeAttribute("id");
allDescendants[i].removeAttribute("onclick");
allDescendants[i].removeAttribute("onfocus");
allDescendants[i].removeAttribute("onmouseover");
}
placeholder.innerHTML = quicklaunchmenu.innerHTML;
}
</script>

< iframe id="SourcePage" style="display:none;" src="http://[YourSite]/default.aspx" onload="DisplayQuickLaunch()"></iframe>

function DisplayQuickLaunch()

{

var placeholder = document.getElementById("LeftNavigationAreaCell");

var quicklaunchmenu = null;

var SourcePage = document.getElementById("SourcePage");

try {

if(SourcePage.contentDocument)

// Firefox, Opera

{quicklaunchmenu = SourcePage.contentDocument.getElementById("LeftNavigationAreaCell") ;}

else if(SourcePage.contentWindow)

// Internet Explorer

{quicklaunchmenu = SourcePage.contentWindow.document.getElementById("LeftNavigationAreaCell") ;}

else if(SourcePage.document)

// Others?

{quicklaunchmenu = SourcePage.document.getElementById("LeftNavigationAreaCell") ;}

}

catch(err) { alert ("Loading failed");}

var allDescendants = quicklaunchmenu.getElementsByTagName("*");

for (i=0;i<allDescendants.length;i++) {

allDescendants[i].removeAttribute("id");

allDescendants[i].removeAttribute("onclick");

allDescendants[i].removeAttribute("onfocus");

allDescendants[i].removeAttribute("onmouseover");

}

placeholder.innerHTML = quicklaunchmenu.innerHTML;

}

</script>

5 Oct 2013

An error has occurred after removal of an extended zone

by Stacy Simpkins | posted in: SharePoint Development, Troubleshooting | 0

Let’s say you’ve applied the advice from unextending an extended zone and are now either getting a blank page after re-using the the vanity url or you’re receiving a message that “Something has went wrong” or “An error has occurred”. You ran

Get-SPWebApplication http://sitename.com | Remove-SPWebApplication http://sitename.com -Zone "Intranet"

1	Get-SPWebApplication http://sitename.com \| Remove-SPWebApplication http://sitename.com -Zone "Intranet"

22 Sep 2013

Enable and Use Developer Dashboard to see how your page loads and view metrics.

by Stacy Simpkins | posted in: PowerShell, SharePoint Administration, SharePoint Development | 0

Pre-requisites: Site-collection administrator Follow these steps, or ask your admin, to enable the developer dashboard in on demand mode: (green-can use your own values, red-controls outcome, black-don’t change it) 1. Open the SharePoint Management Shell as an admin Type … Read More

3 Aug 2013

Exporting and Importing – Cannot import site due to wrong template

by Stacy Simpkins | posted in: SharePoint Administration, SharePoint Development | 0

When you’re migrating sites using export-spweb and import-spweb, you might receive an error message on the import, when reviewing the import log, and in your shell, similar to this: FatalError: Cannot import site. The exported site is based on the template … Read More

23 Jun 2013

SharePoint Virtual Labs and SP 2010 vs 2013

by Stacy Simpkins | posted in: SharePoint Development, Troubleshooting | 0

Sorry to be blogurgitating this week. Here’s a really good technet site with a load of virtual labs: SharePoint Server 2010 Introduction to SharePoint Server 2010 Upgrade Developing KPIs and Scorecards with PerformancePoint Services Web Content Management Visual Upgrade Advanced … Read More