Robert,
Can you explain a bit more what you mean by modifying permission in the spool folder? Only two of us have access to the folder as administrators, and we don't believe we have changed anything. Can a user change something like that without being able to log into the server? (ie. from their workstation).

Troy Funte
Liberty Electronics

----- Original Message -----
From: Robert Bruton
To: vantage@egroups.com
Sent: Tuesday, December 12, 2000 1:27 PM
Subject: RE: [Vantage] Re: [off topic] Print Spooling problem.

Permissions.....Just a thought....could some of your users have create but
not delete/modify permission in the spool folder?

-----Original Message-----
From: Ted Kitch [mailto:ted@...]
Sent: Tuesday, December 12, 2000 2:37 PM
To: vantage@egroups.com
Subject: Re: [Vantage] Re: [off topic] Print Spooling problem.

Here are two suggestions to help with your problem. NT does an OK job of
managing printers, but there still will always be those jobs that hang and
leave files.

[Non-text portions of this message have been removed]

eGroups Sponsor

We no longer allow attachments to files. To access/share Report Files, please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to www.egroups.com, login and be sure to save your password, choose My Groups, choose Vantage, then choose Files. If you save the password, the link above will work the next time you try it.)

[Non-text portions of this message have been removed]

While I have no useful experience with NT, I have seen a similar problem on some Unix systems, where files never print because the job doing the spooling does not close the spool file correctly. are the jobs that hang around from the same user, or the same menu option?
i.e. Do all the jobs that fail to print belong to fred, or does the report of Incomplete Late Shift jobs, always(usually) fail?

Troy Funte wrote:

> I need some help diagnosing a Print Spooler problem.
>
> Observing the C\WINNT\system32\spool\PRINTERS file on our server, I
> see sets of files come and go in the directory. For instance, someone
> sends a print job and the files 0010.spl and 0010.shd appear for a
> few moments and disappear (hopefully). But gradually, some of
> the .spl files remain. When the number of .spl files in the
> directory reaches about 200 or so, then certain people cannot print
> any longer. Deleting these files from the PRINTERS directory clears
> things up and people can print again.
>
> Does anyone understand why this is happening and/or know of a
> solution?
>
> P.S. Before this problem started, everyone would spool to the
> server. A workaround has been to install the HP utility on each
> workstation to spool to the workstation instead of the server. This
> has helped some, but the files still gradually appear on the server
> and clog things up.
>
> Thanks.
>
> Troy Funte
> Liberty Electronics
>
>
> We no longer allow attachments to files. To access/share Report Files, please go to the following link: http://www.egroups.com/files/vantage/
> (Note: If this link does not work for you the first time you try it, go to www.egroups.com, login and be sure to save your password, choose My Groups, choose Vantage, then choose Files. If you save the password, the link above will work the next time you try it.)

--
/* ============================================================== */

William E. Colls Tel 613 591 0079
PROComputer Systems Fax 613 591 3924
67 Willow Glen Dr www.procomsys.com
Kanata Ontario Canada PEG Member 1998051404

Specialists in Progress Software development since 1985

William,
I'm not sure sure how to tell which user the jobs are coming from. I
just have the number on the file, and the contents are empty.

--- In vantage@egroups.com, William Colls <william@p...> wrote:
> While I have no useful experience with NT, I have seen a similar
problem on some Unix systems, where files never print because the job
doing the spooling does not close the spool file correctly. are the
jobs that hang around from the same user, or the same menu option?
> i.e. Do all the jobs that fail to print belong to fred, or does the
report of Incomplete Late Shift jobs, always(usually) fail?
>
> Troy Funte wrote:
>
> > I need some help diagnosing a Print Spooler problem.
> >
> > Observing the C\WINNT\system32\spool\PRINTERS file on our server,
I
> > see sets of files come and go in the directory. For instance,
someone
> > sends a print job and the files 0010.spl and 0010.shd appear for a
> > few moments and disappear (hopefully). But gradually, some of
> > the .spl files remain. When the number of .spl files in the
> > directory reaches about 200 or so, then certain people cannot
print
>> any longer. Deleting these files from the PRINTERS directory
clears
>> things up and people can print again.
>>
>> Does anyone understand why this is happening and/or know of a
>> solution?
>>
>> P.S. Before this problem started, everyone would spool to the
>> server. A workaround has been to install the HP utility on each
>> workstation to spool to the workstation instead of the server. This
>> has helped some, but the files still gradually appear on the server
> > and clog things up.
> >
> > Thanks.
> >
> > Troy Funte
> > Liberty Electronics

