Where do you configure UI Path mobile automation mdmlog?


The log is trying to be created under the wrong user in Windows 10 platform. The bot is trying to create a log under different user when it is logged in as a another user. This causes access denied issue. How is that even possible? Where do we configure the log path. How did it take the other user’s log path?

Here are some possible reasons and explanations for the behavior you described:

  1. User Context: When a bot runs in UiPath or any other automation tool, it operates within the context of the user account under which it is executed. If the bot is running under a different user account, it will inherit that user’s permissions and settings, which could lead to issues if the target log path requires different access rights.
  2. Environment Variables: The log path may be configured using environment variables that differ between user accounts. Environment variables like %USERPROFILE% or %APPDATA% can lead to different paths based on the user context.
  3. Configuration Settings: The log path might be specified in a configuration file or setting that is user-specific, and the bot may be reading those settings, which leads to accessing a different log path for each user.
  4. Hard-Coded Paths: If the log path is hard-coded in the bot’s code or configuration, it will always use the same path regardless of the user context.
  5. Permissions: The bot might be trying to create logs in a location that requires administrative or elevated permissions, which are not available under the current user context.

To address this issue, you can follow these steps:

  1. Check Log Path Configuration: Review your bot’s code and configuration to ensure that the log path is defined correctly and is not relying on environment variables or user-specific settings.
  2. Use Relative Paths: Whenever possible, use relative paths for log files instead of absolute paths. Relative paths are relative to the bot’s execution directory and are not dependent on specific user settings.
  3. Verify User Context: Ensure that the bot is running under the correct user account with the necessary permissions to create logs in the specified location.
  4. Use Appropriate Permissions: If the log path requires elevated permissions, consider adjusting the permissions on the log directory to allow the bot to write logs without administrative privileges.
  5. Test on Different Accounts: Test your bot on different user accounts to identify any issues related to user-specific settings and permissions.