Sage 100

v5.1 advanced. Customer started having issues when emailing invoices through Sage. In the past, they would load the daily batch of invoices into Invoice printing, and it would send them all out no problem. In the last 4-5 days, there have always been a few that show an error when Sage tries to email. The number of such errors in emailing has been increasing every day. Has anyone seen this? Error message: Unable to verify SMTP connection. ChilkatLog: VerifySmtpConnection: DllDate: Jan 19 2012 UnlockPrefix: SBestSoftMAILQ Username: MCSSERVER2:dhiggs Architecture: Little Endian; 32-bit Language: ActiveX Checking TCP/IP connectivity to the SMTP server. This does not check the login/password. Checking connectivity to SMTP server mailmidwestcoinc.com:25 smtp_host: mail.midwestcoinc.com smtp_port: 25 ConnectTimeoutMs_1: 30000 calling ConnectSocket2 IPV6 enabled connect with NO heartbeat. connectingTo: mail. midwestcoinc.com dnsCacheLookup: mail. midwestcoinc.com Resolving domain name (IPV4) GetHostByNameHB_ipv4: Elapsed time: 16 millisec maxTimeMs_connect: 30000 maxTimeMs_connect: 27503 maxTimeMs_connect: 25114 maxTimeMs_connect: 22851 maxTimeMs_connect: 20681 maxTimeMs_connect: 18542 maxTimeMs_connect: 16294 maxTimeMs_connect: 14124 maxTimeMs_connect: 11970 maxTimeMs_connect: 9690 maxTimeMs_connect: 7520 maxTimeMs_connect: 5366 maxTimeMs_connect: 3087 maxTimeMs_connect: 917 timeout waiting for connect to complete numSec: 0 numMicroSec: 917000 Connect function failed. SocketError: WSAEWOULDBLOCK The socket would block. For more information see this Chilkat Blog post: http://www.cknotes.com/?p=210 Failed to connect to SMTP server. --VerifySmtpConnection Failed. --ChilkatLog

What is typical size of invoice batch?

Average number of invoices is 30.

So it is blowing on your SMTP connection also??

I had a similar issue with a client. It turned out that the error was happening if a batch was emailing and then a different user emailed an invoice through Customer Viewer or a different invoicing batch. It seemed like the server couldn't handle the two instances so it threw an error on the first batch that was running.

@JeffSchwenk Not sure what's happening.