SQL Server 2012 Reporting services Report Builder ClickOnce in SharePoint integrated mode

Hi
I've installed SSRS 2012 in Integrated Mode with SharePoint 2013.
I've created RS Application, I have the Content types for Report Builder Report but when I try to create a new Report Builder Report from a document library (using ribbon) it try to lauch the following url
http://sp2013/bi/_layouts/15/ReportServer/RSAction.aspx?RSAction=ReportBuilder&FileUrl=http://sp2013/_layouts/15/ReportServer/rs.rsapplication&SaveLocation=http%3A%2F%2Fsp2013%2Fbi%2FDocuments&Source=http%3A%2F%2Fsp2013%2Fbi%2FDocuments%2FForms%2FAllItems%2Easpx
which gives an 404 Not found error
I've installed Report Builder 3.0 as standalone because from SQL installation I didn't get an Report Builder
What else should I do ?
I've noticed that ReportBuilder_3.....application is in webservices folder of sharepoint
Please help
Sorin Sandu

Hi Sorin,
SQL Server 2012 Reporting Services (SSRS) includes stand-alone and ClickOnce versions of Report Builder. The ClickOnce version can be used with Reporting Services installed in native or SharePoint integrated mode. For more information about how to start
Report Builder, please see:
http://msdn.microsoft.com/en-us/library/ms159221(v=sql.110).aspx
Reference:
SharePoint 2010 – SQL 2012 Reporting Services
SharePoint 2010 - SQL 2012 Reporting Services Part 2
Hope this helps.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Similar Messages

Microsoft OLE DB Provider for SQL Server 2012 Analysis Services Error Code = 0x80040E05

I've been running a package for 6 months without any issues that pulls data from a cube via MDX and moves it to a database.
We've recently moved to a new server x64 and the connections all succeed but at runtime (in 64 = T&F) I get the following error:
[SRC AdExchange [87]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E05.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x00000001 Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
[SSIS.Pipeline] Error: SRC AdExchange failed the pre-execute phase and returned error code 0xC0202009.
I've installed SQL_AS_OLEDB, SQL_AS_ADOMD from Microsoft® SQL Server® 2012 SP1 Feature Pack
Why is my connection failing?

The server has a 10Gbps network connection.
I've installed CU6 for SQL Server 2012 SP1
http://support.microsoft.com/kb/2874879/en-us#hfi
I'm still getting the same error at runtime in BIDS:
[SRC AdExchange [87]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E05.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x00000001 Description: "Error Code = 0x80040E05, External Code = 0x00000000:.".
[SSIS.Pipeline] Error: SRC AdExchange failed the pre-execute phase and returned error code 0xC0202009.
Looking at the errorlog, everything looks normal until:
Launched startup procedure 'sp_ssis_startup'.
Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
Using 'xplog70.dll' version '2011.110.2100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
AppDomain 2 (SSISDB.dbo[runtime].1) created.
Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).
Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (SSISDB.dbo[runtime].1).
AppDomain 3 (master.sys[runtime].2) created.
Software Usage Metrics is enabled.
SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
Service Broker manager has shut down.
Error: 17054, Severity: 16, State: 1.
The current event was not reported to the Windows Events log. Operating system error = (null). You may need to clear the Windows Events log if it is full.
.NET Framework runtime has been stopped.
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXX.com ] for the SQL Server service. Error: 0xffffffff, state: 63. Administrator should deregister this SPN manually to avoid client authentication
errors.
The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/XXXXXXXXXX.com:1433 ] for the SQL Server service. Error: 0xffffffff, state: 63. Administrator should deregister this SPN manually to avoid client authentication
errors.
Wondering about the unsafe assembly in SSIS and deregistering the SPN..
Anyone have any ideas on how to resolve this?
Thanks!

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005 Description: "Internal error: An une

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005
Description: "Internal error: An unexpected error occurred (file 'pcxmlacommon.cpp', line 43, function 'PCFault::RaiseError').
I'm getting above error in the pre- execute phase of a DFT when I'm trying to fetch data from a SSAS cube using mdx query.
I'm using OLE DB provider for connecting to cube.
I got one resolution for Error Code 0X8004005, which asked me to add 'Format= Tabular' in cube's connection string. It does not seem to work either. Can any one help me out on this???

