all groups > sql server reporting services > march 2006 >
You're in the

sql server reporting services

group:

SQL Server 2005 Report Server Error


SQL Server 2005 Report Server Error Eliadem54
3/20/2006 10:29:26 AM
sql server reporting services:
I get the following error when I try

http:\\localhost\ReportServer
or
http:\\[servername]\ReportServer (from a remote server)

An internal error occurred on the report server. See the error log for more
details. (rsInternalError) Get Online Help
Object reference not set to an instance of an object.

It worked (almost) fine untill I changed a setting in IIS for asp.net 2.0
authentication from windows to forms, and back to windows (in the IIS manager
under the reportserver virtual site).

RE: SQL Server 2005 Report Server Error Bing Bing Yu
3/20/2006 1:16:29 PM
Did you restart IIS?

[quoted text, click to view]
RE: SQL Server 2005 Report Server Error MoranTugTom
3/22/2006 10:29:27 AM
URGENT! We are having same issue - IN PRODUCTION. We have been unable to
find out the cause or a solution so far.

Setup: Windows Server 2003, IIS 6.0 with SQL Server 2005 and Reporting
Services 2005 (we have been running successfully on RS2005 for over two
weeks).

Background: This morning at 11:20am, the server application log showed an
error "It is not possible to run two different versions of ASP.NET in the
same IIS process. Please use the IIS Administration Tool to reconfigure your
server to run the application in a separate process."

Around the same time, users began reporting that Reporting Services was
down. If they clicked on a link to a page referencing '../reportserver/',
they would get 'Directory Listing Denied, The Virtual Directory does not
allow contents to be listed.' If they attempted to access thru
ReportsManager, " Parser Error. Could not load type
'Microsoft.ReportingServices.UI.GlobalApp'." Either way, reports were down.

We tried to find out what had happenned this morning and could not find any
connection to what was going on at that time. The only leads we have as to
the cause are as follows, (1). Yesterday we deployed Dundas Charts for the
first time into production. Everything ran fine just as it had in dev. The
reports were working without issue. (2). A developer has been testing out
VS2005. He had published some projects to a test server but says never to
production. Test by the way works fine, only production is down.

Our first attempts to fix were to view the settings that were different in
our production vs dev environment. We found that in dev, the IIS website for
Reports and ReportServer were running ASP.NET 2.0. But in Production, they
were running ASP.NET 1.1.4322. In an attempt to fix, we tried to change this
to ASP.NET 2.0. Since then, Reports Manager will load. However, when you
attempt to run the report you get some scrambled headers and the error
message, "Object reference not set to an instance of an object."

Please let me know if anyone has experienced the same issues or has a
solution. Thanks!



[quoted text, click to view]
AddThis Social Bookmark Button