UiPath Legacy automation

Help Studio
1

Hi Everyone

I received a pop-up notification for a UiPath update. After updating my UiPath, I found that I was unable to use my old legacy automations. I then received another pop-up suggesting I convert the automation to Windows format. Although I proceeded with the conversion, the automation still isn’t functioning properly. When I attempt to run the old legacy automation, I encounter an error message. Can anyone provide assistance on how I can get this legacy automation working again?

Regards
Naman

A UiPath error message indicates that execution cannot start because JIT compilation is disabled for non-Legacy projects. (Captioned by AI)
A UiPath error message indicates that execution cannot start because JIT compilation is disabled for non-Legacy projects. (Captioned by AI)1115×631 115 KB

2

@Naman_Arora,

Can you try upgrading the system package like this and try.

3

UiPath have been asking you to update from Legacy for quite a long time now informing that the legacy support would be removed, so you did have plenty of opportunity to do this before it was forced upon you.

If you want to use Legacy as you say, you need to downgrade to a lower version of studio rather than using the Community version.

4

Sure @ashokkarale I’ll try this & update you.

thanks for your response.

5

@Naman_Arora ,

Can you please share the legacy project with me via DM?

Thank you

6

Hi @ashokkarale

I have tried this but I’m still not able to run legacy automation.

regards
Naman

7

@Alexandru_Bizon

Hi Alex

That’s a official automation, Cannot share here. I can share the errors screenshots, Would you be able to assist me ?

Regards
Naman

1 Like
8

In that case, it would be very helpful if you could:

  • make a copy of the project folder
  • when working with the project copy:
    • start deleting the activities in your project “from the end” and try to run it each time
    • if it works at one point, it means that the last deleted activity and or its configuration is what is causing this issue;
    • please share the full configuration of that activity with us
9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.

10

The issue is caused by the difference between "(U+0022) and “(U+201C) and their Unicode encoding. .NET 8 emphasizes strict compliance while legacy .NET frameworks, were more permissive.

The workaround is to replace “(U+201C) with "(U+0022).