Return
-
Title
Troubleshoot Office 365 Ingestion Errors -
Description
Troubleshoot Office 365 Ingestion Errors -
Resolution
Issue
The following article references further articles with specific Office 365 Ingestion/Import Errors that have been observed when doing migrations with Archive Shuttle
Solution- Error in IMessage.GetRecipientTable: MAPI_E_NOT_ENOUGH_MEMORY
- The process cannot access the file
- Office 365 Throttling and Multiple Service Accounts
- Office 365 Module may log: The parameters passed to the cmdlet represent a managed account, which doesn’t match the namespace state, which is federated
- Archive Shuttle Office 365 Module Logs: Too many users found with EMail – primarySMTP
- Ingesting into Office 365 may report an error: Items and SMTP Mailbox have to be filled in Items Container
- Permissions error logged in Office 365 Module
- Archive Shuttle Office 365 Module Logs: Exchange service is busy
- Office 365 module might report 401 unauthorized from time to time
- Access is denied message is logged from time to time when ingesting into Office 365
- Office 365 module logs an error: Add the user name and password or change the authentication mechanism and try the request again
- “The user name or password is incorrect” is logged during Office 365 ingest
- Archive Shuttle Office 365 Module Logs: EmailAddress element called as invalid according to its data type
- Error while connecting to Office365 | Autodiscover service couldn’t be located
- Office 365 Module Logs an Error: Error: [System.ApplicationException: The request timed out.]
- Office 365 Module Logs an Error: A positional parameter cannot be found that accepts argument