SAP Knowledge Base Article - Preview

2377342 - Wrong database connection used after upgrading to SMP 3.0 SP11


  • During a SAP Mobile Platform (SMP) upgrade , the installation may fail with the following error in the SMPInstall logs:, err, ERROR: Upgrade failed
Exception in thread "main" java.lang.RuntimeException: Failed to init upgrade process.

Caused by: java.sql.SQLException: JZ006: Caught IOException: Connection refused: connect

at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(
at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(
at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(
at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(
at com.sybase.jdbc4.jdbc.SybConnection.<init>(
at com.sybase.jdbc4.jdbc.SybConnection.<init>(
at com.sybase.jdbc4.jdbc.SybDriver.connect(S

  • The log file referres to a port number that is not used at all (i.e. Derby database port might be used instead of the SQLAnywhere database port), dbg, serverHttpsPort number: 8083, dbg, smpServiceType found, dbg, serverAdminHttpsPort number: 8085, dbg, serverSSLHttpsPort number: 8084, dbg, jmxPort number: 1717, dbg, derbyDBPort number: 1527, dbg, osgiPort number: 2401



  • SAP Mobile Platform 3.0 SP10 - SP11


SAP Mobile Platform 3.0


UpgradeNonProxyURL smp sap mobile platform 3.0 Connection refused  Failed to init upgrade process database derby sqlanywhere oracle db2 ase , KBA , MOB-ONP , SAP Mobile Platform on Premise , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.