Buy SharePoint Online eBook
|
a place to explore on SharePoint and Office 365.
2,389 total views
2,389 total views These days, it has been a common issue after installing windows security update in the SharePoint server, it breaks the search functionality in SharePoint 2016. In this troubleshooting technique, we will share how to fix it. How to fix the SharePoint 2016 search issue after installing the security update? When we see this
1,598 total views, 2 views today
1,598 total views, 2 views today 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)
1,407 total views
1,407 total views The config cache is a magical directory in the SharePoint server, why I said the magical directory is – for the many problems in SharePoint, the solution is clearing the config cache, mostly when the out of the timer job does not behave as expected or does not run as per the timer
3,647 total views
3,647 total views Suddenly in SharePoint 2016, the people search has stopped working, when we have tried to search any users from SharePoint 2016, we got the below error: “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
10,652 total views
10,652 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
17,491 total views
17,491 total views A couple of days back we have seen an error “Errors were found when compiling the workflow. The workflow files were saved but cannot be run” while trying to publish the SharePoint designer workflow. The error details were – “Unexpected error on server associating the workflow” This error we have noticed in the
![[Solved] Fix the "The term 'Get-SPWeb' is not recognized as the name of a cmdlet, function" PowerShell error](https://global-sharepoint.com/wp-content/uploads/2020/06/Solved-Fix-the-The-term-Get-SPWeb-is-not-recognized-as-the-name-of-a-cmdlet-function-PowerShell-error.png)
61,654 total views, 4 views today
61,654 total views, 4 views today In this troubleshooting, I will share how to fix the “The term ‘Get-SPWeb’ is not recognized as the name of a cmdlet, function” PowerShell error. Many times, we may notice even though we pass the correct URL to the Get-SPWeb command as an Identity parameter, still, we could see the error
34,150 total views
34,150 total views In this blog, I will share how to auto-populate the field in InfoPath based on another field. Let’s say I have a “Defect Tracking” custom list which has two columns “DefectID” and “Defect Details”. Now, the requirement is – in the InfoPath form there will be a textbox to enter the “Defect ID”
76,605 total views
76,605 total viewsIn this article, I will highlight the SharePoint version history/SharePoint generation from its invention – the year 2000 to 2020. In today’s market, SharePoint is one of the best content management system by Microsoft, it has been widely used across the globe, in the USA most of the big pharmaceutical company use SharePoint to
Buy SharePoint Online eBook
|
You must be logged in to post a comment.