Error
440 Login Timeout.
Cause
There are three causes for this issue happens:
- Invalid credentials to access the configured mailbox.
- Over-utilized resources.
- TLS Settings, MigrationWiz only supports TLS 1.2 at this time.
Resolution
Invalid Credentials
The most common problem when encountering this error is that the user name and password specified cannot access the mailbox.
- You can verify that the username and password are correct by testing mailbox access using OWA.
- If your connector is set to use administrative access, make sure to log in to the mailbox using administrator credentials (since MigrationWiz does it).
- If you have verified that the credentials are correct, enter the credentials into MigrationWiz, and resubmit the mailbox for migration. It may be possible that the credentials were specified incorrectly.
Over-utilized Resources
If you have verified that your credentials are working properly and cannot still log in, you may be over-utilizing resources.
The first thing to do is attempt to open your OWA URL from an external network from a system that is not joined to your domain. If OWA is loaded promptly, check your server resources:
- Check server CPU usage
- Check memory usage
- Check disk I/O usage using a performance monitor
- Check for over-utilization of the network
The most common problem encountered is the over-utilization of the network. This means that you are attempting to migrate too many mailboxes simultaneously, and do not have enough bandwidth to execute them. Refer to our article describing network utilization. Once you have a better understanding of network utilization, configure the correct number of mailboxes you can migrate simultaneously.
TLS Settings
MigrationWiz only supports TLS 1.2 at this time. If the endpoint only allows TLS 1.0, it must be updated to TLS 1.2.