Articles in this section

KB Article: NoRule Folder – File Handling and Document Split Behavior

Overview

The NoRule folder stores files that do not match the file extensions defined in the TM Master database receive rules. These rules can be found under:

System → TM Exchange Client → Receive Rules (per installation)

If a file placed in the COMM folder does not meet the expected extension criteria, it will not be imported and will instead be moved automatically to the NoRule folder.


Supported File Extensions

For a file to be successfully imported, it must match one of the following supported replication file extensions (depending on which database is processing the import):

  • .o2u

  • .u2o

  • .ofu

  • .ufo

Any other file type detected in the COMM folder will be rejected and transferred to the NoRule folder.


Common Cause: Document Split Files

The files placed in the NoRule folder are often related to the splitting of document files.

This behaviour is most commonly observed on office installations, but it can also occur on vessel servers.


How File Splitting Works (TM Exchange)

This behaviour is controlled by the Max File Size setting:

System → TM Exchange Client → Settings → Max File Size

Example Scenario

  • Max file size is set to 1 MB

  • A replication file of 10 MB exists in the COMM folder

Result

TM Exchange will automatically:

  1. Split the 10 MB file into 10 individual 1 MB parts

  2. Send the split files to the destination system

  3. Reassemble the files back into a single 10 MB replication file on arrival

If the reassembly process does not complete successfully, the individual split files may appear in the COMM folder and eventually be moved to the NoRule folder due to invalid file extensions.


Document Resend Interval

Each database also has a configurable Document Resend Interval setting.

Default Setting

  • 4 days (can be adjusted per installation)

Behaviour

If the receiving database does not successfully import a document within the configured resend interval:

  1. The source database will resend the document

  2. This retry process will continue until the document is successfully received

  3. Once imported, the document is marked as complete and resend attempts stop


Recommendations

To prevent repeated NoRule folder entries and replication issues, verify the following on all installations:

  • Max File Size setting is appropriate and consistent

  • Document Resend Interval is correctly configured

  • TM Exchange receive rules are properly set

  • Network stability and replication performance are adequate


Important Note About NoRule Files

Once files are placed in the NoRule folder:

  • They are no longer used by the system

  • They will not be reprocessed or reimported

  • They can be safely archived or removed after investigation

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.