Stop SQL Reporting Server Hijacking /Reports - sql-server

How do you stop SQL server reporting services from hijacking the /reports virtual folder on ALL websites on the server it's installed on. Have just discovered that all the websites on the box with the reporting server on (its a dev box), have /Reports overridden by the reporting services manager. How do I turn this off?
Have tried stopping the service, disabling it in the config file, all to no avail (the service is still hijacking the url, you just get a "service unavailable" error instead of the report manager). Short of uninstalling reporting services, is there a way to switch this off?

I had the exact same problem - very annoying when your own web application uses a /Reports folder, couldn't understand why I was getting "File or Directory Not Found" errors on IIS when navigating to my reports page.
Phil is correct the easiest solution (using SQL Server 2008 R2) is to run Reporting Services Configuration Manager, connect to your local instance and change the Virtual Directory under "Report Manager URL" to something more unique (I used "/ReportingServices").
This fixed the problem and my /Reports folder was restored to my own web app!

Assuming you are using SQL Server 2008 R2 reporting services you can do this via the Reporting Services Configuration Manager.
But consider telling us the version of reporting services.

You can also change the port it listens to via the Reporting Services Configuration Manager.
I have set mine to 8080 instead of 80, and it has solved the problem for me.

Related

SSAS Cube deployment error

I was going to process the cube deployment and found the error.
I changed the target server name from 'localhost' to this,and tried different way but in vain.
Here is the snap from my SSMS
You may have multiple issues going on but the first and foremost is you do NOT deploy SSAS Multidimensional [MDX] models to a SQL Database Engine Instance!
Unless you have a very odd configuration ATI-PC\MSSQLSERVER should point to the default MS SQL Server Database Engine Instance NOT an SSAS MDX instance!
The SSMS screen shot you show is for the local host connection you show is for a Database Engine with SQL Server Authentication (SA), which I would assume the instance is called MSSQLSERVER which is the default instance name.
1) What is your SSAS instance name?
2) Does your windows account have permissions? SSAS doesn't allow for SQL server authentication so it must be windows authentication.
3) Is SQL Browser running?
4) Have you configured SQL Browser to allow for the protocols and to allow connections from both Localhost and ATI-PC(InstanceName)?
to connect to Analysis Services Change the Server Type. When first launching SSMS you can do that via changing server type and then modifying the server name to the appropriate name.
If your SSMS is already open you can select "Connect" drop down and choose Analysis Services.
Check on your SQL Browser Configuration by Launching "SQL Server (Version) Configuration Manager" then step through the different areas as far as how to configure it is somewhat self explanatory and because you are deploying an AdeventureWorks cube I would surmise that the configuration would be earlier in you tutorial you are working on.
I am sure that you have 'SQL Browser' service running in services.msc. Still I doubt your account which you logged in has access to SSAS and also to connect to that underlying SQL Server. Try checking both for the access, if you selected deploy as service account check that account has access in SSAS. If still you have issues trying checking the eventvwr if you are getting any more errors. If it is development box try recycling SSAS services and try deploying?

deploying reports to report server

I configured SSRS 2008 on a remote server.
I can access the report manager from my local machine using http://SERVER_NAME/Reports_INSTANCE_NAME
problem is that when I try to deploy a report from BIDS, I get the "reporting services login" dialog box that asks me for user and password. I try my AD user and it doesnt work.
I already added myself to all possible roles, including System Administrator.
I saw online that the problem maybe with the IIS website that must be configured to allow anonymous access. That's fine, but where can I configure that since SSRS2008 doesn't create the websites on IIS anymore (also read that online) and I don't seem to have this possibility using the Reports Service Configuration Manager
Take a look at the link below...it's in reference to 2008 CTP, but there are still some items to check in your setup...
http://blogs.msdn.com/b/lukaszp/archive/2008/03/26/solving-the-reporting-services-login-issue-in-the-february-ctp-of-sql-server-2008.aspx
Similar issue / resolution here as well...
Repeated Reporting Services Login issue when deploying through BIDS to a remote server
In your report configuration file, try removing the RSWIndowsNegotiate from the Authentication tag:
<Authentication>
<AuthenticationTypes>
<RSWindowsNegotiate />
</AuthenticationTypes>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>

Reporting Service SQL Server 2008 not deploying

I have two pairs of servers, one web server one DB server in each pair. I installed SQL Server 2008 in my DB servers and everything works, but reporting services only works in one.
In one of my servers, reporting service refuses to deploy my reports to http://xx.xx.xx.xx/ReportServer and says "Unable to deploy the server check to make sure target url is correct..." However it works fine in the other server.
What are the possible conditions for a reporting service to refuse deployment??
Does it require IIS to deploy? Are there some sort of port 80 restrictions on one of the servers making it unable to deploy?
Any ideas??
check your rights on the server you can't deploy to.
also, go onto the server where you can't deploy to and double check the url for the web service in reporting services configuration

sql reporting server virtual directory

I have sql reporting services installed in my system.
I can access it through the url http://localhost/Reports_SQLEXPRESS/
But the strange thing is I am not able to view this virtual directory in my IIS management console. I need to set the permissions for this virtual directory, but it cannot be found.
What might be the problem?
i assume that you are using reporting service 2008 look at this two links
http://www.networkworld.com/community/node/33694
http://msdn.microsoft.com/en-us/library/aa337491.aspx
Reconfigure your report server with Reporting Service Configuration Manager.

New to SSRS Configuration

I am trying to install and configure SSRS on SQL 2005.
When I click Reporting Services Configuration, I get a message saying
No report servers were found on the specified machine - Details
Invalid namespace.
How can I resolve this?
You don't "configure SSRS on SQL Server 2005", as such.
It's a component that you choose at install time (like Analysis Services, Integration Services etc). For SSRS, then you require IIS as a prerequsite and it won't be installed if IIS is not present.
The error itself is 100% correct if SSRS is not installed...
Is it actually installed?
Edit:
Just got this on one of my feeds: KB 960374 that describes the exact error above
Quite simple. Place your disc with SQL in and run setup. Add features to your existing instance and select Reporting Services. Once installed it would have created 2 databases on your SQL Server named ReportServer and ReportServerTempDB
Open the services configuration and you should be prompted to connect to an instance of Reporting Services.
If you see this screen then you are ready to go.
--Read this only if you might have questions to ask
Setup a service account for Network Service (save the .snk key and it will create your IIS entries etc. If you don't have IIS then upgrade your OS to a compatible version. It can be installed via Add or Remove Windows Features)
Make sure your new database is selected in the Database section. If not, then follow the screen to add it
Open the Report Manager URL and click on the link. (You may need to be in as an administrator)
When you want to deploy reports, simply update your solution properties with the TargetURL pointing to the Web Service URL that is available after setting up the Service Account)
Ask anything further if you need the guidance. I've done this to about 5 servers in the past month already, so I know what can go wrong.
Cheers,

Resources