MicrosoftReportViewer

I can get a report viewer working on local server using the control "MicrosoftReportViewer"-- but not at DASP.
I see there is a property named "reportServer URL" that is defaulted to localhost/reportserver .....
do I need to point this somewhere else??
---Jim

 

The Msft report viewer does work locally but...
Do you just need good reports you can create locally?
If so, do you have a recent Msft Office suite?
One more, the Crystal Reports addin for VS runs locally.
(I'm just trying to think of what may work best for you locally...)

 

thanks for the terrific replies.

i reviewed the post re the ReportViewer and havefew questions ... (I am using VS2008 freebie)

/////////////////



The report viewer control is a control that came with VS.NET 2005 that enables you to embed reports directly into your ASP.NET pages. The control can be configured to operate in 2 modes, local mode and remote mode.


When local mode is used, the control processes and renders report using the built-in engine and the report definition files on the web server.


When remote mode is used, the control will display report that is processed by the reporting service engine.


In this post, we will focus on how to configure report viewer control to display reports housed in Reporting Service 2005.


/////////////////


still not clear about the diference in the local and remote modes. Where is the "built in engine"? Do you first have to, first,"create the report", and then put it somewhere and then eneble others to view it?


I am assuming i want the "remote mode" -- here it seems (guessing) that the report is requested, prepared on the spot, and then passed back to the page. this means i dont have to prepare anything -- so this sounds better.


Can you provide a rationale as to why you would use one way ot the other?


---jim

 

I read more on this on other forums -----


All I want to do is to have a page titled "summary report". when the user goes to this page, he sees the current summary based on all entries to the db in a nice neat format. I really dont want to have to pre-prepare a report and then give all access to my pre-prepared report. I want to use the pagefunctionality (available from MSReportViewer)to save the report to a localfile in a .pdf form.


Also, do I need to purchase the Report Server add-on to allow this to happen?


---Jim

 

i thought i'd give it another go with the MicrosoftReportViewer control. I just placedthe controlon the contentPlaceholder of my form. The I selected the "design a new report" from the task menu. I could have selected "Use Server report" but i didnt (it thought this meant that i was using the local report mode??). Next I followed the directions and created a report (report1.rdlc) inmy project folder. I ran this locally and all is well -- nice looking report. Then I uploaded all to the DASP site and ran it and got the error below. Seems to be looking for some stuff on the DASP site. Does this suggest that all i got to do is sign up for the DASP report service?


---jim



Server Error in '/' Application.


Configuration Error


Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Source Error:

Code:

Line 57: 				<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
Line 58: 				<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
Line 59: 				<add assembly="Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
Line 60: 				<add assembly="Microsoft.ReportViewer.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>
Line 61: 			[b]

Source File: E:\web\gvopscom000\htdocs\web.config Line: 59

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.

Code:

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Version Information:Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433 <!--
[FileNotFoundException]: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
[ConfigurationErrorsException]: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (E:\web\gvopscom000\htdocs\web.config line 59)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
at System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai)
at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
at System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName)
at System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed)
at System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories)
at System.Web.Compilation.BuildManager.CompileCodeDirectories()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
[HttpException]: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (E:\web\gvopscom000\htdocs\web.config line 59)
at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)
[HttpException]: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (E:\web\gvopscom000\htdocs\web.config line 59)
at System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
at System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
--><!--
This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using <customErrors mode="Off"/>. Consider using <customErrors mode="On"/> or <customErrors mode="RemoteOnly"/> in production environments.-->

 

I have no idea but would suggest you open a support ticket and ask, if you already copied your /bin/ files to the server.
Salute,
Mark

 

thanks anyway!! In fact, I bought the Report Service ($5/mo) and retried the app ---- still failed for the same above reason!!


---Jim

 

Keep me posted.
I'm seriously behind in everything right now, except baby sitting...
But I'm willing to install the service and run some tests if it will help.
All the best,
Mark

 

thanks --


went to Helpdesk -- they said DASP did not support ReportViewer (RV)Version 9. So dug around the web and found MS's site to download RV. This downloaded an .exe which i ran and it said it was installed OK. There was a "Version 2007" a "Version 1.0" and a "Version 2008". I assumed the Version 2008 was actually Version 9.0 so I downloaded Version 2007.


Redid theweb page w/o modifying Vis Studio 2008 -- however, I can see by the web.config that is still used the same Version 9.0 --- must be something else I have to do ....


It would seem that adding ReportVersion 9.0 at DASP should be a priority -- since us'es who have bought into MS's hype re VS2008 woud like to just use the VS2008 w/o all the fuss!


