Data Driven subscriptions stop working after multiple edits?

This has happened several times. We set up a data driven subscription and it
runs fine. We can edit it a few times and it works fine afterwards also.
But at some point after perhaps editing it 5 or 6 times it jsut stops
working. The job never fires off like it wasn't scheduled. You can delete
it and recreate it, then it works fine again. There doesn't seem to be a
concrete pattern to it. It seems like the subscription jsut becomes
corrupted or something
Has anyone encountered a problem like this?Hi,
When i had tested data driven subscriptions i had changed the schedule say
at least about 25 times or more, i had not faced any issues.
One observation i had was if the time set for the schedule is the same as
the current computer time on click finish it does not run immediately. The
schedule time should always be a future time.
Regards,
Pugaz
"sebring1130" wrote:
> This has happened several times. We set up a data driven subscription and it
> runs fine. We can edit it a few times and it works fine afterwards also.
> But at some point after perhaps editing it 5 or 6 times it jsut stops
> working. The job never fires off like it wasn't scheduled. You can delete
> it and recreate it, then it works fine again. There doesn't seem to be a
> concrete pattern to it. It seems like the subscription jsut becomes
> corrupted or something
> Has anyone encountered a problem like this?|||I figured out what is causing this. When you first create a data-driven sub.
it works fine. Later, however, if you edit it to re-run it you run into a
problem if the subscription is set to run on a one-time basis only. You
select "one time" as the schedule and set the time you want it to fire off.
However you can't enter a date. Instead of picking up today as the default
like it does when you first create the subscription, it keeps the same date
that you originally used when you first set it up. So if you are editing a
one-time scheduled subscription and you didn't create the subscription that
same day, the schedule you just created is already in the past and thus never
fires. You can confirm this by checking the schedule table. A workaround is
to update the table manually...
Update Schedule
Set StartDate = '2004-11-10 14:10'
Where ScheduleID = 'whatever'
"sebring1130" wrote:
> This has happened several times. We set up a data driven subscription and it
> runs fine. We can edit it a few times and it works fine afterwards also.
> But at some point after perhaps editing it 5 or 6 times it jsut stops
> working. The job never fires off like it wasn't scheduled. You can delete
> it and recreate it, then it works fine again. There doesn't seem to be a
> concrete pattern to it. It seems like the subscription jsut becomes
> corrupted or something
> Has anyone encountered a problem like this?