• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 638
  • Last Modified:

Windows batch or VB script : check if oldest file in folder is more than 50 secs

Print jobs in our Win 2003 occasionally got stuck.  Generally, a print
job spooled will be printed within half a minute & at any one time,
we've always seen one print job that's causing the problem (not
seen any multiple print job causing problem at any one time yet).

A print job will create one .spl & one .shd file to the folllowing folder:
   C:\Windows\System32\Spool\Printers

For this example, say, we have 3 print jobs:
abc.spl & abc.shd
bcd.spl & bcd.shd
cde.spl & cde.shd

I'll need a script (that I'll run every minute using Windows scheduler)
to check for the oldest (modified date/time) .spl to see if it is more
than 50 secs old.

If the oldest .spl file (take for example it's abc.spl in this case) is
more than 50 secs old, the script will

a) move abc.spl & abc.shd to c:\temp\stuckjob\  folder   &
b) move the rest of the files (in this case, it's bcd.* & cde.*)
    to c:\temp\goodjob\  folder
c) then restart the print spooler (ie issue 'sc stop spooler'
    followed by 'sc start spooler'
d) move back c:\temp\goodjob\*.* to
    C:\Windows\System32\Spool\Printers   folder
0
sunhux
Asked:
sunhux
  • 2
2 Solutions
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Not going to do this with a batch file since a batch file cannot check a file time to the second (without some other utility to look at file properties).

I wouldn't be looking to do 50 seconds ... why not every minute - something (relatively) easy?

Also, why do this at all.  Print jobs should not regularly get stuck.  If you're having problems, I'd fix the problems, not improvise a long term work-around to the problem.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Correct, a cmd batch would not allow for that granularity. VBS and PowerShell do, however. Nevertheless, I have to agree to what Lee said above - better to resolve the issue than use a flaky workaround.

PowerShell:
set-location C:\Windows\System32\Spool\Printers
get-childitem -filter '*.spl'|
  where {  ((get-date) - $_.LastWriteTime).TotalSeconds -gt 50 } |
  foreach-object {
    move-item $_, $_.Replace('.spl', '.shd') -Destination c:\temp\stuckjob\
    move-item * -Destination c:\temp\goodjob\
    restart-service Spooler -force
    move-item c:\temp\goodjob\* .
  }
}

Open in new window

0
 
sunhuxAuthor Commented:
Not quite regular affair but about once every 2-3 months, we have
one incident of a job being stuck & held up all other jobs in the spooler.
No specific error code in Event viewer too.

Is PowerShell available in Win 2003 or I need to install a PowerShell?
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
You'll need to download it. Windows Update should provide it as optional update.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now