Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

PBI desktop- Rvisual ends in timeout error after 5 minutes

I am running a regression model (linear model) and displaying a graph through Rvisuals. Everything works fine on my laptop and I receive the output in less than a minute (~40 seconds) in PowerBI R visuals.

 

But on a colleagues laptop the same code ends in timeout error, as in the attachment. I removed the R from his laptop and installed the one that I have (from Microsoft website) and still the same error. When I run the same code in Rsudio in his laptop, the results are delivered under a minute (~40 seconds).   

 

Both of our laptop has 16GB RAM, 64 bit operating system (Windows-10). 

 

This looks strange, as the code which runs on Rstudio is not running in PBI desktop. Has anyone encountered this problem before  or any advise on what else should be compared between our laptops?

 

Rversion used- R-3.5.3

 

Thanks,

Ashvin

  • Anonymous's avatar
    Anonymous
    6 years ago

    Thanks for your message, however its a problem with only 1 Laptop and so I advised the user to reinstall everything. He didn't reported it again so I assume its solved now.

2 Replies

  • v-eachen-msft's avatar
    v-eachen-msft
    Community Support

    Hi Anonymous ,

     

    I am running a regression model (linear model) and displaying a graph through Rvisuals. Everything works fine on my laptop and I receive the output in less than a minute (~40 seconds) in PowerBI R visuals.


     According to your situation, I don't think your R viusal exceeds the limit. You could check the version and type(32bit or 64 bit) of Power BI on your colleague's laptop or run it on a third laptop. If it doen't work,  you could create a support ticket to get support from Microsoft engineer. 

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thanks for your message, however its a problem with only 1 Laptop and so I advised the user to reinstall everything. He didn't reported it again so I assume its solved now.