SMTP notifications throwing an exception w/O365

Question

I'm getting the following error message when trying to send notifications from scheduled tasks to users. This is after configuring the system to use an office 365 support account to send these emails.

My "Mail Settings" for our site are smtp (Our MS smtp server address which i won't list) on port 587
This server requires an encrypted connection (SSL) is checked
This server requires authentication is checked

The account username and password are indeed correct and when i test email settings i do get a test email in my inbox confirming it works. When running the task again though i get the following message below in the logs and the users never receive the email.

Softerra.Adaxes.CommandPipeline.CommandProcessingException: The following command threw an exception while being executed: Send e-mail notification (Your Bay Equity Domain password will expire in 7 day(s)). ---> System.Net.Mail.SmtpException: The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1 Client was not authenticated
at System.Net.Mail.MailCommand.CheckResponse(SmtpStatusCode statusCode, String response)
at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at #Td.#zj.Send(String toAddress, String subject, String textBody, String htmlBody, String fromAddress, String cc, String bcc)
at Softerra.Adaxes.CommandPipeline.Actions.SendMailNotificationAction.ExecuteAction(IAdmTop targetObject)
at Softerra.Adaxes.CommandPipeline.Actions.ActionBase.Execute(IAdmTop targetObjectArg)
at Softerra.Adaxes.CommandPipeline.Actions.ActionBase.Execute(ICommand command)
--- End of inner exception stack trace ---

Comments

Hello,

I've asked our QA team to reproduce the issue in our testing environment and will update this topic as soon as they come up with something.

---

What version of Adaxes are you running?

---

Our version is 2012.1

---

What I need to know is the full version number, including the build number. To get a full version number:

1. Open Adaxes Administration Console.
2. In the Console Tree, right-click the service node of your Adaxes service.
3. Click Properties.
   
4. Find the full version number on the General tab.
   

---

sorry, Version 3.3.8906.4 (64bit)

Answer 1

Hello,

We confirm this as our bug. Thank you for the bugreport!

The thing is when you back up your Adaxes configuration and then restore it again, an incorrect flag is set for credentials in your Mail Settings. The bug will be fixed in our next release.

To remedy the issue until the new release is available:

1. Stop your Adaxes service.

2. Navigate to the folder where your Adaxes service is installed (by default, C:\Program Files\Softerra\Adaxes 3\Service).

3. Find the file called Softerra.Adaxes.Service.exe.Config. The file contains settings of your Adaxes service.

4. Open the file with a text editor.

5. Find the following block in the file:

    <!-- Mail settings -->
      <mailSettings configProtectionProvider="CurrentUserDataProtectionProvider">
        <EncryptedData>
          <CipherData>
             ...
           </CipherData>
         </EncryptedData>
       </mailSettings>

   The block contains Mail Settings of your Adaxes Service.

6. Delete everything that is between the opening and the closing mailSettings tags and also all parameters in the opening mailSettings tags. You should receive:

    <!-- Mail settings -->
      <mailSettings>
       </mailSettings>

   This will delete all the Mail Settings of your Adaxes service.

7. Save the file.

8. Start your Adaxes service.

9. Reconfigure the Mail Settings of your Adaxes Service.

Comments

I've done just that but now the directory service is unavailable on the admin console. I can confirm the service is indeed started and the file does show the changes made though i don't know why i can't mind to the directory.

---

Also there is no firewall enabled on the server and AV has been turned off. It doesn't appear it could be either of these.

---

Take a look at Adaxes Service Event Log. Are there any erorrs or warnings related to the issue? See Service Event Log for information on how to view the Event Log.

Also, try restarting Adaxes service and Adaxes Administration Console.

If this doesn't help, send the edited configuration file to our support email (adaxes@softerra.com).

---

All i see in the logs is the following,

Event ID : 0
Service cannot be started. The service process could not connect to the service controller

I've sent over the edited file.

---

The error message says:

Event ID : 0
Service cannot be started. The service process could not connect to the service controller

but you wrote:

I can confirm the service is indeed started and the file does show the changes made though i don't know why i can't mind to the directory.

So, did Adaxes service managed to start or not?

---

The AdaxesBackend service does show started but that error in the logs is the last thing i see since 9:17 this morning. Does it have dependencies on any other services i'm missing?

---

And apparently i wasn't starting the right service. Was under the impression there was only one. Now the service is actually on and the admin console connected as well. The email has been setup and tested successfully. Thanks.

---

I've had this same bug pop up again. Any idea when Adaxes is going to address this issue for Office 365? Maybe a patch update for affected organizations?

---

Hello,

The issue is reproduced when restoring a configuration backed up with the Back up credentials option disabled. Did you restore Adaxes service configuration recently? If yes, the fix for this issue will be available in Adaxes 2013.1 to be released in a week or two. To remedy the issue, you can perform the steps listed in SMTP notifications throwing an exception w/O365 to remedy the issue.

As a workaround until the new release is available, you can avoid restoring Adaxes service configuration until the new release. We would prefer not to release a custom build with the fix for the issue so short before the new release as we are currently heavily loaded with the pre-release tasks. However, if you need the fix urgently, we will make a custom build for you.

---

The issue was fixed in Adaxes 2013.1. Now, Adaxes correctly backs up and restores Mail Settings even when the Back up credentials option is disabled.

Note that after upgrading and restoring your Adaxes service configuration in Adaxes 2013.1 for the first time, you need to perform additional actions to save Email Settings correctly:

1. Stop your Adaxes service.

2. Navigate to the folder where your Adaxes service is installed (by default, C:\Program Files\Softerra\Adaxes 3\Service).

3. Find the file called Softerra.Adaxes.Service.exe.Config. The file contains settings of your Adaxes service.

4. Open the file with a text editor.

5. Find the following block in the file:

    <!-- Mail settings -->
      <mailSettings configProtectionProvider="CurrentUserDataProtectionProvider">
        <EncryptedData>
          <CipherData>
             ...
           </CipherData>
         </EncryptedData>
       </mailSettings>

   The block contains Mail Settings of your Adaxes Service.

6. Delete everything that is between the opening and the closing mailSettings tags and also all parameters in the opening mailSettings tags. You should receive:

    <!-- Mail settings -->
      <mailSettings>
       </mailSettings>

   This will delete all the Mail Settings of your Adaxes service.

7. Save the file.

8. Start your Adaxes service.

9. Reconfigure the Mail Settings of your Adaxes Service.

After performing these steps once, you can back up and restore Adaxes service settings using the normal back up / restore procedure.