[THIN] Re: printes going offline

  • From: Jason CitrixADmin <jasoncitrix@xxxxxxxxx>
  • To: thin <thin@xxxxxxxxxxxxx>
  • Date: Mon, 1 Dec 2014 08:21:03 -0500

I have tried to make sure that "advanced features" are turned off,
bi-directional support is not always available and there are no entries in
the event log for printing.
There is no need for server reboot, as they can log off, log back in and
print for awhile again.

On Wed, Nov 26, 2014 at 10:01 AM, Jason CitrixADmin <jasoncitrix@xxxxxxxxx>

> I will check on that
> On Wed, Nov 26, 2014 at 9:44 AM, Jan <tinybeetle@xxxxxxxxx> wrote:
>> Check for print errors in the event log. At least that's what I run into.
>> I don't know how to fix them (other than a server reboot).
>> They usually contain the following:
>> Event Type: Error
>> Event Source: Print
>> Event Category: None
>> Event ID: 6161
>> "Win32 error code returned by the print processor: 6. The handle is
>> invalid."
>> Your situation may be different since you're on x64 and my servers are
>> still x32.
>> One thing that I've found that helps with some of my problematic users is
>> to change the printer settings on their desktop, unchecking "Enable
>> Advanced Printing Features" and ensuring that "Enable Bidirectional
>> Support" is also unchecked.
>> On Wed, Nov 26, 2014 at 9:27 AM, Jason CitrixADmin <jasoncitrix@xxxxxxxxx
>> > wrote:
>>> I have a user that at apparently random times has her printers go
>>> Offline (as seen on the server).  Usually this occurs after multiple print
>>> jobs but not every time.  She is using a Canon Printer and an HP LaserJet
>>> printer.  Both of which are currently mapped to HP laserJet 4 drivers.
>>> However she has the same issue if we use the Citrix universal driver.
>>> Th printer remains Online on her local PC, but it on the app server that
>>> the printer shows as offline and the jobs queue up in the spool.
>>> I am at a loss as to the cause at the moment.
>>> I think my next step is to see if we can set her up to log into a single
>>> server that we can troubleshoot on if there are any changes to the server
>>> that need to be made.
>>> We have W2k3 x64 and a mixture of XenApp 5.6 and 6.2  servers

Other related posts: