locked
OWSTIMER issues RRS feed

  • Question

  • Hello.

    We need your help because we are having issues with OWSTIMER on our SharePoint server.   FYI, the task manager shows that OWSTIMER process  runs under account “softadm”.
    Here are the logs we get on our server:

    Every Hour (code : 6398)

    The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID 20487113-310f-4a1f-b4be-2198f6f0c439) threw an exception. More information is included below.

    An update conflict has occurred, and you must re-try this action. The object SPSearchDataAccessServiceInstance Parent=SPServer Name=CODSHAREPOINT is being updated by STATCAN\softadm, in the OWSTIMER process, on machine CODSHAREPOINT.  View the tracing log for more information about the conflict.”

     When we reboot the server (6641)

    The SSP Timer Job Distribution List Import Job was not run.
    Reason: Logon failure: unknown user name or bad password

    Technical Support Details:

    System.ComponentModel.Win32Exception: Logon failure: unknown user name or bad password
       at Microsoft.Office.Server.Utilities.WindowsSecurity.GetUserTokenFromCredentials(String userDomainName, String password, LogonType logonType)
       at Microsoft.Office.Server.Utilities.WindowsSecurity.GetUserTokenFromCredentials(String userDomainName, String password)
       at Microsoft.Office.Server.Administration.JobHandler.Execute(Object state, Boolean timedOut)

    ---

    Things were running fine until we had to repair the database server.  Here is what was done:

    The OS was reinstalled.  
    All disks were reformatted.
    All SharePoint accounts were added to the admin group for the OS.
    The database software was reinstalled.
    The databases including the master database were restored from backups.
    Databases and accounts were identical to the way they were prior to replacing the disks.

    Any other software or configuration changes installed by SharePoint if any would have been lost.
    There is no login error reported by the Database Server.
    ---

    Our system architect, who normally performs maintenance on the SharePoint server, is gone until May 20
    th.  We know that he has tried to reset the password as it is  suggested in another post, using instructions found on http://blogs.msdn.com/joelo/archive/2006/08/22/712945.aspx.

    Has the error something to do with the database server update ?  Can you give us some hints on how to correct the problem ?
    Thanks for any help that you can provide us.

    Friday, May 8, 2009 2:39 PM

All replies

  • i think the issue is related to the search related. did you try stop and restart search.
    also check the sql server logs for that.
    thanks

    patel
    Friday, July 10, 2009 3:39 AM
  • I encountered this issue in one of my clients' servers, they changed the MOSS 2007 service account, so I did the below & got the issue resolved

    1- Go to Central Administration>Shares Services  Administration, then ensure that all SSP's there have the new user name & password right; If you are not sure about the password, re-enter it there better

    2- Run the below 2 scripts:

            A-updatefarmcredentials

               stsadm -o updatefarmcredentials -identitytype configurableid -userlogin Domain\SPServiceAccount -password Password

            B- updatepassword

                stsadm -o updateaccountpassword -userlogin Domain\SPServiceAccount -password Password

     

    3- Go to Administrative Tools>Services, retype user name & password in the below 3 services LogOn Tab window

            A- Windows SharePoint Services Administration

            B-  Windows SharePoint Services Search

            C- Windows SharePoint Services Timer

            D- Windows SharePoint Services Tracing

    4- Go to Shared Services Administration>Select the default SSP then go to Personalization Services Permissions, Click Add Users/ Groups and add your SSP process account with Manage User Profiles permissions.

     

    This actually solved my issue; try it & let us know If it didn't work for you

     

    Thanks,

    I. ElShafie


    I. Elshafie
    Monday, January 24, 2011 8:32 AM