Commented Issue: Creates "wrong" format of SQL Client Alias [20228]

Tried allowing it to create an alias for me.

Parameters I provided in the script:
DBServer (or alias name if creating alias): SPSQL
Create Instance: TRUE
Instance Name: SQL01
PORT: 1433

The alias that it created had following settings:

Alias: SPSQL
Network Libraries: Other
File name: DBMSLPCN
Parameters: SPAPP03 (the machine on which I am running the script)
(Screen shot attached)

I looked in the functions PS1 and saw where its hardwiring the protocol to DBMSLPCN.


```
If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\"))) {
$protocol = "dbmslpcn"
}
else {
$protocol = "DBMSSOCN"
}

```

When I create SQL aliases I always use TCP/IP.
I've never used any other format and this appears to be the consensus.

I can tell you that when the script tries to use the weirdo alias format it creates it fails to establish communication with SQL.


If I pre-create the Alias and simply reference the alias in the script it communicates fine.

My assumption is that this format of Client Alias is no good.

Can you please advise?

Thanks much.
Comments: ** Comment from web user: PerrySharePoint **

autospinstaller with the xml has this same bug, and it causes the install to fail until the ps1 is fixed. (There are other issues reporting this problem as well.)

I just submitted a patch which provides a workaround--the user has to specify a dbport for every alias that will be used, to inform the ps1 to use tcpip aliases.

Just submitted patch 18261 to fix this.