---Jim

 

HeHe...yur a hoot.
Thanks for the update bro.

 

thanks for the feedback ..


Can you suggest an alternative approach. The ReportViewer is dirt simple to use from my limited experience with VS2008 and makes pretty reports for e-mail and printing in .pdf. I also attempted to use the Crystal Stuff but the learning curve was much steeper. I paid for the "report Server" capability at DASP but really dont know what to do with that.


The Help Desk suggested going to ReportViewer 8.0 but I couldnt figure out how to disengage version 9.0 and re-engage Version 8.0 ...


---Jim

 

thanks for the idea Bruce. Makes since to me ---


I researched the web for an older version of ReportViewer and found one associated with VS2005 -- Version=8.0.50727.817


---- However, this doesnt seem to be the one you have there .... see error below.


Any ideas??


---Jim



Server Error in '/' Application.


Configuration Error


Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=8.0.50727.817, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Source Error:

Code:

Line 57: 				<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
Line 58: 				<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
Line 59: 				<add assembly="Microsoft.ReportViewer.WebForms, Version=8.0.50727.817, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
Line 60: 				<add assembly="Microsoft.ReportViewer.Common, Version=8.0.50727.817, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>
Line 61: 			[b]

Source File: E:\web\gvopscom000\htdocs\web.config Line: 59

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.ReportViewer.WebForms, Version=8.0.50727.817, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.

Code:

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Version Information:Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433 <!--
[FileNotFoundException]: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=8.0.50727.817, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
[ConfigurationErrorsException]: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=8.0.50727.817, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (E:\web\gvopscom000\htdocs\web.config line 59)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
at System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai)
at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
at System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName)
at System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed)
at System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories)
at System.Web.Compilation.BuildManager.CompileCodeDirectories()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
[HttpException]: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=8.0.50727.817, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (E:\web\gvopscom000\htdocs\web.config line 59)
at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)
[HttpException]: Could not load file or assembly 'Microsoft.ReportViewer.WebForms, Version=8.0.50727.817, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (E:\web\gvopscom000\htdocs\web.config line 59)
at System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
at System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
--><!--
This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using <customErrors mode="Off"/>. Consider using <customErrors mode="On"/> or <customErrors mode="RemoteOnly"/> in production environments.-->

 

Jek and I discussed this through a different thread ... I thought I'd post my back and forth with Discount here as well.


Ifought with this for days and finally gave up because I had an alternative.


If anyone get s this solved I'd really like to hear about it ... this is a really important part of a bigger effort I'm about to slide into. I added the Discount discssuion here so that anyone else having trouble can raise the issue with them so they know that 'the demand has surfaced'.