Hey guys,

if you go look in event viewer, you will be able to see all the people that
have printed. So if you go to administrative tools under programs and in
event viewer. then when event viewer opens up, look under the log menu, and
make sure that system is checked, and then under view, check newest first

hope this helps

-----Original Message-----
From: Troy Funte [mailto:tfunte@...]
Sent: Tuesday, December 12, 2000 10:40 AM
To: vantage@egroups.com
Subject: [Vantage] Re: [off topic] Print Spooling problem.

William,
I'm not sure sure how to tell which user the jobs are coming from. I
just have the number on the file, and the contents are empty.

--- In vantage@egroups.com, William Colls <william@p...> wrote:
> While I have no useful experience with NT, I have seen a similar
problem on some Unix systems, where files never print because the job
doing the spooling does not close the spool file correctly. are the
jobs that hang around from the same user, or the same menu option?
> i.e. Do all the jobs that fail to print belong to fred, or does the
report of Incomplete Late Shift jobs, always(usually) fail?
>
> Troy Funte wrote:
>
> > I need some help diagnosing a Print Spooler problem.
> >
> > Observing the C\WINNT\system32\spool\PRINTERS file on our server,
I
> > see sets of files come and go in the directory. For instance,
someone
> > sends a print job and the files 0010.spl and 0010.shd appear for a
> > few moments and disappear (hopefully). But gradually, some of
> > the .spl files remain. When the number of .spl files in the
> > directory reaches about 200 or so, then certain people cannot
print
>> any longer. Deleting these files from the PRINTERS directory
clears
>> things up and people can print again.
>>
>> Does anyone understand why this is happening and/or know of a
>> solution?
>>
>> P.S. Before this problem started, everyone would spool to the
>> server. A workaround has been to install the HP utility on each
>> workstation to spool to the workstation instead of the server. This
>> has helped some, but the files still gradually appear on the server
> > and clog things up.
> >
> > Thanks.
> >
> > Troy Funte
> > Liberty Electronics

eGroups Sponsor

<http://rd.yahoo.com/M=102308.1038796.2731130.908943/D=egroupmail/S=17000071
83:N/A=466331/?http://features.yahoo.com/webceleb/carrey/> Click Here!

We no longer allow attachments to files. To access/share Report Files,
please go to the following link: http://www.egroups.com/files/vantage/
<http://www.egroups.com/files/vantage/>
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)

Troy,

Here is my take on this one... Check the amount of disk space on the c: drive
were the spool files are located, If you are running out of disk space or it's low
some small print jobs will print, but large print jobs will fail. You may need to
change the location of the printer spool location to another drive that has more space

Hope this helps,

Jeff

Troy Funte wrote:

> I need some help diagnosing a Print Spooler problem.
>
> Observing the C\WINNT\system32\spool\PRINTERS file on our server, I
> see sets of files come and go in the directory. For instance, someone
> sends a print job and the files 0010.spl and 0010.shd appear for a
> few moments and disappear (hopefully). But gradually, some of
> the .spl files remain. When the number of .spl files in the
> directory reaches about 200 or so, then certain people cannot print
> any longer. Deleting these files from the PRINTERS directory clears
> things up and people can print again.
>
> Does anyone understand why this is happening and/or know of a
> solution?
>
> P.S. Before this problem started, everyone would spool to the
> server. A workaround has been to install the HP utility on each
> workstation to spool to the workstation instead of the server. This
> has helped some, but the files still gradually appear on the server
> and clog things up.
>
> Thanks.
>
> Troy Funte
> Liberty Electronics

