Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Windows Server Help
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



Print jobs hanging, queues not clearing

Windows Server Help


Reply
 
Thread Tools Search this Thread
  #1  
Old 06-08-2008
MN
 
Posts: n/a
Print jobs hanging, queues not clearing

Periodically (every 2 days) print jobs hang and will not clear. Both nodes
of the cluster (2003 Enterprise) have to be rebooted and then printing
resumes successfully. Seeing 6161 errors in the System event log that may
or may not be related to this.



Reply With Quote
  #2  
Old 06-08-2008
Alan Morris [MSFT]
 
Posts: n/a
Re: Print jobs hanging, queues not clearing

what is the error code returned from the 6161 error? There are a couple of
transport failures that get caught here

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"MN" <mn0001@nycap.rr.com> wrote in message
news:u$bhw4y9IHA.5700@TK2MSFTNGP02.phx.gbl...
> Periodically (every 2 days) print jobs hang and will not clear. Both
> nodes of the cluster (2003 Enterprise) have to be rebooted and then
> printing resumes successfully. Seeing 6161 errors in the System event log
> that may or may not be related to this.
>



Reply With Quote
  #3  
Old 06-08-2008
MN
 
Posts: n/a
Re: Print jobs hanging, queues not clearing

I've seen random codes, for example:

Error Code returned by the print processor: 2. The system cannot find the
file specified.
Error Code returned by the print processor: 259. No more data is available.
Error Code returned by the print processor: 1241. The network address could
not be used for the operation requested.
Error Code returned by the print processor: 2250. This network connection
does not exist.
Error Code returned by the print processor: 0. The operation completed
successfully. (this one is somewhat baffling).

I am not certain there is a definite correlation between the 6161s and the
jobs getting stuck in the queue, but it seems as though every time the queue
problem surfaces, there are some 6161's in the event log, but not for every
print job, very intermittent.

"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:eR$nBs39IHA.2324@TK2MSFTNGP06.phx.gbl...
> what is the error code returned from the 6161 error? There are a couple
> of transport failures that get caught here
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "MN" <mn0001@nycap.rr.com> wrote in message
> news:u$bhw4y9IHA.5700@TK2MSFTNGP02.phx.gbl...
>> Periodically (every 2 days) print jobs hang and will not clear. Both
>> nodes of the cluster (2003 Enterprise) have to be rebooted and then
>> printing resumes successfully. Seeing 6161 errors in the System event
>> log that may or may not be related to this.
>>

>
>



Reply With Quote
  #4  
Old 06-08-2008
Alan Morris [MSFT]
 
Posts: n/a
Re: Print jobs hanging, queues not clearing

these two are when the device is not reachable on the current transport

> Error Code returned by the print processor: 1241. The network address
> could not be used for the operation requested.
> Error Code returned by the print processor: 2250. This network connection
> does not exist.




error 2 (file not found)

259 The application stopped sending data, the job usually prints after the
timeout

0 Usually indicates a rendering failure and GDI (the process that the
spooler calls to transform data to page) reset the failure ID to 0.

GDI rendering can fail due to resource failures. If there is a GDI handles
leak, the spooler will post a 6162 error when the GDI handle count
approaches the limit (default is 10000). For most other GDI failures the
return code is 0 and it's hard to track them down. The jobs are typically
deleted since GDI signals that it's done with them.


