SQL server reporting services installation

HI all,
During the SQL server 2008 Reporting Services installation, select the Install the default
configuration option to associate the default Reporting Services instance
to BPC." In my case, the only available option on the Configuration is "Install but not configure". The other two, the "Native m
ode default configuration" and the "Sharepoint integration" are grayed out or disabled.
Please advice.
Regards,
Raghuram.

Yes Raghu,
you have to select the third option.
So the RS components and services will be installed but it will be necessary to open after the installation configuration tool for RS.
There you have to follow step by step and to provide the required information.
Like RS user service or where is the SQL Server or where you have to create the Reports database and others...
It is not really a big deal to configure the RS if you follow all the steps.
Regards
Sorin Radulescu

Similar Messages

SQL Server Reporting Services FAQ

Hi All,
This thread is a summary of the Frequently Asked Questions on SQL Server Reporting Services. We consolidate them and post here for your reference. If you have any further questions, please kindly start a new thread so that more community members, MVPs, and MSFTs can join the discussion and share their ideas. Thanks for your understanding.
Part I: SQL Server Reporting Services General Topics
1. How to migrate SQL Server 2008 Reporting Services to another computer?
2. How to combine connecting string via parameter?
3. How to install a 32-bit version of SQL Server 2005 Reporting Services on a computer that is running a 64-bit version of Windows?
4. Error of EXECUTE permission denied on object 'xp_sqlagent_notify'.
5. Security consideration for anonymous access to Report Server.
6. How to create a custom report template in Reporting Services?
7. Does Reporting Services support horizontal tables which have fixed rows and dynamic columns?
8. How to reset the page number back to 1 every time the report gets a group break?
9. How to open the drill- through report in a new browser window?
10. How to verify the version of SQL Server?
11. How to use multiple datasets?
12. How to upgrade report from SQL Server 2000 to SQL Server 2005?
13. Out of memory error when exporting reports to Excel.
14. How to improve PDF quality of the report exported in Reporting Services 2005?
15. How to enable the Select All option for a multi-value parameter?
Part II: SQL Server Reporting Services SharePoint Integrated Mode Topics
1. How to deploy reports to SQL Server Reporting Services in SharePoint Services integrated mode?
2. How to integrate SQL Server Reporting Services and SharePoint Services?
3. How to refer the reports on the Report Server in SharePoint Services?
4. How to manage user to view reports in SharePoint integrated mode?
5. What information is needed when posting questions regarding SharePoint integrated mode?
6. Is Report Builder available in SharePoint Integrated Mode?
PLEASE NOTE: Microsoft does not offer formal support for the communities you'll find here. Instead, our role is to provide a platform for people who want to take advantage of the global community of Microsoft customers and product experts. Microsoft may monitor content to ensure the accuracy of the information you'll find, but any information provided by Microsoft staff is offered "AS IS" with no warranties, and no rights are conferred. You assume all risk for your use.
Microsoft Online Community Support

