Problem
description:
Troubleshooting done:-
We
have received the following error message while creating the site collection
underneath one web application.
Error message:
The operation that you are attempting to perform cannot be completed
successfully. No content databases in
the web application were available to store your site collection. The existing content databases may have
reached the maximum number of site collections, or be set to read-only, or be
offline, or may already contain a copy of this site collection. Create another content database for the Web
application and then try the operation again.
Troubleshooting done:-
If you see the error message then you will experience it is
somewhat misleading. How?
See-
1) Checked
the content database is attached or not [By means of Central Administration] -
Yes, it’s already there.
2) Checked
the maximum & minimum site collection number and its already max 5000 and
min 2000. The actual numbers of site collections are only 50! Strange!
3) Checked
the status of web application – whether its Read Only / content
prevented/locked/unlocked [By means of Central Administration]
4) Checked
the status from SQL end and it was fine.
This issue can be resolved in multiple ways-
Resolution:-
1)
Create
a new content database and check new site collections are getting created or
not.
2)
You
can also test this by creating a site collection in a different web application
– By this way you are trying to isolate the problem. Whether it’s restricted to
single web app/single content database/complete farm.
3)
Check
the database status –
i.
Central
administration
ii.
Application
management
iii.
Manage
content databases
iv.
Select
the appropriate web application from the dropdown
v.
Check
the status
vi.
In
my case, it’s showing error
Note: I would like to highlight that the above mentioned ‘error’
status does not make any impact on the existing site collections so nothing to
worry about it.
4) Execute IISRESET
and check the results
5) Check the status
from the SQL end and make sure there is no problem with the logs as the database
consists of mdf and ldf files, this problem might be occur due log files gets
full!
In
my case, it’s showing the database status as “Error” so I performed the
following steps-
1. Detach
the content database from the web application
2. IISRESET
3. Attach
the content database back & check the results.
Now
site collections can be created without any problems!
Issue
resolved! Happy SharePoint…
If
you have any queries/questions regarding the above mentioned information then
please let me know. I would be more than happy to help you as well as resolves
your issues, Thank you.
Reference:
Product applies
to:
1)
SharePoint
Server 2010
2)
SharePoint
Foundation 2010
