Hot answers tagged

10

No, you can't do the in place upgrade.only supported way is database upgrade or using 3rd party tools. When you upgrade from SharePoint Server 2013 with Service Pack 1 (SP1) to SharePoint Server 2016, you must use a database attach upgrade, which means that you upgrade only the content for your environment and not the configuration settings. https:/...


8

You can use same url or change the URL at the destination farm. If you use the old url, only thing it will take time when you point your DNS to new servers. If you use new url: People who bookmarked the old url will see the difficulites if some site collections hardcoded url they will upset or if you have custom app which use the hardcoded url then they ...


8

Shall we migrate directly from SP 2007 to O365 direct? Yes, you can migrate directly from SharePoint 2007 to SharePoint Online, It's not like the SharePoint On-Prem where you should first upgrade to SharePoint 2010 to can upgrade to SharePoint 2013. If yes, Could you please list out various options available to migrate to O365 directly? Manually copying ...


7

Couple of things can change the database size. If There is any unused or white space inside the content database then during the backup and restore method database automatically shrink it. If there is any orphan items inside the content db then during db restore method it may clear those. There are possibility that you deleted data in SharePoint 2013 or may ...


7

Actually, It's an early question, where there is no any published info related to the SharePoint 2019 yet. But what is expected based on the previous SharePoint upgrade path process, There is no direct upgrade path from SharePoint 2013 to SharePoint 2019. you should upgrade first to SharePoint 2016 then to SharePoint 2019. Meanwhile, what I am sure,...


6

Yes, Service Pack 2 contains all Cummulative Updates and Hot fixes before it.. including SP1 Install SharePoint 2010 Service Pack 2 the right way SharePoint Server 2010 Service Pack 2 has been released (Updated July 31st, 2013)


5

I should have checked this earlier. I made 2 empty SharePoint projects. One 2010 and one 2013 and did a compare of the different files. The only difference i could find was in the csproj file. In the SP 2013 project there is a <TargetOfficeVersion>15.0</TargetOfficeVersion> property that was not present in the SP 2010 project. I added it and ...


5

You could loop through all the existing sub-sites with a PowerShell script, and use the feature cmdlets to activate the feature on existing sites. Using this method you could also insert some logic/conditions to enable or not enable the new feature if that is useful.


5

When you install the executable for a Cumulative Update (CU), you have not actually upgraded your servers yet. The PSConfig.exe (Command Line), or the SharePoint Products Configuration Wizard (GUI), will need to be run to upgrade both the running binaries, and make any changes to the SharePoint database schemas provided in the CU. In this case, you have the ...


5

I had the same problem when running IE on the server and opening the Central Admin URL. Went to all Programs/Microsoft SharePoint 2010 Products/SharePoint 2010 Central Administration and ran that as an Administrator and had no problems adding users. I was also able to add users when I used a workstation to add users via the URL.


5

The search database is not a content database. You need to upgrade using the SharePoint 2010 Farm Configuration Wizard. I would run that and see where it gets you and then you can find any errors in the upgrade logs. Here is a link to help. http://www.justanothertechnologyguy.com/2011/11/databases-require-upgrade-or-not.html Excerpt: •Open a command box ...


5

When you create a new web application, the content database associated with it is fresh in the sense that you haven't added any data to it yet. The purpose of upgrading from SP 2010 to SP 2013 is to carry over the content from SP 2010 to SP 2013. So you delete the original content database as you don't need it and attach the content database from SP 2010 to ...


5

You can use below code to find deployment status $Name = "MySharePoint.wsp" Write-Host -NoNewline "Waiting..." $Solution = get-SpSolution $Name while($Solution.JobExists) { sleep 5 Write-Host -NoNewline "." $Solution = get-SpSolution $Name } Write-Host "Deployment Completed"


5

Get-SPProduct -local doesn't actually return whether you are missing some updates. Instead as described in the TechNet: Returns a list of the SharePoint-related products installed in the farm and the versions of all updates installed for each product. However to understand why this affects the Configuration Wizard's execution the command's steps should ...


5

Guidance on upgrade to SP2019 has now been published on Microsoft Docs: https://docs.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-from-sharepoint2013-to-sharepointserver-2019 Microsoft supported upgrade path is DBAttach method for Site Collections and requires an intermediate SP2016 farm: The upgrade scenario has not changed in SharePoint ...


