none
issue when trying to capture the sharepoint uls logs RRS feed

  • Question

  • I am trying to capture the SharePoint ULS logs for the something went wrong error,

    but came up with below message, not sure what could be the cause.

    Please help

    Below is the warning message:


    since above is not clear, below is the message pasted 

    WARNING: Unable to start job CollectLogFiles_XXXXX_1831278062 on server XXXX.
    WARRNING: Cmdlet did not return any records in the log file. Check your time range or filters.

    I have given time range as well but still why it is happening

    • Edited by SravanC Friday, August 16, 2019 11:57 AM
    Friday, August 16, 2019 11:51 AM

Answers

  • Hi Sravan,

    Run the below script and make sure all your timer services are in online. If the timer Service is not online the script will start. or else try manually restarting timer service from all servers manually. Then give it a try.

    asnp *sh*
    $farm = Get-SPFarm 
    $FarmTimers = $farm.TimerService.Instances 
    foreach ($FT in $FarmTimers){write-host "Server: " $FT.Server.Name.ToString(); write-host "Status: " $FT.status; write-host "Allow Service Jobs: " $FT.AllowServiceJobs; write-host "Allow Content DB Jobs: " $FT.AllowContentDatabaseJobs;"`n"}
    $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"} 
    if ($disabledTimers -ne $null) 
    {foreach ($timer in $disabledTimers) 
    {Write-Host -ForegroundColor Red "Timer service instance on server " $timer.Server.Name " is NOT Online. Current status:" $timer.Status 
    Write-Host -ForegroundColor Green "Attempting to set the status of the service instance to online..." 
    $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online 
    $timer.Update() 
    write-host -ForegroundColor Red "You MUST now go restart the SharePoint timer service on server " $FT.Server.Name}} 
    else{Write-Host -ForegroundColor Green  "All Timer Service Instances in the farm are online. No problems found!"}   
    Thanks & Regards,


    sharath aluri

    • Marked as answer by SravanC Friday, August 16, 2019 1:10 PM
    Friday, August 16, 2019 12:56 PM

All replies

  • Hiya,

    Basically it's a one time, timer job that needs to run. So there are quite a lot of things that can cause this.

    1: How many servers are in this farm? (Check which servers gives the timer job error, one or all)

    2: Are you experiencing any performance issues in general on the farm? (Execution of timer jobs can be messed up if the server performance is not adequate)

    3: The basic steps would be to reset timer job cache prior to running and see if this helps.

    Friday, August 16, 2019 12:00 PM
  • Hi Arnecke,

    Thank you for the response

    1. 

    2 WEB FRONT

    2 APP 

    2.

    NO We are not experiencing performance issues.. 

    3. How to reset the timer job cache. Please share me the steps with screenshots 

    Friday, August 16, 2019 12:05 PM
  • Hi Sravan,

    Run the below script and make sure all your timer services are in online. If the timer Service is not online the script will start. or else try manually restarting timer service from all servers manually. Then give it a try.

    asnp *sh*
    $farm = Get-SPFarm 
    $FarmTimers = $farm.TimerService.Instances 
    foreach ($FT in $FarmTimers){write-host "Server: " $FT.Server.Name.ToString(); write-host "Status: " $FT.status; write-host "Allow Service Jobs: " $FT.AllowServiceJobs; write-host "Allow Content DB Jobs: " $FT.AllowContentDatabaseJobs;"`n"}
    $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"} 
    if ($disabledTimers -ne $null) 
    {foreach ($timer in $disabledTimers) 
    {Write-Host -ForegroundColor Red "Timer service instance on server " $timer.Server.Name " is NOT Online. Current status:" $timer.Status 
    Write-Host -ForegroundColor Green "Attempting to set the status of the service instance to online..." 
    $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online 
    $timer.Update() 
    write-host -ForegroundColor Red "You MUST now go restart the SharePoint timer service on server " $FT.Server.Name}} 
    else{Write-Host -ForegroundColor Green  "All Timer Service Instances in the farm are online. No problems found!"}   
    Thanks & Regards,


    sharath aluri

    • Marked as answer by SravanC Friday, August 16, 2019 1:10 PM
    Friday, August 16, 2019 12:56 PM
  • Thank you sharth. It worked.

    in one of the server Timer service is stopped which could not allow to capture the logs

    Friday, August 16, 2019 1:11 PM
  • Hi Sharath,

    Thanks.  

    Best Regards, 

    Lisa Chen 


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Monday, August 19, 2019 6:08 AM
    Moderator