Forum Discussion
Odata: unable to create platform context.
Sometimes (randomly as far as i know) the scheduled refresh for the dataset which uses https://XXXX.sharepoint.com/sites/EPM/_api/projectdata fails with the following error:
OData: Request failed: The remote server returned an error: (500) Internal Server Error. (Unable to create platform context. Please ensure that you have Log On Permissions on the server).
If I manually refresh I don't get the error but i don't know why the scheduled refresh is having issues. This is problematic because after 4 failed refreshes the scheduled refresh will stop refreshing. I looked online but can't really find any similar issues.
Any help would be greatly appreciated!
3 Replies
Hi Anonymous,
Based on my research, the above error could occur when SharePoint lists have calculated fields. Do you get any errors when removing calculated columns from SharePoint list?
There is a similar thread for your reference.
http://community.powerbi.com/t5/Integrations-with-Files-and/DataSource-Error-connecting-to-SharePoin...Regards,
Daniel He
Hi,
thanks for your quick reply. I'm not getting any inital errors while connecting. Data set loads fine for about 2 weeks now (refreshes 3 times a day). So my guess is that it shouldn't have anything to do with the calculated columns, otherwise it would have given me the error consistently. The problem with troubleshooting this issue is that i can't seem to replicate the behaviour when it fails. Because that data needs to be up to date very consistently i wanted to understand what is triggering this failure. I think the topic you linked should consistently give an error and not from time to time or did i read it wrong?
I know this is a very old thread, but there are very few threads on this topic and I just found another cause.
I mistakenly called the odata query on the root sharepoint site:
https://XXXX.sharepoint.com/_api/projectdata/Projects
rather than the pwa site following
https://XXXX.sharepoint.com/sites/pwa/_api/projectdata/Projects
The error message was 100% correct, it was a simple typo on my part, but took a while to work it out. Hope this helps someone else.
