Remove Corrupted Sharepoint SQL Reporting Services

Hi,
I had my sharepoint 2013 foundation with sharepoint-SQL reporting services integrated removed from my server 2012. And I removed my sharepoint folders and regedit files for sharepoint manually to ensure complete uninstallation of sharepoint from my server.
But now I did a reisntall of sharepoint and it works completely fine, but when I tried to install the reporting services again I cant as it says it is already installed but the service is not listed in my sharepoint Services list and when i tried removing
the reporting service using the SQL installer from control panel it exits with an error
Action required:
Use the following information to resolve the error, and then, try to uninstall this feature again.
Feature failure reason:
An error occurred during the setup process of the feature.
Error details:
§ Error installing SQL Server Reporting Services
There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.
Error code: 25012
Log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150220_144131\sql_rsshp_Cpu64_1.log
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_rsshp.msi%40Sqlmsirc_NotifyFeatureStates_64%4025012 to get help on troubleshooting.
§ Error installing SQL Server Reporting Services
Install-SPRSServiceProxy : The term 'Install-SPRSServiceProxy' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At
line:1 char:35+ & {$DebugPreference = 'Continue'; Install-SPRSServiceProxy -uninstall}+
~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Install-SPRSServiceProxy:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
Error code: 0x80131500
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x6A1944E2%400xC68B78F0&EvtType=0x6A1944E2%400xC68B78F0 to get help on troubleshooting

Install the sharepoint reporting services add-in to the exact same drive where you installed it before using the MSSQL installation file, now uninstall the add-in and the reporting service feature from the control panel. This will remove the corrupted
files completely and now do a fresh installation

Similar Messages

Sharepoint SQL Reporting Services Add-In

Hi,
I have installed the Sharepoint SQL reporting services Add-in in one of my application servers and when I call the sites created from the application server itself they show the add-in feature in them in the "site features "list. But when I call
the same site from a WFE in the farm with no add-in installed the the site doesn't show the add-in feature in the "site Feature" list.
This is not supposed to happen as I have tried the same in another farm and the add-in was needed to be installed only in the application server and it would automatically be shown in sites even when they are called from a WFE or anywhere.

SSRS in SharePoint Integrated mode requires the installation of two components. SSRS in SharePoint Integrated mode only needs to be installed on one App server. But the SSRS SharePoint Add-in needs to be installed on all the WFEs and the app
server where SSRS in SharePoint Integrated mode is installed. Not sure how you got it to work in the other farm. Take a look at the following article:
https://msdn.microsoft.com/en-us/library/hh479775.aspx
You will note in the diagram that the Add-in is installed on each WFE.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Installed SQL Reporting Services 2012 on SharePoint 2013 Server. SQL Reporting Service not available In the list of runnning services or new service applications

