Notifications
Announcements
No record found.
Once we upgraded our CE from version 8.2 On-prem to 9.1 On-prem, our existing Background Workflows fail immediately when triggered with error “Exception: Event failed due to an exception”. We tried stopping and restarting the MS Asynchronous Processing Service on the application server. Ideas?
Hi Allison.Check the Application log in Event viewer for any errors while reproducing the error(triggering the workflow) on the server(s) for the deployment.Unhandled exceptions should be written there which foretell more on what the issue is.If needed you also have the option to enabled Tracing on the servers that depending on trace level(default: Error) which should capture this in full.Here is a guide to enable this https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/monitor-and-troubleshoot-dynamics-365?view=op-9-1Keep in mind that these trace files can grow quite fast(once again, depending on trace level) so be sure to monitor the directory to not fill the disk and remember to turn in off once you've captured the real exception.I suggest you post the error in in this thread even thou you might directly see what's causing it and how you approached in resolving it as it may help others in the same situation.Hope this helps.Philip
Hi Allison.Just checking in if you were able to find and resolve this issue?Best regards.Philip
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Tom_Gioielli 83 Super User 2025 Season 2
Gerardo Rentería Ga... 49 Most Valuable Professional
#ManoVerse 40
