February 6, 2009 at 7:14 am
I think you're probably correct about removing IIS. Unfortunately for me, there are 3 websites and 20 virtual directories on this production box. Many of the sites/virtuals were created and configured by vendors to support their products we purchased. What's worse is the box is in use 21 hours (5:00 AM to 2:00 AM) every day. So I basically have a 3-hour window to rebuild IIS, unless I can gain more access to it on the weekend.
Yesterday I removed SSRS completely and reinstalled it. For anyone who didn't know, it is possible to remove and reinstall SSRS without affecting the database at all. Just use the Change option in Add/Remove Programs. It didn't even ask for a reboot. Unfortunately, when I reinstalled it, SP2 wasn't applied so the newly installed Report Server doesn't match the version of the existing Report Server database. Hopefully I can fix that this weekend by reinstalling SP2.
Question: If I export the IIS configuration to an XML file, remove and reinstall IIS, and then import the configuration again, do you think the problem will resurface? Is the problem in the configuration itself?
February 6, 2009 at 8:50 am
This could cause you problem but this is the last I know because I am one of the few people who knows how to get IIS 6 in both 32bits and 64bits going. Se if you can apply what is in the text below.
Give ASP.NET, IIS_WPG and NETWORK SERVICE users authorization into the security properties of all the folders related to the project and gave them full control authorization to these folders for Reporting services.
Kind regards,
Gift Peddie
February 6, 2009 at 11:47 am
I finally found the problem!!!!
The Default Web Site was set for anonymous access only. I added Integrated Windows authentication by checking the box and then told it to apply the changes to the Reports and Report Server virtual directories.
I don't know how I missed this one, as many times as I went over everyhthing. But it's working now. Hallelujah!!
Thanks for all of your suggestions.
February 6, 2009 at 11:55 am
I had assumed it is the first thing you will check before posting I glad to see your problem is fixed.
The reason Windows authentication is required for SSRS 2005 and 2000, that is the reason you must run Vista Ultimate or Business to run SSRS.
Kind regards,
Gift Peddie
February 9, 2009 at 12:12 pm
Oh, and there was one other tiny detail. Keep Alive was turned off on the default web site. Turning that on made it work.
February 9, 2009 at 12:40 pm
You almost lost me but you are talking about adjusting the Session Property from the default value of 20 minutes to something higher. That is what keep alive is adjusting the session property in Asp.net by default it is 20 minutes.
http://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx
Kind regards,
Gift Peddie
February 9, 2009 at 2:17 pm
I'm talking about the Enable HTTP Keep-Alives checkbox on the Web Site tab of the Default Web Site. The box was unchecked, and I checked it. And the Report Manager started working.
February 9, 2009 at 2:22 pm
That property is enabled by default if it was off then it maybe related to your IIS 6 configuration when you started using it.
Kind regards,
Gift Peddie
Viewing 8 posts - 16 through 22 (of 22 total)
You must be logged in to reply to this topic. Login to reply