"0 timer jobs found. Check input values or use the WebAppUrl parameter." #48
Comments
|
Note, this issue does NOT occur if I omit the -Mode Full parameter. |
|
I've confirmed that this is not a regression issue. @brianlala can I ask you to run the following on your environment. I need to troubleshoot what timer job is actually giving you a hard time. Just tried on a Single Server SP2013 SP1 server and didn't get that issue. Import-Module ReverseDSC $spTimers = Get-SPTimerJob } |
|
OK I'll try in a bit, thanks Nik. |
|
Oops looks like we have a missing function: Repair-Credentials : The term 'Repair-Credentials' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
|
|
My bad, comment out the line that calls into it. I forgot to include it in my snippet, but you can just safely ignore that line for the purpose of this test. I've edited the snippet in my previous comment |
|
Very similar output to what ReverseDSC gives: Scanning Timer Job { RemoveWordConversionJobHistory }[231/250]...
Looks like it's choking on "Word Automation Services" ? |
|
Yeah, but at least now we know that it is the Word Automation Timer Job that is failing. I'll investigate further |
|
Reproduced your error, but whenever I had 2 UPS which created two instances of Farm wide timer jobs. The SPDSC has logic in it that there should be no more than 1 instances (actually....exactly 1 instance) of a Farm wide timer job that should exist. In my case I have two, so it errors out....you're case is a little different. This will sound exhaustive, but can you put the output of running Get-SPTimerJob | select Type even if it is 250 entries? The issue has been opened in SharePointDSC as well dsccommunity/SharePointDsc#791 |
|
Here's the output of Get-SPTimerJob | select TypeName | Sort-Object TypeName: TypeNameMicrosoft.Office.DocumentManagement.Internal.DocIdEnableWorkItemJobDefinition |
|
Thanks @brianlala What is weird is that there is an entry for Word Automation Services Timer Job, but the error says it found '0' instances. Do you get something if you run: |
|
FWIW - I can replicate your issue. Deploying the Word Automation Service App does create a new timer job with name Word Automation Services Timer Job, I do see it in the list when I do Get-SPTimerJob, but can't get to it by doing Get-SPTimerJob -Type "Word Automation Services Timer Job" |
|
Get-SPTimerJob -Type "Word Automation Services Timer Job" returns nothing. However, Get-SPTimerJob | Where-object {$_.TypeName -eq "Word Automation Services Timer Job"} | FL returns one timer job: DisplayName : Word Automation Services Timer Job |
Details of the scenario you try and problem that is occurring:
Single-server SharePoint 2013 farm, recent CU, SQL server co-installed. Trying to extract config using the following command line:
& "C:\Program Files\WindowsPowerShell\Scripts\SharePointDSC.Reverse.ps1" -Mode Full -OutputFile C:\temp\SP-Farm.DSC.ps1 -Verbose
Getting the following error:
0 timer jobs found. Check input values or use the WebAppUrl parameter.
At line:61 char:17
The DSC configuration that is using the resource:
n/a or not sure
Version of the Operating System and PowerShell the DSC Target Node is running:
Windows Server 2012 R2
Name : ConsoleHost
Version : 5.0.10586.117
InstanceId : 47b9b456-d127-4d2e-9b8d-146d2f1d2b40
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-US
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace
Version of the DSC module you're using:
2.2.0.0
The text was updated successfully, but these errors were encountered: