Merge pull request #210957 from Clare-Zheng82/0909-Add_Web_activity_error_codes

[Supportability] - Add Web activity error codes

Author: prmerger-automator[bot]

articles/data-factory/data-factory-troubleshoot-guide.md

@@ -7,7 +7,7 @@ ms.service: data-factory
 ms.subservice: troubleshooting
 ms.custom: synapse
 ms.topic: troubleshooting
-ms.date: 08/03/2022
+ms.date: 09/13/2022
 ms.author: abnarain
 ---
 
@@ -1022,56 +1022,114 @@ If the HDI activity is stuck in preparing for cluster, follow the guidelines bel
 
 ## Web Activity  
 
-### Error code: 2128
+### Error Code: 2001
 
-- **Message**: `No response from the endpoint. Possible causes: network connectivity, DNS failure, server certificate validation or timeout.`
+- **Message**: `The length of execution output is over limit (around 4MB currently).`
 
-- **Cause**: This issue is due to either Network connectivity, a DNS failure, a server certificate validation, or a timeout.
+- **Cause**: The execution output is greater than 4 MB in size but the maximum supported output response payload size is 4 MB.
 
-- **Recommendation**: Validate that the endpoint you are trying to hit is responding to requests. You may use tools like **Fiddler/Postman/Netmon/Wireshark**.
+- **Recommendation**: Make sure the execution output size does not exceed 4 MB. For more information, see [How to scale out the size of data moving using Azure Data Factory](https://docs.microsoft.com/answers/questions/700102/how-to-scale-out-the-size-of-data-moving-using-azu.html).
 
-### Error code: 2108
+### Error Code: 2002
 
-- **Message**: `Error calling the endpoint '%url;'. Response status code: '%code;'`
+- **Message**: `The payload including configurations on activity/dataSet/linked service is too large. Please check if you have settings with very large value and try to reduce its size.`
 
-- **Cause**: The request failed due to an underlying issue such as network connectivity, a DNS failure, a server certificate validation, or a timeout.
+- **Cause**: The payload you are attempting to send is too large.
 
-- **Recommendation**: Use Fiddler/Postman/Netmon/Wireshark to validate the request.
+- **Recommendation**: Refer to [Payload is too large](data-factory-troubleshoot-guide.md#payload-is-too-large).
 
-#### More details
-To use **Fiddler** to create an HTTP session of the monitored web application:
+### Error Code: 2003
 
-1. Download, install, and open [Fiddler](https://www.telerik.com/download/fiddler).
+- **Message**: `There are substantial concurrent external activity executions which is causing failures due to throttling under subscription <subscription id>, region <region code> and limitation <current limit>. Please reduce the concurrent executions. For limits, refer https://aka.ms/adflimits.`
 
-1. If your web application uses HTTPS, go to **Tools** > **Fiddler Options** > **HTTPS**.
+- **Cause**: Too many activities are running concurrently. This can happen when too many pipelines are triggered at once.
 
-   1. In the HTTPS tab, select both **Capture HTTPS CONNECTs** and **Decrypt HTTPS traffic**.
+- **Recommendation**: Reduce pipeline concurrency. You might have to distribute the trigger time of your pipelines.  
 
-      :::image type="content" source="media/data-factory-troubleshoot-guide/fiddler-options.png" alt-text="Fiddler options":::
+### Error Code: 2010
 
-1. If your application uses TLS/SSL certificates, add the Fiddler certificate to your device.
+- **Message**: `The Self-hosted Integration Runtime ‘<SHIR name>’ is offline`
 
-   Go to: **Tools** > **Fiddler Options** > **HTTPS** > **Actions** > **Export Root Certificate to Desktop**.
+- **Cause**: The self-hosted integration runtime is offline or the Azure integration runtime is expired or not registered.
 
-1. Turn off capturing by going to **File** > **Capture Traffic**. Or press **F12**.
+- **Recommendation**: Make sure your self-hosted integration runtime is up and running. Refer to [Troubleshoot self-hosted integration runtime](self-hosted-integration-runtime-troubleshoot-guide.md) for more information.
 
-1. Clear your browser's cache so that all cached items are removed and must be downloaded again.
+### Error Code: 2105
 
-1. Create a request:
+- **Message**: `The value type '<provided data type>', in key '<key name>' is not expected type '<expected data type>'`
 
-1. Select the **Composer** tab.
+- **Cause**: Data generated in the dynamic content expression doesn't match with the key and causes JSON parsing failure.
 
-   1. Set the HTTP method and URL.
- 
-   1. If needed, add headers and a request body.
+- **Recommendation**: Look at the key field and fix the dynamic content definition.
+
+### Error code: 2108
+
+- **Message**: `Error calling the endpoint '<URL>'. Response status code: 'NA - Unknown'. More details: Exception message: 'NA - Unknown [ClientSideException] Invalid Url:<URL>. Please verify Url or integration runtime is valid and retry. Localhost URLs are allowed only with SelfHosted Integration Runtime`
+
+- **Cause**: Unable to reach the URL provided. This can occur because there was a network connection issue, the URL was unresolvable, or a localhost URL was being used on an Azure integration runtime.
+
+- **Recommendation**: Verify that the provided URL is accessible.
+
+<br/> 
+
+- **Message**: `Error calling the endpoint '%url;'. Response status code: '%code;'`
+
+- **Cause**: The request failed due to an underlying issue such as network connectivity, a DNS failure, a server certificate validation, or a timeout.
+
+- **Recommendation**: Use Fiddler/Postman/Netmon/Wireshark to validate the request.
+
+    **Using Fiddler**
+    
+    To use **Fiddler** to create an HTTP session of the monitored web application:
+    
+    1. Download, install, and open [Fiddler](https://www.telerik.com/download/fiddler).
+    
+    1. If your web application uses HTTPS, go to **Tools** > **Fiddler Options** > **HTTPS**.
+    
+       1. In the HTTPS tab, select both **Capture HTTPS CONNECTs** and **Decrypt HTTPS traffic**.
+    
+          :::image type="content" source="media/data-factory-troubleshoot-guide/fiddler-options.png" alt-text="Fiddler options":::
+    
+    1. If your application uses TLS/SSL certificates, add the Fiddler certificate to your device.
+    
+       Go to: **Tools** > **Fiddler Options** > **HTTPS** > **Actions** > **Export Root Certificate to Desktop**.
+    
+    1. Turn off capturing by going to **File** > **Capture Traffic**. Or press **F12**.
+    
+    1. Clear your browser's cache so that all cached items are removed and must be downloaded again.
+    
+    1. Create a request:
+    
+    1. Select the **Composer** tab.
+    
+       1. Set the HTTP method and URL.
+     
+       1. If needed, add headers and a request body.
+    
+       1. Select **Execute**.
+    
+    1. Turn on traffic capturing again, and complete the problematic transaction on your page.
+    
+    1. Go to: **File** > **Save** > **All Sessions**.
+    
+    For more information, see [Getting started with Fiddler](https://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureFiddler).
+
+### Error Code: 2113
+
+- **Message**: `ExtractAuthorizationCertificate: Unable to generate a certificate from a Base64 string/password combination`
+
+- **Cause**: Unable to generate certificate from Base64 string/password combination.
+
+- **Recommendation**: Verify that the Base64 encoded PFX certificate and password combination you are using are correctly entered.
+
+### Error Code: 2403
 
-   1. Select **Execute**.
+- **Message**: `Get access token from MSI failed for Datafactory <DF mname>, region <region code>. Please verify resource url is valid and retry.`
 
-1. Turn on traffic capturing again, and complete the problematic transaction on your page.
+- **Cause**: Unable to acquire an access token from the resource URL provided.
 
-1. Go to: **File** > **Save** > **All Sessions**.
+- **Recommendation**: Verify that you have provided the correct resource URL for your managed identity.
 
-For more information, see [Getting started with Fiddler](https://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureFiddler).
 
 ## General