none
OWSTIMER.EXE stürzt um 06:11:14 jeden Tag (SharePoint 2010) ab RRS feed

 > 

  • Frage

  • Question
    Anmelden
    0
    Anmelden

    Hi,

    in allen einen  SharePoint 2010 Farmen nekomme ich fast jeden Tag ein MS Event ID 1000

     <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Application Error" />
      <EventID Qualifiers="0">1000</EventID>
      <Level>2</Level>
      <Task>100</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2012-03-02T05:11:16.000000000Z" />
      <EventRecordID>35145</EventRecordID>
      <Channel>Application</Channel>
      <Computer>"Server XXX"</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>OWSTIMER.EXE</Data>
      <Data>14.0.6108.5000</Data>
      <Data>4e274365</Data>
      <Data>KERNELBASE.dll</Data>
      <Data>6.1.7601.17651</Data>
      <Data>4e21213c</Data>
      <Data>ebf00baa</Data>
      <Data>000000000000cacd</Data>
      <Data>4360</Data>
      <Data>01ccf769ba3cdae9</Data>
      <Data>C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\OWSTIMER.EXE</Data>
      <Data>C:\Windows\system32\KERNELBASE.dll</Data>
      <Data>231db431-6426-11e1-963d-68b599c9f89c</Data>
      </EventData>
      </Event>


    ULSLOG ( OWSTIMER.EXE (0x4360) 0x3D48  ....  repead many Times between 03.02.2012 06:11:14.49 and 03.02.2012 06:11:14.62.)

    03.02.2012 06:11:14.49 OWSTIMER.EXE (0x4360) 0x3D48 SharePoint Foundation Timer 2mz9 Medium Pausing timer job. JobId: 2ec7f355-ddae-45e5-8e7a-66a3bc9a22ba, TargetInstanceId 92386fc6-281d-49fc-af15-a175e29b1c85
    03.02.2012 06:11:14.49 OWSTIMER.EXE (0x4360) 0x3D48 SharePoint Foundation Timer 2mz9 Medium Pausing timer job. JobId: 18e1e92d-a619-4054-b1c2-c56ed1539c9c, TargetInstanceId e6ba8245-66a3-49fb-ac8d-9e535d864ba4
    03.02.2012 06:11:14.49 OWSTIMER.EXE (0x4360) 0x3D48 SharePoint Foundation Timer 2mz9 Medium Pausing timer job. JobId: 52b1be22-5d0d-422f-ace7-2f9e71e2be3c, TargetInstanceId 92386fc6-281d-49fc-af15-a175e29b1c85
    03.02.2012 06:11:14.49 OWSTIMER.EXE (0x4360) 0x3D48 SharePoint Foundation Database tzku Verbose ConnectionString: 'Data Source=A-FARM-SPFARMP2-0002;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15
    03.02.2012 06:11:14.62 OWSTIMER.EXE (0x4360) 0x3D48 SharePoint Foundation Database tzku Verbose ConnectionString: 'Data Source=A-FARM-SPFARMP2-0002;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15
    03.02.2012 06:11:14.62 OWSTIMER.EXE (0x4360) 0x3D48 SharePoint Foundation Database tzku Verbose ConnectionString: 'Data Source=A-FARM-SPFARMP2-0002;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15
    03.02.2012 06:11:14.62 OWSTIMER.EXE (0x4360) 0x3D48 SharePoint Foundation Database tzku Verbose ConnectionString: 'Data Source=A-FARM-SPFARMP2-0002;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15
    03.02.2012 06:11:14.63 OWSTIMER.EXE (0x4360) 0x3D48 SharePoint Foundation Timer 8gs7 Medium The timer service is stopping
    03.02.2012 06:11:14.85 OWSTIMER.EXE (0x3048) 0x4B3C SharePoint Foundation Unified Logging Service b8fx High ULS Init Completed (OWSTIMER.EXE, onetnative.dll)
    03.02.2012 06:11:14.85 OWSTIMER.EXE (0x3048) 0x4B3C SharePoint Foundation General 0000 Medium Microsoft SharePoint Foundation log file
    03.02.2012 06:11:14.86 OWSTIMER.EXE (0x3048) 0x4B3C SharePoint Foundation Timer 8gs6 Medium The timer service is starting
    03.02.2012 06:11:14.88 OWSTIMER.EXE (0x3048) 0x39D0 SharePoint Foundation SQM 8zj1 Verbose SQM: Datapoint id 56 marked as Bits OR datapoint.

    hat jemand eine Idee?
     

    Freitag, 2. März 2012 08:19
    |