Hi I'm trying to setup SQL reporting services in a SharePoint 2013 farm consisting of:
4 WFE's
4 App Servers (NLB Central Admin x 4 servers)
4 App Severs for SSRS (Light limited SharePoint services running)
I've installed SSRS 2012 SP1 by following the guide (http://msdn.microsoft.com/en-us/library/gg492276.aspx) on one of the SSRS SharePoint 2013 servers and ensuring Reporting Services - SharePoint and Reporting Services Add-in for SharePoint Products is selected.
All completed without errors and I have even upgraded to SP2 for troubleshooting but no joy.
I've then gone into SharePoint Central Admin and I cannot see SQL Reporting Service available In the list of runnning services on the server I have just installed SSRS on and going to manage service applications I cannot see in the new dropdown menu SQL
Reporting Services.
I have ran the following commands in the SHarePoint management shell:
Install-SPRSService and Install-SPRSSeviceProxy
and
get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
The reply was that the service was already online on the server.
So in powershell all seems ok but it does not appear in central administration.
I have also moved Central Administration to the SSRS SharePoint server too.
Any other suggestions? Here is the same problem but in SP2010 (http://social.technet.microsoft.com/Forums/office/en-US/6a21cc05-1f9b-49ad-a9bb-44aa5b3ce312/action?threadDisplayName=after-installing-sql-reporting-services-service-for-sharepoint-2012-service-is-not-in-the-list-of)
In my lab environment of a 4 server SP2013 farm it worked immediately when i installed it on the app server (CA host) so I dont think it is my install strategy.
I guess my next attempt is to install SSRS on an app server with central administration hosted.
Thanks

I had the same issue on 2 different environments.
I had 2 application servers. One had Central Administration. I installed SSRS on the other one and it never appeared in the Service Applications in SharePoint.
When I also provisioned Central Administration on the other application server and went to the service applications using Central Admin on that server, the SSRS service application was there.
Since then I always install SSRS on the server which hosts Central Admin. No issues then.

SQL Reporting services installing sharepoint mode - Error while installing

Hi I have SharePoint 2013 environment and now i am trying to install SSRS sharepoint mode.
I use SQL server enterprise version 2012 SP1.
While installing this i got and error at the end.
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
Could not load file or assembly 'System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
1- Now i am not able to uninstall this
2- I also don't see the service application in Central admin under New.
Please help me to resolve this issue.
My name is yogendra

Hi,
According to your post, my understanding is that you failed to install SSRS sharepoint mode.
Please make sure you install Reporting Services SharePoint Mode for SharePoint 2013
correctly.
You can refer to:
Install Reporting Services SharePoint Mode for SharePoint 2013
Installing and configuring SQL Reporting services on SharePoint 2013
In addition, please install Windows Management Framework 3.0 on the
build server.
More information:
Exception
Message: Could not load file or assembly 'System.Management.Automation, PublicKeyToken=31bf3856ad364e35'
How to use SQL Server in Windows and Windows Server environments
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Upgrade Sharepoint 2010 SQL Reporting Services from 2008 R2 to 2014

I'm about to do the upgrade of SharePoint 2010 Reporting Services from 2008 R2 to 2014. The instructions say it can be done "in-place" with no downtime. I've seen this article:
http://whitepages.unlimitedviz.com/2012/03/upgrading-sql-server-reporting-services-to-2012-in-sharepoint-integrated-mode/
It covers 2012 so I assume the same holds true for 2014.
I'd like to get the low down from anyone who has actually performed the upgrade of SSRS from 2008 R2 to 2014. Anyone done this upgrade? Any issues?
David Jenkins

So far I would have to say that the upgrade can be done "in-place" but there is a "DOWNTIME".
This article has helped a lot:
http://blogs.catapultsystems.com/tlingenfelder/archive/2012/07/10/upgrading-sql-server-reporting-services-2008-r2-to-sql-server-reporting-services-2012-in-sharepoint.aspx
In the article it tells you about a bug in the SQL Upgrade process where
the Domain account you use will not work. When you type in the password it fails. On top of that it will lock the Domain account because of a bad password! There is probably something wrong with the authentication process and it garbles the password.
Anyway, you end up having to change the account to the "Network Service" account before you can do the upgrade. This means the services get restarted which means???
DOWN TIME! He goes over other errors. I haven't reviewed these issues yet.
The other thing I learned is that everything needs to be SQL Server 2008 R2 SP2 in order to upgrade. You don't find this out until almost the last step in the installation process.
Now I have to wait until next week to actually do the upgrade because I have to schedule an SP2 install. :(
David Jenkins

SharePoint 2013 and SQL Reporting Services Integration Mode

I'm setting up a production environment with SQL Server 2012 SP1 (Clustered) and SharePoint 2013.
I successfully setup the integration using PowerShell (Install-SPRSService & Install-SPRSServiceProxy). I can see the SQL Reporting Service on the CA Services and it's started, I've also created the Services Application without any issues (And linked it
to my web application). However the Report Server Integration feature is missing from my site collection and so are the content types. I even tried creating a new site collection and no dice.
Appreciating any help.
Best,
MI

Hi MI,
As per my understanding, I think this issue is caused by you haven’t install the Reporting Services add-in for SharePoint Products or is not installed correctly. If we install the Reporting Services add-in for SharePoint Products after the installation of
the SharePoint Server, then the Report Server integration feature and the Power View integration feature will can be activated for root site collections. For other site collections, we can manually activate the features. To fix the issue you occurred, we should
install or reinstall the Reporting Services add-in for SharePoint Products.
For more information about Install Reporting Services 2012 SharePoint Mode for SharePoint 2013, please see the following article:
http://msdn.microsoft.com/en-us/library/jj219068.aspx
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SharePoint 2010 with SQL Reporting Services 2012 "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"

i have a small sharepoint farm "2 servers" (WFE) and SQL Server 2012 ,
i installed rsSharePoint for reporting services , as a read the Reporting services is Application Service with SQL 2012 not as SQL 2008 R2 with SharePoint integrated mode, so after installation when am trying to configure the SQL Server
Reporting Services Application services i got the below error :
"Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"
any kind of help would be much appreciated .

I'm having the same issue, but to me it seems like the instructions I've seen are all over the place. I already have SP 2013 and SQL 2012 SP 1 installed. I already added the features for Reporting Services - Sharepoint and Reporting Services
Add-in for SharePoint Products. I didn't see the Reporting Service service in CA, so I ran the powershell scripts to add SPRSService and SPRSServiceProxy.
My initial quest, was to get the BI features enabled, which took me on the journey of adding the Report Services, then I got the error.
Then when I read this about installing the BI features
http://blogs.msdn.com/b/querysimon/archive/2012/11/26/installing-the-bi-features-of-sharepoint-2013.aspx, which I already had SQL and SP installed. Do I have to rerun and selct the SQL Server PowerPoint for SharePoint option? I have the PowerPoint
Configuration Tool on my SQL server, I run it and I get PowerPivot for SP 2013 Configuranoi is missing prerequisits: SP 2013 EE is required. Which I have EE.
Is Reporting Services different or in addition to the BI Feature (PowerPivot)?
Have I missed a step?
Thanks for you help.
Kim
Kim.Williams

SQL Reporting Services stops on my SharePoint 2007 Moss environment?

Hi,
I have SharePoint 2007 Moss SP3 installed on my VMWare server. I have a separate database VMWare server. I have SQL Server Reporting Services configured. Every other day the SQL Reporting Service stops, it seems to time out and logs a 7031 windows event.
I've had to create a scheduled task to restart this service every day at 4am. The OWSTIMER process consumes around 50% CPU. Any solutions for the above?
Thanks.

Hi AspNet-Scotland,
The application pool for Central Admin might be timing out, increasing the shutdown time limit for the process model from the default of 90 seconds to something longer (300 seconds) should resolve it if the cause is time-outs.
This post explains how to change the Shutdown Time limit:
http://www.sharepointpapa.com/blog/_layouts/15/start.aspx#/Lists/Posts/Post.aspx?ID=20
scroll down about half way on the post, or search for High level steps,
Cheers,
Stacy Anothersharepointblog.blogspot.com

Upgrade 2010 to 2013 with SQL Reporting Services

I'm getting ready to upgrade to 2013.
When I run the Test-SPContentDatabase I get:
Category : MissingWebPart
Error : True
UpgradeBlocking : False
Message : WebPart class [ab6d9dad-e23c-ce4f-ff98-f6575a1ccf4c] (class [
Microsoft.ReportingServices.SharePoint.UI.WebParts.ReportView
erWebPart] from assembly
[Microsoft.ReportingServices.SharePoint.UI.WebParts,
Version=10.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91]) is referenced [24] times
in the database [is-sharepoint], but is not installed on the
current farm. Please install any feature/solution which
contains this web part.
Remedy : One or more web parts are referenced in the database
[is-sharepoint], but are not installed on the current farm.
Please install any feature or solution which contains these
web parts.
Locations :
Category : MissingAssembly
Error : True
UpgradeBlocking : False
Message : Assembly
[Microsoft.ReportingServices.SharePoint.UI.ServerPages,
Version=10.50.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91] is referenced in the
database [is-sharepoint], but is not installed on the
current farm. Please install any feature/solution which
contains this assembly.
Remedy : One or more assemblies are referenced in the database
[is-sharepoint], but are not installed on the current farm.
Please install any feature or solution which contains these
assemblies.
Locations :
Category : Configuration
Error : False
UpgradeBlocking : False
Message : The [is.photomask.com] web application is configured with
claims authentication mode however the content database you
are trying to attach is intended to be used against a
windows classic authentication mode.
Remedy : There is an inconsistency between the authentication mode of
target web application and the source web application.
Ensure that the authentication mode setting in upgraded web
application is the same as what you had in previous
SharePoint 2010 web application. Refer to the link
"http://go.microsoft.com/fwlink/?LinkId=236865" for more
information.
Locations :
The first two have to do with reporting services. I'm trying to workout how to go about getting these errors to go away. I don't want to remove SQL reporting or migrate a broken site and fix it later. FYI it does migrate but reporting services
is of course broken.
So what I was wanting to do was to upgrade SQL Reporting Services for SharePoint 2010 from 2008 SQL to 2014 SQL first. This would be in the hopes that it would make the migration to SharePoint 2013 work as the assemblies would change to the proper
version.
Can anyone elaborate on my upgrade path?
I'm still looking up the "Claims Based" authentication thing. I've found an article on how to migrate it so not a big deal. I do wonder however if this is tied to the issue I saw with default.aspx and home.aspx being denied to all users
after I did migrate a content db.
David Jenkins

Hi David,
The following sections describe the basic steps needed to upgrade or migrate from 2008 versions of Reporting Services SharePoint mode to 2014 version.
SQL Server 2008 R2 to SQL Server 2014
Starting environment: SQL Server 2008 R2, SharePoint 2010.
Ending environment: SQL Server 2014, SharePoint 2010.
In-place upgrade is supported and there is no down time for your SharePoint environment.
Install the SQL Server 2014 version of the Reporting Services add-in for SharePoint on each web front-end in the farm. You can install the add-in by using the SQL Server 2014 installation wizard or by downloading the add-in.
Run SQL Server 2014 installation to upgrade SharePoint mode for each “report server”. The SQL Server installation wizard will install the Reporting Services Service and create a new Service application.
If you also want the ending environment to run SharePoint 2013, you need to complete a database-attach upgrade of the SharePoint 2010 to SharePoint 2013.
For more scenarios information, please refer to:
http://msdn.microsoft.com/en-us/library/ms143747.aspx#bkmk_sharePoint_scenarios
Per the supported combinations of SharePoint and Reported Services Components, I’d recommend you firstly upgrade Reporting Services to 2014, then upgrade SharePoint to 2013.
For more information:
http://msdn.microsoft.com/en-us/library/gg492257.aspx
The link below is the reference for migrating a Reporting Services:
http://msdn.microsoft.com/en-us/library/hh759331.aspx
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Workflows 2013 and SQL Report Services: Configure on Independent Servers or Existing App Servers?

Currently, my SharePoint 2013 Farm has Workflows 2013 and SQL Report Services installed on app servers, along with other applications. Workflows 2013 isn't working correctly (installed prior to my coming on board with the organization), I'm assuming it
is a configuration issue, but rather than re-configure, I've read that is recommended to be a standalone server. It was also recommended by a MSFT rep that our report services have its own independent server. Currently, Report Services is also installed on
an app server that runs other applications on the farm.
Has anyone had any experience with installing Workflows 2013 and/or SQL Report Services on independent vs. existing application servers?
Additionally, my existing application servers have 24 GB of RAM (I believe the recommendation for SharePoint production environments is 12 GB), should I plan for the potentially new servers (Workflows and Report Services) to also have 24 GB of RAM? Not really
sure if it will be needed if they have dedicated tasks.
Thanks for any input you can provide!

It entirely depends on load. WFM will work just fine installed on servers in the SharePoint farm. SSRS preferably should go on the end-user facing servers for better performance.
The questions you're asking are all "it depends" :)
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.

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 Reporting Services & OLAP Cubes for Data Modeling.

I've been using PowerPivot & PowerView in Excel 2013 Pro for some time now so am now eager to get set up with Sharepoint 2013 Reporting Services.
Before set up Reporting Services I have just one question to resolve.
What are the benefits/differences of using a normal flat table set up, compared to an OLAP cube?
Should I base my Data Model on an OLAP Cube or just Connect to tables in my SQL 2012 database?
I realize that OLAP Cubes aggregate data making it faster to return results, but am unclear if this is needed with Data Modeling for Sharepoint 2013.
Many thanks,
Mike

So yes, PV is an in-memory cube. When data is loaded from the data source, it's cached in memory, and stored (compressed) in the Excel file. (also, same concept for SSAS Tabular mode... loads from source, cached in mem, but also stored (compressed) in data
files, in the event that the server reboots, or something similar).
As far as performance, tabular uses memory, but has a shorter load process (no ETL, no cube processing)... OLAP/MDX uses less memory, by requiring ETL and cube processing... technically tabular uses column compression, so the memory consumption will be based
on the type of data (numeric data is GREAT, text not as much)... but the decision to use OLAP (MDX)/TAB (DAX) is just dependent on the type of load and your needs... both platforms CAN do realtime queries (ROLAP in multidimensional, or DirectQuery for tabular),
or can use their processed/in-memory cache (MOLAP in multidimensional, xVelocity for tabular) to process queries.
if you have a cube, there's no need to reinvent the wheel (especially since there's no way to convert/import the BIDS/SSDT project from MDX to DAX). If you have SSAS 2012 SP1 CU4 or later, you can connect PV (from Excel OR from within SP) directly to the
MDX cube.
Generally, the benefit of PP is for the power users who can build models quickly and easily (without needing to talk to the BI dept)... SharePoint lets those people share the reports with a team... if it's worthy of including in an enterprise warehouse,
it gets handed off to the BI folks who vet the process and calculations... but by that time, the business has received value from the self-service (Excel) and team (SharePoint) analytics... and the BI team has less effort since the PP model includes data sources
and calculations - aside from verifying the sources and calculations, BI can just port the effort into the existing enterprise ETL / warehouse / cubes / reports... shorter dev cycle.
I'll be speaking on this very topic (done so several times already) this weekend in Chicago at SharePoint Saturday!
http://www.spschicagosuburbs.com/Pages/Sessions.aspx
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

