Category: SharePoint Server Error

Product Version Job: Collection was modified; enumeration operation may not execute

Collection was modified; enumeration operation may not execute in SharePoint Product Version Timer Job

 6,193 total views

 6,193 total views 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 Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object

Continue reading

[Fixed]: The page ‘catalogs/DeviceChannelMappings.aspx’ allows a limit of 11

Sorry something went wrong the page allows a limit of 11 direct dependencies, and that limit has been exceeded

 7,201 total views

 7,201 total views 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 it is not registered as safe.” Then

Continue reading

Transport-level error – the specified network name is no longer available – analysis

Transport-level error - the specified network name is no longer available - analysis

 28,519 total views

 28,519 total views 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.).”, this error is generally generated by the

Continue reading

[Fixed] “Sorry, something went wrong. There was an exception in the Database” (SharePoint Server Error)

 39,990 total views

 39,990 total views 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: All of a sudden, our SharePoint 2016 search is not working. From the browser getting the below error: ULS log report

Continue reading