PowerView spreadsheet throws error when displayed Sharepoint - sharepoint-2013

I'm trying to access a PowerView spreadsheet in Sharepoint 2013 and I get the error below:
An error occurred while loading the model for the item or data source 'EntityDataSource'. Verify that the connection information is correct and that you have permissions to access the data source.
Here is what I have:
Server 1 - Sharepoint 2013 Server, with RS for Sharepoint Add-in installed, Analysis services feature installed
Server 2 - Contains the SQL Server installation which is used for holding the CRM 2013 databases as well as Sharepoint 2013 Config and Content databases.
I have created a Power View report in Excel 2013, using the OData
feed from my CRM 2013 organization. I saved this as .xlsx file and
uploaded to my Sharepoint site as a normal document.
I have
created an SSRS Application in Sharepoint Central Administration and
configured it to run under a service account
I have added the
following 'Servers' under my Excel Application -> Data Model settings
in Sharepoint
SQLServerName
SQLServerName\SQLInstanceName
SharepointServerName
SharepointServerName\SQLInstanceName
I have enabled the PowerView Integration Feature,
Report Server Integration Feature in my sharepoint site collection
features.
I am trying to browse to my sharepoint site and click to open the .xlsx file and I get this error.
Below is the detailed error message:
Cannot create a connection to data source 'EntityDataSource'.Microsoft.AnalysisServices.SPClient
We cannot locate a server to load the workbook Data Model.
We cannot locate a server to load the workbook Data Model.Microsoft.Office.Excel.Server.WebServicesWe cannot locate a server to load the workbook Data Model.

This question has been asked a couple times on the SharePoint SE site.
There is an MS support article from Microsoft that addresses this error. It suggests you do the following:
In the Application Management section of the Central Administration home page, click Manage service applications.
On the Manage Service Applications page, click the Excel Services service application that you want to configure.
On the Manage Excel Services page, click Data Model.
Click Add Server.
In the Server Name box, type the name of the Analysis Services instance that you want to add.
Click OK.
If that doesn't work, someone solved this problem by installing SQL Server 2012 SP1.
Someone else solved this issue by ensuring that the account used for Excel Services is an SSAS admin and then rebooting

Thank you #mmarie for the answers/comments.
I was able to partially resolve the issue by 're-installing' the Analysis services on my Sharepoint server. So it turns out I installed it the wrong way first. Followed this article to fix it.
Analysis services for SP 2013
I'm currently experiencing problem with the 'Data Refresh' within the Power Pivot/Power View reports. I have added my service account to the '"Act as part of the operating system" role on the Sharepoint server based on this article Data Refresh, however it did not resolve the issue.
Please let me know if anyone has any inputs.

Related

Missing menu in Power BI

I installed the Reporting Services on my personal laptop. After running on the web Portal URL, I do not see the Branding menu. I'm logging with the admin user And I'm not the Power BI Desktop in setting menu I installed the Express version and my SSms edition is Standard Edition. what can I do?
Not sure of what is your current setup BUT
Setup needed :
SQL Server
Power BI Report Server (Superset of SQL Server Reporting Services)
And then on your server, the branding menu will be accesible with admin rights.
Read this useful link.

SharePoint 2013 Visio document error: the server failed to process the request

When I try to open Visio documents uploaded to my SharePoint site, I get "the server failed to process the request" error. Any help is appreciated!
Here are the steps that I followed that fixed the issue:
Open SharePoint Central Administration on SharePoint server.
Manage service applications (under Application Management).
Select Visio Graphics Service -> Properties
Check what Application Pool is used (SharePoint Web Services Default in my case).
Open IIS -> Application Pools.
Visio App Pool is usually represented by a GUID name. To get the name:
Open SharePoint Management Shell (run as administrator)
Run command: Get-SPServiceApplicationPool | Select Id, Name
Find Id of App Pool (from step 4)
Find the same id in IIS under Name column and check the value in Identity column
Remote to the sql server
Open Sql Server Management Studio -> Connect
Expand the databases that stores your SharePoint content -> Security -> Users
Right click user name obtained in step 6d -> Properties
In Owned Schema and Membership check db_owner
You shouldn't mess with Database unless absolutely necessary. Try this:
$webApp = Get-SPWebApplication http://contoso.com
$webApp.GrantAccessToProcessIdentity("contoso\ServiceAppID")
In our situation, there were errors in event log on the app and WFEs for a bunch of services including the Visio graphic service:
System.IO.FileLoadException: Loading this assembly would produce a different grant set from other instances
I went in to the Visio Graphics Service Settings > Global Settings and looked at the value in the Unattended Service Account, meaning it was registered with the secure store service. I went in to the secure store service and got the following error:
Cannot complete this action as the Secure Store Shared Service is not responding. Please contact your administrator
Recycling IIS on our app server resolved both the issues, so obviously the services having problems were a result of the secure store service being down.
If in the Windows Events the following error is being logged:
Failed to access the cache.
Then, on your SharePoint Web Front End servers, run the following command in the command prompt or PowerShell:
iisreset -noforce

