Hi, this is a Windows Update issue and will occur with any printer being added. The solution is to reboot the workstation after installing or re-installing a printer.

John Nichols

Sage

Why does the Sage PDF converter have to be reinstalled after Windows Updates?  Is there anything being done to prevent this from happening after an update? 

Hi, In the Sage 100 2019 release the Amyuni Driver (Sage PDF Converter) was updated to the 6.0 version of the driver.  Amyuni addressed the windows update issues with this release. Versions of Sage 100 prior to 2019 may continue to experience the windows update issue.

John Nichols

Sage

Our client is using Sage 2019 and has to run PL_AdvancedOptions after windows updates.  Are there any additional settings that he needs to change to prevent this?  

Our client is using Sage 2019 and has to run PL_AdvancedOptions after windows updates.  Are there any additional settings that he needs to change to prevent this?  

Hi, I'm not sure why that would happen.

What happens to Paperless printing that is causing the client to run PL_AdvancedOptions_ui after the Windows update?

I haven't heard it reported in Sage 100 2019 or newer. The only think I can think of is security on the registry is not being updated due to user rights.  

On the workstation set permissions in the registry to Full Control everyone 

HKEY_CURRENT_CONFIG\Software\Sage 100 PDF Converter\Configurations

John Nichols

Sage

Hi jcnichols,

Edit to add: Current converter diver is "Amyuni Document Converger 600, version 6.3.9600.16384"

I'm one of the clients having this issue mentioned above. I'm on Sage 100cloud Advanced 2019, v6.10.2.0.   I've checked the registry you mentioned and it's marked full control for everyone at both the Sage 100 PDF Converter and Configurations levels. I checked a couple different workstations that have had this issue multiple times over the last few weeks and they were both set up the same way, full control for everyone.

The issue is that we receive an error saying "Printer not activated, error code -30". The if you proceed to PL_AdvancedOptions_UI you can reinstall which fixes the issue temporarily (a few days usually).

Alternatively, you can attempt to run a test of the converter, after which you receive the same error previously mentioned, then proceeds with an additional "Error #15: Operating system command failed, Program: SY_PDFConverter_ui.pvc, Line 103". (Full error details below).

Any further information on how to prevent this would be extremely appreciated. It's been like the plague for a long time.

Here is the info window:

Here is the contents of the Objects tab:

Object Identifer   Name

---------------------------------------------

[100001]           *appserv/apssrv

[100002]           SY_Session

[100003]           SY_File

[100004]           SY_Crypto

[100005]           SY_Registration

[100006]           SY_Theme

[100007]           SY_UI

[100008]           SY_LocaleInfo

[100009]           SY_Security

[100010]           SY_Security

[100011]           PL_AdvancedOptions_ui

[100012]           *obj/openssl

[100013]           *obj/openssl2

[100014]           *obj/openssl

[100015]           *obj/openssl2

[100016]           SY_Utility

[100017]           SY_EmailEngine

[100018]           SY_FaxEngine

[100019]           CM_Customizer_Svc

[100020]           SY_ErrorInfo_UI

[100021]           SY_Collection

[100022]           SY_ErrorInfo_BUS

[100023]           SY_DocDateWarn

[100024]           SY_BusinessColl

[100025]           *obj/folder

[100026]           *obj/group

[100027]           *obj/tab

[100028]           *obj/tab

[100029]           *obj/tab

[100030]           *obj/tab

Here is the Files tab:

Channel        File Name

---------------------------------------------

32753          *memory*

32754          *memory*

32755          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_Module.M4T

32756          \\mlc-app01\Sage100\v2019\MAS90\SOA\SY0CTL.SOA

32757          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_Company.M4T

32758          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_ReportManagerFormat.M4T

32759          *memory*

32760          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_UserSecurity.M4T

32761          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_User.M4T

32762          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_Task.M4T

32763          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_RoleSecurity.M4T

32764          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_UserSecurity.M4T

32765          \\mlc-app01\Sage100\v2019\MAS90\MAS_SYSTEM\SY_Task.M4T

