"File not found" error when you open target site.

Issue:

The migration completed successfully with no errors, but when you try to open the target site you receive the File Not Found error:

 The problem is that the master page of the target site (e.g. default.aspx) points to the wrong page layout. This happens because it links to a layout which does not exist in the target site collection. Usually it happens when master page is inherited from the parent site but you migrate the child site only.

Example:

You have http://source/test sub-site whose default.aspx page is linked to a custom master page “Custom.master” located in the top level site.

The target site collection (http://target) does not have the "Custom.master" page. When you migrate the sub-site under the target site collection, you receive the error when open the target site. 

You should copy master page from source to the target manually using SharePoint Designer.

To find out which master page is used:

1. Open the migrated target sub-site in SharePoint Designer.
2. Open default.aspx. The master page relative URL is written in the top level corner:
   

Note: The URL above means that the master page is located in the site collection master page gallery.


To copy the master page:

1. Open the source site collection (http://source) in SharePoint Designer and move to the _catalogs/masterpage
2.  Copy the Custom.master page
3.  Open th target site collection in SharePoint Designer and copy the master page to the _catalogs/masterpage

When the master page is copied you can successfully access target site.

What does the "0x80040E14" error mean

During a migration the 0x80040E14 error may occur. The error occurs when it is unable to complete an action on SQL server. You nay see either of the following errors:

' Unable to complete this operation.  Please contact your administrator.’

'Exception from HRESULT: 0x80040E14’

How to fix:

If you see one of the following messages in Issue report or log files, you need to check the following:

1.     Target SQL server data drive is not full

2.     .mdf and .ldf files of target content database haven't reached their full allocated size

3.     Target content database files are set to increase when full.

Note: There can be another reason for the “0x80040E14” error. Refer to the following Microsoft article for more detailed information: http://support.microsoft.com/kb/841216

Gradual Site Delete: Gradual deletion of site collection in SharePoint 2010

When you delete a Site Collection in SharePoint 2010 from Central Administration or from the site collection settings it is being deleted gradually.
The gradual deletion is performed by the Timer Job Definition called Gradual Site Delete.
In few words:
 The site reference is deleted from SiteMap and Sites tables of configuration and content databases and added into the SiteDeletion table. The Site collection is unavailable for users. But sub-sites still exist in the Webs table of content database. This behavior can cause some issues for third-party tools which read these tables.
 The Gradual Site Delete Timer Job definition is scheduled to be running one time a day. It can be started manually from Central Administration -> Monitoring -> Review job definitions -> Gradual Site Delete.
Here you can edit the timer job or run the job immediately

Refer the following article for more detailed information about the Gradual Site Delete timer job definition.

To delete the site collection completely use the following PowerShell command:

Remove-SPSite -Identity "<URL>"