There was an internal error invoking the timer job…

Actually, there were a lot of them, each looking roughly like this:

Event Type:    Error
Event Source:    Windows SharePoint Services 3
Event Category:    Timer
Event ID:    6772
Date:        6/10/2011
Time:        2:30:01 PM
User:        N/A
Computer:    GFTB-QA-02V
There was an internal error invoking the timer job ‘{FD730E80-C470-4D92-B0E5-F57C98ABDF4A}’ for service ‘{00000000-0000-0000-0000-000000000000}’.

For more information, see Help and Support Center at

Not only did that timer job not exist, don’t you love what you get when you click that helpless link:

No results were found for your query. Please see Search Help for suggestions.


Long story short: of almost 200GB usable space, 5.11MB (yes, MB) was available.  Check the available space on the database disk drive and call on your local SQL Superhero.  In our case, the transaction log was bloated and needed truncating.