To perform a successful initial content deployment from a publishing site the destination has to be an empty site.
This is not to be confused with the <blank> site template.
I have had some success when picking the <choose template later> option in the site creation page in Central Admin but sometimes even this fails.
The only sure way of creating a blank site is to use the following stsadm command
STSADM.EXE -o createsite -url <site-collection-url> -ownerlogin <domain\username> -owneremail <email@address>
Sometimes if a back up fails or for some other reason you SharePoint sites can site can be left quiesced and/or the site collections and central admin site will be locked.
Some of the symptoms of a quiesced or locked farm or site can be a failing content deployment, or users complaining that they can’t edit and have lost their permissions.
Unlike SharePoint 2007 you can no longer unquiesce a farm through central admin unless you add a custom solution such as the one from estruyf .
You have to use PowerShell. Here is the command.
stsadm -o unquiescefarm
Even after running the above command I have still found that some of sites (including central admin) are locked.
You can check you site collections and central admin site are not locked by running the following command
stsadm -o getsitelock -url http://<site>
You can update/unlock using
stsadm –o setsitelock –url http://<site> –lock none
If you go to your SharePoint site and your search box is missing then your search service isn’t running correctly here are things that I have done in the past to get it going
- Perform an IIS reset (quite often this gets everything going again)
- In Central Admin go to services on farm (http://<CentralAdminSite>/_admin/Server.aspx) and check your search service is running.
- In ‘Services’ on your server check that the search services are running.
- In IIS check that your App pools for the Search Service (and any others SharePoint Services) are running – none should have a little black square. If they are not, start them and check after a few minutes to see if they are still running, if not check the username and passwords they are running under (see 5.)
- In the app pool right click and select advanced settings then re-enter the identity name and password
- Check search scopes are set up correctly
- If all of the above fails you may have to resort to creating a Search Service Application in central admin. (http:// <CentralAdminSite>/_admin/ServiceApplications.aspx) – Remember to associate you Web Applications to this new Search Service once you have it all configured