Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
meisalas
Starting Member
6 Posts |
Posted - 2010-09-29 : 17:39:13
|
HELP! I'm losing my hair!I have a subscription to a report, and every time it is called, it's called twice. One Report, one subscription, using one shared schedule.During the schedule time, there are two calls to the subscription, please see exerpts from log, you can see that it is for the same subscription, but 2 seconds apart. 9/29/2010-14:00:13:: Creating Time based subscription notification for subscription: c10a4ea7-4fda-45ef-8f2f-acaf76e25f2a..9/29/2010-14:00:15:: Creating Time based subscription notification for subscription: c10a4ea7-4fda-45ef-8f2f-acaf76e25f2aThis statement is true for a LOT of reports where subscription was edited. Before it was using a custom schedule, but a Shared Schedule was made. This Shared schedule is called twice in succession. I am already literally pulling my hair as I don't know where else to look for. HELP! And THANKS in advance for any idea (or question) that could point out where the problem can be. |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
meisalas
Starting Member
6 Posts |
Posted - 2010-09-29 : 18:42:40
|
Yes, Tara, I did recreate the schedule and didn't help. Subscription was still called twice in succession. Now, I recreated the subscription itself which I was reaaally avoiding as much as possible, since there's about 40 data-driven subscriptions that were affected as well. Am just waiting for that new subscription to fire-up before saying that it worked. I hope there's other way though...Thanks a lot! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
meisalas
Starting Member
6 Posts |
Posted - 2010-09-30 : 12:07:57
|
Yeah, I've checked the ReportServer Database .. Catalog, ReportSchedule , Schedule, Subscriptions, ExecutionLog. No duplicate records anywhere that can possibly cause the subscription to be called once and then two separate schedules (via GUID)I rechecked and verified with the GUIDs in the logs (oh and yeah, those GUIDs, they are just not the friendliest to the eyes) :9/29/2010-12:00:19:: Creating Time based subscription notification for subscription: d1ba9af5-f7f3-4e1d-b5f2-627d2a09f5499/29/2010-12:00:19:: i INFO: Schedule 2111634e-6c12-4936-a27f-8e8d4454840a execution completed at 9/29/2010 12:00:19 PM...9/29/2010-12:00:19:: Creating Time based subscription notification for subscription: d1ba9af5-f7f3-4e1d-b5f2-627d2a09f5499/29/2010-12:00:19:: i INFO: Schedule 2111634e-6c12-4936-a27f-8e8d4454840a execution completed at 9/29/2010 12:00:19 PM. |
|
|
meisalas
Starting Member
6 Posts |
Posted - 2010-09-30 : 12:38:12
|
As for the one subscription that was created and recreated, that worked well. Gah... I guess that's the way I have to go through now, delete and recreate the subscription. Problem has been going on for awhile to continue digging to some other possible solutions.Also, as a history to this subscriptions that are behaving this way, they are those that was created way in the past, that when someone tries editing in on the UI, it bombs right away with the message: "The required field StartDateTime is missing from the input structure." But the subscription works though... just can't edit it.From digging (sorry i don't remember the link anymore), it was an acknowledged bug from Microsoft, and we'd need to delete and recreate the subscription. However, after seeing that there really is an invalid datetime somehow embedded in the MatchData column of subscription (value of 0001-01-01), and replacing it with a valid value, we were able to edit and save the subscription. Apparently, this may have been the result, subscription are called twice. THANKS A LOT!!! |
|
|
|
|
|
|
|