The error listed in the title is repeatedly showing up in the ULS logs, with four different GUIDs. After failing to find any database with a matching guid via get-spdatabase, it was noticed that the guids listed are actually the guids for the servers in the farm:

get-spserver | select address, id

The above command returns the GUIDs being reported in the log.

More details from the log: the name indicates that perhaps this has to do with a feature activation, as the name column has: "timer job job-app-install-queue", and "timer job job-async-feature-activation2"

Any suggestions on what is causing this or how to track this down further?

1 Answer 1


This is an error you can ignore, likely a bug. It appears to impact any job that uses the SPWorkItemJobDefinition class.

  • Thanks Trevor!!
    – Mike2500
    Commented Nov 27, 2019 at 23:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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