DBA cockpit connection XXX cannot be established

Symptom

The following error happens on step 5 'Enter System Parameters' when setting up the 'Managed System Configuration' via Solution Manager Wizard.

         DBA cockpit connection XXX cannot be establishedDetails errors would be
         SQL error 10054: TCP Provider: An existing connection was forcibly closed by the remote host. 
         or
         SQL error 15151: Cannot find the user "XXX_SAPMonitor"  
             
    If the DBA Cockpit Connection Status is greyed out, it means no DBCON entry was found. The connection can be set up from the beginning.
        If the DBA Cockpit Connection Status is in green light, it means an existing DBCON entry was found. The Authentication type and monitor login name cannot be changed.
2, Administrator login.

.
It should meet the following criterion.
-
It must be a login with SysAdmin role in your target SQL Server.
-
It can be either a Windows domain account or a SQL Server login.
-
You cannot specify a Windows account that is local on the target server.
-
If you use a domain account, enter the login as \.
-
If you use a SQL Server login,simply specify the login as .
This account is only used to create the new monitor login and monitor schema and objects. It is not saved anywhere in Solution Manager.

Environment

A solution manager system tries to access a remote SQL Server database.

Cause

These errors are usually caused by incorrect parameter definitions.

Resolution

Let's review every parameter in the Step 5. Then you can understand whether you define the parameter correctly.

1, The color of  "DBA Cockpit Connection Status".

2,    Administrator login. 

Check Note 1904412 for more information