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/data-factory/data-factory-troubleshoot-guide.md
+113-2Lines changed: 113 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -277,18 +277,110 @@ The following table applies to U-SQL.
277
277
278
278
-**Cause**: Azure function activity definition is not complete.
279
279
280
-
-**Recommendation**: Please check the input AzureFunction activity JSON definition has property named 'method'.
280
+
-**Recommendation**: Check if the input AzureFunction activity JSON definition has property named 'method'.
281
281
282
282
283
283
### Error code: 3612
284
284
285
285
-**Message**: `Azure function activity missing LinkedService definition in JSON.`
286
286
287
-
-**Cause**: Azure function activity definition is not complete.
287
+
-**Cause**: Azure function activity definition may not be complete.
288
288
289
289
-**Recommendation**: Please check the input AzureFunction activity JSON definition has linked service details.
290
290
291
291
292
+
## Azure Machine Learning
293
+
294
+
295
+
### Error code: 4101
296
+
297
+
-**Message**: `AzureMLExecutePipeline activity '%activityName;' has invalid value for property '%propertyName;'.`
298
+
299
+
-**Cause**: Bad format or missing definition of a property.
300
+
301
+
-**Recommendation**: Please check if the activity is defined with the correct data.
302
+
303
+
304
+
### Error code: 4110
305
+
306
+
-**Message**: AzureMLExecutePipeline activity missing LinkedService definition in JSON.
307
+
308
+
-**Cause**: AzureMLExecutePipeline activity definition is not complete.
309
+
310
+
-**Recommendation**: Please check if the input AzureMLExecutePipeline activity JSON definition has linked service details.
311
+
312
+
313
+
### Error code: 4111
314
+
315
+
-**Message**: `AzureMLExecutePipeline activity has wrong LinkedService type in JSON. Expected LinkedService type: '%expectedLinkedServiceType;', current LinkedService type: Expected LinkedService type: '%currentLinkedServiceType;'.`
316
+
317
+
-**Cause**: Incorrect activity definition.
318
+
319
+
-**Recommendation**: Please check if the input AzureMLExecutePipeline activity JSON definition has correct linked service details.
320
+
321
+
322
+
### Error code: 4112
323
+
324
+
-**Message**: `AzureMLService linked service has invalid value for property '%propertyName;'.`
325
+
326
+
-**Cause**: Bad format or missing definition of a property.
327
+
328
+
-**Recommendation**: Please check if the linked service definition has correct data.
329
+
330
+
331
+
### Error code: 4121
332
+
333
+
-**Message**: `Request sent to AzureML Service for operation '%operation;' failed with http status code '%statusCode;'. Error message from AzureML Service: '%externalMessage;'.`
334
+
335
+
-**Cause**: Credential used to access Azure ML Service has expired.
336
+
337
+
-**Recommendation**: Please verify credential is valid and retry
338
+
339
+
340
+
### Error code: 4122
341
+
342
+
-**Message**: `Request sent to AzureML Service for operation '%operation;' failed with http status code '%statusCode;'. Error message from AzureML Service: '%externalMessage;'.`
343
+
344
+
-**Cause**: Credential provided in AzureML Service Linked Service is invalid or does not have permission for the operation.
345
+
346
+
-**Recommendation**: Please verify credential in Linked Service is valid and has permission to access AzureML Service.
347
+
348
+
349
+
### Error code: 4123
350
+
351
+
-**Message**: `Request sent to AzureML Service for operation '%operation;' failed with http status code '%statusCode;'. Error message from AzureML Service: '%externalMessage;'.`
352
+
353
+
-**Cause**: `Properties of the activity such as pipelineParamters are invalid for the Azure ML pipeline.`
354
+
355
+
-**Recommendation**: Please check the value of activity properties to match expected payload of the published Azure ML pipeline specified in Linked Service.
356
+
357
+
358
+
### Error code: 4124
359
+
360
+
-**Message**: `Request sent to AzureML Service for operation '%operation;' failed with http status code '%statusCode;'. Error message from AzureML Service: '%externalMessage;'.`
361
+
362
+
-**Cause**: The published Azure ML pipeline endpoint does not exist.
363
+
364
+
-**Recommendation**: Please verify the published Azure ML pipeline endpoint specified in Linked Service exists in Azure ML Service.
365
+
366
+
367
+
### Error code: 4125
368
+
369
+
-**Message**: `Request sent to AzureML Service for operation '%operation;' failed with http status code '%statusCode;'. Error message from AzureML Service: '%externalMessage;'.`
370
+
371
+
-**Cause**: Server error on Azure ML Service.
372
+
373
+
-**Recommendation**: Please retry later. Contact Azure ML Service team for help if issue remains.
374
+
375
+
376
+
### Error code: 4126
377
+
378
+
-**Message**: `AzureML pipeline run failed with status: '%amlPipelineRunStatus;'. Azure ML pipeline run Id: '%amlPipelineRunId;'. Please check in AzureMLService for more error loggings.`
379
+
380
+
-**Cause**: AzureML pipeline run failed.
381
+
382
+
-**Recommendation**: Please check in AzureMLService for more error loggings and fix the ML pipeline
383
+
292
384
293
385
## Custom
294
386
@@ -564,6 +656,25 @@ The following table applies to Spark, Hive, MapReduce, Pig, and Hadoop Streaming
564
656
565
657
-**Recommendation**: Use Fiddler or Postman to check the endpoint.
566
658
659
+
660
+
### Error code: 2208
661
+
662
+
-**Message**: `Invoking Web Activity failed with HttpStatusCode - {0}.`
663
+
664
+
-**Cause**: The target service returned failure status.
665
+
666
+
-**Recommendation**: Use Fiddler/Postman to validate the request.
667
+
668
+
669
+
### Error code: 2308
670
+
671
+
-**Message**: `No response from the endpoint. Possible causes: network connectivity, DNS failure, server certificate validation or timeout.`
672
+
673
+
-**Cause**: There can be multiple reasons for this error like network connectivity, DNS failure, server certificate validation or timeout.
674
+
675
+
-**Recommendation**: Use Fiddler/Postman to validate the request.
676
+
677
+
567
678
To use Fiddler to create an HTTP session of the monitored web application:
568
679
569
680
1. Download, install, and open [Fiddler](https://www.telerik.com/download/fiddler).
0 commit comments