Since the jobs just hang there, is there any other 3rd party print monitor
software on the server. HP has something called HP Master Monitor.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"MN" <mn0001@nycap.rr.com> wrote in message
news:ev8WnQ89IHA.3884@TK2MSFTNGP05.phx.gbl...
> I've seen random codes, for example:
>
> Error Code returned by the print processor: 2. The system cannot find the
> file specified.
> Error Code returned by the print processor: 259. No more data is
> available.
> Error Code returned by the print processor: 1241. The network address
> could not be used for the operation requested.
> Error Code returned by the print processor: 2250. This network connection
> does not exist.
> Error Code returned by the print processor: 0. The operation completed
> successfully. (this one is somewhat baffling).
>
> I am not certain there is a definite correlation between the 6161s and the
> jobs getting stuck in the queue, but it seems as though every time the
> queue problem surfaces, there are some 6161's in the event log, but not
> for every print job, very intermittent.
>
> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
> news:eR$nBs39IHA.2324@TK2MSFTNGP06.phx.gbl...
>> what is the error code returned from the 6161 error? There are a couple
>> of transport failures that get caught here
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "MN" <mn0001@nycap.rr.com> wrote in message
>> news:u$bhw4y9IHA.5700@TK2MSFTNGP02.phx.gbl...
>>> Periodically (every 2 days) print jobs hang and will not clear. Both
>>> nodes of the cluster (2003 Enterprise) have to be rebooted and then
>>> printing resumes successfully. Seeing 6161 errors in the System event
>>> log that may or may not be related to this.
>>>

>>
>>

>
>



Reply With Quote
  #5  
Old 07-08-2008
MN
 
Posts: n/a
Re: Print jobs hanging, queues not clearing

No, there are no third-party monitors installed on either node of the
cluster. I neglected to mention earlier this was a clustered print server.

"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:eZ2vsi%239IHA.1204@TK2MSFTNGP04.phx.gbl...
> these two are when the device is not reachable on the current transport
>
>> Error Code returned by the print processor: 1241. The network address
>> could not be used for the operation requested.
>> Error Code returned by the print processor: 2250. This network
>> connection does not exist.

>
>
>
> error 2 (file not found)
>
> 259 The application stopped sending data, the job usually prints after
> the timeout
>
> 0 Usually indicates a rendering failure and GDI (the process that the
> spooler calls to transform data to page) reset the failure ID to 0.
>
> GDI rendering can fail due to resource failures. If there is a GDI
> handles leak, the spooler will post a 6162 error when the GDI handle count
> approaches the limit (default is 10000). For most other GDI failures the
> return code is 0 and it's hard to track them down. The jobs are
> typically deleted since GDI signals that it's done with them.
>
>
> Since the jobs just hang there, is there any other 3rd party print monitor
> software on the server. HP has something called HP Master Monitor.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "MN" <mn0001@nycap.rr.com> wrote in message
> news:ev8WnQ89IHA.3884@TK2MSFTNGP05.phx.gbl...
>> I've seen random codes, for example:
>>
>> Error Code returned by the print processor: 2. The system cannot find
>> the file specified.
>> Error Code returned by the print processor: 259. No more data is
>> available.
>> Error Code returned by the print processor: 1241. The network address
>> could not be used for the operation requested.
>> Error Code returned by the print processor: 2250. This network
>> connection does not exist.
>> Error Code returned by the print processor: 0. The operation completed
>> successfully. (this one is somewhat baffling).
>>
>> I am not certain there is a definite correlation between the 6161s and
>> the jobs getting stuck in the queue, but it seems as though every time
>> the queue problem surfaces, there are some 6161's in the event log, but
>> not for every print job, very intermittent.
>>
>> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
>> news:eR$nBs39IHA.2324@TK2MSFTNGP06.phx.gbl...
>>> what is the error code returned from the 6161 error? There are a couple
>>> of transport failures that get caught here
>>>
>>> --
>>> Alan Morris
>>> Windows Printing Team
>>> Search the Microsoft Knowledge Base here:
>>> http://support.microsoft.com/search/?adv=1
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> "MN" <mn0001@nycap.rr.com> wrote in message
>>> news:u$bhw4y9IHA.5700@TK2MSFTNGP02.phx.gbl...
>>>> Periodically (every 2 days) print jobs hang and will not clear. Both
>>>> nodes of the cluster (2003 Enterprise) have to be rebooted and then
>>>> printing resumes successfully. Seeing 6161 errors in the System event
>>>> log that may or may not be related to this.
>>>>
>>>
>>>

>>
>>

>
>



Reply With Quote
  #6  
