Recently, I migrated a SharePoint 2010 farm to SharePoint 2016 and used an automated installation process using PowerShell and AutoSPInstaller to install the new SharePoint 2016 farm that ensured that the latest updates where applied, leaving the SharePoint 2016 farm updated and working properly (if you want to learn more about how to install a SharePoint farm in an automated way using PowerShell, I invite you to click here and here).

After installing the farm and migrating the web applications, new updates were installed in the farm (if you want to keep up with the latest SharePoint updates, click here) but when I ran the SharePoint Products and Configuration Wizard to ensure the new updates were properly installed (to know more about the need to run SharePoint Products and Configuration Wizard after a SharePoint farm update, click here), I got an error that was preventing me to finish the update process.

Important Note: Both source SharePoint 2010 and target SharePoint 2016 farms have Standard SharePoint licenses.

The Problem

After installing the updates and after running the SharePoint Products and Configuration, I was getting the following error:

The error details:

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information:

Feature (Name = [SharePoint Portal Server Status Indicator List template], Id = [065c78be-5231-477e-a972-14177cc5b3c7], Description = [SharePoint Portal Server Status Indicator List template], Install Location = [BizAppsListTemplates]) is referenced in database [Content_DB], but isn’t installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)

Feature (Name = [SharePoint Server Enterprise Site Features], Id = [0806d127-06e6-447a-980e-2e90b03101b8], Description = [Features such as the Visio Services, Access Services, and Excel Services applications included in the SharePoint Server Enterprise License.], Install Location = [PremiumWeb]) is referenced in database Content_DB] but isn’t installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)

Feature (Name = [SharePoint Portal Server Report Library], Id = [2510d73f-7109-4ccc-8a1c-314894deeb3a], Description = [SharePoint Portal Server Report Library], Install Location = [ReportListTemplate]) is referenced in database [Content_DB], but isn’t installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)

Feature (Name = [InfoPath Forms Services Support], Id = [c88c4ff1-dbf5-4649-ad9f-c6c426ebcbf5], Description = [InfoPath Forms Services Lists and Related Pages to Enable Presentation of Forms on the Server.], Install Location = [IPFSSiteFeatures]) is referenced in database Content_DB], but isn’t installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)

Feature (Name = [Data Connections Feature], Id = [00bfea71-dbd7-4f72-b8cb-da7ac0440130], Description = [], Install Location = [DataConnectionLibrary]) is referenced in database Content_DB], but isn’t installed on the current farm. The missing feature might cause upgrade to fail. If necessary, please install any solution that contains the feature and restart upgrade.        (EventID:ajxkh)

Upgrade [SPContentDatabase Name=Content_DB] failed.        (EventID:an59t)

Exception: The upgraded database schema doesn’t match the TargetSchema        (EventID:an59t)

Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: The upgraded database schema doesn’t match the TargetSchema

There are two main problems here:

• There are references in the content database to SharePoint Enterprise Features (InfoPath Form Services, Visio Services, Excel Services, etc) – my guess here is that sometime along the way, the source SharePoint 2010 farm had an Enterprise SharePoint license and was downgraded to a Standard license, leaving behind however references to Enterprise features in the content database
• There is a mismatch between the content database schema version and the version of SharePoint updates installed in the farm

One additional symptom that confirms there is an upgrade issue is the Upgrade Status page in Central Administration that showed the upgrade status as Failed:

The Solution

The solution to this problem was a two part solution, both applied in the target SharePoint 2016 farm:

• Fixing the missing Enterprise features references in the content database
• Fixing the content database schema version mismatch

Fixing the missing Enterprise features references in the content database

To fix the problem with references to Enterprise SharePoint features, I used the SharePoint Feature Administration and Clean Up Tool, which basically enables us to delete from the Farm, Web Application, Site Collection and sub sites any references to features that are not installed in the farm. The version I used was the version 2.4.8 that you can download here, that supports SharePoint 2016. The version 3.0, for some reason, didn’t detect the farm, which made it useless (maybe a beta version, not sure).

