SQL Server 2012 - reporting services - scale-out-deployment

I am facing an issue which is related to a scale out deployment. I am deploying a FIM reporting based on System Center and I have 2 sql servers in this scenario.
Now the problem is that Reporting services configuration manager (from sql1) says that the scale out deployment has been established. Sql1 is joined and sql2 is waiting to join. I don't know why the servers has been appeared under the scale out deployment
because I don't want to create the scale out deployment.
So how can I remove the scale out deployment without breaking anything?
Also if I look at the Reporting services configuration manager from sql2 the scale out deployment panel is empty like it should be.

Hi 2xTsei,
According to your description, two report server instances have been configured to a scale-out deployment, while you haven’t performed this configuration.
In Reporting Services, a report server scale-out deployment is two or more report server instances that share a single report server database. To finish this configuration, we should use Reporting Services Configuration tool to connect to each report server
to the shared database and join a new report server instance. So the scale-out deployment shouldn’t be configured automatically. It’s likely that someone has configured this deployment who can access those two instances.
Reference:
How to: Configure a Report Server Scale-Out Deployment (Reporting Services Configuration)
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support
Hi and thanks for your reply.
That is a little bit weird because I am 100% sure that we didn't manually configured scale out deployment. I need to inspect this more.

Similar Messages

SQL 2012 SP1 Enterprise (SSRS in SharePoint mode): Reporting Services scale-out deployment is not supported in this edition of Reporting Services

Hello,
SSRS in SharePoint mode is driving me insane.
We are recreating a SharePoint 2013 (SP1) farm in a test environment with the following set-up:
2 SP Web FrontEnds
2 SP Application Servers
1 SQL Server
At both SP APP Servers, we installed SSRS (SQL 2012 Enterprise w/ SP1) in SP integrated mode.
We managed to start the SSRS SP service at the first SP APP Server. However when we try to start it on the second APP Server, we get the following error:
"Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot
be started on this server unless it is stopped on all other servers in the farm. "
Now I can't stress this enough: This is a SQL Server 2012 SP1 Enterprise. This is the image we got from our MSDN subscription. There is no mistake here.
Could someone please advise why SP might think this version of SSRS is not the correct one?
Thanks in advance for your help.
Regards,
P.

Hello,
I'm afraid that is not it.
After a long, frustrating and strenuous investigation and troubleshooting, we found the problem.
The problem is the current ISO for SQL Server 2012 Enterprise SP1 (x64) found at MSDN. Bear in mind that we downloaded this ISO from MSDN about a month ago.
As soon as we recreated the environment using the ISO for SQL Server 2012 Enterprise SP2 (x64) found at MSDN, everything worked as expected -- and that includes running more than one SSRS in SharePoint mode.
Also bear in mind that we tried updating the SQL SP1 install with SP2 and subsequent cumulative updates but that never fixed the problem.
There is something fundamentally wrong with that ISO with SP1 slipstreamed in it that no matter the subsequent updates installed, SSRS in SharePoint mode fails to work properly on a multi-server environment. We went as far as SP2 with CU3 and nothing seemed
to fix the problem. And yes, we also performed manual updates to the SSRS and PowerPivot SharePoint MSI add-ins.
I am shocked and distraught to find out that I lost hours of work due to a dodgy ISO image.
Regards,
P.

SSRS in SharePoint Mode: Reporting Services scale-out deployment is not supported in this edition of Reporting Services [not true]

