I have an accessDB which using ODBC connection to SQL and used in queries.
Tried to use the queries to create a report on PowerBi, Issue is whenever I tried to update the dataset it gives me ODBC--call failed.
Tried created the ODBC connection on gateway machine. they are all 32 bit [ODBC/Power Bi Desktop] etc.
Can someone please help?
had to install office 64bit and access 64bit driver
also had to refresh all the linked tables and views from access to rectify the issue.
Related
After a Firebird 3.0 update, our PowerBI Dataset can't find the Firebird database, although the ODBC Setup works just fine.
But the most bizarre part, I can create a new Dataflow-set with the exact same data source (same Gateway to ODBC Source) and it works!
I've created a whole new Workspace and uploaded the Dataset/Report into it, the same error occurs.
Some Info:
We've recently updated our Firebird database from 2.5 to 3.0
Our connection worked just fine with 2.5
The ODBC-Source connects to a raw Firebird (main.FDP) database.
A direct connection to the live-Data is not possible, the ODBC-Setup throws an error (File database not found), so I copied the main.FDP into a different folder, that way the ODBC setup connects successfully.
On Power BI Desktop via Power Query Editor, I can see the actual live data, but if I "Close & Apply", the same error occurs (File Database not found) on the refreshing window.
#Mark Rotteveel, thanks for the Solution.
The Solution was the pathing, i added "localhost:[...]" as prefix and it works.
I have SSMS installed on my laptop along with a localdb I created:
I am trying to create a connection with my localdb (in Power BI Service) and my local SQL db via my gateway but I keep getting an error. Here is a screenshot:
I am uploading a report from Power BI Report Builder. I am able to connect using the same credentials on Power BI Report Builder. However, when I enter the credentials on Power BI Service I get an error. Does anyone know why I am getting this error?
Try to install and use the normal SQL Server instead of LocalDB. When connecting to LocalDB, the necessary SQL Server infrastructure is automatically created and started, but I'm not sure that the Power BI Gateway supports that.
In the SnowFlake web interface, the INFORMATION_SCHEMA is visible and accesible. When logging in to PowerBI, with exactly the same user, the INFORMATION_SCHEMA is not shown. The PowerBI report should contain data of the INFORMATION_SCHEMA, how can I get this to be visible in PowerBI
Are you using PowerBI's native connector to Snowflake? Have you tried with the ODBC connector option instead? I ask because I've seen differences in native connectors versus the ODBC option and it's possible the native connector has some limitations that PowerBI can help work out with their native Snowflake connector. Note that the PowerBI team maintains/owns the native connector to Snowflake so you can follow-up with them.
There's also the potential option of using ACCOUNT_USAGE views instead of the INFORMATION_SCHEMA depending on what the user is looking for.
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 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)?