Old 07-08-2008
Alan Morris [MSFT]
 
Posts: n/a
Re: Print jobs hanging, queues not clearing

You mentioned cluster previously

the support group normally has one remove all the third party print language
and port monitor software. What monitors are listed under the node
registry as well as the cluster registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors

HKEY_LOCAL_MACHINE\Cluster\Resources\CLUSTERGUID\Parameters\Monitors



How to troubleshoot printing problems in Windows 2000 and in Windows Server
2003
http://support.microsoft.com/kb/260142/en-us



The Print Spooler service may stop frequently and you may receive a Dr.
Watson error message when you try to access the printer on a Windows
2000-based print server
http://support.microsoft.com/kb/888206/en-us
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"MN" <mn0001@nycap.rr.com> wrote in message
news:OVP%234f$9IHA.1428@TK2MSFTNGP06.phx.gbl...
> No, there are no third-party monitors installed on either node of the
> cluster. I neglected to mention earlier this was a clustered print
> server.
>
> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
> news:eZ2vsi%239IHA.1204@TK2MSFTNGP04.phx.gbl...
>> these two are when the device is not reachable on the current transport
>>
>>> Error Code returned by the print processor: 1241. The network address
>>> could not be used for the operation requested.
>>> Error Code returned by the print processor: 2250. This network
>>> connection does not exist.

>>
>>
>>
>> error 2 (file not found)
>>
>> 259 The application stopped sending data, the job usually prints after
>> the timeout
>>
>> 0 Usually indicates a rendering failure and GDI (the process that the
>> spooler calls to transform data to page) reset the failure ID to 0.
>>
>> GDI rendering can fail due to resource failures. If there is a GDI
>> handles leak, the spooler will post a 6162 error when the GDI handle
>> count approaches the limit (default is 10000). For most other GDI
>> failures the return code is 0 and it's hard to track them down. The
>> jobs are typically deleted since GDI signals that it's done with them.
>>
>>
>> Since the jobs just hang there, is there any other 3rd party print
>> monitor software on the server. HP has something called HP Master
>> Monitor.
>>
>>
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "MN" <mn0001@nycap.rr.com> wrote in message
>> news:ev8WnQ89IHA.3884@TK2MSFTNGP05.phx.gbl...
>>> I've seen random codes, for example:
>>>
>>> Error Code returned by the print processor: 2. The system cannot find
>>> the file specified.
>>> Error Code returned by the print processor: 259. No more data is
>>> available.
>>> Error Code returned by the print processor: 1241. The network address
>>> could not be used for the operation requested.
>>> Error Code returned by the print processor: 2250. This network
>>> connection does not exist.
>>> Error Code returned by the print processor: 0. The operation completed
>>> successfully. (this one is somewhat baffling).
>>>
>>> I am not certain there is a definite correlation between the 6161s and
>>> the jobs getting stuck in the queue, but it seems as though every time
>>> the queue problem surfaces, there are some 6161's in the event log, but
>>> not for every print job, very intermittent.
>>>
>>> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
>>> news:eR$nBs39IHA.2324@TK2MSFTNGP06.phx.gbl...
>>>> what is the error code returned from the 6161 error? There are a
>>>> couple of transport failures that get caught here
>>>>
>>>> --
>>>> Alan Morris
>>>> Windows Printing Team
>>>> Search the Microsoft Knowledge Base here:
>>>> http://support.microsoft.com/search/?adv=1
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>> "MN" <mn0001@nycap.rr.com> wrote in message
>>>> news:u$bhw4y9IHA.5700@TK2MSFTNGP02.phx.gbl...
>>>>> Periodically (every 2 days) print jobs hang and will not clear. Both
>>>>> nodes of the cluster (2003 Enterprise) have to be rebooted and then
>>>>> printing resumes successfully. Seeing 6161 errors in the System event
>>>>> log that may or may not be related to this.
>>>>>
>>>>
>>>>
>>>
>>>

>>
>>

