Sage 100

 View Only
Expand all | Collapse all

Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

  • 1.  Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-11-2021 19:09
    Went live 10 days ago on Sage Advanced 2020 upgraded from 2015. Printing worked fine for 9 days  Printing issues started occurring yesterday intermittently only certain users. They get "A generic error occurred in GDI+"  or "The device is not ready" error printing sales orders to a Okidata 3410 dot matrix. After they get an error, it starts printing blank pages with no error for that user.  Meanwhile other users can print to same printer/same form code with no issues.  Appears to be tied to workstation or user.  A reboot on the workstation fixes it for awhile and then it starts again.   Any ideas?

    ------------------------------
    Kelley Johnson
    Kelley Johnson Consulting
    ------------------------------


  • 2.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-11-2021 19:15
    Did they upgrade servers as well - or was only the Sage upgraded?

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 3.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-11-2021 19:17
    Yes new server as well - Windows 2019 server

    ------------------------------
    Kelley Johnson
    Kelley Johnson Consulting
    ------------------------------



  • 4.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-11-2021 19:27
    Are they using the server's OKI printer. Is CSODBC active?  Oki's have three different printer emulations - OKI, IBM and Epson.  Might want to check to ensure that the driver is is the same as the printer settings.

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 5.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-11-2021 21:28
    Printers are installed on a 2012 fileserver and shared. No CS ODBC. This is the same setup they have had for years using Okidata MLPacemark 3410 driver.

    event log on one of the workstations

    Faulting application name: pvxwin32.exe, version: 9.62.36.0, time stamp: 0x5e4c4330

    Faulting module name: crpe32.dll, version: 13.0.21.2533, time stamp: 0x59a7d440

    Exception code: 0xc0000005

     



    ------------------------------
    Kelley Johnson
    Kelley Johnson Consulting
    ------------------------------



  • 6.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-12-2021 02:35
    Crpe32.dll is the library Crystal uses to interact with the driver.  It is located in either windows\system32 or windows\syswow64.  Try renaming it, turning off uac, then rerunning workstation setup.  If that doesn't work I would try a different print driver.  I know you've "had the same setup for years", but the server and Crystal version are new so the dll probably doesn't integrate with the driver the same way.  As Jeff mentioned, print a configuration page on the printer to check the emulation then change the driver to match.  You can also try using the generic/text driver.​​

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Assistant to the Traveling Secretary
    ------------------------------



  • 7.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-12-2021 09:36
    Saw this yesterday and wondering when the calls were going to start. 

    Kyocera, OKI and other drivers seem to be affected. 

    Windows 10 crashes when printing due to Microsoft March updates (bleepingcomputer.com)

    ------------------------------
    Eric Lunceford
    First Mate Business Solutions
    Oklahoma City, OK
    877-880-8960
    https://www.firstmatellc.com/
    ------------------------------



  • 8.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-12-2021 10:02
    Great suggestions from everyone and I will do a deeper dive on site today and report back. I suspected the windows updates all along as the issue started right after they installed. I pointed that out to IT but they didnt want to spend the time to roll back and wanted to rule out everything else first.  T

    Thank you everyone for the input, it is much appreciated.

    ------------------------------
    Kelley Johnson
    Kelley Johnson Consulting
    ------------------------------



  • 9.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-12-2021 12:17
    Edited by Jeff Schwenk 03-12-2021 12:28
    Just took a call from client on a similar (same?) issue.  He resolved it by uninstalling a recent MSFT update (released this week).  I will post the details when he sends it.

    Update - Here it is.       KB5000802 March 9th update
    He also sent along some links.

    https://www.bleepingcomputer.com/news/microsoft/windows-10-crashes-when-printing-due-to-microsoft-march-updates/
    https://arstechnica.com/gadgets/2021/03/blue-screen-of-the-day-update-crashes-windows-10-pcs-on-print/
    https://www.google.com/amp/s/arstechnica.com/gadgets/2021/03/blue-screen-of-the-day-update-crashes-windows-10-pcs-on-print/%3famp=1

    Kelley, I think your instinct is correct about the windows update!!!
    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 10.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-12-2021 13:09
    Yep.  Looks like it's a Win 10 update as @Eric Lunceford and @Jeff Schwenk indicated.  I received an email last night:

    "Hi Doug we are having an issue printing SOs and only on the dot matrix printer. It prints fine on a laser printer. When the error message pops up, below message shows. "`

    Uninstalled KB5000802 or KB5000808 updates on the Win 10 computers that used the dot matrix printer and all is working correctly again.  I told them to check with IT and make sure uninstalling the updates doesn't create a security vulnerability.


    ​​

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Assistant to the Traveling Secretary
    ------------------------------



  • 11.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-14-2021 10:58
    My client was getting mostly blank paper when printing sales orders to either of their Epson DFX 9000 dot matrix printers; printing to other lasers perfectly fine. I ended up changing the printer setting in devices/printers to 'print directly to the printer' rather than the currently-enabled spool settings

    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------



  • 12.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-14-2021 11:00
    ...but client wasn't getting any error messages.

    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------



  • 13.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-15-2021 09:20
    @Brett Zimmerman That is a blast from the past for printing to dot matrix.  I remember changing that setting "print directly to the printer" as one of the standard troubleshooting steps.  ​

    ------------------------------
    alan niergarth
    Velosio LLC
    ------------------------------



  • 14.  RE: Unable to print SO_SalesOrder4.rpt. A generic error occurred in GDI+.

    Posted 03-15-2021 12:37
    IT removed the updates and resolves issue. Microsoft says they pulled the updates which is not true. They reinstalled. Then another new update KB4601319 also causes the same issue. IT had to remove that as well and put in place group policies to prevent windows updates. What a nightmare!

    ------------------------------
    Kelley Johnson
    Kelley Johnson Consulting
    ------------------------------