View Complete Post
I developed an ASP.net 1.1 web application that is written in VS2203 and I am using Reporting Services 2005 to render some reports in PDF Format. My problem was it is working fine in local (XP) and Production environment (Windows 2003 Server).fromo long back the solution was not working for my integration Server which has windows 2003 Server (1.1) and we installed the 2.0,3.5 frameworks. It is throwing an Object refernce error while render the report. Is there any permisions or something missing.
I have wasted so much time in a finding a solution and I appreciate any help in that.
I've been working on my first asp.net application and for the most part it's been pretty smooth. Right now I'm having trouble getting reporting services working under SQL Server 2005. I developed the site with Visual Studio 2010 and didn't think about any of the .Net 4.0 compatibility issues that have arisen. I'm having no problems with the site communicating with SQL Server 2005 for the regular database stuff. The only problem I'm having is with setting up Reporting Services. I have the .Net 4.0 framework installed on the server, however Reporting Services is still using 2.x. I'm not sure if this is a problem with SSRS or with IIS. When i go to localhost/Reports it's reading my web.config for my application and throwing an error: "Parser Error Message: Unrecognized attribute 'targetFramework'." This is referring to a line in my web.config where targetFramework is set to 4.0.
Software that I'm using:
Custom report items in SQL Server 2005 Reporting Services address your needs for custom reports without the pain of doing it from scratch.
MSDN Magazine October 2006
Reporting has always been one of the dark arts of development. The tools typically seem to do just enough to get you to a certain point, then leave you to find workarounds to solve more complex issues.
MSDN Magazine July 2006
Many applications require some degree of integration with a reporting tool. A good solution, SQL ServerT Reporting Services 2005, provides Web-based reports and can be integrated into both WindowsÃÂ® Forms and Web-based applications.
MSDN Magazine June 2006