In this troubleshooting article, we will learn about How to fix “The term ‘Get-MsolUser’ is not recognized as the name of a cmdlet”. When we try to connect to Office 365 services, sometimes we may get the below error: “The term ‘Get-MsolUser’ is not recognized as the name of a cmdlet” How to fix the
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 workflow of
![[Fixed] Error – activate the SharePoint Server Publishing Infrastructure feature in SharePoint Online site](https://i0.wp.com/global-sharepoint.com/wp-content/uploads/2020/06/Fixed-Error-–-activate-the-SharePoint-Server-Publishing-Infrastructure-feature-in-SharePoint-Online-site.jpg?fit=965%2C540&ssl=1 "[Fixed] hidden error: Activate SharePoint Server Publishing Infrastructure feature in SharePoint Online site (Microsoft 365) 5")
Activate SharePoint server publishing infrastructure feature – When I was trying to activate the “SharePoint Server Publishing Infrastructure” feature in the SharePoint online communication site, getting the error – “Sorry, something went wrong An unexpected error has occurred. Technical Details, Troubleshoot issues with Microsoft SharePoint Foundation.“ Activate SharePoint server publishing infrastructure feature error When we
![[Fixed] Server relative urls must start with SPWeb.ServerRelativeUrl"in reading web part properties!](https://i0.wp.com/global-sharepoint.com/wp-content/uploads/2020/06/Fixed-Server-relative-urls-must-start-with-SPWeb-ServerRelativeUrl-in-reading-web-part-properties.png?fit=958%2C538&ssl=1 "Instantly Fixed: Server relative urls must start with SPWeb.ServerRelativeUrl\"in reading web part properties! - SharePoint Online (Microsoft 365) 7")
Server relative URLs must start with SPWeb.ServerRelativeUrl” in reading web part properties! – Recently I was working on, to the get web part properties details from the SharePoint site page using the PowerShell CSOM, then I got this error “Exception calling “ExecuteQuery” with “0” argument(s): “Server relative URLs must start with SPWeb.ServerRelativeUrl” in reading web
![[Solved] Getting Error "InfoPath cannot generate a form template for the SharePoint list"](https://i0.wp.com/global-sharepoint.com/wp-content/uploads/2020/05/Getting-Error-InfoPath-cannot-generate-a-form-template-for-the-SharePoint-list.jpg?fit=889%2C448&ssl=1 "Instantly Solved: Getting Error \"InfoPath cannot generate a form template for the SharePoint list\" 9")
InfoPath cannot generate a form template – when we want to customize the SharePoint custom list using the InfoPath designer and click on the “Customize in Infopath” link from the SharePoint list ribbon, we will get this error – “InfoPath cannot generate a form template for the SharePoint list” and “the soap response indicates that
![[Solved] Edit user Permission is greyed Out SharePoint Online](https://i0.wp.com/global-sharepoint.com/wp-content/uploads/2020/05/Solved-Edit-user-Permission-is-greyed-Out-SharePoint-Online.jpg?fit=748%2C470&ssl=1 "Instantly Solved: Edit user Permissions greyed out SharePoint Online - Microsoft 365 11")
Edit user Permissions greyed out SharePoint Online – sometimes, we may notice that edit user permission is greyed out in the SharePoint Online document library, list, or site permission page – even though you are in the “Site Owners” group. This behavior is noticed both in SharePoint online and on-premise. How to fix the edit
Can not upload SharePoint App to SharePoint App Catalog – when I was trying to upload the SharePoint app to the App Catalog site which I have downloaded from GitHub, I was not able to upload it – was getting the “The documents cannot be uploaded because different permissions are needed. Request the necessary permissions.”
In this “Failed to upgrade SharePoint products” troubleshooting article, we will learn about how to fix the upgrade database error when the SharePoint configuration wizard failed, basically, we might see the below two errors or exceptions: Failed to upgrade SharePoint Products Exception: The upgraded database schema doesn’t match the TargetSchema Issue Description (Failed to upgrade
In this “SharePoint Server Error” article, we will learn about when we get “Server error: http://go.microsoft.com/fwlink?LinkID=177673”  from SharePoint sites and how to fix it. Issue Description: SharePoint Server Error: http://go.microsoft.com/fwlink?LinkID=177673 During our SharePoint content database migration, we faced this issue. Let’s say we have migrated the content database from SharePoint one version to another version(for
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 © 2024 Global SharePoint. All rights reserved. |
