Power View issue

can't use Power view in Excel 2013. When clicking Insert -> power view, I got the error such as "can't load data model", then the error "exception from HRESULT: 0x800A03EC" is got.

Hi,
Did the same error pop up when you clicked Power Pivot > Manage or Add to Data Model? If it was, this issue might be caused by the Office
2013 application did not install correctly.
I recommend we repair Office 2013 or use a new installation copy to reinstall it. (If you are using 64bit operation system, please install the 64bit Office. Some of our customers fix the issue by using this method.)
Hope it's helpful.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Similar Messages

Power view in SharePoint - Changing the default save location?

Is it possible to change the default location when saving Power view back into SharePoint?
Our users are creating their own power view reports by clicking a power view shared data source in SharePoint document library.
When saving their reports, the default location is always the same location where the data source is. This is described here also:
https://support.office.microsoft.com/en-us/article/Power-View-in-SharePoint-Server-Create-save-and-print-reports-f616575e-02bf-46cd-b94a-b744245ef9d1?CorrelationId=a852221e-b063-4020-a20a-53d8e8fb8b8b&ui=en-US&rs=en-US&ad=US
Quote from the link: "The first time you save the
report, the default location will be the folder where the model is located."
Ok, understood. But is it possible to change this???

Hi again
Ouch! Not the network!
One of the hard learned issues that folks are unaware of until they encounter problems is that Captivate does not do well when a project is stored on a network. It's fine to keep projects there in order to back them up or as a transfer pivot location to allow others to edit, but you never want to open Captivate, click File > Open and browse to a network location to open a project for editing.
Best practice at this point is to keep projects on your local C drive when you make edits.
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

Remove Blank Values from Slicer in Power View

Hi all,
I am trying to create a power view report from a power pivot data model. After creating the model when I try to use the slicer in power view I am seeing the Blank record. Then I checked that dimension in model where I don't have any blank value in there.
Also I checked in fact table where it has a relationship with that dimension and I don't see any blank value there as well.
I am currently blocked with this issue. Experts please jump in and give some ideas how to remove blank value from there.
Thanks

As MM-99 already stated correctly, the BLANK-member is created if there is one or more non-matching row in your fact-table that does not exist in the dimension-table
maybe you have some issues with upper and lower case?
or maybe there are some whitespace characters contained in the text?
to identify the issues you may want to create a calcuated column in your fact-table as =RELATED('DimTable'[MyKeyColumn])
then you can filter on that column and see if any blank values appear
hth,
gerhard
Gerhard Brueckl
blogging @ http://blog.gbrueckl.at
working @ http://www.pmOne.com

Cannot connect to specific Cube through BI Semantic Model for Power View in SharePoint 2013

I'm trying to create a connection to an Analysis Services Cube through a BI Semantic Model connection in SharePoint 2013 to create a Power View report. I'm able to connect to other cubes on the same server, and I have SQL Server 2012 SP1 Update 9 installed
so it's not a versioning issue.
I've captured a log of two different connection attempts to show this in action. I can't post links, but just send me a message if you need it, just in case there's any interest in it. The first is a successful connection to an alternate cube
on the same server, and the second is an unsuccessful attempt that produces and error with "Internal error: An unexpected exception occurred.".
On the SharePoint side, the error is reported as:
Internal error: An unexpected exception occurred. ---> Microsoft.ReportingServices.DataExtensions.AdomdTestConnectionException: Internal error: An unexpected exception
occurred.
This cube was working the previous day, but it has since been edited and it no longer works now but there's no clear reason why. It can still be queried directly through SSMS with MDX queries, and produces no errors.
Any help is much appreciated,
Ryan

Hi Ryan Myers,
According to your description, when you tried to connect to an Analysis Services Cube in SharePoint 2013 through BI Semantic Model, you get the error message: Internal error: An unexpected exception occurred. But the MDX queries works fine in SSMS.
It's hard to give you the exact reason that cause this issue based on the limited information, please validate if the connection string is correct. Besides, we can troubleshoot this issue by using the Windows Event logs and msmdsrv.log.
We can access Windows Event logs via "Administrative Tools" --> "Event Viewer". SSAS error messages will appear in the application log.
The msmdsrv.log file for the SSAS instance that can be found in \log folder of the instance. (C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log)
Reference:
Data collection for troubleshooting Analysis Services issues
Data Connection For a Power View Report
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.

