That is not a good sign, it shows that a Farm can not create a Timer Job. You can do a basic deployment test solutions and follow this guide  

Thank you. I will try that.

This issue is resolved.  Even though the SharePoint Timer service was started in services.msc, the timer service instance object for one of the web server was set to Disabled.The resolution can be found in the forum below (Solution #1): 

SharePoint Timer jobs not running(Specially one-time timer jobs) – Sujeet Sharma 

Hi @Shruti Patrabansh 

The URL you have mentioned is not working. Could you please suggest resolution steps you followed. We are doing it for  Nintex 2016.

Nintex for SharePoint‌ If you can help that would be helpful. #Nintex2016UpgradeTo4.3.3

If you get the issue run this script to see if the timer service is offline /disabled

$farm = Get-SPFarm
$disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}
if ($disabledTimers -ne $null) {foreach ($timer in $disabledTimers) {Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status}}

If offline, run below script on one server in the farm then re-start SP Timer service on EVERY SP servers that has reported its timer service as offline/ disabled

$farm = Get-SPFarm
$disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}
if ($disabledTimers -ne $null)
{
foreach ($timer in $disabledTimers)
{
Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status
Write-Host "Attempting to set the status of the service instance to online"
$timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online
$timer.Update()
}
}
else
{
Write-Host "All Timer Service Instances in the farm are online! No problems found"
}

I ran into this issue and I had trouble using the script that darrentcs posted since it contained a emoji :O

Here is where it is posted on a Microsoft KB:

https://support.microsoft.com/en-us/help/2616609/administrative-timer-jobs-not-running-after-upgrade

Reposted in a code block

$farm = Get-SPFarm

$disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}

if ($disabledTimers -ne $null)

{

foreach ($timer in $disabledTimers)

{

Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status

Write-Host "Attempting to set the status of the service instance to online"

$timer.Status = =Microsoft.SharePoint.Administration.SPObjectStatus]::Online

$timer.Update()

}

}

else

{

Write-Host "All Timer Service Instances in the farm are online! No problems found"

}