Tag Info

New answers tagged

0

The problem was quite strange. My user account was twice in the web.SiteUsers set. Once with the claims authentication i:0#.w|domainname\username and an other with classic authentication domainname\username. I remove those users and then it worked fine. I think I had this issue during the migration of the contentdb' users. (from 2010 to 2013)


0

The application pool acoount had no permission on the DB. Adding the permission solved my problem.


1

Probably you got more information than you posted, but just in case you didn't know yet - the proc_StartUndirtyList stored procedure is used to start a new link fixup operation. A back-end database server and front-end Web server work together to implement link fixup. The back-end database server tracks forward links from list items to documents. When the ...


0

When you run the move coomand, user will get correlation Id, sometime 404.typically this is advised to run in after hours, because you have to run iisreset after it.After you run the Move-SPSite cmdlet, run the IISReset command to update changes to IIS. Their is no power shell or other method, which will tell you exact timings.its depend upon, hardware of ...


2

1 - The Move-SPSite cmdlet moves the data in the specified site collection from its current content database to the content database specified by the DestinationDatabase parameter. A no-access lock is applied to the site collection to prevent users from altering data within the site collection while the move is taking place. Once the move is complete, the ...


0

From your information, its look like you trying to move the subsite into different content database. which is not possible, you should move the site collection from one DB to other. Now, if you want to move the subsite into own db then: Move subsite to own site collection first, using export & import process. Now move new site collection to different ...


0

The extra size was about the log. (generated during the copy precess, also if the recovery model was in simple mode). After the copy, I shrank the contentDB and everything was fine. (the sizes were the same)


0

Yes, it will delete the web from the Database. But you will not get the space back just with this action. Once something removed from the DB it will not reduced by size rather the white space(unused Space) increased. I think, you have to shrink the database to get the space back(reduce the size of content DB). their is one rule in the health n monitor ...


0

when you restore the existing DB even with new ID/GUID but still site collection url will be same, so in that case it will not work. For Sp 2010 You have to go with either backup and restore to new database or export & import method. For Sp 2013 If you want to copy of existing site then you can use copy-spsite command. Copy-SPSite ...


0

Is it something on the home page? Here's a quick test: navigate to (site collection url)/_layouts/settings.aspx



Top 50 recent answers are included