You are probably missing an update.
I saw a MS Connect post https://connect.microsoft.com/SQLServer/feedback/details/250920/error-using-oledb-or-datareader-to-get-analysis-services-data where that suggestion was proposed as a fix, but is for an older SQL Server version.
So do there is a question if you pull data from SQL Server 2012 SSAS using SSIS 2012 (so no other build is involved).
Arthur My Blog

RDL Reports are not working after installing SQL Server 2012 Service Pack 2 in the SharePoint integration Mode

I am using Reporting Service Integration mode with SharePoint. SSRS is installed on separated machine of SharePoint stacks in Integration Mode. Everything was working properly and I could create/edit/modify RDL reports(parameters, Datasource, Subscription)
inside SharePoint and Document Libraries.
But after installing SQL Server 2012 Service Pack 2, on opening RDL reports inside SharePoint I receive this error message.
The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation
I should mention that SSRS is installed in the SharePoint integration Mode and there is no SSRS management console.

Hi Hedayat-Abedijoo,
According to your description, you are using Reporting Services in SharePoint Integrated mode, and everything worked fine before you install SQL Server 2012 Service Pack 2. After the package is installed, when you open RDL reports, the error occurred: The
permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation.
According to my search, there may be two reasons for the problem:
This is caused when the application pool account that runs the SharePoint Web application you are on in IIS and the application pool account that SharePoint believes is running the site differ. This happens if the application pool account is changed directly
in IIS instead of through SharePoint (using the approved method).
This error can be caused when Kerberos authentication has been set up correctly and delegation in a double hop scenario will succeed, but Reporting Services integration has been set up for Trusted Account rather than Windows Authentication. This causes
SharePoint to continue to impersonate the logged-on user when contacting Reporting Services; when Reporting Services compares the application pool account to the user account making the request, they are not equal.
In this case, we can solve the problem by changing the application pool account in IIS back to the previous account and set AuthenticationTypes to RSWindowsNTLM only. For detail information, please refer to 8.3 “The permissions granted to user 'Domain\User'
are insufficient for performing this operation” in the document:http://msdn.microsoft.com/en-us/library/ee384252(SQL.100).aspx
If you have any questions, please feel free to let me know.
Thanks,
Wendy Fu

Sql Server 2012 - Standard/Custom Reports in SSMS

Hi,
I want to develop my own Custom Reports in Sql Server. I want to know the underlying report logic (tables used, joins etc) of the existing
Standard reports thru SSMS. Is it possible to locate the source code (.rdl) of these Standard Reports to get an idea about the underlying logic which could be used in my Custom Reports ?
I am using Sql Server 2012
Thanks

Hello,
The standard reports are embedded in an assembly, you can not get the source RDL reports ... without conflicting copyrights.
Customer reports are pretty easy, the database connection is passed from SSMS to the report, just design the report as you like, see
Custom Reports in Management Studio
You can get my customer reports for SSMS 2005 (you can upgrade them to your used version) as an example here:
https://onedrive.live.com/?cid=D974FC8F54C88BA9&id=D974FC8F54C88BA9%21132
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL Server 2012 Analysis Services Deployment Wizard broken after SP1

I have installed SQL Server 2012 SP1, now I cannot edit Data Source Connection Strings anymore in the Deployment Wizard.
When clicking the button labeled "..." I get an error "Could not load file or assembly 'Microsoft.Data.ConnectionUI, Version=8.0.0.0' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference".
This happened on two different 2008 R2 servers and local windows 7 desktop, SP1 Cumulative Update 1 does not fix the error.
Please help!

