locked
MOSS 12 Log File error RRS feed

  • Question

  • Hi, See this unexpected huge LOg files( 400,000kb)  in 12 folder , below pasting few comments

    w3wp.exe (0x16E0)                        0x1B34 CMS                            Publishing                     7fz3 Medium   Setting [Display] as the FormContext.FormMode for the current page 

    w3wp.exe (0x16E0)                        0x1B34 CMS                            Publishing                     7fz3 Medium   Setting [Display] as the FormContext.FormMode for the current page 

    w3wp.exe (0x16E0)                        0x1B34 CMS                            Publishing                     7fz3 Medium   Setting [Display] as the FormContext.FormMode for the current page 

    w3wp.exe (0x16E0)                        0x1B34 CMS                            Publishing                     7fz3 Medium   Setting [Display] as the FormContext.FormMode for the current page 

    w3wp.exe (0x16E0)                        0x1B34 CMS                            Publishing                     7fz3 Medium   Setting [Display] as the FormContext.FormMode for the current page 

    changed the event & trace logs to None & None in central Admin

    please advice what other setting changes I shoud do to reduce this Log files

    Friday, April 12, 2013 3:31 PM

All replies

  • Hi,

    in 12Hive ( c:program files\commonfiles\.......12 LOGS ) folder I see the log files are huge - over 400,000KB ..I changed Trace & Event Logs to None & None in CEntral Admin- Operations - Diagonistic Logging - but still find these Log file gettiing created

    Any other settings I need to do to reduce this LOG files .....showing none errors in Event Logs

    Friday, April 12, 2013 2:47 PM
  • LOGS will house the .log and .usage files both, which are controlled in two different locations in CA.

    Generally when I set up the logging, I create a seperate LOGS folder on a drive that is different from where the sharepoint binaries are stored, and in the LOGS dir have 2 folders, ULS and USAGE.

    Try setting up a similar configuration and see if the logs are still showing up in the 12 hive.  Occasionally I'll notice that the usage logs get locked by the timer service, and a quick restart of the sharepoint timer will usually resolve the issue.


    ieDaddy
    Blog: http://iedaddy.com
    Twit: @iedaddy

    Friday, April 12, 2013 4:07 PM
  •  How do I seperate LOG folders ? please advice on this

    Also which Timer job I should restart to resolve this issue ? please help

    Friday, April 12, 2013 5:37 PM
  • Under central admin -> monitoring

    - you'll see one link for configure diagnostic logging with a place to change the trace log path

    - another link for usage and health data collection with a log file location

    Make the appropriate changes there.

    on the machine, open services.msc and you'll see a sharepoint timer job, just restart it.


    ieDaddy
    Blog: http://iedaddy.com
    Twit: @iedaddy

    Friday, April 12, 2013 5:42 PM
  • Tried these options....restarted the time job, still generating HUGE files...

    any other suggestions ? am seeing in log file lots of general & publishing notofications..

    Have chnged both event & trace logs to none & none...still generating huge file...

    Friday, April 12, 2013 6:05 PM
  • ok, I think this may work with 2007, try using powershell to change the log levels

    Set-SPlogLevel - you can use this to change the levels

    Clear-SPLogLevel - will set all categories back to default.

    http://technet.microsoft.com/en-us/library/ee748656(v=office.14).aspx


    ieDaddy
    Blog: http://iedaddy.com
    Twit: @iedaddy

    Friday, April 12, 2013 6:08 PM
  • Some links on log configuration best practices  - http://www.sharepointboost.com/blog/how-to-configure-sharepoint-2010-logs/

    http://www.sharepointdiary.com/2012/12/diagnostic-logging-in-sharepoint-2010.html


    sharing is learning Whenever you see a reply and if you think is helpful, click "Vote As Helpful"! And whenever you see a reply being an answer to the question of the thread, click "Mark As Answer"

    Friday, April 12, 2013 6:21 PM
  • this issue is happening in our 2007 Prod server.

    The only work arround this time I did is check mark * do not collect error log reports....so atleast we can get rid of the disk space issue !

    if some unexected error happens on ths server or SP sites, I can always turn back the log file collection and see the logs..hope this is ok ??

    Friday, April 12, 2013 6:40 PM
  • I tried turning off * collection of logs ...but it is still showing & generating Logs with HUGE MB sizes....

    can anyone tell me where are these logs coming from...most of it says IIS workers process logs...

    Friday, April 12, 2013 7:00 PM
  • IIS logs are handled from the IIS interface or through command line/powershell:

    http://technet.microsoft.com/en-us/library/cc754631(v=ws.10).aspx

    appcmd set config /section:httpLogging /dontLog:True 

    http://urbanelementuk.blogspot.com/2009/05/iis7-change-site-logs-location-via.html



    ieDaddy
    Blog: http://iedaddy.com
    Twit: @iedaddy

    Friday, April 12, 2013 7:03 PM
  • HI,

    One of the first things the script I use to setup all of my SharePoint deployments does is to compress the contents of both the ULS logs Folder and the IIS Logs Folder. Secondly, you can reduce the length of time the logs are stored for...


    Ivan Sanders My LinkedIn , My Blog, @iasanders, BI in SP2013, SP2013 Content Packs.

    Saturday, April 13, 2013 2:35 PM
  • Hi,

    Is your issue resolved, please let us know so I can get this ticket off my plate...

     

    -Ivan


    Ivan Sanders My LinkedIn , My Blog, @iasanders, BI in SP2013, SP2013 Content Packs.

    Wednesday, April 17, 2013 3:42 AM
  • Its not resolved yet. we are monitoring the LOG files...these were IIS LOGS created due to some publishing feature, have done some changes on the web.config file...
    Wednesday, April 17, 2013 1:34 PM