Hello,
We are experiencing some issues with SharePoint 2013 which is driving me insane.
We have a deployment with two SQL Servers (HA groups) and four SharePoint servers: 2 Application servers, and 2 Web FrontEnd servers.
We installed SSRS for SharePoint in both application servers. The disc I have used is the MSDN image of SQL Enterprise 2012 w/ SP2.
ISO name: en_sql_server_2012_enterprise_edition_with_service_pack_2_x64_dvd_4685849.iso
MD5: 003e14c55fa648ad15f8be1e2439bd06
The installation completes without any problems. We can start the SSRS SharePoint Service in the first application server without any issues. However when we try to start the second one, we get the following error:
Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the sql reporting services service in the farm. The SQL Server Reporting Services cannot be started on
this server unless it is stopped on all other servers in the farm.
Now I am at a loss here. As I mentioned, we have used an image of SQL Server Enterprise. This is the same image we used on other environment, which worked as expected (we got no such error).
I have included the text related to the correlation error from the SP logs below.
Has anyone ever seen this issue before? Very, very strange!
Regards,
P.
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=9.742 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 6t8h High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.23, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Web Controls 88wu High [Forced due to logging gap, Original Level: Verbose] SPGridView.OnRowCreated() - Row.RowType={0}, .RowState={1}, .RowIndex={2}, .DataItemIndex={3} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General af4yd High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.28, Original Level: Verbose] TenantAppEtag record requested but there is no sitesubscription or tenantId for site {0} so we will use the WebApp Id for the cache. 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Asp Runtime aj1kp High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.43 OWSTIMER.EXE (0x1F10) 0x0B40 SharePoint Foundation Health abire Medium Failed to Sql Query data XEvent collector on sql-01. The error is Object reference not set to an instance of an object.
01/29/2015 14:13:26.51 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 7034 Critical An attempt to start/stop instance of service Microsoft SQL Server Reporting Services Shared Service on server SPAP-01 did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.40, Original Level: Verbose] SQL connection time: 0.0821 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88b9 High [Forced due to logging gap, Original Level: Verbose] Determining if the current user is a SharePoint Farm Administrator 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject ReportingWebServiceInstance. Version: 1118292 Ensure: False, HashCode: 52212853, Id: 5a4058b9-2ecd-421e-b9ae-818bbc57c8c6, Stack: at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.57, Original Level: Verbose] SQL connection time: 0.0965 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88ch High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.84, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 8nca Medium Application error when access /_admin/Server.aspx, Error=Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.87 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Runtime tkau Unexpected System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.89 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,2 agb9s,9 b4ly,309 8xqz,331 8nca,15 tkau,8 ajlz0 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48)). Execution Time=712.2145 6f83e49c-cc03-d049-90f4-81439b542cf8

