Info Archive

What an ordeal. After numerous errors and features that were not installed on the new server I finally get to a point where I believe I can import a site (our intranet) to the development server I have set up.

But , you noticed i said believe .. Another error. This one stating “Error: Cannot import site. The exported site is based on the template SPS#0 but the destination site is based on the template STS#1. You can import sites only into sites that are based on same template as the exported site.”

Well Crap, I vaguely remember running into this in the past and couldn’t for the life of me remember how I fixed it (I had slept since then).

I knew that I didn’t pick the right Site Template (in this case I picked Blank Site) and a quick search confirmed that STS#1 was a Team Site, and SPS#0 was a Sharepoint Server Portal Site but I couldn’t find “Sharepoint Server Portal Site” in my list of Templates to install. Well that is because the Template is obsolete… Great … thank you MS. But don’t fret, although it is obsolete you can still install it, just not with the GUI.

To create a site with Template SPS#0 Do this…

Create a Powershell Script with the following code and run it:

[Code]

Get-SPWebTemplate
$template = Get-SPWebTemplate “SPS#0”
New-SPSite -Url “YourSiteUrl” -OwnerAlias “Domain\UserNameAccount” -Template $template

[\Code]

There you go.

 

Be the first to comment

Sharepoint 2010 user AD Permissions not updating

Posted April 23, 2012 By Kevin Bennett

Needed to add a new user “immediately” to have access to a site. No it was needed immediately, but lack of planning on someone’s part made it appear to be immediate. So I added to the AD group and went home.

…. 15 minutes later I get a call that they still can’t access the site, so double checked that I put the user in the correct AD group. Well I did but when I went to permissions for the site and tested the user permission it didn’t show up.

So a quick search revealed that when using Claims based Authentication there is a default property setting called token-timeout and it is set for 1440 minutes (24 hours)

To View and change this do the following:

stsadm -o getproperty -propertyname token-timeout

This will get your default setting

stsadm -o setproperty -propertyname token-timeout -propertyvalue

I ran this on my app server

 

Be the first to comment

New Site

Posted January 13, 2012 By Kevin Bennett

So this is my new blog, I plan on using this to post crap about sharepoint and the headaches (solutions) I find in my daily workings to run, fix, or improve it. I am in no way a Sharepoint Expert, I am just a .33 FTE Admin for a site and company.

I will do my best to be correct and use proper terminology, but feel free to leave CONSTRUCTIVE Criticisim as you see fit.

Mainly I am tired of having to look up fixes or hacks over and over and over again because I don’t log them down in a place I can get to after I leave the job. This does make me better at googling but takes time out of my other .66 FTE time

Be the first to comment