Sharepoint 2013 Reporting services not fetching data via linked server

We have a functional SharePoint 2013 farm in production with WFE (Server 1 , windows server 2012) and WFE ( Server 2 , windows server 2012) and SharePoint databases including report server databases on (Server 3, which SQL Server 2012 on windows
server 2012)
Kerberos Authentication is enabled and Windows Authentication happens. Claims to Windows Service seems to work correctly too. No double hop issue. The SharePoint Reporting Services seem to be configured correctly and Reports get generated as expected
in the following cases.
1. If data is being pulled from Server A (SQL Server 2008 R2 Server on Windows Server 2008), Report gets generated no issues.
2. If data is being pulled from Server B (SQL Server 2008 R2 Server on Windows Server 2008), Report gets generated no issues.
The problem:-
We have a view on Server A, which is fetching data from Server B. This report does not get generated. Gives an NT/Authority logon failure. Server B is created as a linked Server on Server A. The setting to run under users security context is checked.
If I execute Query Builder from Report Builder 3.0, the query on the view gets the data and data is displayed in the report for next 10-15 min but after that the connections gets lost or if the user logs out and logs back in, the connection is lost
again.
Has some one experienced a issue like this? Can a report not work on a view getting data from linked server? Or I have missed some thing really important.
Any help is highly appreciated?
cheers!
Rachna
Rachna

Hi,
From your description, my understanding is that you got an error when you clicked System settings after configuring Reporting Services service application.
What size did you use for the memory? Please make sure the server has enough memory to run SharePoint and all services.
In addition, please open
http://localhost:xxxxx/SecurityTokenServiceApplication/securitytoken.svc to check if there is something about this issue.
Here is a similar post about this issue, please take a look at:
http://whitepages.unlimitedviz.com/2012/07/setting-up-reporting-services-2012-with-sharepoint-2013/
As this issue is about Reporting Services, I suggest you create a new thread on SSRS forum, more experts will assist you with SSRS.
SSRS forum:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=sqlreportingservices
Best Regards,
Wendy
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Similar Messages

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

SharePoint 2013 Reporting Services Error activating ReportingWebService.svc

I get below error when i tried accessing System Settings after creating Reporting Services Service Application in SharePoint 2013, looked in to many blogs but didn't find any fix
tried https://social.msdn.microsoft.com/forums/sqlserver/en-US/c2066c96-d8d0-46b5-89ff-abd806b3169d/reportingwebservicesvc-could-not-be-activated
tried http://sharepointconnoisseur.blogspot.com/2014/07/how-to-resolve-requested-service-http.html
and also tried http://sharepoint.stackexchange.com/questions/80118/sharepoint-2010-reporting-services-integration-set-server-defaults-error
but nothing worked
The Error is:
The requested service, 'http://localhost:32843/99f510a2628e4f24a5dbde00a57f0cbb/ReportingWebService.svc' could not be activated. See the server's diagnostic trace logs for more information.
Error Log:
Application error when access /_admin/ReportServer/ReportingServicesSystemSettings.aspx, Error=The requested service, 'http://localhost:32843/9a9f58cdb5b34551921277056e5ebc82/ReportingWebService.svc' could not be activated. See the server's diagnostic trace
logs for more information. Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown
at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.ReportingServices.ServiceContract.IReportServiceManagement.GetSystemProperties(ICollection`1 properties)
at Microsoft.ReportingServices.SharePoint.SharedService.ProxyHelper.<>c__DisplayClass9.<GetSystemProperties>b__8(IReportServiceManagement mchannel)
at Microsoft.ReportingServices.SharePoint.SharedService.ProxyHelper.DoManagementChannelCall(Action`1 caller)
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.get_SystemProperties()
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.LoadSettings()
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
System.ServiceModel.ServiceActivationException: The requested service, 'http://localhost:32843/9a9f58cdb5b34551921277056e5ebc82/ReportingWebService.svc' could not be activated. See the server's diagnostic trace logs for more information. Server stack
trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown
at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.ReportingServices.ServiceContract.IReportServiceManagement.GetSystemProperties(ICollection`1 properties)
at Microsoft.ReportingServices.SharePoint.SharedService.ProxyHelper.<>c__DisplayClass9.<GetSystemProperties>b__8(IReportServiceManagement mchannel)
at Microsoft.ReportingServices.SharePoint.SharedService.ProxyHelper.DoManagementChannelCall(Action`1 caller)
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.get_SystemProperties()
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.LoadSettings()
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.ServiceModel.ServiceActivationException: The requested service, 'http://localhost:32843/9a9f58cdb5b34551921277056e5ebc82/ReportingWebService.svc'
could not be activated. See the server's diagnostic trace logs for more information. Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown
at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.ReportingServices.ServiceContract.IReportServiceManagement.GetSystemProperties(ICollection`1 properties)
at Microsoft.ReportingServices.SharePoint.SharedService.ProxyHelper.<>c__DisplayClass9.<GetSystemProperties>b__8(IReportServiceManagement mchannel)
at Microsoft.ReportingServices.SharePoint.SharedService.ProxyHelper.DoManagementChannelCall(Action`1 caller)
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.get_SystemProperties()
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.LoadSettings()
at Microsoft.ReportingServices.SharePoint.SharedService.UI.ReportingServicesSystemSettings.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
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)

