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,...


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

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

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

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

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

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

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

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 $...


3

What you are seeing are references in your database after a solution/webpart that was not removed correctly. I assume that you just uninstalled and removed the solution? If you know in which site och sub site the web part and feature was activated, you could add and install the solution again to your farm and follow those steps: Go to the site or sub sites ...


3

Like with most things of this nature it's PowerShell to the rescue. Basically you can get the App instance, Import the updated package, then update the instance with the new package. $AppInstanceOnSite = Get-SPAppInstance -web "<URL>" | Where {$_.Title -eq "<AppName>"}; $NewAppFile = Import-SPAppPackage -Path <local path to .app file> -...


3

By default when we create a web application in SharePoint 2013, it gets created with Claims authentication. When we migrate the content DB to 2013, it recognizes the user account only in this format i:0#.w|domain\username . Though it’s an AD account it no more recognizes the Domain\UserName format. SharePoint assumes all users to be claim users and renders ...


3

The farm couldn't have been 'upgraded', but the databases certainly could have. For the Content Databases, you can run the following T-SQL query: SELECT * FROM Versions (NoLock) That will tell you the version history in the Version column.


3

This is not an easy job as it is not supported path of Migration. In your situation, I highly recommend using the 3rd party tools(ShareGate, Metalogix etc). Another Option, I am thinking( complex, required a lot of work). Build a new 2010 std farm. Deactivate ent features from current 2010 farm detach Content Db from Prod 2010 and attach to 2010 Std farm. ...


3

As far I know, Sql server 2016 is not supported with sharepoint 2013. At this time, SQL Server 2016 RTM is not supported. https://technet.microsoft.com/en-us/library/cc262485.aspx#section4


3

SQL Server 2016 will not be supported by SharePoint 2010 or 2013. Microsoft's policy for SQL Server is when SharePoint is released, it supports the current version of SQL Server (SQL 2012 for SharePoint 2013) +1 (SQL Server 2014), aka N+1. So, while it may work (or may not depending on SQL Server removed features), Microsoft will not support you should they ...


3

Yes it will save the resource , To stop web application. Open IIS > Application pool > Application Pool > Stop Application pool of your web application. If you don't use the web application anymore , try to delete it (IIS /Content Database) from Central administration > Application Management > Manage Web APllication Select your web application > From ...


3

As you know Service Pack 1 is a mandatory requirement for installing any subsequent SharePoint 2013 cumulative updates as the new baseline! In your case, you just need to install the Service Pack 1 over SharePoint 2013 RTM from Service Pack 1 for Microsoft SharePoint Server 2013 (KB2880552)


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