Avatar of maureen99
maureen99Flag for United States of America

asked on 

error e000e020 since daylight savings time change

Hello,

I found our backups did not run after daylight savings time with the following error in the logs:

e000e020 - The job was scheduled to run, but the availability window closed before the job could start. There may not have been any destination devices available during the window, or the job may have been submitted to run when the window was closed.

Even after I change the time window to be back an hour and set the start no later than time to allow 2 hours in the time window, I still get failures on the test run.  The log on the test run failure is very vague:

e0008703 - The test run has detected a potential problem. See the job log for details.
For additional information regarding this error refer to link V-79-57344-34563

I have looked at the link but it doesn't give any information that I can use.

Does anyone have any insight as to why this may still be failing even after the time window is changed?  The time on the server is correct and the backup device is accessible and has the correct time.

I have also cross posted this ad symantec, and found a couple of threads on this issue here however the link on how to use the no longer works and I am unfamiliar with bestop.bat.

I appreciate any help with this issue and thanks very much,

Maureen
Storage SoftwareWindows Server 2003Storage

Avatar of undefined
Last Comment
maureen99
Avatar of eagle-22
eagle-22
Flag of United States of America image

A couple things I would try:
1) Run Live update to install any latest updates or patches
2) stop all services and then restart them (making sure the time is correct on the server before hand).

Avatar of maureen99
maureen99
Flag of United States of America image

ASKER

The time is correct on the server.  I ran live update and applied all the fixes that were out there.
Stopped the services and restarted them.

Still get the same results.

Another thread here indicated running BEutility.exe.  Should I be trying to run a repair on the database?
ASKER CERTIFIED SOLUTION
Avatar of eagle-22
eagle-22
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of maureen99
maureen99
Flag of United States of America image

ASKER

Thank you.

I checked the disk space to the NAS this is going to and there is enough.  
I tried running a test job "now" and it fails.
I can expand the time window to more than 2 hours

Unfortunately, we are a non-profit and got backup exec from techsoup.com so we can't call symantec for support.
Avatar of maureen99
maureen99
Flag of United States of America image

ASKER

Can anyone tell me if I should be using beutility on the database?  It was recommended in a different thread on this error.
Avatar of maureen99
maureen99
Flag of United States of America image

ASKER

I did a right click on one of the jobs and did a run now and the job ran.  After that the test run ran as well, and the jobs ran overnight.  

thanks alot for your help,

Maureen
Windows Server 2003
Windows Server 2003

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo