New answers tagged

2

Have a look at the following MSDN article: https://blogs.msdn.microsoft.com/manhar/2012/04/17/how-to-reduce-the-size-of-logging-database-or-how-to-purge-the-old-data-from-logging-database/ it will answer your question. The title says how to decrease the size of the logging database, but the article describes how to change the retention periods. An example ...


0

ULS - Unified Logging Service. SharePoint, it's services, and if implemented 3rd party application can use the ULS to write to the SharePoint trace log files. Each server keeps a copy of it's own logs. In Central Admin under Monitoring you can configure the diagnostic information that is collecter, or use the Set-SPDiagnosticConfig cmdlet. The WSS ...


1

Another Options, this only works, If you have the Windows server backup then you restore the files from the backup. We have SharePoint Server backup, which will backup all the drives.


1

You could look into the WSS_Logging database, depending on how the logs were deleted, especially if you have SQL backups of WSS_Logging. Check out this link to read how to query it: https://technet.microsoft.com/en-us/library/hh769360(v=office.14).aspx


1

Once those files are deleted, they're gone. If you've set up the Usage Database, there may be additional information in the View dbo.ULSTraceLog which you can query directly via SQL Server Management Studio. It also depends on the number of days you've trimmed there.


0

If its your custom timer job & if you are using the on-premises version of SharePoint 2013 than please debug the code first as this can be an error of the code. You can debug the timer job by attaching the same OWSTIMER.Exe from the visual studio.



Top 50 recent answers are included