Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Error 2292 - invalid schedule interval

Updated: 21 May 2010 | 2 comments
Dawsie's picture
Dawsie
Accredited
0 0 Votes
Login to vote
Hi,
Here is another call for help which surrounds a stuck/slow/growing A5 queue.
This is an EV2007 (no Service Packs so far) running on Windows 2000 SP4 processing four Exchange servers with a total of over 2000 items stuck in the A5 queues for each of of the Exchange servers which are not moving. The logs show an error 2292
“The schedule interval specified is invalid, the agent schedule should be <=60 and is currently 122”

These errors appear at exactly 10 second intervals and it therefore takes all of the five hours available from the start of the site schedule and the start of the backup thus not leaving any time to process any other entries in the A5 queues which are therefore gradually growing.

I have unsuccessfully searched for anything which has a 10 second timeout to give a clue. Unfortunately I do not have any DTRACE information yet.

Eventually I may be forced to stop the services and purge the A5 queues which should be safe since Safety Copies are in use.
 
Is this a new error to EV2007?
Discussion Filed Under:
,

Comments

EV Director's picture
28
Jan
2008
0 Votes 0
Login to vote
EV Director
Symantec Employee

Hi,
 
Goto your archiving schedule and look to change the scheduling from 1 hour to 15 minutes.  ok that and then go back again, change it back to hours.  It sounds like you've got a corrupt value in the database somehow.

Mike Bilsborough
Director,Enterprise Vault Engineering Support 

Dawsie's picture
31
Jan
2008
0 Votes 0
Login to vote
Dawsie
Accredited

Excellent idea.
Problem was transitory, and so although it was logged over 1000 times, there was no actual corruption in the schedule fileds in the SQL Directory database that I could see, it must have been caused by a caching problem in SQL access which reported the corrupt data.
 
Thanks for the help - a few pointers is a lot quicker than a detailed debugging session.

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
270,002