Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Windows services question

  • 14-12-2004 2:44pm
    #1
    Registered Users, Registered Users 2 Posts: 10,339 ✭✭✭✭


    Hi all,

    a probably very simple question but....

    A client's Server is running backup exec and a faulty tape has caused a job to run way past it's expected end time. Cant eject tape until the job is stopped.

    So, cancel job, close Backup Exec, services, stop and start the BE services, open backup exec and yaaay, hte backup has stopped. At least that's the idea.

    The Backup Exec Server service decided to hang with a "stopping" status.

    Tried Command prompt Net Stop "backup Exec Server" but it reports helpmsg 2189 and an explanation that the service is hung (great insight that :rolleyes: )

    Tried using PSkill from sysinternals

    http://www.sysinternals.com/ntw2k/freeware/pskill.shtml

    pskill -t \\<server name> "Backup Exec Server"

    but it just reports that the service does not exist.

    Anyone know another way to stop a hung service without resorting to a reboot?


Comments

  • Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 93,604 Mod ✭✭✭✭Capt'n Midnight


    Open the job - in frequency / schedule tick the box that says "enable automatic cancellation" and choose a time about 50% Longer than the job should take or early in next morning.

    use pslist \\server to get the process ID number for the process beserver
    and then pskill \\server 313 (or whatever)

    pslist \\server | find /i "b"

    note: if you have ticked the box that says send notifications AND you have logging set to directory or file level, beserver can take HOURS to smtp off the logs.. - Tools - Options - Job logs - summary only

    Depend on the version and as long as it's not an SQL server, the quickest way of stopping all services that are responding is to stop the BKupexec service from the icon on the taskbar.


  • Registered Users, Registered Users 2 Posts: 10,339 ✭✭✭✭LoLth


    thanks cap'n :) I wasnt using the process ID of the service.... me hangs head in shame....


Advertisement