I have fresh installed SQL Server Reporting Services 2012 on a Sharepoint 2010 box (SP1+february 2012 Cumulative update - latest CU as of now). SSRS 2012 architecture is new, as Reporting Services Sharepoint integrated is now a service application instead of a separate instance as it was on SSRS 2008 R2. Reporting Services configuration manager is no longer used as everything is now configured through Sharepoint Central Admin - Reporting Services Service App Management. The issue is: I can no longer get Sql Server Data Tools (formerly BIDS) to deploy reports to a sharepoint library, it seems SSDT report server projects still rely on the old architecture, requiring a report server url as one of the deploy properties, which no longer exists due to the new ssrs 2012 sharepoint service app approach... Whenever I try to deploy a report, a reporting services login dialog box shows up, no matter which credentials you provide, the report never gets deployed. Please advise, I need to use Visual Studio 2010 as my development environment to deploy reports to sharepoint libraries, but all that has to be achieved having ssrs 2012 sharepoint integrated as the destination deploy environment.

I haven't solved this issue yet, but let me post about more findings after further digging, so that the Microsoft experts have more information to get me an answer. SSRS 2012 behaves different from SSRS 2008 R2, concerning sharepoint integrated mode. Let me enumerate the changes: SSRS 2012 integrating with Sharepoint 2010 differences compared SSRS 2008 R2 integration: 1) No SSRS SQL Server instance of type sharepoint integrated is used anymore. 2) No SSRS configuration manager is used anymore. 3) No Reporting Services Integration option used anymore, under Sharepoint Admin Site. In summary, whenever you think of how to come up with the solution of this issue, forget completely about these 3 points I mentioned. Now, let me talk about my findings: In SSRS 2012, sharepoint takes care of all SSRS web service behavior. Reporting Services is now a service application after you install 2 options from sql server 2012 install media: Reporting Services SharePoint and Reporting Services add-in for SharePoint 2010 Products. Both are under SHARED COMPONENTS (no new database instance as it was in SSRS 2008 R2). Now, specifically about the problem that originated this post: Deploy does not work from a report server project in Visual Studio 2010 Shell (now named SQL Server Data Tools, formerly BIDS), because of the deploy properties TargetServerURL, TargetReportFolder, etc). There is a vast amount of information on msdn and on independent blogs on how to fill these properties correctly, but all for 2008 R2 version only. What about now, for SSRS 2012, with the new architecture? I tried using different TargetServerURL project properties, and could come up with some conclusions: Sharepoint integrating with SSRS 2012 does not "expose" a /ReportServer URL anymore, as it was before. In a SSRS 2008 R2 integrated mode configuration, the url http://servername/ReportServer responded with the root directory for folder listings, indicating reportserver was listening... Now in SSRS 2012 I can only get a 404 not found page when trying to use http://servername/ReportServer. The only way to get SSRS 2012 to respond was to use the following syntax: http://<site>/_vti_bin/reportserver. The behavior of this reponse is the same as it was in 2008 R2. I figured that out from this post: http://www.duncansutcliffe.com/?p=22. Let me quote what Duncan Sutcliffe says: "Theres a problem with SQL Server 2012 SSRS running in integrated mode, though. It runs as a SharePoint managed service so it doesnt have its own web service URL any more." Okay, then I tried setting TargetServerURL to "http://<site>/_vti_bin/reportserver", apparently it got reporting services to answer, but the another error came up: The path of the item '/http://ServerName/site/folderlibray' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. ---> System.UriFormatException: Invalid URI: The format of the URI could not be determined. I'm stuck at this point, still need advice from Microsoft specialists. By the way, it intrigues me as no one came up with such an issue like this one yet, after doing a lot of research throughtout blogs, forums and msdn.

So far it appears that the architecture is geared toward the BISM if you opt for SharePoint integration. The only thing I could successfully deploy was the tabular model. Yes, Reporting Services is available in SharePoint integrated mode along with the BISM. But it looks like there is an expectation that Report Server reports and and associated data will either be created by the end user on the SharePoint site (By clicking on New Document and selecting from the dropdown) or, if the developer creates a Report Server project, he/she will have to deploy it somewhere else and then upload the items into a SharePoint library. Somebody please tell me that this is not the case... because I could find no way to deploy from Data Tools to SharePoint. By the way, RenatoFX, a lot was said about this (and what might be coming problems) here

The good news is that Report Builder 3 can consume the tabular model from the new Analysis Services in 2012. I was happy to see that work.

