An 'HTTP 500 Internal Server Error' appears when attempting to invoke Toad DevOps Toolkit via the API. The error response contains the following details:
|
Status |
Finished |
|
Error |
No valid license found. Please add a valid license before using Toad DevOps Toolkit. |
|
Submitted |
2026-04-29T06:35:18Z |
This error indicates that a valid Toad DevOps Toolkit license is either not present on the system, not correctly placed, or not recognized by the application.
Follow the steps below to apply a valid license and resolve the HTTP 500 error.
Check your email inbox for a message from Quest containing the .dlv license file as an attachment. If you cannot locate it, contact Quest Support and we will assist with reissuing the file.
Once you have the .dlv file, choose one of the following options:
Option A (Recommended): Place the .dlv file in the default location defined in the License.cfg configuration file:
C:\ProgramData\Quest Software\Toad Devops Toolkit\License.cfg
Open License.cfg to confirm the exact target path where the .dlv file should be placed.
Option B: Place the .dlv file in a location of your choosing, then update the path inside License.cfg to point to the new location.
After placing the .dlv file, run the following commands in PowerShell to apply the license:
$TDT = New-Object -ComObject 'Toad.ToadAutoObject'
$TDT.Licensing.AddLicense('C:\path\to\your\license.dlv')
$TDT.Quit()
Replace C:\path\to\your\license.dlv with the actual full path to your .dlv file.
To confirm that the license has been applied correctly, run the following in PowerShell:
$TDT = New-Object -ComObject 'Toad.ToadAutoObject'
$TDT.Licensing
$TDT.Quit()
This will display the locally cached license information so you can verify it is valid and active.
If a license was previously cached and you need to load a new one, run the command below. Note: this will clear the existing cached license before loading the new one from the .dlv file.
$TDT = New-Object -ComObject 'Toad.ToadAutoObject'
$TDT.Licensing.Refresh()
$TDT.Quit()
Once all steps are completed, restart Toad DevOps Toolkit and attempt to use the tool again