Firewall configuration for 07-07/10-10 migration

Adding a farm requires the same configuration as described in Help.
For 07-07 migration different firewall configuration is required:

1. When creating a migration job the BrowserBroker service connnects to the remote BrowserAgent service.
Their ports can be found in the "server.socket_port" variable in the following files:
Quest Software\Migration Manager for SharePoint\Web Interface\SharePoint Browser\SPInfo.conf - for BrowserAgent port
Quest Software\Migration Manager for SharePoint\Web Interface\SharePoint Browser\SPInfoBroker.conf - for BrowserBroker port.

So, from a server with console the outbond connection for the Broker service should be allowed, on a server without console - inbound connection for the Agent service.

2. Source and Target serivces on the corresponding servers should have access to Repository database:

Outbound connections for pythonservice.exe should be allowed on both servers, SQL ports should be opened on the server wher Repository database is located.

3. Source service creates shared folder on the source server and exports content to the folder, target service connects to the folder remotely and uses it foe importing:

Outbound connection from the target server should be allowed for the pythonservice.exe and inbound connections should be allowed on the source server for the shared folder (SMB port 445)

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

07/10 reorg: Access denied error on a list veiw importing

Issue:

You have a customized view with a web part in a document library.

The following error message occurs on import:

(-2147352567, 'Exception occurred.', (0, u'', u'Access denied.', None, 0, -2147024891), None)

If you go to the import.log file, you see the following:

[7/9/2010 4:27:37 PM]: Progress: Importing File Shared Documents/Forms/AllItems.aspx.

[7/9/2010 4:27:37 PM]: FatalError: Access denied.
   at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException ex)
   at Microsoft.SharePoint.Library.SPRequest.PatchUrl(String bstrUrl, String bstrWebRelFileUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)
   at Microsoft.SharePoint.Deployment.ImportObjectManager.FixLinkInFile(String fileUrl, Guid webId, String oldTargetUrl, String newTargetUrl)
   at Microsoft.SharePoint.Deployment.LinkSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
   at Microsoft.SharePoint.Deployment.FileSerializer.UpdateLinks(SPFile file, String linksXml, StreamingContext context, ISurrogateSelector selector)
   at Microsoft.SharePoint.Deployment.FileSerializer.UpdateFileAssocData(SPFile file, SPWeb web, Guid id, String fileUrl, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, StreamingContext context, ISurrogateSelector selector, ImportObjectManager objectManager)
   at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFileAndAssocData(Object fileOrListItem, SPWeb web, Guid id, String& fileUrl, Boolean fileExistsInDb, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, StreamingContext context, ISurrogateSelector selector)
   at Microsoft.SharePoint.Deployment.FileSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
   at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)
   at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)
   at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
   at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
   at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)
   at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
   at Microsoft.SharePoint.Deployment.SPImport.Run()

How to fix:

The issue may occur with the following web parts:

• filter web part
• content editor web part containing a link to another list/doc lib

As a workaround delete the web part or the whole list view on the source and repeat migration.

07-07/10-10: Migrate sub-site with a custom permission level

Issue:
You see the following error in the import.log for a migration job:

Progress: Importing Role Assignment for "sub-site".
FatalError: The given key was not present in the dictionary.
 
Error description:
By default permission levels of a site are inherited from its top level site (i.e. site collection). The issue occurs in the following scenario:
There is the http://source site collection and the http://source/sub-site sub-site. The "sub-site" has a user (or group) with permissions assigned via a custom permission level. The permission levels are inherited from the site collection.
When the "sub-site" is migrated to a new http://target site collection, the custom permission level is not created on the sub-site level as it should be created on site collection level. If the target site collection does not have the custom permission level, the error occurs.

How to fix:
There are two workarounds:

1. Create the custom permission level in the target site collection manually and retry import for the migration job
2. Break inheritance of permission levels on the source "sub-site" and restart migration job.

2007/2010 reorganization: After migration you see two lists with the same name in the Site Content

After migration of a list using SharePoint 2007 /2010 reorganization scenario you could see duplicated lists on the target site:

Actually both links open the same list.

As a workaround:

1. Open the list settings.
2. Set a non-default view as a default.The duplicated link is gone.
3. Switch back to the desired default view.