The issue is: I can no longer get Sql Server Data Tools (formerly BIDS) to deploy reports to a sharepoint library, it seems SSDT report server projects still rely on the old architecture, requiring a report server url as one of the deploy properties, which no longer exists due to the new ssrs 2012 sharepoint service app approach... Whenever I try to deploy a report, a reporting services login dialog box shows up, no matter which credentials you provide, the report never gets deployed. Hi RenatoFX, If you installed SQL Server Data Tools(SSDT) on Windows Vista or Windows Server 2008, please right-click on SSDT and select "Run as administrator". There are some articles about puslish a report to SharePoint library for your reference. Please see: http://technet.microsoft.com/en-us/library/ms155802.aspx http://technet.microsoft.com/en-us/library/bb283155.aspx For more information about what's new in Reporting Services 2012, please see: http://technet.microsoft.com/en-us/library/ms170438.aspx Regards, Bin LongBin Long TechNet Community Support

Hi Bin Long, I installed SQL Server Data Tools (SSDT) on a Windows 7 machine. Besides that, I have logged in as a domain administrator account, with full permissions on local machine as well as on sharepoint destination library. You provided articles which I already have gone through reading, but the documentation does not match behavior in real life. If you have the time, I would like you to try and setup a pure sharepoint 2010 + sql server 2012 reporting services integration, then try to deploy a simple rdl report file from an SSDT report project to a sharepoint library, which accepts files of content type report. As simple as that. What worked flawlessly in SQL Server 2008 R2 just does not work anymore. It seems to me Microsoft has left loose ends this time, I can cite 2 evidences: 1) SSRS report parameters documentation: http://msdn.microsoft.com/en-us/library/ms155391.aspx, if you look closely and compare the differences between SQL Server 2012 and SQL Server 2008 R2 (there's a dropdown list choice you can select which version the documentation refers to), Microsoft admits that the report server url for sharepoint integrated mode has changed COMPLETELY. What was before in SQL Server 2008 R2, was the format " http://server/reportserver?/Sales/Northwest/Employee Sales Report&rs:Command=Render&EmployeeID=1234 Now as the MSDN documentation states, the new format in SQL Server 2012 is: http://myspsite/subsite/_vti_bin/reportserver?http://myspsite/subsite/AdventureWorks 2008R2/Employee_Sales_Summary_2008R2.rdl&ReportMonth=3&ReportYear=2008 What I mean by this evidence, is that, just like report server url changed between the two SQL Server versions, the TargetServerURL deployment property of a report server project in SSDT also should demand a change in behavior, because it is simply NOT WORKING in SSRS 2012. Either SSDT should account for the new architecture of sharepoint integrated SSRS 2012, or sharepoint integrated SSRS 2012 should "expose" or "emulate" the behavior existing in SSRS 2008 R2, so it would not break deploy funcionality on a report server project with destination sharepoint library ssrs 2012 integrated. 2) This documentation http://technet.microsoft.com/en-us/library/ee635898.aspx about deployment and version support, supposedly refers to SQL Server 2012, but strangely enough it says "You can use the SQL Server 2008 R2 version of SQL Server Data Tools (SSDT) to open, modify, preview, save, and deploy both SQL Server 2008 and SQL Server 2008 R2 Reporting Services reports". SSDT is the new name of BIDS, it exists only on SQL Server 2012, what type of naming mess is MSDN talking about when it says "SQL Server 2008 R2 version of SSDT?"... Besides that, the article says it's about SQL Server 2012, but the content of it does not mention SQL Server 2012 (and the existence of compatibility) at all. I will only hope in future CUs or SPs on either SQL Server 2012 or Sharepoint that Microsoft ties up those loose ends...

RenatoFX, I agree. Documentation is no help. I could not successfully deploy to SharePoint by following documentation instructions.

Bin Long, What you have posted (links) are instructions that DO NOT work. I have tried it. And, no, permissions is not an issue for me, either.

One month later... were you able to make it work? I have the same problem on my test server. I have everything installed on the same server (SharePoint, SSRS and SSDT), I am admin of all and everything. When I try to deploy a data source or a report, I have an error "The specified folder is not valid. Specify a value for the TargetReportItemFolder property in the deployment settings. If you are deploying to a SharePoint site, the location must be a fully-qualified URL to the target library or folder". I saw inside some documentation that deploying from SSDT may require that the server is specified inside the Internet Explorer's "Trusted sites". The server was already inside the "Local intranet" part, I tried to move it to "Trusted sites" without luck. I am not new to SSRS and I'm used to deploy (SSRS 2005, 2008, 2008R2, SharePoint Integrated or Native), but I must say I'm a little lost with the deployment from SSDT 2012 to SSRS 2012 SharePoint Integrated, as nothing seems to work...

