locked
At least one recipient could not be resolved to a record in the system or is marked as "Not Allow" email RRS feed

  • Question

  •  

    After open an account or lead in Microsoft Dynamics CRM 4.0 and create an
    activity appointment appear this message: At least one recipient could not be resolved to a record in the system or is marked as "Not Allow" email, but has registered an email and Not Allow email isn't marked.
    I have installed this hotfix: http://support.microsoft.com/kb/949141/EN-US/ but the message still appears.
    Language of Microsoft Dynamics CRM 4.0: Portuguese-Brazil
    Version: Enterprise
     
    Thanks.
    Monday, October 6, 2008 4:21 PM

Answers

  • Download the diag tool and turn dev errors on, see if you get a more detailed error message:

     

    blogs.msdn.com/benlec/archive/2008/03/04/crmdiagtool4-for-microsoft-crm-4-0-has-been-released.aspx

     

     

    • Marked as answer by Jim Glass Jr Tuesday, June 23, 2009 8:52 PM
    Friday, October 10, 2008 1:42 PM

All replies

  •  

    Does the user that tries to create an appointment have an email address in CRM as well? For an appoinment it is not enough for the lead or account for whom you create it to have an email. An organizer must have an email address as well, otherwise you will get this message.

     

    Kind regards,

    Kuba

    Wednesday, October 8, 2008 1:59 PM
  • Download the diag tool and turn dev errors on, see if you get a more detailed error message:

     

    blogs.msdn.com/benlec/archive/2008/03/04/crmdiagtool4-for-microsoft-crm-4-0-has-been-released.aspx

     

     

    • Marked as answer by Jim Glass Jr Tuesday, June 23, 2009 8:52 PM
    Friday, October 10, 2008 1:42 PM
  • Hello All,

       I have noticed this behavior as well... No matter what Contact is selected, this message is displayed in the Appointment Form.
    This occurs for any Account as well...

       Unfortunately, the error message does not appear in it's own window, so the Diagnostic Tool will not give us any more information with Web Dev Errors.

       Has anyone determined the cause?

    Al

      


    Tuesday, October 21, 2008 3:38 PM