Justin,
I'm using your theory to coincide Print jobs Time/Date stamp with
the time/date on the .spl files that are left in the Spool
Directory. Some people's work fine (are deleted when the job is
done) and some stick around and are not deleted after printing.

Troy

--- In vantage@egroups.com, Justin Sorenson <Justin@w...> wrote:
> Hey guys,
>
> if you go look in event viewer, you will be able to see all the
people that
> have printed. So if you go to administrative tools under programs
and in
> event viewer. then when event viewer opens up, look under the log
menu, and
> make sure that system is checked, and then under view, check newest
first
>
> hope this helps
>
> -----Original Message-----
> From: Troy Funte [mailto:tfunte@e...]
> Sent: Tuesday, December 12, 2000 10:40 AM
> To: vantage@egroups.com
> Subject: [Vantage] Re: [off topic] Print Spooling problem.
>
>
> William,
> I'm not sure sure how to tell which user the jobs are coming from.
I
> just have the number on the file, and the contents are empty.
>
> --- In vantage@egroups.com, William Colls <william@p...> wrote:
> > While I have no useful experience with NT, I have seen a similar
> problem on some Unix systems, where files never print because the
job
> doing the spooling does not close the spool file correctly. are the
> jobs that hang around from the same user, or the same menu option?
> > i.e. Do all the jobs that fail to print belong to fred, or does
the
> report of Incomplete Late Shift jobs, always(usually) fail?
> >
> > Troy Funte wrote:
> >
> > > I need some help diagnosing a Print Spooler problem.
> > >
> > > Observing the C\WINNT\system32\spool\PRINTERS file on our
server,
> I
> > > see sets of files come and go in the directory. For instance,
> someone
> > > sends a print job and the files 0010.spl and 0010.shd appear
for a
> > > few moments and disappear (hopefully). But gradually, some of
> > > the .spl files remain. When the number of .spl files in the
> > > directory reaches about 200 or so, then certain people cannot
> print
> >> any longer. Deleting these files from the PRINTERS directory
> clears
> >> things up and people can print again.
> >>
> >> Does anyone understand why this is happening and/or know of a
> >> solution?
> >>
> >> P.S. Before this problem started, everyone would spool to the
> >> server. A workaround has been to install the HP utility on each
> >> workstation to spool to the workstation instead of the server.
This
> >> has helped some, but the files still gradually appear on the
server
> > > and clog things up.
> > >
> > > Thanks.
> > >
> > > Troy Funte
> > > Liberty Electronics
>
>
>
>
> eGroups Sponsor
>
>
<http://rd.yahoo.com/M=102308.1038796.2731130.908943/D=egroupmail/S=17
000071
> 83:N/A=466331/?http://features.yahoo.com/webceleb/carrey/> Click
Here!
>
> We no longer allow attachments to files. To access/share Report
Files,
> please go to the following link:
http://www.egroups.com/files/vantage/
> <http://www.egroups.com/files/vantage/>
> (Note: If this link does not work for you the first time you try
it, go to
> www.egroups.com, login and be sure to save your password, choose My
Groups,
> choose Vantage, then choose Files. If you save the password, the
link above
> will work the next time you try it.)

Jeff,
C: drive has 600+ MB of space, and many of these jobs that stick
around are very small. It must be something else.

Thanks for the reply.

Troy

