Report Manager returning a 500 error

Hi,
So here's what happened. I had successfully deployed an ASP.Net
application, had it running and using SQL 2K5 reporting services just fine.
I rolled out an update to the application, and included an UpdatePanel in a
few of the pages (nothing related to the reports, page-wise).
First snag I ran into was that the Report server (and manager) could not
load the System.web.extensions dll, that was deployed with my project. Both
report services virtual directories are sub-directories to my application on
Win 2K3, so it was inheriting that part of the web.config. I put a <remove>
section in both reporting services web.configs to remove the HttpModule
section named 'ScriptModule', added in to use ASP.NET Ajax v 1.0.
After doing that, the report server virtual directory comes up, so I can
basically browse the server, see the models, and even run the reports that
already exist etc, but can't use the ReportManager web app. The report
manager says that the report server could not be contacted, and to make sure
it is on. In the logs, it shows that a 500-server error was received, and
obviously ends there.
Any advice anyone has on what the problem might be, I'd appreciate it.
Thanks for the help,
PeteHello Pete,
I understand that you have an application to install the reporting services
and you could not get the report manager work.
According to the error state that the report manager could not find the
report server, you may check the following things:
1. RSWebApplication.config file under the C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportManager folder. You may check the
following element:
<UI>
<ReportServerUrl>http://yourservername/your application virtual dic
name/reportserver</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
2. rsreportserver.config file under the C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer
<UrlRoot>http://yourservername/your application virtual dic
name/reportserver</UrlRoot>
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Thanks for the quick response. I tried what you suggested below and it
still didn't fix the problem. Here's a bit more information about the setup.
The DB, Report Server, and IIS for the application all run on the same box,
which is running Windows Server 2K3. I have it setup that the Website is
called <appname> and then it has two virtual directories underneath that
website for ReportServer and ReportManager. Since it is an intranet
application, you access it by going to http://machinename, which defaults to
the one website on it. If you go to http://machinename/ReportManager, you
can access the GUI to manage reports, models, etc. (at least before it was
broken). Going to http://machinename/ReportServer gives you the website
browsing aspect of it, but not the GUI you'd expect.
In the config files you had me check for ReportManager, the <ReportServUrl>
field was empty, but the ReportServer virtual directory field was filled in,
with the proper name of the virtual directory. The <UrlRoot> you mentioned
was already filled in and point to the same URL mentioned above for the
ReportServer itself.
On another note, as I had only been using the ASP.NET AJAX extensions in one
location, I removed that UpdatePanel, and all ajax related items in my
application-specific web.config file, and the Report Manager worked again
immediately. So, I'm thinking there is some direct connection to the two
that I can't find out that is causing it to crash.
Again, any help would be very much appreciated. I don't really think just
avoiding the ASP.NET Ajax extensions is a viable option in the long term.
Thanks,
Pete|||Hello Pete,
I would like to know if you put the whole url for the report server in the
<ReportServUrl> and remove the virtual directory value,
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Yes, I put the full path of the reportServer URl into that location, and
removed the reference to the ReportServerVirtual directory. That
unfortunately did not fix the problem. Any other suggestions would be
appreciated.
Thanks,
Pete
"Wei Lu [MSFT]" wrote:
> Hello Pete,
> I would like to know if you put the whole url for the report server in the
> <ReportServUrl> and remove the virtual directory value,
>
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Pete,
Could you please let me get the report server error log?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Unfortunately I can't get you the client's server log - it is on a
restricted internal machine, and they don't allow internet access from it or
connection of external drives.
In order to provide for a temporary fix, I went ahead and un-did my ASP.NET
Ajax changes in the web.config file and it started working again. It is far
from an ideal solution, but I didn't have time to work through it any more.
If you have any other solutions I'd like to hear them, as I'd like to improve
the UI of our application using ajax at some point in the future.
Thanks,
Pete
"Wei Lu [MSFT]" wrote:
> Hi ,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello Pete,
If you have time to get the reportserver error log, you may send it to me.
By default, the log file is located at \Microsoft SQL Server\<SQL Server
Instance>\Reporting Services\LogFiles.
Otherwise, I may lack of information to troubleshoot the error.
Hope it helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.