SharePoint List data source giving HTTP 401 "Unauthorized" error

I have built a report that uses a SharePoint list as its data source. The data source is set to use Windows Authentication (integrated security) in SSRS. It runs just fine in SSRS/BIDS, but when deployed to the Report Manager environment, I receive an error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'ListData'. (rsErrorExecutingCommand)
An error occurred when accessing the specified SharePoint list. The connection string might not be valid. Verify that the connection string is correct. (rsSPDataProviderError)
The request failed with HTTP status 401: Unauthorized.
I have deployed both the report object and the data source to the environment from BIDS. I checked the Properties to confirm that integrated security was set on the Report Manager end as well, so I am not sure as to why it's not passing the credentials properly to the source.
Any ideas/suggestions?
The service account for SSRS will not help you. It is good to have a specific service account to run the SSRS service, but that is not what gets used to authenticate. It is also good to set up an execution account on the server using the reporting services configuration tool which helps with running unattended reports, but again that's not your issue.
Kerberos is one option, yes, but if you aren't using it already it's a big effort for a small issue.
Sharepoint list datasource will only accept integrated security connections, so what you need to do in the datasource is to store a windows user as credentials in the report server.
I usually create a user called Reportuser (e.g. reportuser#[domain].com). Create this user on your domain, make sure it has access to SharePoint.
In BIDS/visual studio in the properties for the datasource for your report, under the credentials tab, click the radio button next to "Use Windows Authentication (integrated security)".
Upload the datasource to the report manager website. ( You've done this part).
Navigate to the Report manager website, and the properties of the uploaded datasource.
Under the section starting with "Connect using":
Check the "Credentials stored securely in the report server" option
Enter the username and password like this (where domain is replaced with the domain of your network):
reportuser#domain.com
password
Important part: Tick the "Use as Windows credentials when connecting to the data source"
Test the connection and will work - I have just tested it.
Check these cases:
use the second option in Connect Using section for datasource. Check attached Image.
Check whether you have configured all the web.config entries correctly. You can trace this type of error by attaching the w3wp process.
I had this very same problem and found out that the account that I was using was incorrect due to SharePoint Designer and Visual Studio using the same credentials. When I tried to deploy my reports I noticed that it failed because it was using a user without permissions. The user was not my currently logged in user. Instead it was the one that I had last used to log into SharePoint Designer. Once I logged into SharePoint Designer using a user who also had the report permissions I wanted it then was able to correctly log in to SSRS using Visual Studio. The windows credentials between those two programs are tied together.

How can I use web service methods to show rdl reports on report viewer remotely and instead of URL and Report Path?

I need to know is there any way that we could use SSRS web Service methods to use as URL for Report viewer? In better way I have a rdl report published on SSRS Web server and from the client side I have a report viewer to get that report from SSRS web server and shows it on my WinForm. Report viewer uses of remote processing mode and URL of the Web server and Path of rdl file. How ever I want to use Web Service methods (if there is any) instead of URL and Path to show my report on my Winform by Report viewer is any one expert knows how to do so?
Thanks
From my experience in reporting services
you can use the report service to get the information of any item in your Report server,
To open(View)any report you will need the report path .
Thanks ,
Sufian

Using a Web Service to access data outside MOSS using AD for authentication

So here is the scenario:
I have a MOSS 2007 box and I want my clients to be able to access a SharePoint site via the internet. I am told that I will be using an IPA and AD for authentication. However I have a DB outside of SharePoint that holds various business data and I want to use Web Services to access the data, manipulate it, and send it back to SharePoint via web parts.
The issue is that, from what I understand, I am going to have to authenticate the AD user every time a request to the Web Service happens. Obviously I dont want to do this every time because they have already authenticated to get onto the site, however I do want each call to have some form of security so its not open calls to my db. I do plan on having other applications access this service outside of SharePoint, so I dont want to have to reinstall the service for each application or even again.
Has anyone had to perform this task or something similar or do you have any suggestions on how to do this?
Thank you in advance and happy coding!
Why not just deploy the webservice to Sharepoint using a Sharepoint solution and a Feature.
That way it will be running under the sharepoint app pool and all authentication is done by sp.
Edit:
Seeing that SharePoint should not be in "control" (as stated in the comment), you should create the webservice, and run the application it's under in as using Windows Authentication. IMHO you should create a WCF Service. The, using the information found in this article you make the Service authenticate users against the AD usergroups they are in. see the "Security: Authentication" section of the article.
Then in Visual Studio you create a webpart and add a service reference to the project, pointing to your newly created Service. Have the webpart perform the needed logic (i.e. display data etc.)
Deploy the webpart to SharePoint using a SharePoint solution (.wsp files, created with WSPBuilder). Google for SharePoint + wspbuilder + tutorials. The solution should contain 1 feature to deploy the webpart. WSPBuilder integrates with VS and allows for the creation of WSPBuilde project. add a webpart feature item to the project (it will create the xml (deployment related) and code file for the webpart.