SharePoint Server Error Archives - Global SharePoint Diary

Product Version Job Collection was modified enumeration operation may not execute

By Global SharePoint on April 29, 2021February 3, 2023

7,567 total views

7,567 total views 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

Posted in: Check SharePoint patch level, collection was modified enumeration operation may not execute sharepoint, get-spproduct -local, Product Version job failed SharePoint 2016, Product version timer job fails, SharePoint 2013 patch missing/required, sharepoint 2013 product version timer job

SharePoint SharePoint 2016 search issues SharePoint Server Error SharePoint Troubleshooting

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

By Global SharePoint on March 27, 2021June 19, 2022

'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

9,237 total views

9,237 total views 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

Posted in: allows a limit of 11 direct dependencies, allows a limit of 11 direct dependencies and that limit has been exceeded, and that limit has been exceeded SharePoint 2013, SharePoint 2016 Direct Dependencies Limit with User Controls, SharePoint 2016 Limit Of 11 Direct Dependencies, This page allows a limit of 200 controls

SharePoint SharePoint Server Error SharePoint Troubleshooting

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

By Global SharePoint on February 7, 2021February 3, 2023

33,310 total views

33,310 total views 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

Posted in: A transport-level error has occurred when receiving results from the server the specified network, A transport-level error has occurred when sending the request to the server. (provider tcp provider, Availability group listener, Microsoft Sharepoint Troubleshooting, SharePoint On-Premise, sql server alwayson availability groups, SQL Server Exception, SQL server high availability, sqlexception 0x80131904: a transport-level error has occurred when receiving results from the server, TCP provider the specified network name is no longer available. communication link failure, The specified network name is no longer available sql server error 64, What is availability group in sql server

SharePoint SharePoint 2010 SharePoint 2013 SharePoint 2016 SharePoint 2019 SharePoint Server Error

Instantly Solved: “Sorry, something went wrong. There was an exception in the Database” (SharePoint Server Error) – SharePoint 2016/2019

By Global SharePoint on November 1, 2019November 17, 2022

Sorry, something went wrong. There was an exception in the Database. Please retry your operation and if the problem persists, contact an administrator

41,913 total views, 2 views today

41,913 total views, 2 views today 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

Posted in: Microsoft Sharepoint Troubleshooting, SharePoint upgrade database error, something went wrong, Sorry something went wrong

Category: SharePoint Server Error

Product Version Job Collection was modified enumeration operation may not execute

Like this:

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

Like this:

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

Like this:

Instantly Solved: “Sorry, something went wrong. There was an exception in the Database” (SharePoint Server Error) – SharePoint 2016/2019

Like this:

Category: SharePoint Server Error

Product Version Job Collection was modified enumeration operation may not execute

Share this:

Like this:

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

Share this:

Like this:

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

Share this:

Like this:

Instantly Solved: “Sorry, something went wrong. There was an exception in the Database” (SharePoint Server Error) – SharePoint 2016/2019

Share this:

Like this: