On May 17, 4:04 pm, Rocks <R...@discussions.microsoft.com> wrote:
> The new pool setup successfully, but didn't fix the problem. I've reset IIS
> several times, too.
>
> I was hoping to avoid a reinstall. :(
>
> David
>
> "EMartinez" wrote:
> > On May 16, 9:12 pm, Rocks <R...@discussions.microsoft.com> wrote:
> > > I've been running SQL RS 2005 for a few months, when now it's quit working.
> > > It's hard to determine when, but here's my story.
>
> > > I'm running one server with Windows 2003 SP2, Exchange 2003, and SQL 2005.
> > > All coexists pretty well - with enough RAM!
>
> > > I was trying to fix a non-working Exchange OMA folder (requires 1.1), and
> > > uninstalled ASP.net 2.0 - oops. So, I reinstalled, but no amount of telling
> > > the Reports and ReportServer folders to use v2 makes any difference.
> > > aspreg_iis -lk shows the whole reporting webiste using the correct version.
> > > Actually, if I set them to use 1.1, I get a server error, as would be
> > > expected. But, when they're configured to use 2, I get my login prompt, and
> > > immediately get a plain ol' "page cannot be displayed." This is when I try to
> > > access folders that have long worked well, and now don't - very frustrating.
>
> > > Reporting Services configuration shows all green checkboxes. I can't find
> > > any anomolies in the Event log, or in RS' logs either, but I could be missing
> > > something.
>
> > > I've confirmed that my ReportServerURL is configured properly, and that my
> > > IIS settings are correct. I haven't seen anything to this effect, but should
> > > I create a new application pool for RS? It's using the Default.
>
> > > Any suggestions would be appreciated!
>
> > If you are using both ASP.NET 1.1xxx and ASP.NET 2.0, then a new
> > application pool would be a good idea (and is a web good practice). If
> > this is not the case, have you tried resetting IIS? This might clear
> > it up. If you have, and you don't get any other suggestions, I would
> > suggest reinstalling SSRS. Sorry that I could not be of greater
> > assistance.
>
> > Regards,
>
> > Enrique Martinez
> > Sr. Software Consultant

"EMartinez" wrote:

> On May 17, 4:04 pm, Rocks <R...@discussions.microsoft.com> wrote:
> > The new pool setup successfully, but didn't fix the problem. I've reset IIS
> > several times, too.
> >
> > I was hoping to avoid a reinstall. :(
> >
> > David
> >
> > "EMartinez" wrote:
> > > On May 16, 9:12 pm, Rocks <R...@discussions.microsoft.com> wrote:
> > > > I've been running SQL RS 2005 for a few months, when now it's quit working.
> > > > It's hard to determine when, but here's my story.
> >
> > > > I'm running one server with Windows 2003 SP2, Exchange 2003, and SQL 2005.
> > > > All coexists pretty well - with enough RAM!
> >
> > > > I was trying to fix a non-working Exchange OMA folder (requires 1.1), and
> > > > uninstalled ASP.net 2.0 - oops. So, I reinstalled, but no amount of telling
> > > > the Reports and ReportServer folders to use v2 makes any difference.
> > > > aspreg_iis -lk shows the whole reporting webiste using the correct version.
> > > > Actually, if I set them to use 1.1, I get a server error, as would be
> > > > expected. But, when they're configured to use 2, I get my login prompt, and
> > > > immediately get a plain ol' "page cannot be displayed." This is when I try to
> > > > access folders that have long worked well, and now don't - very frustrating.
> >
> > > > Reporting Services configuration shows all green checkboxes. I can't find
> > > > any anomolies in the Event log, or in RS' logs either, but I could be missing
> > > > something.
> >
> > > > I've confirmed that my ReportServerURL is configured properly, and that my
> > > > IIS settings are correct. I haven't seen anything to this effect, but should
> > > > I create a new application pool for RS? It's using the Default.
> >
> > > > Any suggestions would be appreciated!
> >
> > > If you are using both ASP.NET 1.1xxx and ASP.NET 2.0, then a new
> > > application pool would be a good idea (and is a web good practice). If
> > > this is not the case, have you tried resetting IIS? This might clear
> > > it up. If you have, and you don't get any other suggestions, I would
> > > suggest reinstalling SSRS. Sorry that I could not be of greater
> > > assistance.
> >
> > > Regards,
> >
> > > Enrique Martinez
> > > Sr. Software Consultant
>
>
> This link might be helpful.
> http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/3ff5e1a8562f067/f84fd2caceb47a09?lnk=st&q=page+cannot+be+displayed+reporting+services&rnum=2#f84fd2caceb47a09
>
> Regards,
>
> Enrique Martinez
> Sr. Software Consultant
>