MissingAssembly: Reporting Services

Hello -
I am in the process of testing my database and I received the error below. I already have the Reporting Service Add-in installed on my application and web servers. Can I continue the upgrade or should this get resolved before I mount
the database? thanks
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 [SP_WSS_Content_BSD], 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
[SPRetail_WSS_Content_BSD], but are not installed on the
current farm. Please install any feature or solution which
contains these assemblies.
Locations :

The missing dll is referring to the 2008 Reporting Services Add-in. If you installed 2012 Reporting Services Add-in for SharePoint 2013 the version is 11.0.0.0
I had the same problem after upgrading a custom report solution in our 2013 environment. The report worked but this error bugged me. Here is a link to the script I ran to remove the assembly references.
http://etienne-sharepoint.blogspot.com/2011/10/solving-missingassembly-errors-from.html It's simple and works like a charm. Hope this helps!
Jennifer Knight (MCITP, MCPD)

Similar Messages

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

$100 to the person that can work with me on getting Lightswitch, Telerik Reporting, Azure reporting service working.

I give up. I am not a professional developer however I am pretty good at coding. But I have limitations and do not understand how all the pieces fit together when it comes to WCF, LightSwitch and Telerik Reporting service.
I have spent the better part of the past 5 evenings attempting to deploy a WCF service to my azure account to create reports for my application. I know this should be simple but I cannot find an example that ties all the pieces together.
I have a
working lightswitch application deployed to Azure
20+ working telerik reports created in a separate project (Reports have parameters that is one of the problems)
No way to get the two to talk together.
If you have experience and feel you can help me please respond to this post and I will set up some time for us to work together online.
Regards a very frustrated part time developer
Cliff
P.S. Sorry if this is an inappropriate use of the forum but I am at my wits end!

(I am not in the running for the 'bounty' just trying to help on the WCF RIA part...)
When you deploy the application to Azure you should be able to hit the WCF RIA Service using:
site/{class name}.svc/
For example if you look at the reports I have in this example:
LightSwitch Survey: Handling
Complex Business Logic Using WCF RIA Services
You can use the live application at the following link: https://survey.lightswitchhelpwebsite.com/HTMLClient (use your
username and password from
LightSwitchHelpWebsite.com)
The call in Fiddler looks like this:
/WCF_RIA_ServiceData.svc/SurveyResults?$filter=(SurveyId%20eq%202)&$top=45&$inlinecount=allpages
This is what your reports should be calling. Can you get this far?
Unleash the Power - Get the LightSwitch 2013 HTML Client / SharePoint 2013 book
http://LightSwitchHelpWebsite.com

Reporting Services Webpart - web part does not auto render consistantly

We are on SharePoint 2010 (integrated with Reporting Services)- on several sites we have added the Reporting Services Web Part and with a saved parameter. The behavior of this web part is not consistent. There are times when I open up a site
and the web part will auto render the report. 5 minutes later I can go into the same site, and the web part does not auto render the report. I have to do edit page, or close and re-open the web site. Has anyone experienced this type of behavior.
I've looked for assistance with this issue on-line cannot find anything that specifically addresses this issue.

Hi Karen,
If the parameters have default values in the report, then the report can be rendered automatically.
For this issue, I recommend to verify the things below:
Does this issue occur when you open the page with the web part in a new tab in the browser or go back to the previous opened tab?
Does this issue occur in the server side or client side?
Please add the site to trusted sites in Internet Explorer to see how it works.
Please change another browser to see how it works.
For narrowing down the issue scope, please test with another report and compare the results.
Thanks,
Victoria
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]

Reporting Services 2008 R2 - SharePoint Integration Mode

Hi everyone,
I installed Reporting Services 2008 R2 in my SharePoint(2013) server and configurated the SSRS to run in SharePoint Integrate mode. But, when I run the command Install-SPRSService in SharePoint 2013 Management Shell, I get this error:
Does anyone know how resolve it ? I search but I didn't get a solution :(
Thanks in advance!
Best Regards!

SSRS 2008 R2 isn't supported with SharePoint 2013. You'll need a minimum of SSRS 2012 SP1. In addition, SSRS 2008 R2 doesn't include the cmdlet you're looking for because it isn't a Service Application, rather it sat external to SharePoint.
The support matrix is at http://msdn.microsoft.com/en-us/library/gg492257.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.