In this case, to remove the missing feature references, I used the SharePoint Feature Administration and Clean Up Tool to:

• Remove the missing features from the farm
• Remove the missing features from the sub sites

First, I removed the missing features from the farm, by removing the features marked as “Faulty” in the “Farm Feature Administration” tab, using the “Uninstall” button for each missing feature.

After that, I removed the features marked as ERROR in the “Remove / deactivate features in the selected sites” tab, by selecting all the site collection faulty features and using the “Remove from selected SiteCollection” button.

Finally, for each site, I selected the faulty site features and removed them by using the “Remove from selected Site (SPWeb)” button.

Fixing the content database schema version mismatch

To fix the version mismatch between the content database schema version and the version of installed SharePoint updates, I executed the following PowerShell command (executed with “run as administrator”):

Get-SPContentDatabase | Upgrade-SPContentDatabase

After this, I ran the SharePoint Products and Configuration Wizard again, and this time, it ran successfully:

To confirm if everything was OK, I checked the following pages in Central Administration in the target SharePoint 2016 farm:

• The Upgrade Status page
• The Database Upgrade Status page

In the Upgrade Status page, there is now a Succeeded upgrade status:

In the Database Upgrade Status page, there is an indication of “No action required” for all content databases in the farm, meaning that all databases were properly upgraded and the respective schema version is the same as the installed SharePoint updates:

Hope this helps!

Related Articles

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

In the meantime, SharePoint 2019 RTM is already out there! If you want to know all about the new features available in the new SharePoint Server release, click here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If SharePoint 2019 is still not an option, you can learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

If you are involved in a SharePoint upgrade and want to learn more about the upgrade process, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

Happy SharePointing!

The post SharePoint 2016 Upgrade: How to solve the “Feature is referenced in database but isn’t installed on the current farm” error appeared first on Blog IT.

Today i will talk about Publishing Features!!! During this afternoon I was trying to activate Publishing Features but i wasn’t having success because Page Library not was created on activation! So there are more than two Publishing Feature that we need have in consideration, it’s not enough Activate Publishing Infrastructure Feature and Publishing Feature. If you want activate all Publishing Features you can do it pragmatically or using Powershell script:

SharePoint Server – Powershell:

 
Disable-SPFeature –identity 'publishingSite' -URL http://server/ -force
Disable-SPFeature –identity 'PublishingResources' -URL http://server/-force
Disable-SPFeature –identity 'Publishing' -URL http://server/ -force
Disable-SPFeature –identity 'PublishingLayouts' -URL http://server/ -force
Disable-SPFeature –identity 'publishingweb' -URL http://server/ -force

Enable-SPFeature –identity 'publishingSite' -URL http://server/ -force
Enable-SPFeature –identity 'PublishingResources' -URL http://server/ -force
Enable-SPFeature –identity 'Publishing' -URL http://server/ -force
Enable-SPFeature –identity 'PublishingLayouts' -URL http://server/ -force
Enable-SPFeature –identity 'publishingweb' -URL http://server/ -force

SharePoint Online – Powershell:

 
Disable-SPOFeature –Identity "F6924D36-2FA8-4f0b-B16D-06B7250180FA" -Scope Site
Disable-SPOFeature –Identity "AEBC918D-B20F-4a11-A1DB-9ED84D79C87E" -Scope Site
Disable-SPOFeature –Identity "22A9EF51-737B-4ff2-9346-694633FE4416" -Scope Web
Disable-SPOFeature –Identity "D3F51BE2-38A8-4e44-BA84-940D35BE1566" -Scope Site
Disable-SPOFeature –Identity "94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB" -Scope Web

Enable-SPOFeature –Identity "F6924D36-2FA8-4f0b-B16D-06B7250180FA" -Scope Site
Enable-SPOFeature –Identity "AEBC918D-B20F-4a11-A1DB-9ED84D79C87E" -Scope Site
Enable-SPOFeature –Identity "22A9EF51-737B-4ff2-9346-694633FE4416" -Scope Web
Enable-SPOFeature –Identity "D3F51BE2-38A8-4e44-BA84-940D35BE1566" -Scope Site
Enable-SPOFeature –Identity "94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB" -Scope Web