Antworten

  • Question
    Anmelden
    1
    Anmelden

    Hi Florian,

    anscheinend passiert was beim normalem Service Recycle. Es gibt einen Timer Job der den OWSTIMER Dienst jede Nacht durchstartet. Der Job heißt Timer Service Recycle. Ich konnte leider nicht mehr als das rausfinden, allerdings sehe ich den Fehler als unkritisch wenn der OWSTIMER Dienst doch normal startet.

    http://technet.microsoft.com/en-us/library/cc678870.aspx#DefaultJobs

    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 9fw9 Medium Attempting to recycle the timer service process. 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6uaj Verbose A channel was registered for the admin operation. 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6uak Verbose A remoting client was registered for the admin operation. 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6ual Verbose A message sink was created for the admin operation. 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Database tzku Verbose ConnectionString: 'Data Source=A-FARM-SPFARMP2-0002;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job job-timer-recycle). Execution Time=630014.888362242 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring nass Verbose ____Execution Time=630014.888362242 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring nass Verbose ____SPRequest Objects=0 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring nass Verbose ____SQL Query Count=2 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring nass Verbose ____Service Calls=0 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Usage Infrastructure d0hz Verbose Starting write trace for type Microsoft.SharePoint.Administration.SPTimerJobUsageEntry with correlationID 41e99ca8-f5ee-4a75-b5e3-b6df8b1ab763 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Usage Infrastructure d0i0 Verbose Successful wrote trace for type Microsoft.SharePoint.Administration.SPTimerJobUsageEntry with correlationID 41e99ca8-f5ee-4a75-b5e3-b6df8b1ab763 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Logging Correlation Data 77a3 Verbose Ending correlation. Transfer to 37d87615-4ecd-4f90-9400-1131f1deedad 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 8e46 Verbose End invoke timer job Timer Service Recycle, id {1B6CE8C4-F842-4F03-B021-29AA05B130E4}, DB n/a 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6gfa Verbose Entered VtimerStore::HrGetISPNativeConfigurationProvider 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6gfd Verbose Exiting VtimerStore::HrGetISPNativeConfigurationProvider 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Database tzku Verbose ConnectionString: 'Data Source=A-FARM-SPFARMP2-0002;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Logging Correlation Data 77a3 Verbose Ending correlation. 37d87615-4ecd-4f90-9400-1131f1deedad

    [...]

    03/04/2012 06:11:15.28 OWSTIMER.EXE (0x466C) 0x31F0 SharePoint Foundation Timer 8gs7 Medium The timer service is stopping 

    [...]

    03/04/2012 06:11:15.58 OWSTIMER.EXE (0x3C90) 0x2090 SharePoint Foundation Timer 8gs6 Medium The timer service is starting 

    Gruß,
    Andrei

    • Als Antwort vorgeschlagen Alex Pitulice Dienstag, 13. März 2012 12:06
    • Als Antwort markiert Florian Warncke Dienstag, 13. März 2012 13:24
    Sonntag, 11. März 2012 10:16
    |

