Tag Info

Hot answers tagged

4

Checking the list of ststadm operations seems that there is no stsadm command for disabling a timer job. There is only a command to delete a timer job (deletessptimerjob). In that case you are left with two options: Disable the timer job using the UI in Central Administration (Central Administration -> Operations -> Job Definitions) Disable the timer job ...


2

plz try with this Export and import a subsite, list, or library: stsadm -o export –url [url of subsite, list, library] –filename D:\spbackup\backup.bak -quiet -overwrite stsadm -o import –url [url of subsite, list, library] –filename D:\spbackup\backup.bak -quiet If the command is entered correctly and you have the permission needed to run the export, ...


2

Out of the box of PowerShell cmdlets, It can't be done. It's no valid cmdlets in the Index of SharePoint Server 2010 Windows PowerShell cmdlets However, Stefan Goßner wrote the blog post SharePoint Variations – The complete Guide – Part 16 – Translation Support which go over the topic in detail. He suggest to use PublishingService to export/import ...


1

Check your database version using following Get-SPContentDatabase <DB name>| Format-List * In this check the SchemaVersionXML if it is "4.0.145.0" then you have to run the below powershell script **Upgrade-SPContentDatabse –Identity <DB Name> and then take fresh back up and try.


1

To query Windows Registry is probably the most reliable way to detect if SharePoint installed (Visual Studio uses this technique). Please follow the article How To: Detect the Installed SKU of SharePoint 2010 for more details. It contains code sample that demonstrates how to retrieve the registry key of the installed SKU of SharePoint Server 2010. ...


1

Yes, Your understanding is correct. When you run the migrateuser command if new login does not exist in AD then this command will throw the errors. It will copy the permission from old ID to new ID.


1

You can use the pwoershell to get the alerts for a site collection. First you make sure powershell is properly configured. Now run the below script and you will get it. Add-PSSnapin microsoft.sharepoint.powershell $site = Get-SPSite "http://dlvrn2010.com/sites/spalerts/ $alertResultsCollection = @() foreach ($web in $site.AllWebs) { ...


1

I am sure Gary Lapointe's custom stsadm will not work in 2013. You need to do the following things. 1st deploy the Lapointe.wsp to install all the custom commands. Download it from here :SharePoint 2013 Server Cmdlets (x86, x64) Once above solution succesfully installed then all his custom command will be available. Now you to run the following command. ...


1

SharePoint 2007 does not have PowerShell support. In Visual Studio create a console application that loops through all the site collections and sites. You need to run this program on the SharePoint 2007 server. http://msdn.microsoft.com/en-us/library/office/ms462161(v=office.14).aspx static void Main(string[] args) { SPFarm farm = ...


1

To get the site id use powershell. Interestingly in my case I can create the powershell object. E.g. $s=Get-SpSite <url> $s.ID Go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN Then execute STSADM -o deleteconfigurationobject -id <site id> In once case this worked Or you can try deleting $s.Delete ...


1

I am not sure if i am late or not. this error comes for one of the following reasons: Backup SharePoint server version is different than the restore server version The backup file is corrupted The used user account is not having the permission on the content DB for the web application that you want to restore on.



Only top voted, non community-wiki answers of a minimum length are eligible