session printers

[Guest yair]

Hi,

 

I've recently managed to finally update my 2K3 server from SP1 to SP2. Ever

since, the server, which functions as a terminal server doesn't allow users

to print to a mapped printer, and registers an error (event ID 6161 - Win32

error code returned by the print processor: 3. The system cannot find the

path specified). The server prints to all other printers, both local and

remote (as long as they are not in a specific session)

 

Naturally, I went through all possible posts but none seem to address this

specific problem. Tried cleanspl.exe and all other remedies including

checking the registry, backing up the other server's spooler and restoring it

to this one, and so on.

 

To complicate matters even further, this server has a duplicate server (with

SP2) and the clients can log on and print without any problelem.

 

Any ideas?

 

Thanks in advance,

 

Yair Millenbach

[Guest Piet van Dongen]

Re: session printers

 

Hi Yair,

 

Do you have installed the right printer driver on the terminal server that

doesn't remap the printers?

 

 

Regards,

 

Piet van Dongen

 

_____________________________

MCSA/MCSE Windows 2000/2003

MCTS Windows Server 2008

MCDBA SQL Server 2000

 

CCEA XP/3.0/4.0

CCA XenServer

CCSP

 

RES PowerFuse Certified Professional

RES Wisdom Certified Professional

 

 

 

"yair" <yair@discussions.microsoft.com> schreef in bericht

news:A54C9B3A-BEDE-4E2B-A517-D47A61615D7C@microsoft.com...

> Hi,

>

> I've recently managed to finally update my 2K3 server from SP1 to SP2.

> Ever

> since, the server, which functions as a terminal server doesn't allow

> users

> to print to a mapped printer, and registers an error (event ID 6161 -

> Win32

> error code returned by the print processor: 3. The system cannot find the

> path specified). The server prints to all other printers, both local and

> remote (as long as they are not in a specific session)

>

> Naturally, I went through all possible posts but none seem to address this

> specific problem. Tried cleanspl.exe and all other remedies including

> checking the registry, backing up the other server's spooler and restoring

> it

> to this one, and so on.

>

> To complicate matters even further, this server has a duplicate server

> (with

> SP2) and the clients can log on and print without any problelem.

>

> Any ideas?

>

> Thanks in advance,

>

> Yair Millenbach

[Guest yair]

Re: session printers

 

Hi Piet,

 

Yes. I used the HP Laserjet 4 Plus driver (from the MS list).

I also installed the local Kyocera driver (OEM) for a kyocera printer, which

can't use the same HP driver.

 

Any thoughts?

 

Thanks,

 

Yair

 

"Piet van Dongen" wrote:

> Hi Yair,

>

> Do you have installed the right printer driver on the terminal server that

> doesn't remap the printers?

>

>

> Regards,

>

> Piet van Dongen

>

> _____________________________

> MCSA/MCSE Windows 2000/2003

> MCTS Windows Server 2008

> MCDBA SQL Server 2000

>

> CCEA XP/3.0/4.0

> CCA XenServer

> CCSP

>

> RES PowerFuse Certified Professional

> RES Wisdom Certified Professional

>

>

>

> "yair" <yair@discussions.microsoft.com> schreef in bericht

> news:A54C9B3A-BEDE-4E2B-A517-D47A61615D7C@microsoft.com...

> > Hi,

> >

> > I've recently managed to finally update my 2K3 server from SP1 to SP2.

> > Ever

> > since, the server, which functions as a terminal server doesn't allow

> > users

> > to print to a mapped printer, and registers an error (event ID 6161 -

> > Win32

> > error code returned by the print processor: 3. The system cannot find the

> > path specified). The server prints to all other printers, both local and

> > remote (as long as they are not in a specific session)

> >

> > Naturally, I went through all possible posts but none seem to address this

> > specific problem. Tried cleanspl.exe and all other remedies including

> > checking the registry, backing up the other server's spooler and restoring

> > it

> > to this one, and so on.

> >

> > To complicate matters even further, this server has a duplicate server

> > (with

> > SP2) and the clients can log on and print without any problelem.

> >

> > Any ideas?

> >

> > Thanks in advance,

> >

> > Yair Millenbach

>

[Guest Piet van Dongen]

