Description:
This article outlines the support options available, errors encountered and the troubleshooting steps to be taken if launch fails with SSMS client.
Common Error messages:
Scope
FortiPAM.
Solution
Step 1:
Verify the SSMS version used.
The SSMS version on FPAM supported is 19 and 20 only.
Step 2:
Verify if custom launchers are used, custom launcher are not supported with SSMS, standard available launcher for SSMS should be used.
Step 3:
If using version 20, ensure that settings exists under C:\Users\<user>\AppData\Roaming\Microsoft\SQL Server Management Studio\20.0.
If using version 19, ensure that settings exists under C:\Users\<user>\AppData\Roaming\Microsoft\SQL Server Management Studio\19.0.
Step 4:
Remove 'User settings' from the version used respectively.
C:\Users\user\AppData\Roaming\Microsoft\SQL Server Management Studio\20
C:\Users\user\AppData\Roaming\Microsoft\SQL Server Management Studio\19
Step 5:
Disable SQL-logging in the secret and enable credential-delegation.
The above steps will remove any user settings that may be causing the issues. After launching the secret successfully, the file should appear again in the appropriate directory as noted in Step 4.
If the issue persists, it may be necessary to submit a case to Fortinet Technical Support.
In that case, the following debug output may be useful:
diag debug reset
diag debug console timestamp enable
diag wad debug enable category tds
diag wad debug enable category auth
diag wad debug enable category sql
diagnose wad debug enable level verbose
diagnose debug enable
To disable the debugs, use the command 'diag debug disable'.
Related articles:
Launching a secret for the mySQL server - FortiPAM documentation
