Billing Email Issue for Sage Timeslips Premium Elite 2023

SUGGESTED

I receive an error message when I try to Email a bill to clients. I have all boxes checked and then I tell it to email to clients, I make sure the client's name is checked & email is correct. I then receive a message that says "Sending emails was completed. 0 of 1 email messages sent." I click  "View Log" and receive this message. (NOTE - Client's name is XXXX for privacy). Can anyone help with this? 

I have tried several different methods and it always does says same thing. Looks like it goes through but always says "Sending emails was completed. 0 of __ email messages sent."  

Reprint Bills: 2/26/2024

Start Time: 4:11:34 PM

End Time: 4:11:35 PM

 

Email Client: MAPI64

0 of 1 email messages sent

 

Client                        Invoice Number      Status

-----------------------------------------------------------------

XXXXXX                       I:555555            Failure : Unknown Error

  • 0

    Hi Natalie, my guess is that you need to install the latest service release for Timeslips Premium (build 30.0.5.96) which introduced 64-bit support for connecting to Outlook.  You can confirm your build # in the help menu and about Sage Timeslips.

  • 0
    SUGGESTED

    Hi Natalie,

    Based on the info you sent, we can assume you have installed the latest version, and while the 64-bit functionality works for most folks, it does not for others.

    The "Unknown Error" is coming from Outlook, and we have no method to determine the cause of the Outlook failure for certain.  We have seen issues where the Outlook security was set to deny 3rd party applications from sending, other instances where the security pop-up stating that an "application is attempting to send an email on your behalf".  Microsoft has dozens of answers on this, and they all work on different systems differently.  You or your IT can start here at Microsoft and see if this works for you - A program is trying to send an email message

    In other cases the option that has consistently worked for us is to remove the 64-bit Microsoft 365 and install the 32-bit version.