Unable to load dependencies whllapi.dll file in uipath windows studio 2022.10.3

Help Studio
1

UiPath windows studio not accepting qws3270 dll files in the .net 6.

Kindly provide any suggestions…

2

@Chillaxkrish,

What’s the error?

Thanks,
Ashok :slight_smile:

3

Invoke Method: Unable to load DLL ‘whllapi.dll’ or one of its dependencies: The specified module could not be found. (0x8007007E)

Above is the error message from UiPath…

I’m using .net 6 project added dependencies whllapi for the automation qws3270 emulator… Using C# script

4

I’d be glad to assist you with the “Unable to load DLL ‘whllapi.dll’ or one of its dependencies” error you’re encountering in UiPath Studio when using a .NET 6 project with the whllapi.dll dependency for QWS/3270 automation.

Understanding the Error:

This error typically indicates that UiPath cannot locate the necessary whllapi.dll file or one of its dependent DLLs at runtime. It’s crucial to ensure these files are correctly placed and referenced in your project.

Resolving the Issue:

Here are several steps to troubleshoot and fix the issue:

  1. Verify File Location:

    • Double-check the installation path of the QWS/3270 emulator. The whllapi.dll file is likely located within this directory. Common installation locations include:
      • C:\Program Files (x86)\IBM\Client Access\Emulator (32-bit system)
      • C:\Program Files\IBM\Client Access\Emulator (64-bit system)

  2. Copy DLLs to Project Folder (if applicable):

    • In some cases, you might need to manually copy whllapi.dll and any required dependencies (e.g., whllapic.dll) to your UiPath project’s bin or Debug folder (depending on your build configuration).

  3. Configure Project References:

    • Using NuGet Packages: If you’re using a NuGet package for QWS/3270 automation, ensure it’s properly installed and referenced in your project. Check the package documentation for specific instructions.
    • Manual References: If you’re not using NuGet, you might need to add references to the whllapi.dll file and its dependencies in your project’s properties. Right-click on your project, go to “Add” → “Reference,” and browse to the DLL locations.

  4. 32-bit vs. 64-bit Compatibility:

    • Make sure your UiPath Studio instance (32-bit or 64-bit) matches the architecture of the whllapi.dll file and the QWS/3270 emulator you’re using. If there’s a mismatch, you might need to install the appropriate version of UiPath Studio or the emulator.

  5. Check for Conflicting DLLs:

    • In rare cases, other DLLs with the same name in your system’s search path might interfere. Try copying the required DLLs to a temporary location outside the standard system paths to see if it resolves the issue.

Additional Considerations:

  • If you’re still encountering problems after trying these steps, consult the documentation for your QWS/3270 emulator software to see if there are specific instructions for UiPath integration.
  • Consider searching UiPath forums or communities for similar issues and potential solutions from other users.

By systematically following these troubleshooting steps, you should be able to resolve the whllapi.dll loading error and successfully use the QWS/3270 automation library in your UiPath .NET 6 project.

5

When installing.nuget package in the UiPath windows version it’s showing bad format .DLL invalid … what would be the reason…?

6

troubleshoot the “Bad IL format. DLL invalid” error you’re encountering when installing NuGet packages in UiPath Studio on Windows. Here are the common causes and potential solutions:

1. Package Compatibility Issues:

  • Check Package Versions: Ensure that the NuGet package you’re installing is compatible with your current UiPath Studio version. Refer to the package’s documentation or the UiPath documentation for supported versions. You can update or downgrade packages using the Manage Packages window in UiPath Studio.
  • Version Conflicts: If you’re using multiple packages with dependencies, verify that their versions don’t conflict. Use the Manage Packages window or tools like NuGet Package Explorer (Install and manage packages in Visual Studio using the NuGet Package Manager | Microsoft Learn) to identify and resolve conflicts.

2. Corrupted NuGet Cache:

  • Clear NuGet Cache: A corrupted NuGet cache can sometimes lead to installation issues. Try clearing the cache by following these steps:
    1. Close UiPath Studio.
    2. Open the Windows Command Prompt (or PowerShell) as an administrator.
    3. Run the command: nuget locals -ClearAll
    4. Restart UiPath Studio and attempt the installation again.

3. Missing or Corrupted .NET Framework:

  • Verify .NET Framework Installation: UiPath Studio relies on the .NET Framework for certain functionalities. Ensure you have the correct version installed based on your UiPath Studio version (.NET Framework documentation | Microsoft Learn). You can download the .NET Framework from the Microsoft website (Download .NET Framework | Free official downloads).
  • Repair .NET Framework: If the .NET Framework is already installed, try repairing it using the Windows Control Panel’s “Programs and Features” or “Apps & features” section.

4. Temporary Network Issues:

  • Retry Download: If the issue is transient, simply retrying the installation might resolve it. Sometimes network hiccups can cause download errors.

5. Antivirus Interference (Less Likely):

  • Temporarily Disable Antivirus: In rare cases, antivirus software might interfere with NuGet package installations. Temporarily disable your antivirus (be sure to re-enable it afterward) and try the installation again. Caution: Disabling antivirus software increases your computer’s vulnerability, so do this only as a last resort and re-enable it as soon as possible.

Additional Tips:

  • Restart UiPath Studio: Sometimes, a simple restart can clear up temporary glitches.
  • Reinstall UiPath Studio: If none of the above solutions work, consider reinstalling UiPath Studio to ensure a clean installation.
  • Community Forums and Support: If you’re still facing issues, reach out to the UiPath Support for further assistance. They may have encountered similar issues and can provide specific guidance.

By following these steps systematically, you should be able to identify the root cause of the “Bad IL format. DLL invalid” error and successfully install the NuGet packages in your UiPath Studio project.