The final message to discount was as follows (I don't have their final response but it was basically a reiteration of that below).
I believe you specify Visual Studio 2008 is supported, do you not?
I believe that the Report Viewer control is a standard part of VS 2008. But it also has a 'deployment sdk' and a separate service pack.
The problem appears to be for those of us developing in VS2008 and deploying to a DASP hosted site ... the 2005 (version 8) and 2008 (version 9) 'trip' over each other.
I also can't get my app to publish with the Report Viewer control Version 8.0 (VS2005) now that I've moved to NET 3.5 even when I remove all references to the Version 9.0 control.
I'll bet a dollar that the Version 9.0 control got registered in whatever you use for the GAC, even though you don?t expressly install it.
While I understand that this raises a testing and deployment problem I would suggest, respectfully, that you can't claim to support VS 2008 when it breaks using built in controls.
My, previously working, VS 2005 site no longer works now that I have moved it to VS 2008. If you actually don't support NET 3.5 AND/OR VS2008 then my apologies I misunderstood ... I'll have to find a workaround or move my site.
If you do actually support them ... then you have a bug that can be easily enough fixed.
</o>
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: March-06-08 11:56 AM
To: [email protected]
Subject: [TECH-DASP #1141130]: Report Services / VS 2008
</o>
Dear Customer,
</o>
Report viewer control version 9 is not a standard windows dll is not currently installed due to lack of demand.
I'll forward your request to our engineer and we will definitely consider making it available if more demand surfaces.
Thank you for your understanding.

 

I hope you'll be able to support report viewer version the earliest time possible. thanks in advance

 

I hope you'll be able to support report viewer version 9 the soonest time possible.

 

Please let me know when you will have Report Viewer 9 (VS2008) installed.


Steve

"Why does it always do what I tell it...not what I want it to?"

 

can you provide a staus of the Version 9.0 of the ReportViewer on DASP?


else provideme with some workaround to get reports going on my site. The ReportViewer reports look great on my local server --- really odd why its so hard to geta standard out-of-the-box Microsoft VS2008 control running at DASP!!


---jim

 

It's on my short list right now, just after I get this video on ASP.NET 2.0 Membership/Roles Provider done.
Salute,
Mark

 

i am confused (but not unusual) -- all i want to do is to pull in the "MicrosoftReportViewer" control from the Toolbox builtin to the VS2008 web designer. I can make it work fine on my local server and see reports exactly like the one you demo-ed. There are also the CrystalReports controls with VS2008 -- but i am aware that DASP doesnt support this feature. When I tried this before, it said the MicrosoftReportViewer 9.00 assembly was missing. I am now assuming that it has been added???

I signed up for the MS SQL SSRS feature of DASP -- but am not sure i need this.

To create a web-viewable report :::
Can I just
(1) create a report page on my development site locally
(2) load up the MicrosoftReportViewer control and fix up the report in my VS2008webdesignerlocally
(3) copy the site to DASP and have this work when the user logs in through DASP.

Is it that easy or do i have to follow the rather complex instructions related to the Report Server provided by DASP?

Thank you mucho for the effort to assist with this !!

---Jim

 

jek said...
i am confused (but not unusual) -- all i want to do is to pull in the "MicrosoftReportViewer" control from the Toolbox builtin to the VS2008 web designer. I can make it work fine on my local server and see reports exactly like the one you demo-ed. There are also the CrystalReports controls with VS2008 -- but i am aware that DASP doesnt support this feature. When I tried this before, it said the MicrosoftReportViewer 9.00 assembly was missing. I am now assuming that it has been added???

I signed up for the MS SQL SSRS feature of DASP -- but am not sure i need this.

To create a web-viewable report :::
Can I just
(1) create a report page on my development site locally
(2) load up the MicrosoftReportViewer control and fix up the report in my VS2008webdesignerlocally
(3) copy the site to DASP and have this work when the user logs in through DASP.

Is it that easy or do i have to follow the rather complex instructions related to the Report Server provided by DASP?

Thank you mucho for the effort to assist with this !!

---Jim
You do not need MS SQL SSRS if you want to use the ReportViewer Control in LOCAL MODE.

You do need MS SQL SSRS if you want to use the ReportViewer Control in REMOTE MODE.

Local mode works well for less complex reports.

If you want to use a report on stored on the Report server of your DASP account, it can only work with data stored on your DASP account database.

HTH![/quote]

Steve

"Why does it always do what I tell it...not what I want it to?"

 

Hi,
I'm still going through the MSDN White Papers but I did create one of the reports in VS2008.
From what I can tell so far the Report Designer is a better choice.
However MSDN does have some technical articles about using the reports with an application.

So yes, my next step will be to illustrate how to do the same from VS2008.
As to which DASP servers have access to version 9, I'll have to check with the crew.
I did everything on the IIS7 WS2008 server.

Can you give me a few tips about how you'll create and use them? It will help...
And how you will share the reports, i.e. user logins.

The reports I created yesterday use "secure" connections that are saved into the reports.
I have no idea how they are encrypted but the reports assured me the information was secure.
Salute,
Mark

 

I haven't had time to look at it but I wanted to thank all concerned for you responsiveness in publishing this control once it was determined the issues it was causing were more wide spread than first blush.


Now I just have to move all that work back out of DASP SSRS 2005 ... oh well

 

I just spent a couple of hours with it and everything went very well.

1. To remote Discountasp.netServer from Vista Home Premium SP1
2. SQL Server 2005 RS, which got fed from my local SQL Server 2005
3. Microsoft SQL Server Reporting Services Version 9.00.3215.00

In the past I created a gazillion reports with Crystal Reports and SQL Server 2000.
If you're used toCR these will be no problem at all, even Matrix reports.


I was able to create the data and test reports with no problem.
Even installed the Report Builder on Vista from the remote Report Server. Very nice feature.


I'm attaching a screen shotI just took from one of the reports.
In the screen shot I've clicked to open the File Format combo...
XML, CSV, TIFF, PDF, Web Archive and Excel.


I'll create some videos tomorrow.
Salute,
Mark

 

I'm still working through the MSDN White Papers on this but wanted to post something that may be helpful...


Converting RDL and RDLC Files<!---->
http://msdn2.microsoft.com/en-us/library/ms252109.aspx