Troubleshooting Tip: Error 'Connection Timeout Expired', 'Unable to connect to server' secret launcher for SSMS client

Description

This article describes the support options available, errors encountered and the troubleshooting steps to be taken if launch fails with the SSMS client.

Scope

FortiPAM.

Solution

Common error messages:

 
Step 1:

• Verify the SSMS version used. 

• The only SSMS versions supported on FortiPAM are v19 and v20.

Step 2:

Verify if custom launchers are used. Custom launchers are not supported with SSMS, so the standard available launcher for SSMS should be used.

Step 3:

If version 20 is being used, ensure that settings exist under the following directory:

C:\Users\<user>\AppData\Roaming\Microsoft\SQL Server Management Studio\20.0.

If version 19 is being used, ensure that settings exist under the following directory:

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

After that, it is necessary to restart SSMS (the SQL Server) on the local environment to generate a usersetting.xml file under the location above.

Step 5:

Disable SQL-logging in the secret and enable credential-delegation:

config secret target
    edit <target id>
        set sql-server-log-status disable
    next
end

config secret database
    edit <secret id>
        set sqlserver-credential-delegation enable
    next
end

The steps above 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: see Welcome to Fortinet Support.

Provide the output of the following debug commands, or use them to debug manually:
 

diagnose debug reset
diagnose debug console timestamp enable
diagnose wad debug enable category tds
diagnose wad debug enable category auth
diagnose wad debug enable category sql
diagnose wad debug enable category http
diagnose wad debug enable category secret
diagnose wad debug enable level verbose
diagnose debug enable

To disable the debug processes, use the command 'diagnose debug disable'.

Note:

• Verify that SQL Server Authentication is selected in SQL Server Management Studio (SSMS). Windows Authentication is currently not supported by FortiPAM when launching SQL Server Management Studio secrets:

Related documents:

• Launching a secret for the MySQL server

• Creating a target