amyuni – Schulz Consulting

Sage 100 Paperless Email Electronic Delivery Failing With Rackspace

November 8, 2022 by Wayne Schulz

We have had two of our customers – both using Rackspace – secure.emailsrvr.com – call to report Sage 100 Paperless Email errors. In both cases they suddenly couldn’t use electronic delivery to send Sage 100 paperless office forms.

Fortunately there is a fast fix which you can perform yourself to completely resolve this problem.

A paperless email error mean that critical forms such as sales orders, invoices, purchase orders and payroll stubs suddenly stop going out over the company’s SMTP email connection.

The first (and most common) cause of this type of error is a login password that was changed for the account used to send email in Sage 100.

If you can verify that no account password changes have happened then the resolution might be the same one that I found worked for both of these customers.

The Sage 100 Paperless Email Error Message

In all cases when Sage 100 cannot send an email it will generate a very lengthy and somewhat confusing error message. The error message may look similar to below.

If you are using secure.emailsrvr.com as your SMTP outgoing email connection and your error matches the one shown below then there’s a good chance this fix will resolve your issue.

Here’s the error which both my customers received. I’ve removed only the smtp_user: field and replaced it with [email address here]. In actuality your error message will include the name of the email account being used to send mail.

Unable to login to SMTP connection.
ChilkatLog:
VerifySmtpLogin:
DllDate: Jan 19 2012
UnlockPrefix: SBestSoftMAILQ
Username: RECOS02:Accountant
Architecture: Little Endian; 32-bit
Language: ActiveX
Need new SMTP connection
checkForExistingConnection: Elapsed time: 0 millisec
SMTP_Connect:
Connecting to SMTP server secure.emailsrvr.com:25
smtp_host: secure.emailsrvr.com
smtp_port: 25
smtp_user: [email address here]
ConnectTimeoutMs_1: 30000
calling ConnectSocket2
IPV6 enabled connect with NO heartbeat.
connectingTo: secure.emailsrvr.com
dnsCacheLookup: secure.emailsrvr.com
dnsCacheHit: 173.203.187.10
GetHostByNameHB_ipv4: Elapsed time: 0 millisec
maxTimeMs_connect: 30000
myIP_1: 210.105.50.10
myPort_1: 50785
connect successful (1)
socketConnect: Elapsed time: 31 millisec
InitialResponse: 220 smtp5.relay.iad3a.emailsrvr.com ESMTP – VA Code Section 18.2-152.3:1 forbids use of this system for unsolicited bulk electronic mail (Spam)

initialResponse: Elapsed time: 47 millisec
sendingHello: EHLO RECOS02

sendEhlo: Elapsed time: 0 millisec
helloResponse: 250-smtp5.relay.iad3a.emailsrvr.com
250-PIPELINING
250-SIZE 75000000
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250 8BITMIME

helloResponse: Elapsed time: 31 millisec
login_method: LOGIN
535 5.7.8 Error: authentication failed: UGFzc3dvcmQ6
Failed to get response to login password
ConnectionLog:
220 smtp5.relay.iad3a.emailsrvr.com ESMTP – VA Code Section 18.2-152.3:1 forbids use of this system for unsolicited bulk electronic mail (Spam)
EHLO RECOS02
250-smtp5.relay.iad3a.emailsrvr.com
250-PIPELINING
250-SIZE 75000000
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250 8BITMIME
AUTH LOGIN
334 VXNlcm5hbWU6
YWNjb3VudGluZ0ByZWVzZWNvLmNvbQ==
334 UGFzc3dvcmQ6
PlVtPDJnNVo=
535 5.7.8 Error: authentication failed: UGFzc3dvcmQ6

–ConnectionLog
Failed to login using LOGIN method
–SMTP_Connect
Failed to connect to SMTP server.
Failed.
–VerifySmtpLogin
–ChilkatLog

What Worked To Resolve This Paperless Office Email Error

In both cases the fix was the very same. And it had nothing to do with a changed email password. For some reason we had to change one parameter in the Library Master – Company Maintenance screen.

In the field marked SMTP Encryption I changed the value from NONE to TLS/STARTTLS and then tested the email ( use the “Test E-Mail” button in the lower right corner) and found the issue was resolved.

