Merge pull request #8244 from MicrosoftDocs/main

Auto push to live 2025-02-18 02:00:08

Author: Deland-Han

.openpublishing.redirection.developer.json

@@ -6254,6 +6254,10 @@
     {
       "source_path": "support/developer/webapps/iis/www-modules-features/add-remove-global-modules.md",
       "redirect_url": "/troubleshoot/developer/webapps/iis/www-administration-management/add-remove-global-modules"
+    },
+    {
+      "source_path": "support/mem/configmgr/update-management/error-0x800f0831-installing-update.md",
+      "redirect_url": "/troubleshoot/windows-server/installing-updates-features-roles/error-0x800f0831-installing-update"
     }
   ]
 }

support/dynamics-365/field-service/rso/locked-booking-infeasible.md

@@ -0,0 +1,44 @@
+---
+title: Locked Booking Is Infeasible in Resource Scheduling Optimization
+description: Resolves issues with booking locks in the Resource Scheduling Optimization add-in for Microsoft Dynamics 365 Field Service.
+ms.author: AnilMur
+author: anilmur
+ms.reviewer: mhart
+ms.date: 02/18/2025
+ms.custom: sap:Resource Scheduling Optimization
+---
+# Locked booking is infeasible in Resource Scheduling Optimization
+
+This article helps you resolve the "Locked booking is infeasible" error that occurs in the [Resource Scheduling Optimization add-in](/dynamics365/field-service/rso-overview) for Microsoft Dynamics 365 Field Service.
+
+## Symptoms
+
+When a [locked booking](/dynamics365/field-service/booking-lock-options) can't respect all defined constraints, the Resource Scheduling Optimization request continues but skips the identified resources that have violations. You might encounter the following error message:
+
+> System failed to optimize some records. Inner error(s): Locked booking is infeasible, reason: Violation. Tracing data points: RequirementId, RequirementName, BookingId, BookingName, ScheduledTimeWindow, FullTimeWindow, ArrivalTime, Lock Type
+
+## Cause
+
+The tracing data points in the error message can help you identify what went wrong. The violation types include:
+
+- Time window violations:
+
+  - The locked booking is outside of the resource's working hours.
+  - The promised time window is invalid.
+  - The travel time is invalid.
+  - The locked booking conflicts with a [scheduled break time](/dynamics365/field-service/set-up-bookable-resources#add-work-hours).
+
+- Eligibility check failures:
+
+  - **Meets Required Skills**. A locked booking has an invalid match to the [resource skill characteristics](/dynamics365/field-service/set-up-characteristics).
+  - **Meets Required Roles**. A locked booking has an invalid match to the [resource role](/training/modules/configure-bookable-resources-urs-dynamics-field-service/).
+  - **Meets Resource Preferences**. A locked booking has an invalid ["must choose from" or "restricted" resource](/dynamics365/field-service/resource-preferences).
+
+  For more information, see [Resource Scheduling Optimization constraints](/dynamics365/field-service/rso-optimization-goal#understand-constraints).
+
+## Resolution
+
+To solve the issue, update the booking settings, and then rerun Resource Scheduling Optimization:
+
+1. Adjust the settings to resolve the identified violation. For example, update the [booking lock options](/dynamics365/field-service/booking-lock-options#booking-lock-options) or adjust the [Resource Scheduling Optimization constraints](/dynamics365/field-service/rso-optimization-goal#understand-constraints).
+1. Save the changes and [run the Resource Scheduling Optimization process](/dynamics365/field-service/rso-run-optimization) again.

support/dynamics-365/field-service/toc.yml

@@ -63,6 +63,8 @@
 
 - name: Resource Scheduling Optimization add-in
   items: 
+    - name: Locked booking is infeasible
+      href: rso/locked-booking-infeasible.md
     - name: Optimization request fails to modify some bookings
       href: rso/system-failed-modify-bookings-error.md
     - name: '"Object reference not set to an instance of an object" error'

support/mem/configmgr/toc.yml

@@ -359,8 +359,6 @@ items:
           href: update-management/different-software-updates-results-displayed.md
         - name: Errors when servicing a server group
           href: update-management/errors-servicing-server-group.md
-        - name: Error 0x800f0831 installing updates
-          href: update-management/error-0x800f0831-installing-update.md
         - name: .NET Framework 4.7.2 updates fail to sync
           href: update-management/dotnet-framework-updates-fail-to-sync.md
     - name: State messaging

support/mem/configmgr/update-management/media/state-messaging-description/system-workflow.png

@@ -52,6 +52,9 @@ For more information about configuring Group Policy for WSUS clients, see [Confi
 
 ## Check for issues relating to BITS
 
+> [!NOTE]
+> [Windows Update Delivery Optimization](/windows/deployment/do/waas-delivery-optimization) allows clients to download updates from Microsoft Update or a WSUS server for Windows 10, Windows 11, and server operating systems newer than Windows Server 2016. For more information, see [common issues with Delivery Optimization](/windows/deployment/do/delivery-optimization-troubleshoot) and [a comprehensive list of all Delivery Optimization settings](/windows/deployment/do/waas-delivery-optimization-reference).
+
 Background Intelligent Transfer Service (BITS) is the service used by WSUS to download updates from Microsoft Update to the main WSUS server, and from WSUS servers to their clients. Some download issues may be caused by problems with BITS on the server or client computers. When you troubleshoot download problems, you should ensure that BITS is running properly on all affected computers.
 
 The BITS service must run under the **LocalSystem** account by default. To configure the service to run under the correct account, follow these steps:

support/mem/configmgr/update-management/troubleshoot-issues-with-wsus-client-agents.md

@@ -21,7 +21,7 @@ Before you start troubleshooting, it's best to verify that everything is configu
 
 - Verify that auto-enrollment is enabled for all users who will enroll the devices in Intune. For more information, see [Microsoft Entra ID and Microsoft Intune: Automatic MDM enrollment in the new Portal](/windows/client-management/mdm/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal).
 
-  :::image type="content" source="media/troubleshoot-windows-auto-enrollment/verify-auto-enrollment.png" alt-text="Screenshot shows options to verify auto-enrollment." lightbox="media/troubleshoot-windows-auto-enrollment/verify-auto-enrollment.png"::::::
+  :::image type="content" source="media/troubleshoot-windows-auto-enrollment/verify-auto-enrollment.png" alt-text="Screenshot shows options to verify auto-enrollment." lightbox="media/troubleshoot-windows-auto-enrollment/verify-auto-enrollment.png":::
 
   - Verify that **MDM user scope** is set to **All** to allow all users to enroll a device in Intune.
   - Verify that **MAM User scope** is set to **None**. Otherwise, this setting will have precedence over the MDM scope and cause issues.

support/mem/intune/device-enrollment/troubleshoot-windows-auto-enrollment.md

@@ -1,8 +1,8 @@
 ---
 title: Cannot establish connection to Access Database Engine OLE DB
 description: Provides a resolution for the issue that you can't establish a connection with database actions to Access Database Engine OLE DB in Power Automate for desktop.
-ms.reviewer: adija, pefelesk
-ms.date: 03/19/2024
+ms.reviewer: adija, pefelesk, iomavrid
+ms.date: 02/18/2025
 ms.custom: sap:Desktop flows\Power Automate for desktop errors
 ---
 # Can't establish a connection to Access Database Engine OLE DB
@@ -26,7 +26,7 @@ Consider the following scenario in Microsoft Power Automate for desktop:
 
 This error message occurs because the appropriate 64-bit driver isn't installed on your machine. Kindly note that Power Automate for desktop is based on 64-bit architecture and thus is only compatible to 64-bit database drivers.
 
-## Resolution
+## Workaround
 
 Verify that you have 64-bit Access Database driver installed on your machine by going to ODBC Data Source Administrator (64-bit) application on windows and then the **Drivers** tab. If you don't see "Microsoft Access Driver" in the list, you need to download and install the 64-bit version from [Microsoft Access Database Engine 2016 Redistributable](https://www.microsoft.com/download/details.aspx?id=54920).
 

support/power-platform/power-automate/desktop-flows/cannot-connect-access-database-engine-ole-db.md

@@ -0,0 +1,53 @@
+---
+title: Expression Couldn't be Evaluated Error When Using Encrypted Text
+description: Provides a resolution for the Expression couldn't be evaluated error when using direct encrypted text in Power Automate for desktop.
+ms.reviewer: iomavrid
+author: yiannismavridis
+ms.author: iomavrid
+ms.date: 02/18/2025
+ms.custom: sap:Desktop flows\Power Automate for desktop errors
+---
+# "Expression couldn't be evaluated" error when using encrypted text
+
+This article helps you resolve the "Expression couldn't be evaluated" error that occurs when you run a desktop flow with an action that uses direct input.
+
+_Applies to:_   Power Automate  
+
+## Symptoms
+
+A desktop flow with an action that uses direct input generates the following error when it's run on a machine different than the one where the flow was created:
+
+> Failed with error: Expression couldn't be evaluated
+
+For example,
+
+- The **Direct password input** option:
+
+  :::image type="content" source="media/error-expression-could-not-be-evaluated/direct-password-input.png" alt-text="Screenshot that shows the Direct password input option in a desktop flow action.":::
+
+- The **Direct encrypted text input** option:
+
+  :::image type="content" source="media/error-expression-could-not-be-evaluated/direct-encrypted-text-input.png" alt-text="Screenshot that shows the Direct encrypted text input option in a desktop flow action.":::
+
+## Cause
+
+The error occurs because direct inputs are encrypted using the local machine's [Data Protection API (DPAPI)](/dotnet/standard/security/how-to-use-data-protection) and can't be decrypted when the flow is run on another machine.
+
+This limitation is highlighted when you hover over the info icon if any of the direct input options is selected.
+
+:::image type="content" source="media/error-expression-could-not-be-evaluated/encrypted-tooltip.png" alt-text="Screenshot that shows the tooltip that provides additional information about the limitations of using direct encrypted text or password input.":::
+
+## Resolution
+
+To run the flow on a different machine, modify the flow to use [sensitive variables](/power-automate/desktop-flows/manage-variables#sensitive-variables/power-automate/desktop-flows/manage-variables#sensitive-variables).
+
+1. Open the desktop flow in Power Automate for desktop.
+1. Locate the action that uses direct password input or direct encrypted text input.
+1. Replace the direct input with a sensitive variable:
+   1. Select the **Password input as variable** or **Input as text, variable or expression** option to use a variable as a password input or text input.
+   1. Choose a variable that's marked as sensitive.
+1. Save the modified flow and test it on a different machine to ensure that the error is resolved.
+
+## More information
+
+[Use passwords in certain actions within desktop workflows](/power-automate/desktop-flows/how-to/use-passwords)