>
>



Reply With Quote
  #7  
Old 11-08-2008
MN
 
Posts: n/a
Re: Print jobs hanging, queues not clearing

Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors:

Node 1:
BJ Language Monitor
Local Port
MPD Port 2.0 (not on node 2)
PJL Language Monitor
Standard TCP/IP Port
USB Monitor

Node 2:
BJ Language Monitor
Local Port
PJL Language Monitor
Standard TCP/IP Port
USB Monitor

Under HKEY_LOCAL_MACHINE\Cluster\Resources\CLUSTERGUID\Parameters\Monitors I
am not sure how to determine the cluster GUID. I see GUIDs listed under the
Cluster key (ClusterInstanceID and ClusterNameResource) but don't see those
GUIDs listed under the HKEY_LOCAL_MACHINE\Cluster\Resources keys.

"Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
news:%23KlK0qL%23IHA.1016@TK2MSFTNGP03.phx.gbl...
> You mentioned cluster previously
>
> the support group normally has one remove all the third party print
> language and port monitor software. What monitors are listed under the
> node registry as well as the cluster registry
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
>
> HKEY_LOCAL_MACHINE\Cluster\Resources\CLUSTERGUID\Parameters\Monitors
>
>
>
> How to troubleshoot printing problems in Windows 2000 and in Windows
> Server 2003
> http://support.microsoft.com/kb/260142/en-us
>
>
>
> The Print Spooler service may stop frequently and you may receive a Dr.
> Watson error message when you try to access the printer on a Windows
> 2000-based print server
> http://support.microsoft.com/kb/888206/en-us
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/search/?adv=1
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "MN" <mn0001@nycap.rr.com> wrote in message
> news:OVP%234f$9IHA.1428@TK2MSFTNGP06.phx.gbl...
>> No, there are no third-party monitors installed on either node of the
>> cluster. I neglected to mention earlier this was a clustered print
>> server.
>>
>> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
>> news:eZ2vsi%239IHA.1204@TK2MSFTNGP04.phx.gbl...
>>> these two are when the device is not reachable on the current transport
>>>
>>>> Error Code returned by the print processor: 1241. The network address
>>>> could not be used for the operation requested.
>>>> Error Code returned by the print processor: 2250. This network
>>>> connection does not exist.
>>>
>>>
>>>
>>> error 2 (file not found)
>>>
>>> 259 The application stopped sending data, the job usually prints after
>>> the timeout
>>>
>>> 0 Usually indicates a rendering failure and GDI (the process that the
>>> spooler calls to transform data to page) reset the failure ID to 0.
>>>
>>> GDI rendering can fail due to resource failures. If there is a GDI
>>> handles leak, the spooler will post a 6162 error when the GDI handle
>>> count approaches the limit (default is 10000). For most other GDI
>>> failures the return code is 0 and it's hard to track them down. The
>>> jobs are typically deleted since GDI signals that it's done with them.
>>>
>>>
>>> Since the jobs just hang there, is there any other 3rd party print
>>> monitor software on the server. HP has something called HP Master
>>> Monitor.
>>>
>>>
>>>
>>> --
>>> Alan Morris
>>> Windows Printing Team
>>> Search the Microsoft Knowledge Base here:
>>> http://support.microsoft.com/search/?adv=1
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> "MN" <mn0001@nycap.rr.com> wrote in message
>>> news:ev8WnQ89IHA.3884@TK2MSFTNGP05.phx.gbl...
>>>> I've seen random codes, for example:
>>>>
>>>> Error Code returned by the print processor: 2. The system cannot find
>>>> the file specified.
>>>> Error Code returned by the print processor: 259. No more data is
>>>> available.
>>>> Error Code returned by the print processor: 1241. The network address
>>>> could not be used for the operation requested.
>>>> Error Code returned by the print processor: 2250. This network
>>>> connection does not exist.
>>>> Error Code returned by the print processor: 0. The operation completed
>>>> successfully. (this one is somewhat baffling).
>>>>
>>>> I am not certain there is a definite correlation between the 6161s and
>>>> the jobs getting stuck in the queue, but it seems as though every time
>>>> the queue problem surfaces, there are some 6161's in the event log, but
>>>> not for every print job, very intermittent.
>>>>
>>>> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
>>>> news:eR$nBs39IHA.2324@TK2MSFTNGP06.phx.gbl...
>>>>> what is the error code returned from the 6161 error? There are a
>>>>> couple of transport failures that get caught here
>>>>>
>>>>> --
>>>>> Alan Morris
>>>>> Windows Printing Team
>>>>> Search the Microsoft Knowledge Base here:
>>>>> http://support.microsoft.com/search/?adv=1
>>>>>
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>>
>>>>> "MN" <mn0001@nycap.rr.com> wrote in message
>>>>> news:u$bhw4y9IHA.5700@TK2MSFTNGP02.phx.gbl...
>>>>>> Periodically (every 2 days) print jobs hang and will not clear. Both
>>>>>> nodes of the cluster (2003 Enterprise) have to be rebooted and then
>>>>>> printing resumes successfully. Seeing 6161 errors in the System
>>>>>> event log that may or may not be related to this.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>