Also that you can activate Programmatically:

 

        private void ActivatePublishingFeatures(SPWeb web, SPSite site)
        {
            // Publishing Site
            string sharePointPublishingSite = "f6924d36-2fa8-4f0b-b16d-06b7250180fa";
            Guid sharePointPublishingSiteGuid = new Guid(sharePointPublishingSite);

            if (site.Features[sharePointPublishingSiteGuid] == null)
            {
                site.Features.Add(sharePointPublishingSiteGuid, true);
            }

            // Publishing Resources
            string sharePointPublishingResources = "aebc918d-b20f-4a11-a1db-9ed84d79c87e";
            Guid sharePointPublishingResourcesGuid = new Guid(sharePointPublishingResources);

            if (site.Features[sharePointPublishingResourcesGuid] == null)
            {
                site.Features.Add(sharePointPublishingResourcesGuid, true);
            }

            // Publishing
            string sharePointPublishing = "22a9ef51-737b-4ff2-9346-694633fe4416";
            Guid sharePointPublishingGuid = new Guid(sharePointPublishing);

            if (web.Features[sharePointPublishingGuid] == null)
            {
                web.Features.Add(sharePointPublishingGuid, true);
            }

            // Publishing Layouts
            string sharePointPublishingLayouts = "d3f51be2-38a8-4e44-ba84-940d35be1566";
            Guid sharePointPublishingLayoutsGuid = new Guid(sharePointPublishingLayouts);

            if (site.Features[sharePointPublishingLayoutsGuid] == null)
            {
                site.Features.Add(sharePointPublishingLayoutsGuid, true);
            }

            // Publishing Web
            string sharePointServerPublishingWeb = "94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb";
            Guid sharePointServerPublishingWebGuid = new Guid(sharePointServerPublishingWeb);

            if (web.Features[sharePointServerPublishingWebGuid] == null)
            {
                web.Features.Add(sharePointServerPublishingWebGuid, true);
            }
        }

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post Activating all Publishing Feature – Programmatically & Powershell – SharePoint 2010, 2013, 2016 & Online: appeared first on Blog IT.

Today i will talk about List and Library Alerts and how can you get all Active alerts for a specific list using powershell script and how can you disable all alerts.

This is very useful script, when you need move a large list of items on a maintenance routine and you don’t want send a large number of emails/ notifications for users who subscribe alerts, this script help you disable and enable them.

This first PowerShell Script get all SharePoint list alerts with state active.

 

Add-PSSnapin Microsoft.SharePoint.PowerShell –ErrorAction SilentlyContinue

#Variables
$WebURL = "http://YourWebUrl"
$ListName="YourListName"

#Function to Get All Active Alerts on a Given List
Function Get-ListAlerts($WebURL, $ListName)
{
  #Get the Web and List objects
  $Web = Get-SPWeb $WebURL
  $List = $web.Lists.TryGetList($ListName)

  #Get All Alerts created in the list - Which are Active
  $ListAlerts = $Web.Alerts | Where-Object {($_.List.Title -eq $List.Title) -and ($_.Status -eq "ON")}

  foreach($Alert in $ListAlerts)
  {
          write-host "Alert' - $($Alert.Title)' Created for User - '$($Alert.User.Name)'"
  }

 #Dispose web object
 $Web.Dispose()
}

#Call the function Appropriately to Disable or Enable Alerts 
Disable-ListAlerts $WebURL $ListName

 

If you want disable all alerts on this specific list you just need run the following script.

 

Add-PSSnapin Microsoft.SharePoint.PowerShell –ErrorAction SilentlyContinue

#Variables
$WebURL = "http://YourWebUrl"
$ListName="YourListName"

