Table of Contents

Reasons for Timeout Issues with FORNAV File Service

Issue

The FORNAV File Service may report a timeout error during operations.

Possible Causes

Operation Takes Too Long

The most common cause of timeouts is that the requested operation simply takes too long to complete. This frequently occurs when scanning directories containing many files or subfolders.

  • Recommendation: Reduce the number of files/folders or reorganize data into smaller directories if possible.

Timeout Setting is Too Low

In older versions of the FORNAV extensions (before version 7.4), the default timeout was set to 10 seconds. From FORNAV version 7.4 onward, the default timeout is 60 seconds.

  • Recommendation:
    • Verify and adjust the timeout setting on the FORNAV Direct Print and File Setup page in Business Central.
    • Alternatively, set the timeout directly in AL code for custom implementations.

Routing Configuration Issues

Incorrect routing setup can lead to timeouts. Routing defines how print and file requests are handled.

  • Recommendation:
    Verify your routing configuration on the Direct Printer Routing page, accessible from the Direct Print and File Setup page in Business Central. Incorrect or missing routing rules can cause delays or timeouts.

Polling Misconfiguration

Timeouts can occur if polling is incorrectly configured in the config.json file for the FORNAV Direct Print and File Service.

  • Recommendation:
    • Review the polling settings in the config.json file.
    • Ensure polling intervals and settings are correctly configured according to FORNAV documentation.

Docker with Hyper-V Isolation and No SSL

Running Business Central in a Docker container with Hyper-V isolation enabled but without SSL configured can cause network timeouts.

  • Recommendation:
    • Enable SSL in the Business Central Docker environment.
    • Alternatively, consider changing the isolation mode or deploying outside of Docker.

Business Central Caching Issues

In Business Central 24.5 or newer (on-premises) with multiple service tiers, using FORNAV extensions version 7.3 or earlier can result in timeouts due to changes in Business Central database caching.

  • Recommendation:
    • Upgrade FORNAV extensions to version 7.4 or newer to resolve caching compatibility issues.

Expired Demo Period or Invalid License

A timeout can occur if the 30-day demo period for FORNAV has expired and Business Central does not have a valid FORNAV license installed.

  • Recommendation:
    • Verify the licensing status in Business Central.
    • Install a valid FORNAV license if the demo period has expired.

Summary

Timeout errors in FORNAV File Service can be caused by:

  • Lengthy operations (e.g., large folder scans).
  • Low timeout settings (adjustable in FORNAV Direct Print and File Setup or AL code).
  • Routing misconfiguration (check Direct Printer Routing page).
  • Incorrect polling configuration (config.json).
  • Docker environments using Hyper-V without SSL.
  • Business Central caching issues (upgrade FORNAV extensions to version 7.4 or newer if applicable).
  • Expired demo period or missing valid FORNAV license.