Announcements
We have a massive number of PartnerDiagnosticScope errors in our Event Log.
It's a BC OnPrem with Azure AD Authentification. (AT Business Central 20.3 (Plattform 20.0.42653.43007 + Anwendung 20.3.42673.43026))
Errors:
Server instance: BC
Category: OData
ClientSessionId: 6f65722e-f8c8-4f44-ae15-2b81c8775a95
ClientActivityId: 293f292c-e459-4cf8-aede-625250b46812
ServerSessionUniqueId: 00000000-0000-0000-0000-000000000000
ServerActivityId: eae3e270-6f16-4fc1-85c1-da243d77254f
EventTime: 11/22/2022 09:35:02
Message PartnerDiagnosticScope was not initialized during the request, this is likely a bug and needs to be investigated.
ProcessId: 12616
Tag: 0000GWP
ThreadId: 86
CounterInformation:
CustomParameters: {
}
GatewayCorrelationId:
Hi, thanks for the feedback, we will try to see what's wrong.
hi
The "PartnerDiagnosticScope was not initialized during the request" error message indicates that there is a problem with the PartnerDiagnosticScope object not being properly initialized during an OData request in Business Central.
Here are some steps you can take to investigate and resolve this issue:
Check the Business Central service tier logs: Check the service tier logs for any errors or warnings that might be related to the PartnerDiagnosticScope issue. The logs can be found in the Event Viewer or in the Business Central Administration Center.
Check the OData requests: Use a tool such as Fiddler or the built-in OData debugger in Business Central to capture and examine the OData requests that are causing the errors. Look for any patterns or similarities between the requests that are causing the errors.
Check the Azure AD authentication: Verify that the Azure AD authentication is properly configured and functioning correctly. Check the Azure AD application registration, permissions, and certificates to ensure that they are up-to-date and correctly configured.
Update Business Central: If you are not already on the latest version of Business Central, consider updating to the latest version to see if the issue has been resolved in a more recent release.
DAniele
Hi Marco,
We have the same error while accessing the API/WS with OAuth for one of our Customers.
Are we sure that upgrading them to the latest CU will solve this? Asking as they will have to spend on an upgrade.
Thanks in advance.
Hello,
This a bug and was resolved in build 20.0.47051.0:
Thank you.
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156