I figured this one out....seems like the TargetServerURL property is the important one to tell the server whether its in native or sharepoint integrated mode. So if native, you put the URL to the reportserver. If sharepoint integrated, you put in the URL to the sharepoint site where the report server feature is enabled. NOT the _vti_bin/reportserver. So in my case it is http://servername/sites/bi That works. The docs actually say that...just not that obviousThanks -howardm

Sorry bi-king, that's not the case. What you described applies to SSRS 2008 R2. This whole thread is about SSRS 2012 instances to be configured to work as sharepoint 2010 integrated. Specifically in this scenario (Sharepoint 2010+SSRS 2012), Microsoft's development tool (formerly named BIDS, now named SQL Server Data Tools) cannot deploy a report to a sharepoint library. To keep SSDT report deployment functionality working, the target MUST BE a sharepoint box with an SSRS 2008 R2 instance configured as sharepoint-integrated mode. Downgrade if you will, just as I did... Until when?

I just tested a quick deployment from SSDT to SharePoint site and worked just fine. Can you provide some information as to what your deployment properties look like? Here is what I have setup for mine as an example: TargetServerURL: http://<servername/ TargetDatasetFolder: blank, nothing here, not using TargetDataSourceFolder: http://<servername>/shared documents/Data Sources TargetReportFolder: http://<servername>/shared documents/ReportForums TaregetReportPartFolder: blank, nothing here, not using TargetServerVersion: SQL Server 2008 R2 or later Just make sure you have the URL paths all set and the slashes in the right spots and you should be just fine.

I just tested a quick deployment from SSDT to SharePoint site and worked just fine. Can you provide some information as to what your deployment properties look like? Here is what I have setup for mine as an example: TargetServerURL: http://<servername/ TargetDatasetFolder: blank, nothing here, not using TargetDataSourceFolder: http://<servername>/shared documents/Data Sources TargetReportFolder: http://<servername>/shared documents/ReportForums TaregetReportPartFolder: blank, nothing here, not using TargetServerVersion: SQL Server 2008 R2 or later Just make sure you have the URL paths all set and the slashes in the right spots and you should be just fine.

I don't understand, it works today... I don't know what I didn't wrong the other day. Between the two tests, I configured it for my native report server, so I don't remember exactly the configuration I put last time, but it's working now.

Yes, SSDT can indeed deploy a report to a sharepoint site sucessfully. The deployment properties are exactly as you described, accurate to the documentation. BUT, check out sharepoint configuration. As of Sharepoint 2010 SP1+february 2012 Cumulative update, configured to work SOLELY with the new SSRS 2012 architecture (remember **1) No SSRS SQL Server instance of type sharepoint integrated is used anymore, 2) No SSRS configuration manager is used anymore, 3) No Reporting Services Integration option used anymore, under Sharepoint Admin Site **) it does NOT deploy. SSRS 2012 does not respond to URL http://servername/ReportServer, as it did on SSRS 2008 R2. Correct me if I'm wrong, but your sharepoint environment is set up to use an SSRS 2008 R2 sharepoint integrated instance installed on the sharepoint box. In this case, deployment from SSDT works. The purpose for starting this thread was to discuss a scenario where SSRS 2008 R2 is not present AT ALL in any kind of configuration. SSRS 2012 only please, no downgrade allowed for coming up with the solution. :-)

My setup was strictly related to the subject of the thread, SQL Server 2008 R2 was in no way used in this, just SQL 2012. This definitely works with 2012 and you should not be using a ReportServer URL reference when deploying to SharePoint, always a SharePoint site. I am aware that SSRS is now a Shared Service application just like Excel Services, PerformancePoint Services, etc. The deployment does work just fine as described. If you are having issues then you need to post the Deployment settings you have setup in your project along with the SharePoint site information you are trying to reference.

I was having the same issues and getting errors when deploying from VS2010 to Sharepoint 2010. The thing that fixed it for me was, as Dan says, making sure the slashes are in the right place. In particular the one at the end of: TargetServerURL: http://<servername/ Also, there seem to be occasions where you might receive an error on first try, but it will deploy fine if you try again.