Skip to main content
Answer

Create Lab workflow

  • December 6, 2021
  • 3 replies
  • 128 views

Forum|alt.badge.img+10

Hello, 

I will me very grateful for help. 

When doing dev-test of the virtual machine, it throws me such a message. I am asking for help, where to set email addresses in the workflow "Create Lab" (when I try to find such a wrokflow, I get the error "user have no permission on this entity")

Error Code: [19: 857]
Description: Failed to send email as no email is valid, please check recipient (s) emails
Source: commserv, Process: Workflow

Greetings, 

Kinga 

Best answer by Mike Struening

Sorry for the delayed reply @kszaf !  I just got back from holiday yesterday.

Are you still running into this?  If so, might be best to just open a support case (and share the number here to track).

Thanks!

3 replies

Mike Struening
Vaulter
Forum|alt.badge.img+22

Hi @kszaf , thanks for the post!

From what I can see, the Workflow here is called by the VSA process, but is not necessarily exposed otherwise.

I want to focus on the job itself and see where we can get as I’m not finding much in our database.

Can you look at JobManager.log, vsbackup.log, and workflow.log for this job ID at this time?

That’s a good place to start.


Forum|alt.badge.img+10
  • Author
  • Novice
  • December 22, 2021

Hi @Mike thanks for your time. 

So I try go round problem and I add parametere: > sendWorkflowEmailsViaCommserverhttps://documentation.commvault.com/additionalsetting/details?name=%22sendWorkflowEmailsViaCommserver%22&id=2278

during the instruction:
https://documentation.commvault.com/11.24/expert/8681_adding_additional_setting_from_commcell_console.html

 

Unfortunately, it still doesn't work, at the stage of sending the email still have error:

Error Code: [19:857]
Description: Failed to send email as no email is valid, please check recipient(s) emails
Source: commserv, Process: Workflow

 

 

 


Mike Struening
Vaulter
Forum|alt.badge.img+22

Sorry for the delayed reply @kszaf !  I just got back from holiday yesterday.

Are you still running into this?  If so, might be best to just open a support case (and share the number here to track).

Thanks!