Spooler service stopping on Windows Server 2008 Terminal Server

  • Thread starter Thread starter Jason A Ash
  • Start date Start date
J

Jason A Ash

Guest
Hello,

I've recently run into an issue with a client who is running Windows
Server 2008 as a Terminal Server. What is occurring, is the print
spooler service is stopping, with no errors or warnings. Restarting the
spooler service allows printing to continue.

The client is accessing a Foxpro based program, and we are using Remote
Application for the remote users, rather than a full desktop. The
server is up-to-date on Windows updates.

Other clients, connecting to an identical Terminal Server, running the
same application, in the same office, have no problems with the print
spooler stopping.

Any thoughts?

Thank you,
Jason A.
 
Re: Spooler service stopping on Windows Server 2008 Terminal Server

Hello Jason,

Is it only with a specific printer or with all? Make sure that you have the
correct drivers installed. Check that domain users have write right on the
C:\windows\system32\spooler folder.
Did you use web access or remote desktop connections? For RDP the client
computer must be running Remote Desktop Connection (RDC) 6.0 or RDC 6.1.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hello,
>
> I've recently run into an issue with a client who is running Windows
> Server 2008 as a Terminal Server. What is occurring, is the print
> spooler service is stopping, with no errors or warnings. Restarting
> the spooler service allows printing to continue.
>
> The client is accessing a Foxpro based program, and we are using
> Remote Application for the remote users, rather than a full desktop.
> The server is up-to-date on Windows updates.
>
> Other clients, connecting to an identical Terminal Server, running the
> same application, in the same office, have no problems with the print
> spooler stopping.
>
> Any thoughts?
>
> Thank you,
> Jason A.
 
Re: Spooler service stopping on Windows Server 2008 Terminal Server

Not sure on the printers, another tech was working with this client
prior to me.

I'll check the write permissions on Monday.

We're using Remote Desktop, not web access, and have been making sure
all clients are running RDC6.1, and .NET Framework 3.0

Thanks,
Jason A.

Meinolf Weber wrote:
> Hello Jason,
>
> Is it only with a specific printer or with all? Make sure that you have
> the correct drivers installed. Check that domain users have write right
> on the C:\windows\system32\spooler folder.
> Did you use web access or remote desktop connections? For RDP the client
> computer must be running Remote Desktop Connection (RDC) 6.0 or RDC 6.1.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hello,
>>
>> I've recently run into an issue with a client who is running Windows
>> Server 2008 as a Terminal Server. What is occurring, is the print
>> spooler service is stopping, with no errors or warnings. Restarting
>> the spooler service allows printing to continue.
>>
>> The client is accessing a Foxpro based program, and we are using
>> Remote Application for the remote users, rather than a full desktop.
>> The server is up-to-date on Windows updates.
>>
>> Other clients, connecting to an identical Terminal Server, running the
>> same application, in the same office, have no problems with the print
>> spooler stopping.
>>
>> Any thoughts?
>>
>> Thank you,
>> Jason A.
>
>
 
Re: Spooler service stopping on Windows Server 2008 Terminal Server

Not sure on the printers, another tech was working with this client
prior to me.

I'll check the write permissions on Monday.

We're using Remote Desktop, not web access, and have been making sure
all clients are running RDC6.1, and .NET Framework 3.0

Thanks,
Jason A.

Meinolf Weber wrote:
> Hello Jason,
>
> Is it only with a specific printer or with all? Make sure that you have
> the correct drivers installed. Check that domain users have write right
> on the C:\windows\system32\spooler folder.
> Did you use web access or remote desktop connections? For RDP the client
> computer must be running Remote Desktop Connection (RDC) 6.0 or RDC 6.1.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hello,
>>
>> I've recently run into an issue with a client who is running Windows
>> Server 2008 as a Terminal Server. What is occurring, is the print
>> spooler service is stopping, with no errors or warnings. Restarting
>> the spooler service allows printing to continue.
>>
>> The client is accessing a Foxpro based program, and we are using
>> Remote Application for the remote users, rather than a full desktop.
>> The server is up-to-date on Windows updates.
>>
>> Other clients, connecting to an identical Terminal Server, running the
>> same application, in the same office, have no problems with the print
>> spooler stopping.
>>
>> Any thoughts?
>>
>> Thank you,
>> Jason A.
>
>
 
