Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 23146
  • Last Modified:

Backup Exec will not complete a Cancel Pending job.

I have Backup Exec 9.1 running on a Windows 2003 Server. I have a job stuck in the Cancel Pending state. How can I get this job to complete canceling? The nighly jobs will not que up until this one completes! Thanks.
0
endpointnet
Asked:
endpointnet
1 Solution
 
Duncan MeyersCommented:
Try stopping and restarting the BAckup EXec services. You *may* find that the Job Engine won't stop and goes off into limbo (the service state goes to "Stopping" and doesn't change.) - if this happens, you need to reboot the server - no way around it I'm afraid.

Hope this helps.
0
 
Cyber-DudeCommented:
Yah, it happens: Please submit 'Process Explorer' and stop the devices manully.

There you go:
http://www.sysinternals.com/ntw2k/freeware/procexp.shtml

Download that utility and runit. You will notice 'Veritas Software Corporation' made processes (under 'Company Name' column). just 'Kill' them and restart the services via service manager...

That easy...

Cyber
0
 
Cyber-DudeCommented:
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
endpointnetAuthor Commented:
Thanks. That was a simple, perfect solution. The Process Explorer stopped the services, I restarted manually and the stuck job was complete and the next day's job is set to run. Thank you.
0
 
kinnea01Commented:
I had a similar problem with the Backup Exec services hanging and managed to restart them without a reboot.
I stopped the following processes in 'Task Manager' - 'Processes':

beserver.exe
benetns.exe
bengine.exe

Then I stopped all the remaining Backup Exec services that were still running using 'Computer Management- - Services'

I then restarted all the Backup Exec services using 'Computer Management'

Everything was then back to normal.
0
 
TIC_TelecomCommented:
kinnea01's solution worked quickly for me.

Thanks!
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

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