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.
Solution/Work-Around
- Close the PrintQueue
- Go to the affected PrintEnvironment
- Check the port (name)
- Check the port setup (IP
address, path)
- If necessary create a
completely new PrintQueue
- Then check all PrintEnvironments with the same port
Related Articles & Links- Print Environment Settings
- Add Print Environments &
PrintQueues
- Print and CutQueues
Related Articles
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 ...
Print Environment Invalid or Wrong Version
Problem/Question When importing a Print Environment, the user gets a warning message that says: “Print Environment file invalid or wrong version" This error message appears when trying to import a Print Environment into an older or wrong version of ...
Windows Printer Port
Problem/Question How to create a Windows Printer Port? Solution/Work-Around Please notice that not all printer models do support Windows Printer port Select <Manage> under "Queues" in the Ergosoft ControlCenter Choose the client to which you want to ...
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 ...