Reporting Services and Directory Browsing?

If I use the URL 'http://my.rportingserver.com/ReportServer', I am presented
with a list of the directory contents, as if Directory Browsing were turned
on for the directory in IIS. At the bottom of the directory listing, is an
indication that this is a Reporting Services function:
Microsoft SQL Server Reporting Services Version 9.00.1314.00
Needless to say, Directory Browsing is turned off in InetMgr. What controls
this directory listing, and can it be turned off ?
Thanks !Report manager is the front for RS. So you will see a listing inspite of
turning off directory browsing. Basically to access all the reports it is
provided if you dont want the listing to be displayed, then remove the access
rights "Read" (I think it is browse) from the configuration.
Amarnath
"RJ" wrote:
> If I use the URL 'http://my.rportingserver.com/ReportServer', I am presented
> with a list of the directory contents, as if Directory Browsing were turned
> on for the directory in IIS. At the bottom of the directory listing, is an
> indication that this is a Reporting Services function:
> Microsoft SQL Server Reporting Services Version 9.00.1314.00
> Needless to say, Directory Browsing is turned off in InetMgr. What controls
> this directory listing, and can it be turned off ?
> Thanks !

Reporting Services 2005 - Problems displaying a report via a ReportViewer control.

I have a report that displays fine in VS 2005 (in the Preview tab), and if I hit it via a URL in IE as a deployed report. However, when I embed it in a ReportViewer control for display on a web site, I get no data back for the report. I am using an Oracle database for the data source. None of the the logs in reporting services show anything wrong, there are no events in the event viewer to indicate any problems, Oracle logs also show no problems and no errors are returned to the page when the "View Report" button is clicked.

Anyone out there have a clue? I certainly don't.

Mike

The web site is executing the report viewer control with a certain (ASP.NET) user context. Most likely this account does not have any permissions to access the installation of the Oracle client software (or the Oracle client software is not installed at all on the web server).

Check this KB article for more details how to configure directory security: http://support.microsoft.com/?kbid=870668

-- Robert

|||

I thought the same thing at first, but permissions checked out fine. I found out that the problem is a rather esoteric interaction of Div and Table HTML element display characteristics during report generation (at least that's what the MSDN article says at http://msdn2.microsoft.com/en-us/library/ms252090.aspx).

The gist of it is that when you have the ReportViewer control properties set to render Asynchronously and have the height set to a '%' value (I was using 100%), the calculated height passed in the HTML is set to '0' so no report displays. You have the choice of using a fixed height and Asynchronous rendering or a percentage height and synchronous rendering.

Mike

|||

Thanks for posting your findings!

-- Robert

sql

Reporting Services - Web Service URL

I have installed SQL SERVER Katmai with default settings but for some reason I cannot access the Reporting Services. When I go to the Reporting Services Configuration I cannot configure the WebService URL. I also cannot access http://<servername>/Reports or http://<servername>/ReportServer. Can someone tell me what the problem could be?

Is the SQL Server Reporting Services Windows Service running at all?

|||

Service is running, however, I cannot get into the ReportServer through the SQL Server Management Studio or Internet Explorer. All other services are operating fine. I even checked to make sure there were no IIS sites with the same name as Reports or ReportServer.

|||

Reporting services is behaving different, in the SQL Server Configuration manager the "log on" properties tab for the "Reporting Services" says that Account settings &c are managed by the Reporting Services Configuration tool and it shows a disabled button labeled "Not Installed".

In the Surface Area Configuration tool I get an "invalid namespace" error on all 3 Reporting services items, 2x for system.management and once for sqlsac.

And the Reporting Services Configuration tool freezes when I click the WebService URL option. The Report Manager URL does work, and so does the link to the web interface, using port 8080. Trying to add or edit the entries in the "multiple identities" list under the "advanced" tab however also results in the tool freezing.

And this is using XP Pro SP2.

|||

I am on Windows XP Pro with SP2 and I don't have any issues. You can use the Web Service URL link in the RS Configuration utility to change the port. Assuming you are running on port 8080, http://localhost:8080/reportserver should respond.

|||

I am using Vista Home Premium and the Reporting Services does not work even though the others services do. My next step is to upgrade to Vista Ultimate and put Kamai on my Windows 2003 Server. I understand that there are processing that don't work on the Home editions of Vista that work on the Business editions. I will report my findings.

|||

Vista is not officially supported with the July CTP. For better experience I'd recommend you stick with Windows XP .

|||

That is right, I had already seen that http://localhost:8080/reportserver did work. But I had to dig into some .config files to find that URL, as it didn't work via the Reporting Services Configuration tool. So, I still wonder what's causing the problems I described...

|||

Is therer something else listening on the original port (probably 80)? What does netstat -no show?

|||

Sure, the standard IIS webservice. Has to be there for the installation to run smoothly.It choked a few times when I had an Apache server active there. But that's all OK now. It's not the web interface that has problems. It's SAC and Reporting Services Config.

|||

You shouldn't need IIS running at all for installation to run (in fact, it is better to turn it off if you aren't using it). Are you sure you are using the latest CTP?