Alle Antworten

  • Question
    Anmelden
    0
    Anmelden

    Hi Florian,

    könntest du das ganze Log hochladen und hier verlinken? In diesem Abschnitt steht leider nicht viel..

    Gruß,
    Andrei

    Montag, 5. März 2012 18:58
    |
  • Question
    Anmelden
    0
    Anmelden

    Hallo Andrei,

    die Logs liegen im Skydrive

    Dienstag, 6. März 2012 11:57
    |
  • Question
    Anmelden
    1
    Anmelden

    Hi Florian,

    anscheinend passiert was beim normalem Service Recycle. Es gibt einen Timer Job der den OWSTIMER Dienst jede Nacht durchstartet. Der Job heißt Timer Service Recycle. Ich konnte leider nicht mehr als das rausfinden, allerdings sehe ich den Fehler als unkritisch wenn der OWSTIMER Dienst doch normal startet.

    http://technet.microsoft.com/en-us/library/cc678870.aspx#DefaultJobs

    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 9fw9 Medium Attempting to recycle the timer service process. 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6uaj Verbose A channel was registered for the admin operation. 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6uak Verbose A remoting client was registered for the admin operation. 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6ual Verbose A message sink was created for the admin operation. 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Database tzku Verbose ConnectionString: 'Data Source=A-FARM-SPFARMP2-0002;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job job-timer-recycle). Execution Time=630014.888362242 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring nass Verbose ____Execution Time=630014.888362242 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring nass Verbose ____SPRequest Objects=0 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring nass Verbose ____SQL Query Count=2 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Monitoring nass Verbose ____Service Calls=0 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Usage Infrastructure d0hz Verbose Starting write trace for type Microsoft.SharePoint.Administration.SPTimerJobUsageEntry with correlationID 41e99ca8-f5ee-4a75-b5e3-b6df8b1ab763 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Usage Infrastructure d0i0 Verbose Successful wrote trace for type Microsoft.SharePoint.Administration.SPTimerJobUsageEntry with correlationID 41e99ca8-f5ee-4a75-b5e3-b6df8b1ab763 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Logging Correlation Data 77a3 Verbose Ending correlation. Transfer to 37d87615-4ecd-4f90-9400-1131f1deedad 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 8e46 Verbose End invoke timer job Timer Service Recycle, id {1B6CE8C4-F842-4F03-B021-29AA05B130E4}, DB n/a 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6gfa Verbose Entered VtimerStore::HrGetISPNativeConfigurationProvider 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Timer 6gfd Verbose Exiting VtimerStore::HrGetISPNativeConfigurationProvider 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Database tzku Verbose ConnectionString: 'Data Source=A-FARM-SPFARMP2-0002;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Asynchronous Processing=False;Connect Timeout=15'    ConnectionState: Closed ConnectionTimeout: 15 37d87615-4ecd-4f90-9400-1131f1deedad
    03/04/2012 06:10:31.01 OWSTIMER.EXE (0x466C) 0x3D7C SharePoint Foundation Logging Correlation Data 77a3 Verbose Ending correlation. 37d87615-4ecd-4f90-9400-1131f1deedad

    [...]

    03/04/2012 06:11:15.28 OWSTIMER.EXE (0x466C) 0x31F0 SharePoint Foundation Timer 8gs7 Medium The timer service is stopping 

    [...]

    03/04/2012 06:11:15.58 OWSTIMER.EXE (0x3C90) 0x2090 SharePoint Foundation Timer 8gs6 Medium The timer service is starting 

    Gruß,
    Andrei

    • Als Antwort vorgeschlagen Alex Pitulice Dienstag, 13. März 2012 12:06
    • Als Antwort markiert Florian Warncke Dienstag, 13. März 2012 13:24
    Sonntag, 11. März 2012 10:16
    |
  • Question
    Anmelden
    0
    Anmelden

    HI Andrei,

    ich danke dir für deine Aussage da bisher auch meine Farmen davon nicht in mitleidenschaft gezogen wurden brauchte ich auch eine zweite Meinung

    Dienstag, 13. März 2012 13:25
    |