Skip to main content
Nintex Community Menu Bar
Solved

Mailbox migrated to Exchange online

  • April 12, 2022
  • 10 replies
  • 70 views
  • Translate

Forum|alt.badge.img+7

Hi There

We have recently migrated mailboxes to exchange online. Would anyone please advise me if I need to make any changes on the settings?

Currently, no email is being sent out by the service account. Service account has been assigned a license. I have verified emails are being sent using outlook client but not via workflows.

 

Please help.

 

Thanks

Best answer by chruff

This error is typically related to TLS settings.  In particular, it indicates that TLS 1.2 needs to be configured on the K2 server.  This lines up with your move to Exchange Online, as Microsoft is enforcing TLS 1.2 in order to allow communication between your server and their cloud.  

 

To resolve this, you'll need to add the missing registry keys from this KB to the K2 server's registry: https://community.nintex.com/t5/Technical-Issues/K2-and-TLS-1-2-Support/ta-p/124200.  Afterward, restart the K2 server, and then attempt to 'Retry' these failed workflow instances from K2 Management.  This will need to be done on both of the Production servers.

View original

  • Nintex Employee
  • April 12, 2022

Did you run the Setup Manager with the 'Configure' option after migrating the mailbox?  This should disperse the needed settings across the environment (such as the Connection String editor, Host Server .config file, and Environment Library).

 

If you've already done that, are workflows going into error state, or are they simply not sending any emails?  Are these task emails or emails from a 'Send Email' step?  Both?  Have you checked the Host Server logs during the time when an email was expected to send, but did not, and cross-checked for any error messages?

Translate

Forum|alt.badge.img+7
  • Scholar
  • April 12, 2022

hi @chruff 

 

Thanks Chruff. I will do this now. I have to run Cumulative updates as well, shall I run this after the update?

 

Also, we have 2 prod environments, shall I run the setup manager one after another or can run simultaneously?

 

Please advise.

 

Translate

Forum|alt.badge.img+7
  • Scholar
  • April 13, 2022
not sure why Cumulative update was converted as bleep.
Translate

  • Nintex Employee
  • April 13, 2022

It's recommended to upgrade one node at a time, because the K2 service will go down briefly during the Configure process.  For your second question, it's always best practice to keep your K2 server on the latest CUs and fix packs, but this shouldn't be related to your email issue.

Translate

Forum|alt.badge.img+7
  • Scholar
  • April 13, 2022

thanks @chruff 

 

I am receiving SourceCode.Workflow.Shapes.EWS: Autodiscover Failure: The Exchange server is not available, the password is incorrect or the e-mail address does not exist. error after update. Do you have any idea on this?

Translate

Forum|alt.badge.img+7
  • Scholar
  • April 13, 2022

@chruff 

Also, i have successfully ran the configuration without any issues. It seems that email notification action are not working and thw workflow runs into an error

Task notification emails seems to be working fine.

 

Please advise.

Thanks

Translate

  • Nintex Employee
  • April 13, 2022

This error is typically related to TLS settings.  In particular, it indicates that TLS 1.2 needs to be configured on the K2 server.  This lines up with your move to Exchange Online, as Microsoft is enforcing TLS 1.2 in order to allow communication between your server and their cloud.  

 

To resolve this, you'll need to add the missing registry keys from this KB to the K2 server's registry: https://community.nintex.com/t5/Technical-Issues/K2-and-TLS-1-2-Support/ta-p/124200.  Afterward, restart the K2 server, and then attempt to 'Retry' these failed workflow instances from K2 Management.  This will need to be done on both of the Production servers.

Translate

Forum|alt.badge.img+7
  • Scholar
  • April 13, 2022

hi @chruff we have Windows 2016 so it is enabled by default. 

 

Any advise on this?

Translate

  • April 13, 2022

Does the following Keys exist in the registry on the K2 Server?

 

HKLM:SYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Server

HKLM:SYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Client

 

HTH

Vernon

 

Translate

Forum|alt.badge.img+7
  • Scholar
  • April 14, 2022

thank you all, updating the registry worked in my case. 

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings