Forum Discussion
Refreshing data never goes right, help?!
Hi ltkort,
Firstly, after you use personal gateway to configure schedule refresh for your ODBC data source, do you check if there are any other errors in Refresh history? According to the above error message you mentioned, it can be caused by that there are incorrect date values in data source. In your scenario, you will need to correct these illegal data values to make schedule refresh work properly. There is a similar thread for your reference.
Secondly, in Power BI Service, you can specify different time to refresh the dataset and it can only be 8 times during a day. How long will the dataset refresh once? It depends on your schedule time.
Thirdly, you can use on-premises gateway to schedule refresh for ODBC data source, we should put connection string using dsn which reflects “Driver={ yourdriver};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;”.
Thanks,
Lydia Zhang
- ltkort9 years agoFrequent Visitor
Okay, so if i use the driver: MySQL ODBC 5.3 Unicode Driver, my database / username is Lars_V4 and password is PASSWORD, and my server adres is 123.henk.123.nl
What should my connection string be? - ltkort9 years agoFrequent Visitor
Anonymous Okay, I figured it out. I now have a on premise data gateway, I added the datasources and they are connected.. But when I am in Schedule refresh I cannot click on manage gateways... I do not know whats wrong
- Anonymous9 years agoNot applicable
Hi ltkort,
When we add data source under gateway, we should input connection string like"dsn=sourcename". For more details, you can review the following screenshots.
1. Check your odbc source name(testodbc1 in my scenario) in Power BI Desktop.
2. Add data source under gateway by entering connection string , account and password .
3. Schedule refresh for dataset in Service.
Thanks,
Lydia Zhang- ltkort9 years agoFrequent Visitor
Anonymous Thank you it works!
I still have one problem.. I get the following error:Data source errorNot a legal OleAut date.. The exception was raised by the IDataReader interface.Cluster URIWABI-NORTH-EUROPE-redirect.analysis.windows.netActivity IDdf5e0578-48fd-480c-bba9-f1c084426223Request ID25f1cd98-a41d-ce77-4e2b-a152dbbddd9bTime2016-09-22 09:42:18Z
Is there a way to check which date field this is? I have over 45 collums with date's. And the solution you send me earlier does not work for me. I have a Date/Time stamp, if i convert this to whole number and change it back it does not change the time (it stays on 00:00:00). I tried it and it takes a long time (over 2.000.000 records).
Is there a way to check where exactly it goes wrong? Is there a log or something where this is stated? Or can I run a script that tracks this?