I managed to fix it by modifying the Workaround from Microsoft a bit.
Microsoft Fix: https://support.microsoft.com/en-us/kb/2809127/
Summary of fix:
Open the following configuration file in a text editor, such as Notepad, as an administrator:
<var class="sbody-var" style="box-sizing:border-box;"><system drive>:</var>\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Microsoft.AnalysisServices.Deployment.exe.config
2. Insert the runtime XML tags after the </startup> tag in the configuration section:<configuration>
<startup>
<requiredRuntime version="v4.0.30319" safemode="true" />
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.ConnectionUI" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="8.0.0.0-9.0.0.0" newVersion="10.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.ConnectionUI.Dialog" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="8.0.0.0-9.0.0.0" newVersion="10.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
What i did to make it work:
<configuration>
<startup>
<requiredRuntime version="v4.0.30319" safemode="true" />
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.ConnectionUI" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="10.0.0.0" newVersion="8.0.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Microsoft.Data.ConnectionUI.Dialog" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="10.0.0.0" newVersion="8.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Instead of redirecting from version 8 and 9 to 10, i reverted it and made sure it uses version 8.

Reporting Services Native versus High Availability SharePoint integrated?

SQL noob here, thanks.
I'm building a new 2008R2 HA SQL server that's part of a SharePoint farm. I'm looking at the Reporting Services Configuration Manager side by side with the old server.
Old server: Report Server Mode is Native
HA server: SharePoint integrated
I want the SQL setups to be as consistent as possible, but don't see a way to switch the HA server to Native. Doable? I read
http://technet.microsoft.com/en-us/library/bb326407(v=sql.105).aspx but I want to keep the same database name. Can I delete the SharePoint Integrated Report Server DB and recreate
as native?
Thanks,
Scott

Hi scogordo,
According to your description, you want to switch to native mode for the HA server with SharePoint. Right?
In Reporting Services, as you can see in your link, we have to specify a database running at native mode as report server database. Since you still want to keep the previous database name, we suggest you change the name of previous database.
Then use the previous name for the new created native mode database.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

[Forum FAQ] Reporting Service Point cannot be installed on a Site System Server running SQL Server 2012 SP1

Symptom: When you install Reporting Service Point role on a Site System Server running SQL Server
2012 SP1, you may encounter an issue that the Reporting Service Point role cannot be installed. The error log “srsrpMSI.log” and “srsrpsetup.log” may throw the error as shown in Figure 1 and Figure 2.
03:32:03:764]:
MainEngineThread is returning 1618
Figure 1: Error -1
<03/03/14 03:32:03>
srsrp.msi exited with return code: 1618
Figure 2: Error -2
Reason: All the two logs indicate an error return code 1618. From the KB below you may know what
the return code means.
ERROR_INSTALL_ALREADY RUNNING
1618
Another installation is already in progress. Complete that installation before proceeding with this install.
KB link:
http://support.microsoft.com/kb/290158 “it is related to an Office Suite KB, anyway, the MSI return code is the same meaning”
You can look into Resource Manager and Event Viewer to find the other currently running MSI installation. You may get a warning in Event Log that means the MSI wants to install a SQL Server
related Component (Figure 3). The Resource Manager confirms this (Figure 4).
Event Log:
Event ID: 1004
Source: Msinstaller
Level: Warning
Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}',
feature 'SQL_Tools_ANS', component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed. The resource '' does not exist.
Figure 3: Event Log
Figure 4: Resource Manager
Resolution: the error is exactly what the following KB describes.
KB Link:
http://support.microsoft.com/kb/2793634
After we resolve the SQL Server 2012 issue, the Reporting Service Role is installed successfully.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

SQL Server 2012 Cumulative update package 2 (CU2) for SQL Server 2012 Service Pack 2 - why only for x86 ?

