"The feature Power View is not supported in this edition of Reporting Services" after installation of November CU for SharePoint

We had deployed Reporting Services / PowerPivot /Powerview for a customer and everything was tested and appeared to be working fine . However after installing the November CU we now get the following error :
"The feature Power View is not supported in this edition of Reporting Services"
Initially PowerPivot wasn't working either but that got resolved after re-installing the rssharepoint and sppowerpivot msi files. Has anyone faced this issue?

Hi,
According to your description, my understanding is that the PowerView not work after installing the November CU Updates.
I check the November CU updates, it have no affects on the PowerView or PowerPivot.
The reason for this issue may occur when the PowerPivot Service Application is not running after installing the CU updates.
Here is a detailed article for your reference:
http://support2.microsoft.com/default.aspx?scid=kb;EN-US;2889944
Best Regards
Forum Support
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]
Jerry Guo
TechNet Community Support

Similar Messages

In SharePoinr 2013. Unsupported Reporting Services Functionality The feature: "Power View" is not supported in this edition of Reporting Services.

Hi,
I am getting the below error which click "Create Power View Report" option in "Power Pivot Gallery"
Unsupported Reporting Services Functionality
The feature: "Power View" is not supported in this edition of Reporting Services.
I have uploaded "Power Pivot" excel file in "Power Pivot Gallery".
It is frustrating like anything. Can anyone help on it.
SharePoint 2013. SQL Server 2012. I have enable all the service applications success in CA.
Thanks in Advance.
Poomani Sankaran

Hi,
Please try to download the SP1 Edition of the rsSharePoint.msi
file and install it. You have to install the SP1 edition of RS if you are using SP 2013.
Here is a similar thread for your reference:
http://social.technet.microsoft.com/Forums/en-US/2d2ecfae-b524-43f3-bf93-0bddfe904b75/the-feature-power-view-is-not-supported-in-this-edition-of-reporting-services?forum=sharepointadmin
Best Regards
Dennis Guo
TechNet Community Support

The feature: "Report part gallery" is not supported in this edition of Reporting Services.

Struggling trying to get off the ground on same basic reporting functionality - I have a report that basically just dumps out the contents of a table for now. When I attempt to publish the report, I get "The feature: "Report part gallery"
is not supported in this edition of Reporting Services." for both the single param I am trying to define for the report and the Tablix report part. What
can I do with this version of Reporting Services? Ultimately, I need to create a few very simple reports and then be able to display them in a UI developed in Visual Studio 2013 via a Web Form. It seems that Visual Studio 2013 does not
offer a report viewer so that is another issue entirely (hoping the one for 2011 will work). I am just trying to design and publish a few simple reports right now and can't even get past that right now.

Hello,
What's the version and edition of SSRS did you used?
Report Part Gallery is only available in Standard Edition and above. If you using SSRS express edition, you can try to create a subreport which ccontain the Tablix report part content, and then add the subreport in other reports to meet the similar requirement.
You can refer to the following blog about compare Subreport with Report Part.
http://www.mssqltips.com/sqlservertip/2314/ssrs-report-parts-versus-sub-reports-faq/
As for display SSRS report in Visual Studio, you can using the ReportViewer controls in Visual Studio.
http://msdn.microsoft.com/en-us/library/ms251671.aspx
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SSRS in SharePoint Mode: Reporting Services scale-out deployment is not supported in this edition of Reporting Services [not true]

