Summary

The FlexNet Manager Suite (FNMS) export to ServiceNow fails with Error Code 1, and no corresponding import transaction is created in ServiceNow.

Note: This issue is most commonly observed in FNMS Cloud environments.

Symptoms

The integration between FNMS and ServiceNow stops functioning, and data exports are rejected by ServiceNow.

The following symptoms may be observed:

On the FNMS Side

• ServiceNow export jobs fail with Error Code 1.
• Export logs show the request was rejected by ServiceNow.

On the ServiceNow Side

• No import transaction is created.
• No import run is visible in Import Transactions.
• Import runs may remain in a Waiting or Processing state without completion.

Cause

One possible cause is that the export payload exceeds the maximum inbound request size allowed by ServiceNow.

By default, ServiceNow supports inbound REST payloads of up to 10 MB. If the exported data exceeds this limit, ServiceNow may reject the request before creating an import transaction.

Resolution

Verify whether the following ServiceNow system property exists and is configured appropriately:

To check the property:

1. Log in to ServiceNow with administrative privileges.
2. Navigate to System Properties.
3. Open sys_properties.list.
4. Search for the property: glide.rest.scripted.max_inbound_content_length_mb
5. Review the configured value and determine whether it is sufficient for the size of the payload being exported from FNMS.

If the payload size exceeds the configured limit, consider increasing the property value in accordance with your organization's ServiceNow policies and performance guidelines.

Additional Information

When this issue occurs, ServiceNow may reject the request before an import transaction is created, making it appear as though no data was received. Reviewing both the FNMS export logs and the ServiceNow system property configuration can help identify whether the request size is the root cause of the failure.