Sage 100

 View Only

  • 1.  "A StartDocPrinter call was not issued" when attempting to print a Crystal Report form or report in Sage 100

    Posted 01-16-2019 12:26
    Edited by Brett Zimmerman 01-16-2019 12:58
    Does anyone have other suggestions for "A StartDocPrinter call was not issued" error when attempting to print a Crystal Report form or report in Sage 100?  This is v2018.5, after Upgrading from v2013.  Below is the kb article.  Client is on a peer-to-peer network so we think it has something to do with that, e.g. a 'share' issue (as per below).  We were previously able to resolve the error, I believe by removing the printer and re-installing, but then it resurfaced. I think I'll also try having them log onto that computer as 'administrator' to see if that helps and/or lead us toward a possible permissions/rights issue, although another wrinkle is that when they get the error, at least sometimes it'll work fine if they just try again.


    Cause

    • Error caused by an issue with the Windows printer share.
    • The error message could instead be due to a Crystal error.

     

    Resolution

    Possible Resolutions:

    • Windows printer share issue:
    • Crystal processing error:
      • Preview the report or form
      • See if another error displays instead:
        • Example: Database Vendor Code 9
        • Example: Database Vendor Code 1011 or 1012
      • Search the Sage Knowledgebase for the other error

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

    RON GOUVEIA12-30-2014 09:03

    Upgrading from Sage 100 Standard 4.4 to v2014SU4. On terminal server one user getting 'Unable to pr...

    • 1.  UPGRADING FROM SAGE 100 STANDARD 4.4 TO V2014SU4.

      0 RECOMMEND
      Posted 12-30-2014 09:03
      REPLY INLINE
      Upgrading from Sage 100 Standard 4.4 to v2014SU4. On terminal server one user getting 'Unable to print AP_Check1.rpt. A StartDocPrinter call was not issued'. Don't see anything like this in Knowledgebase. Any ideas? TIA


    • 2.  RE: UPGRADING FROM SAGE 100 STANDARD 4.4 TO V2014SU4.

      0 RECOMMEND
      Posted 12-30-2014 09:22
      REPLY INLINE
      I had the same error a while back due to a hung print job. Stop and restart the print spooler in the services.


    • 3.  RE: UPGRADING FROM SAGE 100 STANDARD 4.4 TO V2014SU4.

      0 RECOMMEND
      Posted 12-30-2014 09:24
      REPLY INLINE
      thanks Miranda! I'll give that a try.


    ------------------------------
    - Brett
    ------------------------------


  • 2.  RE: "A StartDocPrinter call was not issued" when attempting to print a Crystal Report form or report in Sage 100

    Posted 01-16-2019 14:09
    Does it work from the "server"​?

    ------------------------------
    Jeff Schwenk
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 3.  RE: "A StartDocPrinter call was not issued" when attempting to print a Crystal Report form or report in Sage 100

    Posted 01-18-2019 08:53
    They're running a peer-to-peer and I believe this issue is happening on the computer where Sage resides.

    ------------------------------
    - Brett
    ------------------------------

    Original Message


Related Content