# \#jvm

**URL:** https://community.cdata.com/tag/jvm/858.md

[Latest](https://community.cdata.com/latest.md) · [Categories](https://community.cdata.com/categories.md) · [Tags](https://community.cdata.com/tags.md)

---

## [SAP ERP JDBC: “sapjco3.dll already loaded in another classloader” when used from Jaspersoft Studio](https://community.cdata.com/t/sap-erp-jdbc-sapjco3-dll-already-loaded-in-another-classloader-when-used-from-jaspersoft-studio/1246)

<div class="topic-metadata">

**Author:** [@James\_B](https://community.cdata.com/u/James_B)\
**Replies:** 0\
**Last updated:** [December 2, 2025, 4:36pm UTC](https://community.cdata.com/t/sap-erp-jdbc-sapjco3-dll-already-loaded-in-another-classloader-when-used-from-jaspersoft-studio/1246 "2025-12-02T16:36:04Z")

</div>

The CData SAP ERP driver uses the sapjco3.jar dependency, which must be referenced in the classpath. This JAR, in turn, depends on sapjco3.dll, whose path must be added to the PATH system environment variable. When usin…
