Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Property "com.glide.attachment.max_size" of 3MB causes some LDAP records not to be imported if using MID server - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Property "com.glide.attachment.max_size" of 3MB causes some LDAP records not to be imported if using MID server
KB0623372

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


1827 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

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.

what is showed on the load data

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.<init>(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.

 Cause of the problem


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.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • Screen Shot 2017-06-23 at 2.08.27 PM.png
  • Size_exceeds_error.png

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.