2578699 - "A bad request was made to SAP Analytics Cloud agent" error message appears in SAP Analytics Cloud

• When trying to create model based on Import Data Connection the following error message appears in SAP Analytics Cloud: A bad request was made to SAP Analytics Cloud agent.
• The following message is also logged to the Tomcat logs: "<Driver Name> has been compiled by a more recent version of the Java Runtime (class file version 57.0), this version of the Java Runtime only recognizes class file versions up to 52.0"

SAP Analytics Cloud 2026.14.5

1. Log on to SAP Analytics Cloud.
2. From the Main Menu, choose Create → Model.
3. Select an Import Data Connection.
4. Try to search for a query or table.
5. An error message appears in the UI.
6. The Tomcat log contains the "class file version" message described above.

There are multiple possible causes, all relating to a mismatch between the Java Runtime version used by Tomcat and the version required by the driver or connector:

1. JDBC driver compiled for a newer Java version than SAPJVM/JRE running Tomcat. For example, a JDBC driver compiled for Java 13 (class file version 57.0) will fail when Tomcat runs on SAPJVM 8 (which only reads up to class file version 52.0). This is the most common cause.
2. JAVA_HOME environment variable points to a JVM with a different architecture (x86 vs. x64) than Tomcat. A mismatch causes Tomcat to load an incompatible JVM, leading to runtime errors including class loading failures.
3. vcredist (Visual C++ Redistributable) architecture does not match the Tomcat architecture. If a 32-bit vcredist is installed but Tomcat is running as 64-bit (or vice versa), native library loading can fail.
4. Tomcat JVM path is not pointing to the SAPJVM jvm.dll. Tomcat Properties may reference an incorrect or mismatched JVM binary.
5. SAP Cloud Connector is configured to use HTTPS to communicate with Tomcat, but Tomcat is only configured for HTTP (or vice versa), causing the connection layer to fail before the class loading error is reached.

Work through the following checks in order. Each check addresses one of the potential causes above.

1. Verify JDBC driver compatibility with SAPJVM 8

• This is the most common cause. The SAP Analytics Cloud Agent runs on SAPJVM 8 (Java 8, class file version 52.0). Any JDBC driver deployed must be compiled for Java 8 (JRE 8) or lower.
• For Microsoft SQL Server: Use the Microsoft JDBC Driver for SQL Server version 7.x or earlier (compiled for Java 8). Versions 9.x and later require Java 11+. Download from the Microsoft JDBC Driver documentation.
• For other databases: Check the driver's release notes for the minimum required JRE version. Use a variant explicitly marked as compatible with Java 8 / JRE 8.

Place the compatible driver .jar file in the correct agent library folder and restart Tomcat.

2. Verify JAVA_HOME architecture matches Tomcat architecture

The SAP Analytics Cloud Agent Simple Deployment Kit installs a 64-bit Tomcat on Windows. Confirm:

• JAVA_HOME points to a 64-bit JVM (SAPJVM 8 x64).
• Do not mix 32-bit JVM with 64-bit Tomcat or vice versa.

Check JAVA_HOME by running echo %JAVA_HOME% in a command prompt on the agent server and verify the path points to a 64-bit SAPJVM installation.

3. Verify vcredist architecture matches Tomcat

Ensure the Microsoft Visual C++ Redistributable (vcredist) installed on the server matches the Tomcat bitness:

• 64-bit Tomcat → install vcredist_x64.exe
• 32-bit Tomcat → install vcredist_x86.exe

If in doubt, install both variants. Mismatched vcredist can prevent native library loading at Tomcat startup.

4. Verify Tomcat JVM path points to the correct jvm.dll

Open the Tomcat Properties (Tomcat service manager → Java tab) and check the Java Virtual Machine field:

• It must point to jvm.dll located inside the SAPJVM installation directory, for example: C:\sapjvm_8\jre\bin\server\jvm.dll
• If this field is blank or points to a different JVM, correct it. A Tomcat reinstall may be required to fully reset this setting.

5. Verify Cloud Connector protocol matches Tomcat configuration

In SAP Cloud Connector, check the protocol configured for the backend mapping pointing to the Tomcat host and port:

• If Tomcat is configured for HTTP only, ensure Cloud Connector is set to HTTP (not HTTPS) for that mapping.
• If Tomcat is configured for HTTPS, ensure the corresponding SSL certificate is correctly set up.

• KBA 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
• KBA 2487011 - What information do I need to provide when opening a case for SAP Analytics Cloud?
• KBA 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
• SAP Analytics Cloud Connection Guide
• SAP Analytics Cloud Get More Help and SAP Support
• Need More Help? Contact Support 

Your feedback is important to help us improve our knowledge base.

SAP Analytics Cloud, SAC, Import Data Connection, Tomcat, SAPJVM, Java Runtime, class file version, JDBC driver, SQL Server, JVM, JAVA_HOME, vcredist, x86, x64, Cloud Connector, on-premise, agent, LOD-ANA , KBA , LOD-ANA , SAP Analytics Cloud (SAC) , LOD-ANA-BI , Business Intelligence Functionality, Analytic Models , LOD-ANA-PL , Planning , LOD-ANA-BR , SAC Boardroom , LOD-ANA-PR , SAC Predictive , Problem