Forum Discussion
Crashing PBI changing credentials
I have a large PBI with various data sources (SQL database, cubes, Sharepoints, etc). Sometimes my PBI is trying to load a recent change and it crashes OR crashes my computer requiring a hard restart. When this happens, more often than not when I get PBI up and running again it seems like it has either reset or a new version has been loaded. I identify this with the new to PBI screen asking for name and other contact details. When I enter this information and go to my Query Editor, each individual query seems to require an update of my credentials. Given the size this is quite time consuming. Any idea why this is happening and is there any way to avoid??
Thanks!
Hi Anonymous ,
The permission here means credentials,if you clear the permission,once you get the data,you need to re-enter the credential,but it can be helpful to clear those unused credentials ,which will take up a certain memory.
Following steps you can also try:
1,Check whether the version of desktop has been updated to the latest one.
2.Run the desktop and see the process in task manager, if it's very high,it may be the issue.
3.Clear the cache in your desktop :
Best Regards,
Kelly
3 Replies
- v-kelly-msft
Community Support
Hi Anonymous ,
Try the following steps to do troubleshooting:
1.Have you updated desktop to the latest version?
2.Will it happen if you only load a single data source such as SQL?
3.Try to clear your historical data source as below:
Best Regards,
Kelly- AnonymousNot applicable
v-kelly-msftWhat happens when I clear permissions? Does it reset permissions so I need to reset them or is it similar to clearing cache/cookies?
- v-kelly-msft
Community Support
Hi Anonymous ,
The permission here means credentials,if you clear the permission,once you get the data,you need to re-enter the credential,but it can be helpful to clear those unused credentials ,which will take up a certain memory.
Following steps you can also try:
1,Check whether the version of desktop has been updated to the latest one.
2.Run the desktop and see the process in task manager, if it's very high,it may be the issue.
3.Clear the cache in your desktop :
Best Regards,
Kelly