Sage 100 PDF Converter - Unspecified

SOLVED

We have several clients that are having issues with the Sage 100 PDF Converter printer after installing Windows updates and running the pl_advanceoptions_ui utility.  In Devices and Printers the Sage 100 PDF printer shows in an area called Unspecified.  You cannot access the properties of this printer but you are able to print Paperless.  In one case we deleted the printer and tried to reinstall but were unable to recreate the printer.  The only way to get it back was to uninstall the Windows updates and then reinstall the Sage PDF Converter printer. 

Has anyone else experience this issue?

Thanks

Sue

  • 0

    Ran into this today after running wksetup on a new workstation. We uninstalled the printer using pl_advancedoptions_ui, reinstalled using that utility, and it was still in the unspecified area. Restarted the workstation and then it appeared in the printers area.

  • FormerMember
    0 FormerMember

    We have same issue, but I just print to a Print to PDF printer instead and I don't have any issues and I don't have to uninstall etc. 

  • 0

    After each Feature update, we either have to remove the printers using pl_advanceoptions_ui or change a registry setting.

    On the 2019 install it is making me remove and reinstall them right after the initial install.

    I have not reported the issue to sage but I think i have seen KB articles on it.

  • +1
    verified answer

    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

  • 0 in reply to jcnichols

    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? 

  • 0 in reply to 6538

    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

  • 0 in reply to jcnichols

    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?  

  • 0 in reply to 6538

    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

  • 0 in reply to jcnichols

    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

  • 0 in reply to llevron20
    SUGGESTED

    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