Reporting Services - Web Service URL

I have installed SQL SERVER Katmai with default settings but for some reason I cannot access the Reporting Services. When I go to the Reporting Services Configuration I cannot configure the WebService URL. I also cannot access http://<servername>/Reports or http://<servername>/ReportServer. Can someone tell me what the problem could be?

Is the SQL Server Reporting Services Windows Service running at all?

|||

Service is running, however, I cannot get into the ReportServer through the SQL Server Management Studio or Internet Explorer. All other services are operating fine. I even checked to make sure there were no IIS sites with the same name as Reports or ReportServer.

|||

Reporting services is behaving different, in the SQL Server Configuration manager the "log on" properties tab for the "Reporting Services" says that Account settings &c are managed by the Reporting Services Configuration tool and it shows a disabled button labeled "Not Installed".

In the Surface Area Configuration tool I get an "invalid namespace" error on all 3 Reporting services items, 2x for system.management and once for sqlsac.

And the Reporting Services Configuration tool freezes when I click the WebService URL option. The Report Manager URL does work, and so does the link to the web interface, using port 8080. Trying to add or edit the entries in the "multiple identities" list under the "advanced" tab however also results in the tool freezing.

And this is using XP Pro SP2.

|||

I am on Windows XP Pro with SP2 and I don't have any issues. You can use the Web Service URL link in the RS Configuration utility to change the port. Assuming you are running on port 8080, http://localhost:8080/reportserver should respond.

|||

I am using Vista Home Premium and the Reporting Services does not work even though the others services do. My next step is to upgrade to Vista Ultimate and put Kamai on my Windows 2003 Server. I understand that there are processing that don't work on the Home editions of Vista that work on the Business editions. I will report my findings.

|||

Vista is not officially supported with the July CTP. For better experience I'd recommend you stick with Windows XP .

|||

That is right, I had already seen that http://localhost:8080/reportserver did work. But I had to dig into some .config files to find that URL, as it didn't work via the Reporting Services Configuration tool. So, I still wonder what's causing the problems I described...

|||

Is therer something else listening on the original port (probably 80)? What does netstat -no show?

|||

Sure, the standard IIS webservice. Has to be there for the installation to run smoothly.It choked a few times when I had an Apache server active there. But that's all OK now. It's not the web interface that has problems. It's SAC and Reporting Services Config.

|||You shouldn't need IIS running at all for installation to run (in fact, it is better to turn it off if you aren't using it). Are you sure you are using the latest CTP?

Reporting Services - Web Service URL

I have installed SQL SERVER Katmai with default settings but for some reason I cannot access the Reporting Services. When I go to the Reporting Services Configuration I cannot configure the WebService URL. I also cannot access http://<servername>/Reports or http://<servername>/ReportServer. Can someone tell me what the problem could be?

Is the SQL Server Reporting Services Windows Service running at all?

|||

Service is running, however, I cannot get into the ReportServer through the SQL Server Management Studio or Internet Explorer. All other services are operating fine. I even checked to make sure there were no IIS sites with the same name as Reports or ReportServer.

|||

Reporting services is behaving different, in the SQL Server Configuration manager the "log on" properties tab for the "Reporting Services" says that Account settings &c are managed by the Reporting Services Configuration tool and it shows a disabled button labeled "Not Installed".

