Simple but I almost always have to go back and “remember” after a month or two of not working with Powershell.
To run a Powershell script don’t forget to put .\ in front of your script name if you are running it from the directory it is located at. For example:
[code] .\CopyContent.ps1[/code]
Let me just say, if you are not using ULViewer or don’t have it in your toolkit .. you should.
What it does: You know that cryptic error message you get in sharepoint .. come on, you know ..the Correlation ID: alksdlkjf-234l3245-0sllksdf-234234. Yeah that awesome error that tells you exactly what is wrong (not)! Well the ULViewer will shed some light on what is happening on your site when that error is generated.
So jump over to your Web Front End server and fire up ULViewer. Select File, Open, ULS Logs. Now Bring up the browser and reproduce that error. Jump back to ULViewer and press pause. Scroll up and look for the event code. You see it … now read the details.
I have found that 4 out of 5 times (that’s the tv version of math, not the scientific) that it will actually tell you what is wrong, either a missing file, missing feature .. etc.
Now use it .. and use it often.
Here is a simple PowerShell Command to list all databases used in SharePoint
[code]Get-SPDatabase | Sort-Object disksizerequired -desc | Format-Table Name | out-file c:\databases.txt[/code]
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.
As I believe I stated in earlier posts, I am border line OCD. Myself I blame this on the 14 years in the military with all the inspections. So now in my civilian career I am constantly fighting with systems that I inheriting which do not conform to my (not always correct) rank and file structure.
Lately I have spent a lot of time trying to get our SharePoint Environment up to my standard since I have worked off most of the little issues. My most recent endeavor was getting the Web Applications to at least look similar and meaningful. By default SharePoint will name a web application “SharePoint – (Port Number)” and our systems had many of these. And worse it allows the creator to make changes so we had “SP – 80 – internal”, “SharePoint – 565682325”, and even a “Test” which turned out to be our Intranet Web Application.
Disclaimer – Now I take absolutely no credit in the below code but like everything else on this site I wanted to log in down so I don’t have to go somewhere else to find it. If you were the one that originally posted this Thank you thank you thank you thank you .. and my OCD thanks you as well.
Below is the PowerShell code to change the Web Application name
[code]
$a=Get-SPWebApplication | where {$_.Name -match “CurrentName”}
$a.Name
$a.Name=”NewName”
$a.Update()
Get-SPWebApplication | where {$_.Name -match “NewName”}
[/code]
To use:
Now maybe I can sleep better at night knowing my IIS looks organized!