I created a Snowflake connection via Power BI Desktop after providing the Server and Warehouse Name; then under Advanced Options I specified the Database and entered the following in the SQL statement text area:
call myStoredProcedureName();
and received a pop-up stating "Unable to connect. We encountered an error while trying to connect. Details: 'Native queries aren't supported by this value'".
This is using Snowflake type connection so what am I missing? If I execute using the same syntax directly in Snowflake, I get the results without any issues.
Forgot to mention that I'm using Import mode, b/c my 1st attempt using Direct mode produced an error clearly stating Direct Mode wasn't supported.
Related
When I tried to connect to my oracle db by using a parameter in power bi it would return with an error after inputting a parameter
THe error
We encountered an error while trying to connect Details: " EvaluateNativeQueryUnpermitted failure: the query SELECT * FROM table isn't approved for execution
I try to use a parameter when connecting in inputting a sql command,
I am trying to connect to AWS Athena from Power BI using the new Athena connector. The first page prompts for a DSN which I supply (and which works when connecting through the old ODBC method) but when the new connector attempts to connect with this DSN the following error is thrown:
Unable to connect
We encountered an error while trying to connect. Details: "We cannot
convert the value null to type Record."
I had the same issue and I figured out the reason it was happening. When you mention your DSN in the Amazon Athena (Beta), the next thing it will ask is your login (which has two options).Do not take the 2nd option. Pick the first option where the all setting are pulled from your DSN settings, which you did to setup your datasource.
Now if you once did it wrong, It won't ask you again the same things to fix it. Create a new powerbi file and do the steps.
As Janzaib mentioned above, you picked the wrong option when you set up your datasource. But you don't need to create a new file. You can click Data source settings and then find the name of the DSN and edit the permissions. Then the setting is pulled from your DSN and you are good to go.
I had to do a strange workaround to get this to work for me. When I selected the Amazon Athena connection type in PowerBI, typed in the DSN name, and hit OK, I got the error above with no way to correct it. To get it to work, I typed a dummy name in the Role entry ("xyz") before hitting OK. Then I was presented with an authentication dialog - where I could select "Use Data Source Configuration," which would work.
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 been trying to connect to a SQL server DB via Power BI Desktop. The connection mode selected is DirectQuery . I am able to establish the connection to the SQL db. But in the report viewer i don't see the table loaded. And i keep getting this popup saying - Unexpected error. Couldn't load the model schema.
But when i open the query editor, i am able to see the table contents and do some transformations. But when trying to load it doesn't come up in the report viewer Fields pane on the right. Again get this error- Couldn't load the model schema.
I have tried the resolution related to windows defender. But get that -resetplatform is not an valid option.
Users can work around this issue by running the following command from
an elevated command prompt: "C:\Program Files\Windows
Defender\MpCmdRun.exe –resetplatform"
In case it helps someone, this is how i solved it.
When trying to connect to SQL server from PBI desktop, skip giving the port number in the server input box. Although the tool tip mentions u can enter as server:port.
By connecting this way, i was able to load the model both in report viewer as well as see data and transform on Query editor.
A very trivial issue. but took quite a while to figure out.
I had the exact same problem on my Windows 7 machine. I then installed the latest Power BI version (Version: 2.62.5222.761 64-bit (September 2018)) from the Microsoft store on my Windows 10 machine. Surprisingly, it worked there.
I'm trying to use an OLEDB connection to connect to my SAS datasets from QlikView.
I am able to set up the connection, but I am not able to load my data. Executing the data import results in the following error: "the local provider does not currently support sql processing"
My loading code looks like this:
LOAD "account",
balance,
"open_closed";
SQL SELECT *
FROM "BASE_DATA";
Is there any way to solve this?
We read SAS data into QlikView using SAS ODBC driver that connects to SAS/SHARE.
This requires that you have one of the following three:
1. SAS/SPD Server
2. SAS/SHARE Server
3. SAS locally on desktop (will not work on server license)