How to Fix Bad IL Format error while publishing document understanding project

Hi Team,

I have created the Document Understanding process using the Document understanding template in UiPath studio. When i publish this process i get the error message as shown below while loading dependencies. Its reporting error for in total 18 files

Bad IL format. The format of the file .nuget\packages\UiPath.cefsharpbundle.netcore\1.9.0\lib/net6.0-windows7.0/Ijwhost.dll’ is invalid.

Bad IL format. The format of the file .nuget\packages\UiPath.emgucvbundle\1.1.0\lib/net5.0/concrt140.dll is invalid.

It still goes ahead with package creation and creates the package.

I have tried updating the dependencies to the latest available version but still the same issue
image

Please suggest how to resolve this issue

1 Like

Hello @Benajir_Khan1

Do you get this error when you try to debug or validate the project in Studio?

Does it only happen when you try to publish to Orchestrator?

Thanks
Lahiru

The project shows some compilation errors that appear when it is built, but disappear when it is debugged or run. The errors also show up when the process is published to orchestrator during loading dependencies, but the package is still created and can be executed in both attended and unattended mode. I am not sure if these errors will affect the document understanding process in any way .
Thus checking here if if there is any solution of this problem

Hello @Benajir_Khan1

I have seen this happening too… So far I have not seen any impact on the process execution. Probably this is something internal.

Thanks
Lahiru

Did anyone get a resolution to this? I am getting the same issue but won’t publish to orchestrator for me. Project works within studio fully.

2 Likes

I have a bot that uses Excel, System and UiAutomation packages. That’s it. Still I get this error: Bad IL format. The format of the file ‘C:\Users\surya.avantsa.nuget\packages\UiPath.emgucvbundle\1.1.0\lib/net5.0/msvcp140_atomic_wait.dll’ is invalid. C:\Users\surya.avantsa.nuget\packages\UiPath.emgucvbundle\1.1.0\lib/net5.0/msvcp140_atomic_wait.dll

I see these when I run, debug or publish. Not when I analyze the project or this file.

Hey, did you solve this error?

It shows the error initially but at the end it compiles and publishes correctly.

Thanks for the follow up.

I get the same error and it will publish but then it fails from orchestrator unattended… it will however run locally

This issue is still in studio 24.10.1 for windows projects & libraries. VB or C# doesn’t seem to make a diffference, but I don’t get this compile error in windows-legacy or cross-platform projects.

It’s not preventing me from publishing or running the code, but it’s annoying to see those see those red compile errors which you can’t do anything about. Please fix!

I did try locally removing the package so studio could redownload it, but that didn’t help either.

Exact same situation for me. So far it does not appear to impact process execution, but it is annoying (and disconcerting).

I also run into the same thing.

I tried to reinstall the UIAutomation.Activities which point to the EmguCVBundle:
image
But that doesn’t solve it.

I also found out that the folder “UiPath.emgucvbundle” isn’t installed when you install UIAutomation.Activities:

The error message still occurs after installing the EmguCVBundle package:
image
After installing the bundle I still can’t find the folder “UiPath.emgucvbundle”.

I agree that, however the workflows run normally (attended as wel as unattended) it’s really annoying seeing the red lines go by when compiling. Also when something else goes wrong you won’t notice it because you think it’s the same old red lines.

Hope this gets looked into by a developer.

Thanx in advance

Cause:

These “Bad IL Format” errors are not affecting the project execution or compilation.

These are false errors. They can be ignored in the generated logs (execution and Event Viewer logs). In the higher Studio versions they will set as warnings or removed completely. Until then, you need to ignore them.

Solution:

Ignore for now the “Bad IL Format” false errors for various dll files in your project compilation/execution.

Test the behavior in Studio 23.10.9 using this link https://download.uipath.com/versions/23.10.9/UiPathStudio.msi and https://download.uipath.com/versions/24.10.6/UiPathStudio.msi (in these versions those false errors should be treated as Warnings instead of errors)

References for “Studio logged Bad IL format compilation errors when running some projects containing libraries migrated from Windows - Legacy. These errors did not affect project execution.”:

1 Like