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.
Related
Hi I am the beginner developer, I am trying to send my data to sql from VS and I did Migration process. in packing manager console I wrote enable-migration and now I got configuration file also and after than I changed the value from false to true and wrote update-database I am not getting error its just says
PM> update-database
Specify the '-Verbose' flag to view the SQL statements being applied to the target database.
No pending explicit migrations.
Running Seed method.
and when I checked sql there is no my database also any tables
I am trying to make travel website and there are some page exist and I got some models files of them and I guess I need to create connection between sql and vs I had the code in vstudio but when I try to create database and tables with my datas in studio, its not happening
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.
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)?
I'm using SQL Server 2005 with Reporting Services. I have many reports installed, some using shared data sources and some not; some go to web services, some to sql server databases, and now I'm trying to connect to a DB2 database.
I have successfully created a shared data source and report in Visual Studio 2005. I can pull data just fine and display it on my report in the designer. I am now trying to install the report and datasource through the ssrs web service (the same way I have for all other reports).
The problem is that most of our data sources use Integrated Security, and for this data source I am using 'Credentials are not required' since they are listed in the connection string. Here's my install code:
Dim definition As New ServiceProxy.DataSourceDefinition
definition.ConnectString = connectionStringIncludingUsernameAndPassword
definition.Extension = "OLEDB"
definition.CredentialRetrieval = ServiceProxy.CredentialRetrievalEnum.None
ServiceWebService.CreateDataSource(dataSourceName, containingFolderFromRoot, True, definition, Nothing)
This also works fine and gives no errors, and appears to create the datasource properly in ssrs. But when I go to run the report I get this error:
The current action cannot be completed
because the user data source
credentials that are required to
execute this report are not stored in
the report server database.
(rsInvalidDataSourceCredentialSetting)
My report is properly connected to my data source, and my data source is properly set to credentials not required, so it is all the same as it is inside Visual Studio. I'm out of ideas.
The problem was several fold:
the user name and password were listed in the connection string instead of inside the server
the db2 connect software installed on the report server was out of date (8 instead of 9)
the user group 'DB2Users' did not have any members
After correcting these problems, the report works!