A connection to the SQL Server through the SQL Command Line Executable is not permitted.
A SQL Command Line command needs to be successful before the Wavelink product can connect with the SQL Command Line Executable. If this cannot occur the installation will fail and the credentials not verified message will appear.
Resolution or Workaround
This can be tested by bringing up a command line and typing the following command:
If successful, manually connect to the DB from the eserver machine by typing the following command into a command prompt:
sqlcmd -H ipaddress,port -U user -P password -d avalanche50. If a different version of avalanache replace the avalanche50 with the correct version such as avalanche52 or avalanche53
Wavelink does not support/reconcile instance names. If the test can be run successfully using the dns name or straight IP then the installation should complete. If a server name is followed by \instance name the installation will fail. The following example illustrates a server followed by an instance name:
sqlcmd gco2squl12\cnfstaging -U sa -d avalanche50. If a different version of avalanache replace the avalanche50 with the correct version such as avalanche52 or avalanche53
Fortunately, MS SQL has a named instance that does not require a client to specify the name of the instance in order to make a connection. It is known as a default instance. It is named MSSQLSERVER
Since it does not does not require a client to specify the name in order to make a connection to the DB, there is no name for the WL product to reconcile. This results in a successful SQL Command Line command, connection, credential verification and installation.