DocAve for SharePoint Migration

DocAve for SharePoint Migration

Now a day’s many organizations using the Docave Migration Tool for the migration purpose. In this article I am explaining the details of the tool. With DocAve SharePoint Migrator, administrators can perform full-fidelity content migration from previous versions of Microsoft SharePoint, such as SharePoint Server 2010 and SharePoint Server (MOSS) 2007, to SharePoint Server 2013, SharePoint Server 2010, and SharePoint Online at the site, subsite, or item level. DocAve’s efficient and reliable data transfer is unique in its ability to migrate content while retaining all of the associated metadata, letting organizations maximize their return on existing investments and gain more value from Microsoft’s latest release

Do cave tool is using for the below reasons: 

Migrate SharePoint content from previous SharePoint versions to the latest SharePoint version or SharePoint Online with full fidelity .

Reduce human errors, data loss, and migration times by automating the process of migration 

Plan migration jobs according to business needs with flexible job scheduling

.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

The Remote server returned an error(503) server unavailable or The HTTP service located at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc is too busy

The Remote server returned an error(503) server unavailable 
(or ) The HTTP service located at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc is too busy

Issue: when we try to browse the SharePoint site, we should get the error “The Remote server returned an error(503) server unavailable”. 

 or The HTTP service located at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc is too busy

Solution: the issue occur is due to the security Token service application pool. Follow the below steps to resolve the issue.

 1.    Ensure that the password provided to the user name for Token application pool is correct.

2.    Ensure that the “security Token service application” is in started state

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!