Hey guys...
Im a little bit confused... i wanted to download the newest hotfixes for SQL server 2012...
But the download for :
2983175 Cumulative update package 2 (CU2) for SQL Server 2012 Service Pack
is only for the platform: x86 available ... but my SQL server 2012 is running in a x64 environment...
(when i checked the older cumulative updates... they're all only for x86.. can someone tell me why ? )
thanks and regards,
Dominic

There doesn't exist an SQL Express "Standard". It's two different editions.
For Express there are three 32bit/64bit editions:
Express, Express with Tools and Express with Advanced Services.
Express with Tools is essentially Express with Management Studio Tools, Express with Advanced Services adds also BI (Business Intelligence) + Reporting Services.
As for where you can apply the cumulative update, on the link you can see this:
Microsoft SQL Server 2012 Service Pack 2, when used with:
Microsoft SQL Server 2012 Analysis Services
Microsoft SQL Server 2012 Developer
Microsoft SQL Server 2012 Enterprise
Microsoft SQL Server 2012 Express
Microsoft SQL Server 2012 Business Intelligence
Microsoft SQL Server 2012 Standard
Microsoft SQL Server 2012 Web
"If there's nothing wrong with me, maybe there's something wrong with the universe!"

SharePoint 2013 - SQL Server 2012 PPIV - using a PPIV workbook as a data source - getting PPIV web service error

I created a PowerPivot (SQL Server 2012 SP1) workbook and uploaded it to SharePoint 2010 Portal and started using it as a data source in an excel file. This worked fine and we saw no issues with it until we moved to SharePoint 2013 environment.
I uploaded the same PowerPivot workbook (source workbook) to SharePoint 2013 Portal and now trying to use it as a data source. I tried to change connection properties so that I could use the new portal address for the workbook. When
I try to save my changes, I see that OLAP queries are getting fired "Refreshing OLAP cube" shows up in the status bar, but eventually after running these OLAP queries (I would say after a minute), I get the following error -
Couldn't find anything specific in SharePoint logs or maybe I wasn't looking for the right thing.
Has anyone seen this issue? Why would PPIV service throw an error after running for a while? Is it a timeout issue of some kind? How can we take care of this?
Thanks,
Sonal

ULS log showed the following exception: The maximum number of allowed sessions per user has been exceeded.
Under Excel Services global settings, max limit is set. Default is 25, increasing it resolved this issue.
Thanks,
Sonal

SharePoint 2013 Enterprise and SQL Server 2012 Standard edition vs. Enterprise - feature question

I can't seem to find any clear answers to the implications of installing SQL Server 2012 standard edition vs. enterprise in regards to SharePoint 2013.
I understand that to get many of the features you need Enterprise edition of SQL 2012; but, what I can't figure out is if the backend SharePoint SQL 2012 is standard; but, the PowerPivot/SSRS server is Enterprise will we still get the features?
If we have 3 tier SharePoint farm, one of those tiers is for the SQL Server database backend. If that SQL instance is 2012 standard and we add another server to the farm w/ SQL 2012 Enterprise to handle the tabular models, PowerPivot, and SSRS in integrated
mode will we still get the features?
Or, can we (should we) install Enterprise 2012 as the SharePoint database backend and let that instance triple down as also the PowerPivot and SSRS instance?
The Degenerate Dimension

Hi MMilligan,
SQL Server 2012 Standard is not supported PowePivot for SharePoint . In addition, SQL Server 2012 Standard is also not support some Reporting Services Features.
For more information, please refer to Features Supported by the Editions of SQL Server 2012:
http://msdn.microsoft.com/en-us/library/cc645993.aspx.
Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1):
http://msdn.microsoft.com/en-us/library/jj218795.aspx.
If you have any problem, please feel free to let me know.
Thanks.
If you have any feedback on our support, please click
here.
Maggie Luo
TechNet Community Support

Excel 2007 Download Error from SQL Server 2012