Power View for Sharepoint 2013 'Feature not available'

Hello All,
We are trying to set up Power view in Sharepoint but every time I click the power button on a report we get the "The
feature: "Power View" is not supported in this edition of Reporting Services." error.
Our setup consists of two servers. One is the sharepoint 2013 Enterprise server and the other is our DW server that sits outside of the farm.
The DW Server has Sql 2012 SP1 (Enterprise) and two instances of AS, one in multi-dimensional mode and one with power pivot for SP.
We were able to get power pivot working with Sharepoint without issue but we can't seem to get Power View to work. I've read through some threads but it still doesn't seem clear what I need to do. Someone mentioned that we needed to install Sharepoint
on the DW server but we would like to avoid that if we can due to the current load on the server. Another suggestion was to install the RsSharepoint on the sharepoint server and that would enable power view.
I know there is already an RS Service app, would that needed removed as well?

Only SQL BI and SQL Enterprise have the appropriate edition of Reporting Services to enable PowerView:
http://technet.microsoft.com/en-us/library/cc645993(v=sql.110).aspx#Reporting
You would need to uninstall SSRS using SQL Standard and re-install with BI or Enterprise on the SharePoint server.
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.

Power View can only print one sheet at a time with Power BI Mobile Apps

I have PowerView for Excel 2013 on Power BI Preview. I have 2 reports sheet and 2 hidden data sheets on Excel.
I'm getting error on Mobile Application in Windows 8 RT tablet.
I should see 4 reports in preview page, but I see 2 correct reports and 2 errors.
Power View can only print one sheet at a time. Please switch to the desired sheet and try again.
Why this occurs? What should done in Excel?
Kenny_I

Thank you for reporting this issue. This is a known issue that we had fixed last week. In a few days, the updated version of the app will be available in the Windows store. At that time, your app should automatically get updated to the newest version, if
you have not changed your default settings.
If you still experience issues next week this time, please post back and perhaps share your workbook, so we can do a thorough investigation.
Thank you.

Range Filter Mode not working and throws error in Power View (SharePoint 2013)

