The product version job collection was modified enumeration operation may not execute – sometimes we may get this error from the SharePoint server that “Product Version Job: Collection was modified; enumeration operation may not execute ((Correlation=0b9de10e-4bb7-4010-ab62-e91d5375e0ac)”, and in the ULS log we will get the below entry: “at System.Collections.Generic.List`1.Enumerator.MoveNextRare() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse) at
The page ‘catalogs/DeviceChannelMappings.aspx’ allows a limit of 11 – I was fixing the SharePoint 2016 search issue where I was getting the below error while searching anything in the SharePoint 2016 search box: “The base type ‘Microsoft.Office.Server.Search.Internal.UI.SearchResultsLayoutPage’ is not allowed for this page. The type Microsoft.Office.Server.Search.Internal.UI.SearchResultsLayoutPage, Microsoft.Office.Server.Search, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c could not be found or
The specified network name is no longer available – if you have a SharePoint farm with multiples servers, then from the SharePoint server log we might get this error – “A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 – The specified network name is no longer available.).”,
How to fix “Sorry, something went wrong. There was an exception in the Database. Please retry your operation and if the problem persists, contact an administrator” in SharePoint 2016 search. Issue Descriptions: “Sorry, something went wrong. There was an exception in the Database” (SharePoint Server Error) All of a sudden, our SharePoint 2016 search is
| Contact Us: support@global-sharepoint.com | Support this site| Privacy Policy| Sitemap | Copyright © 2023 Global SharePoint. All rights reserved. |
