Re: Product: 32 Bit HP BiDi Channel Components Installer -- Config
As for the general error...
I have seen this before and in my case(s) the cause was either corrupted
install of the driver or a driver\configuration mismatch. The solution was to
reinstall the offending driver on the server and move on.
Spicificly the HP BiDi is Hewlett Packards bidirectional communication
between the spooler and the physical printer and as I recall it is used in
verifying printer configuration each time a user attempts to access the
printer.
As for the TS portion...
I suspect why you are seeing it on your TS is that you do not have the same
driver installed on your TS server as on your TS clients and your RDP-Tcp
Properties allows the default "Windows Printer mapping" enabled. As a result
when your clients connect, the TS attempts to establish instances of the
clients print queue(s) sessions for them based on there local configuration
(including the driver).
Example:
When the client attempts to connect to the TS the TS will attempt to clone
ALL of the print queues on the client using the drivers installed on the TS
server (not the client). If the TS does not have a suitable driver it will
complain. If the driver is corrupt on the server it will complain.
This can result in driver mismatches and odd results. If you do not have a
need for your clients to print from within there TS session you should
disable the feature.
If you need the printing capability you should make sure your drivers match
EXACTLY down to the date and version or you can begin a session of chasing
your tail.
Check out Microsoft's white paper on "Windows Point and Print Technical
Overview" if you have not previously. A simple goggle search will bring it up.
Best of luck.
"node808" wrote:
> Not specific to TS???? Then why does it only occur only on my terminal
> servers? My other print servers function normally. Seems to be very
> specific to TS.
>
> "Priya Raghavan [MSFT]" wrote:
>
> > Hi,
> >
> > You might want to post this query in the printers newsgroup, as it is not
> > specific to TS.
> >
> > --
> > Thanks,
> > Priya.
> >
> > http://blogs.msdn.com/ts
> > --
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > "Michael" wrote in message
> > news:FD61309E-F3A4-4AA5-8168-C399BA407205@microsoft.com...
> > >I have the same issue on my Server 2003 Terminal Server cluster. Do I just
> > > need to install a different driver?
> > >
> > > Michael
> > >
> > > "Kaushal Mehta [MSFT]" wrote:
> > >
> > >> Hi Matt,
> > >>
> > >> I fail to understand if this question is related to terminal services.
> > >>
> > >> Could you please explain it a bit more?
> > >>
> > >> Thanks,
> > >> Kaushal Mehta.
> > >>
> > >> "Matt" wrote in message
> > >> news:FEEF95D9-7D72-45B3-B393-E84855E0A409@microsoft.com...
> > >> > Hi, Same problem here too with at least 3 different printers/drivers.
> > >> > Where
> > >> > is the "MS Universal PCL 5e" driver? When I go to install a "New
> > >> > Driver"
> > >> > I
> > >> > don’t see MS or Microsoft as a Manufacturer.
> > >> >
> > >> > Thanks
> > >> >
> > >> >
> > >> > "karsten" wrote:
> > >> >
> > >> >> Hi Mr555,
> > >> >>
> > >> >> i have the same problem,
> > >> >> it is a problem with the HP Driver PCL 6, take the MS universell PCL
> > >> >> 5e
> > >> >> Driver for HP and forget this problem
> > >> >>
> > >> >> bye
> > >> >>
> > >> >> Karsten
> > >>
> > >>
> >
> >