What to do in case of schedule failures

Created by Robert Cross, Modified on Mon, 14 Jul, 2025 at 11:01 AM by Robert Cross

Experiencing a data sync failure? In many cases, sync issues can be diagnosed and resolved quickly by following the steps below.


Step 1: Check the Logs

Start by reviewing the sync failure logs, which are available through:

  • Email Notifications (if you’ve enabled alerts)

  • Data Lake Sync PortalSync JobsLog Details

The logs will typically contain error messages or codes that point to the root cause of the failure.


Common Error Causes

Here are some of the most frequent reasons for a data sync to fail:

  • Expired Database Password: The database user account used by Data Lake Sync may have an expired password. Update it and ensure the new credentials are active.

  • Locked User Account: Excessive login attempts, policy violations, or manual locks can disable the database user account. Verify the account status with your DBA team.

  • Database or Network Unavailable: The destination database may have been offline, rebooting, or unreachable due to firewall or routing issues at the time of sync.

  • Infor Service Account Removed: The service user created in Infor Portal may have been deleted or lost necessary security roles, which will block sync job execution.


Step 2: Take Action Based on the Log

Once you identify the cause:

  • Fix expired passwords or unlock the user account in the destination database.

  • Check network/firewall access to confirm Data Lake Sync still has external access to your database.

  • Verify the Infor Ming.le user is still active and assigned the required security roles.

See the Data Lake Sync Setup Guide for role requirements.


Step 3: Wait for the Next Scheduled Sync

If the log shows a temporary issue (e.g., a brief network outage or database restart), it may resolve on its own.

Let the next scheduled sync run, then re-check the status in the portal or via notification email.


Step 4: Contact Support

If the issue persists after taking corrective steps:

  1. Gather the following information:

    • Time and date of the failed sync

    • Error messages or log excerpts

    • Affected table(s) or sync job name

    • Confirmation of database/network status

    • Details of any recent system changes

  2. Contact the support team and include the above information to expedite resolution.

Support Contact: support@datalakesync.com


By methodically checking logs, addressing root causes, and involving support when necessary, you can restore your Data Lake Sync processes quickly and confidently.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article