Property "com.glide.attachment.max_size" of 3MB causes some LDAP records not to be imported if using MID server - Support and Troubleshooting

Property "com.glide.attachment.max_size" of 3MB causes some LDAP records not to be imported if using MID server Issue  Property com.glide.attachment.max_size of 3 MB causes some LDAP records not to be imported if using MID server

Problem The import set related to the data load shows the Load completed field as empty even though the status of the import set is Processed.

Symptoms The system logs and testing the data source "Load all data" displays: GlideRecord not a SYS_ATTACHMENT record .

The localhost logs includes the following entries:

2017-06-22 17:30:58 (166) worker.0 worker.0 SEVERE *** ERROR *** com.glide.db.impex.LDAPProbeLoader java.lang.IllegalArgumentException: GlideRecord not a SYS_ATTACHMENT record at com.glide.ui.SysAttachmentInputStream. (SysAttachmentInputStream.java:73) Cause The MID server tried to create an attachment with the data received from the LDAP query; however, it exceeded the value set on the com.glide.attachment.max_size system property.

Resolution In the short term, set the sys_properties com.glide.attachment.max_size to a higher value.

In the long term, consider tuning your LDAP query to return only the required attributes. For example, if the attributes field is empty on the LDAP server form, it will try to query and retrieve all of the attributes of the records from the LDAP server including binaries, which increases the amount of data. Therefore, it could exceed the attachment limit set.

For tips about how to set the LDAP attribute, see the community article Setting the attributes to reduce LDAP import times .