AzureMLComputejob failed. NonCompliantReason while running Command Component

45659249 20 Reputation points Microsoft Employee
2023-06-07T13:50:23.1733333+00:00

User's image

While running a Command Component I am facing above error. This component was working fine couple of days earlier.

Azure Machine Learning
Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. YutongTie-9091 54,016 Reputation points Moderator
    2023-06-08T03:19:55.4466667+00:00

    Hello @45659249

    Thanks for reaching out to us, the screenshot you shared can not be zoomed, we can not see the details clear, if it is possible, could you please share a clear error details to us? Or you can share the log to us so that we can see what is the problem.

    Based on the error "NonCompliantReason while running Command Component", there could be several reasons why this error occurred, but some common causes include:

    Insufficient resources: If your job requires more resources than are available in your compute target, it may fail. You can try scaling up your compute target or optimizing your job to reduce its resource requirements.

    Incorrect command syntax: If there is an error in the command syntax of your job, it may fail. You can try reviewing your command syntax and ensuring that it is correct.

    Missing dependencies: If your job requires dependencies that are not installed on your compute target, it may fail. You can try installing the required dependencies or using a different compute target that already has the dependencies installed.

    1. Data issues: If there are issues with your input data or output data, your job may fail. You can try reviewing your data and ensuring that it is in the correct format and that there are no missing or corrupted files.

    To troubleshoot this issue further, you can try reviewing the logs and error messages generated by your job to identify the specific cause of the failure. You can also try running your job locally or on a different compute target to see if the issue persists.

    I hope this helps! Let me know if you have any further questions.

    Regards,

    Yutong

    -Please kindly accept the answer if you feel helpful to support the community, thanks a lot.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.