Re: session printers

 

Hi Yiar,

 

Are borh the server at the exact same patchlevel?

First try the delete the printer drivers and reinstall them.

Kyocera has an print driver delete tool (google this)

 

If this will not work try you got to find out if a file is missing.

Try to print from the working TS server en use Filemon from SysInternals (=

now M$)

Then try to print from the bad behaving TS server.

 

Compare this two text files with an text compare tool like google docs and

you find the missing file...

 

With future service pack installs, backup your server with an image tool

(ghost, acronis) so you always can do a rollback.

 

Regards,

 

Piet van Dongen

 

_____________________________

MCSA/MCSE Windows 2000/2003

MCTS Windows Server 2008

MCDBA SQL Server 2000

_____________________________

CCEA XP/3.0/4.0

CCA XenServer

CCSP

_____________________________

RES PowerFuse Certified Professional

RES Wisdom Certified Professional

 

 

 

"yair" <yair@discussions.microsoft.com> schreef in bericht

news:587D828E-C576-401F-A913-985E0F3E5C66@microsoft.com...

> Hi Piet,

>

> Yes. I used the HP Laserjet 4 Plus driver (from the MS list).

> I also installed the local Kyocera driver (OEM) for a kyocera printer,

> which

> can't use the same HP driver.

>

> Any thoughts?

>

> Thanks,

>

> Yair

>

> "Piet van Dongen" wrote:

>

>> Hi Yair,

>>

>> Do you have installed the right printer driver on the terminal server

>> that

>> doesn't remap the printers?

>>

>>

>> Regards,

>>

>> Piet van Dongen

>>

>> _____________________________

>> MCSA/MCSE Windows 2000/2003

>> MCTS Windows Server 2008

>> MCDBA SQL Server 2000

>>

>> CCEA XP/3.0/4.0

>> CCA XenServer

>> CCSP

>>

>> RES PowerFuse Certified Professional

>> RES Wisdom Certified Professional

>>

>>

>>

>> "yair" <yair@discussions.microsoft.com> schreef in bericht

>> news:A54C9B3A-BEDE-4E2B-A517-D47A61615D7C@microsoft.com...

>> > Hi,

>> >

>> > I've recently managed to finally update my 2K3 server from SP1 to SP2.

>> > Ever

>> > since, the server, which functions as a terminal server doesn't allow

>> > users

>> > to print to a mapped printer, and registers an error (event ID 6161 -

>> > Win32

>> > error code returned by the print processor: 3. The system cannot find

>> > the

>> > path specified). The server prints to all other printers, both local

>> > and

>> > remote (as long as they are not in a specific session)

>> >

>> > Naturally, I went through all possible posts but none seem to address

>> > this

>> > specific problem. Tried cleanspl.exe and all other remedies including

>> > checking the registry, backing up the other server's spooler and

>> > restoring

>> > it

>> > to this one, and so on.

>> >

>> > To complicate matters even further, this server has a duplicate server

>> > (with

>> > SP2) and the clients can log on and print without any problelem.

>> >

>> > Any ideas?

>> >

>> > Thanks in advance,

>> >

>> > Yair Millenbach

>>

[Guest yair]

Re: session printers

 

Hi Piet,

 

Both servers are at the exact patchlevel, to the latest update.

I alreay used both Kyocera's deleter.exe and MS's cleanspl.exe on the server

and reinstalled the files.

 

Tried both filemon and processmon and thought I found the problem -

shell32.dll in %systemroot%\system32 seemed to deny access -- but then I saw

that the second server acts exactly the same way. So no better insight here

I'm afraid.

 

I thought of creating an image of the second server and replicate it to the

first one, but there is software on the first one that can't be replaced so

I'm rather stuck here too.

 

Any other ideas?

 

Thanks in advance.

 

Yair Millenbach

 

"Piet van Dongen" wrote:

> Hi Yiar,

>

> Are borh the server at the exact same patchlevel?

> First try the delete the printer drivers and reinstall them.

> Kyocera has an print driver delete tool (google this)

>

> If this will not work try you got to find out if a file is missing.

> Try to print from the working TS server en use Filemon from SysInternals (=

> now M$)

> Then try to print from the bad behaving TS server.

>

