Skip to content
IFS Wire

Community · Question

Cleaning an unbounded FSM 6 Mobile Service download folder on-premise

Asked by IFS Wire DeskEditorial · 10 Nov 2026 · 0 views

Type:
Technical
Version:
FSM 6 Update 29

Sourced from IFS Community · original thread · roklde

0

On an on-premise FSM 6 Update 29 setup, Mobile Service runs on a separate DMZ server and its download folder has grown to roughly 85 GB with about 100,000 files. There is no scheduled process or parameter that clears the folder. The MOBILE DEVICE CLEANUP job removes device records and messages in the database, but it does not delete files on the server.

The folder holds cached attachments, old ZIP copies, PERSON__DEVICESEQ.zip initialization databases, image ZIPs, and leftover .tmp files. How do customers clean this folder? Are old init ZIPs still needed after a device has downloaded them? How are cached attachments used? Can leftover .tmp files cause HTTP404 when a device looks for attachments?

Technical details Product: FSM 6 Update 29, on-premise. Mobile Service on a separate DMZ server. Folder contents observed: cached attachments, old ZIP copies, PERSON__DEVICESEQ.zip init databases, image ZIPs, leftover .tmp files. Process name: MOBILE DEVICE CLEANUP (cleans DB device records/messages only, not server files). Error when attachments missing: HTTP404. Cleanup approach reported: PowerShell script or manual.

Any attachments are visible to signed-in members.

1 answer

0

✓ Accepted answer

There is no out-of-the-box cleanup for the Mobile Service download folder. Customers typically clear it with a scheduled PowerShell script or by manual deletion.

Init ZIPs (PERSON__DEVICESEQ.zip and similar) are not needed once the mobile device has already downloaded them.

Attachments are fetched when the mobile device activates/initializes and again during device sync. If the device can no longer find an attachment on the server, the result is HTTP404 (not found).

In the source thread, the asker planned to schedule a PowerShell cleanup based on this guidance.

Prerequisites and limitations No OOTB scheduled cleanup of the download folder. MOBILE DEVICE CLEANUP must not be relied on for file-system cleanup. Removing init ZIPs only after devices have downloaded them; removing attachments that devices still need can surface HTTP404. PowerShell/manual cleanup is a customer-owned operational practice, not a product feature.

Sourced from IFS Community · original thread · roklde

Answered by IFS Wire DeskEditorial · 10 Nov 2026