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
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-troubleshoot-validation-for-schema-failed-error.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,32 +78,32 @@ In the submitted YAML file, go to the “path” parameter and double check whet
78
78
79
79
## Error - Missing Field
80
80
81
-
The submitted YAML file is missing a required parameter. For example – for ml job create (that is, `commandjob` schema), if the “compute” parameter isn't provided, this error will be encountered because compute is required to run a command job.
81
+
The submitted YAML file is missing a required parameter. For example – for ml job create (that is, `commandjob` schema), if the “compute” parameter isn't provided, this error will be encountered because compute is required to run a command job.
82
82
83
83
### Solution - Missing Field
84
84
85
85
Check the prescribed schema for the asset type you're trying to create or update – check what parameters are required and what their correct value types are. [Here's a list of schemas](reference-yaml-overview.md) for different asset types in AzureML v2. Ensure that the submitted YAML file has all the required parameters needed. Also ensure that the values provided for those parameters are of the correct type, or in the accepted range of values. Save the YAML file and resubmit the command.
86
86
87
-
## Error - Can't Parse
87
+
## Error - Cannot Parse
88
88
89
-
The submitted YAML file can't be read, because either the syntax is wrong, formatting is wrong, or there are unwanted characters somewhere in the file. For example – a special character (like a colon or a semicolon) that has been entered by mistake somewhere in the YAML file.
89
+
The submitted YAML file can't be read, because either the syntax is wrong, formatting is wrong, or there are unwanted characters somewhere in the file. For example – a special character (like a colon or a semicolon) that has been entered by mistake somewhere in the YAML file.
90
90
91
-
### Solution - Can't Parse
91
+
### Solution - Cannot Parse
92
92
93
93
Double check the contents of the submitted YAML file for correct syntax, unwanted characters, and wrong formatting. Fix all of these, save the YAML file and resubmit the command.
94
94
95
95
## Error - Resource Not Found
96
96
97
-
One or more of the resources (for example, file / folder) in the submitted YAML file doesn't exist, or you don't have access to it.
97
+
One or more of the resources (for example, file / folder) in the submitted YAML file doesn't exist, or you don't have access to it.
98
98
99
99
### Solution - Resource Not Found
100
100
101
-
Double check whether the name of the resource has been specified correctly, and that you have access to it. Make changes if needed, save the YAML file and resubmit the command.
101
+
Double check whether the name of the resource has been specified correctly, and that you have access to it. Make changes if needed, save the YAML file and resubmit the command.
102
102
103
-
## Error - Can't Serialize
103
+
## Error - Cannot Serialize
104
104
105
105
One or more fields in the YAML can't be serialized (converted) into objects.
106
106
107
-
### Solution - Can't Serialize
107
+
### Solution - Cannot Serialize
108
108
109
109
Double check that your YAML file isn't corrupted and that the file’s contents are properly formatted.
0 commit comments