Reporting Services not able to connect with sharepoint

HI
We have a Sql server instance where we are not able to install reporting services, so what we have done is we have created one more sql server instance on the same server with reporting services.
When we configured reporting services in sharepoint integrated mode and try to connect that web service url in sharepoint we are getting an error in sharepoint central administartion that not able to connect to the reporting services.
Request you to throw some light on the same.
Thanks
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

Hi Geeth,
Based on the limited information, I am not very clearly about you issue. In order to solve the problem more efficiently, I need to clarify some information. Could you post more detail information about “try to connect that web service url in sharepoint we
are getting an error in sharepoint central administartion”? For example, the detail steps about the action, the screenshot of the action, and what error message you received. I’m not sure which step are you trying to do. And could you tell me the edition of
your SQL Server and SharePoint? It is benefit for us to do further analysis.
References:
2008 R2:
http://technet.microsoft.com/en-us/library/bb283190(v=sql.105).aspx
http://sharepointtaskmaster.blogspot.in/2010/11/intergration-reporting-service-with.html
http://technet.microsoft.com/en-us/library/bb326213(v=sql.105).aspx
2012:
http://technet.microsoft.com/en-us/library/47efa72e-1735-4387-8485-f8994fb08c8c
http://denglishbi.wordpress.com/2011/07/22/configuring-sql-server-denali-reporting-services-sharepoint-2010-integration/
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

"Reporting services" service does not start automatically

I have installed reporting services from SQL Express SP1 package. OS is Windows 2000 SP4. Just after installation "Reporting services" service has StartMode=Automatic and LogOnAS=LocalSystem as shown in SQL Server Configuration Manager. When system is rebooted reporting services state is Stopped and there is 2 errors in System log:
1. Timeout (30000 milliseconds) waiting for the SQL Server Reporting Services (REPS) service to connect.
2. The SQL Server Reporting Services (REPS) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
If i select "start" from service's context menu then it starting normally and it's state becomes Running.
What can i do to make reporting services starting automatically on system load?

i have the same problem here in one of our servers ,, it was working and suddenly it stopped i don't know why
when i reviewed the Event Viewer :
Event Type: Error
Event Source: SQL Server Report Service
Event Category: None
Event ID: 0
Date: 8/22/2010
Time: 12:05:26 PM
User: N/A
Computer: SERVICE-CENTER
Description:
Service cannot be started. Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information. ---> System.UnauthorizedAccessException:
Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at Microsoft.ReportingServices.Diagnostics.Globals.SafeOpenXmlDocumentFile(XmlDocument doc, String pathToXmlFile)
   at Microsoft.ReportingServices.Diagnostics.RSConfiguration.LoadDocument()
   at Microsoft.ReportingServices.Diagnostics.R...
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Any body can help with this ,, because i didn't find anything helpful till now !!!
dear all
i installed SQL Server 2005 SP2 and it solved my problem
wish you all luck

Reporting Services Point, remote SQL issue

I'm trying to install Reporting Services Point on a remote SQL 2008 R2 SP2 server. I select the SQL server under Servers and Site System Roles and it lists the site database server name, database name (should this name be the same as the DB found in Reporting
Services Configuration Manager?), folder name and reporting services server instance. I enter a new account that is a sysadmin on the SQL click verify and get:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).
Ping works both ways, remote connection on this SQL instance are enabled, static ports configured, a rule to allowany is set in the firewall. Should I perhaps be entering the port (this instance uses a non-standard one) in the Add Site System Roles
Wizard?
If I open up Reporting Services Configuration Manager, the service is started, mode is native, a domain user account is used for the service account, web service URL opens, I even created a new DB. Report Manager URL opens.
SCCM itself uses the same remote SQL instance, so it appears connectivity works fine.
Any assistance is appreciated.

Thank you very much - CypherMike.
You helped me so much!!!
I installed the DB on another Instance so i had to change the port # and just here i found this info that i need to use comma to define the port.
Tnx

Reporting Services Point status message errors.

