Failed to install package 'Test.helpdesk.Invoices.1.0.4'

Hello guys, i’m trying to run a process on Orchestrator, but i’m getting the following error:

Failed to install package ‘Test.helpdesk.Invoices.1.0.4’

RemoteException wrapping System.Exception: Failed to install package ‘Test.helpdesk.Invoices.1.0.4’ —> RemoteException wrapping System.Exception: NU1202: Package Test.helpdesk.Invoices 1.0.4 is not compatible with net6.0-windows7.0 (.NETCoreApp,Version=v6.0). Package Test.helpdesk.Invoices 1.0.4 supports: net8.0-windows7.0 (.NETCoreApp,Version=v8.0)

NU1202: Package Test.helpdesk.Invoices 1.0.4 is not compatible with net6.0-windows7.0 (.NETCoreApp,Version=v6.0) / win10-x64. Package Test.helpdesk.Invoices 1.0.4 supports: net8.0-windows7.0 (.NETCoreApp,Version=v8.0)

— End of inner exception stack trace —

at UiPath.Service.Core.ProjectInstaller.InstallCore(InstallProjectCommand installCommand)

at UiPath.Service.Core.NetWindowsProjectInstaller.InstallCore(InstallProjectCommand installCommand)

at UiPath.Service.Core.Telemetry.RobotTelemetryExtensions.WithTelemetry[TResult](IRobotTelemetryClient container, Func1 internalFunc, RobotTelemetryOperationBase telemetryOperation, Action1 telemetryArgsFunc)

at UiPath.Service.Core.ProjectInstaller.InstallWithTelemetry(InstallProjectCommand installCommand)

at UiPath.Service.Core.ProjectInstaller.<>c__DisplayClass5_0.<b__0>d.MoveNext()

— End of stack trace from previous location —

at UiPath.Service.Core.ProjectInstaller.Install(InstallProjectCommand installCommand)

at UiPath.Service.Core.PackageService.InstallProcess(PublishedProcess process, ImpersonableIdentity identity, IRobot robot, CancellationToken ct)

at UiPath.Service.Job.InstallPackage(ImpersonableIdentity identity, CancellationToken ct)

at UiPath.Service.Job.PrepareForExecution(ImpersonableIdentity identity, CancellationToken ct)

at UiPath.Service.Job.UiPath.Service.Core.IExecutorEvents.ExecutorAvailable(ImpersonableIdentity identity, CancellationToken ct)

at UiPath.Service.Core.ExecutorService.Available(AvailableMessage availableMessage)

at UiPath.CoreIpc.Server.<>c__DisplayClass7_3.<<-ctor>g__InvokeMethod|6>d.MoveNext()

— End of stack trace from previous location —

at UiPath.CoreIpc.Server.<>c__DisplayClass7_1.<<-ctor>g__HandleRequest|3>d.MoveNext()

— End of stack trace from previous location —

at UiPath.CoreIpc.Server.<>c__DisplayClass7_2.<<-ctor>b__5>d.MoveNext()

— End of stack trace from previous location —

at UiPath.CoreIpc.Helpers.Timeout[TResult](TimeSpan timeout, List1 cancellationTokens, Func2 func, String message, Func`2 exceptionHandler)

Can anyone please help me?
Thank you in advance

1 Like

@rafael01.carvalho,

This is the issue.

Package Test.helpdesk.Invoices 1.0.4 is not compatible with net6.0-windows7.0 (.NETCoreApp,Version=v6.0) / win10-x64. Package Test.helpdesk.Invoices 1.0.4 supports: net8.0-windows7.0 (.NETCoreApp,Version=v8.0)

Your package is developed on higher version than supported by your robot version.

Update your robot version to compatible version of Studio.

Thanks,
Ashok :slightly_smiling_face:

@rafael01.carvalho,

Before the first approach I suggested, try this.

Install this .Net 8.0.8 Desktop Runtime.

Once done, try triggering the bot again. If this doesn’t work then upgrade the bot also along with this .Net runtime.

@ashokkarale where do i upgrade the .NET version?

On the robot machine where the package is not being deployed.

Is there any way that i can create a project with the .net 6.0?
I have the UiPath Studio V2024.10.1 Enterprise Edition

@rafael01.carvalho,

The .Net version depends on the UiPath Studio version.

Though I’m still looking for more concrete documentation for which Studio version results in which .net version.

I will update here once find out.

Ok thank you very much

@rafael01.carvalho

  1. Is the project created with windows compatibility?
  2. what is this test.helpdesk? is it a custom package youd eveloped
  3. is that package published to orchetsrator?

cheers

1 - Yes, it’s windows compatible
2 - The test.helpdesk is the name of the project
3 - Yes, it’s published on Orchestrator