x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 87 subscribers
  • Views 8817 views
  • Users 0 members are here
Browse Forums
Announcements
289
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
43
topics
90
replies
Payroll, Time Tracking, and Job Cost
775
topics
1k
replies
Reporting and Analytics
960
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
emaher

Getting printer error 30 printer not activated when generating PDF direct deposit stubs.

SUGGESTED
Posted By

We are on Sage 100 2014 update 6

 

Most stubs generate just fine, it's just one or two (and NOT the same one or two) every pay cycle that throw an error 30 and fail to generate.  Approximately 400 stubs are generated each payroll cycle.

Sage directed me to remove the "Sage PDF Converter", leaving only the "Sage 100 PDF Converter".  This had no effect on the problem.

Anyone else encountered this and/or found a solution?

  • 0
    Hi,

    The error 30 is a PDF driver time out.
    Can you provide some additional information, or can you provide a Sage support case# from support.

    Sage 100 2014 update 6

    * Advanced, premium or standard?

    * If Sage 100 Standard, is it being run across a network or locally?

    * Is this a Terminal Server\Citrix install?

    * Version of PDF Driver?
    Use Windows update to get latest 5.x version (5.0.1.9)Devices and Printers/Sage 100 PDF Converter/About Tab

    *File Version of Crystal Reports runtime engine?
    C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\crpe32.dll
    Locate the DLL \ right mouse click\ Properties \ Details

    Thx
    John Nichols
    Sage
  • 0
    We are on Sage 100 2014 Advanced and were directed by our reseller to go in to the properties of the Sage PDF Converter and add a local port called sage and assign the converter to that instead of nul:. We weren't having issues but were told this helps prevent issues.

    I am curious why your converter would be called Sage 100 PDF Converter and ours is just Sage PDF Converter.
  • 0 in reply to Jon_K
    Sage 100 PDF Converter is the new version (new driver), fixing a number of issues, included with newer versions / Product Update levels.
    Sage PDF Converter is the old version (old driver), requiring the port fix you mention, and permissions adjustments.
  • 0 in reply to Jon_K
    Hi,
    In Sage 100 2014 PU4 (2013 PU8), the PDF printer name was changed to "Sage 100 PDF Converter". Instances of "Sage PDF Converter" were not removed (for backward compatibility). The PDF driver was also updated. There is no reason to change the port name to sage or anything else, Amyuni (the developer of the PDF driver) recommends a nul: port for both x64 and x86 operating systems (the only time this would have mattered is with the 3.x version of the driver.) The current driver is version 5.0.1.9 and available via Windows Update. Hope this clarifies.
    John Nichols
    Sage
  • FormerMember
    0 FormerMember in reply to jcnichols

    I am encountering "printer not activated, error code -30" when attempting to create a pdf from a standard report. 

    We are on Sage 100 Contractor 2018.  The OS is Windows 10.  Both the application and the DB are on the same desktop. 

    In our printers and scanners dashboard the Sage 100 Contractor PDF Export shows 4 documents in queue, but the error does not save the PDF to any location.

    After the original error a follow up error appears:

    Error in processing report. Error details: The system cannot find the file specified.

    Any help is appreciated.  Thank you.

  • 0 in reply to FormerMember

    Try going to your printer properties, and make sure the port for the Sage PDF printer is set to NUL:.  This seems to have fixed it for us.

    We were also told by Sage that the system only allows 20 seconds (IIRC) for a print job to complete.  If it doesn't complete in that amount of time, you'll get an error.  The timeout cannot be increased.

    Finally, verify that you are not running Sage from a UNC path (\\servername\sharename).  It needs to run from a drive letter.  I believe you will have to uninstall and reinstall to change this.

  • 0 in reply to FormerMember

    Dozer,  this is Sage 100 ERP forum not Sage 100 Contractor.  Although the answer may be similar you may want to repost your question in the Sage 100 Contractor forum.

  • 0 in reply to TomTarget

    I have a client just going live on PR Direct Deposit and they are running into the same issue.  Sage 100 v2017.3 Standard. I had followed the KB article to put in the Registry fix 2 days prior to the live payroll and successfully sent stubs to PDF, but the error recurred during the live payroll.  It got through 2 or 3 stubs, then threw the error.

  • 0 in reply to FormerMember
    SUGGESTED

    Go to Printer Properties>Security

    Make sure the group EVERYONE is in the ACL and is granted full rights.

    Now heres the additional step we have randomly been seeing on some installs.. Microsoft (or someone else) is adding additional security principals to the list and THEY need the full control permissiion. Once you verify everything on the ACL has full contol, your Error 30 will probably disappear. Hope that helps

*Community Hub is the new name for Sage City