In Automation account DSC node status is Unresponsive.

These are the few latest logs I see in the winEvents

Hi Ravulacheruvu Deepthi, Thanks for posting your query in Microsoft Q&A.

The log you’re seeing means that the DSC agent thinks a consistency check is still running. If that check never finishes (due to deadlock, corrupted MOF, or long-running resource execution), then all new checks are skipped. As a result, the VM stops sending reports back to Azure Automation, and the node shows up as Unresponsive.

Recommended fix:

Verify windows Event Logs

Get-WinEvent -ComputerName dscsvr2 -ListLog *dsc*

Looking in the Operational log you can find the error and the related resource:

Get-WinEvent -ComputerName dscsvr2 -LogName Microsoft-Windows-DSC/Operational -MaxEvents 10  |
Select-Object TimeCreated, Message |
Format-List

The event log also points to a json file that contains more detailed logging, this matches what would be returned if you ran the Start-DscConfiguration with the -Verbose and -Wait switches.

You will see a line:

Message: Job {93E0C95E-8F21-11E9-85A2-00155D016620}: Details logging completed for C:\Windows\system32\configuration\ConfigurationStatus\{93E0C95E-8F21-11E9-85A2-00155D016620}-0.details.json.

If an error occurs while the script is running, you’ll be able to see the details and use that information to fix the script.Refer document: https://learn.microsoft.com/en-us/powershell/dsc/troubleshooting/troubleshooting?view=dsc-1.1

If you need more details, you can turn on the debug and analytic logs for DSC and then rerun the configuration. These logs provide additional messages that can help you identify the exact reason why the configuration failed.

• Event Viewer → Applications and Services Logs → Microsoft → Windows →Desired State Configuration → Analytic.
• Very detailed, low-level trace of what the DSC Local Configuration Manager (LCM) is doing.
• Look for any error messages that might provide insight into what went wrong.

And also try resolving below steps:

Check current configuration of the nodes:

Get-DscConfigurationStatus

Refer document: https://learn.microsoft.com/en-us/powershell/module/psdesiredstateconfiguration/get-dscconfigurationstatus?view=dsc-1.1

Manually stop a stuck DSC job

Stop-DscConfiguration -Force

Remove corrupted DSC configuration files

If still stuck:

Remove-DscConfigurationDocument -Stage Current, Pending, Previous

refer document: https://learn.microsoft.com/en-us/powershell/module/psdesiredstateconfiguration/remove-dscconfigurationdocument?view=dsc-1.1

Restart DSC Services

Restart-Service -Name "DSC"

Re-register Node if Needed

Although you mentioned that you've tried unregistering and re-assigning the DSC configuration, ensure you properly clean up by completely uninstalling the DSC extension and performing a re-registration with Register-AzAutomationDscNode.

or reboot the VM if the LCM is locked.

Register-AzureAutomationDscNode -ResourceGroupName <RG> -AutomationAccountName <AA> -AzureVMName <VM>

refer document to re register:https://learn.microsoft.com/en-us/azure/automation/automation-dsc-onboarding#register-azure-vm-for-dsc

Verify LCM Configuration: Run the command Get-DscLocalConfigurationManager and ensure that your LCM is configured correctly. Look for any anomalies in the configuration

Network Connectivity:Make sure your VM can reach Azure services. Networking issues, such as proxy settings or firewall rules blocking traffic, can stop the node from checking in.

Service Health: Look at the Azure Service Health dashboard to see if there are any ongoing issues with Azure Automation that could be affecting DSC.

I hope these steps help you resolve the issue. If you run into any further issues, please feel free to post them here.

Hi Ravulacheruvu Deepthi, just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this

Hi Sandhya thanks for the troubleshooting steps, but I know my DSC is stuck at one script and I want to know which exact code of my script is stuck. I need more debug logs I do not see Analytic logs.

Hello Ravulacheruvu Deepthi,

The Event Viewer screenshot shows the Desired State Configuration logs, where the admin log contains no events, while the Operational log does have entries. This suggests that the Analytic and Debug logs for Desired State Configuration are not currently enabled or displayed in the Event Viewer.

To Troubleshoot the issue, as I mentioned in the above response manually,

1.Enable the Analytic and Debug logs in Event Viewer:

• Right-click on the Analytic log (not visible yet in their view, but can be made visible)
• Select View → Show Analytic and Debug Logs in the Event Viewer.
• Navigate again to Applications and Services Logs → Microsoft → Windows → Desired State Configuration.
• Right-click Analytic and choose Enable Log.
• Similarly, enable the Debug log if available

After enabling, rerun the DSC configuration and then check these logs for detailed trace messages about which script or resource is causing the DSC job to hang.

also check the detailed ConfigurationStatus JSON files from:

C:\Windows\System32\Configuration\ConfigurationStatus\ These files often show detailed error explanations for stuck resourcesI hope these helps you resolve the issue.