Hi Brian. I just tested a SQL/SharePoint install on the same machine and had to fight with a SQL connection failure juste with create SQL Alias set to true. I checked the created alias and it is creating a Shared Memory (Other) alias because SQL is installed on the same box. I had to set the alias creation to false to finish the install. I looked this on Technet and MS states that you cannot create an Alias for Shared Memory.

https://technet.microsoft.com/en-us/library/ms187662(v=sql.105).aspx

_You cannot create an alias using the shared memory protocol, but if shared memory is enabled, then connecting to the Database Engine by name, creates a shared memory connection. A shared memory connection string uses the format lpc:<servername>[\instancename]._

and since Shared Memory works like this:

_Shared memory is always tried first, and cannot be moved from the top position of the Enabled Protocols list in the Client Protocols Properties list._

there is no need for a 'other' alias I guess. Just a standard TCP/IP alias. Shared Memory will be used first if SQL is on the same box. I just tested it disabling all other protocols. SharePoint still works.

↧

Created Unassigned: Deploy Enterprise Search Service without Portal Webapplication [22545]

July 7, 2017, 2:06 am

≪ Previous: Created Unassigned: SQL Alias and Shared Memory [22540]

I want to deploy the enterprise search service, but I don't want to deploy the portal webapplication with AutoSPInstaller.
In this case the script gives the error, that
$xmlinput.Configuration.WebApplications.WebApplication
is empty.

Fix:
In function CreateEnterpriseSearchServiceApp, remove the three lines
> $portalWebApp = $xmlinput.Configuration.WebApplications.WebApplication | Where {$_.Type -eq "Portal"} | Select-Object -First 1
> $portalURL = ($portalWebApp.URL).TrimEnd("/")
> $portalPort = $portalWebApp.Port

Therefore it is working. (After all you don't even need these variables in this function.)

↧