Merge pull request #109991 from uhabiba04/master

PMEds28 · web-flow · commit 447d10aa4a51 · 2020-04-02T10:22:59.000+01:00
updating as per the standards and fixing minor formatting issues
diff --git a/articles/industry/agriculture/troubleshoot-azure-farmbeats.md b/articles/industry/agriculture/troubleshoot-azure-farmbeats.md
@@ -14,7 +14,7 @@ This article provides solutions to common Azure FarmBeats issues. For additional
 ## Install issues
 
   > [!NOTE]
-  > If you are restarting the install because of an error, make sure to delete the Resource Group or delete all resources from the Resource Group before re-triggering the install.
+  > If you are restarting the install because of an error, ensure to delete the **Resource Group** or delete all resources from the Resource Group before re-triggering the installation.
 
 ### Invalid Sentinel credentials
 
@@ -26,31 +26,32 @@ Increase the quota, or delete the unused batch accounts and restart the installa
 
 ### Invalid resource group location
 
-Make sure the Resource Group is in the same location as the Region specified during installation.
+Ensure the **Resource Group** is in the same location as the **Region** specified during installation.
 
 ### Other install issues
 
 Contact us with the following details:
 
 - Your Subscription ID
 - Resource Group name
-- Attach the log file for the Deployment failure using the steps below:
+- Follow the below steps to attach the log file for the Deployment failure:
 
-    1. Navigate to the Resource Group in the Azure portal.
-    2. Select Deployments under Settings section on the left hand side.
-    3. For every deployment that shows "Failed", click through to details and download the deployment details. Attach this file to the mail.
+    1. Navigate to the **Resource Group** in the Azure portal.
+    2. Select **Deployments** under **Settings** section on the left hand side.
+    3. For every deployment that shows **Failed**, select through to the details and download the deployment details. Attach this file to the mail.
 
 ## Sensor telemetry
 
 ### Can't view telemetry data
 
 **Symptom**: Devices or sensors are deployed, and you've linked FarmBeats with your device partner, but you can't get or view telemetry data on FarmBeats.
 
-**Corrective action**:
+**Corrective action**
 
 1. Go to your FarmBeats Datahub resource group.
 2. Select the **Event Hub** (DatafeedEventHubNamespace), and then check for the number of incoming messages.
 3. Do either of the following:
+
    - If there are *no incoming messages*, contact your device partner.  
    - If there are *incoming messages*, contact us with your Datahub and Accelerator logs and captured telemetry.
 
