Troubleshooting an import that fails
This article guides you through the process of troubleshooting an import that fails. It provides steps to help you eliminate common causes for your problem by verifying that the configuration of your networking is correct.
Symptoms may include the following:
- No rows are returned
- Connectivity issues (log message)
- Import takes a really long time
- Import does not complete
- Import stopped in the middle
- Import says complete, but not all data is present
- User cannot log in through LDAP
- Scheduled import does not run at the defined time
- Data discrepency after report
- Data is truncated
- Import fails after upgrade
Determine whether any of the troubleshooting steps below are true for your environment. Each step provides a link to an article that can help you eliminate possible causes and take corrective action as necessary.
- Confirm that there have not been recent system admin changes on the customer side (for example, any effect of security policies, such as password changes) that are affecting the import.
- Confirm that there is not a connectivity or networking issue on the customer side.
- Determine if the import failed due to resource constraints on MID Server VM. For more information, see KB0538131: Determining if an import failed due to constraints on a MID Server installed on a VM.
|Note: If your problem still exists after trying the steps in this article: Submit an incident to Customer Support and note this Knowledge Base article ID (KB0538434) in the problem description. For more information, see Customer Support.|