Wednesday, March 21, 2012

Report Viewer

I know this is a little out of the charter for this forum however there isn't
a Visual Developer forum that fits as close to the issue I'm running into.
Report Viewer in VS2005 seems to draw a lot of its function if not base code
from SQL Reporting Services so I'm hoping that someone knows what is going on
with this report.
Setup:
Two system (Three if you count the dev machine):
SQL Server (2000) Framework 1.1
Web Server (IIS 6.0) Framework 2.0
From VS2005 dev workstation:
I set up a data source pointing to the SQL database table that I wanted to
use. Then laid out a chart. Tweeked it so that it would apear the way I
wanted it to look. Test samples of the page look great and everything works
fine. So I published it to the web server.
WEB Server:
Pulled up error due to missing components for ReportViewer on the web server
deployment, so I installed the ReportViewer tool to the web server and cleard
the web to be sure it was clean and republished.
Page now works (sorta) but the area on the page where I have the chart
displayed fails to display the graph and instead displays the following
message:
An error occurred during local report processing.
The definition of the report 'Main Report' is invalid.
The report definition is not valid. Details: Data at the root level is
invalid. Line 1, position 1.
Now I search high and low for any information on this error message but can
not find a reference that is even close to it.
Looked at all the report related code and it looks just fine. Has anyone
run into a similar issue and/or have an idea what might be causing this?
Again, everything is fine on the dev box . Just when the pubished work is
used from the web server I'm getting this.Yes, have you resolved this issue?
seandwilkins@.gmail.com|||The problem is a Framework incompatiblity. There is no resolution. Where
we've
been able to slide with legacy version of framework has been in data source
objects. I was kinda hoping there was a work around for this as we can
develope rep;orts on the 2.0 framework, but those reports don't work on the
1.1.
Core reason for this is that the reports are tightly bound to RS 2005. So
for those of us coming in to Visual Studio developement at the 2005 level, we
will either have to learn to deal with VS2003 or wait till the powers to be
place a blessing on SQL 2005.
"SeanDWilkins@.gmail.com" wrote:
> Yes, have you resolved this issue?
> seandwilkins@.gmail.com
>

No comments:

Post a Comment