Provide a way to view ULS Logs on SharePoint Online
Currently there is no way to see the logs for your Tenant in SharePoint online. So it gets very hard to debug when all you see is "An unexpected error occurred".
This category has been deprecated. Please go to https://sharepoint.uservoice.com/ to submit any feature requests related to SharePoint.
Sri Sunkavalli commented
SharePoint online is so buggy. MSFT should do a better job to log errors and display to users and admins. There should be an easy way to troubleshoot quickly instead of approaching MSFT with tickets. Looking for this feature soon in the portal.
Michael LaPointe commented
For my company SharePoint online is unusable without access to the logs or some way to show the stack dump to know what is wrong. There's way too much that's buggy with SharePoint online to not have this. I was trying to do something simple like activate publishing features and it just throws the dummy response with the useless correlation ID. We figured out how to get that working finally but it took way too much trial and error to figure out what was blocking it. Now we are stuck with some error in a custom masterpage. It works fine if you go to the page directly but because the links run through start.aspx it dies on that page with the dummy error response.
Wouter Spelt commented
Hi, please provide a way to view ULS logs on SP Online.
This would be very helpfull in case of an internal server error in SP online.
this really needs sorting out salesforce offers this functionality why not sharepoint online?
Craig Giordano commented
I get so frustrated when there is nothing I can do, or even tell the user. I end up looking like a dummy. You call for support and you get is "I understand your concern blah blah blah. Please leave feedback on the web site". You end getting a little bit of insincere, moral support, but no technical support.
I'm just going to tell my users "you can't create an event in your calendar, or add an item to your list, because Microsoft sucks".
Pierre-Alain SCHNEE commented
We shoud be able at least to see the error message belonging to a correlation id.
This is clearly one of the most important feature for any administrator or developer.
How to troubleshoot issues with only a correlation id ? What do we say to the user ?
I need to have access to ULS logs as a developer unless how we can debug codes there.
Paul Matthews commented
Really need this feature. Trying to debug OOTB workflow which are falling over, need an internal error message, not "Error Occurred"
I need this feature as a developer.
Hello? anyone listening here? This is number two on the top voted items. How is this not in the current sprint?
Massimo Prota commented
Some scenarios where accessing ULS log is required
Working with Web Parts:
- When importing a malformed or invalid XML definition. The real details can only be seen in ULS.
- When editing XSL of a CQWP: if there's an error SP just displays the latest good version known. Real details of an error can only be seen in ULS
Working with No Code Sandbox Solutions:
- See full error details when something with feature (de)activation goes wrong
Working with (SPD) Workflows:
- Troubleshoot SharePoint Designer workflows
Martijn Eikelenboom commented
A use case: Provisioning sites through code sometime gives an error when loading a site for the first couple of times. After that it seems to go away. I would really like to know what's going on. A log report would probably help.
Stefan Bauer commented
Developer Dash Board would be more useful to see what happens under the hood. It also provide more detailed information. Form my point of view.
Robert Seso commented
At least the parts of the ULS logs for the exceptions that happen during CSOM/REST calls should be exposed in some way.
Matt Williams commented
This is a must to be able support O365 correctly in an organisation
Please have this feature available please. This is a productivity concern in our organization. If we are to get ULS log from support every now and then, our development/operational activities will be affected.
I tried both solutions provided in below links. But, couldn't get ULS logs data at all.
Sometimes I badly need it as a Developers
Oleg Snurnikov commented
Yes, please do that!