Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S SharePoint.WarmUp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CodePlex
  • SharePoint.WarmUp
  • Issues
  • #11

Closed
Open
Created May 31, 2018 by Laurent Sittler@lsittler©Owner

Time service crashes, Event ID 8311, Event ID 1001, and large Central Admin Content DB

Hello,

I ran into an issue over the past couple of months with SharePoint WarmUp. It started when I noticed my Central Admin Content DB growing up to 50GB. When the WarmUp job runs every 15 minutes I receive the following error in my servers event viewer 5 times, one for each web application:

Event ID 8311

An operation failed because the following certificate has validation errors: Subject Name: The root of the certificate chain is not a trusted root authority.

That is then followed by Event ID 1001:

Problem signature:

P1: owstimer.exe

P2: 14.0.6123.5000

P3: 4fd15afa

P4: Microsoft.SharePointP5: 14.0.0.0

P6: 4fd15297P7: 13d

P8: 2e

P9: System.IO.DirectoryNotFound

nP10:

Attached files:

These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_owstimer.exe_75faa0b55ee7439b93a483edffdf550d2d03f7c_d69a7826

When the timer job runs it also causes my Timer Service to crash, so any other jobs running at that time also fail.

Has anyone else experienced this and do you have any suggestions for a fix?

Thank you,

B

Assignee
Assign to
Time tracking