Re: Printing Issue

Manfred and TCP,
I'm having the same problem with a SBS Server 2003. I have a network
connected HP2600n colour laser printer connected and hosted by the server.
Was working fine until around mid October. Print Jobs from regular users
hang in the print queue. If I restart the Print Spooler service they print.
If the print queue is empty, and I log on to a work station as a domain
administrator, I can print to the printer without problem.
I also had a problem with two LaserJet 1000 printers connected to laptop
workstation through the laptops USB port. If I shared these printers on the
network and listed them in the directory, they wouldn't print either. The
job would hang in the print queue, and the queue would indicate that the
printer was warming up, but go no further.
Since then we have added 4 network connect Samsung printers to the network.
They've been printing fine for all users until yesterday. Two of the printer
queues hung. I re-started the Print Spooler service and the jobs printed.
The Samsung's have been fine since then, but still not able to print to the
HP 2600n. (The LaserJet 1000s have been removed from the network).
Sorry for the long post, but wanted to give you all the info I could.

Bob

"Manfred Zhuang [MSFT]" wrote:

Hello Customer,

Would you please send me the MPS report for further research?

In addition, if it is convenient, please connect another printer to the
network and check if the issue persists.

Thank you for your understanding and cooperation.

Best regards,

Manfred Zhuang(MSFT)
Microsoft Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Printing Issue
| thread-index: Acg2e5nsgUVSLvpFRQC4saW/PTwP0w==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?dGNw?= <tcp@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <82A99033-12AF-48F1-9D9E-F3CBCC30D5DC@xxxxxxxxxxxxx>
<379AC263-6223-4607-97E6-649FD46FFBE8@xxxxxxxxxxxxx>
<3A23ECFF-2BD9-45F7-A857-15536C8F313E@xxxxxxxxxxxxx>
<4E7495A6-15C1-499A-BA66-3DA1A379511D@xxxxxxxxxxxxx>
<As70#KfIIHA.540@xxxxxxxxxxxxxxxxxxxxxx>
<B1280B4F-EBDA-4FFB-AD68-CE8745DF75AB@xxxxxxxxxxxxx>
<7qNyILlNIHA.6908@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: Re: Printing Issue
| Date: Tue, 4 Dec 2007 05:43:07 -0800
| Lines: 304
| Message-ID: <C2D77A01-89A3-487A-A738-EF598C5FF92F@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:79924
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Yes.
|
| "Manfred Zhuang [MSFT]" wrote:
|
| > Hello Customer,
| >
| > Thank you for your reply.
| >
| > I understand that the issue persists.
| >
| > I would like to confirm that does the issue happen for all the users?
Does
| > the issue happen for all the client workstations?
| >
| > If you connect the printer to another computer, does the issue persist?
| >
| > I look forward to hearing from you.
| >
| > Best regards,
| >
| > Manfred Zhuang(MSFT)
| > Microsoft Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| > --------------------
| > | Thread-Topic: Printing Issue
| > | thread-index: Acg0befUwyb4qzZlSNuQPvvXho9wVg==
| > | X-WBNR-Posting-Host: 207.46.193.207
| > | From: =?Utf-8?B?dGNw?= <tcp@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | References: <82A99033-12AF-48F1-9D9E-F3CBCC30D5DC@xxxxxxxxxxxxx>
| > <379AC263-6223-4607-97E6-649FD46FFBE8@xxxxxxxxxxxxx>
| > <3A23ECFF-2BD9-45F7-A857-15536C8F313E@xxxxxxxxxxxxx>
| > <4E7495A6-15C1-499A-BA66-3DA1A379511D@xxxxxxxxxxxxx>
| > <As70#KfIIHA.540@xxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: Re: Printing Issue
| > | Date: Sat, 1 Dec 2007 15:00:02 -0800
| > | Lines: 286
| > | Message-ID: <B1280B4F-EBDA-4FFB-AD68-CE8745DF75AB@xxxxxxxxxxxxx>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:79407
| > | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Does anyone have any new information on this? The issue is still
| > outstanding
| > | for me and is very perplexing. Any help would be greatly appreciated.
| > |
| > | In response to MSFT's post, I tried all the provided suggestions to
no
| > | avail. Printer logs do not show much.
| > |
| > | Thanks!
| > |
| > | "Manfred Zhuang [MSFT]" wrote:
| > |
| > | > Hello Customer,
| > | >
| > | > Thank you for posting here and also thanks to Dave for input.
| > | >
| > | > From your post, I understand that the print job always hangs in
queue.
| > | >
| > | > If the issue is urgent to your business, it is recommended that you
| > contact
| > | > Microsoft Customer Support Services (CSS) via telephone so that a
| > dedicated
| > | > Support Professional can assist you recover the server in a more
| > efficient
| > | > manner. Please be advised that contacting phone support will be a
| > charged
| > | > call.
| > | >
| > | > For a complete list of Microsoft Customer Support Services phone
| > numbers
| > | > and information about support costs, visit the following Microsoft
Web
| > | > site:
| > | > http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
| > | >
| > | > For this problem, I suggest you may also try following steps:
| > | >
| > | > Suggestion 1: Clear Printer Spooler files and enable the spooler
service
| > | > ===================
| > | > Note: I assume that the system is installed on local disk (C:).
| > | >
| > | > 1. Click Start, click Run, type "Services.msc" (without the
quotation
| > | > marks) in the open box and click OK.
| > | > 2. Double-click "Printer Spooler" in the Services list.
| > | > 3. Click on Stop and click OK.
| > | > 4. Click Start, click Run, type "%WINDIR%\system32\spool\printers",
in
| > the
| > | > open window, please delete all files in this folder.
| > | > 5. Click Start, click Run, type "Services.msc" (without the
quotation
| > | > marks) in the open box and click OK.
| > | > 6. Double-click "Printer Spooler" in the Services list.
| > | > 7. Click on Start. In the Startup Type list, make sure that
"Automatic"
| > is
| > | > selected and Click OK.
| > | >
| > | > Suggestion 2: Turn Printer Event Logging
| > | > =========================
| > | > 1. Click Start, point to Settings, and then click Printers.
| > | > 2. On the File menu, click Server Properties, and then click the
| > Advanced
| > | > tab.
| > | > 3. To turn on spooler error event logging to the system log file,
click
| > to
| > | > select or clear the "Log spooler error events" check box.
| > | > 4. To turn on spooler warning event logging to the system log file,
| > click
| > | > to select or clear the "Log spooler warning events" check box.
| > | > 5. To turn on spooler information event logging to the system log
file,
| > | > click to select or clear the "Log spooler information events" check
box.
| > | > 6. Either restart the spooler service or restart the server.
| > | > 7. Check if there are any error logged in event log.
| > | >
| > | > Suggestion 3: Check local printer port/monitor
| > | > ============================
| > | > 1. Start Registry Editor.
| > | > 2. Locate the Local Port value under the following key in the
registry:
| > | >
| >
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\LocalPort
| > | > 3. Double-click the Driver subkey, and then edit the value. Change
the
| > | > string value to "Localspl.dll" (without the quotation marks), and
then
| > | > click OK.
| > | > 4. Check the following registry key for third-party monitors.
Remove
| > any
| > | > non-default monitors:
| > | > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
| > | >
| > | > The default port monitors are:
| > | > AppleTalk Printing Devices (When Services for Macintosh is
installed)
| > | > BJ Language Monitor
| > | > Local Port
| > | > PJL Language Monitor
| > | > Standard TCP/IP Port
| > | > USB Monitor
| > | > Microsoft Shared Fax Monitor
| > | > LPR Port
| > | >
| > | > 5. Check the following registry key for third-party print
providers.
| > Remove
| > | > any non-default print providers:
| > | > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers
| > | >
| > | > The default print providers are:
| > | > Internet Print Provider
| > | > LanMan Print Services
| > | >
| > | > 6. Check the following registry key for third-party print
processors.
| > | > Remove any non-default print providers:
| > | >
| >
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windo
| > | > ws NT x86\Print Processors
| > | > The default print processor is:
| > | > WinPrint
| > | >
| > | > 7. Change the third-party print processor to WinPrint.
| > | > 8. Click Start, point to Settings, and then click Control Panel.
| > | > 9. Double-click Printers and Faxes, right-click the printer, and
then
| > click
| > | > Properties.
| > | > 10. On the Advanced tab, click Print Processor.
| > | > 11. In the Print Processor box, click WinPrint.
| > | > 12. Click OK two times.
| > | > 13. Quit Registry Editor.
.

Relevant Pages

  • RE: LDAP & Find People not working
    ... > Microsoft CSS Online Newsgroup Support ... > This newsgroup only focuses on SBS technical issues. ... > | Yes, the scanner is on the local area network, so as you indicated below, ... > | So I wonder why the scanner does not see the LDAP server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Cannot Connect via remote desktop
    ... You can establish the RDP connection and it is stops work soon. ... work stably for your network. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: Cannot Connect via remote desktop
    ... You can establish the RDP connection and it is stops work soon. ... work stably for your network. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: "Delayed Write Failed" error message when you write a file to
    ... Check the network. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... message when you write a large file to a server. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2003 Premium and ISA2004 SP3 FTP and POP3 problems
    ... Based on my research on the error code, I think this is a know network ... Can you access external FTP on SBS? ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)