Article - CS282332

Following installation of ThingWorx on Microsoft SQL Server (MSSQL), Tomcat fails to start with error "Connections could not be acquired from the underlying database"

Modified: 18-Mar-2025   


Applies To

  • ThingWorx Platform 7.4 to 9.6
  • Microsoft SQL Server

Description

  • Apache Tomcat service stops immediately after starting
  • ThingWorx Server does not start up because connection could not be acquired from the Microsoft SQL Server (MSSQL) database
  • Have installed Thingworx, but getting a 503 Service Unavailable error in browser
  • The licenseRequestFile.txt and license file not generated in connected mode inside ThingworxPlatform folder on starting Tomcat service
  • Errors in \ThingworxStorage\logs\ApplicationLog.log:
[L: ERROR] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] [message: Connections could not be acquired from the underlying database!]
[L: INFO] [O: c.t.p.p.PersistenceProvider] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Connection ThingworxPersistenceProvider, type MssqlPersistenceProviderPackage stopped
[L: WARN] [O: c.t.p.p.PersistenceProvider] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Could not find persistenceProviderPackage MssqlPersistenceProviderPackage and thus could not stop data processing
[L: ERROR] [O: c.t.s.ThingWorxBootstrapper] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] [message: Unable to initialize and start system: Connections could not be acquired from the underlying database!]
  • \ThingworxStorage\logs\ApplicationLog.log displays ThingWorx attempts to connect to PostgreSQL and not Microsoft SQL Server
YYYY-MM-DD hh:mm:ss [L: INFO] [O: c.t.s.ThingWorxPersistenceHandler] [I: ] [U: SuperUser] [S: ] [P: ] [T: main] Default Persistence Provider Name = ThingworxPersistenceProvider
YYYY-MM-DD hh:mm:ss [L: INFO] [O: c.t.s.ThingWorxPersistenceHandler] [I: ] [U: SuperUser] [S: ] [P: ] [T: main] Default Persistence Provider Package Name = PostgresPersistenceProviderPackage
 
  • Platform installer does not progress and reports one of the below errors
    • Connection to Server could not be established, please check the information you have entered
    • Failed to validate the SQL Server connection and administrator privileges. Check the information you entered.
This is a printer-friendly version of Article 282332 and may be out of date. For the latest version click CS282332