--- In vantage@egroups.com, Jeffrey Myers <myersjg@o...> wrote:
> Troy,
>
> Here is my take on this one... Check the amount of disk space
on the c: drive
> were the spool files are located, If you are running out of disk
space or it's low
> some small print jobs will print, but large print jobs will fail.
You may need to
> change the location of the printer spool location to another drive
that has more space
>
> Hope this helps,
>
> Jeff
>
> Troy Funte wrote:
>
> > I need some help diagnosing a Print Spooler problem.
> >
> > Observing the C\WINNT\system32\spool\PRINTERS file on our server,
I
> > see sets of files come and go in the directory. For instance,
someone
> > sends a print job and the files 0010.spl and 0010.shd appear for a
> > few moments and disappear (hopefully). But gradually, some of
> > the .spl files remain. When the number of .spl files in the
> > directory reaches about 200 or so, then certain people cannot
print
> > any longer. Deleting these files from the PRINTERS directory
clears
> > things up and people can print again.
> >
> > Does anyone understand why this is happening and/or know of a
> > solution?
> >
> > P.S. Before this problem started, everyone would spool to the
> > server. A workaround has been to install the HP utility on each
> > workstation to spool to the workstation instead of the server.
This
> > has helped some, but the files still gradually appear on the
server
> > and clog things up.
> >
> > Thanks.
> >
> > Troy Funte
> > Liberty Electronics

another thing that can work if you have troubles Troy, is if you go into
Services, you can start and stop the spooler to delete them.

-----Original Message-----
From: Troy Funte [mailto:tfunte@...]
Sent: Tuesday, December 12, 2000 1:33 PM
To: vantage@egroups.com
Subject: [Vantage] Re: [off topic] Print Spooling problem.

Justin,
I'm using your theory to coincide Print jobs Time/Date stamp with
the time/date on the .spl files that are left in the Spool
Directory. Some people's work fine (are deleted when the job is
done) and some stick around and are not deleted after printing.

Troy

--- In vantage@egroups.com, Justin Sorenson <Justin@w...> wrote:
> Hey guys,
>
> if you go look in event viewer, you will be able to see all the
people that
> have printed. So if you go to administrative tools under programs
and in
> event viewer. then when event viewer opens up, look under the log
menu, and
> make sure that system is checked, and then under view, check newest
first
>
> hope this helps
>
> -----Original Message-----
> From: Troy Funte [mailto:tfunte@e...]
> Sent: Tuesday, December 12, 2000 10:40 AM
> To: vantage@egroups.com
> Subject: [Vantage] Re: [off topic] Print Spooling problem.
>
>
> William,
> I'm not sure sure how to tell which user the jobs are coming from.
I
> just have the number on the file, and the contents are empty.
>
> --- In vantage@egroups.com, William Colls <william@p...> wrote:
> > While I have no useful experience with NT, I have seen a similar
> problem on some Unix systems, where files never print because the
job
> doing the spooling does not close the spool file correctly. are the
> jobs that hang around from the same user, or the same menu option?
> > i.e. Do all the jobs that fail to print belong to fred, or does
the
> report of Incomplete Late Shift jobs, always(usually) fail?
> >
> > Troy Funte wrote:
> >
> > > I need some help diagnosing a Print Spooler problem.
> > >
> > > Observing the C\WINNT\system32\spool\PRINTERS file on our
server,
> I
> > > see sets of files come and go in the directory. For instance,
> someone
> > > sends a print job and the files 0010.spl and 0010.shd appear
for a
> > > few moments and disappear (hopefully). But gradually, some of
> > > the .spl files remain. When the number of .spl files in the
> > > directory reaches about 200 or so, then certain people cannot
> print
> >> any longer. Deleting these files from the PRINTERS directory
> clears
> >> things up and people can print again.
> >>
> >> Does anyone understand why this is happening and/or know of a
> >> solution?
> >>
> >> P.S. Before this problem started, everyone would spool to the
> >> server. A workaround has been to install the HP utility on each
> >> workstation to spool to the workstation instead of the server.
This
> >> has helped some, but the files still gradually appear on the
server
> > > and clog things up.
> > >
> > > Thanks.
> > >
> > > Troy Funte
> > > Liberty Electronics
>
>
>
>
> eGroups Sponsor
>
>
< http://rd.yahoo.com/M=102308.1038796.2731130.908943/D=egroupmail/S=17
<http://rd.yahoo.com/M=102308.1038796.2731130.908943/D=egroupmail/S=17>
000071
> 83:N/A=466331/? http://features.yahoo.com/webceleb/carrey/
<http://features.yahoo.com/webceleb/carrey/> > Click
Here!
>
> We no longer allow attachments to files. To access/share Report
Files,
> please go to the following link:
http://www.egroups.com/files/vantage/
<http://www.egroups.com/files/vantage/>
> < http://www.egroups.com/files/vantage/
<http://www.egroups.com/files/vantage/> >
> (Note: If this link does not work for you the first time you try
it, go to
> www.egroups.com, login and be sure to save your password, choose My
Groups,
> choose Vantage, then choose Files. If you save the password, the
link above
> will work the next time you try it.)

