Sage 100

 View Only
  • 1.  I need help. Just upgraded from version 4.4 to 100

    Posted 02-18-2014 19:46
    I need help. Just upgraded from version 4.4 to 100 2013 standard. Email through MAS worked before the upgrade. Tried replacing and registering the 4.4 Chilkat dlls on th 2013 installation and still no luck so changed them back to the 2013 Chilkat dlls. Customer has an in-house Exchange server. MAS is configured to send email to the Exchange smtp server through port 25 with no encryption. Below is the detail of the error when sending a test message: Unable to login to SMTP connection. ChilkatLog: VerifySmtpLogin: DllDate: Jan 19 2012 UnlockPrefix: SBestSoftMAILQ Username: SERVER2008:administrator Architecture: Little Endian; 32-bit Language: ActiveX Need new SMTP connection checkForExistingConnection: Elapsed time: 0 millisec SMTP_Connect: Connecting to SMTP server sbs2011.abccompany.local:25 smtp_host: sbs2011.abccompany.local smtp_port: 25 smtp_user: invoicing ConnectTimeoutMs_1: 30000 calling ConnectSocket2 IPV6 enabled connect with NO heartbeat. connectingTo: sbs2011.abccompany.local dnsCacheLookup: sbs2011.abccompany.local dnsCacheHit: 192.168.20.5 GetHostByNameHB_ipv4: Elapsed time: 0 millisec maxTimeMs_connect: 30000 myIP_1: 192.168.20.3 myPort_1: 53524 connect successful (1) socketConnect: Elapsed time: 0 millisec InitialResponse: 220 SBS2011.abccompany.local Microsoft ESMTP MAIL Service ready at Tue, 18 Feb 2014 14:22:59 -0600 initialResponse: Elapsed time: 0 millisec sendingHello: EHLO server2008 sendEhlo: Elapsed time: 0 millisec helloResponse: 250-SBS2011.abccompany.local Hello [192.168.20.3] 250-SIZE 10485760 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-AUTH 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250-XEXCH50 250 XSHADOW helloResponse: Elapsed time: 0 millisec This SMTP server did not list authentication methods. Defaulting to LOGIN authentication method. login_method: LOGIN 504 5.7.4 Unrecognized authentication type Failed to send AUTH LOGIN 220 SBS2011.abccompany.local Microsoft ESMTP MAIL Service ready at Tue, 18 Feb 2014 14:22:59 -0600 EHLO server2008 250-SBS2011.abccompany.local Hello [192.168.20.3] 250-SIZE 10485760 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-AUTH 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250-XEXCH50 250 XSHADOW AUTH LOGIN 504 5.7.4 Unrecognized authentication type Failed to login using LOGIN method --SMTP_Connect Failed to connect to SMTP server. Failed. --VerifySmtpLogin --ChilkatLog


  • 2.  RE: I need help. Just upgraded from version 4.4 to 100

    Posted 02-18-2014 19:51
      |   view attached
    See attached file - In Exchange Server 2010, find the SMTP Receive Connector, right-click then choose Properties. At the properties page select Authentication. Then click the Basic authentication checkbox. This allow LOGIN method to be used by Chilkat and any other email client (If you're wondering why not use TLS it's because Exchange is not responding to the Chilkat request asking if it supports TLS - so Chilkat defaults to LOGIN).

    Attachment(s)



  • 3.  RE: I need help. Just upgraded from version 4.4 to 100

    Posted 02-18-2014 19:53
    We have had success turning on the encryption and authenticating with a domain user account.


  • 4.  RE: I need help. Just upgraded from version 4.4 to 100

    Posted 02-18-2014 19:56
    Thanks guys for your responses. @EricAnderson - any reason everything worked using 4.4 but now it fails with 2013? Nothing changed on the Exchange server.,


  • 5.  RE: I need help. Just upgraded from version 4.4 to 100

    Posted 02-18-2014 19:57
    never mind... the document explains why. thanks.


  • 6.  RE: I need help. Just upgraded from version 4.4 to 100

    Posted 02-18-2014 20:59
    This was the supplemental unedited workarond document I wrote for Sage Engineering to explain why in v2013 the Sy_EmailEngine.pvc program needed to get fixed to properly support the newer version of ChilkatMail used in v2013. NOTE: This is a workaround as it forces you to lower the email security. IOW you can't use TLS on Exchange Server 2010 (prolly 2013 and 2007 too) with MAS v2013 and that is not because of Chilkat but because they won't retrofit Sy_EmailEngine to accomodate the Chilkat programming changes (they don't really even understand the issue! @#^&*^&) This was largely based on what I learned from an Exchange Server case with for @JimWoodhead 's client from an early v2013 implementation of his.


  • 7.  RE: I need help. Just upgraded from version 4.4 to 100

    Posted 02-18-2014 21:11
    Gracias Alnoor... I will get with their IT guy and see if we can get it to work tomorrow.


  • 8.  RE: I need help. Just upgraded from version 4.4 to 100

    Posted 02-19-2014 11:28
    Email is working. I didn't need to make any changes on the Exchange server. I tried blanking out the user name and password and it worked. The only entry in MAS is the smtp server domain name and port. Thank you to all of you!