I am getting the same error on Windows 7. Wednesday, February 3, PM. Proposed as answer by blucier Monday, March 22, PM. Tuesday, March 9, AM. Hi John I can imagine, this will be the solution. I'm going to test it with several clients on next days. As first I'm going to create the new registry key manually. Inbetween I'm trying to find out how we can implement this new registry key with a GPO.
Any suggestions for me? Tuesday, March 9, PM. Thank you for the answer John. We've been struggling with this randomly occurring print issue since W7 released. My initial tests have found this reg hack to work after restarting the print spooler. All our network printers reside on a W2K3 server. Hoping to see something formally on this from Microsoft.
Monday, March 22, PM. Very simple solution using Group Policy Preferences. Once you upgrade your print server to or higher, you can simply change the value back.
Wednesday, March 31, AM. Hi there, I've not been able to find that registry path on our Windows 7 x64 clients. Any additional steps? Tuesday, April 6, AM. Wednesday, April 14, PM. It was fine until a few weeks ag Looking from the XP client, the print Q accepts the job, says its OK, and then the job disappears.
I can delete it, restart it, etc, but nothing actually happens I have tried your reg fix but to with no success. I can only get the "stuck" job to print by restarting the print spooler on the W7 machine Any ideas?
Thursday, April 15, PM. Hi John - again. I should have said W7 Profesional, not Premium. I am using Windows Registry Editor Version 6.
Tuesday, May 25, PM. Does anyone have a solution if we dont have the particular reg key on client machines Thanks. Friday, July 2, AM. Hi Is this thread dead or is there no answer to this problem. Any assistance would be great as its becoming a nuisance to users now.
Wednesday, July 14, PM. The answer from John Dickson above resolved our issue. Thursday, July 15, PM. Restart Print Spool service and you'll be set. Will be interested to see the article when it is posted, perhaps a link could be posted here. Friday, November 19, PM. In the past, these sorts of names were often avoidable by remapping the print queues to workstations using an alternative method, such as mapping them as network printers using their UNC name e.
In later versions of PaperCut NG and PaperCut MF, an automatic check for certain strings like Remote Downlevel Document was added, such that these errant document names derived from the operating system were ignored in favour of an attempt to read the genuine, original document name from within the spool file.
As of version The print-provider. All Comments. Collapse -. Delete and re-establish the printer queues. Back to Windows Forum. Start or search. Start New Discussion. Create a new discussion If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Track this discussion and email me when there are updates. One is the document itself, the other is a file called "Local Downlevel Document".
This file gets stuck in the queue. In order to get rid of it, I have to delete the printer and reinstall it. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Vijay A.
0コメント