IMPORTANT ANNOUNCEMENT

These forums were permanently set to read-only mode on July 20, 2022. From that day onwards, no new posting or comment is allowed on the site, but the historical content remains intact and searchable.

A new location for posting questions about PlanetPress Suite is now available:

OL Learn - PlanetPress Classic (opens in new tab)

Topic Options
#53877 - 08/31/16 09:43 AM printer failed initialize
spen Offline
OL Newbie

Registered: 08/22/16
Posts: 3
We use Optimized PostScript. When you use the Split job every option I get this error message : Printer failed to initialize. It does this on all of our fiery printers and it does this when you print to a PDF.

This option has worked in the past. I have re-install all my printers and have re-install Printshop Mail. I am running 7.2.6.

The jobs print find if we don't use the Split Every option.

How do we fix this?

Top
#53881 - 08/31/16 06:09 PM Re: printer failed initialize [Re: spen]
Jeff_K
Unregistered


This is a known issue due to Windows updates.

Please remove:
windows7 KB3177725
windows 10 KB3176493

Top
#53905 - 09/06/16 01:25 PM Re: printer failed initialize [Re: spen]
spen Offline
OL Newbie

Registered: 08/22/16
Posts: 3
thanks..that fix the problem

Top
#54800 - 04/10/17 03:15 AM Re: printer failed initialize [Re: spen]
ivang Offline
OL Newbie

Registered: 04/10/17
Posts: 5
I also got this error message when try to "Save as PDF" : Printer failed to initialize.My OS is Windows Server 2008 R2 Foundation.
Can you help me?

Top
#55114 - 07/21/17 04:13 PM Re: printer failed initialize [Re: Anonymous]
spen Offline
OL Newbie

Registered: 08/22/16
Posts: 3
this issue has came back. the PC does not have this windows update.
can there be something else causing this problem again.

Thanks

Top
#55122 - 07/27/17 05:12 AM Re: printer failed initialize [Re: spen]
Sander vd Berg Offline
OL Expert

Registered: 06/10/08
Posts: 207
Loc: Objectif Lune NL
This was something Microsoft had broken in one update and fixed in a later update.

Removing the faulty update was only necessary in 2016 while we were waiting for Microsoft to issue an official fix. All you should need to do now is make sure the latest updates are installed.

Please open a support ticket if the problem persists. It may be a different issue altogether.

Top