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

After detaching a database in SharePoint then subsequently deleting in SQL Server I have been getting 404 Errors at my root site collection default.aspx page, and a few other random site collections for some strange reason, I should note that:

A) That root site collection never was even on my content database that I deleted
B) Site collections that were on that content database, but were moved onto other content databases still are functioning normally.
C) This was the "Original" Content database, it spun up with the web application but was to be phased out for better database servers. We had been moving everyone off to different databases.

This is completely bizzarre. Any suggestions on troubleshooting 404 messages with SharePoint in general will likely be appreciated here.

share|improve this question
up vote 0 down vote accepted

Well we figured it out...for some reason some publish data was removed and a check-out/check-in of the default.aspx file fixed the problem. We have a solution but I'm now extremely curious as to underlying cause...

share|improve this answer

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.