Re: Spooler service stopping on Windows Server 2008 Terminal Server

The usual reason that the Print Spooler stops is becuase of a defective
printer driver.

You might find the folks that hang out in
microsoft.public.vista.print_fax_scan or
microsoft.public.windowsxp.print_fax can help you.

Printer drivers tend to be indiosyncratic, so it will be important to know
what printers are installed/connected and what printer drivers are installed
on the server where the Print Spooler stops.

You may find that the print vendor has a newer driver that solves this
problem.
--
Bruce Sanderson
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Jason A Ash" <JasonAAsh@community.nospam> wrote in message
news:uexLIRz$IHA.4684@TK2MSFTNGP06.phx.gbl...
> Hello,
>
> I've recently run into an issue with a client who is running Windows
> Server 2008 as a Terminal Server. What is occurring, is the print spooler
> service is stopping, with no errors or warnings. Restarting the spooler
> service allows printing to continue.
>
> The client is accessing a Foxpro based program, and we are using Remote
> Application for the remote users, rather than a full desktop. The server
> is up-to-date on Windows updates.
>
> Other clients, connecting to an identical Terminal Server, running the
> same application, in the same office, have no problems with the print
> spooler stopping.
>
> Any thoughts?
>
> Thank you,
> Jason A.
 
Re: Spooler service stopping on Windows Server 2008 Terminal Server

>I've recently run into an issue with a client who is running Windows
>Server 2008 as a Terminal Server. What is occurring, is the print
>spooler service is stopping, with no errors or warnings. Restarting the
>spooler service allows printing to continue.
>
>The client is accessing a Foxpro based program, and we are using Remote
>Application for the remote users, rather than a full desktop. The
>server is up-to-date on Windows updates.
>
>Other clients, connecting to an identical Terminal Server, running the
>same application, in the same office, have no problems with the print
>spooler stopping.
>
>Any thoughts?

Whenever I hear of this issues on server 2003, I usually tell people
to check and see what the print processor is on the client and server
side. Haven't tried things on Server 2008 but I would imagine not much
has changed in MS land with this. Do a properties on the printer on
the server side, click the Advanced tab, if there's a Print Processor
button click it, if this hasn't change since 2003 server you'll likely
see Winprint and some other options as "Print Processor" options.
Check and make sure both client and server are set to Winprint.

HP's and a few others always hijack this processor and use there own
print processor which I find to screws up even the simplest of things.
Give it a shot and let me know how it goes.

- Thee Chicago Wolf
 
Re: Spooler service stopping on Windows Server 2008 Terminal Server

Hi,

I am wirting to see how evertything is going?

