Hi folks,
I’m going nuts over this.
On SharePoint 2013, I have several deployments where I have missing corrolation ids in the ULS logs. When I hit an error, sometimes the id cannot be found.
I have checked the following:
- I do not have an extra-space at the end of the corrolation id when I copy / paste.
- I have set Event Level and Trace Level to Verbose for all the categories for diagnostic purposes.
- I have used UlsViewer and Notepad++ to search the ULS logs.
Is there someting I am missing?
Hi Yves,
thank you for your answer. I am trying that today.
Hi Frédéric,
I encountered the same problem. Â I received a correlation ID but couldn’t find it in the ULS logs. Â You’ll have to give the SharePoint system accounts permission to write to the ULS logs.
I added the various SharePoint system accounts to the Builtin/Performance Log Users Group in the Active Directory and then restarted the server. Â Then I performed the same action to receive an error and the correlation ID could be found in the ULS logs.
I hope this helps.
Regards,
Yves
Hi Vlad,
thanks for your reply. I only have one server since it’s a dev machine. The ULS log is actually working. But not everything seems to be logged.
Two things:
1. I read somewhere that the domain accounts used by SharePoint must be in the “Performance Log Users” to be able to write to the ULS. Do you know if it’s true?
2. The “SharePoint Tracing Service” uses the “Local Service” account. Some people seem to use domain accounts for this service. Which one is better?
Thanks for you help!
Fred
Hey Fred,
Did you check that your servers are actually doing new logs? Sometimes the ULS logging bugs and no new logs are being made. Â
Also, if you got more than 1 SharePoint Server in your Farm, you might want to use Merge-SPLog to get your log errors.Â
Merge-SPLogFile -Path ".\error.log" -Correlation "5ca5269c-8de5-4091-3f1b-f179af4d5121"Â
