How to trouble shoot error relates to business central communicating with Dataverse

(0) Share

Report

Posted on by B@houston

Hi everyone,

I would like to seek some advise as to how to trouble shoot the errors in business central relate to Dataverse. For example, this below error. Should we check the access in D365 Sales or in the Business Central. If you have any articles documents helpful ? Thank you.

When user creates a sales invoice and post the invoice the error shows up.

"An error occurred when communicating with Dataverse.

Detailed description: SecLib: CheckPrivillege failed. User 795fdaeb-7e03-eb11-0813-000d3af33756, PrivililedgeName:PrvRead

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

Marco Mels on at

Like (1)

Report

Hello,

Your message seems to indicate that the connection setup was done successfully from BC to Dynamics 365 for Sales and a full synchronization was done successfully. Now incremental synchs show these errors which seem to relate to missing permissions.

If the above is true, my bet is that the synchronization user is being used somehow. It should be a non-nteractive user. Or the user is missing roles in Dynamics 365 for Sales. Maybe you can give him / her a role like Salesperson or Salesmanager.

From the error itself, it seems that this is a permission issue in Dynamics 365 for Sales.

Thanks.

Was this reply helpful? Yes No
B@houston on at

Like (0)

Report

Thank you Marco and this works.

Was this reply helpful? Yes No
Leonard Nicolson 5 on at

Like (0)

Report

Hi B@houston

I have exactly the same issue. Whenever an invoice is posted from a Sales Order in BC, the invoice posts ok but an error pops up and the error appears on the error register. Would you mind sharing the exact steps you took to resolve it in BC and CE.

In advance, thank you

Leonard

Was this reply helpful? Yes No
B@houston on at

Like (0)

Report

Hi @Leonard,

To resolve this issue, pleas add a security role of Sales Manager, or Sales Rep in the D365 Sales, and test if the issue is gone. Thank you.

Was this reply helpful? Yes No