Have this issue been sovled or you need further assistance? please feel
free to let me know.

Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
--->Date: Sat, 16 Aug 2008 10:03:04 -0400
--->From: Jason A Ash <JasonAAsh@community.nospam>
--->User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
--->MIME-Version: 1.0
--->Subject: Re: Spooler service stopping on Windows Server 2008 Terminal
Server
--->References: <uexLIRz$IHA.4684@TK2MSFTNGP06.phx.gbl>
<ff16fb66a69dd8cacdc72727dd4a@msnews.microsoft.com>
--->In-Reply-To: <ff16fb66a69dd8cacdc72727dd4a@msnews.microsoft.com>
--->Content-Type: text/plain; charset=ISO-8859-1; format=flowed
--->Content-Transfer-Encoding: 7bit
--->Message-ID: <#A4hNj6$IHA.1180@TK2MSFTNGP04.phx.gbl>
--->Newsgroups: microsoft.public.windows.server.general
--->NNTP-Posting-Host: d149-67-209-137.col.wideopenwest.com 67.149.137.209
--->Lines: 1
--->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.general:43367
--->X-Tomcat-NG: microsoft.public.windows.server.general
--->
--->Not sure on the printers, another tech was working with this client
--->prior to me.
--->
--->I'll check the write permissions on Monday.
--->
--->We're using Remote Desktop, not web access, and have been making sure
--->all clients are running RDC6.1, and .NET Framework 3.0
--->
--->Thanks,
--->Jason A.
--->
--->Meinolf Weber wrote:
--->> Hello Jason,
--->>
--->> Is it only with a specific printer or with all? Make sure that you
have
--->> the correct drivers installed. Check that domain users have write
right
--->> on the C:\windows\system32\spooler folder.
--->> Did you use web access or remote desktop connections? For RDP the
client
--->> computer must be running Remote Desktop Connection (RDC) 6.0 or RDC
6.1.
--->>
--->> Best regards
--->>
--->> Meinolf Weber
--->> Disclaimer: This posting is provided "AS IS" with no warranties, and
--->> confers no rights.
--->> ** Please do NOT email, only reply to Newsgroups
--->> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
--->>
--->>> Hello,
--->>>
--->>> I've recently run into an issue with a client who is running Windows
--->>> Server 2008 as a Terminal Server. What is occurring, is the print
--->>> spooler service is stopping, with no errors or warnings. Restarting
--->>> the spooler service allows printing to continue.
--->>>
--->>> The client is accessing a Foxpro based program, and we are using
--->>> Remote Application for the remote users, rather than a full desktop.
--->>> The server is up-to-date on Windows updates.
--->>>
--->>> Other clients, connecting to an identical Terminal Server, running
the
--->>> same application, in the same office, have no problems with the print
--->>> spooler stopping.
--->>>
--->>> Any thoughts?
--->>>
--->>> Thank you,
--->>> Jason A.
--->>
--->>
--->
 
Re: Spooler service stopping on Windows Server 2008 Terminal Serve

Re: Spooler service stopping on Windows Server 2008 Terminal Serve

I am having a similar issue. I have a customer running Windows Server 2008.
They have two printers/copier/fax machines both Toshiba. They are connecting
via a network Card. They are located in two seperate geographic locations.
The remote location connects via Terminal Services over a VPN. When they are
connected and printing. The print spooler service shuts down randomly. This
only occurs while connected via terminal Services. The main office has the
same exact printer and works great. Please Help!!

"Thee Chicago Wolf" wrote:

> >I've recently run into an issue with a client who is running Windows
> >Server 2008 as a Terminal Server. What is occurring, is the print
> >spooler service is stopping, with no errors or warnings. Restarting the
> >spooler service allows printing to continue.
> >
> >The client is accessing a Foxpro based program, and we are using Remote
> >Application for the remote users, rather than a full desktop. The
> >server is up-to-date on Windows updates.
> >
> >Other clients, connecting to an identical Terminal Server, running the
> >same application, in the same office, have no problems with the print
> >spooler stopping.
> >
> >Any thoughts?
>
> Whenever I hear of this issues on server 2003, I usually tell people
> to check and see what the print processor is on the client and server
> side. Haven't tried things on Server 2008 but I would imagine not much
> has changed in MS land with this. Do a properties on the printer on
> the server side, click the Advanced tab, if there's a Print Processor
> button click it, if this hasn't change since 2003 server you'll likely
> see Winprint and some other options as "Print Processor" options.
> Check and make sure both client and server are set to Winprint.
>
> HP's and a few others always hijack this processor and use there own
> print processor which I find to screws up even the simplest of things.
> Give it a shot and let me know how it goes.
>
> - Thee Chicago Wolf
>
 
Re: Spooler service stopping on Windows Server 2008 Terminal Serve

Re: Spooler service stopping on Windows Server 2008 Terminal Serve