4

We upgraded one of our 225GB content databases in roughly 4 hours so 4 days is excessive. What this actually sounds like is that one of the servers in the mix is running into severe resource issues and is having to swap to disk a lot more than it should. I'd check all the servers in the farm including the SQL server and make sure that they have adequate ...


4

Are you missing custom solutions in your new 2010 farm, that exist in the 2007 farm? Compare the installed features/solutions in both farms. However, you really should upgrade to SP2. The preupgradecheck stsadm command was added in SP2 and is very good at identifying where you're going to have issues. The upgrade alone may even solve your problems.


4

I found the solution to this issue: Both versions of the site definitions (14 and 15) need to be present in respective hives at the time of performing upgrade. If either of them is absent the error will show up. See here for more information: http://sharepointnadeem.blogspot.com/2014/01/sharepoint-following-sites-are-using.html


4

It's an easy fix, at least this worked for me. Steps: Double click package in Visual Studio Go to Advanced tab Change the product version to 14.0 and you are good to go


4

How many Servers in the Farm? Web site mentioned in the error ( ****.local80) still exist and working? If you have more than one server in farm, simply copy the web.config file from other server for same Virtual directory and re ran the Config wizard. Or Simply delete the Web Application( i am sure your web app not working as missing web.config) or re ...


4

While recommended to install security updates as soon as possible, you will need to evaluate the security risk of not installing a particular security patch. This is something we will not be able to help you with. You do not need to install the Cumulative Update if you do not wish to install it. Yes, some non-CUs increment the farm build number due to an ...


4

You already found out a lot of stuff regarding security updates, CUs and version number increments. There's nothing wrong in your post, but i would like to add some comments especially to your questions: It is valid to install security-patches for Windows including SharePoint specific security-updates (if there's one available that month). Theoretically ...


4

As already mentioned by others, there is no supported way to downgrade from enterprise to standard edition. Possible workaround: SharePoint 2013 has a configuration option called "licensing". You can enable and disable license-depended features for a group of users. HowTo: Enable licensing via PowerShell. Assign Standard-Licenses to all of your users (...


3

The upgrade was started by a timer job that ran at 6AM. The upgrade can be forced manually through PowerShell: Upgrade-SPSite <http://site> -VersionUpgrade -Unthrottled


3

I finally sorted this issue. I ended up ringing MS on it and their only official supported fix was to delete and recreate the User Profile Service Application & it's database. However this was on our production server and I couldn't do that. Luckily based on their information I was able to come up with an unofficial fix. The error happens because ...


3

Steps to Upgrade from SP 2010 to SP 2013: Make the site in SP 2010 readonly. Using SQL Management Studio, perform the backup of Content database and service database in SP 2010. Restore the databases in SP 2013 SQL server. Attach the content database to a site collection in SP 2013. Similarly, attach the service databse to the corresponding service in SP ...


3

Follow up for everyone, in case they run into this issue. I opened up a case with Microsoft support. One of the first things the technician had me do was a SELECT * on the dbo.MSSLocations database in the Search Service Application admin database. No results were present, while there are 5 rows expected. With that information, the technician had me execute ...


3

Many of the class/id names have changed. Some slightly, some significantly and some are still the same. Off the top of head and from briefly flipping through my notes a few (related to quick-launch and navigation): /*2010 quick launch or current navigation*/ #ms-quickLaunch { your styles } /*2013 quick launch or current navigation*/ #sideNavBox { your ...


3

You will not find the file web.config in this folder C:\inetpub\wwwroot\wss\VirtualDirectories\…local80\web.config' The reason is your web.config file is deleted in your port 80. You have to have web.config file in this folder otherwise you will face this problem. I have the problem in port 40786. The solution is delete the website from your iis server ...


3

There are couple of ways to remove it. Using Powershell First, using this Powershell script by Phil Childs: To use the script, run these functions in a PowerShell console with the SharePoint 2010 add-ons loaded: function Remove-SPFeatureFromContentDB($ContentDb, $FeatureId, [switch]$ReportOnly) { $db = Get-SPDatabase | where { $_.Name -eq $...


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