32766          D:\Sage100\v2019\MAS90\providex.dde

32767          D:\Sage100\v2019\MAS90\providex.ddf

And here is the Stack tab:

Stack    Line       Program

----------------------------------------------------------------------------------------------------

00014   00001  D:\Sage100\v2019\MAS90\SY\SY_ErrorInfo_ui.pvc

00013   00143  D:\Sage100\v2019\MAS90\SY\SY_ErrorInfo_ui.pvc

00012   00040  D:\Sage100\v2019\MAS90\home\lib\_winproc.xeq

00011   07120  D:\Sage100\v2019\MAS90\home\lib\_winproc

00010   00550  D:\Sage100\v2019\MAS90\home\lib\_nomads.pvc

00009   02164  D:\Sage100\v2019\MAS90\SY\SY_CommonUI.pvc

00008   00495  D:\Sage100\v2019\MAS90\SY\SY_ERROR

00007   00103  D:\Sage100\v2019\MAS90\SY\SY_PDFConverter_ui.pvc

00006   00240  D:\Sage100\v2019\MAS90\SY\SY_PDFConverter_ui.pvc

00005   00040  D:\Sage100\v2019\MAS90\home\lib\_winproc.xeq

00004   07120  D:\Sage100\v2019\MAS90\home\lib\_winproc

00003   00550  D:\Sage100\v2019\MAS90\home\lib\_nomads.pvc

00002   02164  D:\Sage100\v2019\MAS90\SY\SY_CommonUI.pvc

00001   00325  D:\Sage100\v2019\MAS90\soa\SY_StartUp.M4P

Hi, I do not see the version you are reporting

 "Amyuni Document Converter 600, version 6.3.9600.16384"  as part of the Window Update.

The last Windows Update Version is 6.0.2.9

The current version available for Amyuni is 6.0.3.1

Can you check to see if there is other software on the workstation utilizing an Amyuni Driver besides Sage 100?   I do not see version 6.3.9600.16384 as a valid version. 

An error 30 means the driver being run is unregistered. Sage 100 registration for the driver is valid for all 6.x versions of the Amyuni PDF Converter.

Per the Amyuni website

"Improved Windows 10 support, no need to reinstall after each Windows 10 update "

You may want to open up a support case and tag my name to it and we can setup a dial (live connect) in session to try and resolve this.

John Nichols

Sage

Thank you John, it may all be coming together! I see this in the about window of the Sage PDF converter:

I pulled that driver number from device properties here:

When you recommended opening a support case I'm assuming you mean with Sage support, correct? If you'd still recommend I do that I certainly can. I assumed the Sage installer would be installing and licensing the PDF converter properly.

Hi,

Your 1st screen shot in your last post shows
AMYUNI Document Converter

Sage distributes
Amyuni PDF Converter   (This screen shot shows the latest version of the driver from Amyuni not the version included with the installation of Sage 100)

These are 2 separate packages/versions of a PDF printer and a PDF printer/creater.

Please uninstall the AMYUNI Document Converter or other Amyuni packages that may be installed on the workstation

Remove older versions of the Amyuni Document Converter Printer Driver

Control Panel\All Control Panel Items\Devices and Printers
Select Sage 100 PDF Driver
Printer Server Properties
Drivers
Please rmove older drivers that are not version 600
Remove all Amyuni Document Converter XXX *except Amyuni Document Converter 600

Sage Support - Yes.  The reason I suggest a call is to resolve the issue more efficiently.

Thanks 

John Nichols

Sage

I have a Windows 7 workstation we are using for a 2019 Advanced upgrade from 2017.  When we print to PL, we get a window popping up prompting for an Output file name.

I have removed all Amyuni drivers except the 600.  Registry setting full control for all users.  But the Amyuni driver version is 6.0.2.9, not 6.0.1.1.  How do I replace the driver version?

Check out Sage Knowledgebase Article 'Paperless Office printing prompts manually for PDF location after Windows updates installed (103205)

Thanks!  That worked!