Error when sending data to "Port name"
Problem/Question
When sending print data, the following error message appears from the Print/CutQueue
“Error when sending data to "Port name". The process hosting the driver for this device has ended."
This error message indicates that there are connection problems between the Print Environment used and the Print/CutQueue.
During the Output Device check, the connection field is grayed out and can not edited. The Print Environment is broken.
Solution/Work-Around
To fix this problem copy the Print Environment and set up the Output Device complete new.
Related Articles & Links
Related Articles
Error 1200 The specified device name is invalid
Problem/Question After a job is screened and sent to the device, this error message occurs: "Error 1200 The specified device name is invalid" This problem usually occurs when something has been changed or renamed in an existing PrintQueue. ...
What is the Support Data ZIP file?
Problem/Question "What is the purpose of the Support.zip file?" The file support.zip contains information as well as relevant data about the installed version of the Ergosoft RIP and can be a great help in troubleshooting. Below you will find a ...
Print or Cut Environment outputs PPL file instead of desired PRN, PRT, Cut file
Problem/Question When printing with a Print Environment or Cut Environment that uses a file interface (E.g. Zuend), the driver will output a .ppl file instead of the required file type like .prn, prt, .cut, etc. The .ppl file is an Ergosoft internal ...
Use Epson USB port
Problem/Question How is an Epson USB Port added to the Print Environment? Since there is no Option for it when adding a new Port. Solution/Work-Around As Epson USB does not have its own interface between the Ergosoft RIP and printer, a Windows ...
How to load an XML resolution file into a Print Environment (Universal Driver)
Problem/Question You receive an error message when closing the Print Environment after loading a new XML file in the Device options? Re-open the Print Environment might be the solution. Not every driver is able to access the XML data right after ...