Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

SQL Server 2008 R2 Currently the log folder is taking upto 109GB's of space!

It keeps repeating the following error:

“An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 11.Could not obtain information about Windows NT group/user 'DOMAIN_NAME\sharepoint.admin', error code 0x6fd”

I have deleted the old logs, the new log file has reached 2.92Gb and is growing by the second.

How do I find out which DB is showing this error and how do I stop this error from occurring? Thanks!

UPDATE The log is growing around 7000 records per minute. Tried to check the server permissions given to DOMAIN_NAME\sharepoint.admin under "Effective" tab I am seeing the same error:

"Could not obtain information about Windows NT group/user 'DOMAIN_NAME\sharepoint.admin', error code 0x6e"

share|improve this question
add comment

1 Answer 1

up vote 1 down vote accepted

It looks like you have an access denied issue. Either your disconnected from the network or AD DS, or the account your using has expired credentials. Try to find the failing job in job history, and change that account to sa account. Then switch back to your service account - and see if you have the correct credentials. If not - look at the AD DS and make sure your credentils are valid.

Ref: Replication Jobs fail with error code 0x6fd

share|improve this answer
    
That's the thing. I have only ONE job at the moment and it is running without errors. I am having trouble finding the source of this error. –  Sameen Ali Apr 9 '13 at 11:07
    
The credentials for the account are current, the account is not locked and the credentials are picked properly at windows level in "users and groups" (local admin group) –  Sameen Ali Apr 9 '13 at 11:14
    
The jobs running on the server were not an issue. I changed the owner of the various DB schema's used by Sharepoint from 'DOMAIN_NAME\sharepoint.admin' to 'sa' and the logs growth seems to have stopped. –  Sameen Ali May 22 '13 at 4:41
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.