Email Tool - Login Denied Error

Wanted to give everyone an update on what I did to get this to start working for me while I was in my office and not just at home via VPN.

1st: As suggested above I had to downgrade of version 2023.1 to 2022.3

2nd: My IT Team created a Remote App Server/Virtual Environment

Logging in via the Remote App Server while at the office allowed me to run the Workflow successfully for all records (8 in my case)

All comments

jallen201

I'm getting the same error after upgrading to 2023.1

But there's a catch first record works, then get this error on record 2 and then the workflow quits. This is a showstopper for many things in my organization

James Allen

jallen201

Here is the error

Screenshot 2023-05-23 093845.png

You have precisely described my issue! This error also came after the 2023.1 update.

Yeah I am using the Version: 2022.3.1.395 and still have the issue.

txjohnnypops79

Same here. Error after the first record. Sent an email to support. Im downgrading now.

TorbenL

Samme issue here. Error after first record. I will reach out to support as well.

Alteryx version: 2023.1.1.123

Wanted to give everyone an update on what I did to get this to start working for me while I was in my office and not just at home via VPN.

1st: As suggested above I had to downgrade of version 2023.1 to 2022.3

2nd: My IT Team created a Remote App Server/Virtual Environment

Logging in via the Remote App Server while at the office allowed me to run the Workflow successfully for all records (8 in my case)

Hi @jsumms, thanks for raising this issue over here. My name is Renat, I am Alteryx Senior PM responsible for data connectivity. Could you please confirm what connection configuration did you use? If your ExchangeOnline configuration is different from the one on attached screenshot, please retry using indicated parameters.

Screenshot 2023-06-09 at 14.22.08.png

Thanks for following up. This is what I am using currently

jonathan_hornbeck

I'm having the same issue after upgrading to 2023.1. Since I upgraded our server to 2023.1 as well, I don't want to have to downgrade everything. Is there anything that has fixed this? I tried a new app password and that didn't work either. Here's my set up which is working fine for server notifications.

Screenshot 2023-06-09 160234.png

Hi @jsumms, I was able to reproduce the error you've encountered while setting up a connection with configuration you provided. We'll attempt to investigate more, but based on the screenshot you provided you're using basic, username/password, authentication when setting up a connection. Microsoft is deprecating support for basic SMPT authentication, https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online, therefore it is recommended that you use OAuth-based authentication when accessing your ExchangeOnline account. To do this, please active DCM and configure the following connection:

Screenshot 2023-06-12 at 9.48.26.png

Using the above configuration shall address the issue.

The link you have provided leads to a dead 404 page. After looking up what was probably supposed to be in the link, Microsoft site it says they ended basic support in 2022. So why is this now effecting us half way through the year in 2023? Older versions of Alteryx work exactly as they are supposed to. Why would this be Microsofts fault? Especially seeing as Basic SMTP is supported by your previous version, and Microsoft has no issues letting it run?

@renat_isch we have also tried to use the DCM connection method in the past using a Data Source with the SMTP Server and Credential of the OAuth w Alteryx App option and it gives us the same results as using the basic username/password method. The DCM method is actually what we were initially using prior to setting it up through a Virtual Server Environment.

Hi @jsumms/ @elliottwood , thanks for your inputs. I was able to replicate that error with basic authentication, whereas Azure AD-based authentication is working just fine for me. Could you please submit support tickets to Alteryx support team - they will collect additional detail we might need to resolve this error.. In the meantime, we will attempt to find the root cause of the behaviour you're facing with basic authentication.

@renat_ish thanks I have a support ticket submitted and am working through this with them at the moment. Hopefully we can get a resolution. At the moment they are thinking it may have something to do with the AMP Engine in the 2023.1 version, but they are currently looking into it further.

Dboff

Hi Renat,

I have changed my configuration to match as per your screenshot but I am still getting the same error. I have 3 emails to be sent, and the error is only showing on the 1st one.

Could you please advise what would be my next steps to fix this?

Thank you,

Daiana

Hi @Dboff, we're aware of the issue and were able to identify the root cause. The problem only persists when using basic username/password authentication. One of our upcoming patch releases will introduce the fix to the issue. I will provide further updates early next week.

Hamder83

I had the same issue, and I sat op a connection over https://sendgrid.com/ in stead. This works as a charm

So now I can send from alteryx, using our email. With sendgrid as smtp

I currently have no ability to use Azure as a connection in my Alteryx. We do not utilize any Azure Directory. Is there not another work around? The email tool is essential to many of our workflows.

juliocor

Because I am having this error when I am sending to more than one email account, my workaround is: instead of connecting a dataset with an email per row to the Email Tool, I am concatenating all email addresses in a single field (separated with comma) and a single row, and it works.

Hi @juliocor , thanks for sharing your workaround with the community. To give you heads up, our upcoming Patch 2 for 2023.1 release will address this issue.

DerikSadowski

Hi @renat_isch I am running into this same issue with some slight differences. We are using Azure-AD authentication and for me it is occurring when the email tool is being used to send more than one email. I am experiencing no problems when I am sending one email per email tool. I wanted to confirm that the patch 2 you mention in your previous post will correct this issue for Azure users as well as users using username/password authentication.

Hi @DerikSadowski, thanks for your message. Yes, I am confirming our upcoming patch will provide the fix to this issue. I will notify you in this thread when the patch is available.

afellows

Why is this marked as solved? As far as I can see there has still been no patch released to fix this. Can we get an ETA on when this will be pushed out?

It's surprising that this bug made it into a release and even more surprising that 3 months after being reported it has not been fixed.

VernOfVrain

What do the settings suggest for google mail?

Hi everyone, thank you for your patience and giving us time to address this issue. I am happy to confirm our latest 23.1 Patch 2 released yesterday is now available for download. The patch addresses the email tool smtp authentication issue. Please install the patch and let us know if it resolves the problem. Looking forward to hearing your feedback.

VernOfVrain

I am not seeing that item in the release notes....
https://help.alteryx.com/release-notes/designer/designer-20231-release-notes

compass

Patch installed, still not able to authenticate using Username/Password. Also noticed nothing about email tool was mentioned in the patch release notes.

lmirandam07

Where are the patch notes...?

Hi @lmirandam07, please review this page for details: https://help.alteryx.com/release-notes/designer/designer-20231-release-notes

kflores27

I have installed the patch in my Alteryx Designer, however all of the flows I need the fix for run on the server. How is this addressed?

luaimatari7

This is issue is still not resolved in the new patch

JamieHankins

I have had the same problem with gmail.

The email tool used to work and still does for one of my colleagues. However, it no longer works to me (probably update related?)

Hi @luaimatari7 / @JamieHankins, We went ahead and tested the patch in our environment and the issue no longer persists. At this point I would encourage you to contact customer support to validate this with them.

charlottemartindale

Did anyone ever find a solution to this? The patched update does not work in 2023.1 or 2023.2 (latest version!!) for OAuth --private authentication.