eGroups Sponsor

<http://rd.yahoo.com/M=102308.1038796.2731130.908943/D=egroupmail/S=17000071
83:N/A=466330/?http://www.yahoo.com> Click Here!

We no longer allow attachments to files. To access/share Report Files,
please go to the following link: http://www.egroups.com/files/vantage/
<http://www.egroups.com/files/vantage/>
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)

Not being familiar with NT, is there a limit to the number of files that can be in one directory, and can this limit be adjusted? If there is a limit, and it can be adjusted upward, that might at least give you a work around, until you can determine why the jobs don't
print, and fix that.

Another though: I think you noted else where that the jobs that did not print were zero length. Could this itself be the problem? If this is the case, could users be starting reports, and the killing them with a control-break exit?

Troy Funte wrote:

> William,
> I'm not sure sure how to tell which user the jobs are coming from. I
> just have the number on the file, and the contents are empty.
>
> --- In vantage@egroups.com, William Colls <william@p...> wrote:
> > While I have no useful experience with NT, I have seen a similar
> problem on some Unix systems, where files never print because the job
> doing the spooling does not close the spool file correctly. are the
> jobs that hang around from the same user, or the same menu option?
> > i.e. Do all the jobs that fail to print belong to fred, or does the
> report of Incomplete Late Shift jobs, always(usually) fail?
> >
> > Troy Funte wrote:
> >
> > > I need some help diagnosing a Print Spooler problem.
> > >
> > > Observing the C\WINNT\system32\spool\PRINTERS file on our server,
> I
> > > see sets of files come and go in the directory. For instance,
> someone
> > > sends a print job and the files 0010.spl and 0010.shd appear for a
> > > few moments and disappear (hopefully). But gradually, some of
> > > the .spl files remain. When the number of .spl files in the
> > > directory reaches about 200 or so, then certain people cannot
> print
> >> any longer. Deleting these files from the PRINTERS directory
> clears
> >> things up and people can print again.
> >>
> >> Does anyone understand why this is happening and/or know of a
> >> solution?
> >>
> >> P.S. Before this problem started, everyone would spool to the
> >> server. A workaround has been to install the HP utility on each
> >> workstation to spool to the workstation instead of the server. This
> >> has helped some, but the files still gradually appear on the server
> > > and clog things up.
> > >
> > > Thanks.
> > >
> > > Troy Funte
> > > Liberty Electronics
>
>
> We no longer allow attachments to files. To access/share Report Files, please go to the following link: http://www.egroups.com/files/vantage/
> (Note: If this link does not work for you the first time you try it, go to www.egroups.com, login and be sure to save your password, choose My Groups, choose Vantage, then choose Files. If you save the password, the link above will work the next time you try it.)

William,

