Azure Automation Hybrid Worker

To troubleshoot the failure of your Azure Automation job, you can follow these steps:

1. Check the Job Status: In the Azure Portal, navigate to the Azure Automation account and check the job status for any error messages or details that can provide insight into why the job failed.
2. Review the Microsoft-SMA Event Logs: On the virtual machine where the Hybrid Runbook Worker is installed, check the Microsoft-SMA event logs. These logs can provide information about job execution and any errors encountered during the process.
3. Verify Hybrid Worker Health: Ensure that the Hybrid Runbook Worker is healthy and giving a heartbeat. You can monitor the HybridWorkerPing metric to check for connectivity issues.
4. Run the Troubleshooter Tool: Use the troubleshooter tool available on the VM to generate an output file that can help identify any issues with the Hybrid Runbook Worker setup. The tool can be found at:
   • For Windows: C:\Packages\Plugins\Microsoft.Azure.Automation.HybridWorker.HybridWorkerForWindows\*\bin\troubleshooter\TroubleShootWindowsExtension.ps1
   • For Linux: /var/lib/waagent/Microsoft.Azure.Automation.HybridWorker.HybridWorkerForLinux-*/Troubleshooter/LinuxTroubleshooter.py
5. Check Permissions: Ensure that the necessary permissions are set correctly for the folders and registry keys required by the Hybrid Runbook Worker, as insufficient permissions can lead to job failures.

By following these steps, you should be able to gather more information on why your job is failing and determine if it has started on the virtual machine.

References:

• Troubleshoot VM extension-based Hybrid Runbook Worker issues in Automation
• Common runbook creation problems on Hybrid Runbook Worker
• Hybrid Runbook Worker overview
• Troubleshoot agent-based Hybrid Runbook Worker issues in Automation

Hello Andrea Longhitano,

Thanks for posting your question in the Microsoft Q&A forum.

Here’s what you can do to troubleshoot the issue:

Check the Job Status: First, check the logs of the specific job in the Azure Portal to see if there are any error messages or logs that could give you more context about why the job failed.

Diagnose Hybrid Worker Issues: Since you're using a Hybrid Worker, run some diagnostics to ensure it’s functioning correctly. You can use the diagnostics available for hybrid workers, which will help check for common issues like connectivity or configuration problems. Here are some links for reference:

• Troubleshoot VM extension-based Hybrid Runbook Worker issues
• Use the Test Cloud Connectivity tool

Verify Job Execution Environment: Ensure that the environment where your job runs meets the requirements. Sometimes, jobs fail if they exceed memory limits (400 MB) or there are permission issues. You might want to consult the relevant diagnostics for these:

• Jobs failing due to memory limits ACIExceededMemoryLimit diagnostics
• Jobs failing due to permission issues Runbook permissions diagnostics

Extension Health: If the Hybrid Worker is not reporting accurately, consider verifying if the installation of the extension for the Hybrid Worker is intact and functioning. Follow the steps listed in Deploy an Extension-Based Hybrid Worker.

If you still face challenges, please let me know the following:

• What error messages are you seeing in the Azure Portal?
• Are you able to access the logs for the job to gather more context?
• Can you confirm the environment (VM) is online and properly configured as a Hybrid Worker?

Hope this helps you get closer to a solution! Let me know if you have any further questions!