1

I have a job "WorkItem User Delivery" that seems to be stuck in TFS 2017 Update 2 (SQL Server 2016). It's been running for 4 days and is causing issues with the other mail/soap jobs and email alerts are very sporadic: Image of JobQueue in TFS OI

I've located the job in [Tfs_Configuration].[dbo].[tbl_JobQueue] with a JobID of 631F49B3-46E1-42EC-8FFF-081BD176C18A. I've already restarted TFSJobAgent with no luck. Is it safe to delete this row from the table and will that be effective in removing the job?

UtahTim
  • 11
  • 3

2 Answers2

0

For the queued jobs, you can try using the RepairJobQueue command to fix scheduled jobs that have stopped running for deployment and collection hosts.

Generally we don't recommend to do actions against the DBs directly as it's not safe.

But if that still not work, you can have a try to clear the related Job Queues. Please remember to backup the DBs first in case meet unexpected problems.

After the backup, you can try clearing the related Notification Job Queues and removing the "WorkItem User Delivery" job with ID : 631F49B3-46E1-42EC-8FFF-081BD176C18A to check if that helps.

To clear the Notification Job Queues, you can reference this thread: TFS Clear Notification Job Queue

Andy Li-MSFT
  • 28,712
  • 2
  • 33
  • 55
0

We recently added two new application tiers to our production infrastructure as we get ready to migrate to a new On-Premises data center. These two new application tiers were not added to our load balanced VIP so no load was actually getting to them (except when I hit them directly).

These new machines didn't have firewall access to the machine that is listening for SOAP calls in the current prod data center (and possibly not even to the mailhost). I believe TFS offloaded these notification/soap jobs to one of these new machines because as soon as I turned off TFSJobAgent on all four machines and turned it back on on only the two original machines did everything start working again.

UtahTim
  • 11
  • 3