Hello,
We are experiencing some issues with SharePoint 2013 which is driving me insane.
We have a deployment with two SQL Servers (HA groups) and four SharePoint servers: 2 Application servers, and 2 Web FrontEnd servers.
We installed SSRS for SharePoint in both application servers. The disc I have used is the MSDN image of SQL Enterprise 2012 w/ SP2.
ISO name: en_sql_server_2012_enterprise_edition_with_service_pack_2_x64_dvd_4685849.iso
MD5: 003e14c55fa648ad15f8be1e2439bd06
The installation completes without any problems. We can start the SSRS SharePoint Service in the first application server without any issues. However when we try to start the second one, we get the following error:
Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the sql reporting services service in the farm. The SQL Server Reporting Services cannot be started on
this server unless it is stopped on all other servers in the farm.
Now I am at a loss here. As I mentioned, we have used an image of SQL Server Enterprise. This is the same image we used on other environment, which worked as expected (we got no such error).
I have included the text related to the correlation error from the SP logs below.
Has anyone ever seen this issue before? Very, very strange!
Regards,
P.
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=9.742 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 6t8h High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.23, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Web Controls 88wu High [Forced due to logging gap, Original Level: Verbose] SPGridView.OnRowCreated() - Row.RowType={0}, .RowState={1}, .RowIndex={2}, .DataItemIndex={3} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General af4yd High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.28, Original Level: Verbose] TenantAppEtag record requested but there is no sitesubscription or tenantId for site {0} so we will use the WebApp Id for the cache. 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Asp Runtime aj1kp High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.43 OWSTIMER.EXE (0x1F10) 0x0B40 SharePoint Foundation Health abire Medium Failed to Sql Query data XEvent collector on sql-01. The error is Object reference not set to an instance of an object.
01/29/2015 14:13:26.51 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 7034 Critical An attempt to start/stop instance of service Microsoft SQL Server Reporting Services Shared Service on server SPAP-01 did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.40, Original Level: Verbose] SQL connection time: 0.0821 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88b9 High [Forced due to logging gap, Original Level: Verbose] Determining if the current user is a SharePoint Farm Administrator 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject ReportingWebServiceInstance. Version: 1118292 Ensure: False, HashCode: 52212853, Id: 5a4058b9-2ecd-421e-b9ae-818bbc57c8c6, Stack: at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.57, Original Level: Verbose] SQL connection time: 0.0965 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88ch High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.84, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 8nca Medium Application error when access /_admin/Server.aspx, Error=Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.87 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Runtime tkau Unexpected System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.89 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,2 agb9s,9 b4ly,309 8xqz,331 8nca,15 tkau,8 ajlz0 6f83e49c-cc03-d049-90f4-81439b542cf8
01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48)). Execution Time=712.2145 6f83e49c-cc03-d049-90f4-81439b542cf8

