Skip to main content
S
Siddharth_Jhs14-Alexandrite
14-Alexandrite
May 14, 2023
Solved

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

  • May 14, 2023
  • 2 replies
  • 1770 views

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

 

Best answer by slangley

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

2 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
May 14, 2023

Articles:

    S
    slangleyCommunity ManagerAnswer
    Community Manager
    May 19, 2023

    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

      S
      Siddharth_Jhs14-AlexandriteAuthor
      14-Alexandrite
      May 19, 2023

      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.

      Terms & ConditionsCookie settingsAccessibility statement