In case you missed the announcement: The Alteryx One Fall Release is here! Learn more about the new features and capabilities here
ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests after December 31, 2025. Set up your security questions now so you can recover your account anytime, just log out and back in to get started. Learn more here
Start Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

Email output error Func 'curl_easy_perform' failed, ret = 67, desc =

BAvitia23
8 - Asteroid
Runing Version: 2022.3.1.486 Patch: 3
When attempting to use the email tool I get the following error:
 
Email (1) Record#1: Func 'curl_easy_perform' failed, ret = 67, desc = Login denied
 
Using:

Outlook/Office365

SMTP: smtp.office365.com
Port: 587
Encryption: STARTTLS
SMTP Authentication: Enabled
Username: <Email Address>
Password: <Password>

 

When logging in directly to smtp.office365.com the user/name password are good, not sure why Alteryx is giving the error with the same information. 

 

The IT department is not aware of what could be causing this. 

2 REPLIES 2
lwolfie
11 - Bolide

I'm not sure this will help.  I get this error when I'm running a workflow from server with an email event added.  It results when Alteryx is trying to send an email using the server service account credentials from desktop designer instead of server.  

ShaneXue
6 - Meteoroid

Yes, I faced the same error. It seems there's a bug in the email sending event. I'm using the Designer Desktop + Schedule tool. When I checked the help information, I saw that this error was fixed in the 2024.1 version. So, I downloaded the 2024.1 version. However, when I tried to run the workflow with the new version of the software, the system couldn't find the controller, and Alteryx services couldn't be enabled. So, I had to revert to the 2023.2 version. Luckily, the error I encountered earlier disappeared, and the workflow now runs smoothly. My suggestion is to hold off on upgrading to the 2024.1 version for now, as we don't know what other issues we might encounter.

Labels
Top Solution Authors