Commented Issue: Trying to connect to "SQL"... - Fail [19412]

I am running into an issue with an installation on a new VM instance and VM database. When I ran the script for the first time it fails when trying to connect to the Dev (Connection Error. Check server name, port, firewall) and the second time the connection fails but different message (Exception calling “Open” with “0” argument(s): “Cannot generate SSPI context.”) . The error details are not pinpointing much or very detail so I was hoping someone has encounter the same issue and have a solution.

Both servers are in the same domain. I checked the SQL server and insured that all the accounts have access to the SQL Instance; Farm Account and Setup Account have sysadmin rights. The port 1433 is open on SQL's firewall. There is connectivity between the servers.

First Time I ran the script…
- Testing access to SQL server/instance/alias: Dev01
- Trying to connect to "Dev01"... - Fail
--------------------------------------------------------------
- Script halted!
- Connection Error. Check server name, port, firewall.
Press any key to exit...

Second Time I ran the script…
- Creating SQL alias “Dev01,1433”...
-Testing access to SQL server/instance/alias: Dev01
- Trying to connect to “Dev01”… - Fail
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Script halted!
- Exception calling “Open” with “0” argument(s): “Cannot generate SSPI context.”
Press any key to exit…
Comments: ** Comment from web user: BenMac **

Hi there,

[VERSION: 3.96]

Same Issue: SQLAlias is being created by AutoSPInstaller, but getting "Connection Error" when running.
Following suggestions about creating an ODBC test connection, i got this fail:

------------------------------------------------------------------------
Microsoft SQL Server ODBC Driver Version 06.01.7601

Running connectivity tests...

Attempting connection
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Invalid connection.

TESTS FAILED!
------------------------------------------------------------------------

However, simply changing the Port setting in SQL Server Client Network Utility
From:
[X] Dynamically determine port

To:
[ ] Dynamically determine port
Port number: 1433 (--> the default port)

And hey presto:

------------------------------------------------------------------------
Microsoft SQL Server ODBC Driver Version 06.01.7601

Running connectivity tests...

Attempting connection
Connection established
Verifying option settings
Disconnecting from server

TESTS COMPLETED SUCCESSFULLY!
------------------------------------------------------------------------

So it would seem that AutoSPInstallerGUI states that if you leave the Port field blank, 1433 is used is NOT TRUE.

Resolution: Always specify the SQL Alias Port Number in your script, even if 1433

Hope this helps,
Ben