"Remote downlevel document" error when printing from DOS application running on XP Pro.
Hello,
I have a strange problem, which seems to be very hard to solve.
I have searched newsgroups and found several people with almost the same issue, but no solution.
The problem:
When printing from an DOS application (XAL 2.60 - Financial system), from some (this is important to note... this is not affecting all Win XP systems) Windows XP Pro systems, the printjob generates 3 "Remote downlevel document" print jobs.
The first 2 of them is garbage, which the printer wont print.
The user has to manually delete the first to documents before the "real" document is printed.
Here is a link with a screenshot of the Printer status window: http://www.eegholm.dk/it/remote.jpg
(sorry the gui language is Danish, but this should give some kind of understanding of the problem.)
My setup:
Mixed users of Win98SE, W2K and XP Pro
Printers in question are HP printers connected to a NT4 printserver (fully patched)
Symantec Antivirus Corporate edition (I have seen some references, that this might be related to the problem)
My question:
Why is these "Remote downlevel document"s created? And only from some machines?
How do I get rid of them?
Why does this only happen on WinXP machines?
Documentation I have read (And links to other peoples problems):
http://support.microsoft.com/?id=kb;en-us;Q312015
http://support.microsoft.com/default.aspx?scid=kb;en-us;q162447
https://www.experts-exchange.com/questions/20820430/remnants-of-spool-files-not-being-removed.html?query=remote+downlevel+document&searchType=all
http://groups.google.com/groups?dq=&start=625&hl=en&lr=&ie=UTF-8&oe=utf-8&group=comp.os.ms-windows&selm=7ad351d.0212261105.70633727%40posting.google.com
Any help appriciated.
Iam about to rollout Win XP on all our clients, and I want this problem fixed before I do the imaging.
I have a strange problem, which seems to be very hard to solve.
I have searched newsgroups and found several people with almost the same issue, but no solution.
The problem:
When printing from an DOS application (XAL 2.60 - Financial system), from some (this is important to note... this is not affecting all Win XP systems) Windows XP Pro systems, the printjob generates 3 "Remote downlevel document" print jobs.
The first 2 of them is garbage, which the printer wont print.
The user has to manually delete the first to documents before the "real" document is printed.
Here is a link with a screenshot of the Printer status window: http://www.eegholm.dk/it/remote.jpg
(sorry the gui language is Danish, but this should give some kind of understanding of the problem.)
My setup:
Mixed users of Win98SE, W2K and XP Pro
Printers in question are HP printers connected to a NT4 printserver (fully patched)
Symantec Antivirus Corporate edition (I have seen some references, that this might be related to the problem)
My question:
Why is these "Remote downlevel document"s created? And only from some machines?
How do I get rid of them?
Why does this only happen on WinXP machines?
Documentation I have read (And links to other peoples problems):
http://support.microsoft.com/?id=kb;en-us;Q312015
http://support.microsoft.com/default.aspx?scid=kb;en-us;q162447
https://www.experts-exchange.com/questions/20820430/remnants-of-spool-files-not-being-removed.html?query=remote+downlevel+document&searchType=all
http://groups.google.com/groups?dq=&start=625&hl=en&lr=&ie=UTF-8&oe=utf-8&group=comp.os.ms-windows&selm=7ad351d.0212261105.70633727%40posting.google.com
Any help appriciated.
Iam about to rollout Win XP on all our clients, and I want this problem fixed before I do the imaging.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Turns out testing this takes a bit longer than expected :)
We are running some remote sites that still needs to be updated, and I found 2 old Win95 computers hiding in the dark.
Ill get back with an update as soon as all pcs on the list is version 8.
We are running some remote sites that still needs to be updated, and I found 2 old Win95 computers hiding in the dark.
Ill get back with an update as soon as all pcs on the list is version 8.
ASKER
Ok... problem is solved now.
It turns out that it is not related to the version of Symantec Antivirus (If it was it must have been a combo of two things)
We had our provider/service partner for XAL make a fix to it, so that it prints to the IP address of the printserver instead of the name.
So basicly he made a conversion table in XAL, so when printing to a printer from a XP computer it prints to \\192.168.0.5\printname instead of \\servername\printname
I dont know why but this solved the problem.
It turns out that it is not related to the version of Symantec Antivirus (If it was it must have been a combo of two things)
We had our provider/service partner for XAL make a fix to it, so that it prints to the IP address of the printserver instead of the name.
So basicly he made a conversion table in XAL, so when printing to a printer from a XP computer it prints to \\192.168.0.5\printname instead of \\servername\printname
I dont know why but this solved the problem.
Great!
Thanks for providing the info, very good to know as I had contacted our support in Iceland who had no solutions for us.
Good luck,
Daniel F.
Thanks for providing the info, very good to know as I had contacted our support in Iceland who had no solutions for us.
Good luck,
Daniel F.
If the DOS application is printing to an lpt port and the dos application does not have the facility to print the print server's IP address how else can we do this. We have a similar problem using Pegasus Opera on a Windows 2003 Server/XP network. There are three Windows 98 machines on the lan/wan.
The logon scripts map the relevant lpt ports being for example net use lpt2: \\server\epsonLQ870
Any ideas as to how we can apply the theory said in the previous comments to our problem..?
The logon scripts map the relevant lpt ports being for example net use lpt2: \\server\epsonLQ870
Any ideas as to how we can apply the theory said in the previous comments to our problem..?
ASKER
Have you tried to map the printer like this:
"\\ip-of-server\epsonLQ870
Maybe that will work?
"\\ip-of-server\epsonLQ870
Maybe that will work?
ASKER
I have currently about 50 Win98 machines and 10 XP/2000.
Its strange that this only happens on some XP machines and that from those only to some printers.
I was hoping I could roll-out the 8.x version of Norton along with the XP machines, but I guess Ill have to try updating all Win98 machines before rolling out XP, just to be sure the issue is gone.
Thanks for your input, Ill make sure to award the points if this makes it work. :)