Merge branch 'main' into live

Author: Deland-Han

.openpublishing.redirection.json

@@ -5897,6 +5897,11 @@
       "redirect_url": "/troubleshoot/sql/database-engine/install/windows/sql-server-upgrade-failed-error-574",
       "redirect_document_id": true
     },
+    {
+      "source_path": "support/windows-server/identity/ldap-kerberos-server-reset-tcp-sessions.md",
+      "redirect_url": "/troubleshoot/windows-server/identity/ldap-kerberos-server-not-respond-udp-request-reset-tcp-sessions",
+      "redirect_document_id": true
+    },
     {
       "source_path": "support/azure/azure-functions/index.md",
       "redirect_url": "/troubleshoot/azure/azure-functions/welcome-azure-functions",

support/azure/active-directory/use-upn-matching-identity-sync.md

@@ -21,7 +21,7 @@ Sometimes you may have to transfer the source of authority for a user account if
 - Azure Management Portal
 - Intune portal
 
-You can transfer the source of authority，so the account can be managed through your local directory service when using identity synchronization with Azure Active Directory (Azure AD).
+You can transfer the source of authority, so the account can be managed through your local directory service when using identity synchronization with Azure Active Directory (Azure AD).
 
 This article discusses how to perform the transfer by using a process known as **UPN matching**. This process uses the user principal name (UPN) to match the on-premises user account to a work or school account in Azure AD.
 

support/azure/virtual-machines/unlock-encrypted-linux-disk-offline-repair.md

@@ -138,7 +138,7 @@ To unlock and mount the encrypted disk manually, follow these steps:
 
 ### Unmount any mounted partitions on the encrypted disk
 
-1. After the repair VM is created, SSH to your repair VM, log in by using the appropriate credentials，and then elevate the account to root:
+1. After the repair VM is created, SSH to your repair VM, log in by using the appropriate credentials, and then elevate the account to root:
 
    ```bash
    sudo -s 

support/developer/browsers/administration/check-ie-version.md

@@ -23,7 +23,7 @@ You can use the following methods:
 The first method is easy but includes many efforts. You can navigate to the following location in the registry after connecting to the remote registry:  
 `HKLM\Software\Microsoft\Internet Explorer`
 
-The above registry includes the values in right pane， which resembles the following:  
+The above registry includes the values in right pane,  which resembles the following:  
 svcVersion     REG_SZ    11.778.18362.0
 
 ## Check settings on remote computer

support/developer/browsers/connectivity-navigation/use-proxy-servers-with-ie.md

@@ -72,7 +72,7 @@ To bypass servers, use an asterisk ("*") as a wildcard to replace actual charact
 
 - Enter a wildcard in the middle of an Internet address, IP address, or domain name that has a common beginning and ending. For example, the entry **www.*.com** matches any entry that starts as **www** and ends as **com**.
 
-- Enter a wildcard at the end of an Internet address, IP address, or domain name that has a common beginning. For example, use **www.microsoft.*** to bypass any entries that begin as **www.microsoft.**，such as `www.microsoft.com`, `www.microsoft.org`, but not `www.microsoftcorporation.com`.
+- Enter a wildcard at the end of an Internet address, IP address, or domain name that has a common beginning. For example, use **www.microsoft.*** to bypass any entries that begin as **www.microsoft.**, such as `www.microsoft.com`, `www.microsoft.org`, but not `www.microsoftcorporation.com`.
 
 To bypass addresses that have similar patterns, use multiple wildcards. For example, use 123.1*.66.* to bypass addresses such as 123.144.66.12, 123.133.66.15, and 123.187.66.13.
 

support/dynamics-365/sales/media/troubleshoot-forecast-issues/permission.png

@@ -3,18 +3,17 @@ title: Troubleshoot issues with forecasting
 description: Provides resolutions for the known issues that are related to forecasting in Dynamics 365 Sales.
 author: sbmjais
 ms.author: shjais
-ms.topic: troubleshooting
-ms.date: 02/28/2022
+ms.reviewer: ladirohit 
+ms.date: 09/06/2023
 ms.subservice: d365-sales-sales
 ---
-
 # Troubleshoot issues with forecasting
 
-This article helps you troubleshoot and resolve issues related to forecasting.
+This article helps you troubleshoot and resolve issues related to forecasting in Microsoft Dynamics 365 Sales.
 
 ## Issue 1 - An error is displayed when you try to create a territory-based forecast
 
-### Symptom
+### Symptoms
 
 When you try to create a territory-based forecast, an error is displayed. Also, the data in a territory-based forecast might not be refreshed.
 
@@ -149,20 +148,125 @@ To resolve this error, your administrator must provide read privileges on **Fore
 
 ### Cause
 
-In a forecast, after updating the forecast category field to Won or Lost, the opportunities are still appearing in the previous pipeline bucket. This error is occurring due to the **Opportunity Forecast Category Mapping Process** workflow is disabled in your organization.
+In a forecast, after updating the forecast category field to **Won** or **Lost**, the opportunities still appear in the previous pipeline bucket. This error occurs because the **Opportunity Forecast Category Mapping Process** workflow is disabled in your organization.
 
 ### Resolution
 
 To resolve the error, activate the **Opportunity Forecast Category Mapping Process** workflow. Follow these steps:
 
 1. Go to **Advanced settings**, and then select **Settings** > **Customizations** > **Customize the System**.
-2. From the sitemap, select **Processes**.
-3. Select the **Opportunity Forecast Category Mapping Process** workflow and select **Activate**.
+1. In the sitemap, select **Processes**.
+1. Select the **Opportunity Forecast Category Mapping Process** workflow and then select **Activate**.
+
+   :::image type="content" source="media/troubleshoot-forecast-issues/activate-opportunity-forecast-category-process.png" alt-text="Activate the Opportunity Forecast Category Mapping Process workflow.":::
+
+    The forecast categories in the opportunities will be updated properly. The opportunities that were changed before activating the workflow must be manually changed. Also, open the **Opportunity Forecast Category Mapping Process** workflow and verify that the conditions are properly defined for each forecast category.
+
+   :::image type="content" source="media/troubleshoot-forecast-issues/opportunity-forecast-category-process-conditions.png" alt-text="The Opportunity Forecast Category Mapping Process workflow conditions.":::
+
+1. Save and close the settings.
+
+## Issue 7 - Can't activate a forecast that has a hierarchy-related column of lookup type
+
+### Cause
+
+This issue occurs because the "Dynamics 365 Sales Forecasting" user doesn't have the read permission to the hierarchy-related lookup entity.
+
+### Resolution
+
+To solve the issue, follow the steps:
+
+1. Go to **Advanced settings**, and select **Settings** > **System** > **Security** > **Security roles**.
+
+1. Open the **Forecast AppUser** role and select the tab where the entity type is present.
+
+   :::image type="content" source="media/troubleshoot-forecast-issues/set-up-read-permission.png" alt-text="Screenshot that shows the the Forecast App User role.":::
+
+1. Enable the **Read** permission at the organization level for the lookup field's entity type.
+1. Save the changes.
+
+## Issue 8 - Can't activate a forecast
+
+### Cause
+
+The forecast activation fails due to multiple reasons.
+
+### Resolution
+
+To solve the issue, follow the steps:
+
+1. Ensure that you have done all the mandatory configurations for your forecast model.
+1. Ensure that hierarchy filters in the forecast configuration don't filter out the entire hierarchy. Go to the **Preview** section in the **General** step to ensure that the hierarchy exists. For more information, see [Add additional filters to a forecast](/dynamics365/sales/add-additional-filters).
+
+## Issue 9 - Can't find the forecast configuration option in App Settings
+
+### Cause
+
+The forecast configuration option might not be visible in the App Settings of the Sales Hub app due to the following reasons:
+
+- You don't have the read permission to the forecast configuration entity.
+- Your administrator didn't manually [add the forecast grid and configuration](/dynamics365/sales/add-forecast-site-map#add-forecast-grid-and-forecast-configuration-options-to-sitemap) under the **Performance Management** section.
+
+### Resolution
+
+To solve the issue, follow these steps:
 
-    :::image type="content" source="media/troubleshoot-forecast-issues/activate-opportunity-forecast-category-process.png" alt-text="Activate the Opportunity Forecast Category Mapping Process workflow.":::
+1. Assign the Forecast Manager security role to the user who should be able to create and manage forecast configurations.
+1. In **Forecast configuration**, the forecast navigation pane items must be added in a custom app.
 
-    The forecast categories in the opportunities will be updated properly. For opportunities that were changed before activating the workflow must be manually changed. Also, open the **Opportunity Forecast Category Mapping Process** workflow and verify that the conditions are properly defined for each forecast category.
+## Issue 10 - Can't view forecasts for user hierarchy
 
-    :::image type="content" source="media/troubleshoot-forecast-issues/opportunity-forecast-category-process-conditions.png" alt-text="The Opportunity Forecast Category Mapping Process workflow conditions.":::
+### Cause
+
+This issue occurs due to insufficient permissions to view the forecast.
+
+### Resolution
+
+To solve the issue, make sure that:
+
+1. One of these conditions is satisfied:
+
+   - You're the owner of the forecast. The **Owner lookup field** in the **Permissions** step of the forecast configuration shows who the owner is.
+
+      :::image type="content" source="media/troubleshoot-forecast-issues/permission.png" alt-text="Screenshot that shows the Permissions step of the forecast configuration.":::
+
+   - You're part of the security roles that have the read permission, as configured in the **Permissions** step of the forecast configuration.
+   - Someone has shared the forecast with you. For more information, see [Enable or disable forecast sharing](/dynamics365/sales/provide-permissions-forecast).
+
+1. The **Owner lookup field** in the **Permissions** step of the forecast configuration isn't set to **None**. If it's set to **None**, no one can view the forecast.
+
+## Issue 11 - Forecast field values show zero or blank in the forecast grid
+
+### Cause
+
+The fields in the rollup entity have field-level security.
+
+### Resolution
+
+To solve the issue, you need to provide the read permission to the Dynamics 365 Sales Forecasting user in the field security profiles. Otherwise, the column will show **0** to all users except system administrators. Follow these steps to configure the field security profiles:
+
+1. Go to **Settings**> **Security** > **Field Security Profiles**.
+1. Select an existing profile or create a new one.
+1. Select **Users** or **Teams** to add the users or teams that you want to grant access to the secure fields.
+1. Select **Field Permissions** to set the permissions for each field. You can select **Read**, **Create**, or **Update**, or a combination of them.
+1. Save and close the profile.
+
+## Issue 12 - Can't manually recalculate the prediction column on the Forecasts page
+
+### Cause
+
+The prediction column on the **Forecasts** page can't be [manually recalculated](/dynamics365/sales/keep-forecast-data-up-to-date#recalculate-and-refresh-forecast-data-manually).
+
+### Resolution
+
+The prediction column in the Forecast is automatically recalculated after every seven days, and it doesn't support manual recalculation. This is because predictions are based on AI-driven models that look at historical data and the open sales pipeline to predict future revenue outcome. The prediction column shows the predicted revenue for each seller and manager based on the **Status** field of an opportunity. To optimize the accuracy of the predictions, ensure the **Forecast Category** values are kept in sync with the **Status** field. For the out-of-the-box forecast category, a workflow ensures that when an opportunity is closed as **Won** or **Lost**, the forecast category is updated with the proper value.
+
+## Issue 13 - Forecast underlying grid view is disabled (read-only) when the page is loading
+
+### Cause
+
+A [custom JavaScript configured in the forecast configuration](/dynamics365/sales/forecast-configure-advanced-settings#upload-the-javascript-library-to-your-forecast) prevents the grid from being editable.
+
+### Resolution
 
-4. Save and close the settings.
+To solve the issue, review the custom JavaScript code and check if it disables the underlying records grid view.

support/dynamics-365/sales/media/troubleshoot-forecast-issues/set-up-read-permission.png

@@ -8,7 +8,7 @@ ms.reviewer: kaushika
 
 This article provides a solution for the Configuration Manager Database Replication Service (DRS) performance issues that occur after you install hotfix [3125525](https://support.microsoft.com/help/3125525).
 
-_Original product version:_   Configuration Manager (current branch), Microsoft System Center 2012 R2 Configuration Manager， Microsoft System Center 2012 Configuration Manager  
+_Original product version:_   Configuration Manager (current branch), Microsoft System Center 2012 R2 Configuration Manager,  Microsoft System Center 2012 Configuration Manager  
 _Original KB number:_   4024301
 
 ## Symptom

support/dynamics-365/sales/troubleshoot-forecast-issues.md

@@ -3,7 +3,7 @@ title: Error may occur when setting the SQL Server Agent job history log
 description: Fixes an error that occurs when setting or changing the maximum number of job history log rows and job history rows per job.
 ms.date: 04/13/2023
 ms.custom: KB5024352
-ms.reviewer: derekw, pcaronauger，v-qianli2
+ms.reviewer: derekw, pcaronauger, v-qianli2
 appliesto:
 - SQL Server 2022 on Linux
 - SQL Server 2019 on Linux