Xerox 700i Digital Color Press and Windows Driver

[alexkukk · Accepted solution]

The story had a sequel...

>Well, if it happened immediately after the system was reloaded, and not only after applying updates.

This is happend with all updates is applying. Now I just tried reload RIP to factory, test it without updates - it is working! Looks like problem was be in some updates. SOLUTION!

[Joe Arseneau]

Well, if it happened immediately after the system was reloaded, and not only after applying updates, then the issue is specific to the device, and since the software cannot be the issue in those circumstances then the only thing left is hardware. So if reversing the SCSI connecter between the RIP and the copier changes nothing, you would require a technician to come on site to Diagnose where that failure is.

[alexkukk]

Great idea but still not work....

[Joe Arseneau]

Go to EFI.com and grab the latest driver for the Fiery.

Then in CWS create a new Virtual Printer called "print2" (Device center > workflows > new)

Then install the new driver locally on the Fiery to the queue "print2"

Print to that one and see if it still faults.

There is a post on EFI's forum, but nobody ever helped the only other person who has reported the is...

I will keep looking, I hesitate to install Windows updates on my lab equipment as it puts it out of spec and causes issues like this. we try to only run the updates approved by EFI on their systems.

[alexkukk]

Well... thanks again! "Just-in-case" was made Full System clone before that updates. Firewall was disabled "forever". About Fiery System Update - all updates is done! Windows update now is it done also. Nothing is changed... print from CWS all OK! ... but from Windows print driver - not. I'm repeating - I tried to print from locally from RIP. This means - network connection is not used, no firewall, no closed ports... I'm a little in panic.

[Joe Arseneau]

Hopefully you read this before running updates.

I highly suggest not running Windows updates directly.

Click on the Fiery's start menu and go to All Programs > Fiery > System Updates

Then install all the updates through there. By default it will only be set to Notify for updates, but that never works because it notifies you by email that they are available, and nobody really sets up a Fiery to email, and when they do the tend to not create the Fiery admin email address.

Also, this may have been fixed by now, but there was an issue with SP2, or around the same time in another patch, that would enable the Windows Firewall. This also happens often when running Windows updates directly. The trouble is it blocks much needed ports, so the Web interface ,Connection by CWS, scanning and the retrieval of print jobs via driver all get blocked.

Simply go back in and disable the Windows Firewall if that happens to you.

[alexkukk]

Thanks, Joe!
You just read my mind :) Yesterday I try that solution: Remove printer, delete drivers from Windows 7 "Print server properties". That means - do a complete removal. After, do like in your post. Still nothing works. Also I was surprised - into Fiery EX RIP via RDP logon locally I have the same error message... but I just tried to print Windows standard test page! Today I will try launch Windows 7 Update in my Fiery RIP and post the result in here. If you have any idea, please let me to know!

[Joe Arseneau]

If CWS jobs import and print fine the Fiery is not the issue, the driver is. Remove the print driver from the PC/Mac/Server and reinstall a fresh downloaded copy obtained from the Fiery webtools under the downloads tab. Make sure to do a complete removal and not just right-click and remove.

[alexkukk]

Running a Xerox 700i Digital Color Press with an Fiery EXi External server. The copier and the server once lost connection. After restart server, every job sent to press from Windows printer drivers - print two pages with the "PS undefined error, offending command currentmatrixOrig" error. But then I use Fiery Command Workstation soft and PDF file format - this press works fine! Yesterday I make the "full factory restore" with original DVD, but this error still present. Any suggestions?