Sage 100

Broken paperless email V2013. I am upgrading a client to V2013 and I am having a issue getting paperless emailing on to work. with Sage 100 Standard V2013. I am receiving the below message during the ""Email Test"" and it is not emailing out documents. Plus 2013 workstation setup breaks V4.4 too. Note. if I rename the common components folder and reinstall the V4.4 workstation, I can get the v44 system to work but the 2013 gets objects error. Any bright ideas? Note: The system worked fine on V4.4. before the upgrade Unable to login to SMTP connection. ChilkatLog: VerifySmtpLogin: DllDate: Jan 19 2012 UnlockPrefix: SBestSoftMAILQ Username: HR:anak Architecture: Little Endian; 32-bit Language: ActiveX Need new SMTP connection checkForExistingConnection: Elapsed time: 0 millisec SMTP_Connect: Connecting to SMTP server exchange01.carvincorp.com:25 smtp_host: exchange01.carvincorp.com smtp_port: 25 domain: carvincorp.com smtp_user: martine ConnectTimeoutMs_1: 30000 calling ConnectSocket2 IPV6 enabled connect with NO heartbeat. connectingTo: exchange01.carvincorp.com dnsCacheLookup: exchange01.carvincorp.com dnsCacheHit: 192.168.240.22 GetHostByNameHB_ipv4: Elapsed time: 0 millisec maxTimeMs_connect: 30000 myIP_1: 192.168.240.204 myPort_1: 2620 connect successful (1) socketConnect: Elapsed time: 0 millisec InitialResponse: 220 Exchange01.CarvinCorp.com Microsoft ESMTP MAIL Service ready at Fri, 15 Mar 2013 12:26:34 -0700

Jim - try just manually registering all the Chilkat DLLs in the 2013 version of the Common Components folders

I did the regcom.bat in the common components but didn't manually register them... I will try that.

This came up before - We have an Evernote on it. https://www.evernote.com/l/AQ7yoD9PmKROhZAy5d5dwAtUZ5-uztVV0-8

Unfortunately it is something exchange . I tested the email with my Gmail account and it works so it is some issue with exchange logins. I did validate the credentials with the 4.4 and they are working. Do looks like SAGE broke something. From: do-not-reply@socialcast.com [mailto:do-not-reply@socialcast.com] On Behalf Of Wayne Schulz Sent: Friday, March 15, 2013 5:42 PM To: Jim Woodhead Subject: Re: [90 Minds Consulting Group] Broken paperless email V2013. I am upgrading a client to V2013 and I am having a issue getting paperless emailing on to work. with Sage 1...

Why does it seem 50% of MAS problems these days relate to Paperless?

Here is a Chilkat Test Email vbs I used recently at a client. It's from their website but I changed it up to emulate the way Paperless uses it and during the email send if it fails, it displays the error to the screen and to a text file. Change it up to point to the Exchange server. If the email send fails, look at the error. If it does succeeds but recipient doesn't receive it, have Carvin's IT look at the ""bad mail"" folder on the Exchange Server to see if it got held up there. In my case, Chilkat test vbs was running successfully with no error and recipient was receiving. Then I omitted the .FromAddress in the vbs, that's when it hit the ""bad mail"" just like the Paperless Test in Company Maintenance. However actual forms like POs and SOs emailed okay cuz the From Email-Address from Paperless / Setup / Form Maint was being sent. You might want to try emailing a form directly from the Viewer as well.

Sage 2013 PU 2 has been pre-released to developers - so the general release is on the horizon.

@LeeGraham, can you tell if perhaps they have imbedded the 941 in PU 2?

Paperless should have been updated before they released 2013. They are using such an old driver. They probably did not want to pay maintenance for all these years. I guess they plan to get current with Amuyni this year.

John - yes the PR 941 program is in the PU 2 release file.

... or the Pre-Release file, to be exact.

@AlnoorCassim . here is the updated version for V2013

well I ran into this today also upgrading MAS200 from 4.5 to V2013. The script works fine from an XP machine but cannot get it to run from the Win 2008 server. I registered the .dll. comes back with issue line 6 createobject(""Chilkatmail2.chilkatmailman2"")

We are waiting for a Fix from SAGE for this. Kudo's to Alnoor for finding the issue. Sage didn't have a Exchange server to test.. DOH!!!

Anyone get the fix for this yet?

I think so. Funny I have an appointment to confirm in 10 minutes. It was a setting on exchange. Alnoor assisted on it.

