In the Timer Job Definitions page there are a few jobs that I would like to delete (orphaned Content Deployment jobs). However, when I run the following command they dont show up (only about 4 show), and, in the Timer Job Definition page the web site column lists "N/A" for the ones I want to delete. I really dont know what value to use for -title in order to get these jobs to show. Any advice? "SSP" is the only SSP that shows on/_admin/managessp.aspx (of course it has about 5 websites).stsadm -o enumssptimerjobs -title SSP

Hi, try this: Central Administration > Operations > Timer Job Definitions and mouse over the job you need to delete andlook at Internet Explorer status bar (in the right bottom corner) while pointing your mouse cursor on the orphan timer job. Note down the GUID after JobId= Run the following command and replace objectId with above GUID number. stsadm.exe -o deleteconfigurationobject -id <objectId> Hope this helps!Cheers,Daniel Bugday Web: http://www.sharepointforum.com/ Blog: http://www.sharepointforum.com/en-US/Blog/

That did it! For some reason the delete command I found and thought to use required the -title as well. I wanted to do it the way you suggested but didnt know about "deleteconfigurationobject". Excellent, thanks!

HiDaniel Bugday Thanks....! Hi Intrawebs, I did it with "deleteconfigurationobject", when we copy the JobId it had "%2D" and removed that it worked fine, may be it will be helpful to you, Thanks Modiyam

Hi Daniel,Canthis command parameter of stsadm be used to remove orphan database entries from the SharePoint Farm cofnig database? I deployed PWA once but then it was misbehaving on one of front ends so I edned up deleting it and redeploying a new instance of PWA. Hoever, the database names used in the initial deployment stuck in the farm config database fot some reason and every time I run a patch of anything that requires sharePoint configuration wizzard i have attach those phantom databases or else the wizard fails.. so do you know if this can be used with orphan database entries???

Thanks so much for the post!Its saved my life... I used the above said comment and replaced "%2D" with - and it worked.Toufiq.

Hi Daniel,Canthis command parameter of stsadm be used to remove orphan database entries from the SharePoint Farm cofnig database? I deployed PWA once but then it was misbehaving on one of front ends so I edned up deleting it and redeploying a new instance of PWA. Hoever, the database names used in the initial deployment stuck in the farm config database fot some reason and every time I run a patch of anything that requires sharePoint configuration wizzard i have attach those phantom databases or else the wizard fails.. so do you know if this can be used with orphan database entries??? I'm running into the same problem. What's the best procedure for this?

Hi,i use this command to remove orphaned content deployment jobs and have never used it for other things.I'll look into this as soon as i get to my SharePoint environment and let you know!What exactly are you trying to do?Cheers, Daniel Bugday Web: SharePoint Forum Blog: SharePoint By Bugday

Threre's PoweShell way: you can list timer jobs with: Get-SPTimerJob it will show you "Name" of the timer job (not display name). once you know it: $job = Get-SPTimerJob NameOfTimerJob $job.Delete() Get-Process owstimer | Stop-Process by killing "owstimer" process you can avoid caching of "Job Definitions" you just deleted and don't worry, it'll start automatically in a few seconds Moderator Note: NEVER propose your own posts as answers. The "Propose as Answer" function is for people to propose the good anwers of other people. It is NOT for self-proposing. (This thread was in any case closed October 2009)

Threre's PoweShell way: you can list timer jobs with: Get-SPTimerJob it will show you "Name" of the timer job (not display name). once you know it: $job = Get-SPTimerJob NameOfTimerJob $job.Delete() Get-Process owstimer | Stop-Process by killing "owstimer" process you can avoid caching of "Job Definitions" you just deleted and don't worry, it'll start automatically in a few seconds