Solved

Error when creating ODX Notification on Critical Errors


Userlevel 1
Badge +1

Hi,

We are unable to set up Notification on Critical Errors for the ODX Server. Both service and database for the ODX is on prem. The Exchange Server is deployed as a hybrid. TimeXtender version 6221.1

This is the error message:
 

 

Setting up notification for the executions in the MDW’s and SSL’s is no problem. No authentication is required by the Exchange server.

BR

Anders

icon

Best answer by Christian Hauggaard 29 October 2023, 01:55

View original

16 replies

Userlevel 6
Badge +5

@anders.e.jonsson 

Is it only in the notification on critical errors menu? It seems to work without password and so in the one for execution packages.

Userlevel 1
Badge +1

Hi Thomas,

Yes, that’s correct. Only error in the notification on critical errors set up.

And it works without username and password in the notifications for execution packages. No problem setting it up, and notifications are sent.

BR

Anders

Userlevel 6
Badge +5

You can confirm that it also works in the latest LTS version without user and password?

 

Userlevel 1
Badge +1

Hi Thomas,

 

I’m not sure I understand what you want me to do. Latest LTS version of what?

BR

Anders

Userlevel 6
Badge +5

The option to send notifications on critical errors also exist in the ODX in the 20.10.43 release, but what you experience in the new release was changed due to the issue you explained, I wondered if it actually was changed for the ODX, and only for the Execution Package one.

If it was it changed from working to not and if it did not, it was not added then hence why it does not work now.

Userlevel 1
Badge +1

Hi Thomas,

We have only tried to set up notifications on critical errors in version version 6221.1. And it’s in that same version it works without username and pwd for notifications for execution packages

BR

Anders

Userlevel 1
Badge +1

Hi @Thomas Lind 

Can you confirm that this is a bug, or have we done something wrong?

BR
Anders

Userlevel 6
Badge +5

It is in review, so I assume so. It might only be an issue regarding the Test email.

So it may actually work still, only it can’t send out test mails.

Userlevel 1
Badge +1

Hi,

It’s not possible set up the Notification at all. Not just the test mails that is failing. Therefore it’s not possible for us to establish whether it would work or not.

BR
Anders

Userlevel 6
Badge +5

Our Product team is currently testing a fix for this which will then be released.

Userlevel 6
Badge +5

Hi @anders.e.jonsson 

Sorry for the late reply on this. A fix has been released for this in 6346.1. Please try upgrading to the latest version.

For reference, please see the below release notes:

  • Trying to send a “critical notification” e-mail would result in an error if not username or password was provided.
Userlevel 1
Badge +1

Hi Christian,

The error “Error when creating ODX Notification on Critical Errors” still remains in release 6346.1.

It’s not sending that is the problem. It’s not possible to set up the notification at all. The error appears when clicking “OK” or “Test Notification”.

BR
Anders

Userlevel 6
Badge +5

Hi @anders.e.jonsson 

Are you getting the same error message as before?

 

Userlevel 1
Badge +1

Hi @Christian Hauggaard ,

yes it’s identical apart from the RefCode

 

I have attached the details in a text file.

BR
Anders

 

Userlevel 6
Badge +5

@anders.e.jonsson OK thanks for confirming. Can you please try restarting TimeXtender and try again now?

Userlevel 1
Badge +1

Hi @Christian Hauggaard 

“If you are reading this, your email server settings are correct.
You can now receive notifications from the ODX server.”

It works now 😊.

Thanks!
Anders

Reply