![[Fixed]: How to fix No gulpfile found in SPFx framework project](https://i0.wp.com/global-sharepoint.com/wp-content/uploads/2020/07/Fixed-How-to-fix-No-gulpfile-found-in-SPFx-framework-project.jpg?fit=961%2C539&ssl=1 "[Fixed]: How to fix No gulpfile found error in SPFx framework project 1")
No gulpfile found error in SPFx – when we work on the SPFx framework project, after running the “yo @microsoft/sharepoint” command, if we try to run the “Gulp serve” or “Gulp build” command we will get the error “No gulpfile found“. What is the root cause of the “No gulpfile found” error (No gulpfile found
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) 7")
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) 9")
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] Fix the "The term 'Get-SPWeb' is not recognized as the name of a cmdlet, function" PowerShell error](https://i0.wp.com/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?fit=959%2C532&ssl=1 "[Solved]: \"The term 'Get-SPWeb' is not recognized as the name of a cmdlet, function\" PowerShell error 11")
In this “The term ‘Get-SPWeb’ is not recognized” troubleshooting article, 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
| Contact Us: support@global-sharepoint.com | Support this site| Privacy Policy| Sitemap | Copyright © 2024 Global SharePoint. All rights reserved. |
