We are using SQL Server Reporting Services 2008 to build reports. We're accessing the reports trough the Webservice (ReportExecution2005.asmx), render them to html to embed them in an aspx page. Everything works quite well.
Only on the computer of one developer images aren't rendering. When copying the url of the image and pasting it in the browser, it says:
Reporting Services Error
The stream cannot be found. The stream identifier that is provided to an operation cannot be located in the report server database. (rsStreamNotFound)
The guy is running Windows Vista, on my own Windows 7 environment everything works. With SSRS 2005 I had the same problem on Windows 7, but it was resolved by installing SSRS 2008.
Any ideas?
This is an ancient question but I stumbled across the following article which describes (in great detail) what a particular development group found during their research.
Avoiding Reporting Services ‘StreamNotFound’ Exception when Viewing Multiple Instances of the Same Report
In the end, here is what solved their problem:
"... [we] discovered you can disable session cookies (in the ReportServer.dbo.ConfigurationInfo table) which (after an IISReset) indeed fixed the problem entirely."
Related
We are in the process of upgrading servers from Windows 2003 to Windows 2008 R2 and from SQL 2005 to SQL 2008 R2. Our applications are all web based. For the most part we have been successful in the transition, but our report viewer seems to be causing some issue. We have gone through the process of adding the handler definition to the system.webserver container in the web.config to make it work with IIS 7.5. The reports render correctly with parameters and without, and are able to be exported without issue. Our problem is that when we click on the Print icon to print the report we are presented with a Windows Security dialog box asking for a username and password. The context of the prompt is my web server.
I've found a lot of documentation on getting the username/password prompt when linking directly to a report or when initially rendering the report in the report viewer, but I have not been able to find anything about the username/password prompt occurring solely when the print icon is clicked. I feel like this is probably some silly configuration setting somewhere but I am unable to find it.
Thanks for your help!
EDIT:
Let me also note that this is pointing to an SSRS server and not to embeded RDLC reports in the application itself. Looking through fiddler, the 401 is for:
GET /Reserved.ReportViewerWebControl.axd?ReportSession=qqmrflihqpiu4c45hoqlxt45&ControlID=f029b0c1-7a9e-4a61-9750-4a53d5eb0087&Culture=1033&UICulture=1033&ReportStack=1&OpType=PrintHtml
So as it turns out Report Viewer version 8 is not compatible with SSRS 2008 R2. The resolutin to this is to upgrade the viewer. I upgraded mine to version 10 and it works flawlessly. I hope this helps someone else
Here are the details:
We have a dynamic data website using Telerik Open access, hosted through IIS 6. This application has been running fine with no issues in production. Recently, we added two new tables to the SQL database. These were added to the Telerik Open Access model and when tested in Visual Studio 2012 there was never any issues and ran brilliantly.
Then we published to production and when I browse to the application directly through IIS 6 to ensure it runs we get the error - "this program cannot display the webpage".
So we removed those two tables from the Telerik Open Access model and re-published and the Application runs great. So we re added the tables again and the same error comes from IIS.
This makes no sense as IIS normally gives an intelligible error. Why would IIS have an issue with two additional entities added to the Model but Visual Studio does not?
It looks like the model is somehow cached.
You could try restarting the IIS in order to avoid the issue with the new entities in your model.
We had a metadata file associated with the model, and it was not configured correctly. When we fixed it and re-deployed, it worked great. The strange thing is that Visual Studio ignored the error and it took publishing it to error on us. Strange.
I don't have the code in front of me right now (but will in an hour or so), but suspect that the solution is very simple so I'll post a general description of the problem and update it later:
Problem:
A site built on ASP.NET works fine when browsing it through Visual Studio, but when attempting to connect via browser, it complains about looking for a default page (I can update later with the exact error).
Details:
Our development team is trying to set up a (VERY) simple wiki server for our internal project using SEWEN WIKI, a wiki server based on Wikiplex. None of us are web developers.
I'm 99% positive that it's something as simple as creating a index.html or something as an entry point for the browser, but I'll admit my domain knowledge here is about 0.
IIS has been updated to 7.5 (min required is 7), and ASP.NET has been upgraded past 4 (the required version). The operating system is Windows 2008 Server, and the wiki is developed in Visual Studio 2010.
If anybody has any ideas, I'd love to know. Thanks!
Assuming that you have ASP.NET enabled on your server as #Patrick suggests in the comments, it's possible that you need to configure a Default Document as #ScottSelby suggests.
Here is documentation on this topic from Microsoft: Configure the List of Default Documents in IIS 7
I've illustrated this below:
In the Features View of IIS, click Default Document:
In Default Document, ensure that you have your designated page, commonly default.aspx:
I have installed the Visual Studio 2008 sp1 Report Viewer Redistributable on the web server. I had to download it from microsoft, because the location I've seen other people post does not exist on my install of visual studio. I downloaded the one that is located here: http://www.microsoft.com/downloads/details.aspx?familyid=BB196D5D-76C2-4A0E-9458-267D22B6AAC6&displaylang=en.
I think the location people say ReportViewer.exe is in, is usualy: C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\ReportViewer\ReportViewer.exe. I have Visual Studio Team Suite Development Edition 2008 and the v2.0 directory under SDK does not exist. That may be some of my problem, I do not think so though.
I say all that to say that I can design the Microsoft Report, and I can run the page with the report viewer locally just fine. It seems to work really great, and could help out the company quite a bit.
However when I deploy to the webserver the page that host the reportviewer control will allways either say "This page does not have a precompiled..", or something like that. It usualy doesn't say anything and just sits there trying to load.
Other pages in the same website do not exhibit these symptoms. I have also successfully gotten crystal reports to display it's viewer, by installing the redistributable on the web server.
There must be something going on with one of our web servers. I finally got the report to load and it came up with an error message that said the same thing that this forum post talks about http://social.msdn.microsoft.com/Forums/en-US/vsreportcontrols/thread/b237dbab-7670-4c7a-b9af-70c5be7101d9.
I was then able to check the box that says allow precompiled site to be updatable. That fixed my issue. I now have both crystal and microsoft reports working correctly. Maybe this post will help someone else.
edit 2/18/2010 8:18am cst I thought it was fixed apparently not, as soon as I published to the web server again, the page will not load anymore. I am going to try and setup a completely new server in a virtual machine, to try and do more testing.
edit 2/19/2010 8:17am cst I spent alot of yesterday setting up a brand new virtual machine with server 2003, visual studio 2008, and sql 2005. I ran the same report page, all it has on it is the report viewer control. It still will not load. I figure there is something you have to do with IIS configuration to get it to work, since it won't load with default settings.
edit 2/19/2010 9:47am cst I have created a new web application with only the report in it, brand new web.config file. Something about my web.config file is causing the problem. This new web application is apparently working. I am now going to try and see if any new pages can be added to the previous web app at all. Maybe something is causing all new pages to not load.
edit 2/19/2010 10:12am cst Bizarrely the report sometimes loads. This happens on both the test environment, and the production environment. I did find a somewhat funny angry bug report to microsoft that explains the problem with the rdlc files compiling. That is what produces the following error:
**
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.
**
The Bug report url: http://connect.microsoft.com/VisualStudio/feedback/details/468068/rdlc-files-are-build-into-resources-during-publish-this-is-a-marker-file
The blog post url that fixes it: http://weblogs.asp.net/stephensonger/archive/2008/09/10/deploying-rdlc-files-in-local-mode-for-asp-net-applications.aspx
As you can tell, possibly you don't find it funny, but there is a bug that causes rdlc files to compile for some reason. You can also fix it by having your site be updatable, which is one of the check boxes you can check when you publish in visual studio.
edit 2/19/2010 10:51am cst My next step is to snapshot the current virtual machine, go back to the point I installed sql 2005. At that point I'll install visual studio 2010 rc and see if it exhibits the same problem.
edit 3/3/2010 9:15am cst I don't know what fixed it, but both crystal and microsoft reports have been displaying correctly for awhile now. I made no changes other than what I have mentioned here.
I'd like to set up SQL Server Reporting Services but I don't know where to start. The books out there are okay but don't seem to fit what I need to do. That is, I want to set up my ASP.NET 3.5 application to be able to view reports I create, both in a web report viewer and downloadable as PDF/Excel.
What are the basic steps to do this? Do I need IIS installed on the SQL box?
Reporting Services for SQL Server 2005 is built on top of IIS. Reporting Services for SQL Server 2008 is not, but you may still need IIS installed anyway; I seem to remember that the install process checked for IIS as a precondition.
What version of SQL Server are you using? I assume that you have a version with reporting services, but just to verify, the Express editions don't have it. SQL Server developer edition is the cheapest way to go; it's usually available on Amazon for something like $45. Developer edition has everything, but with a restricted license.
I haven't messed with reporting services much (it's on my list, but never seems to get to the top of the list). However, the 2008 version uses Visual Studio 2008 for developing reports (renamed as SQL Server Business Intelligence Development Studio). Once you have all that installed, you should be good to go.
You can access the SSRS implementation via a SOAP API.
http://msdn.microsoft.com/en-us/library/aa256607(SQL.80).aspx
This should allow you access to reports via a report viewer which you has built in means for exporting to pdf / excel etc.
Install it from the main SQL Server installer. Make sure you also install the client tools on the machine you'll be using for development.
Use Visual Studio (or BIDS) to create and deploy your reports. There are standard templates to get you started.
When you access the reports over the web, you will have the option of downloading them as PDF or Excel (no special settings or code is required)
Embedding reports in an ASPX page takes a little more work. When you get past the items above, post another question about the details (it mainly involves a couple of special controls).
The ASP.NET ReportViewer control can operarate in two modes, local or remote. In remote mode it will display reports from a SSRS server, in local mode you can add the reports directly to your visual studio project and the control will handle the rendering. This might be more suitable if you don't want to install IIS.
In my experience it is easier to create the reports in remote mode but in local mode you can use business objects as a data source.
Have a look at http://www.gotreportviewer.com, this has a good explanation and links to other resources and sample code.