Share
Report
2Hi everyone,
I'm working on a Master Data Management (MDM) setup in Business Central SaaS, and I'm running into an issue with job queue entries crashing shortly after setup.
Here's our setup:
- One parent company (OPERATIONS) acting as the MDM source
- Multiple child companies pulling data from OPERATIONS via the native BC MDM module
- One child company (PARAM) configured as our template company
- One parent company (OPERATIONS) acting as the MDM source
- Multiple child companies pulling data from OPERATIONS via the native BC MDM module
- One child company (PARAM) configured as our template company
The problem:
I configured the MDM subscription in PARAM on April 30th around 4:50 PM. The job queue entries were created automatically (one per table — Customers, Vendors, Countries, Payment Terms, etc.), all running Codeunit 5339 (Integration Synch. Job Runner).
I configured the MDM subscription in PARAM on April 30th around 4:50 PM. The job queue entries were created automatically (one per table — Customers, Vendors, Countries, Payment Terms, etc.), all running Codeunit 5339 (Integration Synch. Job Runner).
About 40 minutes later, the Customer sync job fell into Error status with the following message:
"A problem occurred and the task stopped. System updates or regular maintenance processes are probably the cause."
"A problem occurred and the task stopped. System updates or regular maintenance processes are probably the cause."
All other job queue entries then went into Suspended (inactivity timeout) status and never restarted automatically. As a result, no data changes made in OPERATIONS since April 30th were replicated to PARAM.
The job queue entries were running under a regular user account (not a dedicated service account).
My questions:
1. Is it expected that MDM job queue entries do not restart automatically after a crash or BC maintenance?
2. Is using a dedicated service account mandatory for MDM job queue entries to run reliably in BC SaaS?
3. Is there a recommended way to set up MDM job queue entries so they are resilient to BC automatic maintenance windows?
1. Is it expected that MDM job queue entries do not restart automatically after a crash or BC maintenance?
2. Is using a dedicated service account mandatory for MDM job queue entries to run reliably in BC SaaS?
3. Is there a recommended way to set up MDM job queue entries so they are resilient to BC automatic maintenance windows?
Thank you in advance!
Categories:
I have the same question (0)
All responses (
Answers (