For SMTP Encryption, the following is an explanation of the encryption each option would use between the SMTP client and SMTP server when sending e-mail.

None – Select this for no encryption. This is traditionally offered on port ID 25

SSL – Also known as Implicit SSL, select this to encrypt the communication for the entire session. This is normally offered on port ID 465

Note: SSL is a deprecated standard. It has been replaced by TLS.

TSL/Start TSL – Also known as Explicit SSL, select this to begin the communication unencrypted, then later when the client issues a STARTTLS command, communication will be encrypted for authenticating and sending the e-mail. This can be offered on a variety of ports including port ID 25, 443, or 587

Important Note: The e-mail engine used in Sage 100 2018 and Sage 100 2017 and lower use TLS 1.0. TLS (Transport Layer Security) is a cryptographic security protocol designed to provide communications security over a computer network and over the Internet. TLS 1.0 and 1.1 standards is deprecated due to known security issues. Major providers such as Apple, Google, Microsoft, Cisco, etc. have either already discontinued use in favor of current TLS 1.2 standards, or have plans to do so in the immediate future.

If the above doesn’t work – and you are using the same smtp.emailsrvr.com as the example – then try re-entering the password for the email account and test your email again.

If that still doesn’t work then you should consult your Sage partner to see if you may need to upgrade your Sage 100 to meet TLS 1.2 requirements which some email providers have been implementing.

If you found this information helpful and would like to receive timely Sage 100 news on a weekly basis – you become a member of my Sage 100 email newsletter. This newsletter goes out Thursday with tips and news related to Sage 100 ( formerly MAS 90 ).

Sage Releases Paperless Driver Update To Resolve Error -30 and Prompting for PDF Location in Sage 100 v2019+

May 28, 2021 by Wayne Schulz

Sage just released an important update for users of Sage 100 Paperless Office. This update is available for Sage 100 2019, Sage 100 2020, and Sage 100 2021.

After Windows updates, users may have seen errors such as:

Sage 100 PDF Converter prompts for a path to create the PDF
Sage 100 opens a “Output File Name” window and suggests a file name of “Crystal Reports – .pdf” when printnig to Paperless PDF
Sage 100 prompts for ‘File name’ when printing to Paperless Office
Sage 100 Paperless Office displays “Save As” window to create PDFs

Sage 100 Paperless Office (Sage 100 PDF Converter) stops responding when trying to create PDF
No response when printing to Paperless Office (Journals & Registers, Forms, Reports)
Receive message “PDF document was not created successfully”
Receive “Printer not activated -30” error message when printing to Paperless Office or creating PDFs via Paperless Office

It seemed that Microsoft Windows updates were updating the AMYUNI PDF driver to a version that was causing Sage to report either a Printer Error -30 or prompt for a location to save the paperless office documents.

Both of these issues were the result of Windows Updates. To resolve this Sage has updated the AMYUNI PDF driver to a version that shouldn’t continue to be modified by Windows updates.

To download the fix please visit the Sage knowledgebase here. In addition, you may wish to refer to this Sage KB article which outlines a way to manually remove the AMYUNI PDF driver which may be required if paperless error messages continue to recur.

Sage 100 Paperless Issue: Printer not activated, error code -41 or Printer not activated, error code -30

May 21, 2021 by Wayne Schulz

We are receiving calls from Sage 100 users who observe an error while attempting to print from Sage 100. In many cases, the company is making use of Sage’s paperless office feature, which allows for the printing of journals, registers, reports, and forms to a PDF file.

The error messages are typically one of the following:

Error Code -41
Error Code -30
Unable to process the lockfile
Printer not activated
Cannot create PDF
PDF not created successfully
Prompt for a location to save PDF

The cause of this error is frequently a Windows update replacing or modifying the driver used for the paperless functionality – AMYUNI – to either an incompatible version or remove some key registry folders, which can result in this error.

The fastest way to correct paperless errors is to reinstall the paperless driver on the affected computer(s).

To reinstall the paperless driver, you must be logged into Windows as a user who is a member of the local Windows administrator group on the computer you are reinstalling.