My Reporting Services Point seems to work OK -all reports are available and run correctly both through the console and via the website. However, I am seeing the following warning in the SMS_SRS_REPORTING_POINT status messages every hour:
"The SQL Reporting Services datasource on Reporting point server "Databaseserver.contoso.com" is missing or has been changed outside of Configuration Manager. It will be rebuilt based on the RSP configuration."
Here's what I think is causing the issue, but I don't know how to solve it.
The reports database is on the same remote SQL server as my site database. Because these site systems were installed automatically through the SCCM installation process, they show up in the Servers and Site Systems Role without an intranet FQDN. However,
when I add the RSP to the database server, it creates a new entry because when manually adding site systems SCCM insists on automatically adding the intranet FQDN. So I now have two separate entries for the same server:
\\DBServer01 - component server, site database server, site system
\\DBServer01.contoso.com - component server, reporting services point, site system
Any thoughts on how to stop these errors?

Yes, I know this is an old post, but I’m trying to clean them up.
In the past when I have seen this, they will automatically clean themselves up after a few days. (aka up to a week later). Have it clean itself up yet?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Reporting Services Point SSL after Role installed

Scenario,
Reporting Services (SQL 2012) installed on a remote server and not configured with SSL. Reporting Services Point installed and functioning correctly.
We now have enabled SSL in RS Configuration using a cname for the certificate (sccmreports.domain.com) and it is working via web browser, however when I attempt to remove the port 80 binding it breaks SCCM's ability to connect to the reporting point via
the admin console. Presumably, if SSL is not enabled prior to installing the RSP that SCCM only knows to connect via HTTP?
If this is the case, outside of uninstalling and re-installing the RSP now is there a way to "tell" SCCM to use HTTPS to connect? Maybe its a different issue altogether?
Thanks!

The SSRS connection info is stored in Site control file, which is in the view vSMS_SC_SiteControlXML. If you change the SSRS address manually, the info cannot be updated automatically so that you must reinstall SSRS.
Juke Chou
TechNet Community Support

Reporting Services web service complex xml type report parameters

Hi,
I have the following xml type parameter in my request query that I use in reporting services.
<Parameter Name="accountDetails" Type="XML" xmlns:d4p1="thevalue" xmlns:i="thevalue">
<DefaultValue>
<d4p1:AccountDetailDto>
<d4p1:AccountNumber>12345</d4p1:AccountNumber>
<d4p1:AccountType>Sales</d4p1:AccountType>
</d4p1:AccountDetailDto>
</DefaultValue>
I want to know how I can assign values to the accountDetails parameter from report parameters, I've tried to call it from the dataset parameter properties but it doesn't return any values. I created Parameters!accountDetails.Value on the dataset parameters
properties and assigned it the following value: it only returns empty columns
="<AccountDetailDto><AccountNumber>"& Parameters!AccountNumber.Value &"</AccountNumber><AccountType>"& Parameters!AccountType.Value &"</AccountType></AccountDetailDto>"
You're help will be highly appreciated as I've been trying to solve this for a while now

Hi Alisa,
Perhaps I should explain my problem clearly...
This is my query request that I send to the webservice:
<Query>
<Method Name="GetPerAccountAssetAllocation" Namespace="http://tempuri.org/">
<Parameters>
<Parameter Name="accountDetails" Type="XML" xmlns:d4p1="thevalue" xmlns:i="thevalue">
<DefaultValue>
<d4p1:AccountDetailDto>
<d4p1:AccountNumber>12345</d4p1:AccountNumber>
<d4p1:AccountType>JSE</d4p1:AccountType>
</d4p1:AccountDetailDto>
</DefaultValue>
</Parameter>
</Parameters>
</Method>
<SoapAction>http://tempuri.org/IPortfolioManagementService/GetPerAccountAssetAllocation</SoapAction>
<ElementPath IgnoreNamespaces="true">*</ElementPath>
</Query>
It works well when I run it just like this, that is without specifying any parameters in the report data dialogue window or on the dataset parameters properties, it returns the values and columns correctly.
So my problem is, I need to find out how(xml parameter syntax, steps e.t.c)
I can do to allow users to specify the accountDetails parameter, its quite tricky for me coz its an xml type parameter, Im not sure if I should just specify the AccountNumber and
ReportType parameters separately:
I've tried the following without any success:
1. Under the dataset properties: I tried not to specify a default value for the accountDetails parameter on the xml query, then I added a parameter called "accountDetails" under the dataset parameters properties, then under parameter
value I added the following xml value :
<d4p1:AccountDetailDto>
<d4p1:AccountNumber>Parameters!AccountNumber.Value</d4p1:AccountNumber>
<d4p1:AccountType>Parameters!AccountType.Value</d4p1:AccountType>
</d4p1:AccountDetailDto>
(I also added the AccountNumber and AccountType parameters under the report data dialogue window)
This returns empty columns, is there something I'm missing, or am I doing this incorrectly?