Report on Journals, SQL reporting service error

Hi Experts, I have one issue on BPC MS 5.1 "Reports on Journal" issue. When trying to run the report on journals, the pop-up web base screen returning "SQL Reporting Service Error". Going to check the SQL reporting services configuration, all the services are green beside the two optional configurations - "Sharepoint Integration" and "Encryption Keys", and going to webadmin tasks - publish reports, all the items have been build and published. Any clue?
Thanks
Thomas

Thanks Sorin, I have no access to the SQL currently, I will get the info ASAP with our basis. By the way, when I run the report from BPC server side, the extra msg came out(not only : Error Msg: Reporting Services Error)
Error Msg: Reporting Services Error
The item '/XXXAPPset/JEF_LEGALAPP_ByUser' cannot be found. (rsItemNotFound)
Is this mean something missing when system trying to build the report? since I can't find the Journal report format when I open the link "Http://domain/reports"
Thanks and Regards,
Thomas

Coldfusion and SQL reporting service 2005?

Ive been searching google for hours with no clear answer. How
can you use coldfusion to pull in an sql report from reporting
service? Via a web service or wsdl i assume, but how?

Anwar,
It's important to get the terms right here.
SQL Reporting Services is not the same as SQL Server Reporting Services (SSRS).
SQL Reporting Services refers to an Azure service that lets users develop reports in the cloud. However, it is being retired in Oct. 2014, so you'll want to stay away from that.
SQL Server Reporting Services (SSRS) is the reporting module that is part of SQL Server. This is a sophisticated tool that lets developers create and publish reports that users can access through various methods. It has schedule and refresh capabilities,
and can leverage SQL Server Analysis Services (SSAS) and SQL Server Integration Services (SSIS). You'd most likely use SSRS if you're creating sophisticated reports and queries that you don't want your users creating.
SQL Report Builder is a report creation tool designed for users who want to stay in Microsoft Office. It can be used by developers or end users.
http://technet.microsoft.com/en-us/library/dd220460.aspx
Both environments let you create reports that can be shared (published) on a report server or through SharePoint.
So it's really a matter of what you're most comfortable using.
Hope that helps.

