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
Similar Messages
-
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-81439b542cf8Hi 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. -
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: "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 -
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 -
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 SankaranHi,
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 -
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] -
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 -
What does "Scale out deployment (Web Farms)" mean for SP2013 and SQL 2012 SSRS?
Dear community,
in the
Feature List of Reporting Services 2012, it's written that "Scale out deployment (Web farms)" is not possible for SQL 2012 Standard edition. However, does this relate as well to SSRS in SP-integrated mode, or only to native mode?
In other words: is it possible to deploy SSRS using SQL 2012 STANDARD on more than one server in a SP2013 farm?
And just to be sure: am I right to assume that in both cases, you can create multiple SSRS Svc Applications (be they all running on the same server) and assign them to different web applications (through their proxy groups)?
Cheers,
CHi CHinz,
According to your description, you want to configure scale-out deployment for SQL Server Reporting Services 2012 standard edition. Right?
As you can see in the msdn liabrary, for SQL Server 2012, scale-out deployment is only supported in Enterprise and Business Intelligence editions. This is related to both native mode and sharepoint integrated mode.
It's not supported to deploy a SSRS 2012 standard edition instance on more than one server.
Since scale-out deployment is for different report server instance to share one report server database. You can use different web applications to access the same report in different report server instances.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou -
Web Deploy error - "This method is not supported by this class"
I have an MVC project which I am trying to deploy to one of our internally-hosted web front end servers via a TFS build process. Our server hosts the MS Deploy service, and other solutions deploy without problems to the same box. The parameters for the build
process are as follows:
/p:DeployOnBuild=True /p:DeployTarget=MsDeployPublish /p:MSDeployPublishMethod=WMSVC /p:MsDeployServiceUrl=https://<server>:8172/msdeploy.axd /p:DeployIISAppPath="<internal.site.com>" /p:username=<username> /p:password=<password>
/p:IncludeIisSettingsOnPublish=false /p:AllowUntrustedCertificate=True /p:OutputPath=bin\ /p:SkipExtraFilesOnServer=True /p:VisualStudioVersion=11.0
The error message I receive at the point the build reaches the deployment activity is:
Web deployment task failed. (Could not complete the request to remote agent URL 'https://<server>:8172/msdeploy.axd?site=<internal.site.com>'.)
Could not complete the request to remote agent URL 'https://<server>:8172/msdeploy.axd?site=<internal.site.com>'.
The request was aborted: The request was canceled.
This method is not supported by this class.
We've found
this StackOverflow post which describes the same error we're experiencing, however the suggested solution is something we already do in our server configuration, so this doesn't resolve the issue for us.
Has anyone seen this error before, or is able to make any suggestions why it is happening?Hi Matt,
You have to have a look in the build log then copy the command that is under Run MSBuild node and executed it on the build agent.
You should find something like below:
C:\Program Files (x86)\MSBuild\12.0\bin\amd64\MSBuild.exe /nologo /noconsolelogger "C:\Builds\....sln" /nr:False /fl /flp:"logfile=C:\Builds\...log;encoding=Unicode;verbosity=normal" /p:SkipInvalidConfigurations=true /p:CreatePackageOnPublish=true /p:DeployOnBuild=true /p:SkipExtraFilesOnServer=True /m /p:OutDir="C:\Builds\...\bin\\" /p:Configuration="DEV" /p:Platform="Any CPU" /p:VCBuildOverride="C:\Builds\....sln.Any CPU.DEV.vsprops" /dl:WorkflowCentralLogger,"C:\Program Files\Microsoft Team Foundation Server 12.0\Tools\Microsoft.TeamFoundation.Build.Server.Logger.dll";"Verbosity=Normal;BuildUri=vstfs:///Build/Build/31630;IgnoreDuplicateProjects=False;InformationNodeId=14;TargetsNotLogged=GetNativeManifest,GetCopyToOutputDirectoryItems,GetTargetPath;LogProjectNodes=True;LogWarnings=True;TFSUrl=http://...-tfs:8080/tfs/...;"*WorkflowForwardingLogger,"C:\Program Files\Microsoft Team Foundation Server 12.0\Tools\Microsoft.TeamFoundation.Build.Server.Logger.dll";"Verbosity=Normal;" /p:BuildId="aa2d3857-27e9-4854-b44f-4ca625ccd786,vstfs:///Build/Build/31630" /p:BuildLabel="..._2015.02.27.2" /p:BuildTimestamp="Fri, 27 Feb 2015 11:16:41 GMT" /p:BuildDefinition="..."
Daniel -
"Charging is not supported with this acessory" opped up out of the blue
I left my phone charging after i woke up, took it off when it was 100% and went to work. When i came back home, i plugged it again and the "Charging is not supported with this acessory" error popped up. I was using the same cable and wall charger i always used, the ones that came with my 3GS, and they were working for sure, since i had them charge my phone sooner today. When i plugged it on my PC, it synced but the charging error persisted. Tried to reboot the phone, alredy did it 4 times, no sucess either.
I tried another 3GS cable and wall charger, up to no succes. Now, after these trials, iTunes isn't even recognizing my 3GS and i'm out of ideas.
Can i get any help or will i have to make a trip to appstore?Dusted off both ends of the cable, the iPhone charger hole, the carger USB hole, all my USB ports, cleaned everything, still no sucess.
Tried my cable and charger with another iPhone 3GS, worked normally, switched to mine, boom, the same error.
I'm sure that the problem is with my phone, but i want to know what is causing this problem or what could possibly solve it? -
SQL blocking during removal of report server from Scale-out-Deployment
I recently removed a 2012 reporting service instance from the Reporting Service Scale-out-Deployment. After I removed the server, there was a lot of blocking on the report DB for about 30 minutes. My report DB is on the same SQL instance as
my TFS databases and the blocking caused web access for TFS and Visual Studio connections to fail during check-out/check-in.
Should I expect blocking to happen every time I remove a report server out of the Scale-out-Deployment?
Thanks,
KAHi KA,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support -
SQL 2008 R2 Setup Scale out deployment issue
Hi All.
Just trying to add a new server to an existing SSRS installation in the form of scale out deployment, the installation is done the instance names called the same and now on the new server, within the scale out deployment section, I can see its status as
joined. On the old originals server, it doesn’t show the new server as joined.
When I run the command RSKeyMgmt.exe –l
I get the message
Unable to locate the Report Server Windows service for instance MSSQLSERVER.
When I go to the server i.e the new one and try navigate to the reports section. I get this error.
The permissions granted to user XXXXX are insufficient for performing this operation. (rsAccessDenied)
On the Report manager Section within Reporting services configuration manager, when I goto the link it simply prompts me with a username/password prompt and it never works even after supplying the correct credentials.
It appears as though I set it up such that it joined the scale out deployment before backing up the encryption keys from the existing server and then restoring it onto the new one. What I am now trying to do is delete the new server entry and start the process
again to restore the encryption key and then only join the scale out deployment.
The issue here is that RSKeyMgmt.exe –l isn’t showing that the server is registered.Hi MrfLinstone,
According to your description, you get the above error when navigate to reports. Right?
Based on the error message, you may not assign the permission to the current use for accessing the target report server. So please follow the steps below to create a system-level role assignment.
If necessary, log on as a local administrator.
Open a browser window and type the Report Manager URL to start the application. For example http://<server name>/reportserver
Click Site Settings at the top of the page.
Click the Security tab at the side of the page. This page shows all system-level role assignments that are currently defined. On a new report server installation, only the two predefined roles, System Administrator and System User, are visible.
There is one built-in role assignment that is created automatically; it maps the built-in local administrators group to the System Administrator role
Click New Role Assignment.
In Group or user name, specify a domain group account that includes all of the users who require permissions to view report server content and subscribe to reports. Specify the account in this format:
domain\group. The account should be in the same domain or in a trusted domain. If you do not have a domain group that fits this description, you can specify individual domain user accounts instead.
Select System User.
Click OK.
Click New Role Assignment again.
In Group or user name, type the name of a domain user account for a user who has administrative responsibilities for this report server. Specify the account in this format:
domain\user. The account should be in the same domain as the report server or in a trusted domain.
Select System Administrator.
Click OK.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou -
SQL Server 2012 - reporting services - scale-out-deployment
I am facing an issue which is related to a scale out deployment. I am deploying a FIM reporting based on System Center and I have 2 sql servers in this scenario.
Now the problem is that Reporting services configuration manager (from sql1) says that the scale out deployment has been established. Sql1 is joined and sql2 is waiting to join. I don't know why the servers has been appeared under the scale out deployment
because I don't want to create the scale out deployment.
So how can I remove the scale out deployment without breaking anything?
Also if I look at the Reporting services configuration manager from sql2 the scale out deployment panel is empty like it should be.Hi 2xTsei,
According to your description, two report server instances have been configured to a scale-out deployment, while you haven’t performed this configuration.
In Reporting Services, a report server scale-out deployment is two or more report server instances that share a single report server database. To finish this configuration, we should use Reporting Services Configuration tool to connect to each report server
to the shared database and join a new report server instance. So the scale-out deployment shouldn’t be configured automatically. It’s likely that someone has configured this deployment who can access those two instances.
Reference:
How to: Configure a Report Server Scale-Out Deployment (Reporting Services Configuration)
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support
Hi and thanks for your reply.
That is a little bit weird because I am 100% sure that we didn't manually configured scale out deployment. I need to inspect this more. -
IE11/Win 8.1 error 'Your client does not support opening this list in windows explorer'
I hoping someone might be able to help with this frustrating issue.
I work on a project where we are using various versions of on-line SharePoint (2007/O365). In order to quickly drag and drop folders we need to often open the document libraries by using the 'open in windows explorer view'.
Using the same device, on occassion this works. But often it gives a rather unhelpful message 'Your client does not support opening this list in Windows Explorer'.
I've searched for this issue over the net and confirm that the sites are added to the 'trusted' sites area and that the 'remember you credientials' is checked on logging in.However, the searches do not seem to apply to IE11/Win8.1 or on-line version of sharepoint
(the suggested hot fix is not suitable)
Only this morning, using the same device I was able, for a short while to open in explorer view, and then for no apparent reason, it began to display the error message. I had changed nothing regarding settings or even closed the browser.
Do you have any support/ideas/fixes on how to resolve this.
Many thanks
valHi Val,
sometimes an answer can be found on the internet by typing the error message from your computer into your favourite search engine.
eg.
http://www.bing.com/search?q=your+client+does+not+support+opening+this+list+in+windows+explorer&form=IE10TR&src=IE10TR&pc=HPNTDFJS
see
http://blogs.technet.com/b/asiasupp/archive/2011/06/13/error-message-quot-your-client-does-not-support-opening-this-list-with-windows-explorer-quot-when-you-try-to-quot-open-with-explorer-quot-on-a-sharepoint-document-library-in-office-365-site.aspx
follow the directions given above.... you need to add the domains to your Intranet sites list, not the Trusted sites list.
Perhaps you already have it mapped to your intranet zone....in which case make sure that you have unchecked "Enable Enhance Protected Mode" on the Intranet zone dialog in Internet Options.
If this is happening 'randomly' on client machines, then users are probably changing their internet security settings in Internet Options. Ensure they are accepting the default.... Internet Options>Security tab, click "Reset all zones to default".
Consult with your system administrators to find out if they are applying a custom security template for the Intranet zone... It may be removing the sharepoint domains from the client Intranet zone's domains lists.
HTH.
Rob^_^
Maybe you are looking for
-
MacBook pro, 8GB, OSX Yosemite I cannot open iPhoto after latest apple upgrade. Getting message latest iPhoto version is not available in the US.
-
Reloading a database in SAP R/3 4.6C on Windows
Hello Anyone know if is possible Reloading a database SAP R/3 4.6C Windows / Oracle, using an specific .R3S??? I have seen there is service DBRELOAD.R3S but is for Unix, ... There is ahother one for Windows? Thanks and regards Javier
-
Hello, I placed a label in the form. But I am unable to drag and place a node from data schema to the label. Please, tell me a solution.
-
How to invoke odi scenario from bpel without passing plain text password
Hi We have following requirement,we would like to invoke odi scenario from oracle bpel process.But one problem is we dont want to pass the odi password as plain text.Please let me know how do i achive this task. Thanks Baji
-
Hi all, I converted to an IMAP Gmail account two weeks ago, and became hooked to the instantaneous mail downloads thanks to the IDLE command. Now, all of a sudden, emails no longer arrive unless I click on "Get Mail." I have not changed my preference