Sage 100

Barebones Sage 100 v4.4 to 2016 UG. I'm still in the testing phase. After installing 2016 the ability for this company to email invoices out of 4.4 appears to be gone. The wonderful 1985 era chilkat program pukes out a few pages of mostly irrelevant information. Unable to login to SMTP connection. ChilkatLog: VerifySmtpLogin: DllDate: Jan 19 2012 UnlockPrefix: SBestSoftMAILQ Username: JUDY-HP2:judy Architecture: Little Endian; 32-bit Language: ActiveX Need new SMTP connection checkForExistingConnection: Elapsed time: 0 millisec SMTP_Connect: Connecting to SMTP server gull1.gull.local:25 smtp_host: gull1.gull.local smtp_port: 25 smtp_user: admin@gullassociates.com ConnectTimeoutMs_1: 30000 calling ConnectSocket2 IPV6 enabled connect with NO heartbeat. connectingTo: gull1.gull.local dnsCacheLookup: gull1.gull.local dnsCacheHit: 172.20.14.10 GetHostByNameHB_ipv4: Elapsed time: 0 millisec maxTimeMs_connect: 30000 myIP_1: 127.0.0.1 myPort_1: 58510 connect successful (1) socketConnect: Elapsed time: 109 millisec InitialResponse: 220 Gull1.gull.local Microsoft ESMTP MAIL Service, Version: 7.5.7601.17514 ready at Wed, 14 Sep 2016 13:27:19 -0400 initialResponse: Elapsed time: 0 millisec sendingHello: EHLO judy-hp2 sendEhlo: Elapsed time: 0 millisec helloResponse: 250-Gull1.gull.local Hello [172.20.14.105] 250-TURN 250-SIZE 250-ETRN 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-8bitmime 250-BINARYMIME 250-CHUNKING 250-VRFY 250 OK 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 Gull1.gull.local Microsoft ESMTP MAIL Service, Version: 7.5.7601.17514 ready at Wed, 14 Sep 2016 13:27:19 -0400 EHLO judy-hp2 250-Gull1.gull.local Hello [172.20.14.105] 250-TURN 250-SIZE 250-ETRN 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-8bitmime 250-BINARYMIME 250-CHUNKING 250-VRFY 250 OK 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

Relevant Sage KB - which I translate to ""we have no clue either"" - thinking maybe someone has run into this. I'm going to try workstation reinstall then kick back and call Sage while I dream of an upgrade where the customer doesn't chase me out into their parking lot because some component of Sage is conflicting. https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=69013&sliceId=1&cmd=displayKC&dialogID=53570&docType=kc&isLoadPublishedVer=&stateId=53572&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

Sounds like the standard/known issue related to the local Common Components folder on the server getting overwritten with the new version upon installing v2016. To get 4.40 e-mailing working again, you need to bring back the 4.40 Common Components folder, and then run regcom.bat (suggest via ""run as administrator). Whenever I do an upgrade on existing server, I always make a bkup of the Common Components folder before installing the new version so that I can easily copy back the old/current version.

Also make copy of the v2016 Common Components folder before bringing back the 4.40 version so that you can easily bring back the v2016 version upon go-live.

Here's a copy of the 4.40 folder in case you don't have it available.

I resolved it this way (BTW - thank you! ) : - Uninstall v440 workstation setup - Rename c:\program files (x86)\Common Files\Sage\Common Components to sage2016.commoncomponents - Re-reun the v440 workstation setup (re-creates the Common Components - presumably only with the v440 DLL files) - Test and the issue resolves The issue is apparently the consolidated use of the common components folder which someone in Sage R&D never saw as an issue when they did it probably because they never actually installed Sage 100 to an actual customer. Thank you again, Brett -- you saved me a few hours on the phone with Sage

Wow, that is a very SAD KB article! Has been a known issue here since the beginning. I believe @JimWoodhead was the first or at least one of the first to post the solution. I always forget about it until I get the call. Should be in my upgrade notes of things to be aware of.

Immediately prior to installing 2016, I usually rename the three version 4 chilkat dlls chilkatmai2.dll, chilkatutil.dll and chilkatcert.dll, or copy them into a ""version 4 chilkat"" folder. Then after installing 2016 copy the three verison 2016 chilkat files into a ""version 53 chilkat"" folder. Then rename the 53 chilkat files in the common components folder and copy the version 4 files back into it. Depending on what version you are using, just swap the diffeernt versions of the three chilkat files in and out of the common components folder.

@DougHiggs - You don't have to reregister them?

You sure do. Forgot that part. Go to a dos prompt. c: then cd \windows\system32 then regsvr32 ""\c:\program files (x86)\Common Files\Sage\Common Components\chilkatmail2.dll"". do this for each chilkat

You have to re-register each time you swap the different versions of the chilkat dlls .

Good to know that I was doing useless steps. I usually open two WIN Explorer windows - one to show the DLL folder and the other to display the folder where regsvr32 is located. Then I drag the DLL over on top of the regsver32 file and let go. It will register. I find that easier than all of the typing which I fat finger on occasion.

Note: I believe you have to do the above process on every local workstation that will be sending via email. At least my fix was on the LOCAL workstation and not the server. I also have not encountered this as much as I might expect and believe the above could only apply to migrations from <4.5 where paperless email transmission is used. I think the KB says that the Chilkat changed at 2013 which implies for upgrades from 2013+ you would not encounter the issue.

You really only need to do it on workstations that use the paperless email from Sage 100 (before the go live date) . All the other workstation can retain the v53 chilkat if they don't need Sage email prior to the cut over. After the cut over everyone has the same 53 chilkat on their computer @JeffSchwenk Your dll registration is great. I will try it next time.

Any little short cut that adds value (eliminates steps) is worth sharing.

We don't recommend installing the new workstation software until the Live upgrade day, just for this reason. Setting up a ""testing"" workstation on a spare machine saves many headaches.

I don't do anything _workstation_-related for this issue; only on the server (as per my posts above).

The Common Components for chilkat are installed on workstations (as we've had this issue hit a few times). I believe the server files are only used with Advanced / Premium and the Spawn Tasks from Server option.