SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

SharePoint Designer tends to behave itself and function as well as it is supposed. That is until yesterday. In the contents of the Lists and Libraries tab for the main/top level site shows nothing. There are supposed to be a whole bunch of lists and libraries there, but instead it only shows a message saying, "There are no items to show in this view." It's a similar situation for the Workflows tab as well. Refreshing the lists, resetting IIS and rebooting the server has done nothing to improve the situation.

The View All Site Content option in the Site Actions menu for the top level site displays all the lists, libraries, etc. All other tabs in SharePoint Designer display everything they're supposed to display, such as Content Types, Subsites, Files, etc. The Lists and Libraries tab, as well as Workflows and all other tabs for all the Subsites seem to work fine and displays everything they are supposed to display. It's just the top level site that seems to have this problem.

I'm not sure what has happened here, nor do I know how to approach this issue. Any help and advice is most welcome.

share|improve this question

It might be late, but here it goes for those who experience the same problem in the future:

On the site for which SPD is bugged (e.g. not showing the existing lists), locate a list that does not work and delete it. Broken lists actually cause this problem.

If you have no broken lists on your site, see if you can locate a list that has previously been created by a .wsp solution/feature that has been disabled. This is also a common cause for the issue.

share|improve this answer
Thank you for the info @Dimitrij. I eventually found this out through another thread as well as a lot of time using my "Google Fu". Basically, if it's broken in the web interface and breaks SPD, then delete it using PowerShell. After doing that a few times, I actually decided to start spending more time learning PowerShell. Thank you again. – RX3R0 Aug 15 '13 at 17:44
Furthering Dimitrij's good answer, see for an excellent method to do this. [Why not include this as a comment? I don't have the required reputation.] – mcook Apr 29 '15 at 4:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.