1.        Question 3: How to install a 32-bit version of SQL Server 2005 Reporting Services on a computer that is running a 64-bit version of Windows?
Answer:
To install the 32-bit version of Reporting Services on a computer that is running the 64-bit version of IIS 6.0, we can follow these following steps:
1.       Uninstall the 64-bit version of Reporting Services.
Note: Side-by-side installations of 32-bit versions of Reporting Services and 64-bit versions of Reporting Services are not supported.
2.       Run the Dotnetfx64.exe file to manually install the .NET Framework.
The Dotnetfx64.exe file is in the Tools\redist\2.0 folder on the SQL Server 2005 Setup media. To download the Dotnetfx64.exe file, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=70186
3.       In IIS Manager, click Web Server Extensions.
4.       In the Details pane, right-click ASP.NET V2.0.50727, and then click Allow.
5.       Right-click Web Sites, and then click Properties.
6.       Click the ISAPI Filters tab.
7.       In the Filter Name column, click ASP.NET_2.0.50727, and then click Edit.
8.       Replace C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_filter.dll with C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll.
Note: The Aspnet_filter.dll file in the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ folder is a 32-bit version of the file.
9.       Click OK two times, and then close IIS Manager.
10.   At a command prompt, run the following command:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
11.   Install the 32-bit version of Reporting Services.
12.   After setup is complete, open IIS Manager, and then click Web Server Extensions.
13.   In the Details pane, right-click ASP.NET V2.0.50727 (32-bit), and then click Allow.
To install the 32-bit version of Reporting Services on a computer that is running the 64-bit version of IIS 7.0, follow these steps:
1.       Enable ASP.NET and IIS before you install Reporting Services.
2.       Open a command prompt. To do this, click Start, point to All Programs, point to Accessories, right-click Command Prompt, and then click Run as administrator.
3.       In the User Account Control dialog box, click Continue.
4.       Copy the following script:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
5.       In the upper-left corner of the Command Prompt window, right-click the command prompt icon, click Edit, and then click Paste.
6.       Press ENTER to run the script.
7.       Install the 32-bit version of Reporting Services. You must apply SQL Server 2005 Service Pack 2 (SP2) after you install Reporting Services in Windows Vista. If you install SQL Server 2005 Express Edition with Advanced Services, you can run SQL Server 2005 Express Edition with Advanced Services SP2.
For more information, visit the following Microsoft Web site:
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2
http://go.microsoft.com/fwlink/?LinkID=63922
8.       Reset IIS.
9.       Configure the report server for local administration. To access the report server and Report Manager locally, follow these steps:
a.       Start Microsoft Internet Explorer.
b.      On the Tools menu, click Internet Options.
c.       Click Security.
d.      Click Trusted Sites.
e.      Click Sites.
f.        Under Add this website to the zone, type http://servername.
g.       If you are not using HTTPS for the default site, click to clear the Require server certification (https:) for all sites in this zone check box.
h.      Click Add.
i.         Repeat steps f and g to add http://localhost, and then click Close.
10.   This step lets you start Internet Explorer either to localhost or to the network computer name of the server for both Report Server and Report Manager.
a.       Create role assignments that explicitly grant you full-permissions access. To do this, follow these steps:
b.      Start Internet Explorer by using the Run as administrator option. To do this, click Start, click All Programs, right-click Internet Explorer, and then click Run as administrator.
c.       Start Report Manager.
d.      Note By default, the Report Manager URL is http://servername/reports. If you are using SQL Server 2005 Express Edition with Advanced Services SP2, the Report Manager URL is http://servername/reports$sqlexpress. If you are using a named instance of Reporting Services, the Report Manager URL is http://servername/reports$InstanceName
e.      On the Home page, click Properties.
f.        Click New Role Assignment.
g.       Type a Windows user account in the following format: domain\user
h.      Click to select the Content Manager check box.
i.         Click OK.
j.        In the upper-right corner of the Home page, click Site Settings.
k.       Click Configure site-wide security.
l.         Click New Role Assignment.
m.    Type a Windows user account in the following format: domain\user
n.      Click to select the System Administrator check box.
o.      Click OK.
p.      Close Report Manager.
11.   Open Report Manager in Internet Explorer without using the Run as administrator option.
Microsoft Online Community Support

SQL Server Reporting Services SharePoint Integrated mode - Power View is not supported

Hi there,
My environment is the following:
SharePoint Server 2013
SQL Server 2012 SP1 Enterprise edition
I am getting the following message when trying to open BISM item with PowerView icon:
"The feature: "Power View" is not supported in this edition of Reporting Services."
My problem is that the first time I installed SQL Server Reporting Services SharePoint integrated, I used the SQL Server 2012 Standard edition ISO. But then I learned that Power View is only available with Enterprise and BI editions. So I uninstalled Reporting
Services Add-in from Control Panel, Reporting Services from the installation media and deleted the three Reporting DBs in the SharePoint DB server.
Then I used SQL Server 2012 SP1 Enterprise media to install again Reporting Services but not sure why I am still getting the message:
"The feature: "Power View" is not supported in this edition of Reporting Services."
Anyone can advice me what could be the problem? Maybe I have not complete deleted the previous SQL Server Reporting Service Share Point integrated mode from the previous installation? What would be the proper way to uninstall Reporting Services?
Any help will be welcome.
Thanks and best regards,
Joss

Hi Joss,
I am in the same situation,
SQL Server was installed in the standard mode because of that the powerview option is not working.
I have changed teh edition using maintenance --> upgrade edition. the sql server components like DB engine, SSAS and integration services are now showing in enterprise edition. The reporting services are installed from the application end still showing
as the reporting services are standard.
we reinstalled the reporting services but still persists the issue.
suggest me is there any work around to fix the issue other than reinstalled the whole SQL Server.
Thanks
Ramu

SQL Server Reporting Services Service - missing in Central Admin