>>
>>

>
>



Reply With Quote
  #8  
Old 12-08-2008
Alan Morris [MSFT]
 
Posts: n/a
Re: Print jobs hanging, queues not clearing

the GUID for the spooler service is what ever it is. It's nothing the
spooler assigns.

I normally just start opening keys until I find the spooler. This number
does match the directory where the print drivers reside.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"MN" <mn0001@nycap.rr.com> wrote in message
news:%23Ojd5n6%23IHA.1016@TK2MSFTNGP03.phx.gbl...
> Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors:
>
> Node 1:
> BJ Language Monitor
> Local Port
> MPD Port 2.0 (not on node 2)
> PJL Language Monitor
> Standard TCP/IP Port
> USB Monitor
>
> Node 2:
> BJ Language Monitor
> Local Port
> PJL Language Monitor
> Standard TCP/IP Port
> USB Monitor
>
> Under HKEY_LOCAL_MACHINE\Cluster\Resources\CLUSTERGUID\Parameters\Monitors
> I am not sure how to determine the cluster GUID. I see GUIDs listed under
> the Cluster key (ClusterInstanceID and ClusterNameResource) but don't see
> those GUIDs listed under the HKEY_LOCAL_MACHINE\Cluster\Resources keys.
>
> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
> news:%23KlK0qL%23IHA.1016@TK2MSFTNGP03.phx.gbl...
>> You mentioned cluster previously
>>
>> the support group normally has one remove all the third party print
>> language and port monitor software. What monitors are listed under the
>> node registry as well as the cluster registry
>>
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
>>
>> HKEY_LOCAL_MACHINE\Cluster\Resources\CLUSTERGUID\Parameters\Monitors
>>
>>
>>
>> How to troubleshoot printing problems in Windows 2000 and in Windows
>> Server 2003
>> http://support.microsoft.com/kb/260142/en-us
>>
>>
>>
>> The Print Spooler service may stop frequently and you may receive a Dr.
>> Watson error message when you try to access the printer on a Windows
>> 2000-based print server
>> http://support.microsoft.com/kb/888206/en-us
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/search/?adv=1
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "MN" <mn0001@nycap.rr.com> wrote in message
>> news:OVP%234f$9IHA.1428@TK2MSFTNGP06.phx.gbl...
>>> No, there are no third-party monitors installed on either node of the
>>> cluster. I neglected to mention earlier this was a clustered print
>>> server.
>>>
>>> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
>>> news:eZ2vsi%239IHA.1204@TK2MSFTNGP04.phx.gbl...
>>>> these two are when the device is not reachable on the current transport
>>>>
>>>>> Error Code returned by the print processor: 1241. The network address
>>>>> could not be used for the operation requested.
>>>>> Error Code returned by the print processor: 2250. This network
>>>>> connection does not exist.
>>>>
>>>>
>>>>
>>>> error 2 (file not found)
>>>>
>>>> 259 The application stopped sending data, the job usually prints
>>>> after the timeout
>>>>
>>>> 0 Usually indicates a rendering failure and GDI (the process that the
>>>> spooler calls to transform data to page) reset the failure ID to 0.
>>>>
>>>> GDI rendering can fail due to resource failures. If there is a GDI
>>>> handles leak, the spooler will post a 6162 error when the GDI handle
>>>> count approaches the limit (default is 10000). For most other GDI
>>>> failures the return code is 0 and it's hard to track them down. The
>>>> jobs are typically deleted since GDI signals that it's done with them.
>>>>
>>>>
>>>> Since the jobs just hang there, is there any other 3rd party print
>>>> monitor software on the server. HP has something called HP Master
>>>> Monitor.
>>>>
>>>>
>>>>
>>>> --
>>>> Alan Morris
>>>> Windows Printing Team
>>>> Search the Microsoft Knowledge Base here:
>>>> http://support.microsoft.com/search/?adv=1
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>> "MN" <mn0001@nycap.rr.com> wrote in message
>>>> news:ev8WnQ89IHA.3884@TK2MSFTNGP05.phx.gbl...
>>>>> I've seen random codes, for example:
>>>>>
>>>>> Error Code returned by the print processor: 2. The system cannot find
>>>>> the file specified.
>>>>> Error Code returned by the print processor: 259. No more data is
>>>>> available.
>>>>> Error Code returned by the print processor: 1241. The network address
>>>>> could not be used for the operation requested.
>>>>> Error Code returned by the print processor: 2250. This network
>>>>> connection does not exist.
>>>>> Error Code returned by the print processor: 0. The operation
>>>>> completed successfully. (this one is somewhat baffling).
>>>>>
>>>>> I am not certain there is a definite correlation between the 6161s and
>>>>> the jobs getting stuck in the queue, but it seems as though every time
>>>>> the queue problem surfaces, there are some 6161's in the event log,
>>>>> but not for every print job, very intermittent.
>>>>>
>>>>> "Alan Morris [MSFT]" <alanmo@online.microsoft.com> wrote in message
>>>>> news:eR$nBs39IHA.2324@TK2MSFTNGP06.phx.gbl...
>>>>>> what is the error code returned from the 6161 error? There are a
>>>>>> couple of transport failures that get caught here
>>>>>>
>>>>>> --
>>>>>> Alan Morris
>>>>>> Windows Printing Team
>>>>>> Search the Microsoft Knowledge Base here:
>>>>>> http://support.microsoft.com/search/?adv=1
>>>>>>
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>>
>>>>>> "MN" <mn0001@nycap.rr.com> wrote in message
>>>>>> news:u$bhw4y9IHA.5700@TK2MSFTNGP02.phx.gbl...
>>>>>>> Periodically (every 2 days) print jobs hang and will not clear.
>>>>>>> Both nodes of the cluster (2003 Enterprise) have to be rebooted and
>>>>>>> then printing resumes successfully. Seeing 6161 errors in the
>>>>>>> System event log that may or may not be related to this.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>

>>
>>

>
>



Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Windows Server Help
Tags: , , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Print jobs hanging, queues not clearing"
Thread Thread Starter Forum Replies Last Post
print jobs go poof groovypucks Windows XP Support 4 18-01-2012 09:17 PM
Print jobs remain in the queue after printing Gus Windows Server Help 4 06-06-2011 10:42 PM
Detect and Repair Stalled print jobs without waiting BenTen Hardware Peripherals 4 17-08-2010 05:16 PM
Print jobs getting stuck in the queue Bottlenecked Hardware Peripherals 5 17-08-2010 12:25 PM
Move print queues to new server dbouton@fuse.net Windows Server Help 10 07-01-2009 09:43 PM


All times are GMT +5.5. The time now is 07:24 PM.