#Function to Disable All Active Alerts on a Given List
Function Disable-ListAlerts($WebURL, $ListName)
{
  #Get the Web and List objects
  $Web = Get-SPWeb $WebURL
  $List = $web.Lists.TryGetList($ListName)

  #Get All Alerts created in the list - Which are Active
  $ListAlerts = $Web.Alerts | Where-Object {($_.List.Title -eq $List.Title) -and ($_.Status -eq "ON")}

  Write-host "Total Number of Active Alerts Found in the list: $($ListAlerts.Count)" 
 
  #Iterate through each alert and turn it OFF
  foreach($Alert in $ListAlerts)
  {
     $Alert.Status="OFF"
     $Alert.Update()
     write-host "Disabled the Alert' $($Alert.Title)' Created for User '$($Alert.User.Name)'"
  }
 
 #Dispose web object
 $Web.Dispose()
}

#Call the function Appropriately to Disable or Enable Alerts 
Disable-ListAlerts $WebURL $ListName

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint – Get all alerts from a specific SP List/Library using Powershell appeared first on Blog IT.

Today i will talk about Storage Metrics in your SharePoint Site Collection!!!

Everyone knows what is the main feature on SharePoint that you could interact with and Structure of SharePoint Site Collections! right!? Site Content and Struct (/_layouts/sitemanager.aspx)!!!

Site Content and Structure page, give you a great overview about all your Site Collection structure. This feature, available since Microsoft Office SharePoint Server 2007, give the capability to navigate dynamically on your site collection hierarchy, it is familiar to Windows Explorer in fact. You can see the site collection hierarchy in the navigation pane as a tree view on the left of the Site Content and Structure page.

But, if you need know more details about storage, probably don’t help you as you expect, so in this case you case access to Storage Metrics (/_layouts/storman.aspx).

Storage Metrics underneath Site Collection Administration, access to your all sub-sites and libraries in SharePoint Online ( also available for SharePoint 2010, SharePoint 2013 and SharePoint 2016) and give you the information about how much storage they are consuming.

It is great!!! Because Storage Metrics allows you to drill down to each site, library and even folder to show a very granular report on your storage consumption, this is very important if you need migrate a large lists or even you are planning an migration between SharePoint Versions without any 3rd Party tool.

Take a Look:

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint Online – Storage Metrics – Monitor storage usage in your Site Collection appeared first on Blog IT.

Today i will show you how can you create SharePoint 2016 Service Accounts using PowerShell script following the Best Practices.

The script not only create all the accounts but also create the respectives OU (Organizational Unit):

• SharePoint Accounts
• SQL Accounts

Service Accounts:

Script:

 

$mydom = (get-addomain).distinguishedname 
$password = "pass@word1" | ConvertTo-SecureString -AsPlainText -Force 

$ouNameSP = "SharePoint Accounts"
$oudnSP = "OU=$ounameSP,$mydom" 

$ouNameSQL = "SQL Accounts" 
$oudnSQL = "OU=$ounameSQL,$mydom" 

#----------------------------> Organizational Unit <---------------------------- 

New-ADOrganizationalUnit -Name $OUNameSP -Path $mydom 
Write-Host "OU $OUNameSP Created" -foregroundcolor green 

New-ADOrganizationalUnit -Name $OUNameSQL -Path $mydom 
Write-Host "OU $OUNameSQL Created" -foregroundcolor green 

#-----------------------------> SharePoint 2016 <-------------------------------

$usersArraySP = @("SP_Farm","SP_Admin","SP_Pool","SP_Services","SP_Crawl","SP_Search",
                  "SP_UserProfiles","SP_PortalSuperReader","SP_CacheSuperUser","SP_VisioUser",
                  "SP_PerfPointUser","WF_Service","SP_MySitePool","SP_PortalSuperUser")

foreach ($usp in $usersArraySP) {
        New-ADUser -Name $usp -DisplayName $usp -SamAccountName $usp -AccountPassword $password 
        -ChangePasswordAtLogon $false -PassThru -PasswordNeverExpires $true -Path $oudnSP 
        Write-Host "$usp Created" -foregroundcolor green
 }

#----------------------------------> SQL <--------------------------------------
$usersArraySQL = @("SQL_Admin","SQL_Service")

