Aramaki
Contributor
Contributor

SendMail fails because of null

Jump to solution

Hello,

as you all know, i'm making some more or less complicated workflows in orchestrator.

One of the requirements was that the user should be notified on success and/or errors.

So i created tasks within my workflow, which send emails with information about downtime, sucess and/or failure.

Now, i'm not very sure about this, but i think it might have something to do with the update we installed some weeks ago; all of my workflows involving a sendmail task, are failing at those exact tasks.

This is the error i get:

Cannot send mail : null (Workflow:Create VM / SendSuccessMail (item14)#15)

(i can post the sourcecode if demanded)

Has anyone else experienced a problem with this?

If so, is there a solution or workaround to get the workflow to notify the user via email?

Thanks a lot and

Regards

Andreas

0 Kudos
1 Solution

Accepted Solutions
cdecanini_
VMware Employee
VMware Employee

Hi Andreas,

Have you setup the mail plug-in configuration in the vCO web configure ?

There are two ways to use the mail plug-in. Either you set up the plug-in with a configuration and will not have to provide it when using a workflow or you will have to create custom worklows defining SMTP settings.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter

View solution in original post

0 Kudos
3 Replies
cdecanini_
VMware Employee
VMware Employee

Hi Andreas,

Have you setup the mail plug-in configuration in the vCO web configure ?

There are two ways to use the mail plug-in. Either you set up the plug-in with a configuration and will not have to provide it when using a workflow or you will have to create custom worklows defining SMTP settings.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter

View solution in original post

0 Kudos
Andreas_Diemer
Enthusiast
Enthusiast

Hi Andreas,

w/o code I can look where / what exeption is caused.

But you've mentiones an update. What did you update?

If you are using Configuration or other non dynamic data check for persistens.

Regards, Andreas

------ for correct and / or useful answers please award points visit http://www.vcoteam.info & http://mighty-virtualization.blogspot.com
Aramaki
Contributor
Contributor

Hi Christophe and Andreas,

since you both were talking about probable issues with the configuration, i just took a look at it.

The mail plugin was configured to use default values and a user which has been deleted recently, so the status of the plugin was red.

At first i tried setting up my own user to do so, but somehow there was a problem with permissions.

Then i simply unset the checkbox "use default values" and now it is working.

Now it is very irritating, why the plugin was set up to use a user at all, but since it works now, i'll stick with the result.

Thanks a lot for your help.

Regards

Andreas

0 Kudos