Reporting Services Point - possibly permissions issue

I'm having a really hard time configuring a working reporting services point in my test SCCM 2012 R2 environment and was hoping someone might be able to help me work out what's gone wrong.
My servers are WS2008 R2. SQL Server 2008 R2 is installed on the primary site server and holds the site database. I installed SSRS onto a separate site server and added it as a reporting services point. This worked, and I see the list of
reports in the SCCM admin console. However, when I try to run a report - either from the console or via web browser - I get this message:
The default value expression for the report parameter 'usertokensids' contains an error. There are no logon servers available to service the logon request. (rsRuntimeErrorInExpression)
   at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
   at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
   at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
   at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
   at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
SMSAdminUI.log shows this message:
[25, PID:3096][06/12/2014 11:24:05] :[fqdnofprimaryserver] : The request failed with HTTP status 503: Server Error.
Now, the reason I think this is a permissions issue is because srsrp.log on the Reporting Point server shows this:
(!) Error retrieving folders - [Login failed for user 'domain\reportingservercomputername$'.].
(I've removed the actual name here, obviously.)
I'm really puzzled about what's going on here, what is trying to authenticate with the SSRS server's machine credentials, and what for. Looking in SQL Server Management Studio on the primary site server which hosts the SQL database, I can see that
the account has a login listed and it has its default schema listed as DBO. On the SSRS server, in Reporting Services Configuration Manager, the Report Server Service Account is set to a dedicated domain user account. The Current Report Server
Database Credential is set to my own Windows login using Current User - Integrated Security - I can't seem to get it to accept the dedicated user account.
Can anyone help me figure out what's gone wrong and how I fix it, please? I'm by no means a SQL person, and I'm at my wit's end with this!
Thanks,
M

The plot thickens.
The SSRS server has these:
"The report server has detected a possible denial of service attack. The report server is dropping requests for service from the IP address 192.168.113.163" (this is the IP address of the primary site system, which hosts the SQL database)
and then
"Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database"
The primary site system, meanwhile, has got thousands of these:
"Login failed for user 'DOMAIN\SSRSSERVERNAME$'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 192.168.113.164]" (that's the IP of the SSRS server)
The Windows firewall is off for both systems. They're on an isolated test network. I still don't understand where the setting is that tells it to make SQL queries using the SSRS server's machine account, rather than the dedicated service account
I created.
Any more ideas? Thanks for your help so far - I really appreciate it!

Reporting Services - All Datasets Broken

Hello there.
We’re having some problems with Reporting Services on a prod site and I was hoping someone might be able to offer a suggestion.
Here are the facts :
We have a SP Server 2010 (not foundation) farm which uses Reporting Services. There is 1 web / application server and 1 SQL server. Reporting Services 2008 R2 is installed on the SQL box.
Sometime in the last 2 weeks the reports all stopped working (last known report run 2 weeks ago). This was picked up yesterday. I'm not aware of anything being manually changed in the farm to cause this.
The reports report directly on SP lists using datasets with SharePoint data connections. There is one dataset per list.
The SQL / Reporting Services box has previously had SP installed on it (Ouch! Inherited system – not sure why SP was installed on SQL box).
A few weeks ago we stopped all SP services on the SQL box but did not uninstall SP from it. This did not affect reporting at the time.
When a report fails, we see this message in the UI :
Looking in the reporting services log messages are like the following, one per dataset :
Query execution failed for dataset 'DataSet1'. ---> System.ArgumentException: Feature '22d91f57-00d1-4e0b-9c04-863a82deaa07' for list template '10001' is not installed in this farm.
The operation could not be completed.
This happens for all datasets for all reports. All datasets are complaining that the feature for the list the data set uses is missing. These are features with list definitions / instances for the lists used in the reports.
The initial thought was that someone had renamed a field or similar, but this would only impact that one dataset. What we are seeing is that
all datasets simultaneously broke.
The features Reporting Services are complaining about are indeed activated in SP in the relevant webs.
On the SQL box the folders for the features Reporting Services are complaining about are not present in the 14 hive at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES, but then as far as I know they never were. On
our dev environment we deleted these feature folders but this didn't reproduce the same error.
We modified an unrelated SP list view yesterday via the SP UI. It’s unlikely but I wonder if there is some kind of list definition XML / voodoo behind the scenes that was interrupted by this.
If you open the broken report in Report Builder directly from SP (via the list context menu), you can run the datasets OK, and do a test connection for the data source - but if you run the report itself you get the usual error. If I use Report Builder on
my local machine to try to save to the web where the reports are stored, I get one of the “feature…is not installed in this farm” errors. I can’t even browse to that web in Report Builder without getting the error.
Things I've tried so far (my infrastructure experience amounts to restart things until they work):
App pool recycle web server.
IISReset web server.
Restart reporting service on SQL box.
Delete the view I thought might have been somehow related.
In summary I have no idea what the root cause is here or what has changed recently. I’m a
programmer and someone else who is no longer available set up this environment so I’m a bit stuck!
Thanks for reading.
Lee

We've resolved this.
It turns out the features it was complaining about really were missing on the Reporting Services box and needed to be present. I wrongly concluded this wasn't the problem initially when we deleted these features on a dev box, restarted a few things and reports
didn't break. I guess something was still being cached somewhere.
Best guess as to why the features went away is that when we disabled all of the SP services on the reporting services box via Central Admin, one of these (probably SharePoint Foundation Web Application), all custom features / solutions were removed
from the box.
Moral of the story I think is make sure your reporting services box is a valid part of the SP farm and has all required features present.
Cheers
Lee

Reporting Services point

I'm trying to install the reporting services role and have hit a road block. We have one primary site and the site database is in a cluster with 3 nodes. The SQL Reporting Services is not installed on the cluster nodes but is installed on its own database
server. Does anyone know if this configuration can be used? If so any help would be appreciated.
I think I should be able to add a new Site System Role for the server hosting the SQL Reporting Services in Administration and install the reporting services point on that site system.
Thank you

Hi,
Please refer to the links below:
Deploying SCCM 2012 Part 12 – Installing and Configuring Reporting Services Point
http://prajwaldesai.com/deploying-sccm-2012-part-12-installing-and-configuring-reporting-services-point/
Configuring Reporting in Configuration Manager
http://technet.microsoft.com/en-us/library/gg712698.aspx#BKMK_InstallReportingServicesPoint
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Reporting Services 2008 error

Good morning all,
I'm using SQL Server 2008 R2 reporting services, and I'm having a problem with the report server and manager pages. I've been able to configure everything in the Reporting Services Configuration Manager, and created the ReportServer and ReportServerTempDB
databases in my SQL Server instance, but when I try to hit either the Web Service URL or the Report Manager URL, I get a 500 error. The stack trace is below, with the error lines in bold. If anyone could help, I would really appreciate it.
Thanks.
rshost!rshost!4c4!08/17/2010-09:19:53:: i INFO: Application domain type ReportManager statistics: created: 11, unloaded: 11, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:53:: i INFO: Appdomain:29 ReportManager_MSSQLSERVER_0-23-129265247936138778 started.
rshost!rshost!4c4!08/17/2010-09:19:53:: i INFO: Application domain type ReportManager statistics: created: 12, unloaded: 12, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:53:: i INFO: Appdomain:30 ReportManager_2-24-129265247938638554 started.
rshost!rshost!4c4!08/17/2010-09:19:54:: i INFO: Application domain type ReportManager statistics: created: 13, unloaded: 13, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:54:: i INFO: Appdomain:31 ReportManager_3-25-129265247940669622 started.
rshost!rshost!4c4!08/17/2010-09:19:54:: i INFO: Application domain type ReportManager statistics: created: 14, unloaded: 14, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:54:: i INFO: Appdomain:32 ReportManager_4-26-129265247942700690 started.
rshost!rshost!4c4!08/17/2010-09:19:54:: i INFO: Application domain type ReportManager statistics: created: 15, unloaded: 15, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:54:: i INFO: Appdomain:33 ReportManager_5-27-129265247944731758 started.
rshost!rshost!4c4!08/17/2010-09:19:54:: i INFO: Application domain type ReportManager statistics: created: 16, unloaded: 16, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:54:: i INFO: Appdomain:34 ReportManager_6-28-129265247946762826 started.
rshost!rshost!4c4!08/17/2010-09:19:55:: i INFO: Application domain type ReportManager statistics: created: 17, unloaded: 17, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:55:: i INFO: Appdomain:35 ReportManager_7-29-129265247948793894 started.
rshost!rshost!4c4!08/17/2010-09:19:55:: i INFO: Application domain type ReportManager statistics: created: 18, unloaded: 18, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:55:: i INFO: Appdomain:36 ReportManager_8-30-129265247950981198 started.
rshost!rshost!4c4!08/17/2010-09:19:55:: i INFO: Application domain type ReportManager statistics: created: 19, unloaded: 19, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:55:: i INFO: Appdomain:37 ReportManager_9-31-129265247953168502 started.
rshost!rshost!4c4!08/17/2010-09:19:55:: i INFO: Application domain type ReportManager statistics: created: 20, unloaded: 20, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:55:: i INFO: Appdomain:38 ReportManager_10-32-129265247955355806 started.
rshost!rshost!4c4!08/17/2010-09:19:55:: i INFO: Application domain type ReportManager statistics: created: 21, unloaded: 21, failed: 0, timed out: 0.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:55:: i INFO: Appdomain:39 ReportManager_11-33-129265247957386874 started.
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:55:: e ERROR: AppDomain ReportManager_11 failed to start. Error: The configuration system has already been initialized.
library!DefaultDomain!4c4!08/17/2010-09:19:55:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: Failed to create HTTP Runtime, Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException:
An internal or system error occurred in the HTTP Runtime object for application domain ReportManager_11. ---> System.InvalidOperationException: The configuration system has already been initialized.
   at System.Configuration.ConfigurationManager.SetConfigurationSystem(IInternalConfigSystem configSystem, Boolean initComplete)
   at System.Configuration.Internal.InternalConfigSettingsFactory.System.Configuration.Internal.IInternalConfigSettingsFactory.SetConfigurationSystem(IInternalConfigSystem configSystem, Boolean initComplete)
   at System.Web.Configuration.HttpConfigurationSystem.EnsureInit(IConfigMapPath configMapPath, Boolean listenToFileChanges, Boolean initComplete)
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
   at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
   at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironmentAndReportErrors(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
   at System.Web.Hosting.ApplicationManager.GetAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
   at System.Web.Hosting.ApplicationManager.CreateObjectInternal(String appId, Type type, IApplicationHost appHost, Boolean failIfExists, HostingEnvironmentParameters hostingParameters)
   at System.Web.Hosting.ApplicationManager.CreateObject(String appId, Type type, String virtualPath, String physicalPath, Boolean failIfExists, Boolean throwOnError)
   at ReportingServicesHttpRuntime.RsHttpRuntime.Create(RsAppDomainType type, String vdir, String pdir, Int32& domainId)
   --- End of inner exception stack trace ---;
appdomainmanager!ReportManager_11-33-129265247957386874!4c4!08/17/2010-09:19:55:: i INFO: Appdomain:39 ReportManager_11-33-129265247957386874 unloading
appdomainmanager!DefaultDomain!4c4!08/17/2010-09:19:55:: e ERROR: AppDomain:ReportManager_11-33-129265247957386874 failed to unload. Error: System.ArgumentNullException: Value cannot be null.
Parameter name: WaitCallback
Server stack trace:
   at System.Threading.ThreadPool.QueueUserWorkItemHelper(WaitCallback callBack, Object state, StackCrawlMark& stackMark, Boolean compressStack)
   at System.Threading.ThreadPool.QueueUserWorkItem(WaitCallback callBack)
   at System.Web.Hosting.HostingEnvironment.InitiateShutdownInternal()
   at System.Web.Hosting.HostingEnvironment.InitiateShutdownWithoutDemand()
   at System.Web.HttpRuntime.ShutdownAppDomain(String stackTrace)
   at System.Web.HttpRuntime.ShutdownAppDomain(ApplicationShutdownReason reason, String message)
   at System.Web.HttpRuntime.UnloadAppDomain()
   at Microsoft.ReportingServices.AppDomainManager.RsAppDomainManager.UnloadAspDomain(Boolean memoryRecycle)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
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.AppDomainManager.RsAppDomainManager.UnloadAspDomain(Boolean memoryRecycle)
   at Microsoft.ReportingServices.AppDomainManager.RsAppDomainManager.CreateHttpRuntime(RsAppDomainType appDomainType, String vdir, String pdir, Int32& domainId).
library!DefaultDomain!4c4!08/17/2010-09:19:55:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerAppDomainManagerException: Failed to create Report Server HTTP Runtime, Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerAppDomainManagerException:
An error occurred when attempting to start the application domain ReportManager within the Report Server service. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the
HTTP Runtime object for application domain ReportManager_11. ---> System.InvalidOperationException: The configuration system has already been initialized.
   at System.Configuration.ConfigurationManager.SetConfigurationSystem(IInternalConfigSystem configSystem, Boolean initComplete)
   at System.Configuration.Internal.InternalConfigSettingsFactory.System.Configuration.Internal.IInternalConfigSettingsFactory.SetConfigurationSystem(IInternalConfigSystem configSystem, Boolean initComplete)
   at System.Web.Configuration.HttpConfigurationSystem.EnsureInit(IConfigMapPath configMapPath, Boolean listenToFileChanges, Boolean initComplete)
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
   at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
   at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironmentAndReportErrors(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
   at System.Web.Hosting.ApplicationManager.GetAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
   at System.Web.Hosting.ApplicationManager.CreateObjectInternal(String appId, Type type, IApplicationHost appHost, Boolean failIfExists, HostingEnvironmentParameters hostingParameters)
   at System.Web.Hosting.ApplicationManager.CreateObject(String appId, Type type, String virtualPath, String physicalPath, Boolean failIfExists, Boolean throwOnError)
   at ReportingServicesHttpRuntime.RsHttpRuntime.Create(RsAppDomainType type, String vdir, String pdir, Int32& domainId)
   --- End of inner exception stack trace ---
   at ReportingServicesHttpRuntime.RsHttpRuntime.Create(RsAppDomainType type, String vdir, String pdir, Int32& domainId)
   at Microsoft.ReportingServices.AppDomainManager.RsAppDomainManager.CreateHttpRuntime(RsAppDomainType appDomainType, String vdir, String pdir, Int32& domainId)
   --- End of inner exception stack trace ---;
rshost!rshost!4c4!08/17/2010-09:19:55:: e ERROR: Failed to create HttpRuntime 80131500.
rshost!rshost!4c4!08/17/2010-09:19:55:: e ERROR: Failed to get appdomain 80131500, pipeline=0x00F99350.
rshost!rshost!4c4!08/17/2010-09:19:55:: e ERROR: Error state. Internal abort for pipeline=0x00F99350 ...

Hi Chris,
From the error messages you posted, the error is caused by the Reporting Services is not able to create the HttpRuntime.
Based on my research, the issue should be caused by the account the Reporting Services is running under does not have sufficient privilege to write files under folder 'RSTempFiles'.
To verify the cause, please check if there is message that resembles the following error message in the Reporting Services error logs:
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerAppDomainManagerException: An error occurred when attempting to start the application domain ReportManager within the Report Server service. --->
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportManager_MSSQLSERVER_0. ---> System.Web.HttpException: The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\RSTempFiles\'.
In case we can verify the issue is caused by insufficient privilege to write files to 'RSTempFiles', we can assign the mentioned account (Service Account) the permissions to write files to the folder to solve the issue.
Generally speacking, giving permission to the service account in the folder per log error in reporting services granted access.
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT

MissingAssembly: Reporting Services

Similar Messages

Maybe you are looking for