Hi Wynn,
I appreciate your attempt to address my concerns, but even your reply seems to ignore the fact that I have not only provided the name of the ISO, but the MD5 checksum of the ISO as well. Also this is the first time I am being asked to double-check the version
of SSRS. The first reply I got to my query simply disregarded the version mismatch.
As per your request, I have checked under the folder you have specified (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices\LogFiles), but unfortunately there are no files under this folder in neither of my two application
servers.
We only have logfiles under C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS
Is there a way I can turn those logs on?
In the meantime, we run the SQL Server Discovery tool and I have attached the summary for you to see that it finds the Enterprise Edition of SQL Server:
Final result: Passed
Exit code (Decimal): 0
Start time: 2015-01-29 15:17:44
End time: 2015-01-29 15:17:56
Requested action: RunDiscovery
Machine Properties:
Machine name: SP-AP-02
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2012 Management Tools - Basic 1033 Enterprise Edition 11.2.5058.0 No Yes
SQL Server 2012 Reporting Services - SharePoint 11.2.5058.0 No Yes
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation edition:
User Input Settings:
ACTION: RunDiscovery
CONFIGURATIONFILE:
ENU: true
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
QUIET: false
QUIETSIMPLE: false
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150129_151743\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
The \Setup Bootstrap\Log folder also has several log files that indicates the version of SQL Server that has been installed. For instance here is an entry of the Detail.txt file:
(01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : CreateSKUCookie succeeded, new checksum is 195 bytes.
(01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : Updated skuCheckSumInfo -> daysLeft=0 sqlEdition='ENTERPRISE' (0x6B9471A8) fileTimeInstalled=0 timeBombValue=0 editionType='Enterprise Edition' edition='Enterprise Edition' writeEditionStrings='True' checkSum=195bytes
(01) 2015-01-28 19:10:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
I hope this help while we don't have any logfiles in the folder you asked me to look into. Please advise me as in how to proceed if logfiles must be generated.
Regards,
P.

Sharepoint 2013 SSRS Interaction with Sql Server 2012 Reporting Services connecting to Sql Server 2008 R2 database

Hi
I'm working on upgrading sharepoint 2010 to sharepoint 2013 with sql server 2008 r2. I've ran into some problems but have been able to get a test farm upgraded. However to run SSRS 2013 it seems Sql Server 2012 Reporting Services are required. Upgrading
to a full sql server 2012 database isn't an option. I know that sql server 2012 reporting services can use sql server 2008 r2 as a catalog and content database so I was wondering could this be a workaround? Importantly would I need a separate machine/virtual
machine to host sql server 2012 reporting services? or could it live on the sql server 2008 r2 machine? Any pointers appreciated. Thanks Dan

Remember that SSRS must be deployed on the SharePoint server. Having said that, yes you can install SSRS 2012 SP1 on a server running SQL 2008 R2. And yes, you can use 2008 R2 as your Database Engine server while SSRS 2012 SP1 runs on the SharePoint server.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Share Data Source between multiple report projects in Microsoft SQL Server 2012 Reporting Services

I have a reports solution in 2012 which contains multiple report projects one each for target deployment folder and we use TFS 2012 for report deployment.
We have a template project which has a bunch of template reports and all the datasources used in different reports.
When I develop a report, I cannot "Preview" in TFS but, for deploy this used to work fine util the reports solution was in TFS 2010 & Visual Studio 2008 R2. Since we moved to TFS 2012 & SSRS 2012 not being able to deploy till I create all
the necessary datasources for each project and now all the developers complaining that they cannot develop reports in TFS itself as they cannot preview (this problem was existing previously) and now not being able to deploy as it errors for each report "Could
not find specified rds file". I tried messing around with the .rptproj file DataSources tag that did not help either by modifying it like below.
<DataSources>
<ProjectItem>
<Name>DB.rds</Name>
<FullPath>Template\Data Source\DB.rds</FullPath>
</ProjectItem>
</DataSources>
Is there a way I could share a Data Source between multiple projects in Microsoft SQL Server 2012 Reporting Services?
Thanks in advance.............
Ione

Hi ione721,
According to your description, you want to create a shared data source which works for multiple projects. Right?
In Reporting Services, A shared data source is a set of data source connection properties that can be referenced by multiple reports, models, and data-driven subscriptions that run on a Reporting Services report server. It must be within one project.
We can't specify one data source working for multple projects. In this scenario, we suggest you put those reports into one project. Otherwise you can only create one data source for each project.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

SQL Server 2012 Reporting services Report Builder ClickOnce in SharePoint integrated mode

Hi
I've installed SSRS 2012 in Integrated Mode with SharePoint 2013.
I've created RS Application, I have the Content types for Report Builder Report but when I try to create a new Report Builder Report from a document library (using ribbon) it try to lauch the following url
http://sp2013/bi/_layouts/15/ReportServer/RSAction.aspx?RSAction=ReportBuilder&FileUrl=http://sp2013/_layouts/15/ReportServer/rs.rsapplication&SaveLocation=http%3A%2F%2Fsp2013%2Fbi%2FDocuments&Source=http%3A%2F%2Fsp2013%2Fbi%2FDocuments%2FForms%2FAllItems%2Easpx
which gives an 404 Not found error
I've installed Report Builder 3.0 as standalone because from SQL installation I didn't get an Report Builder
What else should I do ?
I've noticed that ReportBuilder_3.....application is in webservices folder of sharepoint
Please help
Sorin Sandu

Hi Sorin,
SQL Server 2012 Reporting Services (SSRS) includes stand-alone and ClickOnce versions of Report Builder. The ClickOnce version can be used with Reporting Services installed in native or SharePoint integrated mode. For more information about how to start
Report Builder, please see:
http://msdn.microsoft.com/en-us/library/ms159221(v=sql.110).aspx
Reference:
SharePoint 2010 – SQL 2012 Reporting Services
SharePoint 2010 - SQL 2012 Reporting Services Part 2
Hope this helps.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

SHAREPOINT 2013 WITH SQL SERVER 2012 REPORTING SERVICES - NOT WORKING

The SQL 2012 with SP1 is installed but the Reporting Services are not working and not able to connect the Sharepoint with it.
i also TRIED TO install THE ADD-ON (rsSharePoint.msi) but it doesn't connect and show the Sharepoint Mode and cannot connect the Reporting services.
If I install the Reporting Native feature then the reporting service config displays the Instance else doesn't show and connect to the sql server.
But I am able to access the Configuration manager and TCP/IP are enabled.
I have installed SQL 2012 and Sharepoint 2013. Please revert soon.
Tks - Vinay

Reporting Service
http://msdn.microsoft.com/en-us/library/jj219068.aspx
http://blogs.msdn.com/b/biblog/archive/2012/12/04/installing-and-configuring-sql-reporting-services-on-sharepoint-2013.aspx
http://blogs.msdn.com/b/psssql/archive/2011/02/18/sharepoint-adventures-setting-up-reporting-services-with-sharepoint-integration.aspx
http://dinesql.blogspot.in/2010/06/configuring-reporting-services-2008-r2_07.html
http://www.codeproject.com/Articles/355461/Dynamically-Pointing-to-Shared-Data-Sources-on-SQL
http://www.heysharepoint.com/problems-with-sql-2012-reporting-services/
http://andrewcbancroft.com/2012/06/30/troubleshooting-sql-server-2012-reporting-services-and-sharepoint-2010-integration-part-1/
Please find the helping URL
Thanks
Jaison A
http://infomoss.blogspot.in

SAP NetWeaver BI with Microsoft SQL Server 2012 Reporting Services using XMLA

I am currently implementing SAP BW and am trying to connect the Microsoft SQL Server 2012 Reporting Services product. I am able to connect to SAP BW but there is one problem when i click on Query Designer after adding a DataSet the screen just displays the dialog prompt saying '' NO CUBES WERE FOUND. VERIFY THAT YOU HAVE SELECTED A VALID CATALOG''.
The advanced information depicts the following:

Hi Raunak T,
Just a very basic question from my end:
I believe that "Microsoft SQL server Report Builder" is the 3rd party which uses MDX as interface.
Have you set the property using OLE DB for OLAP in your queries?
BR
Prabhith

SQL Server 2012 Reporting Services, Report Manager - Page not found

Hi all,
I am working on migrating reports to a new server so we can upgrade to a new machine and to SQL Server 2012 SP2. The machine is up and running on Windows Server 2012 and I have installed SQL Server EE 2012 SP2. I have imported the three databases
from 2008R2
* Report Server
* ReportServer TempDB
* RSSubscribers
I have re-applied the encryption keys and I was thinking that everything was good to go until I went to try and manage the subscriptions on a report. I select a report, use the drop arrow to get to manage
and then try to select any of the options such as subscriptions and I get a "Page Not Found Error"
If I take the URL and paste it in another browser, putting the previous server name in, it works fine. So, the URL works fine... I have no idea as to what I should do to figure out the problem. I am considering rebuilding the whole install
just to see if that would fix it.
Thanks

Hi SqlDude,
According to your description, you have bind SSL to a Reporting Services URL Reservation. Now you find in your Report Manager, the Subscription page still start with "http://". Right?
In this scenario, we need to change setting in rsreportserver.config file. Go to rsreportserver.config in "\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer". Find <Add Key="SecureConnectionLevel" Value="0"/>.
Change the value into "3".
Acceptable values are:
3 Most secure—Use SSL for absolutely everything.
2 Secure—Use SSL for rendering and methods that pass credentials but don't insist on it for all SOAP calls.
1 Basic Security—Accepts http but rejects any calls that might be involved in the passing of credentials.
0 Least Secure—Don't use SSL at all.
Besides, if you want to submit a feedback to Microsoft, please feel free to submit
your situation on our product to the following link:
https://connect.microsoft.com/SQLServer/Feedback.
If you have any other questions, please feel free to ask.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SQL Server 2012 Reporting Services Report Manager using non-HTTPS URLs on part of site

For potential ease of understanding, I am seeing the same issue as this person
here.
Currently, my site is successfully using HTTPS in all areas of the /Reports site, with a single exception. If you drill down to a report and go to "Manage", the following links are all http://, not https://:
Parameters
Data Sources
Subscriptions
Processing Options
Cache Refresh Options
Report History
Snapshot Options
Security
These remain regardless of the configuration combinations I enter in Reporting Services Configuration Manager. I'm not sure what makes this part of Report Manager special. Even if I only enable https in the Report Manager URL settings, these links all stay
as http (port 80). I can find no references in config files to this.
Any assistance is welcome. Obviously having non-encrypted links is not acceptable.

Hi SteveKSM,
According to your description, you specify the report manager URL as https://. When you open the child items on report manager, the URL change to the http://.
In your scenario, since you want to set SSRS to require all SSL connections, you need to change the SecureConnectionLevel value to 3 in RSReportServer.config file (located in C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer).
It means that all communication must use secure connections. So please specify this attribute like below:
<Add Key="SecureConnectionLevel" Value="3"/>
Reference:
Configuring the Report Server for SSL Communication and Internet Deployment:
https://msdn.microsoft.com/en-us/library/cc304416.aspx
Report Manager Links with SSL
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

SQL Server 2012- Reporting Services in SharePoint Mode

I would like to use Reporting Services in Native mode but I also installed Reporting Services in SharePoint Mode. Do I need to remove the Shared Feature of Reporting Services in SharePoint Mode and if so how would I do this?
Thanks
Kit52

http://technet.microsoft.com/en-in/library/bb326407%28v=sql.105%29.aspx
Happy to help! Thanks. Regards and good Wishes, Deepak. http://deepaksqlmsbusinessintelligence.blogspot.com/

Sql server 2012 reports

If i develope reports using SQL server 2012 reporting services, can i upload the reports on SQL server 2005 report server and SQL server 2008 Report server ??
h2007

Generally
higher to lower deployment is not supported.
Try to change the properties of the ReportServer Project in Visual Studio and set the target server version as mentioned in below thread.
http://stackoverflow.com/questions/13798289/reporting-services-built-in-2012-deploy-in-2008
Please click the Mark as answer button and vote as helpful if this reply solves your problem

Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager

Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager?
when I check on Microsoft site it says
Reports are not upgraded when you upload a report definition file directly to the report server
or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
When you open an .rdl file in Report Designer in SQL Server Data Tools (SSDT), if the report was
created for a previous namespace, Report Designer automatically creates a backup file and upgrades the report to the current namespace.
This is the only way you can upgrade a report definition file.
Now here is another confusing statement which says
You can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server
2012 report server and it is automatically upgraded on first use. The report server stores the report definition file in the original format. The report is automatically upgraded the first time it is viewed, but the stored report definition file remains
unchanged.
All I want to know is if I deploy a rdl made in 2008 r2 to 2012 will it work on the report manager of
2012?
<o:p>
</o:p>
Mudassar

I have tested this fucntionality and can confirm that ssrs 2008 r2 reports work when you deploy them on new ssrs 2012 report manager .
No Migration is required .
I didnt even moved report server dbs .All I did is just deployed reports on the report manager and it worked .
"You
can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server 2012 report server and it is automatically upgraded on first use. "
Microsoft needs to correct this the documentation is misleading
Mudassar

"SQL Server 2008 Reporting Services does not support map report items"

Hi,
I am trying some new feature that are introduced in SQL Server 2008 R2 version. While I try to use "Map" control within it, it threw the following error:-
"Error 1 The map, Map1, was removed from the report. SQL Server 2008 Reporting Services does not support map report items. "
-Also, similar kind of error I am getting for "Indicator" control.

Hi Tej,
I think you get this error message when you are deploying a report to report server using BIDS, correct? If not, please provide more details on your scenario :-)
If I guessed correctly, then this message is a result of trying to deploy a map report (a SSRS 2008 R2 feature) to a non-R2 2008 report server. When deploying a report of RDL2010 format to a non-R2 report server, BIDS will downgrade the file to RDL2008 format, so that the non-R2 report server can process it. Any report elements using features not supported in RDL2008 will be dropped during this downgrade process.
BIDS gets the server version from a report project property called TargetServerVersion:
http://technet.microsoft.com/en-us/library/ee635898(SQL.105).aspx
If your report server is indeed the 2008 R2 version, then the TargetServerVersion property should be set to "SQL Server 2008 R2 Reporting Services." The project property page also has a "Auto Detect..." option if you are uncertain about the version of your report server.
Hope this helps!
Cheers,
LawrenceThis posting is provided "AS IS" with no warranties, and confers no rights.

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005 Description: "Internal error: An une

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005
Description: "Internal error: An unexpected error occurred (file 'pcxmlacommon.cpp', line 43, function 'PCFault::RaiseError').
I'm getting above error in the pre- execute phase of a DFT when I'm trying to fetch data from a SSAS cube using mdx query.
I'm using OLE DB provider for connecting to cube.
I got one resolution for Error Code 0X8004005, which asked me to add 'Format= Tabular' in cube's connection string. It does not seem to work either. Can any one help me out on this???

You are probably missing an update.
I saw a MS Connect post https://connect.microsoft.com/SQLServer/feedback/details/250920/error-using-oledb-or-datareader-to-get-analysis-services-data where that suggestion was proposed as a fix, but is for an older SQL Server version.
So do there is a question if you pull data from SQL Server 2012 SSAS using SSIS 2012 (so no other build is involved).
Arthur My Blog

SQL Server 2012 - reporting services - scale-out-deployment

Similar Messages

Maybe you are looking for