Thingworx Bootstrap Error : Connections could not be acquired from the underlying database

[Siddharth_Jhs]

Hi Community,

Recently my MS Sql server was poping message that it's login password expired and I need to update it. When I updated my password, Thingworx is not starting and giving following error :

Error : [L: ERROR] [O: c.t.s.ThingWorxBootstrapper] [I: ] [U: SuperUser] [S: ] [P: ] [T: main] *** CRITICAL ERROR ON STARTUP: Connections could not be acquired from the underlying database!

Can anyone suggest how I can troubleshoot this error and avoid such errors in future. Thanks in advance.

Attaching Application log for reference. 

Regards,

Sid

[VladimirN]

Articles:

• "Unable to start Tomcat with error: "java.lang.Exception: Unable to initialize and start system: Connections could not be acquired from the underlying database!" in ThingWorx Platform": https://www.ptc.com/en/support/article/CS351187
• "ThingWorx installer fails with "Connections could not be acquired from the underlying database"": https://www.ptc.com/en/support/article/CS331221
• "Previously running ThingWorx instance fails to start with "Connections could not be acquired from the underlying database" for Microsoft SQL Server": https://www.ptc.com/en/support/article/CS339075
• "Unable to connect to Thingworx": https://www.ptc.com/en/support/article/CS353061
• "ThingWorx fails to start to connect database of Persistence Provider": https://www.ptc.com/en/support/article/CS362373

[slangley · Accepted solution]

Hi @Siddharth_Jhs.

Basically, when you change the password for the ThingWorx user in SQL Server, you need to update the \ThingworxPlatform\platform-settings.json file with the new password.  If it was encrypted just replace with the new password in clear text, then refer to this page of the Help Center for re-encrypting it.

The links to the articles provided by Vladimir contain more details.

Regards.

--Sharon

[Siddharth_Jhs]

Thanks @slangley this is the information I was looking for. Alternatevily, I tried resetting my server login password to the original one which was stored as encrypted text in platform-settings.json file worked for me.