@@ -60,9 +61,9 @@ To understand how to download logs, go to the ["Collect logs manually"](#collect
 
 **Symptom**: Devices or sensors are deployed, and you've created the devices/sensors on FarmBeats and ingested telemetry to the EventHub, but you can't get or view telemetry data on FarmBeats.
 
-**Corrective action**:
+**Corrective action**
 
-1. Ensure you have done the partner registration correctly - you can check this by going to your datahub swagger, navigate to /Partner API, Do a Get and check if the partner is registered. If not, follow the [steps here](get-sensor-data-from-sensor-partner.md#enable-device-integration-with-farmbeats) to add partner.
+1. Ensure you have done the partner registration correctly - you can check this by going to your datahub swagger, navigate to /Partner API, Do a Get and check if the partner is registered. If not, follow these [steps](get-sensor-data-from-sensor-partner.md#enable-device-integration-with-farmbeats) to add partner.
 
 2. Ensure that you have used the correct Telemetry message format:
 
@@ -91,7 +92,7 @@ To understand how to download logs, go to the ["Collect logs manually"](#collect
 
 ### Don't have the Azure Event Hubs connection string
 
-**Corrective action**:
+**Corrective action**
 
 1. In Datahub Swagger, go to the Partner API.
 2. Select **Get** > **Try it out** > **Execute**.
@@ -108,7 +109,8 @@ To understand how to download logs, go to the ["Collect logs manually"](#collect
 
 **Symptoms**: Devices are installed, and you've linked FarmBeats with your device partner. The devices are online and sending telemetry data, but they appear offline.
 
-**Corrective action**: The reporting interval isn't configured for this device. To set the reporting interval, contact your device manufacturer. 
+**Corrective action**
+The reporting interval isn't configured for this device. To set the reporting interval, contact your device manufacturer. 
 
 ### Error deleting a device
 
@@ -118,7 +120,7 @@ While you're deleting a device, you might encounter one of the following common
 
 **Meaning**: The device is associated with multiple sensors that are deployed in the farm.
 
-**Corrective action**:  
+**Corrective action**  
 
 1. Delete the sensors that are associated with the device through Accelerator.  
 2. If you want to associate the sensors with a different device, ask your device partner to do the same.  
@@ -135,16 +137,16 @@ While you're deleting a device, you might encounter one of the following common
 
     > [!NOTE]
     > You can't delete a device if sensors are associated with it. For more information about how to delete associated sensors, see the **Delete sensor** section in [Get sensor data from sensor partners](get-sensor-data-from-sensor-partner.md).
-    > Partners do not have access to delete a device or sensor. Only Admins have access to do the same.
+    > Partners do not have permission to delete a device or sensor. Only Admins have permission to delete.
 
 ## Issues with jobs
 
 ### FarmBeats internal error
 
-**Message**: "FarmBeats internal error, see troubleshooting guide for more details".
+**Message**: "FarmBeats internal error, see troubleshooting guide for more details."
 
-**Corrective action**:
-This issue might result from a temporary failure in the data pipeline. Create the job again. If the error persists, contact us with the error message / logs.
+**Corrective action**
+This issue might result from a temporary failure in the data pipeline. Create the job again. If the error persists, contact us with the error message/logs.
 
 ## Accelerator troubleshooting
 
@@ -154,15 +156,17 @@ This issue might result from a temporary failure in the data pipeline. Create th
 
 **Message**: "No matching users found."
 
-**Corrective action**: Check the email ID for which you're trying to add a role assignment. The email ID must be an exact match of the ID, which is registered for that user in the Active Directory. If the error persists, contact us with the error message / logs.
+**Corrective action**
+Check the email ID for which you're trying to add a role assignment. The email ID must be an exact match of the ID, which is registered for that user in the Active Directory. If the error persists, contact us with the error message/logs.
 
 ### Unable to log in to Accelerator
 
 **Message**: "Error: You are not authorized to call the service. Contact the administrator for authorization."
 
-**Corrective action**: Ask the administrator to authorize you to access the FarmBeats deployment. This can be done by doing a POST of the RoleAssignment APIs or through the Access Control in the **Settings** pane in Accelerator.  
+**Corrective action**
+Ask the administrator to authorize you to access the FarmBeats deployment. This can be done by doing a POST of the RoleAssignment APIs or through the Access Control in the **Settings** pane in Accelerator.  
 
-If you've already been granted access and are facing this error, try again by refreshing the page. If the error persists, contact us with the error message / logs.
+If you've already been granted access and facing this error, try again by refreshing the page. If the error persists, contact us with the error message/logs.
 
 ![Project FarmBeats](./media/troubleshoot-azure-farmbeats/accelerator-troubleshooting-1.png)
 
@@ -172,13 +176,13 @@ If you've already been granted access and are facing this error, try again by re
 
 **Message**: "Error: An unknown error occurred."
 
-**Corrective action**: This error occurs if you leave the page idle for too long. Refresh the page.  
-
-If the error persists, contact us with the error message / logs.
+**Corrective action**
+This error occurs if you leave the page idle for too long. Refresh the page. If the error persists, contact us with the error message/logs.
 
 **Issue**: FarmBeats Accelerator isn't showing the latest version, even after you've upgraded FarmBeatsDeployment.
 
-**Corrective action**: This error occurs because of service worker persistence in the browser. Do the following:
+**Corrective action**
+This error occurs because of service worker persistence in the browser. Do the following:
 
 1. Close all browser tabs that have Accelerator open, and close the browser window.
 2. Start a new instance of the browser, and reload the Accelerator URI. This action loads the new version of Accelerator.
@@ -189,30 +193,30 @@ If the error persists, contact us with the error message / logs.
 
 **Job failure message**: "Full authentication is required to access this resource."
 
-**Corrective action**:
+**Corrective action**: Do one of the following:
 
-Do one of the following:
+- Update FarmBeats with the correct username/password using the below steps and retry the job.
 
-- Update FarmBeats with the correct username / password using the steps below and retry the job.
+  **Update Sentinel username**
 
-    *Update Sentinel Username*
     1. Sign in to [Azure portal](https://portal.azure.com).
     2. In the **Search** box, search for the FarmBeats Datahub resource group.
-    3. Select Storage account storage***** -> Containers -> batch-prep-files -> to_vm -> config.ini
-    4. Click Edit
+    3. Select Storage account storage***** > **Containers** > **batch-prep-files** > **to_vm** > **config.ini**
+    4. Select **Edit**
     5. Update the username in the sentinel_account section
 
-    *Update Sentinel Password*
+  **Update Sentinel password**
+
     1. Sign in to [Azure portal](https://portal.azure.com).
     2. In the **Search** box, search for the FarmBeats Datahub resource group.
     3. Select keyvault-*****
     4. Select Access Policies under Settings
-    5. Click "Add Access Policy"
-    6. Use "Secret management" for Configure from Template and add yourself to Principal
-    7. Click Add, and then click Save on the Access Policies page
-    8. Click Secrets under Settings
-    9. Click Sentinel-password
-    10. Create a new version of the value and enable it
+    5. Select **Add Access Policy**
+    6. Use **Secret management** for Configure from Template and add yourself to Principal
+    7. Select **Add**, and then select **Save** on the **Access Policies** page
+    8. Select **Secrets** under **Settings**
+    9. Select **Sentinel-password**
+    10. Create a new version of the value and enable it.
 
 - Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check to see whether the job is successful.
 
@@ -223,8 +227,8 @@ Do one of the following:
 **Corrective action**:
 
 1. Open [Sentinel](https://scihub.copernicus.eu/dhus/) in your browser to see whether the website is accessible.
-2. If the website isn't accessible, check to see whether any firewall, company network, or other blocking software is preventing access to the website, and then take the necessary steps to allow the Sentinel URL. 
-3. Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check to see whether the job is successful.  
+2. If the website isn't accessible, check whether any firewall, company network, or other blocking software is preventing access to the website, and then take the necessary steps to allow the Sentinel URL. 
+3. Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check whether the job is successful.  
 
 ### Sentinel server: Down for maintenance
 
@@ -238,18 +242,17 @@ This issue can occur if any maintenance activities are being done on the Sentine
 
    For information about any planned or unplanned Sentinel maintenance activities, go to the [Copernicus Open Access Hub News](https://scihub.copernicus.eu/news/) site.  
 
-2. Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check to see whether the job is successful.
+2. Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check whether the job is successful.
 
 ### Sentinel: Maximum number of connections reached
 
 **Job failure message**: "Maximum number of two concurrent flows achieved by the user '\<username>'."
 
 **Meaning**: If a job fails because the maximum number of connections has been reached, the same Sentinel account is being used in multiple jobs.
 
-**Corrective action**:
-Try either of the following:
+**Corrective action**: Try either of the following:
 
-* Wait for the other jobs to finish before re-running failed job.
+* Wait for the other jobs to finish before re-running the failed job.
 * Create a new Sentinel account, and then update the Sentinel username and password in FarmBeats.
 
 ### Sentinel server: Refused connection
@@ -262,14 +265,15 @@ Try either of the following:
 
    For information about any planned or unplanned Sentinel maintenance activities, go to the [Copernicus Open Access Hub News](https://scihub.copernicus.eu/news/) site.  
 
-2. Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check to see whether the job is successful.
+2. Rerun the failed job, or run a satellite indices job for a date range of 5 to 7 days, and then check whether the job is successful.
 
 ### Soil Moisture map has white areas
 
-**Issue**: The Soil Moisture map was generated, but the map has mostly white areas.
+**Issue**: The **Soil Moisture map** was generated, but the map has mostly white areas.
 
 **Corrective action**: This issue can occur if the satellite indices generated for the time for which the map was requested has NDVI values that is less than 0.3. For more information, visit [Technical Guide from Sentinel](https://earth.esa.int/web/sentinel/technical-guides/sentinel-2-msi/level-2a/algorithm).
-1. Rerun the job for a different date range and check to see if the NDVI values in the satellite indices are more than 0.3
+
+1. Rerun the job for a different date range and check if the NDVI values in the satellite indices are more than 0.3.
 
 ## Collect logs manually
 