Hi,
I am using two filters in my power view report.
One for the contact type group and one for year.
First I select multiple contact type group for the first filter and everything works fine.
Then I try to select the year using the range filter and I get this error:
System.ArgumentException: The name 'Year' was specified twice, at index 0 and index 1. Duplicate names are not allowed.
Parameter name: keys[1]
at Microsoft.Data.Common.CommandTrees.ExpressionBuilder.Internal.EnumerableValidator`3.Validate(IEnumerable`1 argument, String argumentName, Int32 expectedElementCount, Boolean allowEmpty, Func`3 map, Func`2 collect, Func`3 deriveName)
at Microsoft.Data.Common.CommandTrees.ExpressionBuilder.Internal.EnumerableValidator`3.Validate()
at Microsoft.Data.Common.CommandTrees.ExpressionBuilder.Internal.ArgumentValidation.ValidateGroupBy(DbGroupExpressionBinding input, IEnumerable`1 keys, IEnumerable`1 aggregates, DbExpressionList& validKeys, ReadOnlyCollection`1& validAggregates)
at Microsoft.Reporting.QueryDesign.ExpressionTrees.ExpressionBuilder.Internal.QueryExpressionBuilder.GroupBy(QueryGroupExpressionBinding input, IEnumerable`1 groupItems, IEnumerable`1 aggregates)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.QdmExpressionBuilder.QdmGroupBy(IEnumerable`1 expressions)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.QdmExpressionBuilder.QdmFilter(IGrouping`2 predicates)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.QdmExpressionBuilder.QdmFilters(IEnumerable`1 filterConditions)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.FilterQueryFactory.AddRowCount(QueryBuilder queryBuilder, Group group, EntitySet entity, IEnumerable`1 rowCountFilterContext)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.FilterQueryFactory.CreateValueWithCountQuery(QueryBuilder queryBuilder, List`1 columns, IEdmFieldInstance fieldInstance, FilterCondition availableValueFilter, FilterCondition activeValueRetentionFilter,
GroupReference& groupRef)
at Microsoft.Reporting.QueryDesign.QueryDefinitionModel.Internal.FilterQueryFactory.CreateValueListQuery(EntityDataModel model, IEdmFieldInstance fieldInstance, Int32 topCount, FilterCondition availableValueFilter, FilterCondition activeValueRetentionFilter,
IEnumerable`1 exclusionPathSegments, ValueListQuerySchema& schema)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterValueQueryFactory.CreateFilterValuesQuery[TFilterMode](TFilterMode filterMode, Int32 maxRowCount, FormulaFilterCondition availableValueFilter, FormulaFilterCondition
activeValueRetentionFilter, ValueListQuerySchema& schema)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.ListFilterMode.ListDataLoader.<LoadDataImpl>d__15.MoveNext()
at Microsoft.Reporting.AsyncEnumerator.AsyncEnumeratorBase.MoveNextChecked()
at Microsoft.Reporting.AsyncEnumerator.AsyncEnumeratorBase.ResumeIterator(Boolean synchronous)
at Microsoft.Reporting.AsyncEnumerator.AsyncEnumeratorBase.BeginExecuteCore(IEnumerator`1 asyncMethod)
at Microsoft.Reporting.AsyncEnumerator.AsyncEnumeratorImpl.BeginExecute(Func`2 asyncMethod)
at Microsoft.Reporting.AsyncEnumerator.BeginExecute(Func`2 asyncMethod, AsyncCallback userCallback, Object userState, AsyncEnumeratorSettings settings)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterMode.DataLoader`1.BeginLoadData(AsyncCallback userCallback, Object userState)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterMode.DataLoader`1.LoadDataAsync()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FieldFilter.LoadDataAsyncCore()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterManager.OnEditCompleted()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.PageFilterManager.OnEditCompleted()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.FilterManager.OnEditCompleted(EventArgs args)
at Microsoft.Practices.Prism.Events.EventSubscription`1.InvokeAction(Action`1 action, TPayload argument)
at Microsoft.Practices.Prism.Events.EventSubscription`1.<>c__DisplayClass2.<GetExecutionStrategy>b__0(Object[] arguments)
at Microsoft.Practices.Prism.Events.EventBase.InternalPublish(Object[] arguments)
at Microsoft.Practices.Prism.Events.CompositePresentationEvent`1.Publish(TPayload payload)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionManager.EditEventAggregator.Exit()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionManager.EditEventAggregator.SelectionManager_SelectionResumed(Object sender, EventArgs e)
at Microsoft.Reporting.Util.RaiseEvent(EventHandler eventHandler, Object sender, EventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Regions.Canvas.Internal.SelectionManager.ResumeSelectionChanges()
at Microsoft.Reporting.AdHoc.Shell.Regions.Canvas.Internal.SelectionManager.<.ctor>b__3(Object s, EventArgs e)
at Microsoft.Reporting.Util.RaiseEvent(EventHandler eventHandler, Object sender, EventArgs eventArgs)
at Microsoft.Reporting.AdHoc.DataManagement.Internal.DataManager.set_HandleRdmChanges(Boolean value)
at Microsoft.Reporting.AdHoc.DataManagement.Internal.DataManager.UndoManager_SuspendRdmHandlingChanged(Object sender, StateChangedEventArgs`1 args)
at Microsoft.Reporting.Util.RaiseEvent[TEventArgs](EventHandler`1 eventHandler, Object sender, TEventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoManager.<.ctor>b__0(Object sender, StateChangedEventArgs`1 args)
at Microsoft.Reporting.Util.RaiseEvent[TEventArgs](EventHandler`1 eventHandler, Object sender, TEventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoManagerApiProperties.set_SuspendDataManagerRdmHandling(Boolean value)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoManagerHasOpenUndoGroupStateImpl.OnUndoGroupCommitting(UndoGroup undoGroup)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoManagerHasOpenUndoGroupStateImpl.HandleUndoGroupStateChanged(Object sender, EventArgs args)
at Microsoft.Reporting.Util.RaiseEvent(EventHandler eventHandler, Object sender, EventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroup.HandleStateEnteredEvent(Object sender, EventArgs args)
at Microsoft.Reporting.Util.RaiseEvent(EventHandler eventHandler, Object sender, EventArgs eventArgs)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroupCommittingStateImpl.EnterState()
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroup.SetState(UndoGroupStateImpl nextState)
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroupOpenStateImpl.Commit()
at Microsoft.Reporting.AdHoc.Shell.Services.UndoManagement.Internal.UndoGroup.Commit()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionManager.CompleteTransaction(Transaction transaction, Boolean completedSuccessfully)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionManager.Transaction.Dispose()
at Microsoft.Reporting.AdHoc.DataStructureManagement.Internal.TransactionalObject.ExecuteInTransaction(Action action)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.ValueAndOperatorConditionFilterMode.CreateRangeFilterCore(IList`1 rangeConditions)
at Microsoft.Reporting.AdHoc.DataStructureManagement.Filtering.Internal.NumericRangeFilterMode`1.CreateRangeFilter(FilterValueAndOperator[] rangeConditions)
at Microsoft.Reporting.AdHoc.Shell.Regions.Canvas.Internal.RangeFilterViewModel`1.<get_UpdateRangeBoundsCommand>b__0(Nullable`1 adjType)
at Microsoft.Practices.Prism.Commands.DelegateCommand`1.<>c__DisplayClass6.<.ctor>b__2(Object o)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.Execute(Object parameter)
at Microsoft.Practices.Prism.Commands.DelegateCommandBase.System.Windows.Input.ICommand.Execute(Object parameter)
at Microsoft.Reporting.Windows.Common.Internal.RangeSlider.FireCommand()
at Microsoft.Reporting.Windows.Common.Internal.RangeSlider.Thumb_DragCompleted(Object sender, DragCompletedEventArgs e)
at System.Windows.Controls.Primitives.Thumb.RaiseDragCompleted(Boolean canceled)
at System.Windows.Controls.Primitives.Thumb.OnLostMouseCapture(MouseEventArgs e)
at System.Windows.Controls.Control.OnLostMouseCapture(Control ctrl, EventArgs e)
at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32 actualArgsTypeIndex, String eventName, UInt32 flags)
If I select List Filter mode and try to achieve this it works fine no issue but when I use range filter this weird problem occurs. Can't I select multiple values using Range Filter Mode ? Isn't that's what it is intended to do ? Is it a known bug ? Any kind
of prior experience or help would be much appreciated.
Vivek Kamath

This looks like it could be a bug. You could file an issue at
http://connect.microsoft.com and include a repro. If this is blocking your business, you could also contact support services and if it is determined to be a defect in a Microsoft product, the support is free.
Brad Syputa, Microsoft Power BI This posting is provided "AS IS" with no warranties.

SQL Server Reporting Services SharePoint Integrated mode - Power View is not supported

Hi there,
My environment is the following:
SharePoint Server 2013
SQL Server 2012 SP1 Enterprise edition
I am getting the following message when trying to open BISM item with PowerView icon:
"The feature: "Power View" is not supported in this edition of Reporting Services."
My problem is that the first time I installed SQL Server Reporting Services SharePoint integrated, I used the SQL Server 2012 Standard edition ISO. But then I learned that Power View is only available with Enterprise and BI editions. So I uninstalled Reporting
Services Add-in from Control Panel, Reporting Services from the installation media and deleted the three Reporting DBs in the SharePoint DB server.
Then I used SQL Server 2012 SP1 Enterprise media to install again Reporting Services but not sure why I am still getting the message:
"The feature: "Power View" is not supported in this edition of Reporting Services."
Anyone can advice me what could be the problem? Maybe I have not complete deleted the previous SQL Server Reporting Service Share Point integrated mode from the previous installation? What would be the proper way to uninstall Reporting Services?
Any help will be welcome.
Thanks and best regards,
Joss

Hi Joss,
I am in the same situation,
SQL Server was installed in the standard mode because of that the powerview option is not working.
I have changed teh edition using maintenance --> upgrade edition. the sql server components like DB engine, SSAS and integration services are now showing in enterprise edition. The reporting services are installed from the application end still showing
as the reporting services are standard.
we reinstalled the reporting services but still persists the issue.
suggest me is there any work around to fix the issue other than reinstalled the whole SQL Server.
Thanks
Ramu

How to build high usability navigation for Power View on SharePoint 2013?

I have Power View on SharePoint 2013. I have both SSAS Multidimentional and Tabular model in use.
I have several Report.drlx file in Report libary in SharePoint.
When I click the file, it works fine, but I feel that there are usability problems like:
A) Getting back to SharePoint site is not intuitive. Difficult to find home.
B) Diffucult to move between report to another. Need to return Document library.
What is best practise for displaying several Power View reports on SharePoint?
Kenny_I

Hi Kenny_I,
Just as you said, we cannot directly navigate to Home page when we view an .rdlx report in SharePoint site. We need click the Arrow to go to the previous page (Document Library), then click “Home” to navigate to Home page. If we want to move from a report
to another report, we should still use the same way. This is by design.
If you want to jump from one report to another report, we can add a hyperlink to a text box in a sheet or view. Personally, I understand your feeling and how frustrated when you find this issue. So, it is my pleasure to help you to reflect your recommendation
to the proper department for their consideration. Please feel free to submit your situation on our product to the following link:
https://connect.microsoft.com/.Your feedback is valuable for us to improve our products and increase the level of service provided.
Thank you for your understanding.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Unable to generate Power View report out of Multidimensional report data source

Hi,
I have created 'Report Data Source' connection to point to Multidimensional cube on Share Point site. But when I try to create a new Power View report out of it, I get following error message :
"An error occured while loading the model for the item or data source 'http://*********/PowerPivot Gallery/TestCube.rsds'. Verify that the connection information is correct and that you have permission to access the data source."
I can see following message in the <moreInformation> section :
<Source>Microsoft SQL Server 2012 Analysis Services</Source><Message>Errors in the metadata manager. The current model can only be expressed when the client is requesting tabular view metadata with VERSION restriction of 2.0 or later.</Message>
Following are the System configurations :
1) SSAS : SQL Server 2012 + SP2 (version 11.0.5058)
2) Share Point 2013
As mentioned in one of the MSDN documents this configuration supports creation of Power View reports on multidimensional cube.
Can any one suggest what might be the issue?
Thanks in advance!

Hi Dipti,
According to your description, you get the connection failure when creating a power view report, and it throws information "Errors in the metadata manager. The current model can only be expressed when the client is requesting tabular view metadata with
VERSION restriction of 2.0 or later." Right?
Based on the error message, the issue should be the SSRS on sharepoint metadata version mismatch when sending to SSAS. There's someone mentioned in a similar thread that this issue can be solved by installing the full package of CU4 for SP1.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/133558cd-ffc8-4608-ae45-fdff01770c6d/powerview-sql-2012-sp1-cu4-cannot-connect-to-dimensional-metadata-version-11?forum=sqlreportingservices
Even you already have SP2 installed, it supposed included CU1~CU9 for SP1. However, it has reported that SP2 doesn't fix all bugs which supposed to be fixed in CU for SP1.
SQL Server 2012 Service Pack 2 is available - but there's a catch!
So please re-install the full CU4 for SP1, restart the services and try again.
Best Regards,
Simon Hou
TechNet Community Support

Power View error: Cannot create a connection to data source 'EntityDataSource'

I have Power View on SharePoint 2013. I have both Multidimentional and Tabular model in use.
I have several Report.drlx file in Report libary in SharePoint.
My colleague is getting following error when building report by dragging Facts and Dimentions to report.
On the hand, I'm not receiving error.
Error is cannot create a connection to data source 'EntityDataSource'
<detail><ErrorCode xmlns="rsErrorOpeningConnection</ErrorCode><HttpStatus">http://www.microsoft.com/sql/reportingservices">rsErrorOpeningConnection</ErrorCode><HttpStatus
xmlns="400</HttpStatus><Message">http://www.microsoft.com/sql/reportingservices">400</HttpStatus><Message xmlns="Cannot">http://www.microsoft.com/sql/reportingservices">Cannot
create a connection to data source 'EntityDataSource'.</Message><HelpLink xmlns="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsErrorOpeningConnection&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=12.0.2000.8</HelpLink><ProductName">http://www.microsoft.com/sql/reportingservices">http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsErrorOpeningConnection&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=12.0.2000.8</HelpLink><ProductName
xmlns="Microsoft">http://www.microsoft.com/sql/reportingservices">Microsoft SQL Server Reporting Services</ProductName><ProductVersion xmlns="12.0.2000.8</ProductVersion><ProductLocaleId">http://www.microsoft.com/sql/reportingservices">12.0.2000.8</ProductVersion><ProductLocaleId
xmlns="1033</ProductLocaleId><OperatingSystem">http://www.microsoft.com/sql/reportingservices">1033</ProductLocaleId><OperatingSystem xmlns="OsIndependent</OperatingSystem><CountryLocaleId">http://www.microsoft.com/sql/reportingservices">OsIndependent</OperatingSystem><CountryLocaleId
xmlns="1033</CountryLocaleId><MoreInformation">http://www.microsoft.com/sql/reportingservices">1033</CountryLocaleId><MoreInformation xmlns="<Source>Microsoft.ReportingServices.ProcessingCore</Source><Message">http://www.microsoft.com/sql/reportingservices"><Source>Microsoft.ReportingServices.ProcessingCore</Source><Message
msrs:ErrorCode="rsErrorOpeningConnection" msrs:HelpLink="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsErrorOpeningConnection&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=12.0.2000.8"
xmlns:msrs="Cannot">http://www.microsoft.com/sql/reportingservices">Cannot create a connection to data source 'EntityDataSource'.</Message><MoreInformation><Source>Microsoft.AnalysisServices.AdomdClient</Source><Message></Message><MoreInformation><Source>Microsoft.SharePoint</Source><Message>Could
not retrieve a valid Windows identity.</Message><MoreInformation><Source>mscorlib</Source><Message>WTS0003: The caller is not authorized to access the service.</Message></MoreInformation></MoreInformation></MoreInformation></MoreInformation><Warnings
xmlns="http://www.microsoft.com/sql/reportingservices" /></detail>
Kenny_I

Hi Kenny_I,
As per my understanding, I think this issue may be caused by your colleague has no permission to access to data source 'EntityDataSource', it is a Kerberos issue. When report server uses ‘Windows authentication (integrated) or SharePoint user’ as the credentials
to access the data source 'EntityDataSource', the authentication would be failed. So we should try to check if the issue is in this scenario. If in this case, we should change the credentials to stored credentials.
Besides, if we don’t configure C2WTS Service Account to use Local System, it needs the following local policy rights:
Act as part of the operating system.
Impersonate a client after authentication.
Log on as a service.
For more details, please refer to the following blog:
http://www.codeovereasy.com/2014/01/powerview-report-fails-no-credentials-are-available-in-the-security-package/
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Power View stuck in loading forever in SharePoint

Hi, we have just configured a new SharePoint instance. We've installed and configured PowerPivot, SSRS SharePoint mode, Excel Services, Performance Point Services, and Silverlight. We uploaded a workbook to a BI site. The workbook contains both standard
Excel sheets and Power View sheets. The standard Excel sheets can render without any problems. But the Power View sheets are stuck in loading. All I see is this loading circle:
There's no error message, and nothing stands out in the logs. We're indeed not sure what's going on. Since there's a loading circle, we assume SSRS is working? Does anyone have ideas? Thanks.
Shining Oh Blue Star

The post on
http://blog.qumsieh.ca/2013/08/19/ssas-sharepoint-2013-we-cannot-locate-a-server-to-load-the-workbook-data-model/ helped us to solve the issue. Basically, several ports on the SSAS server need to be exposed through firewall. These include:
SSAS PowerPivot port: 2382
Standard SSAS port: 2383 (may not be definitely necessary if you only use PowerPivot)
And also, the trickest part: A dynamic port that seems to be different on each installation. In the blog author's case, it was 49165. In our case, it was 62578. To find the port, use Power Query (or another query tool) to load SharePoint's
ULS log, and filter Category to see Data Model only. You'll see the port number in one of the logs which begins with "Uncaught CLR exception crossing the Interop boundary".
I take the problem as solved. But hopefully Microsoft can give us more information on why a dynamic port needs to be opened in firewall, and why it is so difficult to track down the root cause...
Shining Oh Blue Star

MDX not working in Power View on sharepoint 2013

I have this MDX statement below that should be able to dynamically give me a % of total for any dimension. IN power View (sharepoint 2013)
I am getting an error. It works in Excel and works in the AS browser but will not seem to work in power view. Any ideas on how to rewrite it so that it may work. I am surprised I cannot find anything on this online about this issue.
When you highlight the "#ERROR!" in Power view it gives a long description of
"The Axis Function was indirectly referenced from the context of a statement other than SELECT. Evaluations of Expressions involving this function succeed only
when indirectly triggered by a SELECT statement".
CREATEMEMBERCURRENTCUBE.MEASURES.[Percent
of Total] AS
//Used to get % from total
IIF([Measures].[Total Count] = 0,
NULL,
IIF(isempty( ([Measures].[Total Count],
Axis(1)(0)(Axis(1)(0).Count-
1).Dimension.CurrentMember.Parent
)), 1,
[Measures].[Total Count] / ([Measures].[Total Count],
Axis(1)(0)(
Axis(1)(0).Count-
1 ).Dimension.CurrentMember.Parent))),
FORMAT_STRING="#,##0.00
%;-#,##0.00 %";

Hey Mike, Thank you very much for the answer. Just need a little more help please???
I have added two separate MDX statements that should get the individual % for these two separate dimensions.
1. First does it look correct from what your saying individually. Would you write it different?
2. Next can you show me the MDX that would combine them into 1 measure. Once I can see how these two get combined into 1 measure I should be able to do this for the rest of the dimensions.
3. Will Power View ever allow Axis function? Just seems strange that it works in Excel Pivot but not in Power View.
WITH MEMBER [Measures].[Percent] AS
Case
// Test to avoid division by zero.
When IsEmpty ([Measures].[Total Count]) Then Null
// Test for current coordinate being on the (All) member.
When [Status].[Status Name].CurrentMember.Level Is [Status].[Status Name].[(All)] Then 1
Else ( [Status].[Status Name].CurrentMember, [Measures].[Total Count] )
/ ( [Status].[Status Name].CurrentMember.Parent, [Measures].[Total Count] )
End
, FORMAT_STRING ="#,##0.00 %;-#,##0.00 %"
SELECT
{ [Measures].[Total Count],[Measures].[Percent] } ON COLUMNS,
{ [Status].[Status Name].[Status Name]} ON ROWS
FROM [Report]
WITH MEMBER [Measures].[Percent2] AS
Case
// Test to avoid division by zero.
When IsEmpty ([Measures].[Total Count]) Then Null
// Test for current coordinate being on the (All) member.
When [Order Placed Date].[Order Placed Date].CurrentMember.Level Is [Order Placed Date].[Order Placed Date].[(All)] Then 1
Else ( [Order Placed Date].[Order Placed Date].CurrentMember, [Measures].[Total Count] )
/ ( [Order Placed Date].[Order Placed Date].CurrentMember.Parent, [Measures].[Total Count] )
End
, FORMAT_STRING ="#,##0.00 %;-#,##0.00 %"
SELECT
{ [Measures].[Total Count],[Measures].[Percent2] } ON COLUMNS,
{ [Order Placed Date].[Order Placed Date].[Order Placed Year]} ON ROWS
FROM [Report]

Power View Line Chart - Line size

Hi,
Is it possible to change the thickness of lines on a line chart in Power View? How can we interact with axis to change them to logarithmic scale or create double axis?

Hi Tim,
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

Power View in Excel 2013 not staying visible

hello,
i have only been using power view (and power query) for a little while, but noticed that when i open a workbook that has power view sheets, power view is not automatically opened. when i first open the workbook, i see a large blue square on a worksheet
in order to use power view, i have to click on the power view tab, then click the power view button.
is this the way the software is suppose to work?
if it helps, i am running office professional pro plus, excel 2013, with windows 8.1
i don't know if this matters, but i checked to make sure that power view is installed and it is.
any help would be greatly appreciated.
thank you
tracy

hi ed and will,
i think you guys are spying on me - of course, i am right-clicking on the excel icon on the task bar and selecting the workbook that i want to use. isn't that why the files are there - LOL
okay, so i took the loooooooooooooong way, i opened excel, by clicking on the icon on the task bar. a blank workbook opened.
then i opened the workbook that i wanted to use
that power view window with the red circle appeared.
i opened the add-ins screen and power view is installed/enabled.
hmmm, if this hasn't been logged as an issue by someone else already, could there be something wrong with my workbook files or worse, my laptop.
i don't see a frown/smile button in excel - where is it?
this isn't looking so good.
what do you guys think is going on?

Power View issue

Similar Messages

Maybe you are looking for