SharePoint 2013 and SQL Reporting Services Integration Mode

I'm setting up a production environment with SQL Server 2012 SP1 (Clustered) and SharePoint 2013.
I successfully setup the integration using PowerShell (Install-SPRSService & Install-SPRSServiceProxy). I can see the SQL Reporting Service on the CA Services and it's started, I've also created the Services Application without any issues (And linked it
to my web application). However the Report Server Integration feature is missing from my site collection and so are the content types. I even tried creating a new site collection and no dice.
Appreciating any help.
Best,
MI

Hi MI,
As per my understanding, I think this issue is caused by you haven’t install the Reporting Services add-in for SharePoint Products or is not installed correctly. If we install the Reporting Services add-in for SharePoint Products after the installation of
the SharePoint Server, then the Report Server integration feature and the Power View integration feature will can be activated for root site collections. For other site collections, we can manually activate the features. To fix the issue you occurred, we should
install or reinstall the Reporting Services add-in for SharePoint Products.
For more information about Install Reporting Services 2012 SharePoint Mode for SharePoint 2013, please see the following article:
http://msdn.microsoft.com/en-us/library/jj219068.aspx
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Similar Messages

  • Workflows 2013 and SQL Report Services: Configure on Independent Servers or Existing App Servers?

    Currently, my SharePoint 2013 Farm has Workflows 2013 and SQL Report Services installed on app servers, along with other applications. Workflows 2013 isn't working correctly (installed prior to my coming on board with the organization), I'm assuming it
    is a configuration issue, but rather than re-configure, I've read that is recommended to be a standalone server. It was also recommended by a MSFT rep that our report services have its own independent server. Currently, Report Services is also installed on
    an app server that runs other applications on the farm.
    Has anyone had any experience with installing Workflows 2013 and/or SQL Report Services on independent vs. existing application servers?
    Additionally, my existing application servers have 24 GB of RAM (I believe the recommendation for SharePoint production environments is 12 GB), should I plan for the potentially new servers (Workflows and Report Services) to also have 24 GB of RAM? Not really
    sure if it will be needed if they have dedicated tasks.
    Thanks for any input you can provide!

    It entirely depends on load. WFM will work just fine installed on servers in the SharePoint farm. SSRS preferably should go on the end-user facing servers for better performance.
    The questions you're asking are all "it depends" :)
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • SharePoint 2013 and SQL Server AlwaysOn - HA

    Hi guys,
    Please help!
    I need to setup SP13 server on SQL 2012 AlwaysOn (on sql01 and sql02). The HA AlwaysOn group already configured by DB team on these 2 replica with and called SP_AOAG  alias
    My question is can I use this alias to setup SharePoint  or I need to configure the HA AlwaysOn group for SgharePoint  as suggested in the article below:
    http://blogs.msdn.com/b/sambetts/archive/2013/04/24/sharepoint-2013-and-sql-server-alwayson-high-availability-sharepoint.aspx
    Any advice greatly appreciated . 
    BalaiP

    You do not want to use a SQL Alias with an AG Listener. Just point SharePoint straight at the AG Listener. You will need to manually add any accounts to non-primary instances. You do not need to add them to individual databases, of course. You will also
    need to manually set MAXDOP to 1 on non-primary instances.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • How to configure workflow manager 1.0 ? Scenario "sharepoint 2013 and sql server 2012 workflow manager in one server" .

    i have sharepoint 2013 and sql server 2012 in one server . how to configure workflow manager 1.0 on the same server ?

    Please follow below technet article :
    http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
    Installing and Configuring Workflow Manager 1.0 (Step by Step)
    Note: The steps in this article apply to SharePoint Server 2013.
    The SharePoint 2013 Workflow platform is not supported in SharePoint Foundation 2013.
    If my contribution helps you, please click Mark As Answer on that post and
    Vote as Helpful
    Thanks, ShankarSingh(MCP)

  • Is it possible to install SharePoint 2013 and SQL 2012 on single Azure Virtual Machine

    I had a Azure subscription, I need had created only one Virtual Machine, is it possible to install SharePoint 2013 and SQL Server 2012 on that single virtual machine in azure.
    I had SharePoint 2013 and SQL Server 2012 licence from MSDN subscription,
    Finally on Azure virtual machine is it possible to Install SharePoint 2013 and SQL server by downloading these software from MSDN. 

    Hi,
    It is supported to install sharepoint 2013 and SQL server on the same server. However, please check the size of your Azure VM and make sure it is compatible for that.
    The minimum recommended size for a virtual machine is A3 when using SQL Server Enterprise Edition. Select A3 or higher when using SQL Server Enterprise Edition. Select A4 when using SQL Server 2012 or 2014 Enterprise Optimized for Transactional Workloads
    images. Select A7 when using SQL Server 2012 or 2014 Enterprise Optimized for Data Warehousing Workloads images. In addition, the default size for SharePoint 2013 image is A3.
    In addition, as a best practice, you can install them in different servers and then deploy SharePoint 2013 with SQL Server AlwaysOn Availability Groups in Azure:
    Deploying SharePoint 2013 with SQL Server AlwaysOn Availability Groups in Azure
    http://msdn.microsoft.com/en-us/library/azure/dn275959.aspx
    Best regards,
    Susie
    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]

  • SharePoint 2013 and SQL Always On

    How do I setup SharePoint with SQL Always On.
    I have two servers SQL1 and SQL2.  I created Windows 2012 cluster and called it MyCluster.
    I installed SQL Server 2012 SP1 on both servers. I created AlwaysOn group called MyAlwaysOn and added test database to sync between those two servers.
    Now I have to install SharePoint 2013.  How do I specify the SQL server? Do I say that name is SQL1? Or MyCluster? Or MyAlwaysOn?
    MyAlwaysOn does not have IP address or DNS record, so I do not think I can do it. So, is it SQL1 or MyCluster?
    If it is SQL1, do I manualy add SharePoint databases to MyAlwaysOn group? How does it work? How will SharePoint know to switch to SQL2?
    Anyone knows how to do it right?
    Thank you.
    Thank you. Eric.

    Please see))
    http://blogs.msdn.com/b/sambetts/archive/2013/04/24/sharepoint-2013-and-sql-server-alwayson-high-availability-sharepoint.aspx
    Create SharePoint Databases
    Prepare SQL Alias
    We need to fool SharePoint into thinking the SQL server where we'll create the configuration database is called something else. That’s because when you create a farm, whatever destination server you use during the “create new farm” stage isn’t forgotten (to
    simplify), so first thing’s first let’s create fake alias for our SQL “server” – “SP15” as it’s SharePoint 2013 that’ll use it (version 15). As far as SharePoint needs to know everything is going into a SQL box called 'SP15'.
    Now assuming you don’t have SQL Server tools installed (which you shouldn’t if it’s on production!) you’ll need to use a tool called “cliconfg.exe” to create a SQL alias. Run it; click the “Alias” tab, and the Add button.
    Add a name – SP15 for the alias name, but it can be anything - instead of referencing a server-name we’ll reference the name of the alias which will transparently redirect traffic to the alias destination instead.
    And if you know Russian languages
    http://blog.it-kb.ru/2014/04/15/install-two-tier-farm-sharepoint-server-2013-sp1-on-windows-server-2012-r2-part-1-prepare-ha-clustered-sql-server-2012-sp1-cumulative-update-9-instance/
    http://blog.it-kb.ru/2014/04/15/install-two-tier-farm-sharepoint-server-2013-sp1-on-windows-server-2012-r2-part-2-create-a-new-server-farm-with-kerberos-and-language-pack/
    Так как БД SharePoint в нашем случае будут расположены на удалённом экземпляре SQL Server 2012 SP1(CU9), перед началом установки SharePoint
    можно установить пакет Microsoft SQL Server Native Client. Его можно загрузить например со страницы Microsoft
    SQL Server 2012 SP1 Feature Pack (файлENU\x64\sqlncli.msi), а ещё лучше взять дистрибутив клиента обновлённой версии из состава CU9 (файл\SQLServer2012_SP1_CU9\1033_enu_lp\x64\setup\x64\sqlncli.msi)
    Хотя в дальнейшем фактически утилита подготовки к установке Sharepoint всё равно загрузит у установитSQL Server 2008 R2 SP1 Native Client.
    После установки SQL-клиента создадим на нашем сервере SQL-Alias, который будем в дальнейшем использовать для подключения служб SharePoint к серверу SQL Server. Этого конечно можно
    и не делать, но это может оказаться полезным (даст нам дополнительную гибкость) в случае необходимости переноса БД на другой SQL-сервер или экземпляр. Запустим встроенную в ОС утилиту SQL Server Client Network Utility (%windir%\system32\cliconfg.exe)
    и добавим два новых алиаса – с коротким именем SQL-сервера и его FQDN, указав при этом имя экземпляра и статический TCP порт (в нашем случае SHAREPOINT и 1435соответственно).
    Имя самого алиаса в нашем случае будет KOM-AD01-SQLSP

  • Reporting Service Integration mode and Key not valid for use in specified state

    I had to uninstall SharePoint Foundation 2013 and reinstall it.
    What I have done:
    I uninstalled SharePoint and after that I removed all databases.
    I reinstalled SharePoint Foundation 2013 and it completed without errors.
    Everything else is working, except SSRS in Sharepoint Integrated Mode.
    If I check Central Administration - Manage services on server, I can found out that SQL Server Reporting Service Service is
    "Started". But if I try to create new service application (SQL Server Reporting Services Service Application), it gives me an error message:
    "Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B)"
    I uninstalled SSRS in Sharepoint Integrated Mode and I reinstalled it but problems exists.
    It seems that "Encryption Keys" cause this problem.
    https://support.microsoft.com/kb/955757
    https://msdn.microsoft.com/en-us/library/ms156010%28v=sql.110%29.aspx
    I tried to Re-create Encryption Keys and Delete keys, but its not working either. It gives me only error message that:
    "Unable to locate the Reporting Server Windows service for instance MSSQLSERVER."
    I don't have any reporting server databases, because I removed all
    databases when I uninstalled SharePoint. Also I don't have Encryption
    Keys backups.
    I have found several similar question but no answer, example here:
    https://social.technet.microsoft.com/Forums/ie/en-US/df02dc05-5ce8-499d-9ba3-ab392a5fc3af/sharepoint-2013-ssrs-application-error-key-not-valid-for-use-in-specified-state-exception?forum=sharepointdevelopment
    Any ideas how I can fix this problem?

    Hi,
    From the Reporting Server Configuration Manager you have to restore the encryption key.
    Please try to delete databases(reportserver & reportservertempdb) and delete the reportserver and reports site on IIS. Then you have to start over the configuration again.
    If the issue still exists, Please check ULS log to see if anything unexpected occurred.
    For SharePoint 2013, by default, ULS log locates in
    "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS"
    More information about SQL Reporting services Installation with SharePoint 2013 for your reference:
    http://expertsharepoint.blogspot.de/2014/03/sql-reporting-services-installation.html
    Best Regards,
    Dennis Guo
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • ISSUE Sharepoint 2013 databases for reporting services on the second server SQL 2012

    Hello,
    I have server A: Operating system windows 2012 standard, SQL server 2012 standard
    instance: Sharepoint contains data for sharepint
    instance: Reporting should be contain databases for reporting
    Server B:
    Windows server 2012 standard contains installation Sharepoint 2013
    Sharepoint works (without reporting services), it is OK - databases are located on server A:
    My issue is:
    When I have installed reporting services on server B, I have already installed SQL server 2012 on server B, it works.
    I am able to create report in report builder adn place it in to sharepoint.
    But I would like to use only one full SQL machine on server A:
    When I reconfigure repoting settings on server A in central administration - manage service aplications,
    On the SQL server A in instance reporting , there is automatically created databases. It is no problem.
    But the first difference is, when I want to manage service aplication for reporting  in
    Provision Subscriptions and Alerts, there is information
    SQL Server Agent state cannot be determined
    When I want to create report in report builder, I have issue:
    server A-7380mw016\reporting it means server A with full SQL server:
    The Test of connection was successful
    Then I have clicked test connection
    I have recieved this screen with fail: Logon faild for user NT Authority\anonymous logon
    My account belongs to SQL admin on server A (A-7380mw016\reporting) I do not know it is not possible to create report, when it is possible to test connection in the first step and in the second step, there is problem...
    Please, can somebody help me?

    Hi,
    Since you are getting an Anonymous Logon error, it appears there may be a problem passing your credentials to the SQL Server Agent Service. This would indicate a Kerberos issue. See this thread for details:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/46b7c773-6a77-435d-b471-cb9a6ec41c43/has-anyone-else-upgraded-reporting-services-to-denali-2012
    Microsoft Virtual Academy: Breakthrough Insights using SQL Server 2012 : Analysis Services and Credible, Consistent data (Module 2) - Configuring and Securing Complex BI Applications in a SharePoint 2010 Environment with Microsoft SQL Server 2012
    http://technet.microsoft.com/en-us/video/Video/hh858469
    Tips from the video:
    We are connecting to Reporting services using Kerberos when using Reporting Services in SharePoint integrated mode
    For the account using reporting services, we just need a dummy SPN. We go to Attribute editor tab in AD for RS account. And then we will be enabled with Delegation tab.
    In Delegation tab. I we are using claims to windows token, we need to use "Trust this user for delegation to specified services only"
    There you have 2 options: "Use Kerberos only": It means I only want to delegate in the situation where the service that is doing the delegation actually has the Kerberos ticket to start with
    "Use any authentication protocol" When we need protocol transition (like from NTLM to claims for intra farm communication)
    We need to delegate this to SQL server.
    Please check out these articles as well:
    How to configure SQL Reporting Services in SharePoint Server for Kerberos authentication
    http://support.microsoft.com/kb/2723587
    Configure Kerberos authentication (Office SharePoint Server)
    http://blogs.technet.com/b/mbiswas/archive/2009/07/10/configure-kerberos-authentication-office-sharepoint-server.aspx
    Thanks.
    Tracy Cai
    TechNet Community Support

  • SharePoint 2010 with SQL Reporting Services 2012 "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"

    i have a small sharepoint farm "2 servers" (WFE) and SQL Server 2012 ,
    i installed rsSharePoint for reporting services , as a read the Reporting services is Application Service  with SQL 2012 not as SQL 2008 R2 with SharePoint integrated mode, so after installation when am trying to configure the  SQL Server
    Reporting Services Application services i got the below error :
    "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"
    any kind of help would be much appreciated .

    I'm having the same issue, but to me it seems like the instructions I've seen are all over the place.  I already have SP 2013 and SQL 2012 SP 1 installed.  I already added the features for Reporting Services - Sharepoint and Reporting Services
    Add-in for SharePoint Products.  I didn't see the Reporting Service service in CA, so I ran the powershell scripts to add SPRSService and SPRSServiceProxy. 
    My initial quest, was to get the BI features enabled, which took me on the journey of adding the Report Services, then I got the error.
    Then when I read this about installing the BI features
    http://blogs.msdn.com/b/querysimon/archive/2012/11/26/installing-the-bi-features-of-sharepoint-2013.aspx, which I already had SQL and SP installed.  Do I have to rerun and selct the SQL Server PowerPoint for SharePoint option?  I have the PowerPoint
    Configuration Tool on my SQL server, I run it and I get PowerPivot for SP 2013 Configuranoi is missing prerequisits:  SP 2013 EE is required.  Which I have EE.
    Is Reporting Services different or in addition to the BI Feature (PowerPivot)? 
    Have I missed a step?
    Thanks for you help.
    Kim
    Kim.Williams

  • Upgrade 2010 to 2013 with SQL Reporting Services

    I'm getting ready to upgrade to 2013.
    When I run the Test-SPContentDatabase I get:
    Category : MissingWebPart
    Error : True
    UpgradeBlocking : False
    Message : WebPart class [ab6d9dad-e23c-ce4f-ff98-f6575a1ccf4c] (class [
    Microsoft.ReportingServices.SharePoint.UI.WebParts.ReportView
    erWebPart] from assembly
    [Microsoft.ReportingServices.SharePoint.UI.WebParts,
    Version=10.0.0.0, Culture=neutral,
    PublicKeyToken=89845dcd8080cc91]) is referenced [24] times
    in the database [is-sharepoint], but is not installed on the
    current farm. Please install any feature/solution which
    contains this web part.
    Remedy : One or more web parts are referenced in the database
    [is-sharepoint], but are not installed on the current farm.
    Please install any feature or solution which contains these
    web parts.
    Locations :
    Category : MissingAssembly
    Error : True
    UpgradeBlocking : False
    Message : Assembly
    [Microsoft.ReportingServices.SharePoint.UI.ServerPages,
    Version=10.50.0.0, Culture=neutral,
    PublicKeyToken=89845dcd8080cc91] is referenced in the
    database [is-sharepoint], but is not installed on the
    current farm. Please install any feature/solution which
    contains this assembly.
    Remedy : One or more assemblies are referenced in the database
    [is-sharepoint], but are not installed on the current farm.
    Please install any feature or solution which contains these
    assemblies.
    Locations :
    Category : Configuration
    Error : False
    UpgradeBlocking : False
    Message : The [is.photomask.com] web application is configured with
    claims authentication mode however the content database you
    are trying to attach is intended to be used against a
    windows classic authentication mode.
    Remedy : There is an inconsistency between the authentication mode of
    target web application and the source web application.
    Ensure that the authentication mode setting in upgraded web
    application is the same as what you had in previous
    SharePoint 2010 web application. Refer to the link
    "http://go.microsoft.com/fwlink/?LinkId=236865" for more
    information.
    Locations :
    The first two have to do with reporting services.  I'm trying to workout how to go about getting these errors to go away.  I don't want to remove SQL reporting or migrate a broken site and fix it later.  FYI it does migrate but reporting services
    is of course broken.
    So what I was wanting to do was to upgrade SQL Reporting Services for SharePoint 2010 from 2008 SQL to 2014 SQL first.  This would be in the hopes that it would make the migration to SharePoint 2013 work as the assemblies would change to the proper
    version.
    Can anyone elaborate on my upgrade path?
    I'm still looking up the "Claims Based" authentication thing.  I've found an article on how to migrate it so not a big deal.  I do wonder however if this is tied to the issue I saw with default.aspx and home.aspx being denied to all users
    after I did migrate a content db.
    David Jenkins

    Hi David,
    The following sections describe the basic steps needed to upgrade or migrate from 2008 versions of Reporting Services SharePoint mode to 2014 version.
    SQL Server 2008 R2 to SQL Server 2014
    Starting environment: SQL Server 2008 R2, SharePoint 2010.
    Ending environment: SQL Server 2014, SharePoint 2010.
    In-place upgrade is supported and there is no down time for your SharePoint environment.
    Install the SQL Server 2014 version of the Reporting Services add-in for SharePoint on each web front-end in the farm. You can install the add-in by using the SQL Server 2014 installation wizard or by downloading the add-in.
    Run SQL Server 2014 installation to upgrade SharePoint mode for each “report server”. The SQL Server installation wizard will install the Reporting Services Service and create a new Service application.
    If you also want the ending environment to run SharePoint 2013, you need to complete a database-attach upgrade of the SharePoint 2010 to SharePoint 2013.
    For more scenarios information, please refer to:
    http://msdn.microsoft.com/en-us/library/ms143747.aspx#bkmk_sharePoint_scenarios
    Per the supported combinations of SharePoint and Reported Services Components, I’d recommend you firstly upgrade Reporting Services to 2014, then upgrade SharePoint to 2013.
    For more information:
    http://msdn.microsoft.com/en-us/library/gg492257.aspx
    The link below is the reference for migrating a Reporting Services:
    http://msdn.microsoft.com/en-us/library/hh759331.aspx
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • SharePoint 2013 and SQL Server 2014

    Does SharePoint 2013 supports SQL Server 2014 for Reporting Services, PowerPivot

    Yes it does (or rather, SSRS 2014/PowerPivot 2014 support SharePoint 2013). They also support SharePoint 2010.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Coldfusion and SQL reporting service 2005?

    Ive been searching google for hours with no clear answer. How
    can you use coldfusion to pull in an sql report from reporting
    service? Via a web service or wsdl i assume, but how?

    Anwar,
    It's important to get the terms right here.
    SQL Reporting Services is not the same as SQL Server Reporting Services (SSRS).
    SQL Reporting Services refers to an Azure service that lets users develop reports in the cloud. However, it is being retired in Oct. 2014, so you'll want to stay away from that.
    SQL Server Reporting Services (SSRS) is the reporting module that is part of SQL Server. This is a sophisticated tool that lets developers create and publish reports that users can access through various methods. It has schedule and refresh capabilities,
    and can leverage SQL Server Analysis Services (SSAS) and SQL Server Integration Services (SSIS). You'd most likely use SSRS if you're creating sophisticated reports and queries that you don't want your users creating.
    SQL Report Builder is a report creation tool designed for users who want to stay in Microsoft Office. It can be used by developers or end users. 
    http://technet.microsoft.com/en-us/library/dd220460.aspx
    Both environments let you create reports that can be shared (published) on a report server or through SharePoint.
    So it's really a matter of what you're most comfortable using.
    Hope that helps.

  • SAP and SQL Reporting Services.

    Hi,
    I'm trying to implement a few reports using MS SQL Reporting Services.  I don't think that SAP (we are currently on 4.6C, and BW is not an option for now) has anything nearly as cool.  The problem is that SQL RS can only create queries against ODBC and OleDB providers.  One of the solutions would be to create a view in SAP DB and query against it, but the logic behind is just too complicated for a view that you can create in SAP.  Is there another way that I can interface SAP real time to SQL RS?  Anyone had experience with that, or is there a solution from SAP with similar capabilities?
    Thanks,
    Leon

    Hi Leon,
    maybe you can use the SAP.NET Connector and save the results in SQL-SERVER-Tables or use the OLEDB Provider for SAP from NSX software.
    Greetings,
    Andreas Rohr

  • Report Services Integrated mode : Error 503 after 100 seconds

    Hello,
    After resolving an issue with some timeouts in shared datasets (updated value not taken into account), i am now facing another timeout (?) issue with our production sharepoint server and reporting services :
    If a report takes more than 100 seconds to display, the following message is displayed on the top of the page :
    "Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server.  The status code returned from the server was: 503"
    The exception is triggered by the scriptmanager, but i don't know why : all the applications pool are running fine, and if i look in SSRS log, it shows that the task completed successfully !
    Our development server is not affected by this strange behavior.
    Is there a secret timeout switch hidden somewhere ??

    Hi Raphael,
    In Reporting Services, if the report server is under high memory pressure, the report server will refuse new requests until the current application domain is unloaded and a new one instantiated. While requests are refused, you will receive HTTP 503 errors.
    To avoid this issue, you can add more memory, move the report server installation to a computer that has more memory, or change the memory configuration settings. For the detail information about it, please see HTTP 503 Service is Unavailable section on the
    link below:
    http://technet.microsoft.com/en-us/library/ms159778(v=sql.105).aspx
    Besides, for the timeout issue, you can refer to the links below to troubleshooting it.
    http://blogs.msdn.com/b/mariae/archive/2009/09/24/troubleshooting-timeout-errors-in-reporting-services.aspx
    http://geekswithblogs.net/ssrs/archive/2009/10/30/steps-to-resolve-ssrs-timeout-issues.aspx
    If you have any questions, please feel free to ask.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Power Pivot Configuration error while refreshing connection on excel sheet for SharePoint 2013 and Sql server 2014 using BISM file connection

    I am getting following error while refreshing connection on excel sheet in power pivot gallery,
    my scenario,
    using BISM file connection to create and  refresh power pivot excel sheet in power pivot gallery
    throws error and we have sql server 2014 CU6 updated installed plus sharepoint 2013. i checked following msolap110.dll is available in our environment but assembly
    Microsoft.AnalysisServices.ChannelTransport is not available. 
    i found error in event viewer,
    "Activation context generation failed for "C:\Program Files\Microsoft Analysis
    Services\AS OLEDB\110\msolap110.dll". Dependent Assembly
    Microsoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
    not be found. Please use sxstrace.exe for detailed diagnosis.
    what should i do to fix it?
    Thanks for help.
    Deepak Patel

    Rebecca,
    yes, this is issue i am getting.
    Activation
    context generation failed for "C:\Program
    Files\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll".
    Dependent AssemblyMicrosoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
    not be found. Please use sxstrace.exe for detailed diagnosis.
    let me know if you can find fix for it.
    THanks,

Maybe you are looking for