none
OWSTimer.exe Authentication Failures RRS feed

  • Question

  • My domain controller receives over 1200 failed authentication attempts (event 4776 in the Security logs) each day from our Project Server referring to our project server service account.  The OWSTimer.exe application attempts to authenticate using only the first letter of the account (i.e. 's' instead of the full svcprojectserver account name). The domain controller then rejects the authentication attempt with a 0xC0000064 code saying the user isn't found. See below.

    Looking on the project server, I see a 4648 event in the Security logs with the correct 'Subject' credentials AND the failed credentials. See below.

    The confusing part is that the OWSTimer.exe service is running correctly. Our DC's Security logs are filling up though...

    What would you advise?

    Thanks

    Wednesday, September 27, 2017 9:52 PM

Answers

  • Verify that the service account password is correct and account is not locked out.

    This is done in SharePoint Central.   Also, double check that IIS pools have the correct service accounts working properly and service accounts are setup with right passwords as well.


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    • Marked as answer by 10890lrl Monday, December 11, 2017 2:21 PM
    Thursday, October 5, 2017 3:10 AM
    Moderator

All replies

  • Verify that the service account password is correct and account is not locked out.

    This is done in SharePoint Central.   Also, double check that IIS pools have the correct service accounts working properly and service accounts are setup with right passwords as well.


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    • Marked as answer by 10890lrl Monday, December 11, 2017 2:21 PM
    Thursday, October 5, 2017 3:10 AM
    Moderator
  • Hi all

    After working with Microsoft, we re-provisioned the timer service and restarted the servers.

    That seemed to correct the problems

    Thanks

    Monday, December 11, 2017 2:21 PM