I don't think the zero length is the problem, or the number of
files...
When someone prints, two new files come up in the C\WINNT\system32
\spool\PRINTERS folder: a .spl file and a .shd file. Both should
disappear after the print job is done. SOMETIMES, however, the .spl
file is left behind (after a successful print, by the way). When the
number of .spl files gets to be too many (like 200 or so, all of
which have 0 K in length), then no one can print.

Why are the .spl files hanging around and not deleting for SOME users.

Troy

--- In vantage@egroups.com, William Colls <william@p...> wrote:
> Not being familiar with NT, is there a limit to the number of files
that can be in one directory, and can this limit be adjusted? If
there is a limit, and it can be adjusted upward, that might at least
give you a work around, until you can determine why the jobs don't
> print, and fix that.
>
> Another though: I think you noted else where that the jobs that did
not print were zero length. Could this itself be the problem? If this
is the case, could users be starting reports, and the killing them
with a control-break exit?
>
> Troy Funte wrote:
>
> > William,
> > I'm not sure sure how to tell which user the jobs are coming
from. I
> > just have the number on the file, and the contents are empty.
> >
> > --- In vantage@egroups.com, William Colls <william@p...> wrote:
> > > While I have no useful experience with NT, I have seen a similar
> > problem on some Unix systems, where files never print because the
job
> > doing the spooling does not close the spool file correctly. are
the
> > jobs that hang around from the same user, or the same menu option?
> > > i.e. Do all the jobs that fail to print belong to fred, or does
the
> > report of Incomplete Late Shift jobs, always(usually) fail?
> > >
> > > Troy Funte wrote:
> > >
> > > > I need some help diagnosing a Print Spooler problem.
> > > >
> > > > Observing the C\WINNT\system32\spool\PRINTERS file on our
server,
> > I
> > > > see sets of files come and go in the directory. For instance,
> > someone
> > > > sends a print job and the files 0010.spl and 0010.shd appear
for a
> > > > few moments and disappear (hopefully). But gradually, some of
> > > > the .spl files remain. When the number of .spl files in the
> > > > directory reaches about 200 or so, then certain people cannot
> > print
> > >> any longer. Deleting these files from the PRINTERS directory
> > clears
> > >> things up and people can print again.
> > >>
> > >> Does anyone understand why this is happening and/or know of a
> > >> solution?
> > >>
> > >> P.S. Before this problem started, everyone would spool to the
> > >> server. A workaround has been to install the HP utility on
each
> > >> workstation to spool to the workstation instead of the server.
This
> > >> has helped some, but the files still gradually appear on the
server
> > > > and clog things up.
> > > >
> > > > Thanks.
> > > >
> > > > Troy Funte
> > > > Liberty Electronics

Here are two suggestions to help with your problem. NT does an OK job of managing printers, but there still will always be those jobs that hang and leave files.

I used to have an HP LaserJet 4 printer connected to a Windows NT 4 server that would do the same thing that you have complained about. I moved the print queue to a different folder and checked the permissions on it. For this particular server that solved the problem. I've added a link to the KB article from MS that explains how to do this. http://support.microsoft.com/support/kb/articles/Q123/7/47.asp

Following is a batch file that you can schedule (using the AT command) that will stop the print spooler, delete all of the files in it and then restart it. I've used this on numerous servers to clean out the queue on a periodic basis. I set this up to run weekly and it eliminated the issues that I was having with print files being left.

-----------------------------BEGIN BATCH FILE-----------------------------
@echo off
net stop spooler
del %windir%\system32\spool\printers\*.*
net start spooler
------------------------------END BATCH FILE-------------------------------

Hope this helps.

Ted Kitch
ted@...

----- Original Message -----
From: Troy Funte
To: vantage@egroups.com
Sent: Tuesday, December 12, 2000 2:24 PM
Subject: [Vantage] Re: [off topic] Print Spooling problem.

William,

