Search the VMware Knowledge Base (KB)
View by Article ID

Notification email lookups on groups defined for manager emails results with a 404 error in VMware vRealize Automation 6.x (2136687)

  • 0 Ratings

Symptoms

When you have the following configuration in VMware vRealize Automation (Formerly known as vCloud Automation Center) 6.x such as a group is defined in the Group Manager role or the group has an email address defined in active directory or an SMTP server is defined for email notifications, you experience these symptoms:
  • The members of the group fails to receive notifications for the Active Notification Scenarios defined in Administration > Notifications > Scenarios
  • In the /var/log/vmware/catalina.out file of the vRealize Automation appliance, you see entries similar to:

    2015-08-14 11:40:18,609 vcac: [component="cafe:notification" priority="WARN" thread="queue-pool-executer-4" tenant=""] org.springframework.web.client.RestTemplate.handleResponseError:581 - GET request for "https://id.appliance.fqdn/identity/api/tenants/tenanturl/principals/groupname@domain.com/" resulted in 404 (Not Found); invoking error handler2015-08-14 11:40:20,486 vcac: [component="cafe:notification" priority="ERROR" thread="queue-pool-executer-3" tenant=""] com.vmware.vcac.platform.service.integration.ErrorRequestListenerActivator.onErrorMessageRequest:43 - Failed message with id [1a5b730e-dfad-3aeb-11d5-79d22833b223] accepted for error processing.Error Message: [[Error code: 70057 ] - [Error Msg: 70057-No such recipient exists with the id [groupname@domain.com] in tenant [tenanturl]]].Message: [[Payload=RichNotification [recipientId=groupname@domain.com, notificationId=b988c69c-8803-467e-b3bb-ae6d5234b9d1, notificationProviderId=d1ea73e4-ff6a-4bba-8be1-2a1182dcaa32]][Headers={id=1a5b730e-dfad-3aeb-11d5-79d22833b223, timestamp=1439566818479}]]org.springframework.integration.MessagingException: [Error code: 70057 ] - [Error Msg: 70057-No such recipient exists with the id [groupname@domain.com] in tenant [tenanturl]]
  • In the /var/log/vmware/sso/vmware-sts-idmd.log file of the Identity appliance, you see entries similar to:
     
    [2015-08-27 18:57:59,355 tenanturl             0ac141a4-91df-4bd9-91ae-68db81da4b4b ERROR] [ServerUtils] Exception 'com.vmware.identity.idm.InvalidPrincipalException: Failed to find Principal id : {Name: groupname, Domain: domain.com}'com.vmware.identity.idm.InvalidPrincipalException: Failed to find Principal id : {Name: groupname, Domain: domain.com

    In the /var/log/vmware/sso/vmware-sts-idmd.log file of the Identity appliance, you see entries similar to:
     
    [2015-08-27 18:57:59,355 tenanturl             0ac141a4-91df-4bd9-91ae-68db81da4b4b ERROR] [ServerUtils] Exception 'com.vmware.identity.idm.InvalidPrincipalException: Failed to find Principal id : {Name: groupname, Domain: domain.com}'com.vmware.identity.idm.InvalidPrincipalException: Failed to find Principal id : {Name: groupname, Domain: domain.com

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Resolution

This is a known issue affecting VMware vRealize Automation (formerly known as VMware vCloud Automation Center) 6.x.

Currently, there is no resolution. 
 
To work around the issue, define the users that need to be notified instead of the group to be notified.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: