Troubleshoot business events

Important

Dynamics 365 for Finance and Operations is now being licensed as Dynamics 365 Finance and Dynamics 365 Supply Chain Management. For more information about these licensing changes, see Dynamics 365 Licensing Update.

This topic provides tips for troubleshooting issues that involve business events.

Issue Possible resolution
Unable to find navigation to business events in the System parameters form You can access business events by going to System administration > Set up > Business events. This change was made when business events was made generally available in Platform update 26.
Error: Unable to construct endpoint. Exception message: Error retrieving secret '[KeyValueSecretName]' from key vault 'https://[KeyVaultName].vault.azure.net/': AADSTS700016: Application with identifier '7e28cb03-dc28-43b5-b129-e13dcfb4b1fb' was not found in the directory 'ee3fe5c6-26af-42b1-9acf-5ee38e6ead6e'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. It's likely that you may have sent your authentication request to the wrong tenant.
Error: Trace ID: 19dc9946-45b6-4335-9676-6a133dbf4000 Correlation ID: ecbc8a80-f9d0-41ec-9c8f-d334d050bd64 Timestamp: 2019-02-06 23:27:06Z This error typically means that the value in the Azure Active Directory Application ID field is incorrect. Check the Azure Active Directory Application ID value in the customers Azure portal in Azure Active Directory > App Registration.
Error: Unable to construct endpoint. Exception message: Error retrieving secret '[KeyValueSecretName]' from key vault 'https://[KeyVaultName].vault.azure.net/': An error occurred while sending the request. This error is likely due to an incorrect value in the Key Vault DNS Name field. To resolve this, go to the customer's Azure portal and open the key vault object. In the Overview section, check the Key Vault DNS Name value.
Error: Unable to send test event to endpoint. Exception message: 40103: Invalid authorization token signature, Resource:sb://[ServiceBusName].servicebus.windows.net/[QueueName]. TrackingId:cd0eccaa-1717-4f97-b837-4cd7eda99af4_G13, SystemTracker:[ServiceBusName].servicebus.windows.net:[QueueName], Timestamp:2019-02-06T23:36:54 The value in the customer’s Key Vault Secret is likely incorrect. Check the Key Vault Secret value and make sure that it is correct for the endpoint type.
Error: Unable to construct endpoint. Exception message: Error retrieving secret '[KeyValueSecretName]' from key vault 'https://[KeyVaultName].vault.azure.net/': Access denied This is likely due to the Azure Active Directory Application ID not having the appropriate permissions in the Key Vault. To resolve this, go to the Azure portal and open the Key Vault object. Go to Access Policies and add the AAD application with Key, Secret, and Certificate Management template.
Error: Unable to send test event to endpoint. Exception message: 40400: Endpoint not found., Resource:sb://[ServiceBusName].servicebus.windows.net/[QueueName]. This issue is likely a result of the queue/topic/hub name being incorrect. Check the Name field by going to service bus in the Azure portal and reviewing the Topic or Queue name. If it is an Event Hub, go to the Event Hub object in Azure and validate the Hub name.
Error: Unable to send test event to endpoint. Exception message: An error occurred while sending the request. This is likely due to an incorrect endpoint value specified in the Endpoint URL field. Go to the Event Grid object in the Azure portal and open the Event Grid. In the Overview section, this value will be the Topic Endpoint.
Business events do not show up in the catalog The Business event catalog is built during full database sync. As a result, there are some use cases, as noted below, where a manual refresh of the catalog is needed in order to see the new business events. Manual refresh can be invoked from the catalog by going to Manage > Rebuild business events catalog.

When you are implementing business events in Visual Studio you may not see the newly coded business event in the catalog.

When new workflows are configured, such as the workflow elements or steps, might not show up in the business events catalog.

In other situations, when you don’t see certain business events, doing a manual refresh should resolve the issue.
- 0 is an invalid bundle size
- Business events are not getting triggered
- Microsoft Flow is not getting triggered by business events
- Unable to configure business event because it has reached the limit of 0 configured endpoints
One of the reasons why this issue can occur is if certain parameters are not set as expected in the BusinessEventsParameters table. This is due to an update in which some of the business events parameters not being set correctly.

In a non-production environment, you must update the BusinessEventsParameters table so that Enabled =1; ProcessorThreads = 1; EndPointRetryCount = 3; BundleSize = 50; EndPointsPerEvent = 10. After this update, restart the batch service and run IISReset to pick up the latest values.

For production environments, log a support request with Microsoft to get these updated.
Platform update 30 compiler warning when creating custom payload context fields by augmenting via Chain of Command (CoC) the addProperties method in the adapter class. Class 'BusinessEventsServiceBusAdapter' is internal in model 'ApplicationFoundation' and cannot be extended. This is a change in the compiler that prevents an internal API from being extended. This is being tracked as a bug to provide alternate ways to add custom properties. For more information, see this Yammer discussion.
Error: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information This error message on the error tab of active business events can typically be resolved by rebuilding the catalog.
Alert business events don't trigger One of the reasons why an event is not triggerring could be a potential issue with alerts email functionality. Try turning off the send email option in the alert to see if that resolves the issue.