Can I use RS.exe to create the folders in Sharepoint-Integrated Reporting service?

Hello All,
Recently, I am using rs.exe and .rss files to publish my reports to SharePoint-Integrated Reporting Service.
The outstanding issue is, it cannot create non-existing folders for me automatically. I have to created the folder manually.
Thinking BIDS "Deploy" function can make folder creating happen, why the RS.exe doesn't support so?
Does anyone know how to change .rss and rs files to make folders creating automatically.
E.g. If I pass in "ParentFolder" and it doesn't exist on SharePoint, then RS.exe can create the folder first then deploy the RDL files under that folder.
Derek

Hi Derek,
In SSRS, we can use .rss files to publish our reports to a new folder. Please refer to the following script:
Dim definition As [Byte]() = Nothing
Dim warnings As Warning() = Nothing
Dim destinationFolder As String = "DemoReports"
Dim reportsTargetPath As String = "/" + destinationFolder
Dim reportsSourcePath As String = "C:\Demo"
Dim datasourceName As String = "DataSource1"
‘Create the destination Folder
Try
rs.CreateFolder(destinationFolder,”/”, Nothing)
Console.WriteLine("Parent folder {0} created successfully", destinationFolder)
CreateReportDataSource(datasourceName, "SQL", "Data Source=.;Initial Catalog= AdventureWorksDW2012")
Catch e As Exception
Console.WriteLine("Tasks completed successfully.”)
End Try
You can refer to the script in the following blog.
http://sqlserverselect.blogspot.in/2010/10/rsexe-and-rss-scripts-for-automation-of.html
Regards,
Alisa Tang
If you have any feedback on our support, please click
here.
Alisa Tang
TechNet Community Support

Remove Corrupted Sharepoint SQL Reporting Services

Similar Messages

Maybe you are looking for