In the Surface Area Configuration tool I get an "invalid namespace" error on all 3 Reporting services items, 2x for system.management and once for sqlsac.

And the Reporting Services Configuration tool freezes when I click the WebService URL option. The Report Manager URL does work, and so does the link to the web interface, using port 8080. Trying to add or edit the entries in the "multiple identities" list under the "advanced" tab however also results in the tool freezing.

And this is using XP Pro SP2.

|||

I am on Windows XP Pro with SP2 and I don't have any issues. You can use the Web Service URL link in the RS Configuration utility to change the port. Assuming you are running on port 8080, http://localhost:8080/reportserver should respond.

|||

I am using Vista Home Premium and the Reporting Services does not work even though the others services do. My next step is to upgrade to Vista Ultimate and put Kamai on my Windows 2003 Server. I understand that there are processing that don't work on the Home editions of Vista that work on the Business editions. I will report my findings.

|||

Vista is not officially supported with the July CTP. For better experience I'd recommend you stick with Windows XP .

|||

That is right, I had already seen that http://localhost:8080/reportserver did work. But I had to dig into some .config files to find that URL, as it didn't work via the Reporting Services Configuration tool. So, I still wonder what's causing the problems I described...

|||

Is therer something else listening on the original port (probably 80)? What does netstat -no show?

|||

Sure, the standard IIS webservice. Has to be there for the installation to run smoothly.It choked a few times when I had an Apache server active there. But that's all OK now. It's not the web interface that has problems. It's SAC and Reporting Services Config.

|||You shouldn't need IIS running at all for installation to run (in fact, it is better to turn it off if you aren't using it). Are you sure you are using the latest CTP?

Reporting Services - Web Service URL

I have installed SQL SERVER Katmai with default settings but for some reason I cannot access the Reporting Services. When I go to the Reporting Services Configuration I cannot configure the WebService URL. I also cannot access http://<servername>/Reports or http://<servername>/ReportServer. Can someone tell me what the problem could be?

Is the SQL Server Reporting Services Windows Service running at all?

|||

Service is running, however, I cannot get into the ReportServer through the SQL Server Management Studio or Internet Explorer. All other services are operating fine. I even checked to make sure there were no IIS sites with the same name as Reports or ReportServer.

|||

Reporting services is behaving different, in the SQL Server Configuration manager the "log on" properties tab for the "Reporting Services" says that Account settings &c are managed by the Reporting Services Configuration tool and it shows a disabled button labeled "Not Installed".

In the Surface Area Configuration tool I get an "invalid namespace" error on all 3 Reporting services items, 2x for system.management and once for sqlsac.

And the Reporting Services Configuration tool freezes when I click the WebService URL option. The Report Manager URL does work, and so does the link to the web interface, using port 8080. Trying to add or edit the entries in the "multiple identities" list under the "advanced" tab however also results in the tool freezing.

And this is using XP Pro SP2.

|||

I am on Windows XP Pro with SP2 and I don't have any issues. You can use the Web Service URL link in the RS Configuration utility to change the port. Assuming you are running on port 8080, http://localhost:8080/reportserver should respond.

|||

I am using Vista Home Premium and the Reporting Services does not work even though the others services do. My next step is to upgrade to Vista Ultimate and put Kamai on my Windows 2003 Server. I understand that there are processing that don't work on the Home editions of Vista that work on the Business editions. I will report my findings.

|||

Vista is not officially supported with the July CTP. For better experience I'd recommend you stick with Windows XP .

|||

That is right, I had already seen that http://localhost:8080/reportserver did work. But I had to dig into some .config files to find that URL, as it didn't work via the Reporting Services Configuration tool. So, I still wonder what's causing the problems I described...

|||

Is therer something else listening on the original port (probably 80)? What does netstat -no show?

|||

Sure, the standard IIS webservice. Has to be there for the installation to run smoothly.It choked a few times when I had an Apache server active there. But that's all OK now. It's not the web interface that has problems. It's SAC and Reporting Services Config.

|||You shouldn't need IIS running at all for installation to run (in fact, it is better to turn it off if you aren't using it). Are you sure you are using the latest CTP?sql