From the Sage 100 main menu, select File – Run and type in PL_AdvancedOptions_UI

From the resulting dialog box, you can uninstall the drivers and then click install and test

If the above steps work, you should see a successful test during #3, a pdf appearing on your screen with a success message.

Below is a short video from Sage support that illustrates the steps to reinstall the paperless office driver for Sage 100.

Sage has a helpful knowledgebase article – What are the 5 methods to install the Sage PDF Converter which provides additional options for installing the Sage PDF Converter.

The Sage PDF Installation incorporates three elements:

NOTE: User Account Control (UAC)may prevent the installation of the Sage PDF Converter. It is recommended that Windows 7 and Server 2008 Operating Systems disable this feature temporarily, then reboot prior to trying any installation method. Enable UAC after installation is complete and able to create Paperless Office PDFs

Installation of the “Sage PDF Converter” Printer object in Windows
Establishment of the Registry Entry under HotkeyCurrentConfig/Software/Sage PDF Converter
Establishment of the CDINTF300.dll (Driver) to Windows/System32 (32 bit Operating Systems) or Windows/SysWow64 (64 bit Operating Systems)

Printer not activated, error code -41 when printing to Sage 100 Paperless Office

February 8, 2016 by Wayne Schulz

If you’re receiving an Error Code -41 when printing to paperless office through Sage 100, please check that someone hasn’t manually updated the Amyuni PDF drivers.

Presently Sage 100 uses version 500 of the driver. If someone downloaded and applied Amyuni 550 then that may be the reason for your error message.

To fix:

Open Devices and Printers
Right Click on Sage 100 PDF Converter
Select Printer Properties
Open Advanced tab and select Amyuni Document Converter 500

Paperless Office Setup Tips: Ports, Lockfiles

June 6, 2012 by Wayne Schulz

When setting up paperless office – set the printer port (typically the install points it to NULL or LPT1) to SAGE.

When setting up paperless office – turn off the use of lock files via:

File
Run
PL_AdvancedOptions_UI

Note: This has to be done for every company as it is COMPANY SPECIFIC

The lock file use is only needed if you happen to be running other non-Sage instances of the Amyuni application running on your system.

If you are making this change AFTER experiencing issues with lock files – you may also have to go into the registry and remove both the jobs and lock files folders.

USE EXTREME CAUTION. We are not responsible for damage resulting from changes to the system registry which render your system unusable or unstable. These are usually steps best performed by an IT professional.

How To Delete Jobs and Locks folders from the Sage PDF Converter key in the Windows registry. It is only necessary to remove these from the location in the Registry specified here:

On the Windows Start menu, click Run.
In the Open field, enter Regedit and click OK.
Expand the HKEY_CURRENT_CONFIG key using the Plus symbol
Expand the Software Key
Expand the Sage PDF Converter Key
Locate the following folders (if they exist):
Jobs
Locks
Expand the Jobs folder, and delete any subfolders.
Note: Subfolders may prevent the Jobs folder from being deleted.
Delete the Jobs and Locks folders.

For Terminal Server and Multi User Systems:

Go to Devices and Printers in Windows
Remove any “Redirected” Sage PDF Converters. These will normally say something to the effect of Sage PDF Converter (Redirected) or Sage PDF Converter (From Session 9)
Ensure there is only one Sage PDF Converter located in Printers and Faxes, and make sure it is not redirected.
On the Windows Start menu, click Run.
In the Open field, enter Regedit and click OK.
Expand the HOTKEY CURRENT CONFIG key using the Plus symbol
Expand the Software Key
Ensure that the Sage PDF Converter key is present and has 39 values associated with it. If there are no values or if there is only one value that shows “REG_SZ”, Uninstall then Reinstall the Sage PDF Converter on the Terminal Server.

Other resources:

Five ways to install the Sage 100 ERP (formerly Sage ERP MAS 90 and Sage ERP MAS 200) Paperless Office Converter

The Sage 100 Paperless Email Error Message

What Worked To Resolve This Paperless Office Email Error

How To Delete Jobs and Locks folders from the Sage PDF Converter key in the Windows registry. It is only necessary to remove these from the location in the Registry specified here:

For Terminal Server and Multi User Systems:

Contact Us