Workflow problems after you connect to a SharePoint Online or SharePoint Server 2013 site
Problem
Consider the following scenario.
When you use SharePoint Designer 2010, you experience one or more of the following issues:
When you try to edit or publish a workflow, you receive one of the following error messages:
- SharePoint Designer cannot display the item.
- The list of workflow actions on the server references an assembly that does not exist. Some actions will not be available.
You take steps to create a new list workflow, site workflow, or reusable workflow. However, after you have completed the steps, the item isn't present.
When you connect to a SharePoint Online site, you receive the following error message:
- Microsoft SharePoint Designer cannot be used to edit web sites on servers different from SharePoint Server 2010.
When you connect to a SharePoint site, you receive the following error message:
- This web site has been configured to disallow editing with SharePoint Designer.
When you experience one or more of these issues, the following conditions are also true:
- You're using SharePoint Online.
- You've upgraded your on-premises installation of SharePoint Server 2010 to SharePoint Server 2013.
- You've upgraded your installation of SharePoint Foundation 2010 to SharePoint Foundation 2013.
Note
If you're using SharePoint Server 2010, this article doesn't apply to your scenario.
Solution
To resolve these issues, install SharePoint Designer 2013.
Note
You can install SharePoint Designer 2013 alongside SharePoint Designer 2010. However, we recommend that you uninstall SharePoint Designer 2010 before you install SharePoint Designer 2013.
More information
If you're experiencing the message "This web site has been configured to disallow editing with SharePoint Designer" in an on-premises installation of SharePoint Foundation 2013 or SharePoint Server 2013, be aware that a site definition configuration may be responsible for the message. For more information, go to Project Element (Site).
If changes were made to the site by using SharePoint Designer 2010 before you installed SharePoint Designer 2013, you may continue to experience one or more of the symptoms in the "Problem" section. If you're still experiencing these issues, follow these steps:
Exit SharePoint Designer 2013. If you're using the Click-to-Run version of SharePoint Designer 2013, go to step 4. Otherwise, go to step 2.
Install the SharePoint Designer 2013 hotfix that's dated June 11, 2013. For more information, see the Description of the SharePoint Designer 2013 hotfix package (Spd-x-none.msp): June 11, 2013.
Note
This step doesn't apply if you're using the Click-to-Run version of SharePoint 2013.
Start SharePoint Designer 2013, and then connect to your SharePoint site. If the issue persists, go to the next step.
On the local computer, browse to the following folder:
C:\Users\username\AppData\Local\Microsoft\WebsiteCache
Note
To locate some of the files and folders, you may have to configure File Explorer or Windows Explorer to show hidden files, folders, and drives. To do this, see Show hidden files for specific steps for your operating system.
Delete all the files and folders that are present.
On the local computer, browse to the following folder:
C:\Users\username\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache
Delete all the files and folders that are present.
On the local computer, browse to the following folder:
C:\Users\username\AppData\Roaming\Microsoft\Web Server Extensions\Cache
Delete all the files and folders that are present.
Start SharePoint Designer 2013, and proceed with your original intentions.
Still need help? Go to SharePoint Community.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for