so what has changed if it worked on 4.5 but not on 2013? Why would it be exchange? @AlnoorCassim So nothing to do with Sage?

V2013 uses the new version of Chilkat and it is works differently. it have to do with the anonymous settings.

clicking the Basic Authentication on the Authentication tab of the SMTP Receive Connector in Exchange that should do the trick.

Customer just upgraded to 2013 yesterday and they are getting this error message when trying to electronically deliver SO invoices from 2013: Error on 'SendMail'. ChilkatLog: SendEmail: DllDate: Jan 19 2012 UnlockPrefix: SBestSoftMAILQ Username: WORKSTATION-5:LeAnne.Guyer Architecture: Little Endian; 32-bit This is only part of the message and it differs from Jim's original post but this is all I could find regarding Chilkat. Test email works from Company Maintenance, BTW.

did you change servers? is the new server's ip probably registered with exchange to allow anonymous relaying

Same server.

Can you run the paperless forms via the server? Another thought is to bypass the client's server by using a different SMTP mail server.

Yes, it works on the server. Here is a little more info from the error message: login_method: NTLM Using Microsoft SSPI NTLM. response: 535 5.7.3 Authentication unsuccessful Logon denied. Check username, password, and domain NTLM authentication failed Failed to login using NTLM method

FINALLY figured it out. We had to deselect ""Offer Basic authentication only after starting TLS"" - what a PITA.

Wow! Maybe one of our technical wizards can explain what is going on here..... My rear is getting sore just reading about it.....

Installed v2013 on a workstation and now their v4.4 Paperless isn't working via their Exchange server. I changed the settings to use my Comcast account to get them back up and running for the short term. @JimWoodhead - do you think your ""clicking the Basic Authentication on the Authentication tab of the SMTP Receive Connector in Exchange that should do the trick"" post above is the issue here also???

Can't hurt.

Exchange Server enable Basic authentication 1. Locate SMTP Receive Connector 2. Right-Click select Properties 3. Select Authentication 4. Check the Basic Authentication Checkbox Note: This allows LOGIN method to be used by Chilkat

Thanks

Client IT staff claims they made the adjustment that @JimWoodhead posted about. Still having the issue. Guess I'll sleep on it tonight.

Am attempting to do @ThereseLogeais suggestion with deselecting ""Offer Basic authentication only after starting TLS"" next.

Another big score for @ThereseLogeais for posting the deselecting of the ""Offer basic Authentication only after start TLS"" solution.

Is this the same customer from last November or a new one @JeffSchwenk ?

A new one, but still a v2013 upgrade.

I ran into the same error that Therese Logeais posted above after upgrading a customer from 4.5 to 2013 Standard. But, this was in a virtual environment. 1 physical server with 2 virtual servers. vm1 sbs2011: Set up as a domain controller with Exchange 2010. vm2 Windows 2008 R2: Sage 100 Standard. IT made a change to enable Basic Authentication on the Exchange server and paperless docs were finally sent from the server, but not from the workstations. Sage came back with these steps to try and it worked- On the SMTP Receive Connector properties of the Exchange Server on the Authentication Tab: Transport Layer Security checked. Basic Authentication unchecked. Offer Basic authentication only after starting TLS unchecked. Integrated Windows Authentication unchecked. Externally Secured checked. On the Permission Group Tab: Exchange Servers checked. We decided not to go to 2014 because there is only 1 PU and from past experiences, it's a no-no. Now, it looks like we would have had this issue with 2014. I don't think Sage can create a fix since it requires a modification to the Exchange settings.

@WayneSchulz - Can you verify your Evernote link on the third comment from the top? Appears to be dead for me.....

I think this may be it - https://www.evernote.com/l/AQ7yoD9PmKROhZAy5d5dwAtUZ5-uztVV0-8 PS - I edited the link above too in case any tries it and find that suddenly it works.

Anyone who has successfully configured Gmail as SMTP relay in Company Maintenance, was it a paid Gmail account, or free? Also, what version (2013, 2014, 2015)? TIA

@JohnWilder??

I use my free Gmail account for testing anytime a customer 'cannot email through Paperless Office' 9 times out of 10 it works just fine. That said, 'free account' to your question @BobPfahnl

The main issue with Gmail is that the emails have to come from the authenticated email account. No substitution accounts.

Works using client's paid Gmail account which has Admin user and Advanced Settings in Apps for configuring smtp-relay.gmail.com. I can't find that feature in my free Gmail account, just POP and IMAP.