Tag Info

New answers tagged


Try to detach the content database and attach it again using powershell... also do you have the root level site collection in new webapplication... check from central admin..."/" should be 1st in your site collection list....normally root level missing.


PowerShell for SharePoint Online has really limited capabilities at the moment. There is no one liner to automate this task. But you can use CSOM inside your scripts. [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SharePoint.Client') | Out-Null $login = 'test@test.onmicrosoft.com' $password = ConvertTo-SecureString 'password' -AsPlainText ...


Here is the sample that explains the syntax: Export-SPWeb -Identity “http://sp.dev/subsite” -ItemUrl “/subsite/lists/List Title here” -path “c:\output\tempfile.csv” Some Where Options: Identity: full url (absolute) of the site where the list exists ItemUrl: relative path of the list from subsite level. Do not forget to include the leading “/” ...


Just look at the code snippet below and try to imagine the scenario of what will happen: using(SPSite site = new SPSite("http://somesite")) { using (SPWeb web = site.OpenWeb(SameGuid)) { return web.Url; } } The above code can raise an exception because two web objects would be returned, there are infinite scenarios where GUID is used to ...


You can create a powershell script to export list data to csv file and create a windows task to run this daily.


I would use a Timer Job. Just choose the best moment to exec your code and that's all. Maybe this page will help you. http://www.codeproject.com/Tips/634208/Create-and-Deploy-Custom-Timer-Job-Definition-in-S Dan


The error message you are receiving is because your content databases are full. If you go into Central Administration and look at your content databases, you'd see that they are all capped with the number of site collections that they can contain. Simply create a new content database and restore the site into that database and it should work.


Two easy options i am thinking about. Method # 1 Make the changes on the AAM and Update the IIS bindings. Yo may need to IIS reset at then end. Method # 2 Detach the Content Database from web App A & web App B Now attach Content DB from Web app A to Web App B & From web B to Web App A.

Top 50 recent answers are included