Getting an error on the Enterprise Gateway
The following exception occured while the managed iDbconnection
interface was being used the keyword isn't supported: Version
What can be done to fix this?
I was having the same issue, and apparently the cause this error is when you create a manual table by using the 'Enter data' option. I had a data table with just one row but Power BI didn't like that, and kept giving the same error on each refresh attempt. Removing the the table altogether eliminated this error.
http://community.powerbi.com/t5/Service/The-keyword-isn-t-supported-version/td-p/23372
Thanks
Kaz
Related
I have created a VIEW in Amazon Athena using:
CREATE OR REPLACE VIEW sentiment_analysis AS
SELECT
file,
Sentiment,
SentimentScore.Positive AS Positive,
SentimentScore.Negative AS Negative,
SentimentScore.Neutral AS Neutral,
SentimentScore.Mixed AS Mixed
FROM "targeted_sentiment_output"."sentiment_results"
The VIEW works and populates with the data.
I am now trying to load this into Amazon QuickSight, but get the following error:
Your database generated a SQL exception. This can be caused by query timeouts, resource constraints, unexpected DDL alterations before or during a query, and other database errors. Check your database settings and your query, and try again.
I think it may be a timeout error. I have tried to find the Advanced Settings tab to increase the query timeout limit but can't find it. Please can you provide clear instructions on where to locate the timeout limit?
If it is a different error then please explain...
Thanks!
I'm facing major issue in power bi when no data found on earlier data available web resource. Due to this issue I'm not able to apply change in dashboard and advanced editor derived steps throwing an error.
Load was cancelled by an error in loading a previous table
How to resolve the same by creating static tables headers when no data found on resource
You need to add a dummy table with your headers and some dummy info your power query statement. If the data sources doesn't exist then it returns the dummy table and the power query completes, but is an elegant fail. This approach by Chris Webb explains it
https://blog.crossjoin.co.uk/2014/09/18/handling-data-source-errors-in-power-query/
My report was running normally yesterday but now the report on power bi service gives an error of A query failed due to an invalid table, column, or object name.
The gateway is online and doesn't seem to have any issues regarding that.
The report works fine on power bi desktop.
I could not figure out the exact issue for this error.
Could anyone please help me figure this out?
This is what I Get from show details
Not much detail here.
The solution to my question was simple. I work on the .pbix on my local machine and deploy the .pbix to the service linking live database from RDP.
The issue was column name difference in the local database and the live database.
I figured this out by comparing each tablename and columnname for all the tables in both databases.
Within Power BI (On cloud) console, the datasets screen is showng errors in form of alert icon, in detail the error for all of them is :
Something went wrong
Unable to connect to the data source undefined.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: <TABLE_NAME>.
Underlying error message: AnalysisServices: The following system error occurred:
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.DataSourceKind: AnalysisServices
Microsoft.Data.Mashup.ValueError.DataSourcePath: <path1>;<path2>
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
Activity ID: 259c4fc7-dde9-449b-b108-9498b001ea25
Request ID: 56d4ee25-b539-4c05-8cd4-24b894507475
Time: 2019-06-13 12:12:51Z
I already reviewed gateway/ Analysis services but seems to be OK, Any idea what additional to review?
You may check the different privacy level settings in Power BI Desktop and Power BI Service. Make sure you have the same privacy level security.
Check Power BI gateway logs. For example, I received the same error message. Log information showed connectivity issue to SQL. I checked the server, and named pipes was disabled in client protocols. Since the report data source was configured by server name, connectivity could not work. Enabling it resolved the issue.
I have one Tabular SSAS project & I have deployed it on SQL Server Analysis Service 2012.
Then I have created a BISM connection to that deployed project as in following way.
Then I have created one PowerPivot excel report out of that BISM workbook using its connection string & it is working correctly in Excel.
But when I upload it to the SharePoint, it give me following error while refreshing the Data from BISM workbook.
this error is observed only when I open it on browser i.e. Excel Web Access.
but the same error is not observed when I refresh the report in Microsoft Excel 2013.
why is it giving error on only SharePoint i.e. Excel Services. due to this I am not able to change Slicer's either.
One of the solution I found was to use some Hot Fix of SQL Server. but I haven't tried this. Plz refer the below link Hot Fix for SQl Service Pack 1 Update
Please help!
Thanks in advance.
This refresh should be possible, assuming permissions are set up correctly. You should post ULS logs for the time period of the refresh.
Does this same thing happen if you do a scheduled refresh (and choose refresh now)?