I don't think the zero length is the problem, or the number of
files...
When someone prints, two new files come up in the C\WINNT\system32
\spool\PRINTERS folder: a .spl file and a .shd file. Both should
disappear after the print job is done. SOMETIMES, however, the .spl
file is left behind (after a successful print, by the way). When the
number of .spl files gets to be too many (like 200 or so, all of
which have 0 K in length), then no one can print.

Why are the .spl files hanging around and not deleting for SOME users.

Troy

--- In vantage@egroups.com, William Colls <william@p...> wrote:
> Not being familiar with NT, is there a limit to the number of files
that can be in one directory, and can this limit be adjusted? If
there is a limit, and it can be adjusted upward, that might at least
give you a work around, until you can determine why the jobs don't
> print, and fix that.
>
> Another though: I think you noted else where that the jobs that did
not print were zero length. Could this itself be the problem? If this
is the case, could users be starting reports, and the killing them
with a control-break exit?
>
> Troy Funte wrote:
>
> > William,
> > I'm not sure sure how to tell which user the jobs are coming
from. I
> > just have the number on the file, and the contents are empty.
> >
> > --- In vantage@egroups.com, William Colls <william@p...> wrote:
> > > While I have no useful experience with NT, I have seen a similar
> > problem on some Unix systems, where files never print because the
job
> > doing the spooling does not close the spool file correctly. are
the
> > jobs that hang around from the same user, or the same menu option?
> > > i.e. Do all the jobs that fail to print belong to fred, or does
the
> > report of Incomplete Late Shift jobs, always(usually) fail?
> > >
> > > Troy Funte wrote:
> > >
> > > > I need some help diagnosing a Print Spooler problem.
> > > >
> > > > Observing the C\WINNT\system32\spool\PRINTERS file on our
server,
> > I
> > > > see sets of files come and go in the directory. For instance,
> > someone
> > > > sends a print job and the files 0010.spl and 0010.shd appear
for a
> > > > few moments and disappear (hopefully). But gradually, some of
> > > > the .spl files remain. When the number of .spl files in the
> > > > directory reaches about 200 or so, then certain people cannot
> > print
> > >> any longer. Deleting these files from the PRINTERS directory
> > clears
> > >> things up and people can print again.
> > >>
> > >> Does anyone understand why this is happening and/or know of a
> > >> solution?
> > >>
> > >> P.S. Before this problem started, everyone would spool to the
> > >> server. A workaround has been to install the HP utility on
each
> > >> workstation to spool to the workstation instead of the server.
This
> > >> has helped some, but the files still gradually appear on the
server
> > > > and clog things up.
> > > >
> > > > Thanks.
> > > >
> > > > Troy Funte
> > > > Liberty Electronics

eGroups Sponsor

We no longer allow attachments to files. To access/share Report Files, please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to www.egroups.com, login and be sure to save your password, choose My Groups, choose Vantage, then choose Files. If you save the password, the link above will work the next time you try it.)

[Non-text portions of this message have been removed]

Ted,
We may try the suggestion of moving the folder.

When I ran the batch file, it couldn't find the command for "del" to delete the files. I did a "find" and there is a delete.exe file in a subdirectory of a subdirectory in McAffee or something, but didn't know if I dare use it. Whatta think?

Troy Funte
Liberty Electronics

----- Original Message -----
From: Ted Kitch
To: vantage@egroups.com
Sent: Tuesday, December 12, 2000 12:37 PM
Subject: Re: [Vantage] Re: [off topic] Print Spooling problem.

Here are two suggestions to help with your problem. NT does an OK job of managing printers, but there still will always be those jobs that hang and leave files.

I used to have an HP LaserJet 4 printer connected to a Windows NT 4 server that would do the same thing that you have complained about. I moved the print queue to a different folder and checked the permissions on it. For this particular server that solved the problem. I've added a link to the KB article from MS that explains how to do this. http://support.microsoft.com/support/kb/articles/Q123/7/47.asp

