Hello,
I'm currently evaluating vRA 7 and I'm encountering some errors while setting up approval notification. I was wondering if anyone else had already the same issue.
My deployment is a minimal deployment, along with an AD to store users and their emails. I'm trying to setup approval workflow (based on cpu and ram) with reply by email approval.
I've setup the approval policy (it works), the email outbound and inbound (pop). I receive notification as a user that my request was submitted but I dont as an approver receive any notification.
In the error tab I got the following error repeated:
Error Message: [nested exception is org.springframework.dao.IncorrectResultSizeDataAccessException: result returns more than one elements; nested exception is javax.persistence.NonUniqueResultException: result returns more than one elements]. Message: [GenericMessage [payload=RichNotification [recipientId=approver@domain.loc,
The approver is a security group.
Any idea ? Thanks in advance,
Joseph de Clerck.
Hi,
Without answer, I continued to investigate. It seems to be somehow linked to handing pop/imap account to receive approval by email.
anyone else having the same issue?
Regards,
Joseph de Clerck.
It looks like you have a group email address in there. Can you try with an individual to see if that resolves the issue?
Grant
Hi Grant,
I've tested the following cases:
So it seems more linked to POP/IMAP configuration than from approval policy.
Thanks,
Joseph
Well, if you have inbound/outbound configured then the approval policy will attempt to email the approver. If you don't, then it won't... hence the behaviour that you are seeing.
Grant
Hi,
The outbound email configuration is always activated (smtp) and is working when no inbound is configured. In fact the requestor is notified (always) but the approver is only notified when inbound is not configured.
On a fresh install, the first time I tried the inbound configuration it worked out of the boxbut subsequent tries failed with the error on the first message.
Joseph.
In that case, can I ask if the "send from" address has a mailbox? It needs one to check for responses, and thus can't be a group or standalone AD account.
Grant
Can you please try the IP address of the SMTP and IMAP server , also check with your AD team and verify IMAP is configured properly.
Whenever you test the IMAP from VRA , does the authentication works fine.
As you said you are using Security Group for Approver notification , does all having IMAP account and does the security group domain is different than the user ?
Hi Joseph,
Did you ever get a resolution to this issue? I'm having the same problem. Action required emails not being sent. All other email functions working. This all worked when first deployed and tested. Since then "Action required" emails have stopped sending.
Exact same error as you have listed by the way. Thanks.
Rgds,
Padhraic
I know this has been out there a while. The solution can be found in the following KB:
https://kb.vmware.com/kb/2136224
The issue may also be seen in the v7.x release as well. The location of the DB and login information need to be changed for the v7.x releases like this:
For VMware vRealize Automation 7.x, access database in the location cd /opt/vmware/vpostgres/9.x/bin/ and using the default login ./psql -U postgres-d vcac
Did anyone resolve this?
If you're having this issue yourself, post your config and describe your scenario and we'll try to help. As stated above, this does work if you're setup in the correct fashion.
I am unable to access the DB. Keep getting:
psql.bin: FATAL: no pg_hba.conf entry for host "[local]", user "postgres-d", database "vcac", SSL off
We are running v7.2
Post screenshots of your email configuration (outbound and inbound).
We were able to resolve this issue by using the great help that was provided on this discussion.
We need the command to get in the DB and the command posted here worked but I had to insert a space between vpostgres and the "-U"
After we removed the last two entries as the KB stated and restarted the service we ran into another issue where the request would get stuck in submitted mode.
We had to reboot both our appliances and now the approval emails are flowing again.
Thank you very much for the help here.