> Compare this two text files with an text compare tool like google docs and

> you find the missing file...

>

> With future service pack installs, backup your server with an image tool

> (ghost, acronis) so you always can do a rollback.

>

> Regards,

>

> Piet van Dongen

>

> _____________________________

> MCSA/MCSE Windows 2000/2003

> MCTS Windows Server 2008

> MCDBA SQL Server 2000

> _____________________________

> CCEA XP/3.0/4.0

> CCA XenServer

> CCSP

> _____________________________

> RES PowerFuse Certified Professional

> RES Wisdom Certified Professional

>

>

>

> "yair" <yair@discussions.microsoft.com> schreef in bericht

> news:587D828E-C576-401F-A913-985E0F3E5C66@microsoft.com...

> > Hi Piet,

> >

> > Yes. I used the HP Laserjet 4 Plus driver (from the MS list).

> > I also installed the local Kyocera driver (OEM) for a kyocera printer,

> > which

> > can't use the same HP driver.

> >

> > Any thoughts?

> >

> > Thanks,

> >

> > Yair

> >

> > "Piet van Dongen" wrote:

> >

> >> Hi Yair,

> >>

> >> Do you have installed the right printer driver on the terminal server

> >> that

> >> doesn't remap the printers?

> >>

> >>

> >> Regards,

> >>

> >> Piet van Dongen

> >>

> >> _____________________________

> >> MCSA/MCSE Windows 2000/2003

> >> MCTS Windows Server 2008

> >> MCDBA SQL Server 2000

> >>

> >> CCEA XP/3.0/4.0

> >> CCA XenServer

> >> CCSP

> >>

> >> RES PowerFuse Certified Professional

> >> RES Wisdom Certified Professional

> >>

> >>

> >>

> >> "yair" <yair@discussions.microsoft.com> schreef in bericht

> >> news:A54C9B3A-BEDE-4E2B-A517-D47A61615D7C@microsoft.com...

> >> > Hi,

> >> >

> >> > I've recently managed to finally update my 2K3 server from SP1 to SP2.

> >> > Ever

> >> > since, the server, which functions as a terminal server doesn't allow

> >> > users

> >> > to print to a mapped printer, and registers an error (event ID 6161 -

> >> > Win32

> >> > error code returned by the print processor: 3. The system cannot find

> >> > the

> >> > path specified). The server prints to all other printers, both local

> >> > and

> >> > remote (as long as they are not in a specific session)

> >> >

> >> > Naturally, I went through all possible posts but none seem to address

> >> > this

> >> > specific problem. Tried cleanspl.exe and all other remedies including

> >> > checking the registry, backing up the other server's spooler and

> >> > restoring

> >> > it

> >> > to this one, and so on.

> >> >

> >> > To complicate matters even further, this server has a duplicate server

> >> > (with

> >> > SP2) and the clients can log on and print without any problelem.

> >> >

> >> > Any ideas?

> >> >

> >> > Thanks in advance,

> >> >

> >> > Yair Millenbach

> >>

>

[Guest Piet van Dongen]

Re: session printers

 

Can you check the permissions on the spool dir?

 

Else:

 

- stop printer spooler service

- delete content op c:\windows\system32\spool

- delete the key hklm\system\ccs\control\printers\drivers

- reinstall the driver

 

 

Or

 

Are you using a virusscanner that is interfering with creating the printers?

There's an issue with mcafee and citrix...

 

 

Regards,

 

Piet van Dongen

 

_____________________________

MCSA/MCSE Windows 2000/2003

MCTS Windows Server 2008

MCDBA SQL Server 2000

_____________________________

CCEA XP/3.0/4.0

CCA XenServer

CCSP

_____________________________

RES PowerFuse Certified Professional

RES Wisdom Certified Professional

 

 

"yair" <yair@discussions.microsoft.com> schreef in bericht

news:0B04001F-4087-45BC-9BBA-3511B0260600@microsoft.com...

> Hi Piet,

>

> Both servers are at the exact patchlevel, to the latest update.

> I alreay used both Kyocera's deleter.exe and MS's cleanspl.exe on the

> server

> and reinstalled the files.

>

> Tried both filemon and processmon and thought I found the problem -

