Skip to main content
Solved

sapjco3.dll already loaded in another classloader

  • January 5, 2026
  • 6 replies
  • 76 views

Uzumaki
Forum|alt.badge.img+12

Has anyone run into an error message saying sapjco3.dll already loaded in another classloader as they’ve tried to use the SAP BAPI package more than once within a process?

For reference, I’m using a bot that calls the connects to the SAP BAPI package and then calls a child bot which also connects to the SAP BAPI package. Googling the error it looks like while there is one instance of the sapjco3.dll loaded to a java classloader, a second instance can’t be loaded, meaning I can’t have these parent child bots both using sap bapi actions.

I tried to solve this by refactoring my bot so that instead of task bot A connecting to the bapi followed by its child bot task bot B connecting, there is now a driver that delegates control to bot A and then to bot B. I thought this might work since the instance of task bot A finishes execution before bot B is called, but I’ve gotten the same error.

Any advice on this is appreciated.

Best answer by Uzumaki

@Uzumaki Can you make this work by putting all the actions into a single automation? Just for testing.

Fixed the issue. I updated the SAP bapi package on both bots to the most recent version. Now its letting me call the sap bapi connect from both. Even reverted everything from the sibling relationship back to the child-parent and it still works.

6 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+14
  • Automation Anywhere Team
  • January 5, 2026

@Uzumaki Can you make this work by putting all the actions into a single automation? Just for testing.


Forum|alt.badge.img+3
  • Navigator | Tier 3
  • January 6, 2026

Is Theat sap connecting instant you are doing in your every subbot? 


Uzumaki
Forum|alt.badge.img+12
  • Author
  • Navigator | Tier 3
  • January 6, 2026

@Uzumaki Can you make this work by putting all the actions into a single automation? Just for testing.

I was hoping to avoid that because doing so would make this one task bot pretty large. But worst case scenario, that is always an option.


Uzumaki
Forum|alt.badge.img+12
  • Author
  • Navigator | Tier 3
  • Answer
  • January 6, 2026

@Uzumaki Can you make this work by putting all the actions into a single automation? Just for testing.

Fixed the issue. I updated the SAP bapi package on both bots to the most recent version. Now its letting me call the sap bapi connect from both. Even reverted everything from the sibling relationship back to the child-parent and it still works.


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+14
  • Automation Anywhere Team
  • January 6, 2026

@Uzumaki Of course! 🔍 Two different package versions will pull down two copies of the SAP DLL because the DLL is embedded within the package. Great job finding the root cause!


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+14
  • Automation Anywhere Team
  • January 13, 2026

@Uzumaki We are investigating this internally. Would you mind reporting which package versions conflicted with each other? That would help us greatly. Thank you!