Sharepoint 2010 Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint 2010       RSS Feeds

SP 2010 zero length log files

  Asked By: Jason    Date: Apr 22    Category: Sharepoint 2010    Views: 2029

My logs are empty. I know its a permission/writes issue but can't get
to the bottom of it. The problem seems to have cropped up after
switching application pools and services from using the default
installed accounts over to one I've created to service application
pools and services. Having made the switch by "registering" the
account in SP Central Admin and then using the Credential Management
to select the service and assign the account.

Even so, after configuring everything to use an account other than the
installed default, I am now left with log files that get created and
left empty and a warning message that remains about using a built in
account for the SPTraceV4 service.

My log directory has the following accounts and permissions:
Creator Owner - Special (inherited)
System - Full (inherited)
Local Service - Read & Write (assigned) Special (inherited)
WSS_Admin_WPG - Modify and below (inherited)
WSS_Restricted_WPG_V4 - Read & Write (assigned) Special (inherited)
WSS_WPG - Read & Write (assigned) Special (inherited)
spservice account - Modify and below (assigned)
Administrators - Full (inherited)
Users - Read Exec, List folder, Read (inherited)
TrustedInstaller - List folder & Special (inherited)

The three WSS groups contain the following memberships:
Admin - spfarmaccount
Restricted - spfarmaccount
WPG - spfarmaccount, spserviceaccount, spmysitesappaccount

Where did I go wrong?



2 Answers Found

Answer #1    Answered By: Bhavini Chinwalla     Answered On: Jan 07

I'd try running "psconfig.exe -cmd secureresources" first. That will reset
permissions on required objects.

You might also check to see if wsstracing.exe is running in task mgr.

Answer #2    Answered By: Kavita Thanki     Answered On: Jan 07

I was finally able to resolve it by running a powershell
script that changed the account SPTraceV4 was running under. Once that
script finished the logging started. I'll keep your idea handy as this
has happened to me before.

Didn't find what you were looking for? Find more on SP 2010 zero length log files Or get search suggestion and latest updates.