SharePoint 2010 - Change Diagnostic Log Storage Location

AID: 6309
  • Status: Published

1760 points

  • Bychapmanjw
  • TypeTutorial
  • Posted on2011-06-19 at 12:49:36
Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 do not offer the option to configure the location of the SharePoint diagnostic trace log files during installation.  This can, however, be configured through Central Administration or through a simple PowerShell command after installation.  

With the default SharePoint configuration, the SharePoint diagnostic trace logs are stored in the 14 HIVE on the local hard drive of each SharePoint server in a SharePoint farm (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).  If you are not going to store the diagnostic trace log files on a different drive, it is recommended to leave the default location.  However, you may wish to store them on a different local hard drive for storage space or other considerations.  

When deciding where to place the SharePoint diagnostic trace log files, it is important to remember that they must be stored on a local hard drive.  SharePoint does not support storing the diagnostic trace log files on network storage.  Also note that the specified directory location must exist in the same place on all SharePoint servers in the farm.

To configure the SharePoint diagnostic trace log location through Central Administration:

1
Open Central Administration for the SharePoint farm you wish to change the storage location for


2
In Central Administration, browse to Monitoring and then to Configure Diagnostic Logging under Reporting


3
Specify the Path to the storage location under Trace Log


4
Select OK



To configure the SharePoint diagnostic trace log location through PowerShell:

1
Open the SharePoint 2010 Management Shell (PowerShell) on one of the servers in the SharePoint farm


2
Enter the following PowerShell command specifying the log location:

Set-SPDiagnosticConfig –LogLocation PATH_TO_LOG_LOCATION
                                    
1:

Select allOpen in new window


For example:

Set-SPDiagnosticConfig –LogLocation D:\SharePointLogs
                                    
1:

Select allOpen in new window



Either method produces the same result and is only required to be once per SharePoint farm, regardless of how many SharePoint servers are in the farm.  You do, however, need to ensure the configured location exists on each server in the SharePoint farm.  After configuring using either method, the change will be reflected immediately.
Asked On
2011-06-19 at 12:49:36ID6309
Tags

sharepoint

,

sharepoint 2010

,

logs

,

powershell

Topic

MS SharePoint

Views
1175

Comments

Expert Comment

by: nsitsupport on 2012-02-12 at 15:48:02ID: 42826

Hi,

I found you can change the INDEX LOCATION during installation.
SP-INDEX-LOCATION.png
  • 82 KB
  • SharePoint Index File Location During Install
SharePoint Index File Location During Install


However, the DIAGNOSTIC LOGGING.....I haven't found. This seem to be done after only.

Regards

Ian

    Add your Comment

    Please Sign up or Log in to comment on this article.

    Join Experts Exchange Today

    Gain Access to all our Tech Resources

    Get personalized answers

    Ask unlimited questions

    Access Proven Solutions

    Search 3.2 million solutions

    Read In-Depth How-To Guides

    1000+ articles, demos, & tips

    Watch Step by Step Tutorials

    Learn direct from top tech pros

    And Much More!

    Your complete tech resource

    See Plans and Pricing

    30-day free trial. Register in 60 seconds.

    Loading Advertisement...

    Top MS SharePoint Experts

    1. ACH1LLES

      358,298

      Wizard

      0 points yesterday

      Profile
      Rank: Genius
    2. JamieMcAllister

      189,161

      Guru

      0 points yesterday

      Profile
      Rank: Sage
    3. teylyn

      170,328

      Guru

      900 points yesterday

      Profile
      Rank: Genius
    4. ivan_vagunin

      156,400

      Guru

      0 points yesterday

      Profile
      Rank: Sage
    5. QPR

      123,685

      Master

      2,000 points yesterday

      Profile
      Rank: Genius
    6. Tehzar

      100,639

      Master

      0 points yesterday

      Profile
      Rank: Guru
    7. svetaye

      75,681

      Master

      0 points yesterday

      Profile
      Rank: Guru
    8. tedbilly

      71,150

      Master

      0 points yesterday

      Profile
      Rank: Genius
    9. quihong

      52,832

      Master

      0 points yesterday

      Profile
      Rank: Sage
    10. dp_expert

      49,160

      0 points yesterday

      Profile
      Rank: Wizard
    11. colly92002

      41,560

      0 points yesterday

      Profile
      Rank: Master
    12. clayfox

      39,400

      0 points yesterday

      Profile
      Rank: Genius
    13. milindsaraswala

      36,835

      0 points yesterday

      Profile
    14. RainerJ

      31,840

      1,000 points yesterday

      Profile
      Rank: Master
    15. abhitrig

      31,218

      0 points yesterday

      Profile
      Rank: Wizard
    16. dhawalseth

      30,268

      0 points yesterday

      Profile
    17. ImaCircularSaw

      29,438

      0 points yesterday

      Profile
      Rank: Guru
    18. martusha

      25,478

      0 points yesterday

      Profile
    19. zephyr_hex

      21,624

      0 points yesterday

      Profile
      Rank: Genius
    20. FastFngrz

      21,414

      0 points yesterday

      Profile
      Rank: Guru
    21. livanescu

      20,100

      0 points yesterday

      Profile
    22. danshady

      18,870

      0 points yesterday

      Profile
    23. CloudedTurtle

      18,050

      0 points yesterday

      Profile
      Rank: Master
    24. jessc7

      17,102

      0 points yesterday

      Profile
      Rank: Sage
    25. JoeKlimis

      16,318

      0 points yesterday

      Profile
      Rank: Master

    Hall Of Fame