Error when opening site in SharePoint Designer 2013

https://www.brightwork.com/product-blog/error-when-opening-site-in-sharepoint-designer-2013#.Wd8YiWiCzDc


This week we came across an interesting error which took us some time to troubleshoot. There is a lot of conflicting information on the error online so I thought I would give you my experience.
The error occurs when you attempt to open a site using SharePoint Designer 2013. You receive the following. The server could not complete your request. For more specific information, click the Details button. Designer will also crash hand you will need to kill the task in your task manager.
SPDesigner
On a side note when you choose the details button for more specific information you are returned a blank form which is unhelpful.
The solution was to enable some authentication options on the SharePoint Web Services site in iis.
services
I enabled Anonymous Authentication, Asp.net Impersonation, Forms Authentication and Windows authentication.  I found these were disabled when I inspected them. Finally run an iisreset.
Interestingly this was not a new server and users had used SharePoint Designer with sites only the week prior. Unfortunately we were unable to discover the root cause of the issue. Its possible changes were made to Authentication but highly improbable. If anyone has any suggestions as to what may have caused these changes to be required please do comment below. Hope this helps you in the future.

Comments

Post a Comment

Popular posts from this blog

SharePoint Integration with IIS

Image
Before discussing the Integration, we will discuss the architecture of SharePoint at the architecture level. The diagram represents the architecture of SharePoint and split into two halves. The Left-half is administrator world and the right-half is the end-user world. Everything in right half resides in SharePoint content database. Let's continue with some terminologies before goes into deep dive.  Farm A farm is a logical architecture or logical grouping of SharePoint servers that share common resources of SharePoint. It can be a single machine or more than one machine. The farm is differentiated on their tier levels. Might be possible Farm can be 1to N-tier. Installation can either be done at 1 machine to N. Most of the cases in production you have to choose at least 5-tier architecture for application Server, front-end  Server , SQL, AD+DNS, Office Web App Server and Exchange; you can add more than one application server, Front-End etc at any level. Configuration Da
Read more

How to Create an Auto-Incrementing Number Field in a SharePoint List

Auto-numbering is a common requirement when working with SharePoint lists. You may want an auto-incrementing number on Issues list items such as “ISS-001” and so on. If you try using calculated column with ID field and entered a formula such as = (“ISS-00” & [ID]), this won’t work for new items! The reason being ID field is filled ONLY after the item is created. Here are the steps to create an auto-incrementing number field in a SharePoint list designer workflow: Create a new column, such as :  Increment Number  in issue list with Number type. Make this column hidden in a view. Create another column, such as :  Issue No.  in issue list with Formula type and add the following formula = “ISS-00” & [ Increment Number ]. This Column will show the increment items’ numbers in the list. Open SharePoint designer, create new list workflow (for issues list). Add a workflow action: “Update list Item” >> Current Item >> Add >> Set this field to your Target field
Read more

Error:Installing product D:\exchangeserver.msi failed. Fatal error during installation. Error code is 1603.

Error 1603 is a known Microsoft/environmental issue. This error message is displayed by the Microsoft Windows Installer Engine and is a general error code that indicates a problem occurred during the installation. The following is a non-exhaustive list of known causes for this error. Short file name creation is disabled on the affected machine. An Install Script custom action is prototyped incorrectly. A file is locked and cannot be overwritten. The Microsoft Windows Installer Service is not installed correctly. The Windows Temp folders are full. The setup was corrupted after installation and therefore fails with this error during un-installation. An older version of Install Shield Developer is being used. A general error occurred during the installation. Print and File sharing is not installed or enabled when installing MSDE 2000. For more information please visit -  http://support.microsoft.com/kb/834484/en-us Resolution To resolve this issue, complete the fo
Read more