Tag Info

New answers tagged

1

This ended up being an easy fix. For a more complete answer, I want to mention that this was happening on a MySite collection. I activated the SharePoint Server Publishing Infrastructure and SharePoint Server Publishing features at the MySite site collection level. That brought back most of the missing apps for all MySite users. The last issue was the ...


0

You don't need a new DNS server, rather you need to update the DNS record. Right now your URL /DNS pointing to the sharepoint 2010 wfe. After migrating you have to point those DNS to sp2013 wfe.


0

Here are the steps which you need to perform. Stop Content Db to use RBS and Move in all the Files inside the DB from Blob Folder. Verity that files are inside Sql DB by running query. Test by uploading file to Site and verify it stores in sql DB. backup and restore the DB to your new SharePoint 2013 environment. If its a classic mode web app in 2010 then ...


0

I think the fact it started working on a new domain albeit with a login prompt was a coincidence but without any real detail about the original problem it would be hard to determine the issue. SharePoint install and config does not make any changes to AD. The person installing SharePoint on the other hand... It sounds like a simple install so I'll hazard a ...


3

You can also try 3-rd party tool from Virto - SharePoint Copy Move. It will allow you to move one or multiple files from one directory to another and even within site collections and save your versions history. Hope it will help!


3

You can use also 3-rd party tool to move documents with their versions - e.x. SharePoint Copy & Move Files. Althought this is paid version, it has 30 days trial, so you can test everything.


1

I have created a script iterating through all Document Libraries checking for difference in filesize between what SharePoint thinks and how big the file in the Database really is. Im also doing a try/catch so make sure I don't miss any totally corrupt files. Add-PSSnapin Microsoft.SharePoint.PowerShell -erroraction SilentlyContinue ...


0

Wouldn't it just be easier to save the list as a template (including content), then creating a new list - using that template - in the desired site? I actually just had this problem, and went with this solution. Powershell and third-party tools could be necessary if you're crazy customized or have humongous lists, but this method worked for me just fine.



Top 50 recent answers are included