February 13, 2008 at 7:37 am
Has anyone seen this?
We have a subscription for a report which sends out once every month to a specific user. Every time we turn around, jobs get added in SSMS named with mystery names like '1AD0B4AA-E3E8-4651-8269-7A9515F8EA9E'. When we investigate, the jobs are all running the same report. The one report we have the subscription for.
Last month, the end user got three emails because we had three jobs in SSMS. I deleted the extras, named the one job with a user friendly title so someone wouldn't accidently delete it and today when I looked, another mystery job running the report appeared, even though it isn't time for the next report run yet.
I really don't have time to go in every couple of weeks and clean up these jobs that come out of nowhere, so I'd like to locate the source of the problem and stop it now.
We're using 2005, SP1. Any thoughts or comments would be appreciated.
February 13, 2008 at 7:59 am
This may or may not be your problem, but I'm guessing it is. When you rename the job it "breaks" the connection to Reporting Services. RS uses the GUID (job name) for it's subscription. So when you chnage it, RS must recreate it, thus giving you another instance of that subscription.
Your renamed subscription still works, but you just can't edit it through the RS interface.
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. SelburgFebruary 13, 2008 at 9:37 am
Oh, that's a horrible thought!
I want to be able to see these jobs and know what each one does without opening them up and finding the report ID info. I hate the idea that I can't use user-friendly names for them to make administration easy.
BLEARGH!
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply