Ask a Question related to Windows Server, Design and Development.
-
Simon Begin #1
Unable to print to Win2003 shared printer from some apps
I've got some applications that are unable to print to the server since
last week. The errors are "not enough memory" or "Printer not ready".
Printing locally is OK, and redirecting LPT1 to the server's printer
works also(this is a plan B solution, I would rather solve the problem).
On the same machine, other applications works well.
This happens on ALL Win2000+ workstations, different applications
running FoxPro (old version I think) and Access 2.0.
We explored everything we changed from last week (SUS updates, some GPO)
without success.
Anyone has an idea how to find the cause?
Simon Begin Guest
-
Unable to print to Firey printer from Adobe Acrobat 8.0
I have a iMac Mac OS X (10.4.8) 2.33 GHz Intel Core 2 Duo 3GB Ram. I haven installed Adobe Creative Suite 2.3 with the new Adobe Acrobat 8.0. I... -
#26346 [NEW]: Cannot output to a shared printer
From: rich at dwell dot co dot uk Operating system: Windows 2003 PHP version: 4.3.4 PHP Bug Type: Network related Bug... -
Can't print from apps
Please reply to me as well as the list since I can't subscibe to high volume lists without my internet connection choking :) My lprng with a... -
cannot access shared files or printer on windows XP computer
Have Windows 2000 small business server and small (10 computer) LAN. I can share printers attached to Windows 98 computers, but cannot share printer... -
Unable to compile Qt / KDE apps
PM wrote: maybe this helps http://www.linux-community.de/Neues/story?storyid=4627 cu -
Simon Begin #2
Re: Unable to print to Win2003 shared printer from some apps
Solved my problem by restarting the Print Spooler service.
Seems that Win2003 needs rebooting once in a while.
Simon Begin a écrit :> I've got some applications that are unable to print to the server since
> last week. The errors are "not enough memory" or "Printer not ready".
> Printing locally is OK, and redirecting LPT1 to the server's printer
> works also(this is a plan B solution, I would rather solve the problem).
>
> On the same machine, other applications works well.
>
> This happens on ALL Win2000+ workstations, different applications
> running FoxPro (old version I think) and Access 2.0.
>
> We explored everything we changed from last week (SUS updates, some GPO)
> without success.
>
> Anyone has an idea how to find the cause?Simon Begin Guest



Reply With Quote