Hi,
I am following "Install Reporting Services SharePoint Mode for SharePoint 2013" at
http://msdn.microsoft.com/en-us/library/jj219068(v=sql.110).aspx#bkmk_install_SSRS_sharedservice .
I have a WFE, APP and SQL server. We have SQL Server 2012 SP1. Central Admin is installed on the APP server.
I installed the Reporting Services Add-In on the WFE using rssharepoint.msi per "Install or Uninstall the Reporting Services Add-in for SharePoint"
http://technet.microsoft.com/en-us/library/aa905871(v=sql.110).aspx and then ran
Install-SPRSService and Install-SPRSServiceProxy
successfully on the WFE.
I cannot see "SQL Server Reporting Services Service" in Central Admin.
(Central Admin is on the APP server)
get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance finds the service but does not successfully provision it.
The SharePoint LOG just shows: Updating SPPersistedObject SPServiceInstanceJobDefinition Name=job-service-instance-8efb2291-4f12-4fea-bb52-63e86f486e6e. Version: -1 Ensure: False, HashCode: 49732161, Id: 81b73567-58c0-4e94-9072-be5ab39077af, Stack:
I tried installing the "Reporting Services Add-in for SharePoint" again using
rssharepoint.msi on the APP server (since it has central admin), and the install rolls back. The error after running
rsCustomAction.exe /i from the command line - per
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/880b77ac-3228-40ce-99dc-12b0ff0eb46a/reporting-services-add-in-for-sharepoint-installation-interrupted?forum=sqlreportingservices
Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly Microsoft.AnalysisServices.SPClient, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
or one of its dependencies. The system cannot find the file specified.
also saw: SharePoint Web Application content files could not be propagated because no Web Applications could be detected or they are off-line. Which may be normal.
Q. which servers should I be installing the "Reporting Services Add-in for SharePoint"?
Q. how can I fix the errors I see?
macrel

Hi Ketak. Thank you for replying. I already followed your instructions - specifically -
You do not see the SQL Server Reporting Services service in SharePoint Central Administration after installing SQL Server 2012 SSRS in SharePoint mode
I get the following error when I run rssharepoint.msi on the APP sever (where Central Admin is installed). I have to run this other wise
Install-SPRSService and Install-SPRSServiceProxy
are not recognized as commands on that server.
Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly Microsoft.AnalysisServices.SPClient, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
or one of its dependencies. The system cannot find the file specified.
macrel

Verify that SQL Server Reporting Services is installed properly and that it is running.

