Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2021
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We are getting seemingly random the error "One or more providers are not correctly configured".
It worked and then stopped working while nothing was changed.
This happens when we tender payment on a Pay Cash Quick payment method.
Server side we see the error below. What can cause this?
Restarting the server did not resolve the error.
An error occurred during the Retail Server Request. RequestUri: https://xxxxxxxxxxxxxxxxxxdc1dbb8devret.cloudax.dynamics.com/Commerce/Carts('SANJOSE-Hugo_R1-30')/AddTenderLine?api-version=7.3. RequestId: f653a3c7-b857-c000-5f95-48ed14ee0490. Exception: Microsoft.Dynamics.Commerce.Runtime.ConfigurationException: Unable to retrieve tender service for operation: 206.
at Microsoft.Dynamics.Commerce.Runtime.Services.PaymentManagerService.ResolvePaymentService(RequestContext context, Type requestType, String tenderTypeId, Boolean isPreprocessedTenderLine)
at Microsoft.Dynamics.Commerce.Runtime.Services.PaymentManagerService.AuthorizePayment(AuthorizePaymentServiceRequest request)
at Microsoft.Dynamics.Commerce.Runtime.Services.PaymentManagerService.Execute(Request request)
--- End of stack trace from previous location where exception was thrown ---
I've ran into this issue once before and It appeared that the problem might be with the “Operation Name” setup on the “Payment Methods” of the store. We asked to change the value to “Pay Cash” instead of “Pay Cash Quick” and leave the Operation on the Button Grid unchanged.
Run the distribution jobs and test again.
If this doesn't help, you may need to open a Support case to further investigate this issue.
Oriol MachinSupport Engineer / Microsoft Dynamics 365 CommerceNorth America Customer Services and Support
In our case it had something to do with the channel not being published properly.
We republished it (we might have triggered a change somewhere, I'm not sure) - and that resolved the issue.
Business Applications communities