Hi,
From your description, my understanding is that you got an error when you clicked System settings after configuring Reporting Services service application.
What size did you use for the memory? Please make sure the server has enough memory to run SharePoint and all services.
In addition, please open
http://localhost:xxxxx/SecurityTokenServiceApplication/securitytoken.svc to check if there is something about this issue.
Here is a similar post about this issue, please take a look at:
http://whitepages.unlimitedviz.com/2012/07/setting-up-reporting-services-2012-with-sharepoint-2013/
As this issue is about Reporting Services, I suggest you create a new thread on SSRS forum, more experts will assist you with SSRS.
SSRS forum:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=sqlreportingservices
Best Regards,
Wendy
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SharePoint 2013 Reporting Services

I have setup SSRS properly on SharePoint 2013 server. Most of the reports are working fine. I have one report which is not working. I have opened the report in report builder and it has a data source define as
http://servername/_layouts/SPASMXService/SPASMXService.asmx
SPASMXService.asmx file is present on SP 2010 server however it is not on SP 2013 under layouts. I think the report not working because SPASMXService.asmx is missing on SP 2013.
How can I migrate SPASMXService.asmx to SP 2013. I did simple copy of folder from SP 2010 to SP 2013 under both 14 and 15 hives but it did fix the problem.
Please advice.
SP 2013, SQL 2012

This looks like a custom farm solution. Have you upgraded the farm solution to 2013?
Trevor Seward, MCC
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.

Upgrade SharePoint 2007 SSRS integrated mode to SharePoint 2013 Reporting Service (SSRS-2014)

Hi
We are upgrading a SP-2007 site with SSRS integrated reports to SP-2013 and SSRS-2014. As there are many changes done in SP-2013, I would like to know if any of the existing SP-2007 reporting service database need to upgraded to SP-2013 or just upgrading
the SP-2007 content database to SP-2013 and creating a new Reporting Service application will be working fine?
Thanks,
Pat

You'll want to do a few things:
Export the encryption key from the SSRS Configuration application in SharePoint 2007.
Migrate the content database from SharePoint 2007 SP2+ to SharePoint 2010, to finally SharePoint 2013.
Install SSRS 2012 SP1+ on SharePoint 2013.
Migrate the SSRS databases to the SharePoint 2013 SQL Server.
Create a new SSRS Service Application in SharePoint 2013 using the same named databases on the new SQL Server.
Import the encryption key to the SSRS SA.
http://msdn.microsoft.com/en-us/library/jj219068.aspx
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.

Sharepoint 2013 - Search service not working

We have set the search service application to crawl incrementally. The crawls are taking a long time. The content is not vast over the single farm but we do have a few sizable document libraries, lists and media assets. Suggestions as to what to check
again first? Screen shot of the search admin page.

Hi,
According to your post, my understanding is that Search service failed to work in SharePoint 2013.
The cause is that Accounts that are used by application pools or services are members of the Administrators group on the local computer.
I recommend to change the user account to a predefined account, or to a domain user account that is not a member of the Administrators group.
More information:
http://technet.microsoft.com/en-us/library/hh344224(v=office.15).aspx
http://alstechtips.blogspot.com/2013/12/health-analyzer-accounts-used-by.html
http://absolute-sharepoint.com/2013/01/sharepoint-2013-service-accounts-best-practices-explained.html
Best Regards,
Linda Li
Linda Li
TechNet Community Support

SharePoint 2013 web service: Error while sending claim based authentication request (The corresponding SID in the domain is not part of the intended account type)

We are using .asmx services for SharePoint features such as comments, and rating.
Service
Feature used
http://<<hostname>>/_vti_bin/socialdataservice.asmx
Commenting, Rating
http://<<hostname>>/_vti_bin/UserProfileService.asmx
For out of box workflows
In SharePoint 2013,
SharePoint – 80 web application is on claims based mode and user is logging in with windows authentication. With logged-in client context used to call SharePoint's default web service, we are getting below error message from
web service (Social data and user profile services).
Server was unable to process request. ---> The corresponding SID in the domain is not part of the intended account type.
When the service is accessed using console application with Visual Studio credentials (logged in user), we are able to access the service. Below is the code snippet
using (SocialDataService
service = new
SocialDataService())
service.Credentials =
CredentialCache.DefaultCredentials;
SocialCommentDetail detail = service.AddComment("<<url>>",
"Test Comment",
null,
null);
Are SharePoint 2013 web services not supporting request coming with claim based authentication web application?
Thanks, Pratik Agrawal (MAQ Software)

