Sometimes, we may notice this “We apologize for the inconvenience, but we’ve made OneDrive and sites read-only while we do some maintenance.” error message both in SharePoint on-premise as well as online – in this article, we will see what is the “We apologize for the inconvenience, but we’ve made OneDrive and sites read-only while
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 longer available.).”,
In this article, we will learn how to troubleshoot issues that you may experience when you use the “Open with Explorer” command in SharePoint Online. Before we get into the actual problem and resolution we must know about the “Open with Explorer” in SharePoint Online. The Open with Explorer command doesn’t work in the Microsoft
Invalid issuer or signature – sometimes, we get the error “[SecurityTokenException: Invalid issuer or signature.]” in SharePoint online provider hosted app. In this troubleshooting technique, we will see how to fix the “SecurityTokenException: Invalid issuer or signature.” error in the SharePoint Online office 365. Scenario: Invalid issuer or signature Let’s say we have a provider-hosted
Open aspx file Online – many times we might observe strange behavior in modern SharePoint Online while we upload a custom .aspx file in SharePoint Pages or Site Pages library, and try to open it in the browser – what will happen is, it will be downloading the .aspx file instead of browsing – so,
Your tenant administrator has to approve this app – recently I was working with the SharePoint modernization scanner tool, where one of the authentication methods was “Azure ACS App Only”. I am very hands-on to generate the client id and client secret because previously many times I did that, so with confidence, I started generating
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
The page could not be created. Custom Scripting might be deactivated on the destination site – these days I have been working with the SharePoint modern communication site – and facing different types of issues. One of the issues – I have faced is “The page could not be created. Custom Scripting might be deactivated
![[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)
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)
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
| Contact Us: support@global-sharepoint.com | Support this site| Privacy Policy| Sitemap | Copyright © 2023 Global SharePoint. All rights reserved. |
