Determining if an import failed due to resource constraints on MID Server (VM) - Support and Troubleshooting

Determining if an import failed due to resource constraints on MID Server (VM) Description

Determining if an import failed due to resource constraints on a MID Server installed on VM

Problem Scheduled or manual imports are not updating or creating records in the desired table.

Symptoms Import set contains zero records MID Server and instance logs contain Blank column headers were found message

Cause As part of the JDBC or LDAP import process, remote GlideRecord queries are performed against the glide instance to pull data from sys_data_source , ldap_ou_config , and ldap_server_config .

This can be interrupted by a socket error.

Resolution If possible, upgrade to the latest Dublin release or above.

However, if upgrading is not an option, we recommend installing the associated MID Server on a different physical machine that does not have the same network load.