Diresu
asked on
PostScript Error: invalidrestore
I have several users here (All Windows XP machines) that are receiving the below error when printing to a Lexmark Optra W810 PS printer.
ERROR: invalidrestore
OFFENDING COMMAND: restore
STACK:
-savelevel-
-dictionary-
-dictionary-
-dictionary-
-dictionary-
-dictionary-
Couple of things to note. This usually happens when they print out of Adobe Distiller. What's odd about this issue is that the document itself usually prints out fine without any visible issue, but then it prints an additional page with nothing but that error message on it.
Solutions I've Tried
1. Reinstalling printer drivers on the user machine
2. Reinstalling printer driver on the print server
3. Reinstalling the offending Adobe application
4. Made sure Server 2003 is patched and up to date (Per suggestion in a microsoft KB article that described a similar error.)
5. Printed to a different printer, same document....no issues/error
Thats all I can think of right now. Let me know if you need additional information.
-Diresu
ERROR: invalidrestore
OFFENDING COMMAND: restore
STACK:
-savelevel-
-dictionary-
-dictionary-
-dictionary-
-dictionary-
-dictionary-
Couple of things to note. This usually happens when they print out of Adobe Distiller. What's odd about this issue is that the document itself usually prints out fine without any visible issue, but then it prints an additional page with nothing but that error message on it.
Solutions I've Tried
1. Reinstalling printer drivers on the user machine
2. Reinstalling printer driver on the print server
3. Reinstalling the offending Adobe application
4. Made sure Server 2003 is patched and up to date (Per suggestion in a microsoft KB article that described a similar error.)
5. Printed to a different printer, same document....no issues/error
Thats all I can think of right now. Let me know if you need additional information.
-Diresu
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks for the points, Diresu. Did any of my suggestions help, if so which one?
ASKER
Sorry for the late response. Been busy around here.
It was indeed a corrupted graphic. A logo that we been using for a long time so we didn't think to look at that as a possible source of the issue. Taking that out resolved the issue and we have an updated one we are going to use instead that seems to work well with no issues.
It was indeed a corrupted graphic. A logo that we been using for a long time so we didn't think to look at that as a possible source of the issue. Taking that out resolved the issue and we have an updated one we are going to use instead that seems to work well with no issues.