While this applies to 2010, I believe the same is true with 2013:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/925e5f46-317f-46d3-bc55-c67f07eb2372/call-sharepoint-web-services-using-claimbased-authentication?forum=sharepointgeneralprevious
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.

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 2012 SP1 Reporting Services for SharePoint (2013) - Install-SPRSService Not Available

So, at this point, I've blown away an otherwise functional SP2013 + SQL2012SP1 multi-server farm trying to get this to work, only to end up with the same results. Irrespective of whether I install Reporting Services before or after the SP2013 server is in
a farm, SSRS does not seem to be enabled in the farm. I cannot add a new SSRS service application (the menu item does not exist); I cannot start the SSRS service on server (because it isn't here); I cannot execute the Install-SPRSService cmd in SP (yes, the
SharePoint) Powershell (PS comes back with this error:
Install-SPRSservice : The term 'Install-SPRSservice' 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:1
+ Install-SPRSservice
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Install-SPRSservice:String) [],
CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Quite simply, something's broken. I've followed a couple of detailed how-to's on technet and elsewhere... Right at the point when I should be able to create the SSRS service application, the wheels come off the cart. I've tried Import-Module'ing the SQLCMDLETS
and SQLPS PS modules...nothing... The strange thing is that after the installation of the SSRS, if I happen to go into the General Application Settings in Central Admin, I see a new item after Content Deployment:
$Resources:ReportServerResources,AdminReportServerGroupTitle;
$Resources:ReportServerResources,ManageIntegrationSettings; |
$Resources:ReportServerResources,AddTrustedAccounts; |
$Resources:ReportServerResources,SetServerDefaults;
When I uninstall, this goes away.
Greatly appreciate any suggestions you can offer because this is driving me crazy, and I have tried everything I can think of to get this going...

Make sure you are running SharePoint 2010 Management Shell not PowerShell.
Also make sure you are running SharePoint 2010 Management Shell with administrator privileges. Right click the icon and click, "Run As Administrator".
You must have installed "Reporting
Services add-in for SharePoint Products" on the server where you are executing "Install-SPService".
You also may be interested to check this tutorial: Install
Reporting Services SharePoint Mode for SharePoint 2013

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.

Report is not fetching the data from Aggregate..

Hi All,
I am facing the problem in aggregates..
For example when i am running the report using Tcode RSRT2, the BW report is not fetching the data from Aggregates.. instead going into the aggregate it is scanning whole cube Data....
FYI.. Checked the characteristcis is exactely matching with aggregates..
and also it is giving the message as:
<b>Characteristic 0G_CWWPTY is compressed but is not in the aggregate/query</b>
Can some body explain me about this error message.. pls let me know solution asap..
Thankyou in advance.
With regards,
Hari

Hi
Deactivate the aggregates and then rebuild the indexes and then activate the aggregates again.
GTR

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

The SharePoint list query is not valid: Data at the root level is invalid. Line 1, position 1. (rsSPDataProviderError)

Hi there,
All my reports are throwing below error in a sharepoint site configured with Access services. Does anyone have a clue what's causing it?
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'Default'. (rsErrorExecutingCommand)
The SharePoint list query is not valid: Data at the root level is invalid. Line 1, position 1. (rsSPDataProviderError)
Thanks
Manvir

Hi Manvir,
For troubleshooting your issue, please go to C:\Inetpub\wwwroot\wss\VirtualDirectories\ find your Web Application (represented by a port number), then delete an unknown folder created by sharepoint, namely vti_cnf from all the folders and sub-folders in
your web application.
Reference:
http://forums.asp.net/t/985790.aspx?Data+at+the+root+level+is+invalid+Line+1+position+1
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Using Excel 2010 with SharePoint 2013 Excel services

Hello:
What features are we missing when using Excel 2010 (rather than Excel 2013) with SharePoint 2013 Excel services?
Regards
Jeff Gorvits

Hi Jeff,
You might want to read the articles below:
https://support.office.com/en-us/article/Whats-new-in-Power-View-in-Excel-2013-and-in-SharePoint-Server-8e3b4259-421e-41fc-a48e-854388ad14d0?ui=en-US&rs=en-US&ad=US
https://support.office.com/en-us/article/Version-compatibility-between-Power-Pivot-Data-Models-in-Excel-2010-and-Excel-2013-188f44fd-3cfd-4aa7-b4e6-a9402653cbf3?ui=en-US&rs=en-US&ad=US
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

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.

Sharepoint 2013 Reporting services not fetching data via linked server

Similar Messages

Maybe you are looking for