You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
This is about WindowsProcess DSC resource that we are using to invoke an exe. The configuration is pretty straightforward and is shared below. If I look at my application (exe) logs it starts and completes successfully within milliseconds. I am not sure why DSC thinks the process took a while to start. Any pointers appreciated.
WindowsProcess MyResource
{
Ensure ="Present"
Path =<full path to exe on local disk>
Arguments ="<exe command line arguments>"
DependsOn ="<a xRemoteFile resource that completes reliably>"
}
Expected behavior
The exe is invoked and it completes.
Actual behavior
Failure starting process matching path 'C:\\<full path to application>.exe'. Message: Failed to wait for processes to start."
Environment data
The text was updated successfully, but these errors were encountered:
Steps to reproduce
This is about WindowsProcess DSC resource that we are using to invoke an exe. The configuration is pretty straightforward and is shared below. If I look at my application (exe) logs it starts and completes successfully within milliseconds. I am not sure why DSC thinks the process took a while to start. Any pointers appreciated.
Expected behavior
Actual behavior
Environment data
The text was updated successfully, but these errors were encountered: