- Ensure you're checking the correct logging location.
- Navigate to Central Admin >>> Monitoring >>> Configure Diagnostic Logging
- Check the Path value. You can copy the value and paste it into your Windows Explorer address bar for quick access to the logging location.
- Open the Service console from the server where the logs aren't being written.
- Scroll down and check that the "SharePoint Tracing Service" is running.
- If the service is running, you may want to restart it for good measure.
- Most likely it's NOT running though. If it's not, start the service.
- If the service does not use Local System for the account, but instead uses a domain account, it's likely that the password might have changed recently. Obtain the new password and reset the credentials for the service and then restart the service.
- Navigate to Central Admin >>> Monitoring >>> Configure Diagnostic Logging
- Check the Path value. Change it to a folder that does exist.
- Click OK.
- Navigate back to the "Configure Diagnostic Logging" page.
- Change the Path value back to %CommonProgramFiles%\Microsoft Shared\Web Server Extensions\15\LOGS\ and click OK.
Later
C
No comments:
Post a Comment
Comments are moderated only for the purpose of keeping pesky spammers at bay.