I am trying to install DPM 2010 on Windows 2008 R2. Running through installation and the server that I'm installing DPM to will also host the SQL instance and Reporting instance. Pretty much choosing all the defaults.
Installation gets to reporting portion and fails. It says that I need to verify that Reporting Services is running.   The exact error is:
Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components copied during installation.
For details, click the Error tab.
DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the Report Server for Secure Sockets Layer (SSL) connections, see Configuring Report Server for Secure Sockets Layer (http://go.microsoft.com/fwlink/?LinkId=178289)
Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
It is running and working, I can go to the URL and see Reports installed.   It grabbed a server certificate which is valid and binds that to 443. I have tried this as well with the certificate removed.
Here is the relative portion of the DPM 2010 log:
[6/25/2010 10:30:01 AM] * Exception : => System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException: Exception of
type 'Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException' was thrown.
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException.UnableToConfigureAccount(ErrorCode errorCode)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateUserAccount(String server, String password, Boolean create)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SetReportingPassword(String password, String server, String instanceName, String dbConnectionString)
*** Mojito error was: PasswordTooShort; 0; None
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
[6/25/2010 10:30:01 AM] * Exception : => Report configuration failed.Verify that SQL Server Reporting Services is installed properly and that it is running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception --->
Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException: exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException:
Exception of type 'Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException' was thrown.
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException.UnableToConfigureAccount(ErrorCode errorCode)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateUserAccount(String server, String password, Boolean create)
   at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.SetReportingPassword(String password, String server, String instanceName, String dbConnectionString)
*** Mojito error was: PasswordTooShort; 0; None
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.ConfigureReporting(Boolean isRemoteDb, String rsMachineName, String rsInstanceName, String installerPath)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.ConfigureReporting(String reportserverConfigFilePath, Boolean existingDB, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
*** Mojito error was: ReportDeploymentFailed; 0; None
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.ConfigureReporting(String reportserverConfigFilePath, Boolean existingDB, Boolean isOemSetup, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.ConfigureReporting(Boolean isRemoteDb)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: ReportDeploymentFailed; 0; None
[6/25/2010 10:30:07 AM] *** Error : Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
[6/25/2010 10:30:07 AM] Information : Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components
copied during installation.
For details, click the Error tab.
DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the Report Server for Secure Sockets Layer (SSL) connections, see Configuring Report Server for Secure Sockets Layer (http://go.microsoft.com/fwlink/?LinkId=178289)

Hello,
The real problem is the error UnableToConfigureAccount and *** Mojito error was: PasswordTooShort; 0; None
The reason is due to the new password complexity on Windows 2008 which states the following:
Password must meet complexity requirements
This security setting determines whether passwords must meet complexity requirements.
If this policy is enabled, passwords must meet the following minimum requirements:
Not contain the user's account name or parts of the user's full name that exceed two consecutive characters
Be at least six characters in length Contain characters from three of the following four categories:
English uppercase characters (A through Z)
English lowercase characters (a through z)
Base 10 digits (0 through 9)
Non-alphabetic characters (for example, !, $, #, %)
Complexity requirements are enforced when passwords are changed or created.
Default:
Enabled on domain controllers.
Disabled on stand-alone servers.
Note: By default, member computers follow the configuration of their domain controllers.
Please use a more secure password adhering to the above criteria and DPM should install fine.
Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

Trying to make Reporting Services Configuration Manager work. Or, SQL Server Reporting Services.

Under Start > Programs > Microsoft SQL Server 2008, I have the following:
SQL Server Management Studio
Configuration Tools
Integration Services
Import and Export Data
Under Configuration Tools, I have the following:
SQL Server Installation Center
SQL Server Configuration Manager
SQL Server Error and Usage Reporting
Reporting Services Configuration Manager
I tried to enable Reporting Services through 'Reporting Services Configuration Manager' but I don't seem to have much control from this view. I see two boxes, one named Server Name (and it shows my server name) and the other is named Report Servicer Instance (and this is grayed out). If I click on the Find box next to Server Name, I get this message:
Report Server WMI Provider Error: Invalid Namespace
Details
Invalid Namespace
To get the Server Name I right-clicked SQL Server > Properties > General
Any ideas on how to make Reporting Services Configuration Manager work? Or, can you please give me more details on how to access "System control" => "Services"? I'm not seeing it anywhere and I'm not seeing any way to find "Sql Server Reporting Services". Basically, I'm trying to activate my SQL Server Reporting Services.
I am using SQL Server 2008 Express Management Studio. Is SQL Server Reporting Services included in Express Management Studio? I read, online, that it is, but I can't find it anywhere.
Thanks again!
Ryan--
<input id="gwProxy" type="hidden"></input> <input id="jsProxy" onclick="jsCall();" type="hidden" />

Thanks Jerry Nee!! This may be exactly what I’m looking for! I went to this link:
http://www.microsoft.com/downloads/details.aspx?FamilyID=B5D1B8C3-FDA5-4508-B0D0-1311D670E336&displaylang=en#filelist
At the top of the page it says, ‘Microsoft® SQL Server® 2008 Express with Advanced Services’, which seems like this is what I’m looking for, so I downloaded the file named ‘SQLEXPRADV_x86_ENU.exe’
Then, I cut that from my desktop and pasted it in my C-drive and I get a message that says, ‘this folder already contains a file named ‘SQLEXPRADV_x86_ENU.exe’, would you like to replace the existing file?’
I’m thinking…what the heck? Do I already have this thing? If so, why can’t I see SQL Server Reporting Services? Maybe I have it now, and I just don’t know how to access the reporting Services features…
Couple quick questions:
What’s the difference b/w these two files:
‘SQLEXPRADV_x64_ENU.exe’ and ‘SQLEXPRADV_x86_ENU.exe’?
Also, my current version of SSMS, Help > About shows this:
Microsoft SQL Server Management Studio
10.0.1600.22 ((SQL_PreRelease).080709-1414 )
Microsoft Data Access Components (MDAC)
2000.085.1132.00 (xpsp.080413-0852)
Microsoft MSXML
2.6 3.0 5.0 6.0
Microsoft Internet Explorer
8.0.6001.18702
Microsoft .NET Framework
2.0.50727.3603
Operating System
5.1.2600
Should Server Reporting Services be included in this version? I think so!!!
Under Start > Programs > Microsoft SQL Server 2008 > Configuration Tools > Reporting Services Configuration Manager, I see this:
Connect to a report server instance:
Server Name:
Report Server Instance:
My server name is ‘'EXCEL-4J2W8KYNP', which I got from Control Panel > System Properties > Computer Name > Full Computer Name;
However, when I put that server name in the box, and hit ‘Find’ I get this message: ‘Report Server WMI Provider error’ Invalid namespace
Details: Invalid Namespace.
I have no idea what this means…
Thanks for everything!
Ryan---

TF400525: Make sure the SQL Server Reporting Services service for this instance is running.

I am trying to install TFS 2012 update 4 on single server installation.
I am getting below error:
TF400525: Make sure the SQL Server Reporting Services service for this instance is running.

Hi CFSA,
Thanks for your post.
If you want install TFS 2012 Server with Reporting Server, you must ensure the provided Reporting Services is running first.
As Daniel said, please check that in SQL Server Configuration Manager to ensure Reporting Services is installed and running.
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.
Click
HERE to participate the survey.

Sql server reporting service

I have installed Sharepoint 2013 along with SQL 2012 SP1 in a single server installation. over this i have installed SQL server reporting service. however when i click on any reports i get the following error:"
(An attempt has been made to use a data extension 'ADS' that is ei
ther not registered for this report server or is not supported in this edition of Reporting Services. (rsDataExtensionNotFound)

Hi,
It seems the Reporting Services Add-in was not configured for Connected Mode.
Installing the Reporting Services Add-in after SharePoint installation
1. Install the SSRS Add-in according to the steps at
http://go.microsoft.com/fwlink/p/?LinkID=164654&clcid=0x409
2. Activate the SSRS feature according to the steps at
http://msdn.microsoft.com/en-us/library/bb677366(SQL.105).aspx
To install the Reporting Services Add-in for Connected Mode
1. Install the SSRS Add-in either before or after SharePoint Server installation according to the session above.
2. Configure Report Server Integration in SharePoint Central Administrationhttp://msdn.microsoft.com/en-us/library/bb326213(SQL.105).aspx
3. Modify the C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config file on the Reporting Services server. Under the <Data> node, under the <Extension> node, add the
ADS data extension. For example:
<Extension Name="ADS" Type="Microsoft.Office.Access.Reports.DataProcessing.AdsConnection, Microsoft.Office.Access.Server.DataServer, Version=14.0.0.0, Culture=Neutral, PublicKeyToken=71e9bce111e9429c"/> -->
4. Modify the rssrvpolicy file on RS server.
See the below link for details:
Use Access Services with SQL Reporting Services: Installing SQL Server 2008 R2 Reporting Services Add-In (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/ee662542
ERROR: An attempt has been made to use a data extension 'SQL' that is not registered for this report server
http://blogs.msdn.com/b/selvar/archive/2009/03/21/error-an-attempt-has-been-made-to-use-a-data-extension-sql-that-is-not-registered-for-this-report-server.aspx
Please let me know if the information helps.
Thanks.
Tracy Cai
TechNet Community Support

TF255186: The following SQL Server Reporting Services Instance could not be found

Hi,
I'm trying to install TFS 2013 on a remote SQL RS instance.
Using the TFS 2103 U4 installation
SQL 2012 RS, name instance, Server: SQLProdA, Instance Name COMRS
When I enabled tracing using debugView I see the following output:
[4160] [Error @11:07:10.978] Exception Message: TF255186: The following SQL Server Reporting Services Instance could not be found: COMRS. The server name is: SQLProdA. (type TfsAdminException)
Any ideas what the issue is?
Thanks,
reuvy

Hi Charles,
Thanks for the help. I already saw those links, and am already trying with the format. As I wrote above:
Server: SQLProdA, Instance Name COMRS
So I wrote in the box "SQLProdA\COMRS" (without quotes of course) and I still keep getting that error.
I don't know if it matters, but although this is indeed a named instance, nonetheless, the path to the report server uses the default url (ie.
http://servername/reports) as opposed to the name instance version (ie.
http://servername_instance/reports) as mentioned by your link and this post:
https://msdn.microsoft.com/en-us/library/bb552341.aspx
But, I checked with Fiddler on the server and didn't see it trying to even access the link so I don't think it is related. I saw with Process Monitor that it is indeed trying to access via the network resources on SQLProdA, so I know it's trying.
I have noticed something in the past, and wondered if this could be the issue, that for example if I have Management Studio 2014 installed, I cannot connect to a Reporting Services instance which is 2012. Only when Management Studio 2012 is installed
and being used can I connect. I wondered if this possibly could be related, that maybe the API or something else which the installer is using is missing some component to connect to the RS instance.
Just in case, I already installed both the SQL 2012 and 2014 Client Tools Connectivity (although I first installed 2014, and then 2012).
Do you think this could be the issue? If not, do you possibly have any other leads?
Thanks,
Reuvy

[Forum FAQ] The Reporting Server cannot be reinstalled on a same SQL Server Reporting Service instance

Symptom: Sometimes, when you want to reinstall the Reporting Server Role for Operation Manager 2012,
but you may encounter an issue that the Reporting Server Role cannot be reinstalled after you successfully uninstall it. When you check the System Center Operation Manager installation log, you can find the following error as shown in Figure 1.
Figure 1: Reporting Server Role cannot be reinstalled
It seems that the SQL Server Reporting Service has not been configured properly. When you open Reporting Services Configuration Manager to check the settings, the settings seem fine though.
Even you recreate Reporting Service Database, the error remains.
After reviewing the OpsMgrSetupWizard.log, we get the following errors when wizard try to connect to SQL Server Reporting Instance (Figure 2).
[07:24:05]: Error: :CheckHttpAddressResponse failed: Threw Exception.Type: System.Net.WebException, Exception Error Code: 0x80131509, Exception.Message:
The remote server returned an error: (500) Internal Server Error.
[07:24:05]: Error: :StackTrace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckHttpResponseFromSRSUrl(String
httpSite)
Figure 2: Error Log -1
It indicates the Reporting Service encounters an internal error. The Website cannot handle the request. So you may check the Reporting Service log which is located in C:\Users\Administrator.SCOM2012\AppData\Local\SCOM\LOGS
and the following errors may be found (Figure 3).
library!ReportServer_0-18!1448!03/30/2014-02:53:23:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
Unable to load assembly Microsoft.EnterpriseManagement.Reporting.Security, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ---> System.IO.FileNotFoundException:
Could not load file or assembly 'Microsoft.EnterpriseManagement.Reporting.Security' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.EnterpriseManagement.Reporting.Security'
Figure 3: Error Log -2
Reason: After the Reporting Server is installed on a SSRS instance, the Reporting Server of SCOM
needs to modify the web.config and rsreportserver.config file to add its own assembly to make the Reporting Server work. But it does not change it back when Reporting Server is uninstalled. So the assembly cannot be loaded and the SSRS cannot respond
our requests.
Resolution: When the Reporting Server is installed, the old web.config and rsreportsserver.config
files will be backed up to web.config1 and rsreportsserver.config1. So you just need to change the files’ name back, then try to install Reporting Server of SCOM again. Everything would go smoothly.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi AakashGhare,
According to your error message, SQL Server 2008 databases are version 655. SQL Server 2008 R2 databases are 661. When you are trying to attach an 2008 R2 database (v. 661) to an 2008 instance and this is not supported. As other post, once the database has
been upgraded to an 2008 R2 version, it cannot be downgraded. You'll have to either upgrade your 2008 SP2 instance to R2, or you have to copy out the data in that database into an 2008 database (such as using the data migration wizard).
In addition, if you want to use a Windows Batch file code and command to automatically login to SQL Server, detach database and attach a new one database, there is a similar details about batch code for attaching database to a new database, you can refer
to this article.
http://notesbyparth.wordpress.com/2012/06/29/run-sql-commands-from-windows-batch-file-or-attachdetach-database-automatically-using-batch-script/
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

QSUF (Query string url filter) and SQL Server reporting services report viewer parameters

Hi,
this is my issue:
I have a SQL Server reporting services web part on a page with a report with 1 parameter, lets say it's a client list
Then i have a QSUF that will be used to filter the clients list through the URL
However, once i connect the filter and the report viewer web part, the parameter goes away and is no longer accessible
I'd like to somehow keep the parameter visible, in case there is no parameter sent through the URL, i would like the user to be able to choose a client from the parameter drop down list
I saw that there is a "send empty if no values are passed" option, but i can't seem to get this working properly and i don't know if this option will make the parameter visible again
Any help would be appreciated
Thanks.

Hi,
According to your post, my understanding is that the query string url filter web part not worked well with SQL server reproting services web part.
Did you use the Wiki page layout in your environment?
You can change the page to a web part page, then check whether it work.
There is a similar thread for your reference.
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/4d7584e3-8e1a-48bf-9346-32f8cb480dd1/query-string-url-filter-web-part?forum=sharepointgeneralprevious
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Unable to insert sql server reporting services report viewer webpart

Hello,
We are trying to add a SQL Server Reporting Services Report Viewer and when we click add we get the following error message
The file you imported is not valid. Verify that the file is a Web Part description file (*.webpart or *.dwp) and that it contains well-formed XML.
Does anyone know what the fix to this is?

Hi，
The Report Viewer Web Part is a custom Web Part that is installed by the Reporting Services Add-in for SharePoint Products and associated with report definition (.rdl) files that are processed by a Microsoft SQL Server Reporting Services report
server.
To install the Web Part, you must run Setup for the Reporting Services Add-in. You should not install or uninstall the Web Part independently. It is part of the add-in and can only be installed through the add-in setup package. The Report Viewer Web Part
file name is ReportViewer.dwp. It is located in the Program Files\Common Files\Microsoft Shared\web server extensions\15\template\features\reportserver folder and should not be moved to other folders.
To use the Web Part, you must have installed and configured the Reporting Services Add-in and configured the report server for SharePoint integration.
For more information,you can have a look at the blog:
http://msdn.microsoft.com/en-us/library/jj219068.aspx
http://msdn.microsoft.com/en-us/library/aa905871.aspx
http://msdn.microsoft.com/en-us/library/bb522800.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

How do I post to SQL Server Reporting services

Hi
I have been using MS forums for almost 20 years but in the current incarnation I find it utterly imnpossible to post to anywhere useful.
I have a serious issue I need to resolve with SQL Server reporting services but cannot find how to get this message posted because the options I get when trying to post in "FORUM CATEGORY" seem utterly unrelated to what I am doing.
What can I do?
Kind regards
Jonathan
jc

Looks like you figured it out. Let us know if not.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

SQL Server Reporting Services Configuration Error(Subscription)

I have just deployed a new project on the server and i can successfully run report from the BI Site; [Server Name]\Reports and no issue there. But when i try to create Subscription for the same report; I am trying File Share and it throws error as given
below. Do i have to configure anything for subscription in the Reporting Services Configuration Tool???
I also have few questions regarding Configuration;
What account should i use for the Deployed Data Source on the Server? A valid SQL Server Account I assume!!!
What account should i use for the Execution Account (For Unattended Operations) ? A valid Windows Account? or SQL Server account?
What account should i use for the File Share Subscription (Credentials used to access the file share:)? A Valid Windows Account with permission for that folder?
Here is the error I am getting in the log file..
ReportingServicesService!library!b!06/17/2010-09:35:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for
more information., AuthzInitializeContextFromSid: Win32 error: 110;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
ReportingServicesService!library!b!06/17/2010-09:35:04:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
ReportingServicesService!subscription!b!06/17/2010-09:35:04:: Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The report server has encountered a configuration error. See the report server log files for more information. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the report server log files for more information.
   at Microsoft.ReportingServices.Authorization.Native.GetAuthzContextForUser(IntPtr userSid)
   at Microsoft.ReportingServices.Authorization.Native.IsAdmin(String userName)
   at Microsoft.ReportingServices.Authorization.WindowsAuthorization.IsAdmin(String userName, IntPtr userToken)
   at Microsoft.ReportingServices.Authorization.WindowsAuthorization.CheckAccess(String userName, IntPtr userToken, Byte[] secDesc, ReportOperation requiredOperation)
   at Microsoft.ReportingServices.Library.Security.CheckAccess(ItemType catItemType, Byte[] secDesc, ReportOperation rptOper)
   at Microsoft.ReportingServices.Library.RSService._GetReportParameterDefinitionFromCatalog(CatalogItemContext reportContext, String historyID, Boolean forRendering, Guid& reportID, Int32& executionOption, String& savedParametersXml,
ReportSnapshot& compiledDefinition, ReportSnapshot& snapshotData, Guid& linkID, DateTime& historyOrSnapshotDate, Byte[]& secDesc)
   at Microsoft.ReportingServices.Library.RSService._GetReportParameters(ClientRequest session, String report, String historyID, Boolean forRendering, NameValueCollection values, DatasourceCredentialsCollection credentials)
   at Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters)
   at Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
   at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
   at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
   at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService rs, CatalogItemContext reportContext, ClientRequest session, JobType type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]&
secondaryStreamNames)
   at Microsoft.ReportingServices.Library.ReportImpl.Render(String renderFormat, String deviceInfo)
   at Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.SaveReport(Notification notification, SubscriptionData data)
   at Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.Deliver(Notification notification)
I also get following error when I try to create email Subscriptoin
w3wp!processing!6!6/17/2010-09:58:53:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'EU_Database'., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'EU_Database'. ---> System.Data.SqlClient.SqlException: Could not obtain information about Windows NT group/user 'THRY\RPUser',
error code 0x6e.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.ReportingServices.DataExtensions.SqlConnectionWrapper.ImpersonateUser()
   at Microsoft.ReportingServices.DataExtensions.SqlConnectionWrapper.Open()
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
   --- End of inner exception stack trace ---
Thanks,
RP

Hi RP,
For your first issue "cannpt create subscriptions", after analyzing the error logs, it seems to be caused to the service account for the Reporting Services service does not have proper permissions to invoke the WIN32 API.
The SQL Server Reporting Services invokes the Win32 API to impersonate user's permissions to write files to shared folder or call COM+ components.
In this case, we can change the service account to a account has permissions to invoke the Win32 API to solve the issue. For example, we can change the account to be NetworkService or LocalSystem:
1. Backup the encryption key using Reporting Serivces Configuration Manager.
2. Change the service account using Reporting Serivces Configuration Manager.
3. Restore the encryptiong key using Reporting Serivces Configuration Manager.
For your others questions, please see the following inline reply:
--What account should i use for the Deployed Data Source on the Server? A valid SQL Server Account I assume!!!
The account should be a Windows account or the SQL Server account, that has read permissions in the source data base at least.
--What account should i use for the Execution Account (For Unattended Operations) ? A valid Windows Account? or SQL Server account?
The account must be a Windows user account. For best results, choose an account that has read permissions and network logon permissions to support connections to other computers. It must have read permissions on any external image or data file that you
want to use in a report. Do not specify a local account unless all report data sources and external images are stored on the report server computer. Use the account only for unattended report processing.
--What account should i use for the File Share Subscription (Credentials used to access the file share:)? A Valid Windows Account with permission for that folder?
You are right. It must be a Windows account, which has permissions to access and write files to the shared folder.
For more information, please see:
Configuring the Report Server Service Account:
http://msdn.microsoft.com/en-us/library/ms160340.aspx
Execution Account (Reporting Services Configuration):
http://msdn.microsoft.com/en-us/library/ms181156.aspx
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT

Report Builder 1.0 for SQL Server Reporting Services 2008 R2

We are trying to implement Ad-Hoc Reporting using SSRS 2008 R2.
First of all, it is very unhelpful that all SSRS books are for either 2008 or 2012, even though SSRS has major changes in 2008 R2 compared to 2008.
Our instructional materials indicate that we should build Report Models to abstract out our databases into terms familiar to our business users.
The problem we are having is the difference in functionality between Report Builder 1.0 and Report Builder 3.0. Report Builder 3.0 is touted as having the modern, ribbon based interface that is supposed to make end-users feel more comfortable. However,
all the documentation says that end users are supposed to use Report Builder 1.0 for Ad-Hoc Reporting. And, it seems, that the reports generated by Report Builder 1.0 are not round-trip compatible with all the other reporting tools for SSRS 2008 R2.
The documentation we have illustrates that Report Builder 1.0 is nice for Ad-Hoc reporting, because is based on connecting directly to Report Models, and the end users can directly drag-and-drop entities and fields into their reports.
When we try working with Report Builder 3.0, it seems we must first connect to the Report Model as a Data Source and then build a Dataset query on the Report Model. Only then are some entity attributes available to be dropped into the report.
If the user decides another source column is needed, they have to go back, edit the query, save the query, and then drag the column from the Dataset to the report. This does not seem end user friendly at all!
We are also concerned that if we train our users on the seemingly soon-to-be-obsolete Report Builder 1.0, and get them used to having direct Report Model access, that at some point we will have to move them to the Dataset-interrupted approach of Report Builder
2+. Highlighting this perception of impending obsolescence of Report Builder 1.0 is that in our shop that is starting with SSRS 2008 R2, we cannot figure out how to get a copy of Report Builder 1.0 in the first place.
We just don't see our end users being savvy enough to handle the steps involved with creating Datasets on top of Report Model Data Sources. So we would have to build the Datasets for them. But in that case, what point is there in creating any
Report Models in the first place if DBAs are the ones to make Datasets?
As such, it is hard to envision a forward-looking SSRS implementation that has the end user ease-of-use Ad-Hoc reporting that the SSRS 2008 documentation presents.
What is it that Microsoft actually wants/expects SSRS implementers to do?
Dan Jameson
Manager SQL Server DBA
CureSearch for Children's Cancer
http://www.CureSearch.org

Hi Dan,
Report Builder 1.0
Simple template-based reports
Requires report model
Supports only SQL Server, Oracle, and Analysis Services as data sources
Supports RDL 2005
Bundled in SSRS
Report Builder 2.0 or later
Full-featured reports as the BIDS Report Designer
Doesn't require (but supports) report models
Supports any data source
Supports RDL 2008
Available as a separate web download
In your scenario, you want to use Report Builder 1.0 in SQL Server Reporting Services 2008 R2, I am afraid this cannot achieve. Report Builder 1.0 is available in the box in either SQL 2005 or SQL 2008. It is not available as a separate client apps and is
only available as a click once application.
Report Builder 1.0
Report Builder 3.0
Thank you for your understanding.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

SQL server reporting services installation

Similar Messages

Maybe you are looking for