Following is a batch file that you can schedule (using the AT command) that will stop the print spooler, delete all of the files in it and then restart it. I've used this on numerous servers to clean out the queue on a periodic basis. I set this up to run weekly and it eliminated the issues that I was having with print files being left.

-----------------------------BEGIN BATCH FILE-----------------------------
@echo off
net stop spooler
del %windir%\system32\spool\printers\*.*
net start spooler
------------------------------END BATCH FILE-------------------------------

Hope this helps.

Ted Kitch
ted@...
----- Original Message -----
From: Troy Funte
To: vantage@egroups.com
Sent: Tuesday, December 12, 2000 2:24 PM
Subject: [Vantage] Re: [off topic] Print Spooling problem.

William,

I don't think the zero length is the problem, or the number of
files...
When someone prints, two new files come up in the C\WINNT\system32
\spool\PRINTERS folder: a .spl file and a .shd file. Both should
disappear after the print job is done. SOMETIMES, however, the .spl
file is left behind (after a successful print, by the way). When the
number of .spl files gets to be too many (like 200 or so, all of
which have 0 K in length), then no one can print.

Why are the .spl files hanging around and not deleting for SOME users.

Troy

--- In vantage@egroups.com, William Colls <william@p...> wrote:
> Not being familiar with NT, is there a limit to the number of files
that can be in one directory, and can this limit be adjusted? If
there is a limit, and it can be adjusted upward, that might at least
give you a work around, until you can determine why the jobs don't
> print, and fix that.
>
> Another though: I think you noted else where that the jobs that did
not print were zero length. Could this itself be the problem? If this
is the case, could users be starting reports, and the killing them
with a control-break exit?
>
> Troy Funte wrote:
>
> > William,
> > I'm not sure sure how to tell which user the jobs are coming
from. I
> > just have the number on the file, and the contents are empty.
> >
> > --- In vantage@egroups.com, William Colls <william@p...> wrote:
> > > While I have no useful experience with NT, I have seen a similar
> > problem on some Unix systems, where files never print because the
job
> > doing the spooling does not close the spool file correctly. are
the
> > jobs that hang around from the same user, or the same menu option?
> > > i.e. Do all the jobs that fail to print belong to fred, or does
the
> > report of Incomplete Late Shift jobs, always(usually) fail?
> > >
> > > Troy Funte wrote:
> > >
> > > > I need some help diagnosing a Print Spooler problem.
> > > >
> > > > Observing the C\WINNT\system32\spool\PRINTERS file on our
server,
> > I
> > > > see sets of files come and go in the directory. For instance,
> > someone
> > > > sends a print job and the files 0010.spl and 0010.shd appear
for a
> > > > few moments and disappear (hopefully). But gradually, some of
> > > > the .spl files remain. When the number of .spl files in the
> > > > directory reaches about 200 or so, then certain people cannot
> > print
> > >> any longer. Deleting these files from the PRINTERS directory
> > clears
> > >> things up and people can print again.
> > >>
> > >> Does anyone understand why this is happening and/or know of a
> > >> solution?
> > >>
> > >> P.S. Before this problem started, everyone would spool to the
> > >> server. A workaround has been to install the HP utility on
each
> > >> workstation to spool to the workstation instead of the server.
This
> > >> has helped some, but the files still gradually appear on the
server
> > > > and clog things up.
> > > >
> > > > Thanks.
> > > >
> > > > Troy Funte
> > > > Liberty Electronics

eGroups Sponsor

We no longer allow attachments to files. To access/share Report Files, please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to www.egroups.com, login and be sure to save your password, choose My Groups, choose Vantage, then choose Files. If you save the password, the link above will work the next time you try it.)

[Non-text portions of this message have been removed]

eGroups Sponsor

We no longer allow attachments to files. To access/share Report Files, please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to www.egroups.com, login and be sure to save your password, choose My Groups, choose Vantage, then choose Files. If you save the password, the link above will work the next time you try it.)

[Non-text portions of this message have been removed]