Thank you for your help/comments in advance
We are running SQL Server 2012, downloading SSRS reports into Excel 2007.
The report renders to the monitor just fine.
Most downloads are fine but we get an error with the largest downloads (common denominator) but can be hit or miss. Usually a second try it will download. Today we tried numerous times and kept getting the error.
I saw a link to a service pack fix ...https://msdn.microsoft.com/en-us/library/dd255234(v=sql.110).aspx which somewhat fits my issue.
The Report Server Log (O:\MSRS11.MSSQLSERVER\Reporting Services\LogFiles\ReportServerService__04_01_2015.log) gives the following error message:
library!ReportServer_0-2!29bc!04/01/2015-15:02:01:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Invalid offset for item. ReferenceID: fffffffffffffffe, Offset: -2, Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more details.;
library!ReportServer_0-2!29bc!04/01/2015-15:02:12:: i INFO: Dump result: External dump process return code 0x20000001.
External dump process returned no errors.
processing!ReportServer_0-2!29bc!04/01/2015-15:02:12:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more details.;
library!ReportServer_0-2!29bc!04/01/2015-15:02:12:: w WARN: Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See
the error log for more details. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for
more details.
   at Microsoft.ReportingServices.RdlExpressions.ReportRuntime.RegisterRuntimeErrorInExpression(VariantResult& result, Exception e, IErrorContext iErrorContext, Boolean isError)
   at Microsoft.ReportingServices.RdlExpressions.ReportRuntime.EvaluateTextRunValueExpression(TextRun textRun)
   at Microsoft.ReportingServices.ReportProcessing.OnDemandReportObjectModel.TextRunImpl.GetResult(IReportScopeInstance romInstance)
   at Microsoft.ReportingServices.OnDemandReportRendering.InternalTextRunInstance.EvaluateOriginalValue()
   at Microsoft.ReportingServices.OnDemandReportRendering.InternalTextRunInstance.get_ProcessedWithError()
   at Microsoft.ReportingServices.Rendering.SPBProcessing.TextBox.WriteCustomNonSharedItemProps(RPLElementProps nonSharedProps, RPLWriter rplWriter, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.PageItem.WriteNonSharedItemProps(RPLElementProps elemProps, RPLWriter rplWriter, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.TextBox.WriteItemToStream(RPLWriter rplWriter, PageContext pageContext)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.TextBox.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double&
parentPageHeight, Interactivity interactivity)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.Rectangle.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double&
parentPageHeight, Interactivity interactivity)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.TablixContext.AddRowMemberContent(TablixMember rowMember, Int32 rowIndex, Int32 colIndex, Int32 rowSpan, Int32 colSpan, Byte memberState, Int32 defTreeLevel, LevelInfo childLevelInfo,
Double updateWidth)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.TablixContext.AddRowMember(TablixMember rowMember, Int32 rowIndex, Int32 colIndex, Int32 rowSpan, Int32 colSpan, Byte memberState, Int32 defTreeLevel, LevelInfo childLevelInfo)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex,
Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateTablixItems(Tablix tablix, TablixContext context)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double&
parentPageHeight, Interactivity interactivity)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.ReportBody.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double&
parentPageHeight, Interactivity interactivity)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.ReportSection.CalculatePage(RPLWriter rplWriter, Int32 page, Int32 totalPages, Int32 regionPageNumber, Int32 regionTotalPages, Boolean firstSectionOnPage, Boolean lastSection, Interactivity
interactivity, Double heightToBeUsed, PageItemHelper& lastBodyInfo, Boolean& delayedHeader, Boolean& delayedFooter, Boolean& lastSectionOnPage)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.Report.NextPage(RPLWriter rplWriter, ReportSectionHelper& lastPageInfo, Int32 page, Int32 totalPages, Interactivity interactivity, Boolean hasPaginationChunk)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.SPBProcessing.GetReportNextPage(Stream& stream, Boolean collectPageBookmarks)
   at Microsoft.ReportingServices.Rendering.SPBProcessing.SPBProcessing.GetNextPage(RPLReport& rplReport, Boolean collectPageBookmarks)
   at Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties,
