Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Error on 'create site collection'

  Asked By: Chance    Date: Jul 21    Category: Sharepoint    Views: 11548

I'm getting the following error after clicking on create site
collection in central admin:
"There are no inclusions defined for this Web application."

I've successfully created site collections using the same procedure
as for this one. I'd set this one up previously but it had some
oddities (i.e., only some of the site actions menu items were
displayed) so I deleted it and recreated it. The second time around,
when I went to add site content types, that page was essentially
blank. The third time, I deleted it using stsadm.

The only other complicating factor I can think of is I'm using
managed paths (explicit) to make the URLs as desired....but again,
it's worked in all other cases using the same pattern.

And now I can't create site collections at all.

Google has been no help. Anyone have any ideas?!



3 Answers Found

Answer #1    Answered By: Gobinda Navalagi     Answered On: Jul 21

Occasionally, (for reasons unbeknownst to me) you must delete and re-add
an explicit managed path when deleting the site  collection contained
therein. This is especially true if the SQL Server, or some other
connectivity issue, was thrashing during the site collection  deletion

I am assuming you understand the difference between wildcard and
explicit managed paths?

Answer #2    Answered By: Rose Silva     Answered On: Jul 21

I have deleted  and recreated the managed
path (several times). Apparently, because the path name was already
used, MOSS doesn't recognize that it's *really* available again
(incomplete site  collection deletion?). I have been able to "trick"
MOSS into creating a new site by using a wildcard directory and then
typing in the name (e.g., schools/schoolname where schools/ is
wildcard type). But, then my custom content  types are not available.

I tried using the dbrepair operation, but it finds 0 orphans. MS
Support has suggested creating a new config db and reattaching
everything, but that seems a bit extreme. Isn't there any better way
to clean up the previously deleted site collection? An easy solution
would be to create  a path with a name that has never been used, but
I should have mentioned that I need to keep the URL from the
original site (this is for a public facing website).

Any ideas short of changing the name or going through the process of
creating a new config db, etc.?

Answer #3    Answered By: Alka Sarabhai     Answered On: Jul 21

1. The managed path is actually stored in the content  DB. So,
worse case scenario is removing the content database that hosted the
site collection  in question.

2. The orphaned managed path object should be in the contentDB,
not the configDB. You could try the stsadm.exe -o preparetomove command.
It will clean up a contentDB.

Didn't find what you were looking for? Find more on Error on 'create site collection' Or get search suggestion and latest updates.