Could not load file or assembly '(Process Name) Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified

Help Orchestrator
,
1

Hi All,

I have updated my existing project from Legacy to Windows and published using DevOps
and when start running same process it is throwing below error.

image
image671×920 82.9 KB

Gone through same topics here but did not find any proper solution to this
@loginerror @Palaniyappan @balupad14 @Pablito @cheppalli_naga_abhishek @ThomasStocker @lukas.grabmeir

2

Hi @prashantP

Please update all the packages in the manage packages to the latest version and make sure to keep the Runtime Rule as Lowest Applicable Version and the issue will be resolved.

image
image430×637 21 KB

Do the above process for all the packages that are installed for that project.

Regards

3

Hi @prashantP

Update the UiPath Tasks to version 4 and before UiPath Pack Task, add UiPath Install Plataform choose a Windows CLI

image
image1577×635 36.1 KB

Cheers

4

Hi @rikulsilva

Thanks for the reply.

could you please let me know this is due to legacy to windows conversion of project or due to version not updated in DevOps task ?

Thanks

5

Hi @prashantP

Confirm that the assembly file mentioned in the error message is present in the specified location.

You can follow the steps accordingly :

  1. Open the File Explorer application on your Windows machine.
  2. Navigate to the directory where the assembly file is expected to be located(Could be a specific folder).
  3. In the appropriaye directory, use the search box at the top right corner of the File Explorer window to search for the assembly file by its name. Enter the name of the assembly file (including the file extension, such as “.dll”) in the search box.
  4. If the file appears in the search results, it indicates that the assembly file exists in the specified location.
    5.Right-click on the assembly file and select “Properties” from the context menu. In the Properties window, you can check details such as the file size, creation date, and modification date.
6

Hi @prashantP

It’s due the project compatibility. The Windows one needs a Windows CLI. When you publish your project from Studio it does automatically

7

Hi @prashantP

Did you solve this issue yet? Because we had the same issue earlier and we updated the UiPath version (UiPath Install Platform and UiPath Pack) from 3.* to 4.* and used the Windows CLI (ver.23.6.8581.1968) and it works.

Best regards

John

8

Hi,

I have the same problem, did you solve it?

9

First of all the troublesshooting should be started from the CLI build logs. There you need to check if you have any errors. Maybe some dependencies were not retrieved by the build agent.

Some older CLI versions could not obtain the dependencies from Orchestrator. Reference: Automation Ops - UiPath CLI Release Notes

The CLI version should match the version of the Studio that compiled and created the project.

For example:

  • The project which was built in Studio 22.10.x, needs to be packed and published with a CLI from 22.10.x
  • The project which was built in Studio 23.4.x, needs to be packed and published with a CLI from 23.4.x
  • The project which was built in Studio 23.10.x, needs to be packed and published with a CLI from 23.10.x

Not all the CLI versions are compatible with the Orchestrator. Reference: Automation Ops - UiPath CLI

If you packed and deployed the project with a CLI 23.6.x or 23.10.x it will allow you to run only in 2023.10.x robots and up.

10

Hi rikusilva,

Can you show me where to find that interface to change that windows CLI?

thanks.

11

I just re-installed the studio and it worked fine for me, since i tried with very basic process just to display message , in that also i was getting same error hence i re-installed studio and it worked fine for me.