> shell32.dll in %systemroot%\system32 seemed to deny access -- but then I

> saw

> that the second server acts exactly the same way. So no better insight

> here

> I'm afraid.

>

> I thought of creating an image of the second server and replicate it to

> the

> first one, but there is software on the first one that can't be replaced

> so

> I'm rather stuck here too.

>

> Any other ideas?

>

> Thanks in advance.

>

> Yair Millenbach

>

> "Piet van Dongen" wrote:

>

>> Hi Yiar,

>>

>> Are borh the server at the exact same patchlevel?

>> First try the delete the printer drivers and reinstall them.

>> Kyocera has an print driver delete tool (google this)

>>

>> If this will not work try you got to find out if a file is missing.

>> Try to print from the working TS server en use Filemon from SysInternals

>> (=

>> now M$)

>> Then try to print from the bad behaving TS server.

>>

>> Compare this two text files with an text compare tool like google docs

>> and

>> you find the missing file...

>>

>> With future service pack installs, backup your server with an image tool

>> (ghost, acronis) so you always can do a rollback.

>>

>> Regards,

>>

>> Piet van Dongen

>>

>> _____________________________

>> MCSA/MCSE Windows 2000/2003

>> MCTS Windows Server 2008

>> MCDBA SQL Server 2000

>> _____________________________

>> CCEA XP/3.0/4.0

>> CCA XenServer

>> CCSP

>> _____________________________

>> RES PowerFuse Certified Professional

>> RES Wisdom Certified Professional

>>

>>

>>

>> "yair" <yair@discussions.microsoft.com> schreef in bericht

>> news:587D828E-C576-401F-A913-985E0F3E5C66@microsoft.com...

>> > Hi Piet,

>> >

>> > Yes. I used the HP Laserjet 4 Plus driver (from the MS list).

>> > I also installed the local Kyocera driver (OEM) for a kyocera printer,

>> > which

>> > can't use the same HP driver.

>> >

>> > Any thoughts?

>> >

>> > Thanks,

>> >

>> > Yair

>> >

>> > "Piet van Dongen" wrote:

>> >

>> >> Hi Yair,

>> >>

>> >> Do you have installed the right printer driver on the terminal server

>> >> that

>> >> doesn't remap the printers?

>> >>

>> >>

>> >> Regards,

>> >>

>> >> Piet van Dongen

>> >>

>> >> _____________________________

>> >> MCSA/MCSE Windows 2000/2003

>> >> MCTS Windows Server 2008

>> >> MCDBA SQL Server 2000

>> >>

>> >> CCEA XP/3.0/4.0

>> >> CCA XenServer

>> >> CCSP

>> >>

>> >> RES PowerFuse Certified Professional

>> >> RES Wisdom Certified Professional

>> >>

>> >>

>> >>

>> >> "yair" <yair@discussions.microsoft.com> schreef in bericht

>> >> news:A54C9B3A-BEDE-4E2B-A517-D47A61615D7C@microsoft.com...

>> >> > Hi,

>> >> >

>> >> > I've recently managed to finally update my 2K3 server from SP1 to

>> >> > SP2.

>> >> > Ever

>> >> > since, the server, which functions as a terminal server doesn't

>> >> > allow

>> >> > users

>> >> > to print to a mapped printer, and registers an error (event ID

>> >> > 6161 -

>> >> > Win32

>> >> > error code returned by the print processor: 3. The system cannot

>> >> > find

>> >> > the

>> >> > path specified). The server prints to all other printers, both local

>> >> > and

>> >> > remote (as long as they are not in a specific session)

>> >> >

>> >> > Naturally, I went through all possible posts but none seem to

>> >> > address

>> >> > this

>> >> > specific problem. Tried cleanspl.exe and all other remedies

>> >> > including

>> >> > checking the registry, backing up the other server's spooler and

>> >> > restoring

>> >> > it

>> >> > to this one, and so on.

>> >> >

>> >> > To complicate matters even further, this server has a duplicate

>> >> > server

>> >> > (with

>> >> > SP2) and the clients can log on and print without any problelem.

>> >> >

>> >> > Any ideas?

>> >> >

>> >> > Thanks in advance,

>> >> >

>> >> > Yair Millenbach

>> >>

>>