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

Similar Messages

Sql reporting services stops every 24 hours for a short time then restarts

I have noticed that recently in sccm 2012 sp1 the sql reporting services stops every morning at 7:58 am and restarts after a minute or two. The only entry in the event logs is when it stops. I don't see anything tied in with it that stops or
starts at the same time and there are no tasks or anything like that which would point to this time frame. I just thought I would throw this out there to see if anyone had any ideas. Usually with something of this nature there are some corresponding
log entries that go beyond the service stopping, but in this case there isn't. Thanks for any help you can provide.

I think I found out what was going on. I approached this from a different angle and was directed to the sql reporting services logs and found information on the reporting web server stopping. Researching that yielded the following information.
It appears that this is a result of the SSRS Web Server recycling the App Domain, which is supposed to be a pretty normal process. In fact, the configuration file for this process defaults to recycling the app domain twice daily. This lines up
with the time frame that the reporting service is stopping. It restarts it in less that two minutes and logs the recyling in the reporting services log twice daily so why I'm not seeing this entry in the event logs twice daily or even every day must
be a timing thing. I think if it takes an extra millisecond or two to recycle the app domain, it dumps an entry into the windows event logs and the sccm component status monitoring.
http://ask.sqlservercentral.com/questions/97176/reporting-web-server-stopped.html

SQL Report Service Stopped error

Hi,
I have problem using BPC and I run the diagnostics in SAP Server Manager. It reported that the SQL Report Service, which is under Computer Services Status, is Stopped.
Then I tried to manually start the SQL Server Reporting Services (MSSQLSERVER) but I got the following message.
Could not start the SQL Server Reporting Services (MSSQLSERVER) serivce on Local Computer.
Error 1067: The process terminated unexpectedly.
How can this be fixed?
Thanks!
Sunny

I assume a reboot of the server didn't work?
Like Joost said, perhaps an incorrect installation.
You can check whether reporting services is working by typing //servname/reports in the URL of a web page.

Reporting Services Add-in for Sharepoint- does it need an SQL Server license?

In a new project we will be creating an SSRS in Sharepoint integrated mode. For this we'll need SQL Server and Sharepoint on that box.
We'll also have one or more SharePoint Web Front End (WFE) servers. To allow them to connect to the SSRS-in-sharepoint-mode box, and to present the user with the right user interface for doing so, I believe we can install the Reporting Services Add-In for
Sharepoint on the WFE servers.
The question is, do we need to have SQL Server license for each WFE server where we use the Reporting Services Add-In, or is it free to use?
We've had advice that we need to buy a SQL Server license everywhere we use the add-in, but I am not sure this is correct.
Thanks in advance,
Rich

Hello there,
The Reporting service Add-in for SharePoint can be downloaded free on Microsoft Download site. That means it does not need any license on the add-in.
Regards,
Edward
Edward Zhu
TechNet Community Support

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 Server Reporting Services Add-In for SharePoint not installing properly

Environment: Windows Server 2008R2, SQL Server 2012, SharePoint 2013 Enterprise
When I run the install for SQL Server 2012 Reporting Services Add-in for SharePoint it SHOULD install to c:\program files\common files\Microsoft Shared\Web Server Extensions\14 AND 15. Specifically it should drop a mess of ASPx pages for admin to the \templates\Admin\ReportServer
folder. In this environment it only pushes them to the 14 folder and not the 15. Any ideas on why this would happen? I have not ever seen this before and it is hosing the install completely.

Hi Gouranga,
According to your description, when you install the SQL Server 2012 Reporting Services Add-in for SharePoint 2013, you find the files are installed into the folder for sharepoint 2010(..../14). Right?
In Reporting Services, Not all features are supported in all combinations of report server, Reporting Services add-in for SharePoint, and SharePoint Products. Please see the linke below:
Supported Combinations of SharePoint and Reporting Services Server and Add-in (SQL Server 2012)
As you can see in the link, the SQL Server 2012 Reporting Services Add-in is only for Sharepoint 2010. This the reason why it's installed into the file for sharepoint 2010.
Reference:
Where to find the Reporting Services add-in for SharePoint Products (SharePoint 2010 and SharePoint 2013)
Install or Uninstall the Reporting Services Add-in for SharePoint
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

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

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 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 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

Reporting services in three tier SharePoint 2013 environment

Hi,
I am trying to integrate SQL Server 2012SP1 Reporting Services in a three tier SharePoint 2013 environment, but it seems it is not succesful.
The setup is as following:
SRV1: SQL Server with content, config,... and the Reporting Service databases.
SRV2: SharePoint 2013 Application server & Central Administration
SRV3: SharePoint Web Front with SharePoint sites
All application pools are started with domain accounts on SRV2 & 3
When opening the Central Administration site, the Reporting Services Service Application and its Proxy is created and configured. On SRV2 the Application exists in the application pool in IIS, but it does not appear in the SRV3. Should it be created manualluy?
In Central Administration, when opening the site settings the Reporting Services section is created, but when opening the Site Settings for the root site the section shows variables:
$Resources:ReportServerResources,ReportServerSiteSettingsGroupTitle;
$Resources:ReportServerResources,ScheduleList;
$Resources:ReportServerResources,SiteLevelSettings;
$Resources:ReportServerResources,ManageSiteDataAlerts;
I believe i need some help here.
Thanks in advance.
Best regards,
J

Hi J-S,
Generally, the issue occurs if you are in the Windows Powershell instead of the SharePoint Management Shell or the Reporting Services - SharePoint mode feature is not installed. So, please double check you are using the SharePoint Management Shell or install
the Add-in by installing the rssharepoint.msi instead. Here is the download link:
http://www.microsoft.com/en-us/download/details.aspx?id=35583
If it is not the issue, please install the Reporting Services - SharePoint mode from the SQL Server 2012 installation media.
Reference:
http://msdn.microsoft.com/en-us/library/ms144289.aspx#bkmk_cmdlets_not_recognized
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

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.

SQL Reporting Services stops on my SharePoint 2007 Moss environment?

Similar Messages

Maybe you are looking for