Skip to main content
To homepage To homepage

Hi all, at a client we have encountered a curious situation with execution e-mail notifications, hopefully you will be able to help us figure it out.

There are 5 scheduled execution packages for BU's that run every morning. Since two days we are getting e-mail notifications saying these have failed, but when we look in in TimeXtender they in fact have executed successfully.

Each BU execution throws a different connection error message:

  • ERROR RHY000] 0MySQL]SODBC 8.0(w) Driver]Can't connect to MySQL server on 'XXXXXX' (10060)
  • Unable to connect to any of the specified MySQL hosts.
  • The remote server returned an error: (400) Bad Request.
  • <500] Could not execute the specified command: HTTP protocol error. 500 Internal Server Error.

  • ERROR R08001] could not connect to server: Connection refused (0x0000274D/10061)

I will take the top one as an example to show you how it looks. Attached is the full fail notification e-mail.

This package includes has the following settings:

 

This is what the execution log shows:

 

The timeline for this package seems to be:

  • 7/12/2023 6:02:19 AM Start time according to fail e-mail
  • 7/12/2023 6:02:50 AM Start time according to execution log
  • 7/12/2023 6:09:05 AM End time according to e-mail (Fail)
  • 7/12/2023 6:25:06 AM End time according to execution log (Success)

In the event viewer there are no relevant error messages around these times:

 

Hi @MartinMemelink 

Please see this idea and upvote if you agree with the submitted idea

It is likely that you are receiving the first fail notification due to a step that failed and later succeeded upon retry

Hi @MartinMemelink 

Please see this idea and upvote if you agree with the submitted idea

It is likely that you are receiving the first fail notification due to a step that failed and later succeeded upon retry

This could be a similar situation but the client I'm posting about is on version 20.10.39 and concerns business units, not ODX server.

The idea submitted concerns a DW execution (using execution packages, which are also used for Business Units), although the comments for the idea refer to a separate topic (retries) for the ODX. So I believe the same applies to your setup

Hi Christian,

I don’t see how this issue is considered as an Idea. We’re facing this issue as of last Saturday, while no changes have been made.

I expect an Execution Package to 1) Perform executions as defined in Execution Setup, then 2) Do the Failure Handling (retries, if needed) and when everything is done, 3) do the Post Execution which includes sending notifications.

 

We are looking for something that explains the odd behavior. So far we didn’t manage to find anything.

Hope you can help,

Best,

Erik

Update:

The issue persists and we still don't understand why we are receiving fail e-mail notifications for these successfully scheduled executions.

Xpilot suggested the problem could be that the latest saved version of the project was not deployed. This is however not the case. Yesterday we made changes, deployed one of the affected business units and saved as the deployed version, but this morning the same fail e-mails came in.

By the way: the fail notification e-mails started coming from both test and prod environments on the same day.

@erik.van.mastrigt @MartinMemelink I have discussed this issue with our Product team, and have created a bug for this. I will keep you updated on progress

@erik.van.mastrigt @MartinMemelink I have discussed this issue with our Product team, and have created a bug for this. I will keep you updated on progress

Please don't create bugs :)

@erik.van.mastrigt @MartinMemelink I have discussed this issue with our Product team, and have created a bug for this. I will keep you updated on progress

@Christian Hauggaard, any news yet on this bug? We're still experiencing the issue (fail e-mail notifications from succesful executions) on a daily basis. Any help or suggestions would be appreciated.

@RLB I mean added a bug to be investigated, not created ;) 

@MartinMemelink it is still being investigated by the product team.

@MartinMemelink I have created a support ticket to investigate the issue you are describing

@Christian Hauggaard thank you for taking the action, but I think it support is no longer needed, because the e-mail notifications have stopped.

We think the issue occured after migrating Azure tenants and the notifications were coming from the old Azure machines, which we've been told were turned off, but may have been turned on and off again.

Reply


Terms and ConditionsCookie settings