On Sep 23, 9:22 am, Pacware <Pacw...@discussions.microsoft.com> wrote:
> I am having a similar issue. I have a customer running WindowsServer2008.
> They have two printers/copier/fax machines both Toshiba. They are connecting
> via a network Card. They are located in two seperate geographic locations.
> The remote location connects viaTerminalServices over a VPN. When they are
> connected andprinting. The print spooler service shuts down randomly. This
> only occurs while connected viaterminalServices. The main office has the
> same exact printer and works great. Please Help!!
>
> "Thee Chicago Wolf" wrote:
> > >I've recently run into an issue with a client who is running Windows
> > >Server2008 as aTerminalServer. What is occurring, is the print
> > >spooler service is stopping, with no errors or warnings. Restarting the
> > >spooler service allowsprintingto continue.
>
> > >The client is accessing a Foxpro based program, and we are using Remote
> > >Application for the remote users, rather than a full desktop. The
> > >serveris up-to-date on Windows updates.
>
> > >Other clients, connecting to an identicalTerminalServer, running the
> > >same application, in the same office, have no problems with the print
> > >spooler stopping.
>
> > >Any thoughts?
>
> > Whenever I hear of this issues onserver2003, I usually tell people
> > to check and see what the print processor is on the client andserver
> > side. Haven't tried things onServer2008 but I would imagine not much
> > has changed in MS land with this. Do a properties on the printer on
> > theserverside, click the Advanced tab, if there's a Print Processor
> > button click it, if this hasn't change since 2003serveryou'll likely
> > see Winprint and some other options as "Print Processor" options.
> > Check and make sure both client andserverare set to Winprint.
>
> > HP's and a few others always hijack this processor and use there own
> > print processor which I find to screws up even the simplest of things.
> > Give it a shot and let me know how it goes.
>
> > - Thee Chicago Wolf

A third party printing solution will probably address this issue.
Check out <a href="http://www.tricerat.com/screwdrivers/">ScrewDrivers
by triCerat. </a>
 
Re: Spooler service stopping on Windows Server 2008 Terminal Serve

Re: Spooler service stopping on Windows Server 2008 Terminal Serve

Printers and printer drivers are very idiosyncratic. Much depends exactly
on which printer, what version of what printer driver and whether the
printing is is direct (e.g. from the workstation computer via a TCP/IP port)
or via a print server (e.g. a printer object shared from a Windows 2003 or
2008 server).

I suggest you contatct the printer vendor (or the reseller that sold you the
printer) to find out if there is a printer driver specifically for Windows
Server 2008 for the particular print device and if it is supported under
Terminal Services or not.

--
Bruce Sanderson
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Pacware" <Pacware@discussions.microsoft.com> wrote in message
news:64C99AB4-32D1-4FBA-A3B2-F1F0297FAE12@microsoft.com...
>I am having a similar issue. I have a customer running Windows Server 2008.
> They have two printers/copier/fax machines both Toshiba. They are
> connecting
> via a network Card. They are located in two seperate geographic locations.
> The remote location connects via Terminal Services over a VPN. When they
> are
> connected and printing. The print spooler service shuts down randomly.
> This
> only occurs while connected via terminal Services. The main office has the
> same exact printer and works great. Please Help!!
>
> "Thee Chicago Wolf" wrote:
>
>> >I've recently run into an issue with a client who is running Windows
>> >Server 2008 as a Terminal Server. What is occurring, is the print
>> >spooler service is stopping, with no errors or warnings. Restarting the
>> >spooler service allows printing to continue.
>> >
>> >The client is accessing a Foxpro based program, and we are using Remote
>> >Application for the remote users, rather than a full desktop. The
>> >server is up-to-date on Windows updates.
>> >
>> >Other clients, connecting to an identical Terminal Server, running the
>> >same application, in the same office, have no problems with the print
>> >spooler stopping.
>> >
>> >Any thoughts?
>>
>> Whenever I hear of this issues on server 2003, I usually tell people
>> to check and see what the print processor is on the client and server
>> side. Haven't tried things on Server 2008 but I would imagine not much
>> has changed in MS land with this. Do a properties on the printer on
>> the server side, click the Advanced tab, if there's a Print Processor
>> button click it, if this hasn't change since 2003 server you'll likely
>> see Winprint and some other options as "Print Processor" options.
>> Check and make sure both client and server are set to Winprint.
>>
>> HP's and a few others always hijack this processor and use there own
>> print processor which I find to screws up even the simplest of things.
>> Give it a shot and let me know how it goes.
>>
>> - Thee Chicago Wolf
>>
 
Back
Top