Problem) 
Restore-SPSite : The operation that you are attempting to perform cannot be completed
successfully.  No content databases in the web application were available to store your
site collection.  The existing content databases may have reached the maximum number of
site collections, or be set to read-only, or be offline, or may already contain a copy
of this site collection.  Create another content database for the Web application and
then try the operation again.
At line:1 char:1
+ Restore-SPSite "http://site2 " -Path C:\backups\site1.bak ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share...dletRestoreSite:SPCmdletRe
   storeSite) [Restore-SPSite], InvalidOperationException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletRestoreSite

Solution)   To avoid this error create a new content database for that site collection.
steps:
step 1) got to central admin .
2)under databases  click manage content databases 
3) you can see a drop down with a web appliactions selected and when you click on it it says change web application on the top right corner.
4) select the site collection for which you want to add new content database .
5) on top left you can see add a content database click it and  you can still change you site collection in there and next set a db server , dbserver name ,authentication type ,and also we have a failover dtatabase server so that to mirror your current datatbase to help you on when on of the db server breaks .
next you  can set the limit of number of sites before warning event is generated and max sites under this database 

Comments

Post a Comment

Popular posts from this blog

Metalogix Exception thrown: Server was unable to process request. ---> Value does not fall within the expected range. Solution : Look for app pool .Is posible reset iis .
Read more
REST API The Basics Before it can do anything with SharePoint, your remote Web or mobile application must obtain authorized access. In SharePoint 2013 there are two general approaches to authorizing access to a SharePoint site (regardless of whether you’re using REST). The first approach involves authenticating a SharePoint user, in which case your application has the same access to SharePoint data and capabilities as the user. The different ways you can authenticate a user from a Web or mobile application are outside the scope of this article, but we’ll briefly mention two new options in SharePoint 2013 because they affect the way you construct your REST requests: If you’re calling into SharePoint from a remotely hosted application that can’t use client-side code (HTML and JavaScript) exclusively, and there’s no firewall between SharePoint and your application, you can use OAuth 2.0 tokens with Microsoft Access Control Service (ACS) as the secure token server. If client-side ...
Read more
Image
Allow SharePoint 2013 site to load into IFRAME in non-SharePoint application add the code highligted to all of your master pages if you have multiple masterpages. <WebPartPages:AllowFraming runat="server" />
Read more