foreach ($usql in $usersArraySQL) {
       New-ADUser -Name $usql -DisplayName $usql -SamAccountName $usql -AccountPassword $password 
       -ChangePasswordAtLogon $false -PassThru -PasswordNeverExpires $true -Path $oudnSQL
       Write-Host "$usql Created" -foregroundcolor green
 }

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint 2016 – Create Service Accounts using PowerShell script appeared first on Blog IT.

Today i’m going to talk about SharePoint Scenarios and what are the main difference between this three types of scenarios and what scenario should be the option for your environment…

So, the three types of architecture scenario that you can have on your SharePoint environment are the following:

What should you choose?! Well in fact there are so many question that you need answered before take an decision!?

It isn’t easy take a decision, let’s analyse what are the main benefits each architecture:

SharePoint On-Premises:

• Private Cloud
• Dedicated environment
• Internally hosted
• Internally managed
• Internal designed

• Migration Flow:

SharePoint Online:

• Public Cloud
• Partially or fully dedicated
• Externally hosted
• Externally or Internally managed
• Internally managed
• Minimal customization

Cloud benefits according to cloud users?

• Increase efficiency (55 %)
• Improved employee mobility (49 %)
• Increased ability to Innovate (32 %)
• Freed current IT staff for other projects (31 %)
• Reduce IT operation costs (25 %)
• Enabled us to offer new products/ services (24 %)

• Migration Flow:

SharePoint Hybrid Solution:

What is Hybrid SharePoint?

“Productivity services in SharePoint Online (Office 365) which are securely integrated with on-premises SharePoint Server 2016 to provide unified functionality and access to data.”

Why considering a Hybrid SharePoint Solution?

• Large existing investments (customized SP deployments w/lots of data and settings,custom solutions, LOB systems, etc…)
• Functionalities I can’t do in the Cloud that i can do on premises;
• Keep Sensitive Data on Premise
• Collaboration with External Partners
• Capacity Flexibility
• Intranet – Extranet
• Geo Location

Same Benefits of Hybrid SharePoint Solution?

SharePoint Business to Business Collaboration: Extranet for Partners with Office 365

“on-premises extranet site involves complex configuration to establish security measures and governance, including granting access inside the corporate firewall, and expensive initial and on-going cost….SharePoint Online, partners connect directly to a members-only site in Office 365, without access to the corporate on-premises environment or any other Office 365 site. Office 365 Extranet sites can be accessed anywhere…”

SharePoint hybrid sites and search

“A hybrid environment can help your company get started in the cloud, taking a first step to explore the cloud functionality at own your pace. It also enables enterprise users to be connected from almost anywhere to the resources and content they need… SharePoint hybrid features, you can consolidate search results between SharePoint Server and Office 365, consolidate user profiles in Office 365, and offload your users’ personal storage to the cloud…”

• Migration/Interactions Flow:

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint Scenarios – Online, On-Premises or Hybrid!? appeared first on Blog IT.

Today i will post a script very helpful when you are on Migration steps and you need export all wsp solutions.

 

$dirName = "C:\WSP"
if (!(Test-Path -path $dirName))
{
New-Item $dirName -type directory
}
Write-Host Exporting solutions to $dirName
foreach ($solution in Get-SPSolution)
{
    $id = $Solution.SolutionID
    $title = $Solution.Name
    $filename = $Solution.SolutionFile.Name
    Write-Host "Exporting ‘$title’ to …\$filename" -nonewline
    try {
        $solution.SolutionFile.SaveAs("$dirName\$filename")
        Write-Host " – done" -foreground green
    }
    catch
    {
        Write-Host " – error : $_" -foreground red
    }
}

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint – Export all solutions wsp using PowerShell script appeared first on Blog IT.

Today i will show you the full list of TCP/IP Ports that you must consideration on your SharePoint 2016 Farm.

Full list of ports used by SharePoint 2016:

Reference Links:

Security for SharePoint Server 2016
Set-SPServiceHostConfig
TCP/IP Communications (Windows Server AppFabric Caching)

Thanks

Fábio Carvalho
SharePoint Consultant
|create|it|

The post SharePoint 2016 – TCP/IP Ports appeared first on Blog IT.