CreateAndRegisterStream createAndRegisterStream)
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.HandleRenderingException(ReportRenderingException rex)
   at Microsoft.ReportingServices.ReportProcessing.Execution.RenderReport.Execute(IRenderingExtension newRenderer)
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderSnapshot(RenderingContext rc, ProcessingContext pc)
   at Microsoft.ReportingServices.Library.RenderFromSnapshot.DoRendering(ProcessingContext pc, RenderingContext rc)
   at Microsoft.ReportingServices.Library.RenderFromSnapshot.CallProcessingAndRendering(ProcessingContext pc, RenderingContext rc, OnDemandProcessingResult& result)
   at Microsoft.ReportingServices.Library.RenderStrategyBase.ExecuteStrategy(OnDemandProcessingResult& processingResult)
The user sees the following on her monitor when downloading ...

Hi Mark,
As you know this is an known issue in the SSRS 2012 and the fix for this issue was first released in Cumulative Update 3 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article
in the Microsoft Knowledge Base:
2723749Cumulative update package 3 for SQL Server 2012
More details information in below article:
http://support.microsoft.com/en-us/kb/2707015
As I have tested on my loacal environment and can't reproduce the issue and you have also mentioned that that you didn't meet the issue now. If you got the issue next time, please feel free to let us know if the hotfix will work or not.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

Do I need to install x64 and x86 versions of SQL Server 2012 SP2?

Hi,
I have installed x64 version of SQL 2012 SP2. Do I need to install x86 version of SP2 as well?
(I have some x86 components installed as well that came with various things like SSDT-BI and/or Visual Studio installations.)
When I click "SQL Server Installation Center (64-bit).lnk" shortcut and run "Installed SQL Server features discovery report", it says "Microsoft SQL Server 2012 Setup Discovery Report".
When I click "SQL Server Installation Center.lnk" shortcut and run same, it says "Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report".
Both reports say the same thing: the installed version is 11.2.5058.0, which is SP2.

Hi,
I have installed x64 version of SQL 2012 SP2. Do I need to install x86 version of SP2 as well?
(I have some x86 components installed as well that came with various things like SSDT-BI and/or Visual Studio installations.)
When I click "SQL Server Installation Center (64-bit).lnk" shortcut and run "Installed SQL Server features discovery report", it says "Microsoft SQL Server 2012 Setup Discovery Report".
When I click "SQL Server Installation Center.lnk" shortcut and run same, it says "Microsoft SQL Server 2012 Service Pack 1 Setup Discovery Report".
Both reports say the same thing: the installed version is 11.2.5058.0, which is SP2.
Hello,
No you dont have to install X86 version
SQL server 2012 installable will install SQL server as per process architecture of your machine. If it is 32 bit machine it will install 32 bit version and for 64 bit it will install 64 bit version. installable has facility for both
Even on 64 bit machines some files, which always work in 32 bit compatibilyt mode, will be installed as well andand they go to SQL server (X86) folder. BIDS, SSIS always by default works in 32 bit compatibility mode.
If report says version as 11.2.5058 it means component is patched to SP2
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SQL Server 2012 with SP1 on Windows 8.1 Pro

Can I install "out-of-the-box" SQL Server 2012 with Service Pack 1 Enterprise Edition or SQL Server 2012 Developer Edition on my Windows 8.1 VM?
Thanks.

Hello,
SQL Server 2012 SP1 is fully supported by Windows 8.1, and there is no need to install any SQL update for the installation.
Enterprise Edition is not supported on client operating systems like Windows 8.1 but setup won’t prevent you from installing.
Developer Edition is fully supported on client operating systems.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

FILESTREAM garbage collector in sql server 2012

HI
what is FILESTREAM garbage collector in sql server 2012
I restored a backup of a sharepoint 2010 content database it is rbs enabled
when I restore blobs are deleting from a rbs storage folder how its happen
adil

This is a good read
http://www.sqlskills.com/blogs/paul/filestream-garbage-collection/
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SQL Server 2012 Reporting services Report Builder ClickOnce in SharePoint integrated mode

Similar Messages

Maybe you are looking for