Hi Wynn,
I appreciate your attempt to address my concerns, but even your reply seems to ignore the fact that I have not only provided the name of the ISO, but the MD5 checksum of the ISO as well. Also this is the first time I am being asked to double-check the version
of SSRS. The first reply I got to my query simply disregarded the version mismatch.
As per your request, I have checked under the folder you have specified (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices\LogFiles), but unfortunately there are no files under this folder in neither of my two application
servers.
We only have logfiles under C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS
Is there a way I can turn those logs on?
In the meantime, we run the SQL Server Discovery tool and I have attached the summary for you to see that it finds the Enterprise Edition of SQL Server:
Final result: Passed
Exit code (Decimal): 0
Start time: 2015-01-29 15:17:44
End time: 2015-01-29 15:17:56
Requested action: RunDiscovery
Machine Properties:
Machine name: SP-AP-02
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2012 Management Tools - Basic 1033 Enterprise Edition 11.2.5058.0 No Yes
SQL Server 2012 Reporting Services - SharePoint 11.2.5058.0 No Yes
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation edition:
User Input Settings:
ACTION: RunDiscovery
CONFIGURATIONFILE:
ENU: true
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
QUIET: false
QUIETSIMPLE: false
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150129_151743\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
The \Setup Bootstrap\Log folder also has several log files that indicates the version of SQL Server that has been installed. For instance here is an entry of the Detail.txt file:
(01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : CreateSKUCookie succeeded, new checksum is 195 bytes.
(01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : Updated skuCheckSumInfo -> daysLeft=0 sqlEdition='ENTERPRISE' (0x6B9471A8) fileTimeInstalled=0 timeBombValue=0 editionType='Enterprise Edition' edition='Enterprise Edition' writeEditionStrings='True' checkSum=195bytes
(01) 2015-01-28 19:10:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
I hope this help while we don't have any logfiles in the folder you asked me to look into. Please advise me as in how to proceed if logfiles must be generated.
Regards,
P.

SQL 2012 SP1 Enterprise (SSRS in SharePoint mode): Reporting Services scale-out deployment is not supported in this edition of Reporting Services

Hello,
SSRS in SharePoint mode is driving me insane.
We are recreating a SharePoint 2013 (SP1) farm in a test environment with the following set-up:
2 SP Web FrontEnds
2 SP Application Servers
1 SQL Server
At both SP APP Servers, we installed SSRS (SQL 2012 Enterprise w/ SP1) in SP integrated mode.
We managed to start the SSRS SP service at the first SP APP Server. However when we try to start it on the second APP Server, we get the following error:
"Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot
be started on this server unless it is stopped on all other servers in the farm. "
Now I can't stress this enough: This is a SQL Server 2012 SP1 Enterprise. This is the image we got from our MSDN subscription. There is no mistake here.
Could someone please advise why SP might think this version of SSRS is not the correct one?
Thanks in advance for your help.
Regards,
P.

Hello,
I'm afraid that is not it.
After a long, frustrating and strenuous investigation and troubleshooting, we found the problem.
The problem is the current ISO for SQL Server 2012 Enterprise SP1 (x64) found at MSDN. Bear in mind that we downloaded this ISO from MSDN about a month ago.
As soon as we recreated the environment using the ISO for SQL Server 2012 Enterprise SP2 (x64) found at MSDN, everything worked as expected -- and that includes running more than one SSRS in SharePoint mode.
Also bear in mind that we tried updating the SQL SP1 install with SP2 and subsequent cumulative updates but that never fixed the problem.
There is something fundamentally wrong with that ISO with SP1 slipstreamed in it that no matter the subsequent updates installed, SSRS in SharePoint mode fails to work properly on a multi-server environment. We went as far as SP2 with CU3 and nothing seemed
to fix the problem. And yes, we also performed manual updates to the SSRS and PowerPivot SharePoint MSI add-ins.
I am shocked and distraught to find out that I lost hours of work due to a dodgy ISO image.
Regards,
P.

The feature: "The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services.

Hello all,
I have SQL express 2014 advance edition installed ..
and i am connecting SQl server 2008 r2 instance which is in network
while creating datasource in Reportserver which has Express installed ..
got this error ..
please help me how to connect to remote server
Dilip Patil..

Error message says it all.
With SQL Express, Data source should be local SQL DB.
With SQL Enterprise, Standard, BI edition, you can create Data soruce which are hosted on other servers.
Please refer similar thread:
https://social.msdn.microsoft.com/Forums/en-US/c0468e3f-bad7-47a7-a695-75c13762280a/the-feature-the-edition-of-reporting-services-that-you-are-using-requires-that-you-use-local-sql?forum=sqlreportingservices
Cheers,
Vaibhav Chaudhari
[MCTS],
[MCP]

Scale-out deployment is not supported in this edition of reporting services

Can the "scale-out deployment" option be turned off so that I can migrate SSRS databases from Enterprise edition to Standard? After I attached databases from a SSRS 2005 Enterprise to SSRS 2012 Standard I am getting an error about
scale-out deployment not supported. Any way around this so I can migrate the databases, bringing the reports and report subscriptions to the new SSRS instance?
Lee Markum

Hi Lee,
From the
document, we can know that Scale out deployment is a feature that only supported in Enterprise and Business Intelligence editions in SQL Server 2012.
In order to fix this issue, we can refer to the similar thread post by Ben:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/8eebf25f-2c40-40d3-9bb7-bb481fdafc12/is-this-a-scaleout-deployment-?forum=sqlreportingservices
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet 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

When trying to play videos I get the message "requested URL is not supported on this network" how do I fix this?

I receive the error "requested URL is not supported on this network" when trying to play videos on my iPhone. Can you please advise how to fix this problem?

Hi,
You will need to re-instal iCal as an optional install from your OSX installer DVDs. Then run the Mac OS X 10.5.8 Combo Update.
Best wishes

Error message "The currently attached accessory is not supported by this iPod" is shown when connected to my Zeppelin Air Dock.

I have 2 iPods, one is a 60GB Classic formatted to Mac the other is a 80GB Classic formatted to Windows. When either is connected to my Zeppelin Air Dock, a message appears on the iPod saying "The currently attached accessory is not supported by this iPod"
I have updated the firmware on the Zeppelin and have the latest updates on each of the iPods.
The Zeppelin works fine and connects to the computer and laptop without issues.

I'm having the same problem, it just started today. I've been running w/ the nike+ sensor and receive w/ my iPod nano for 6 months, logging 75 runs, so don't understand why I'm getting this error now.
Can someone please reply w/ how to resolve this issue? I have Nike+ challenges coming up soon that I can't miss. Thanks!

An error occurred during local report processing.The definition of the report '' is invalid.The definition of this report is not valid or supported by this version of Reporting Services. he report definition may have been created with a later version of R

Hi,
I am trying to create rdlc file programmatically. Using Memory Table as dataset. Here is my code
' For each field in the resultset, add the name to an array listDim m_fields AsArrayList
  m_fields = NewArrayList()
  Dim i AsIntegerFor i = 0 To tbdataset.Tables(0).Columns.Count - 1
      m_fields.Add(tbdataset.Tables(0).Columns(i).ColumnName.ToString)
  Next i
  'Create Report 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' Open a new RDL file stream for writingDim stream AsFileStream
  stream = File.OpenWrite("D:\MyTestReport2.rdlc")
  Dim writer AsNewXmlTextWriter(stream, Encoding.UTF8)
  ' Causes child elements to be indented
  writer.Formatting = Formatting.Indented
  ' Report element
  writer.WriteProcessingInstruction("xml", "version=""1.0"" encoding=""utf-8""")
  writer.WriteStartElement("Report")
  writer.WriteAttributeString("xmlns", Nothing, "http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition")
  writer.WriteAttributeString("xmlns:rd", "http://schemas.microsoft.com/SQLServer/reporting/reportdesigner")
  writer.WriteStartElement("ReportSections")
  writer.WriteStartElement("ReportSection")
  writer.WriteElementString("Width", "11in")
  writer.WriteStartElement("Body")
  writer.WriteElementString("Height", "5in")
  writer.WriteStartElement("ReportItems")
  writer.WriteStartElement("Tablix")
  writer.WriteAttributeString("Name", Nothing, "Tablix1")
  writer.WriteElementString("Top", ".5in")
  writer.WriteElementString("Left", ".5in")
  writer.WriteElementString("Height", ".5in")
  writer.WriteElementString("Width", (m_fields.Count * 1.5).ToString() + "in")
  writer.WriteStartElement("TablixBody")
  ' Tablix Columns
  writer.WriteStartElement("TablixColumns")
  ForEach fieldName In m_fields
      writer.WriteStartElement("TablixColumn")
      writer.WriteElementString("Width", "1.5in")
      writer.WriteEndElement() ' TableColumnNext fieldName
  writer.WriteEndElement() ' TablixColumns' Header Row
  writer.WriteStartElement("TablixRows")
  writer.WriteStartElement("TablixRow")
  writer.WriteElementString("Height", ".25in")
  writer.WriteStartElement("TablixCells")
  ForEach fieldName In m_fields
      writer.WriteStartElement("TablixCell")
      writer.WriteStartElement("CellContents")
      writer.WriteStartElement("Textbox")
      writer.WriteAttributeString("Name", Nothing, "Header" + fieldName)
      ' writer.WriteAttributeString("CanGrow",  True)' writer.WriteAttributeString("Keeptogether", True)
      writer.WriteStartElement("Paragraphs")
      writer.WriteStartElement("Paragraph")
      writer.WriteStartElement("TextRuns")
      writer.WriteStartElement("TextRun")
      writer.WriteElementString("Value", fieldName)
      writer.WriteStartElement("Style")
      writer.WriteElementString("TextDecoration", "Underline")
      writer.WriteElementString("PaddingTop", "0in")
      writer.WriteElementString("PaddingLeft", "0in")
      writer.WriteElementString("LineHeight", ".5in")
      ''writer.WriteElementString("Width", "1.5in")''writer.WriteElementString("Value", fieldName)
      writer.WriteEndElement() ' Style
      writer.WriteEndElement() ' TextRun
      writer.WriteEndElement() ' TextRuns
      writer.WriteEndElement() ' Paragraph
      writer.WriteEndElement() ' Paragraphs
      writer.WriteEndElement() ' TexBox
      writer.WriteEndElement() ' CellContents
      writer.WriteEndElement() ' TablixCellNext
  writer.WriteEndElement() ' TablixCells
  writer.WriteEndElement() ' TablixRow'writer.WriteEndElement() ' TablixRows          Do not close Rows tag here colse it after details'End of Headers'Details Rows'writer.WriteStartElement("TablixRows")         Since Rows tag in header is not closed not need to open fresh tag
  writer.WriteStartElement("TablixRow")
  writer.WriteElementString("Height", ".25in")
  writer.WriteStartElement("TablixCells")
  ForEach fieldName In m_fields
      writer.WriteStartElement("TablixCell")
      writer.WriteStartElement("CellContents")
      writer.WriteStartElement("Textbox")
      writer.WriteAttributeString("Name", Nothing, fieldName)
      '  writer.WriteAttributeString("CanGrow", True)'  writer.WriteAttributeString("Keeptogether", True)
      writer.WriteStartElement("Paragraphs")
      writer.WriteStartElement("Paragraph")
      writer.WriteStartElement("TextRuns")
      writer.WriteStartElement("TextRun")
      'writer.WriteElementString("Value", fieldName)
      writer.WriteElementString("Value", "=Fields!" + fieldName + ".Value")
      writer.WriteStartElement("Style")
      writer.WriteElementString("TextDecoration", "Underline")
      writer.WriteElementString("PaddingTop", "0in")
      writer.WriteElementString("PaddingLeft", "0in")
      writer.WriteElementString("LineHeight", ".5in")
      ''writer.WriteElementString("Width", "1.5in")''writer.WriteElementString("Value", fieldName)
      writer.WriteEndElement() ' Style
      writer.WriteEndElement() ' TextRun
      writer.WriteEndElement() ' TextRuns
      writer.WriteEndElement() ' Paragraph
      writer.WriteEndElement() ' Paragraphs
      writer.WriteEndElement() ' TexBox
      writer.WriteEndElement() ' CellContents
      writer.WriteEndElement() ' TablixCellNext
  writer.WriteEndElement() ' TablixCells
  writer.WriteEndElement() ' TablixRow
  writer.WriteEndElement() ' TablixRows'End of Details Rows
  writer.WriteEndElement() ' TablixBody
  writer.WriteStartElement("TablixRowHierarchy")
  writer.WriteStartElement("TablixMembers")
  writer.WriteStartElement("TablixMember")
  ' Group
  writer.WriteElementString("KeepWithGroup", "After")
  writer.WriteEndElement() ' TablixMember' Detail Group
  writer.WriteStartElement("TablixMember")
  writer.WriteStartElement("Group")
  writer.WriteAttributeString("Name", Nothing, "Details")
  writer.WriteEndElement() ' Group
  writer.WriteEndElement() ' TablixMember
  writer.WriteEndElement() ' TablixMembers
  writer.WriteEndElement() ' TablixRowHierarchy
  writer.WriteStartElement("TablixColumnHierarchy")
  writer.WriteStartElement("TablixMembers")
  'writer.WriteStartElement("TablixMember")ForEach fieldName In m_fields
      writer.WriteStartElement("TablixMember")
      writer.WriteEndElement() ' TablixMemberNext' writer.WriteEndElement() ' TablixMember
  writer.WriteEndElement() ' TablixMembers
  writer.WriteEndElement() ' TablixColumnHierarchy
  writer.WriteElementString("DataSetName", "tbdataset")
  writer.WriteEndElement() ' Tablix
  writer.WriteEndElement() ' ReportItems
  writer.WriteEndElement() ' Body
  writer.WriteStartElement("Page")
  ' Page Header Element
  writer.WriteStartElement("PageHeader")
  writer.WriteElementString("Height", "1.40cm")
  writer.WriteStartElement("ReportItems")
  writer.WriteStartElement("Textbox")
  writer.WriteAttributeString("Name", Nothing, "Textbox1")
  writer.WriteStartElement("Paragraphs")
  writer.WriteStartElement("Paragraph")
  writer.WriteStartElement("TextRuns")
  writer.WriteStartElement("TextRun")
  writer.WriteElementString("Value", Nothing, "ABC CHS.")
  writer.WriteEndElement() ' TextRun
  writer.WriteEndElement() ' TextRuns
  writer.WriteEndElement() ' Paragraph
  writer.WriteEndElement() ' Paragraphs
  writer.WriteEndElement() ' TextBox
  writer.WriteEndElement() ' ReportItems
  writer.WriteEndElement() ' PageHeader
  writer.WriteEndElement() ' Page
  writer.WriteEndElement() ' ReportSection
  writer.WriteEndElement() ' ReportSections' DataSources
  writer.WriteStartElement("DataSources")
  writer.WriteStartElement("DataSource")
  writer.WriteAttributeString("Name", Nothing, "tbdata")
  writer.WriteStartElement("DataSourceReference")
  writer.WriteEndElement() ' DataSourceReference
  writer.WriteEndElement() ' DataSource
  writer.WriteEndElement() ' DataSources'DataSet
  writer.WriteStartElement("DataSets")
  writer.WriteStartElement("DataSet")
  writer.WriteAttributeString("Name", Nothing, "tbdataset")
  writer.WriteStartElement("Query")
  writer.WriteElementString("DataSourceName", Nothing, "tbdata")
  'writer.WriteElementString("CommandText", Nothing, "/* Local Query */")
  writer.WriteElementString("CommandText", Nothing, "TableDirect")
  writer.WriteEndElement() ' Query'Fields
  writer.WriteStartElement("Fields")
  ForEach fieldName In m_fields
      writer.WriteStartElement("Field")
      writer.WriteAttributeString("Name", Nothing, fieldName)
      writer.WriteElementString("DataField", fieldName)
      writer.WriteElementString("rd:TypeName", fieldName.GetType.ToString)
      writer.WriteEndElement() ' FieldNext
  writer.WriteEndElement() ' Fields' rd datasetinfo
  writer.WriteEndElement() ' DataSet
  writer.WriteEndElement() ' DataSets
  writer.WriteEndElement() ' Report' Flush the writer and close the stream
  writer.Flush()
  stream.Close()
  'Convert to StreamDim myByteArray AsByte() = System.Text.Encoding.UTF8.GetBytes("D:\MyTestReport2.rdlc")
  Dim ms AsNewMemoryStream(myByteArray)
  'Supply Stream to ReportViewer
  ReportViewer1.LocalReport.LoadReportDefinition(ms)
  ReportViewer1.LocalReport.Refresh()When I open rdlc in designer I get following error"Data at the root level is invalid."When I run the aspx I get following error
An error occurred during local report processing.
The definition of the report '' is invalid.
The definition of this report is not valid or supported by this version of Reporting Services.
The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas.
Details: Data at the root level is invalid. Line 1, position 1.
Can anybody guide me?

Hi Wendy Fu,
Thanks for your feed back. I could see Microsoft.ReportViewer.ProcessingObjectModel.dll to add as reference to my project. Actually I can open generated rdlc in designer, at run time I get error. I could not make out where is the exact mistake out of three
options flashed.
The definition of this report is not valid or supported by this version of Reporting Services.
The report definition may have been created with a later version of Reporting Services
or contain content that is not well-formed or not valid based on Reporting Services schemas
Details: Data at the root level is invalid
My web config has following references
<add assembly="Microsoft.ReportViewer.WebForms, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/>
<add assembly="Microsoft.ReportViewer.Common, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/>
May be I have to change these versions to 9 or 10.
First I will try adding Microsoft.ReportViewer.ProcessingObjectModel.dll .
Once thanks for your reply.
Races

When i try to open the iPhoto app, i getting a message "you can't open the application because it is not supported on this type of mac"

when i try to open the iPhoto app, i getting a message "you can't open the application because it is not supported on this type of mac"

To re-install iPhoto
1. Put the iPhoto.app in the trash (Drag it from your Applications Folder to the trash)
2. Download it from the App Store to reinstall It's on your Purchases List* there.
For older versions that have been installed from Disk you'll need these additional steps:
2a: On 10.5: Go to HD/Library/Receipts and remove any pkg file there with iPhoto in the name.
2b: On 10.6: Those receipts may be found as follows: In the Finder use the Go menu and select Go To Folder. In the resulting window type
/var/db/receipts/
2c: on 10.7 or later they're at
/private/var/db/receipts
A Finder Window will open at that location and you can remove the iPhoto pkg files.
3. Re-install.
If you purchased an iLife Disk, then iPhoto is on it.
If iPhoto was installed on your Mac when you go it then it’s on the System Restore disks that came with your Mac. Insert the first one and opt to ‘Install Bundled Applications Only.
*Sometimes iPhoto is not visible on the Purchases List. it may be hidden. See this article for details on how to unhide it.
http://support.apple.com/kb/HT4928
One question often asked: Will I lose my Photos if I reinstall?
iPhoto the application and the iPhoto Library are two different parts of the iPhoto programme. So, reinstalling the app should not affect the Library. BUT you should always have a back up before doing this kind of work. Always.

Firefox 4 unable to use on imac G5 ( without intel chips ), get messageYou can't open the application bcz it is not supported on this architecture.

My iMac G5 without intel chips, Mac OS X 10.5.8.
using Firefox 364 no problem at all.
But unable to install Firefox 4 on it, prompt "You can't open the application because it is not supported on this architecture"

Firefox 4 requires at least OS X 10.5 and an Intel Mac.
There is a third-party version of Firefox 4 that works on PPC Macs, for details see http://www.floodgap.com/software/tenfourfox

What does "you cannot open the application because it is not supported on this architecture" mean?

What does "you cannot open the application because it is not supported on this architecture" mean?

well my mac lion (10.4.11) will run minecraft.jar, but runs very slow , i tried downloading minecraft.zip it showed the mc logo with a x on it, i tried opening it, and it said it cant open it because there is no application to open it, do i need a higher version of mac? mainly leopard or snow leopard? This is what it looks like

The attached iPod model is not supported by this application

I just bought a 20G color iPod. I spoke w/ the Apple tech support & I needed service pack 2. I downloaded it. I didn't have a USB 2.0 port then I installed one. I downloaded the latest Apple updater software 2005-06-26 then I tried the even later version 2005-09-06. When I go into updater, it says it is "initializing" and then says "the attached iPod model is not supported by this application." Reformat and restore are both grayed out. iPod doesn't show up in iTunes and doesn't transfer my library. I just got back from the Apple Store and the suppossed "genius" said the iPod is fine and it is my computer. WHAT is wrong with my computer?

Brad,
you ought a little bit more descriptive! What Version of iTunes are you using? Check the software version of your iPod (if it even has one yet) under Settings-About. Your iTunes and iPod software have to be compatible. If you're running 4.9 you need 2005-06-26. Close iTunes and leave it alone. Deinstall all iPod related software, clean the registry if you want (I don't think this is so much necessary for the iPod software). Then install 2005-06-26 again on your computer first!! Don't connect the iPod. After having installed it, open the Updater, then connect. Before you do that and since you don't have any music on the iPod reset it to factory settings under Settings-Reset all settings. Or at least reset it with pushing Menue and the center knob at once. Many possibilities I know, but either one will work...after that it will remain seen by iTunes and you're a lucky guy (hopefully).
Best regards
Roman

"The feature Power View is not supported in this edition of Reporting Services" after installation of November CU for SharePoint

Similar Messages

Maybe you are looking for