STSADM -o backup -directory: Error Cannot open backup device Operating system error 5 (error not found)
By peter.stilgoe
STSADM -o backup -directory: Error Cannot open backup device Operating system error 5 (error not found)
Ensure the SQL service account is a domain account and it has permissions to
the Shared folder.
Also ensure the account used to execute the backup command has the correct rights on the DB’s as per MS recommendations ie. Owner, creator etc.
More From pstilgoe
Sharepoint 2010: 2 service application databases with the same name showing in Central Admin –> Manage Databases Upgrade Status
By peter.stilgoe
I had a strange problem where if I went into:
Central Admin –> Manage Databases Upgrade Status
in Sharepoint 2010 I had 2 Business Data Connectivity Service databases with the same name! The status of the one in use was ‘No action required’ & the rogue one had ‘Database is too old and upgrade is required’
There was only one database showing on the SQL server, the one in use, if you find you get 2 service application databases with the same name (somehow!?) the command to delete it is:
Stsadm -o deleteconfigurationobject -id b9b3e713-9e53-42ab-a634-a2c54e90a0d6
(replace the guid with the rogue database guid)
More From pstilgoe
How to delete a corrupted Sharepoint list
By peter.stilgoe
Sometime you will find you have a currupted list that you cant delete through the normal way as when you try & access the list or the list settings the webpage throws errors. In this case use STSADM
stsadm.exe -o forcedeletelist -url http://devapp01/Lists/<MyListName>/
More From pstilgoe
Sharepoint 2010: How to get the people picker to work across domains in one way trust
By peter.stilgoe
If you have your Sharepoint farm hosted in a different domain to your users you will notice that the people picker only looks at its local domain, ie does not list any users from the Internal / User domain. Luckily you can get round this fairly easily:
Run this command on all Sharepoint servers in your farm:
stsadm -o setapppassword -password <AnyPasswordYouWant>
Then run this commmand for each web app:
stsadm.exe -o setproperty -url <YourWebApp> -pn "peoplepicker-searchadforests" -pv "domain:<YourDomain>,<Domain Account>,<password>"
You should now be good to go & pull people & resolve names from both domains.
Sharepoint 2010 – Cannot delete service application from Central Admin
By peter.stilgoe
When trying to delete a service application in Sharepoint 2010 from the central admin, sometimes you will find it just stays on the ‘processing’ window for hours (if you wait that long).
If it does you can try & delete the service application using Powershell:
Remove-SPServiceApplication
If that command doesnt work you can force the deletion by using STSADM:
STSADM -o deleteconfigurationobject -id {ID}
The above STSADM command is not documented by Microsoft (or doesnt seem to be)
How to stop the !New tag/indicator from appearing when you add items or documents to your sharepoint site
By peter.stilgoe
When you add a new entry to announcements, to events, or to links on a Microsoft SharePoint Team Services and Windows SharePoint Services Web site, the new entry always includes a tag that is made up of the exclamation point character (!) and the word “new” (!New). This article describes how to stop the !New tag from appearing when you create a new entry.
Windows SharePoint Services 3.0 Web site (inc. MOSS 2007)
To stop the !New tag from appearing next to new entries on a Windows SharePoint Services 3.0 Web site, use the Stsadm.exe tool to change the “Days to Show New Icon” property to zero.
To do this, follow these steps:
Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
Type the following commands, and then press ENTER after each command:
cd /d %programfiles%\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
stsadm.exe -o setproperty -pn days-to-show-new-icon -pv 0 -url [Your Virtual Server's URL]
More From pstilgoe
STSADM restore errors with “No content databases are available for this operation”
By peter.stilgoe
The problem is probably that the GUID of the new site youre trying to restore is the same as an existing site in the content database. Either delete the existing site or I would imagine you could restore to a diffrent content database although I havnt verified this.
More From pstilgoe
STSADM Template references
By peter.stilgoe
GLOBAL#0 = Global template
STS#0 = Team Site
STS#1 = Blank Site
STS#2 = Document Workspace
MPS#0 = Basic Meeting Workspace
MPS#1 = Blank Meeting Workspace
MPS#2 = Decision Meeting Workspace
MPS#3 = Social Meeting Workspace
MPS#4 = Multipage Meeting Workspace
CENTRALADMIN#0 = Central Admin Site
WIKI#0 = Wiki Site
BLOG#0 = Blog
BDR#0 = Document Center
OFFILE#0 = Records Center
OFFILE#1 = Records Center
OSRV#0 = Shared Services Administration Site
SPS#0 = SharePoint Portal Server Site
SPSPERS#0 = SharePoint Portal Server Personal Space
SPSMSITE#0 = Personalization Site
SPSTOC#0 = Contents area Template
SPSTOPIC#0 = Topic area template
SPSNEWS#0 = News Site
CMSPUBLISHING#0 = Publishing Site
BLANKINTERNET#0 = Publishing Site
BLANKINTERNET#1 = Press Releases Site
BLANKINTERNET#2 = Publishing Site with Workflow
SPSNHOME#0 = News Site
SPSSITES#0 = Site Directory
SPSCOMMU#0 = Community area template
SPSREPORTCENTER#0 = Report Center
SPSPORTAL#0 = Collaboration Portal
SRCHCEN#0 = Search Center with Tabs
PROFILES#0 = Profiles
BLANKINTERNETCONTAINER#0 = Publishing Portal
SPSMSITEHOST#0 = My Site Host
SRCHCENTERLITE#0 = Search Center
SRCHCENTERLITE#1 = Search Center
SPSBWEB#0 = SharePoint Portal Server BucketWeb Template



May 26th, 2011
