# Troubleshooting UiPath CLI

> If you run into issues while using the UiPath CLI, consider the following troubleshooting scenarios.

If you run into issues while using the UiPath CLI, consider the following troubleshooting scenarios.

## Issues related to the `.NET` version

### Description

You may encounter issues with UiPath CLI tasks and pipeline operations if the correct version of the `.NET` framework is not installed (or missing) on your system.

When this issue occurs, you may come across error messages such as:

* ```text
  You must install or update .NET to run this application.
  App: C:\Program Files (x86)\UiPath CLI\UiPath.CLI.Windows.23.10.8894.39673\tools\uipcli.exe
  Architecture: x64
  Framework: 'Microsoft.NETCore.App', version '6.0.0' (x64)
  .NET location: C:\Program Files\dotnet
  The following frameworks were found:
  8.0.5 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  8.0.8 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  ```
* ```text
  An error occurred trying to start process 'dotnet' with working directory 'C:\Users\Public\UiPathDevOpsScripts\uipathcli-23.10\tools'. The system cannot find the file specified. Failed to run the command. UiPath.CommandLine.Exceptions.CommandException: Packaging failed due to one or more errors.
  Message: An error occurred trying to start process 'dotnet' with working directory 'C:\Users\Public\UiPathDevOpsScripts\uipathcli-23.10\tools'. The system cannot find the file specified.
  Error at: System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
  ```

### Remedy

You must ensure that you have the correct `.NET` version installed.

For the CLI and `.NET` version compatibility matrix, refer to the [Prerequisites](https://docs.uipath.com/cicd-integrations/standalone/2024.10/user-guide/about-uipath-cli) section.

## Issues related to special character in connection string passwords

In most instances, connection passwords are encapsulated within a single quotation mark ('). However, when the password includes
special characters such as `` ` `` or `$`, a different approach is required.

In these cases, the password must be formatted as `` \`"<password>\`" ``, replacing `<password>` with the actual password. Moreover, you must also adhere to the escape rules as detailed in the following table:

| **Original format in ADUC** | **Escaped format in PowerShell string** |
| --- | --- |
| `cn=James $ Smith` | `` "cn=James `$ Smith" `` |
| `cn=Sally Wilson + Jones` | `"cn=Sally Wilson \+ Jones"` |
| `cn=William O'Brian` | `"cn=William O'Brian"` |
| `` cn=William O`Brian `` | ``` "cn=William O``Brian" ``` |
| `cn=Richard #West` | `"cn=Richard #West"` |
| `cn=Roy Johnson$` | `"cn=Roy Johnson$"` |

### Example

Assume that the original password is `7'8:<=XMe$y[@vC?_4ZeY8c-~y'W!1dU4gnczuf'/p>j```j<I\`" ````.