Forum Discussion
Power BI Hangs on Loading Data to Model
It seems that a reboot of the machine running PBI desktop fixed the issue. I got prompted for a Windows Update and after install of that update the issue went away. Had nothing to do with firewall or network traffic (that didn't seem logical to me since I could preview the data and communicate with the SQL Server using Direct Query and also I could work with the data in Power Query). Anyway I hope this helps someone else.
Hi RAC_GAVIN ,
Because of you mentioned that you use the DQ mode to connect the database correctly, but the mode which you need IMPORT OR LC is unsuccessful. It may be the dataset problem.
The import mode needs that the dataset is not allowed over 1GB. Or your model has too many functions.
Could you please check your dataset?
Best Regards,
Community Support Team _Yinliw
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi - No I can say the dataset or anything in the report is definitively Not the issue. I downloaded a MSFT sample database backup and I encounter the same problem on this network, but when I use that same backup on a laptop with SQL Server (not connected to any network) the data from the table is loaded into the model without issue.
I am guessing it has to do with something network related, although I am not sure what that could be yet. I'm not sure if the Firewall is a logical place to think the problem originates from .. as this is internetwork traffic - it's simply power bi desktop communicating with the SQL Server? If anyone has a good suggestion on how to be most efficient in troubleshooting please advise.
I have pinged an IT resource for help and think this article may be of help to garner some kind of useful information on where it is hanging (since I am not getting an error message and it just spins forever): Power BI Desktop diagnostics collection - Power BI | Microsoft Learn.
My next planned step is to turn on diagnostics and see where the log file stops and then compare that to the laptop with the same database that doesn't have the problem.