Reports Break

I have found I have a problem with my reporting Services 2005 that I am not
sure I understand.
I Have reports in development and they are about to go live, so when I am
working on other things they may not be getting requested for a week or two.
But what happens is when I try to run the reports they give all these
bizarre error messages. If I then go back into the Project where I created
the reports and redeploy them it fixes the problem.
Does anyone have any ideas why I have this problem and how I might go about
troubleshooting it?Not only have I not seen this myself but I haven't really seen anything like
this in the newsgroup. Once you deploy it should work consistently unless
something changes somewhere. For instance, someone messes with IIS behind
the scenes. I have been working with RS since the beta of RS 2000 and I have
never had to redeploy to fix a report.
Perhaps you have something odd going on with your networking. For instance
your DNS. I suggest posting some of the error messages the next time this
happens.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"MrsLeigh" <MrsLeigh@.discussions.microsoft.com> wrote in message
news:03AE1783-140B-4145-A517-9998965400A8@.microsoft.com...
>I have found I have a problem with my reporting Services 2005 that I am not
> sure I understand.
> I Have reports in development and they are about to go live, so when I am
> working on other things they may not be getting requested for a week or
> two.
>
> But what happens is when I try to run the reports they give all these
> bizarre error messages. If I then go back into the Project where I
> created
> the reports and redeploy them it fixes the problem.
> Does anyone have any ideas why I have this problem and how I might go
> about
> troubleshooting it?|||I will do this next time I have an error message. Thank you.
"Bruce L-C [MVP]" wrote:
> Not only have I not seen this myself but I haven't really seen anything like
> this in the newsgroup. Once you deploy it should work consistently unless
> something changes somewhere. For instance, someone messes with IIS behind
> the scenes. I have been working with RS since the beta of RS 2000 and I have
> never had to redeploy to fix a report.
> Perhaps you have something odd going on with your networking. For instance
> your DNS. I suggest posting some of the error messages the next time this
> happens.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "MrsLeigh" <MrsLeigh@.discussions.microsoft.com> wrote in message
> news:03AE1783-140B-4145-A517-9998965400A8@.microsoft.com...
> >I have found I have a problem with my reporting Services 2005 that I am not
> > sure I understand.
> >
> > I Have reports in development and they are about to go live, so when I am
> > working on other things they may not be getting requested for a week or
> > two.
> >
> >
> > But what happens is when I try to run the reports they give all these
> > bizarre error messages. If I then go back into the Project where I
> > created
> > the reports and redeploy them it fixes the problem.
> >
> > Does anyone have any ideas why I have this problem and how I might go
> > about
> > troubleshooting it?
>
>|||I did figure out WHY my reports were breaking now. But I am hoping for some
suggestions coming from this:
My scenario is that I have been creating Shared Data Sources for my database
connections. And I wasn't thinking about the fact that these sources
actually are shared. When I named the datasources I was using the same name
but perhaps 2 different actual databases when I was in different projects.
So when I was deploying the projects when I built them the current project's
datasource was what got put on the Reporting Services Server.
This brings me to my question:
What kind of suggestions does anyone have on how they go about dealing with
Shared Data Sources? Obviously now I know I have to think twice when I
create them. But I am just looking for any best practises anyone might have
to suggest.
"MrsLeigh" wrote:
> I have found I have a problem with my reporting Services 2005 that I am not
> sure I understand.
> I Have reports in development and they are about to go live, so when I am
> working on other things they may not be getting requested for a week or two.
>
> But what happens is when I try to run the reports they give all these
> bizarre error messages. If I then go back into the Project where I created
> the reports and redeploy them it fixes the problem.
> Does anyone have any ideas why I have this problem and how I might go about
> troubleshooting it?