• Home
  • About Us
  • Contact Us
  • Privacy Policy
  • Special Offers
Business Intelligence Info
  • Business Intelligence
    • BI News and Info
    • Big Data
    • Mobile and Cloud
    • Self-Service BI
  • CRM
    • CRM News and Info
    • InfusionSoft
    • Microsoft Dynamics CRM
    • NetSuite
    • OnContact
    • Salesforce
    • Workbooks
  • Data Mining
    • Pentaho
    • Sisense
    • Tableau
    • TIBCO Spotfire
  • Data Warehousing
    • DWH News and Info
    • IBM DB2
    • Microsoft SQL Server
    • Oracle
    • Teradata
  • Predictive Analytics
    • FICO
    • KNIME
    • Mathematica
    • Matlab
    • Minitab
    • RapidMiner
    • Revolution
    • SAP
    • SAS/SPSS
  • Humor

Troubleshooting ADX Portal Email workflows

June 16, 2017   Microsoft Dynamics CRM
pexels photo 2 300x200 Troubleshooting ADX Portal Email workflows

Portal users occasionally receive a generic error message that may leave them feeling frustrated and stuck. In today’s blog, we’ll explain why this happens, what’s been done to fix it, and what you can do when this happens to you…

The Problem

Occasionally, portal users report receiving the following error message:

061517 2101 Troubleshoo1 Troubleshooting ADX Portal Email workflows

In particular, this seems to occur when requesting a password reset or a confirmation email from the ADX Portal (or similar activities that result in an email being sent from the CRM server). There are several scenarios in which the portal may fail.

The Cause

Portal emails are sent by workflows and activities. When those fail, the exception is not bubbling up to the web application and the generic message is produced.

If the portal is on-premises, users may try going to http:// /trace.axd to see the details of the underlying exception. This may help fix the issue in some simple cases, but certainly not all.

Otherwise, the following checklist may help. In almost all cases, following the checklist will eliminate the problem.

The Solution: Checklist

While our list is extensive, it is not, of course, exhaustive. For example, we assume that the CRM is configured for the Server-Side Synchronization – in cases of Router use, more things could go wrong and they are not covered here. Also, the checklist assumes the email server behaves properly and the portal itself is properly set up.

So far, we have encountered and fixed the following reasons for email failure:

  1. CRM User that is set in the workflow “From” is:

    1. Invalid or references the user with the same name but different GUID (just re-assign to the same)
    2. Deactivated
    3. Has no roles or no permission to send emails
    4. Did not accept invitation (flip invitation status on the _user_ record to “Accepted”)
    5. Mail is not allowed in Office 365 console (if user profiles are managed there)
    6. Mail is not approved for this user
    7. User setting to allow other users to send on behalf is not set (in XRMToolbox find User Settings applet, select this user, and flip this setting to “Yes”)
  2. Mailbox for the user is not configured
  3. Mailbox is not approved and tested
  4. Workflow or activity that sends password reset is not activated or does not exist (although unlikely, we have seen this – which results in the need to re-import the ADX solution containing the workflow)
  5. Portal Cache invalidation on Email entity is not enabled (on-premises only, you need to check if it is enabled using Plugin registration tool and confirming that the correspondent step exists)

Summary

As described herein, nearly all of the causes for the “We’re sorry, but something went wrong” error message have been identified and solutions are available. However, ADX Portal behavior may reveal bigger underlying problems in CRM, and receiving this error may signal a need to check all of the workflows and activities designed to send emails for business purposes. We always recommend regression testing the entire system after substantial configuration changes are applied. Doing so will keep your clients and business happily CRM’ing!

Let’s block ads! (Why?)

PowerObjects- Bringing Focus to Dynamics CRM

Email, Portal, Troubleshooting, “Workflows
  • Recent Posts

    • C’mon hooman
    • Build and Release Pipelines for Azure Resources (Logic Apps and Azure Functions)
    • Database version control: Getting started with Flyway
    • Support CRM with New Dynamics 365 Field Service Mobile App
    • 6 Strategies for Achieving Your Business Goals in the New Year
  • Categories

  • Archives

    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • February 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    • December 2016
    • November 2016
    • October 2016
    • September 2016
    • August 2016
    • July 2016
    • June 2016
    • May 2016
    • April 2016
    • March 2016
    • February 2016
    • January 2016
    • December 2015
    • November 2015
    • October 2015
    • September 2015
    • August 2015
    • July 2015
    • June 2015
    • May 2015
    • April 2015
    • March 2015
    • February 2015
    • January 2015
    • December 2014
    • November 2014
© 2021 Business Intelligence Info
Power BI Training | G Com Solutions Limited