Error code 30 PDF Terminal Server

SOLVED

We continue to get "error code 30 printer not activated" on a terminal server 2018, WIN 10. We have manually installed the PDF converter with all boxes checked, and ran Regedit on HKEY_CURRENT_CONFIG\Software. We've turned off UAC and all users have read and write permissions.

We have also turned off antivirus and firewall.

Is there anything we need to do to get paperless to work in a remote environment?

  • +1
    verified answer

    Try not sharing printers with the remote session.

  • +1
    verified answer

    For the latest versions of Sage 100 using newer Sage 100 PDF converter (replaced older Sage PDF Converter) - it has updated Anyuni converter driver - the "Printer not activated: -30" is usually a timeout error when the Print job takes longer than a preset time (I believe it is 20 seconds). You can test by doing a Preview of the document experiencing the error and If the duration of the print job exceeds 20 seconds (or timeout amount), then the Paperless error will occur. Or print to a printer (if printing Forms or Reports) and time the response time to generate the report.  If issue happens on certain machines compare the time to others and see if there is a delay not using Paperless and fix that.

    You can review the Supported Platform Matrix (SPM) to confirm the environment, but if it happens only on 1 or some workstations and not others, you may need to look into why the performance is less optimal on that workstation.

    There can also be problems in Paperless Office in general if the PDF files are being stored somewhere outside the Sage 100 server, you can review the Paperless Office settings to confirm location (Journal/Register Maintenance, Form Maintenance, etc.).

    I also saw a discussion on that error related to printer security: 

    "For the Sage 100 PDF Converter, check Printer Properties >Security. Make sure the group EVERYONE is in the ACL and is granted full rights.

    Sometimes it needs an additional step: something is adding additional security principals to the list and THEY need the Full Control permission."

  • 0 in reply to DGR

    Thank you! We changed Printer Property security and unchecked printer to no redirect and the error went away. Also, performance of printing / updating went faster.