Skip to main content

"Could not connect to the platform database (JNDI resource 'jdbc/kapow/platform')" error

Article # 3035410 - Page views: 556


This Knowledgebase article details the main root causes for the error "Could not connect to the platform database". This applies to Management Consoles or Kapplets (v11.0 and later) deployed into standalone Tomcat.

How to troubleshoot this error?


After deploying Management Console/Kapplets in Tomcat, the web interface doesn't load. The browser shows one (or more) of the following errors:

  • Application failed to start
  • Spring subsystem failed to load
  • Error 500
  • Error 404

Also, in the Tomcat logs, there are multiple entries with the same error

"Could not connect to the platform database (JNDI resource  'jdbc/kapow/platform')"


"Could not connect to the platform database (JNDI resource  'jdbc/kapow/kapplets')"


This error is caused by the lack of communication with the platform database. This can be caused by various reasons detailed below

To troubleshoot this issue, the database configuration is needed. This can be found in the Management Console/Kapplets XML context file normally located under Tomcat's /conf/Catalina/localhost folder. This file has to be created by the user who is deploying the Management Console/Kapplets (see the instructions in the Admin Guide (for MC) or Installation Guide (for Kapplets) for more information).

The table below lists the main possible causes why Tomcat is not able to create the content in the platform database, even when Management Console/Kapplets XML context file exists:

To Check How
is the JDBC driver provided? check the type of database being used (in the Management Console XML context file) and make sure the corresponding driver is uploaded in either:
  • Tomcat lib folder
  • in Tomcat under /webapps/ManagementConsole/WEB-INF/lib (or /webapps/kapplets/WEB-INF/lib )
can the Tomcat machine reach the Database machine? ping and telnet using the machine name/IP and port specified in the Management Console / Kapplets XML context file
do the credentials work? check by logging in to the database using its own Management Tools
is the url connection string correct?

make sure the connection string is correct for the database type.

E.g. are you using a connection string for a MS SQL server meant for SQL authentication and providing Windows credentials (not SQL)?

For Azure installations, SSL may be required, therefore, remove useSSL=false& other changes may be required that differ from the samples in the Installation Guide.

does the database exist? check in the Management Tools of your database server. Management Console / Kapplets needs to have the database created, it will not create it. Also, the case has to match.
does the user have rights to create tables? if the database is empty, Tomcat will create the tables as long as the user provided has the rights. The user credentials are the ones in Management Console/Kapplets XML context file (keep in mind that when using MS SQL with a connection url that uses windows authentication, the credentials that Tomcat will use are the credentials of the user running the Tomcat process, regardless if they are the same as the ones in the XML context file).
were any configuration files copied from and older Management Console (e.g. login.xml, configuration.xml etc) This is not supported. The new Management Console might have different tags in these files. Even if the same data is needed, please use the files from the new Management Console, do not copy a whole file from an older version.

If neither of the options above help, please contact Kofax Technical Support.

Level of Complexity 



Applies to  

Product Version Build Environment Hardware
Kofax RPA ALL      




Article # 3035410