Forum Discussion
Message=Exception while reading from stream, ErrorCode=-2147467 when connecting to a PostgreSQL view
I've been having issues when connecting/ refreshing a specific postgreSQL view in power query editor. I have another view in the same file and that seems to refresh and load without any issues. The refresh/ load issue is maxing out CPU and I get the folllowing error messaging "Message=Exception while reading from stream, ErrorCode=-2147467259". I have tried clearing data source permission as suggested in other threads.
Please can someone advise?
Hi Wenbin,
I did try adding a timeout but that didn't help unfortunately. However changing the view to a materialised view and getting the data as a query has worked!
Thanks,
B
5 Replies
- dharmendars007Memorable Member
Hello bcampos ,
One solution I can think of is go to global Data source settings and remove the source which was connected before and re-connect this should hopefully resolve the issue of refersh.
If you find this helpful , please mark it as solution which will be helpful for others and Your Kudos/Likes 👍 are much appreciated!
Thank You
Dharmendar S
- bcamposFrequent Visitor
Hi dharmendars007 I have tried to achieve this by clearing global data source settings and that has not resolved the issue. Do you have any other suggestions?
Thank you!
- AnonymousNot applicable
Hi dharmendars007, thanks for the quick reply, I'll add more.
Hi bcampos ,
Regarding your question, you mentioned that the CPU usage is very high. Is it because of a timeout during reading? Set the timeout here to see if it helps.
According to this post, you can also check whether it is a firewall problem.
Solved: Postgresql: Exception while reading from stream - Microsoft Fabric Community
Best Regards,
Wenbin Zhou- bcamposFrequent Visitor
Hi Wenbin,
I did try adding a timeout but that didn't help unfortunately. However changing the view to a materialised view and getting the data as a query has worked!
Thanks,
B
- bcamposFrequent Visitor
FYI for anyone who comes across this issue in the future, changing the postgreSQL view to a materialised view has worked as a solution