From 991287a40a4ad2e5407a9dd90b2485bfa66a01ea Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Fri, 26 Sep 2025 11:53:45 -0700 Subject: [PATCH 01/29] Add files via upload --- .../adyen-connector-eft-terminal-id.md | 37 +++++++++++++++++++ ...g-sales-orders-fail-stale-authorization.md | 37 +++++++++++++++++++ ...dyen-connector-store-commerce-app-error.md | 37 +++++++++++++++++++ 3 files changed, 111 insertions(+) create mode 100644 support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md create mode 100644 support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md create mode 100644 support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md diff --git a/support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md b/support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md new file mode 100644 index 00000000000..1f1b372b3c1 --- /dev/null +++ b/support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md @@ -0,0 +1,37 @@ +--- +title: Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set +description: Resolves an issue with the Dynamics 365 Payment Connector for Adyen where the payment authorization calls fail, and a hardware error occurs because the electronic funds transfer (EFT) Terminal ID isn't set. +author: v-chgri +ms.author: johnmichalak +ms.topic: troubleshooting +ms.date: 10/03/2025 +--- +# Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set + +This article provides a solution for an issue with the Dynamics 365 Payment Connector for Adyen where the payment authorization calls fail, and a hardware error occurs because the electronic funds transfer (EFT) Terminal ID isn't set. + +## Symptoms + +Payment authorization calls fail, and a hardware error occurs. An error message in the event log indicates that the **EFT Terminal ID** value isn't set. + +### Root cause + +This issue can occur when the **EFT POS Register Number** field isn't set on the register or the IIS Hardware Station. It can also occur if the value is set but isn't correctly synced to the POS terminal, or when the value is cached. + +## Resolution + +To solve this issue, follow these steps. + +1. Follow the instructions in [Set up a Dynamics 365 register](/dynamics365/commerce/dev-itpro/adyen-connector-setup#set-up-a-dynamics-365-register). +1. Run the 1070 and 1090 distribution schedule jobs. +1. If the issue isn't resolved, consider reactivating the Store Commerce app, because the value of the EFT POS Register Number field may be cached and might need to be reset. + +## More information + +[Dynamics 365 Payment Connector for Adyen overview](/dynamics365/commerce/dev-itpro/adyen-connector) + +[Set up Dynamics 365 Payment Connector for Adyen](/dynamics365/commerce/dev-itpro/adyen-connector-setup) + +[Dynamics 365 Payment Connector for Adyen FAQ](/dynamics365/commerce/dev-itpro/adyen-connector-faq) + +[Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md b/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md new file mode 100644 index 00000000000..6509a6a25e4 --- /dev/null +++ b/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md @@ -0,0 +1,37 @@ +--- +title: Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization +description: Resolves an issue the Dynamics 365 Payment Connector for Adyen where invoicing sales orders fail due to stale authorization. +author: v-chgri +ms.author: johnmichalak +ms.topic: troubleshooting +ms.date: 10/03/2025 +--- +# Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization + +This article provides a solution for an issue with the Dynamics 365 Payment Connector for Adyen where invoicing sales orders fail due to stale authorization. + +## Symptoms + +Invoicing sales orders fail and generate the error "Exception has been thrown by the target of an invocation. System.ArgumentNullException: Value cannot be null." The underlying error in the logs is "The following error occurred during the capture call - Dynamics 365 Payment Connector for Adyen: Error code Decline message Capture failed due to stale authorization." + +### Root cause + +This error happens when an authorization older than the **Authorization stale period (days)** property value is sent to the payment connector for capture. + +## Resolution + +To solve this issue, follow these steps. + +1. In Dynamics 365 Commerce headquarters, go to **Accounts receivable parameters** \> **Credit Card**. +1. In the **Number of days before expired** field, ensure that the value is set to 1 day less than the value set in merchant properties for all channels. The recommended value for **Authorization stale period (days)** is 14 in Adyen merchant properties, and 13 in **Accounts receivables parameters**. +1. Retry invoicing. + +## More information + +[Dynamics 365 Payment Connector for Adyen overview](/dynamics365/commerce/dev-itpro/adyen-connector) + +[Set up Dynamics 365 Payment Connector for Adyen](/dynamics365/commerce/dev-itpro/adyen-connector-setup) + +[Dynamics 365 Payment Connector for Adyen FAQ](/dynamics365/commerce/dev-itpro/adyen-connector-faq) + +[Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md b/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md new file mode 100644 index 00000000000..9ac27a44451 --- /dev/null +++ b/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md @@ -0,0 +1,37 @@ +--- +title: Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated +description: Resolves an issue with the Dynamics 365 Payment Connector for Adyen where the Store Commerce app generates a sign-in error. +author: v-chgri +ms.author: johnmichalak +ms.topic: troubleshooting +ms.date: 10/03/2025 +--- +# Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated + +This article provides a solution for an issue with the Dynamics 365 Payment Connector for Adyen where the Store Commerce app generates a sign-in error. + +## Symptoms + +The Store Commerce app generates the error "Sign in Error. The initialization data couldn't be loaded." + +### Root cause + +This issue can occur when the point of sale (POS) is redeployed, but the dllhost.config file isn't updated. + +## Resolution + +To solve this issue, follow these steps. + +1. Follow the instructions in [Update the Store Commerce app or IIS Hardware Station configuration](/dynamics365/commerce/dev-itpro/adyen-connector-setup#update-the-store-commerce-app-or-iis-hardware-station-configuration). +1. In Task Manager, on the **Details** tab, end the dllhost.exe task. +1. Reopen the Store Commerce app. If you're using a Microsoft Internet Information Services (IIS) Hardware Station, reset IIS. + +## More information + +[Dynamics 365 Payment Connector for Adyen overview](/dynamics365/commerce/dev-itpro/adyen-connector) + +[Set up Dynamics 365 Payment Connector for Adyen](/dynamics365/commerce/dev-itpro/adyen-connector-setup) + +[Dynamics 365 Payment Connector for Adyen FAQ](/dynamics365/commerce/dev-itpro/adyen-connector-faq) + +[Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) From 5e478232a921d6918c2fa916d3d8ad3c0baf239b Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 30 Sep 2025 10:39:49 -0700 Subject: [PATCH 02/29] Update welcome-commerce.yml --- support/dynamics-365/commerce/welcome-commerce.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/welcome-commerce.yml b/support/dynamics-365/commerce/welcome-commerce.yml index 36a43f0e7ae..32416f71268 100644 --- a/support/dynamics-365/commerce/welcome-commerce.yml +++ b/support/dynamics-365/commerce/welcome-commerce.yml @@ -97,7 +97,13 @@ landingContent: url: payments/next-payment-link-not-appearing.md - text: Troubleshoot Dynamics 365 Payment Connector for Adyen issues url: payments/adyen-support.md - + - text: Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set + url: payments/adyen-connector-eft-terminal-id.md + - text: Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization + url: payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md + - text: Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated + url: payments/adyen-connector-store-commerce-app-error.md + # Card - title: Point of sale (POS) linkLists: From a45c987af6533f83ad56fc5095174c9a34ad5bff Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 30 Sep 2025 10:39:56 -0700 Subject: [PATCH 03/29] Update toc.yml --- support/dynamics-365/commerce/toc.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/support/dynamics-365/commerce/toc.yml b/support/dynamics-365/commerce/toc.yml index a9bdcc66547..ec2121bbf51 100644 --- a/support/dynamics-365/commerce/toc.yml +++ b/support/dynamics-365/commerce/toc.yml @@ -64,6 +64,12 @@ href: payments/next-payment-link-not-appearing.md - name: Troubleshoot Dynamics 365 Payment Connector for Adyen issues href: payments/adyen-support.md + -name: Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set + href: payments/adyen-connector-eft-terminal-id.md + -name: Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization + href: payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md + -name: Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated + href: payments/adyen-connector-store-commerce-app-error.md - name: Point of sale (POS) items: - name: Store Commerce app (POS) is suddenly deactivated From 0bbb1d944ada30459d687da653e1488a2d4d8791 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 30 Sep 2025 10:51:48 -0700 Subject: [PATCH 04/29] Update toc.yml --- support/dynamics-365/commerce/toc.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/support/dynamics-365/commerce/toc.yml b/support/dynamics-365/commerce/toc.yml index ec2121bbf51..43b7d7d7b46 100644 --- a/support/dynamics-365/commerce/toc.yml +++ b/support/dynamics-365/commerce/toc.yml @@ -64,11 +64,11 @@ href: payments/next-payment-link-not-appearing.md - name: Troubleshoot Dynamics 365 Payment Connector for Adyen issues href: payments/adyen-support.md - -name: Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set + - name: Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set href: payments/adyen-connector-eft-terminal-id.md - -name: Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization + - name: Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization href: payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md - -name: Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated + - name: Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated href: payments/adyen-connector-store-commerce-app-error.md - name: Point of sale (POS) items: From c75c34a34d59d3fc8ebe5e5c0b8b42c73774a6ce Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 30 Sep 2025 11:03:24 -0700 Subject: [PATCH 05/29] Update and rename adyen-connector-eft-terminal-id.md to adyen-connector-terminal.md --- ...-connector-eft-terminal-id.md => adyen-connector-terminal.md} | 1 + 1 file changed, 1 insertion(+) rename support/dynamics-365/commerce/payments/{adyen-connector-eft-terminal-id.md => adyen-connector-terminal.md} (98%) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md b/support/dynamics-365/commerce/payments/adyen-connector-terminal.md similarity index 98% rename from support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md rename to support/dynamics-365/commerce/payments/adyen-connector-terminal.md index 1f1b372b3c1..d1360b70fff 100644 --- a/support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md +++ b/support/dynamics-365/commerce/payments/adyen-connector-terminal.md @@ -35,3 +35,4 @@ To solve this issue, follow these steps. [Dynamics 365 Payment Connector for Adyen FAQ](/dynamics365/commerce/dev-itpro/adyen-connector-faq) [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) + From a3f54beb826d0a40d02975c06fde496a3df7f763 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 30 Sep 2025 11:03:28 -0700 Subject: [PATCH 06/29] Update toc.yml --- support/dynamics-365/commerce/toc.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/toc.yml b/support/dynamics-365/commerce/toc.yml index 43b7d7d7b46..dcfbb0c7bc7 100644 --- a/support/dynamics-365/commerce/toc.yml +++ b/support/dynamics-365/commerce/toc.yml @@ -65,7 +65,7 @@ - name: Troubleshoot Dynamics 365 Payment Connector for Adyen issues href: payments/adyen-support.md - name: Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set - href: payments/adyen-connector-eft-terminal-id.md + href: payments/adyen-connector-terminal.md - name: Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization href: payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md - name: Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated From f963ca3e185c98947155d47c60835505424e31fe Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 30 Sep 2025 11:03:31 -0700 Subject: [PATCH 07/29] Update welcome-commerce.yml --- support/dynamics-365/commerce/welcome-commerce.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/welcome-commerce.yml b/support/dynamics-365/commerce/welcome-commerce.yml index 32416f71268..89d626a56da 100644 --- a/support/dynamics-365/commerce/welcome-commerce.yml +++ b/support/dynamics-365/commerce/welcome-commerce.yml @@ -98,7 +98,7 @@ landingContent: - text: Troubleshoot Dynamics 365 Payment Connector for Adyen issues url: payments/adyen-support.md - text: Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set - url: payments/adyen-connector-eft-terminal-id.md + url: payments/adyen-connector-terminal.md - text: Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization url: payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md - text: Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated From 3b4e2952d75132be067e5348cf034124b8784319 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 7 Oct 2025 12:27:30 -0700 Subject: [PATCH 08/29] Add files via upload --- .../commerce-offline-implementation.md | 228 ++++++++++++++++++ 1 file changed, 228 insertions(+) create mode 100644 support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md new file mode 100644 index 00000000000..da8afa13dfe --- /dev/null +++ b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md @@ -0,0 +1,228 @@ +--- +title: Troubleshoot Commerce offline implementation +description: Learn how to troubleshoot errors for offline implementations of Microsoft Dynamics 365 Commerce. +author: v-chgri +ms.author: johnmichalak +ms.topic: troubleshooting +ms.date: 10/07/2025 +--- +# + +This article explains how to troubleshoot errors for offline implementations of Microsoft Dynamics 365 Commerce. + +## Issue 1 + + +### Symptoms + +You receive one of the following errors: + +- Microsoft_Dynamics_Commerce_Runtime_AuthenticationFailed +- Microsoft_Dynamics_Commerce_Runtime_AuthorizationFailed +- Microsoft_Dynamics_Commerce_Runtime_WorkerNotFound +- Microsoft_Dynamics_Commerce_Runtime_PartyNotFound +- Microsoft_Dynamics_Commerce_Runtime_RetailStaffNotFound + +#### Root cause + +A sign-in-related issue has occurred. This issue might occur because data isn't found or correctly configured in the offline database. + +### Resolution + +To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. + +## Issue 2: + +### Symptoms + +You receive one of the following errors: + +- Microsoft_Dynamics_Commerce_Runtime_ChannelEmployeeAddressBookNotFound +- Microsoft_Dynamics_Commerce_Runtime_EmployeeNotOnStore + +#### Root cause + +This issue might occur because the store's employee address books aren't found or the worker isn't correctly mapped to the store in the offline database. + +### Resolution + +To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. + +## Issue 3: + +### Symptoms + +You receive one of the following errors: + +- Microsoft_Dynamics_Commerce_Runtime_EmployeePositionAssignmentNotFound +- Microsoft_Dynamics_Commerce_Runtime_EmployeePositionDetailNotFound + +#### Root cause + +This issue might occur because the worker's position detail or assignment isn't found or valid in the offline database. + +### Resolution + +To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. + +## Issue 4: + +### Symptoms + +You receive the following error: + +Microsoft_Dynamics_Commerce_Runtime_EmployeePermissionGroupNotFound + +#### Root cause + +This issue might occur because the worker's POS permission settings aren't found or are configured incorrectly in the offline database. + +### Resolution + +To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. + +## Issue 5: + +### Symptoms + +You receive one of the following errors: + +- Microsoft_Dynamics_Commerce_Runtime_AuthenticationMethodDisabled +- Microsoft_Dynamics_Commerce_Runtime_ChannelConfigurationNotFound +- Microsoft_Dynamics_Commerce_Runtime_ChannelNotPublished +- Microsoft_Dynamics_Commerce_Runtime_ChannelRecordNotFound +- Microsoft_Dynamics_Commerce_Runtime_EmployeePermissionContextNotFound +- Microsoft_Dynamics_Commerce_Runtime_InvalidChannel +- Microsoft_Dynamics_Commerce_Runtime_InvalidChannelConfiguration +- Microsoft_Dynamics_Commerce_Runtime_StaffIdContextMissing +- Microsoft_Dynamics_Commerce_Runtime_LocalDeviceAuthenticationFailed + +#### Root cause + +Unable to switch to offline mode. The channel information is either unavailable or incorrectly configured. + +### Resolution + +To fix this issue, run the **Channel configuration scheduler** job (by default, the **1070** scheduler job). Also, contact your system administrator. + +## Issue 6: + +### Symptoms + +You receive one of the following errors: + +- Microsoft_Dynamics_Commerce_Runtime_CredentialsNotConfigured +- Microsoft_Dynamics_Commerce_Runtime_CredentialsNotFound +- Microsoft_Dynamics_Commerce_Runtime_InvalidAuthenticationCredentials +- Microsoft_Dynamics_Commerce_Runtime_LocalLogonFailed +- Microsoft_Dynamics_Commerce_Runtime_UserBlockedDueToTooManyFailedLogonAttempts + +#### Root cause + +Unable to switch to offline mode. The user information is either unavailable or incorrectly configured. + +### Resolution + +To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. + +## Issue 7: + +### Symptoms + +You receive the following error: + +Microsoft_Dynamics_Commerce_Runtime_CriticalStorageError + +#### Root cause + + +### Resolution + +To check the status of offline database permissions, size, and disk space, you can use the offline dashboard. + +## Issue 8: + +### Symptoms + +You receive the following error: + +Microsoft_Dynamics_Commerce_Runtime_ElevatedUserSameAsLoggedOnUser + +#### Root cause + +This error occurs when the same user tries to perform a manager override. + +### Resolution + +A different user must be used. + +## Issue 9: + +### Symptoms + +You receive one of the following errors: + +- Microsoft_Dynamics_Commerce_Runtime_RealtimeServiceNotSupported +- Microsoft_Dynamics_Commerce_Runtime_TransientStorageError + +#### Root cause + +Unable to switch to offline mode. The offline database is either incorrectly installed or incorrectly configured. + +### Resolution + +Verify that everything has been set up successfully. Also, contact your system administrator. + +## Issue 10: + +### Symptoms + +You receive one of the following errors: + +- Microsoft_Dynamics_Commerce_Runtime_TerminalNotFound +- Microsoft_Dynamics_Commerce_Runtime_DeviceConfigurationNotFound + +#### Root cause + + +### Resolution + +To fix this issue, run the **Channel configuration scheduler** job (by default, the **1070** scheduler job). Also, contact your system administrator. + +## Issue 11: + +### Symptoms + +You receive one of the following errors: + +- Internal_Server_Error +- Request_Timeout_Error +- Microsoft_Dynamics_Commerce_Runtime_InvalidFormat + +#### Root cause + +These errors cover a variety of possible scenarios. + +### Resolution + +Microsoft recommends that you contact Support to get direct assistance (where applicable). + +## More information + +[Commerce offline implementation considerations](/dynamics365/commerce/dev-itpro/implementation-considerations-offline) + +[Commerce Data Exchange implementation guidance](/dynamics365/commerce/dev-itpro/implementation-considerations-cdx) + +[Commerce Data Exchange troubleshooting](/dynamics365/commerce/dev-itpro/cdx-troubleshooting) + +[Commerce Data Exchange best practices](/dynamics365/commerce/dev-itpro/cdx-best-practices) + +[Online and offline point of sale (POS) operations](/dynamics365/commerce/pos-operations) + +[Dynamics 365 Commerce architecture overview](/dynamics365/commerce/commerce-architecture) + +[Select an in-store topology](/dynamics365/commerce/dev-itpro/retail-in-store-topology) + +[Device management implementation guidance](/dynamics365/commerce/implementation-considerations-devices) + +[Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) \ No newline at end of file From 9bf10f23362b623a7415c9949081f14fab3773fe Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 7 Oct 2025 12:31:17 -0700 Subject: [PATCH 09/29] Update toc.yml --- support/dynamics-365/commerce/toc.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/support/dynamics-365/commerce/toc.yml b/support/dynamics-365/commerce/toc.yml index dcfbb0c7bc7..5bd66be1639 100644 --- a/support/dynamics-365/commerce/toc.yml +++ b/support/dynamics-365/commerce/toc.yml @@ -18,6 +18,8 @@ items: - name: CDX download jobs can't be downloaded in a sandbox UAT href: data-synchronization/uat-cdx-broke-after-debug-aos.md + - name: Troubleshoot Commerce offline implementation + href: data-synchronization/commerce-offline-implementation.md - name: Development and SDKs items: - name: Errors when debugging against a Tier 1 Retail Server virtual machine From d60fd7e2b47889c044a7e7f1332c562a2c1ab553 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 7 Oct 2025 12:32:12 -0700 Subject: [PATCH 10/29] Update welcome-commerce.yml --- support/dynamics-365/commerce/welcome-commerce.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/welcome-commerce.yml b/support/dynamics-365/commerce/welcome-commerce.yml index 89d626a56da..7fbedbfbf9f 100644 --- a/support/dynamics-365/commerce/welcome-commerce.yml +++ b/support/dynamics-365/commerce/welcome-commerce.yml @@ -28,7 +28,9 @@ landingContent: - linkListType: how-to-guide links: - text: CDX download jobs can't be downloaded in a sandbox UAT - url: data-synchronization/uat-cdx-broke-after-debug-aos.md + url: data-synchronization/uat-cdx-broke-after-debug-aos.md + - text: Troubleshoot Commerce offline implementation + url: data-synchronization/commerce-offline-implementation.md # Card - title: Development and SDKs From e9c5dde3be7aa35fb425acf57ba19c9158fc30be Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 7 Oct 2025 12:32:54 -0700 Subject: [PATCH 11/29] Update commerce-offline-implementation.md --- .../data-synchronization/commerce-offline-implementation.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md index da8afa13dfe..0bf2982462c 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md @@ -6,7 +6,7 @@ ms.author: johnmichalak ms.topic: troubleshooting ms.date: 10/07/2025 --- -# +# Troubleshoot Commerce offline implementation This article explains how to troubleshoot errors for offline implementations of Microsoft Dynamics 365 Commerce. @@ -225,4 +225,5 @@ Microsoft recommends that you contact Support to get direct assistance (where ap [Device management implementation guidance](/dynamics365/commerce/implementation-considerations-devices) -[Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) \ No newline at end of file + +[Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) From 878e1ce7c89792f6a40e1f6807677545545b1c85 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 7 Oct 2025 14:12:02 -0700 Subject: [PATCH 12/29] Add files via upload --- .../commerce-data-exchange.md | 187 ++++++++++++++++++ 1 file changed, 187 insertions(+) create mode 100644 support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md new file mode 100644 index 00000000000..d20805a5dd8 --- /dev/null +++ b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md @@ -0,0 +1,187 @@ +--- +title: Troubleshoot Commerce Data Exchange (CDX) +description: Learn how to troubleshoot errors for Commerce Data Exchange (CDX) in Microsoft Dynamics 365 Commerce environments. +author: v-chgri +ms.author: johnmichalak +ms.topic: troubleshooting +ms.date: 10/07/2025 +--- +# + +This article explains how to troubleshoot errors for Commerce Data Exchange (CDX) in Microsoft Dynamics 365 Commerce environments. + +## Issue 1 + + +### Symptoms + + + + + +#### Root cause + + + +### Resolution + + + +## Issue 2: + +### Symptoms + + + +#### Root cause + + + +### Resolution + + + +## Issue 3: + +### Symptoms + + + +#### Root cause + + + +### Resolution + + + +## Issue 4: + +### Symptoms + + + +#### Root cause + + + +### Resolution + + + +## Issue 5: + +### Symptoms + + + +#### Root cause + + + +### Resolution + + + +## Issue 6: + +### Symptoms + + + +#### Root cause + + + +### Resolution + + + +## Issue 7: + +### Symptoms + + + +#### Root cause + + +### Resolution + + + +## Issue 8: + +### Symptoms + + + +#### Root cause + + + +### Resolution + + + +## Issue 9: + +### Symptoms + + + +#### Root cause + + + +### Resolution + + + +## Issue 10: + +### Symptoms + + + +#### Root cause + + +### Resolution + + + +## Issue 11: + +### Symptoms + + + +#### Root cause + + + +### Resolution + + + +## More information + +[Commerce Data Exchange best practices](/dynamics365/commerce/dev-itpro/cdx-best-practices) + +[Commerce Data Exchange implementation guidance](/dynamics365/commerce/dev-itpro/implementation-considerations-cdx) + +[Commerce offline implementation considerations](/dynamics365/commerce/dev-itpro/implementation-considerations-offline) + +[Commerce Data Exchange troubleshooting](/dynamics365/commerce/dev-itpro/cdx-troubleshooting) + +[Dynamics 365 Commerce architecture overview](/dynamics365/commerce/commerce-architecture) + +[Select an in-store topology](/dynamics365/commerce/dev-itpro/retail-in-store-topology) + +[Device management implementation guidance](/dynamics365/commerce/implementation-considerations-devices) + +[Configure, install, and activate Modern POS (MPOS)](/dynamics365/commerce/retail-modern-pos-device-activation) + +[Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) + From f6d75841729dba0756d525b6d08d66cdc969ca75 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 9 Oct 2025 09:34:08 -0700 Subject: [PATCH 13/29] Update commerce-data-exchange.md --- .../commerce-data-exchange.md | 104 +++++++++++------- 1 file changed, 66 insertions(+), 38 deletions(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md index d20805a5dd8..faf35e6d77f 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md @@ -12,158 +12,185 @@ This article explains how to troubleshoot errors for Commerce Data Exchange (CDX ## Issue 1 - ### Symptoms +You receive the following error message: - - +`System.ArgumentNullException: Value cannot be null. Parameter name: connectionString at Microsoft.Dynamics.Retail.CommerceDataExchange.SqlTargetRequestHandler.` #### Root cause - +An error has occurred because of batch job statuses. You can view the error in a failed download job on the **Download sessions** page. ### Resolution +Go to **System administration** \> **Inquiries** \> **Batch jobs**, find the data writing batch that is associated with the Commerce Scale Unit that the download job was supposed to be applied to, and change the batch job's status to **Withhold**. In environments that are earlier than version 10.0.12, we recommend that you also create a channel database group that is named **Legacy**, associate the **Default** channel database with this new group, and then exclude the new database group from all distribution schedules. CDX jobs should no longer be generated for the **Default** channel database in the **Legacy** group. - -## Issue 2: +## Issue 2 ### Symptoms - +You can't perform the **Run now** command from the **Distribution schedule** page unless batch processing is used. #### Root cause - +This change was intentionally made in version 10.0.11 because of performance issues that occurred if jobs were run during times when environments were most heavily used. In another change that was made as part of this feature enhancement, recurrence can't be used when the **Full data sync** command (full job synchronization) is run from the **Channel database** page in Commerce headquarters. Only a single occurrence can be run. ### Resolution +Microsoft doesn't recommend that you change this behavior. However, if you're in a development environment, you can change it by going to **Commerce shared parameters** \> **Configuration parameters** and setting a new name, CDX_DISABLE_FORCESCHEDULEINBATCH, that has a value of 1. - -## Issue 3: +## Issue 3 ### Symptoms +You receive the following error message: +`Microsoft.Dynamics.Retail.CommerceDataExchange.SqlWriteRequestRunException: Failed to run SqlWriteRequestRunner for table AX.\.` #### Root cause - +An error has occurred because the length of one or more DBO tables has been extended, so that truncation of data was required. Therefore, a truncation failure has occurred. ### Resolution +Generate a support request. For best practices, see [Enable custom Commerce Data Exchange synchronization via extension](/dynamics365/commerce/dev-itpro/cdx-extensibility). These best practices include removing the extended data type (EDT) extension on the table field that is being edited and using the CDX extension table to store the long (full) value that is required. - -## Issue 4: +## Issue 4 ### Symptoms - +The download session is failing, and the error message states "...tried too many times." #### Root cause +### Resolution +Go to **Retail and Commerce** \> **Headquarters setup** \> **Parameters** \> **Commerce scheduler parameters** and set the **Try count** field to **3**. If the value of this field is too high, download sessions might fail during high-usage times. After you complete this step, the job will set its status to **Canceled** and stop retrying itself. Microsoft recommends that you to read [Commerce Data Exchange best practices](/dynamics365/commerce/dev-itpro/cdx-best-practices). -### Resolution +## Issue 5 +### Symptoms +You can't cancel a running CDX job. -## Issue 5: +#### Root cause -### Symptoms +### Resolution +If this issue occurs in a production environment, sign in to Microsoft Dynamics Lifecycle Services (LCS), and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. +## Issue 6 -#### Root cause +### Symptoms +After you add multiple POS terminals, download sessions take a long time, or there's overall Commerce headquarters slowness. +#### Root cause -### Resolution +When you create a new Store Commerce app offline database and add it to the relevant channel database group, it inherits all existing download sessions since the last full database synchronization occurred. Even at the best of times, the exceptional data generation that might occur can be too large and therefore affect performance. At the worst (that is, busiest) of times, it can severely impair the environment's performance. +### Resolution +Microsoft highly recommends that you have either a "dummy" channel database group (that is, a group that isn't associated with any distribution schedule job) that you assign to the newly generated terminals or a special offline profile where the **Pause offline synchronization** option is set to **Yes**. In this way, data generation can occur when it's required and when the system is most available to do it. (However, the system might pause multiple times as required.) If it's too late to use this approach, create a support request. -## Issue 6: +## Issue 7 ### Symptoms - +Normal, incremental (delta) synchronization takes much too long, even though the number of affected rows is small. #### Root cause - +This issue can occur when a new channel (store) is created, because all the data must be recreated for the new store. ### Resolution +Microsoft highly recommends that you have a "dummy" channel database that is associated with a "dummy" channel database group, and assign it to the newly generated channel (store). In this way, data generation can occur when it's required and when the system is most available to do it. If it's too late to use this approach, create a support request. - -## Issue 7: +## Issue 8 ### Symptoms +The P-job fails to create an upload session, and you receive the following error message: +`System.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK\_UPLOADSESSION'. Cannot insert duplicate key in object 'crt.UPLOADSESSION'.` #### Root cause - ### Resolution +If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. - -## Issue 8: +## Issue 9 ### Symptoms +When you try to download an upload session package from the **Upload sessions** page in Commerce headquarters, you receive the following error message: +`Record for Id - \ not found.` #### Root cause - - ### Resolution +Create a support request. - -## Issue 9: +## Issue 10 ### Symptoms +CDX download sessions fail to be applied, and you receive the following error message: +`Failed to get download session package URI.` #### Root cause +### Resolution +If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. -### Resolution +## Issue 11 +### Symptoms +No download sessions are applied, and no upload sessions are created. -## Issue 10: +#### Root cause + +### Resolution + +If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. + +## Issue 12 ### Symptoms +Upload sessions fail, and you receive the following error message: +`Infolog for task Default:P-0001 (...) Error when bulk inserting data. Target table: RetailListingStatusLog.` #### Root cause +An error has occurred because the upload session package contains multiple records in the **RetailListingStatusLog** table. These records have the same **StatusDateTime** value between two or more. ### Resolution +If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. - -## Issue 11: +## Issue 13 ### Symptoms - +When a cashier tries to switch to offline mode or is forced offline, the switch fails. #### Root cause - +There are many possible causes. First, verify basic information: Does the computer have available hard drive space? If you're using SQL Server Express, is the size of the offline database at the 10 gigabytes (GB) limit? Are there pending download sessions for the register? (Pending download sessions indicate that the register is no longer up to date. Therefore, offline switching might temporarily be prevented.) ### Resolution - +Additionally, we recommend that you contact Microsoft Support. If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. ## More information @@ -185,3 +212,4 @@ This article explains how to troubleshoot errors for Commerce Data Exchange (CDX [Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) + From 637d5fc5dca5052d41b0a6defe270a884b5bbbc1 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 9 Oct 2025 09:36:42 -0700 Subject: [PATCH 14/29] Update welcome-commerce.yml --- support/dynamics-365/commerce/welcome-commerce.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/support/dynamics-365/commerce/welcome-commerce.yml b/support/dynamics-365/commerce/welcome-commerce.yml index 7fbedbfbf9f..d4a7e490560 100644 --- a/support/dynamics-365/commerce/welcome-commerce.yml +++ b/support/dynamics-365/commerce/welcome-commerce.yml @@ -29,6 +29,8 @@ landingContent: links: - text: CDX download jobs can't be downloaded in a sandbox UAT url: data-synchronization/uat-cdx-broke-after-debug-aos.md + - text: Troubleshoot Commerce Data Exchange (CDX) + url: data-synchronization/commerce-data-exchange.md - text: Troubleshoot Commerce offline implementation url: data-synchronization/commerce-offline-implementation.md From 175fa37a3006bb98ac2ca7fa0fcc71e63891ed4e Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 9 Oct 2025 09:37:32 -0700 Subject: [PATCH 15/29] Update toc.yml --- support/dynamics-365/commerce/toc.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/support/dynamics-365/commerce/toc.yml b/support/dynamics-365/commerce/toc.yml index 5bd66be1639..bc23fa03f75 100644 --- a/support/dynamics-365/commerce/toc.yml +++ b/support/dynamics-365/commerce/toc.yml @@ -18,6 +18,8 @@ items: - name: CDX download jobs can't be downloaded in a sandbox UAT href: data-synchronization/uat-cdx-broke-after-debug-aos.md + - name: Troubleshoot Commerce Data Exchange (CDX) + href: data-synchronization/commerce-data-exchange.md - name: Troubleshoot Commerce offline implementation href: data-synchronization/commerce-offline-implementation.md - name: Development and SDKs From 7052bc60a962dc9889b671efb6e847f6a72e7564 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 9 Oct 2025 09:38:06 -0700 Subject: [PATCH 16/29] Update commerce-data-exchange.md --- .../commerce/data-synchronization/commerce-data-exchange.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md index faf35e6d77f..58a0b05bd71 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md @@ -6,7 +6,7 @@ ms.author: johnmichalak ms.topic: troubleshooting ms.date: 10/07/2025 --- -# +# Troubleshoot Commerce Data Exchange (CDX) This article explains how to troubleshoot errors for Commerce Data Exchange (CDX) in Microsoft Dynamics 365 Commerce environments. @@ -213,3 +213,4 @@ Additionally, we recommend that you contact Microsoft Support. If this issue occ [Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) + From 9cbb54ea9c351dca9217b25ca34386b52d5fa646 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 14 Oct 2025 09:13:07 -0700 Subject: [PATCH 17/29] Update commerce-data-exchange.md --- .../commerce-data-exchange.md | 90 ++++++++++--------- 1 file changed, 46 insertions(+), 44 deletions(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md index 58a0b05bd71..da8ebee3751 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md @@ -4,13 +4,13 @@ description: Learn how to troubleshoot errors for Commerce Data Exchange (CDX) i author: v-chgri ms.author: johnmichalak ms.topic: troubleshooting -ms.date: 10/07/2025 +ms.date: 10/14/2025 --- # Troubleshoot Commerce Data Exchange (CDX) This article explains how to troubleshoot errors for Commerce Data Exchange (CDX) in Microsoft Dynamics 365 Commerce environments. -## Issue 1 +## Issue 1: Error due to batch statuses ### Symptoms @@ -24,23 +24,23 @@ An error has occurred because of batch job statuses. You can view the error in a ### Resolution -Go to **System administration** \> **Inquiries** \> **Batch jobs**, find the data writing batch that is associated with the Commerce Scale Unit that the download job was supposed to be applied to, and change the batch job's status to **Withhold**. In environments that are earlier than version 10.0.12, we recommend that you also create a channel database group that is named **Legacy**, associate the **Default** channel database with this new group, and then exclude the new database group from all distribution schedules. CDX jobs should no longer be generated for the **Default** channel database in the **Legacy** group. +In Commerce headquarters, go to **System administration** \> **Inquiries** \> **Batch jobs** and find the data writing batch associated with the Commerce Scale Unit that the download job is supposed to be applied to, and change the batch job's status to **Withhold**. In environments earlier than Commerce version 10.0.12, Microsoft recommends that you also create a channel database group named **Legacy**, associate the **Default** channel database with this new group, and then exclude the new database group from all distribution schedules. CDX jobs should no longer be generated for the **Default** channel database in the **Legacy** group. -## Issue 2 +## Issue 2: Can't execute Run now command Distribution schedule page unless batch processing is used ### Symptoms -You can't perform the **Run now** command from the **Distribution schedule** page unless batch processing is used. +You can't perform the **Run now** command from the **Distribution schedule** page unless batch processing is used. #### Root cause -This change was intentionally made in version 10.0.11 because of performance issues that occurred if jobs were run during times when environments were most heavily used. In another change that was made as part of this feature enhancement, recurrence can't be used when the **Full data sync** command (full job synchronization) is run from the **Channel database** page in Commerce headquarters. Only a single occurrence can be run. +This change was intentionally made in Commerce version 10.0.11 because of performance issues that occurred if jobs were run during times when environments were most heavily used. In another change that was made as part of this feature enhancement, recurrence can't be used when the **Full data sync** command (full job synchronization) is run from the **Channel database** page in Commerce headquarters. Only a single occurrence can be run. ### Resolution -Microsoft doesn't recommend that you change this behavior. However, if you're in a development environment, you can change it by going to **Commerce shared parameters** \> **Configuration parameters** and setting a new name, CDX_DISABLE_FORCESCHEDULEINBATCH, that has a value of 1. +Microsoft doesn't recommend that you change this behavior. However, if you're in a development environment, you can change it in Commerce headquarters by going to **Commerce shared parameters** \> **Configuration parameters** and setting a new name, CDX_DISABLE_FORCESCHEDULEINBATCH, that has a value of 1. -## Issue 3 +## Issue 3: Error due to extended table length ### Symptoms @@ -54,37 +54,36 @@ An error has occurred because the length of one or more DBO tables has been exte ### Resolution -Generate a support request. For best practices, see [Enable custom Commerce Data Exchange synchronization via extension](/dynamics365/commerce/dev-itpro/cdx-extensibility). These best practices include removing the extended data type (EDT) extension on the table field that is being edited and using the CDX extension table to store the long (full) value that is required. +Generate a Microsoft Support request. -## Issue 4 +For information on best practices, see [Enable custom Commerce Data Exchange synchronization via extension](/dynamics365/commerce/dev-itpro/cdx-extensibility). These best practices include removing the extended data type (EDT) extension on the table field that is being edited and using the CDX extension table to store the long (full) value that is required. + +## Issue 4: Error due to download session failure ### Symptoms The download session is failing, and the error message states "...tried too many times." -#### Root cause - ### Resolution -Go to **Retail and Commerce** \> **Headquarters setup** \> **Parameters** \> **Commerce scheduler parameters** and set the **Try count** field to **3**. If the value of this field is too high, download sessions might fail during high-usage times. After you complete this step, the job will set its status to **Canceled** and stop retrying itself. Microsoft recommends that you to read [Commerce Data Exchange best practices](/dynamics365/commerce/dev-itpro/cdx-best-practices). +In Commerce headquarters, go to **Retail and Commerce** \> **Headquarters setup** \> **Parameters** \> **Commerce scheduler parameters** and set the **Try count** field to **3**. If the value of this field is too high, download sessions might fail during high-usage times. After you complete this step, the job sets its status to **Canceled** and stops retrying itself. Learn more at [Commerce Data Exchange best practices](/dynamics365/commerce/dev-itpro/cdx-best-practices). -## Issue 5 +## Issue 5: Unable to cancel a running CDX job ### Symptoms You can't cancel a running CDX job. -#### Root cause - ### Resolution -If this issue occurs in a production environment, sign in to Microsoft Dynamics Lifecycle Services (LCS), and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. +- If this issue occurs in a production environment, sign in to Microsoft Dynamics Lifecycle Services (LCS), and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a support request. -## Issue 6 +## Issue 6: Slow download sessions after adding multiple POS terminals ### Symptoms -After you add multiple POS terminals, download sessions take a long time, or there's overall Commerce headquarters slowness. +After you add multiple POS terminals, download sessions take a long time, or there's overall slowness in Commerce headquarters. #### Root cause @@ -92,13 +91,16 @@ When you create a new Store Commerce app offline database and add it to the rele ### Resolution -Microsoft highly recommends that you have either a "dummy" channel database group (that is, a group that isn't associated with any distribution schedule job) that you assign to the newly generated terminals or a special offline profile where the **Pause offline synchronization** option is set to **Yes**. In this way, data generation can occur when it's required and when the system is most available to do it. (However, the system might pause multiple times as required.) If it's too late to use this approach, create a support request. +Microsoft recommends that you have either: + +- A "dummy" channel database group (that is, a group that isn't associated with any distribution schedule job) that you assign to the newly generated terminals. +- A special offline profile where the **Pause offline synchronization** option is set to **Yes**. In this way, data generation can occur when it's required and when the system is most available to do it. However, the system might pause multiple times as required. If it's too late to use this approach, create a support request. -## Issue 7 +## Issue 7: Incremental (delta) data synchronization takes too long ### Symptoms -Normal, incremental (delta) synchronization takes much too long, even though the number of affected rows is small. +Normal, incremental (delta) data synchronization takes too long, even though the number of affected rows is small. #### Root cause @@ -106,9 +108,9 @@ This issue can occur when a new channel (store) is created, because all the data ### Resolution -Microsoft highly recommends that you have a "dummy" channel database that is associated with a "dummy" channel database group, and assign it to the newly generated channel (store). In this way, data generation can occur when it's required and when the system is most available to do it. If it's too late to use this approach, create a support request. +Microsoft recommends that you have a "dummy" channel database that's associated with a "dummy" channel database group, and that you assign it to the newly generated channel (store). In this way, data generation can occur when required and the system is most available to do it. If it's too late to use this approach, create a support request. -## Issue 8 +## Issue 8: P-job error due to violation of primary key restraint ### Symptoms @@ -116,13 +118,12 @@ The P-job fails to create an upload session, and you receive the following error `System.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK\_UPLOADSESSION'. Cannot insert duplicate key in object 'crt.UPLOADSESSION'.` -#### Root cause - ### Resolution -If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a support request. -## Issue 9 +## Issue 9: Session package download error due to record not found ### Symptoms @@ -130,13 +131,11 @@ When you try to download an upload session package from the **Upload sessions** `Record for Id - \ not found.` -#### Root cause - ### Resolution Create a support request. -## Issue 10 +## Issue 10: Error due to CDX download sessions failing to be applied ### Symptoms @@ -144,25 +143,23 @@ CDX download sessions fail to be applied, and you receive the following error me `Failed to get download session package URI.` -#### Root cause - ### Resolution -If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a support request. -## Issue 11 +## Issue 11: No download sessions are applied, and no upload sessions are created ### Symptoms No download sessions are applied, and no upload sessions are created. -#### Root cause - ### Resolution -If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a support request. -## Issue 12 +## Issue 12: Upload sessions error due to multiple records in the RetailListingStatusLog table ### Symptoms @@ -172,13 +169,14 @@ Upload sessions fail, and you receive the following error message: #### Root cause -An error has occurred because the upload session package contains multiple records in the **RetailListingStatusLog** table. These records have the same **StatusDateTime** value between two or more. +An error has occurred because the upload session package contains multiple records in the **RetailListingStatusLog** table. These records have the same **StatusDateTime** value between two or more records. ### Resolution -If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a support request. -## Issue 13 +## Issue 13: Failure during switch to offline mode ### Symptoms @@ -186,11 +184,14 @@ When a cashier tries to switch to offline mode or is forced offline, the switch #### Root cause -There are many possible causes. First, verify basic information: Does the computer have available hard drive space? If you're using SQL Server Express, is the size of the offline database at the 10 gigabytes (GB) limit? Are there pending download sessions for the register? (Pending download sessions indicate that the register is no longer up to date. Therefore, offline switching might temporarily be prevented.) +There are many possible causes for the failure. First, verify basic information: Does the computer have available hard drive space? If you're using SQL Server Express, is the size of the offline database at the 10 gigabytes (GB) limit? Are there pending download sessions for the register? Pending download sessions indicate that the register is no longer up to date. Therefore, offline switching might temporarily be prevented. ### Resolution -Additionally, we recommend that you contact Microsoft Support. If this issue occurs in a production environment, sign in to LCS, and create a request for immediate support. If the issue occurs in a nonproduction environment, create a support request. +Microsoft recommends that you contact Microsoft Support. + +- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a support request. ## More information @@ -214,3 +215,4 @@ Additionally, we recommend that you contact Microsoft Support. If this issue occ + From 374dacbfb50bbab3fa64b616217d0ff1ebe504a2 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Tue, 14 Oct 2025 09:28:59 -0700 Subject: [PATCH 18/29] Update commerce-offline-implementation.md --- .../commerce-offline-implementation.md | 48 ++++++++----------- 1 file changed, 21 insertions(+), 27 deletions(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md index 0bf2982462c..4d8a86c2ba5 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md @@ -4,14 +4,13 @@ description: Learn how to troubleshoot errors for offline implementations of Mic author: v-chgri ms.author: johnmichalak ms.topic: troubleshooting -ms.date: 10/07/2025 +ms.date: 10/14/2025 --- # Troubleshoot Commerce offline implementation This article explains how to troubleshoot errors for offline implementations of Microsoft Dynamics 365 Commerce. -## Issue 1 - +## Issue 1: Errors due to sign-in issues ### Symptoms @@ -29,9 +28,9 @@ A sign-in-related issue has occurred. This issue might occur because data isn't ### Resolution -To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. +To fix this issue, in Commerce headquarters, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. -## Issue 2: +## Issue 2: Errors due to employee address book not being found, or employee not mapped to store in offline database ### Symptoms @@ -46,9 +45,9 @@ This issue might occur because the store's employee address books aren't found o ### Resolution -To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. +To fix this issue, in Commerce headquarters, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. -## Issue 3: +## Issue 3: Errors due to employee position detail not found or invalid ### Symptoms @@ -63,9 +62,9 @@ This issue might occur because the worker's position detail or assignment isn't ### Resolution -To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. +To fix this issue, in Commerce headquarters, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. -## Issue 4: +## Issue 4: Error due to employee POS permission settings not found or configured incorrectly ### Symptoms @@ -79,9 +78,9 @@ This issue might occur because the worker's POS permission settings aren't found ### Resolution -To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. +To fix this issue, in Commerce headquarters, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. -## Issue 5: +## Issue 5: Channel errors due to inability to switch to offline mode ### Symptoms @@ -103,9 +102,9 @@ Unable to switch to offline mode. The channel information is either unavailable ### Resolution -To fix this issue, run the **Channel configuration scheduler** job (by default, the **1070** scheduler job). Also, contact your system administrator. +To fix this issue, in Commerce headquarters, run the **Channel configuration scheduler** job (by default, the **1070** scheduler job). Also, contact your system administrator. -## Issue 6: +## Issue 6: User errors due to inability to switch to offline mode ### Symptoms @@ -123,9 +122,9 @@ Unable to switch to offline mode. The user information is either unavailable or ### Resolution -To fix this issue, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. +To fix this issue, in Commerce headquarters, run the **Staff scheduler** job (by default, the **1060** scheduler job). Also, contact your system administrator. -## Issue 7: +## Issue 7: Error due to offline database storage issue ### Symptoms @@ -133,14 +132,11 @@ You receive the following error: Microsoft_Dynamics_Commerce_Runtime_CriticalStorageError -#### Root cause - - ### Resolution -To check the status of offline database permissions, size, and disk space, you can use the offline dashboard. +Use the offline dashboard to check the status of offline database permissions, size, and disk space. -## Issue 8: +## Issue 8: Error due to same user attempting to perform a manager override ### Symptoms @@ -154,9 +150,9 @@ This error occurs when the same user tries to perform a manager override. ### Resolution -A different user must be used. +A different user must perform the manager override. -## Issue 9: +## Issue 9: Database errors due to inability to switch to offline mode ### Symptoms @@ -173,7 +169,7 @@ Unable to switch to offline mode. The offline database is either incorrectly ins Verify that everything has been set up successfully. Also, contact your system administrator. -## Issue 10: +## Issue 10: Errors due to terminal or device configuration not found ### Symptoms @@ -182,14 +178,11 @@ You receive one of the following errors: - Microsoft_Dynamics_Commerce_Runtime_TerminalNotFound - Microsoft_Dynamics_Commerce_Runtime_DeviceConfigurationNotFound -#### Root cause - - ### Resolution To fix this issue, run the **Channel configuration scheduler** job (by default, the **1070** scheduler job). Also, contact your system administrator. -## Issue 11: +## Issue 11: Errors due to internal server, timeout, or runtime invalid format issues ### Symptoms @@ -227,3 +220,4 @@ Microsoft recommends that you contact Support to get direct assistance (where ap [Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) + From c374e7a6761bc8c3510522f4adf90ffd1f599a50 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Wed, 15 Oct 2025 11:17:48 -0700 Subject: [PATCH 19/29] Update commerce-data-exchange.md --- .../commerce-data-exchange.md | 49 ++++++++++--------- 1 file changed, 25 insertions(+), 24 deletions(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md index da8ebee3751..1f1e351cfe6 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md @@ -4,7 +4,7 @@ description: Learn how to troubleshoot errors for Commerce Data Exchange (CDX) i author: v-chgri ms.author: johnmichalak ms.topic: troubleshooting -ms.date: 10/14/2025 +ms.date: 10/15/2025 --- # Troubleshoot Commerce Data Exchange (CDX) @@ -24,9 +24,9 @@ An error has occurred because of batch job statuses. You can view the error in a ### Resolution -In Commerce headquarters, go to **System administration** \> **Inquiries** \> **Batch jobs** and find the data writing batch associated with the Commerce Scale Unit that the download job is supposed to be applied to, and change the batch job's status to **Withhold**. In environments earlier than Commerce version 10.0.12, Microsoft recommends that you also create a channel database group named **Legacy**, associate the **Default** channel database with this new group, and then exclude the new database group from all distribution schedules. CDX jobs should no longer be generated for the **Default** channel database in the **Legacy** group. +In Dynamics 365 Commerce headquarters, go to **System administration** \> **Inquiries** \> **Batch jobs**, find the data writing batch associated with the Commerce Scale Unit to which the download job is supposed to be applied, and change the batch job's status to **Withhold**. -## Issue 2: Can't execute Run now command Distribution schedule page unless batch processing is used +## Issue 2: Can't execute Run now command from Distribution schedule page unless batch processing is used ### Symptoms @@ -34,7 +34,7 @@ You can't perform the **Run now** command from the **Distribution schedule** pag #### Root cause -This change was intentionally made in Commerce version 10.0.11 because of performance issues that occurred if jobs were run during times when environments were most heavily used. In another change that was made as part of this feature enhancement, recurrence can't be used when the **Full data sync** command (full job synchronization) is run from the **Channel database** page in Commerce headquarters. Only a single occurrence can be run. +This change was intentionally made in Commerce version 10.0.11 because of performance issues that occur if jobs are run during times when environments are most heavily used. In another change that was made as part of this feature enhancement, recurrence can't be used when the **Full data sync** (full job synchronization) command is run from the **Channel database** page in Commerce headquarters. Only a single occurrence can be run. ### Resolution @@ -50,19 +50,19 @@ You receive the following error message: #### Root cause -An error has occurred because the length of one or more DBO tables has been extended, so that truncation of data was required. Therefore, a truncation failure has occurred. +An error has occurred because the length of one or more DBO tables has been extended, so that truncation of data is required. Therefore, a truncation failure has occurred. ### Resolution Generate a Microsoft Support request. -For information on best practices, see [Enable custom Commerce Data Exchange synchronization via extension](/dynamics365/commerce/dev-itpro/cdx-extensibility). These best practices include removing the extended data type (EDT) extension on the table field that is being edited and using the CDX extension table to store the long (full) value that is required. +For information on best practices, see [Enable custom Commerce Data Exchange synchronization via extension](/dynamics365/commerce/dev-itpro/cdx-extensibility). These best practices include removing the extended data type (EDT) extension on the table field that's being edited and using the CDX extension table to store the long (full) value that's required. ## Issue 4: Error due to download session failure ### Symptoms -The download session is failing, and the error message states "...tried too many times." +The download session fails, and the error message states "...tried too many times." ### Resolution @@ -76,25 +76,25 @@ You can't cancel a running CDX job. ### Resolution -- If this issue occurs in a production environment, sign in to Microsoft Dynamics Lifecycle Services (LCS), and create a request for immediate support. -- If the issue occurs in a nonproduction environment, create a support request. +- If this issue occurs in a production environment, sign in to [Microsoft Dynamics Lifecycle Services (LCS)[(https://lcs.dynamics.com/Logon/Index), and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a Microsoft Support request. ## Issue 6: Slow download sessions after adding multiple POS terminals ### Symptoms -After you add multiple POS terminals, download sessions take a long time, or there's overall slowness in Commerce headquarters. +After you add multiple POS terminals, download sessions take a long time, or you experience overall slowness in Commerce headquarters. #### Root cause -When you create a new Store Commerce app offline database and add it to the relevant channel database group, it inherits all existing download sessions since the last full database synchronization occurred. Even at the best of times, the exceptional data generation that might occur can be too large and therefore affect performance. At the worst (that is, busiest) of times, it can severely impair the environment's performance. +When you create a new Store Commerce app offline database and add it to the relevant channel database group, it inherits all existing download sessions since the last full database synchronization occurred. Even under normal conditions, the exceptional data generation that might occur can be too large and affect performance. At the busiest times, it can severely impair the environment's performance. ### Resolution Microsoft recommends that you have either: - A "dummy" channel database group (that is, a group that isn't associated with any distribution schedule job) that you assign to the newly generated terminals. -- A special offline profile where the **Pause offline synchronization** option is set to **Yes**. In this way, data generation can occur when it's required and when the system is most available to do it. However, the system might pause multiple times as required. If it's too late to use this approach, create a support request. +- A special offline profile where the **Pause offline synchronization** option is set to **Yes**. In this way, data generation can occur when it's required and when the system is most available to do it. However, the system might pause multiple times as required. If it's too late to use this approach, create a Microsoft Support request. ## Issue 7: Incremental (delta) data synchronization takes too long @@ -108,7 +108,7 @@ This issue can occur when a new channel (store) is created, because all the data ### Resolution -Microsoft recommends that you have a "dummy" channel database that's associated with a "dummy" channel database group, and that you assign it to the newly generated channel (store). In this way, data generation can occur when required and the system is most available to do it. If it's too late to use this approach, create a support request. +Microsoft recommends that you have a "dummy" channel database that's associated with a "dummy" channel database group, and that you assign it to the newly generated channel (store). In this way, data generation can occur when required and the system is most available to do it. If it's too late to use this approach, create a Microsoft Support request. ## Issue 8: P-job error due to violation of primary key restraint @@ -120,8 +120,8 @@ The P-job fails to create an upload session, and you receive the following error ### Resolution -- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. -- If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to [Microsoft Dynamics Lifecycle Services (LCS)[(https://lcs.dynamics.com/Logon/Index), and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a Microsoft Support request. ## Issue 9: Session package download error due to record not found @@ -133,7 +133,7 @@ When you try to download an upload session package from the **Upload sessions** ### Resolution -Create a support request. +Create a Microsoft Support request. ## Issue 10: Error due to CDX download sessions failing to be applied @@ -145,8 +145,8 @@ CDX download sessions fail to be applied, and you receive the following error me ### Resolution -- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. -- If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to [Microsoft Dynamics Lifecycle Services (LCS)[(https://lcs.dynamics.com/Logon/Index), and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a Microsoft Support request. ## Issue 11: No download sessions are applied, and no upload sessions are created @@ -156,8 +156,8 @@ No download sessions are applied, and no upload sessions are created. ### Resolution -- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. -- If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to [Microsoft Dynamics Lifecycle Services (LCS)[(https://lcs.dynamics.com/Logon/Index), and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a Microsoft Support request. ## Issue 12: Upload sessions error due to multiple records in the RetailListingStatusLog table @@ -173,8 +173,8 @@ An error has occurred because the upload session package contains multiple recor ### Resolution -- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. -- If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to [Microsoft Dynamics Lifecycle Services (LCS)[(https://lcs.dynamics.com/Logon/Index), and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a Microsoft Support request. ## Issue 13: Failure during switch to offline mode @@ -190,8 +190,8 @@ There are many possible causes for the failure. First, verify basic information: Microsoft recommends that you contact Microsoft Support. -- If the issue occurs in a production environment, sign in to LCS, and create a request for immediate support. -- If the issue occurs in a nonproduction environment, create a support request. +- If the issue occurs in a production environment, sign in to [Microsoft Dynamics Lifecycle Services (LCS)[(https://lcs.dynamics.com/Logon/Index), and create a request for immediate support. +- If the issue occurs in a nonproduction environment, create a Microsoft Support request. ## More information @@ -216,3 +216,4 @@ Microsoft recommends that you contact Microsoft Support. + From f31c9358c0299bcfec266e612428a74e15af238b Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Wed, 15 Oct 2025 11:20:01 -0700 Subject: [PATCH 20/29] Update commerce-offline-implementation.md --- .../data-synchronization/commerce-offline-implementation.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md index 4d8a86c2ba5..7d387deedb2 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md @@ -4,7 +4,7 @@ description: Learn how to troubleshoot errors for offline implementations of Mic author: v-chgri ms.author: johnmichalak ms.topic: troubleshooting -ms.date: 10/14/2025 +ms.date: 10/15/2025 --- # Troubleshoot Commerce offline implementation @@ -221,3 +221,4 @@ Microsoft recommends that you contact Support to get direct assistance (where ap [Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) + From a4c84f14784a3ea17f711a356f2ba68fe4a1fd7b Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Wed, 15 Oct 2025 11:22:11 -0700 Subject: [PATCH 21/29] Update adyen-connector-invoicing-sales-orders-fail-stale-authorization.md --- ...ctor-invoicing-sales-orders-fail-stale-authorization.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md b/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md index 6509a6a25e4..158033e7e51 100644 --- a/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md +++ b/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md @@ -4,7 +4,7 @@ description: Resolves an issue the Dynamics 365 Payment Connector for Adyen wher author: v-chgri ms.author: johnmichalak ms.topic: troubleshooting -ms.date: 10/03/2025 +ms.date: 10/15/2025 --- # Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization @@ -12,7 +12,7 @@ This article provides a solution for an issue with the Dynamics 365 Payment Conn ## Symptoms -Invoicing sales orders fail and generate the error "Exception has been thrown by the target of an invocation. System.ArgumentNullException: Value cannot be null." The underlying error in the logs is "The following error occurred during the capture call - Dynamics 365 Payment Connector for Adyen: Error code Decline message Capture failed due to stale authorization." +Invoicing sales orders fail and generate the error `Exception has been thrown by the target of an invocation. System.ArgumentNullException: Value cannot be null.` The underlying error in the logs is `The following error occurred during the capture call - Dynamics 365 Payment Connector for Adyen: Error code Decline message Capture failed due to stale authorization.` ### Root cause @@ -23,7 +23,7 @@ This error happens when an authorization older than the **Authorization stale pe To solve this issue, follow these steps. 1. In Dynamics 365 Commerce headquarters, go to **Accounts receivable parameters** \> **Credit Card**. -1. In the **Number of days before expired** field, ensure that the value is set to 1 day less than the value set in merchant properties for all channels. The recommended value for **Authorization stale period (days)** is 14 in Adyen merchant properties, and 13 in **Accounts receivables parameters**. +1. In the **Number of days before expired** field, ensure that the value is set to one (1) day less than the value set in merchant properties for all channels. The recommended value for **Authorization stale period (days)** is 14 in Adyen merchant properties, and 13 in **Accounts receivables parameters**. 1. Retry invoicing. ## More information @@ -35,3 +35,4 @@ To solve this issue, follow these steps. [Dynamics 365 Payment Connector for Adyen FAQ](/dynamics365/commerce/dev-itpro/adyen-connector-faq) [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) + From 4f3a761ba63d0924e372f7c3da80d0acc6d3441a Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Wed, 15 Oct 2025 11:23:27 -0700 Subject: [PATCH 22/29] Update adyen-connector-store-commerce-app-error.md --- .../payments/adyen-connector-store-commerce-app-error.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md b/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md index 9ac27a44451..078018f3a30 100644 --- a/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md +++ b/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md @@ -4,7 +4,7 @@ description: Resolves an issue with the Dynamics 365 Payment Connector for Adyen author: v-chgri ms.author: johnmichalak ms.topic: troubleshooting -ms.date: 10/03/2025 +ms.date: 10/15/2025 --- # Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated @@ -12,7 +12,7 @@ This article provides a solution for an issue with the Dynamics 365 Payment Conn ## Symptoms -The Store Commerce app generates the error "Sign in Error. The initialization data couldn't be loaded." +The Store Commerce app generates the error `Sign in Error. The initialization data couldn't be loaded.`. ### Root cause @@ -35,3 +35,4 @@ To solve this issue, follow these steps. [Dynamics 365 Payment Connector for Adyen FAQ](/dynamics365/commerce/dev-itpro/adyen-connector-faq) [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) + From 5399d44d114b17dc81bc01961b7f7d881d6ed95d Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Wed, 15 Oct 2025 11:24:02 -0700 Subject: [PATCH 23/29] Update adyen-connector-invoicing-sales-orders-fail-stale-authorization.md --- ...onnector-invoicing-sales-orders-fail-stale-authorization.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md b/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md index 158033e7e51..51d4274f198 100644 --- a/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md +++ b/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md @@ -12,7 +12,7 @@ This article provides a solution for an issue with the Dynamics 365 Payment Conn ## Symptoms -Invoicing sales orders fail and generate the error `Exception has been thrown by the target of an invocation. System.ArgumentNullException: Value cannot be null.` The underlying error in the logs is `The following error occurred during the capture call - Dynamics 365 Payment Connector for Adyen: Error code Decline message Capture failed due to stale authorization.` +Invoicing sales orders fail and generate the error `Exception has been thrown by the target of an invocation. System.ArgumentNullException: Value cannot be null.`. The underlying error in the logs is `The following error occurred during the capture call - Dynamics 365 Payment Connector for Adyen: Error code Decline message Capture failed due to stale authorization.`. ### Root cause @@ -36,3 +36,4 @@ To solve this issue, follow these steps. [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) + From 26def8e85998392cc41b0e15a07cd060bb813816 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Wed, 15 Oct 2025 11:25:36 -0700 Subject: [PATCH 24/29] Update adyen-connector-terminal.md --- .../commerce/payments/adyen-connector-terminal.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-terminal.md b/support/dynamics-365/commerce/payments/adyen-connector-terminal.md index d1360b70fff..593d867c6be 100644 --- a/support/dynamics-365/commerce/payments/adyen-connector-terminal.md +++ b/support/dynamics-365/commerce/payments/adyen-connector-terminal.md @@ -4,7 +4,7 @@ description: Resolves an issue with the Dynamics 365 Payment Connector for Adyen author: v-chgri ms.author: johnmichalak ms.topic: troubleshooting -ms.date: 10/03/2025 +ms.date: 10/15/2025 --- # Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set @@ -24,7 +24,7 @@ To solve this issue, follow these steps. 1. Follow the instructions in [Set up a Dynamics 365 register](/dynamics365/commerce/dev-itpro/adyen-connector-setup#set-up-a-dynamics-365-register). 1. Run the 1070 and 1090 distribution schedule jobs. -1. If the issue isn't resolved, consider reactivating the Store Commerce app, because the value of the EFT POS Register Number field may be cached and might need to be reset. +1. If the issue isn't resolved, consider reactivating the Store Commerce app, because the value of the **EFT POS Register Number** field may be cached and might need to be reset. ## More information @@ -36,3 +36,4 @@ To solve this issue, follow these steps. [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) + From 11c2054f1dc77ce8c357ae6839cc0c5b90677ff7 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 16 Oct 2025 08:07:17 -0700 Subject: [PATCH 25/29] Update commerce-data-exchange.md --- .../commerce/data-synchronization/commerce-data-exchange.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md index 1f1e351cfe6..615d56af79f 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md @@ -1,10 +1,10 @@ --- title: Troubleshoot Commerce Data Exchange (CDX) description: Learn how to troubleshoot errors for Commerce Data Exchange (CDX) in Microsoft Dynamics 365 Commerce environments. -author: v-chgri +author: johnmichalak ms.author: johnmichalak ms.topic: troubleshooting -ms.date: 10/15/2025 +ms.date: 10/16/2025 --- # Troubleshoot Commerce Data Exchange (CDX) @@ -217,3 +217,4 @@ Microsoft recommends that you contact Microsoft Support. + From 2e3fa96ad7fc5e775bbf2b15ee8dc46509efeade Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 16 Oct 2025 08:17:03 -0700 Subject: [PATCH 26/29] Update commerce-offline-implementation.md --- .../data-synchronization/commerce-offline-implementation.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md index 7d387deedb2..e9fb6f858fb 100644 --- a/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md +++ b/support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md @@ -1,7 +1,7 @@ --- title: Troubleshoot Commerce offline implementation description: Learn how to troubleshoot errors for offline implementations of Microsoft Dynamics 365 Commerce. -author: v-chgri +author: johnmichalak ms.author: johnmichalak ms.topic: troubleshooting ms.date: 10/15/2025 @@ -222,3 +222,4 @@ Microsoft recommends that you contact Support to get direct assistance (where ap [Configure and install Commerce Scale Unit (self-hosted)](/dynamics365/commerce/dev-itpro/retail-store-scale-unit-configuration-installation) + From 275ae96538f51fa388423f2ad045b2ded240cb71 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 16 Oct 2025 08:17:44 -0700 Subject: [PATCH 27/29] Update adyen-connector-invoicing-sales-orders-fail-stale-authorization.md --- ...onnector-invoicing-sales-orders-fail-stale-authorization.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md b/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md index 51d4274f198..7aa4cde4393 100644 --- a/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md +++ b/support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md @@ -1,7 +1,7 @@ --- title: Dynamics 365 Payment Connector for Adyen - Invoicing sales orders fail due to stale authorization description: Resolves an issue the Dynamics 365 Payment Connector for Adyen where invoicing sales orders fail due to stale authorization. -author: v-chgri +author: johnmichalak ms.author: johnmichalak ms.topic: troubleshooting ms.date: 10/15/2025 @@ -37,3 +37,4 @@ To solve this issue, follow these steps. [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) + From 1c92e65a704d10279e3e63cef77312cd5fb3a870 Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 16 Oct 2025 08:18:14 -0700 Subject: [PATCH 28/29] Update adyen-connector-store-commerce-app-error.md --- .../payments/adyen-connector-store-commerce-app-error.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md b/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md index 078018f3a30..f9bd4161212 100644 --- a/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md +++ b/support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md @@ -1,7 +1,7 @@ --- title: Dynamics 365 Payment Connector for Adyen - Store Commerce app or IIS Hardware Station configuration isn't updated description: Resolves an issue with the Dynamics 365 Payment Connector for Adyen where the Store Commerce app generates a sign-in error. -author: v-chgri +author: johnmichalak ms.author: johnmichalak ms.topic: troubleshooting ms.date: 10/15/2025 @@ -36,3 +36,4 @@ To solve this issue, follow these steps. [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) + From 75f3eea037028a6c9ad4f20605ce71b64f035e1b Mon Sep 17 00:00:00 2001 From: Chris Griffin <54049126+v-chgri@users.noreply.github.com> Date: Thu, 16 Oct 2025 08:18:34 -0700 Subject: [PATCH 29/29] Update adyen-connector-terminal.md --- .../dynamics-365/commerce/payments/adyen-connector-terminal.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/support/dynamics-365/commerce/payments/adyen-connector-terminal.md b/support/dynamics-365/commerce/payments/adyen-connector-terminal.md index 593d867c6be..e086c3607d3 100644 --- a/support/dynamics-365/commerce/payments/adyen-connector-terminal.md +++ b/support/dynamics-365/commerce/payments/adyen-connector-terminal.md @@ -1,7 +1,7 @@ --- title: Dynamics 365 Payment Connector for Adyen - EFT Terminal ID isn't set description: Resolves an issue with the Dynamics 365 Payment Connector for Adyen where the payment authorization calls fail, and a hardware error occurs because the electronic funds transfer (EFT) Terminal ID isn't set. -author: v-chgri +author: johnmichalak ms.author: johnmichalak ms.topic: troubleshooting ms.date: 10/15/2025 @@ -37,3 +37,4 @@ To solve this issue, follow these steps. [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail) +