Hi Team, I get an error installing UIpath Orchestrator because “an unexpected error occurred”. I get this error when I run the bot: – Exception in Promax workflow: System.ArgumentException: The path has no legal form. for UiPath.Excel.WorkbookApplication.Initialize(WorkbookArguments args, Boolean onlyIfWorkbookExists) to UiPath.Excel.WorkbookApplication.Initialize(Application excelApp, WorkbookArguments args, Boolean onlyIfWorkbookExists) to UiPath.Excel.Activities.ExcelApplicationScope.c.b__48_0(WorkbookArguments args) to UiPath.Excel.Activities.ExcelApplicationScope.Execute(Native ActivityContext context) to System.Activities.NativeActivity.InternalExecute( ActivityInstance instance, ActivityExecutor-Executor, BookmarkManager bookmarkManager) to System.Activities.ActivityInstance.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager) to System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) I have already changed the Gmail settings as (Enable access) and IMAP access is also enabled. Also, I use Google Chrome and Uipath as admin privileges, but I still can`t fix this. Please specify Please check the number of characters in the source path. For example, it might be C:hsdfdjkbvsdfjkdsbdjfsd. Reduce this to fewer characters and that should solve the problem. I was able to solve it for a specific application for the error “the path is not of a legal form” by flattening the full path. Infolog for task call XXXXXXXXXXXXXXX (52567288272) System.ArgumentException: The path has no legal form. to System.IO.Path.NormalizePath(string path, boolean fullCheck, Int32 maxPathLength, boolean expandShortPaths) to System.IO.DirectoryInfo.Init(string path, checkHost boolean) to Dynamics.Ax.Application.XXXClass.Run() in XXXClass.run.xpp:Line 24 to Dynamics.Ax.Application.BatchRun.runJobStaticCode(Int64 batchId) in BatchRun.runJobStaticCode.xpp:Line 54 to Dynamics.Ax.Application.BatchRun.runJobStatic(Int64 batchId) in BatchRun.runJobStatic.xpp:Line 13 to BatchRun: runJobStatic( Object[] ) to Microsoft.Dynamics.Ax.Xpp.ReflectionCallHelper.MakeStaticCall(Type type, String MethodName, Object[] parameters) to BatchIL.taskThreadEntry(Object threadArg)When I run the class from AOT, there is no error. However, when I run it from the batch job above, it is.

Line 24 of the Run() method is highlighted in red, as shown below: edit: Maybe there`s something inconsistent or unstable in your local repository, I don`t know. I think more information is needed, such as the output of a Git command, the name/size of the local repository, how slow it is when reading repository content, etc. It is difficult to solve your problem with the current information. The problem was that there was a tab character (t) in one of the history paths. After removal, the program works correctly again. I get it every time I try to create a new project with the extension. Occurs with any variation of the project path. Judging by the stack trace, this is an error when copying NuGet files in the UiPathActivityCreator wizard directoryInfo = new System.IO.DirectoryInfo(this.parmSourceFilePath()); →ã”this. parmSourceFilePath()” sets the path to “D:CSVProcessingItemMaster” Can you log on as the AOS service account and then run the AOT class? There may be a more informative error message. The exception occurs while processing a Telerik report that contains a resource specified by the file path, for example =`C:PicturesMyImage.png.` is used as the PictureBox.Value property. When you call the class, add the path parameters in the new() method.

I wouldn`t call it a final solution, there are more and more surprises in the box. However, after one of the previous posts, I checked all the references of all the projects in the solution, and found and removed a few broken links. This helped somewhat, but a few caveats remained, including the message “The way has no legal form.” I then checked the properties of the main app, the Publish tab, and then the app files. The list looked good. Then, I discovered a small “Show all files” checkbox in the dialog box. Only this revealed a referenced library that was no longer there (it was a reference to the Excel Interop library, which no longer existed and that I no longer used in my code). After removing the broken links and restarting Visual Studio, all the problems were gone. Be aware that designer issues are not necessarily related to the form you`re trying to open. An exception occurred while processing pictureBox: System.InvalidOperationException: Invalid image data.

—> System.ArgumentException: The path has no legal form.