Sunday, August 31, 2014

SharePoint 2010 Diagnostic and Usage Analysis Logs best practice

SharePoint 2010 has improved the way the ULS logs information and now these diagnostic logging data can be written to trace files, Windows Event Viewer and a new SharePoint reporting database (new in SharePoint 2010). Trace log files are created in a Log folder under the root folder where SharePoint has been installed by default; that is also called the 14 Hive.

SharePoint diagnostic logging is very important, and extremely helpful when we encounter problems with our SharePoint environment. However, diagnostic logging can be ineffective at times, and can even cause SharePoint performance to slow down if it’s not managed properly. The one thing you should ABSOLUTELY do is move the ULS logs off of the system drive. ULS is designed to stop logging if it percieves a disk space issue and moving the logs off of the system drive ensures that logging isn’t going to fill up the system drive, and that ULS logging isn’t going to contend with your page file for disk IO. Note that in order to change the location fo the log file, the path must exist on ALL SharePoint servers, and the folder’s permissions must be set to allow the SharePoint service to write to it.

There are two sets of logs you want to move in the SharePoint 2010 farm environment, the diagnostic logs and the usage logs.

Diagnostic logs: With Central Admin:

Central Admin > Monitoring > Configure Diagnostic Logging (/_admin/metrics.aspx). The setting is the “Trace Log” path at the bottom. It is recommended changing the Drive letter and leaving the rest of the path alone. It’ll make it easier for you to find things later on.

With PowerShell: You can also use PowerShell to change this. The cmdlet is Set-SPDiagnosticConfig and the parameter is –LogLocation.

Set-SPDiagnosticConfig -LogLocation “E:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS

Usage logs: With Central Admin:

Central Admin > Monitoring > Configure web analytics and health data collection (/_admin/LogUsage.aspx). The setting is the “Log file location” setting. Set it to the same path you did the Trace Log above.

With PowerShell:

The PowerShell cmdlet to alter this is Set-SPUsageService and the parameter is –UsageLogLocation. Set-SPUsageService -UsageLogLocation “E:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\”

ITIL for SharePoint: Defining SharePoint as a Service Using ITIL Service Strategy

Summary SharePoint, by its nature, is a technology--a bundled set of capabilities. It is up to SharePoint owners to determine how to define it and recast it as a service. SharePoint as a service is an approach that recasts SharePoint as a catalog of business-focused services. Treating SharePoint as a service is better (i.e., yields more value) and fundamentally different than simply providing a set of capabilities. This guidance presents an approach to treating SharePoint as an enterprise solution by applying a service management methodology (i.e., Information Technology Infrastructure Library [ITIL]).

What is msvcs.exe Information

This is an undesirable program. This file has been identified as a program that is undesirable to have running on your computer. This consists of programs that are misleading, harmful, or undesirable. If the description states that it is a piece of malware, you should immediately run an antivirus and antispyware program. If that does not help, feel free to ask for assistance on the forums. Name: MsvcService Filename: msvcs.exe Command: msvcs.exe Description: Added by the W32/Rbot-RK worm. This infection connects to an IRC server where it waits for remote commands. File Location: %System% Startup Type: This startup entry is started automatically from a Run, RunOnce, RunServices, or RunServicesOnce entry in the registry. HijackThis Category: O4 Entry Note: %System% is a variable that refers to the Windows System folder. By default this is C:\Windows\System for Windows 95/98/ME, C:\Winnt\System32 for Windows NT/2000, or C:\Windows\System32 for Windows XP/Vista/7. Removal Instructions: How to remove a Trojan, Virus, Worm, or other Malware

What is the OWSTimer.exe process.

Name: SharePoint Timer Service Filename: OWSTIMER.EXE Command: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\50\bin\OWSTIMER.EXE Description: The SharePoint Timer Service is a Window service that is installed with Windows SharePoint Services. This program is used to handled scheduled jobs related to Windows SharePoint. File Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\50\bin\OWSTIMER.EXE Startup Type: This startup entry is installed as a Windows service. Service Name: SPTimer Service Display Name: SharePoint Timer Service HijackThis Category: O23 Entry

Google+ Followers