autospinstaller Issue Tracker Rss Feed

Commented Unassigned: "The local farm is not accessible" [19850]

mlopez_iattc — Tue, 18 Jun 2013 21:16:42 GMT

On a fresh install of Windows Server 2008 R2 SP1, SQL Server 2012 and PowerShell 3.0 (could PS 3.0 be the reason? ):

[all is well until ...]
--------------------------------------------------------------
- SharePoint 2013 binary file installation done!
--------------------------------------------------------------
- Adding IATTC01\SharePointFarm to local Administrators (only for install)...
--------------------------------------------------------------
--------------------------------------------------------------
- Loading SharePoint Powershell Snapin...
The local farm is not accessible. Cmdlets with FeatureDependencyId are not regis
tered.
could not create a CmdletConfiguration for CmdletName Install-SPRSService, Cmlde
tClass , CmdletHelpFile C:\Program Files\Common Files\Microsoft Shared\Web Serv
er Extensions\15\CONFIG\PowerShell\Help\Microsoft.ReportingServices.SharePoint.P
owerShell.dll-help.xml.
Cannot process argument because the value of argument "implementingType" is null
. Change the value of argument "implementingType" to a non-null value.
could not create a CmdletConfiguration for CmdletName Install-SPRSServiceProxy,
CmldetClass , CmdletHelpFile C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\15\CONFIG\PowerShell\Help\Microsoft.ReportingServices.SharePo
int.PowerShell.dll-help.xml.

[this repeats many times until eventually we get to:]

--------------------------------------------------------------
- Checking farm membership for INTRANET in "Intranet1_Config"...

- Attempting to join farm on "Intranet1_Config"...
- No existing farm found.
- Creating config database "Intranet1_Config"...
- Done creating configuration database for farm.
--------------------------------------------------------------
--------------------------------------------------------------
- Configuring the SharePoint farm/server...
- Installing Help Collection...
- Securing Resources...
- Installing Services...
- Installing Features...
- Creating Central Admin site...
- Waiting for Central Admin site...Online
- Updating Central Admin branding text to "IATTC Intranet"...
- Installing Application Content...
--------------------------------------------------------------
- Script halted!

Exception : System.IO.FileNotFoundException: Could not load file
or assembly 'Microsoft.IIS.PowerShell.Framework' or
one of its dependencies. The system cannot find the
file specified.
File name: 'Microsoft.IIS.PowerShell.Framework'
at
System.Reflection.RuntimeAssembly._nLoad(AssemblyName
fileName, String codeBase, Evidence assemblySecurity,
RuntimeAssembly locationHint, StackCrawlMark&
stackMark, IntPtr pPrivHostBinder, Boolean
throwOnFileNotFound, Boolean forIntrospection, Boolean
suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.LoadWithPartial
NameInternal(AssemblyName an, Evidence
securityEvidence, StackCrawlMark& stackMark)
at Microsoft.IIs.PowerShell.Framework.Interop.IAppHo
stElement.get_Properties()
at Microsoft.IIs.PowerShell.Framework.ConfigurationE
lement.get_Attributes()
at Microsoft.IIs.PowerShell.Framework.ConfigurationE
lement.ToPSObject(ConfigurationElement parent)
at Microsoft.IIs.PowerShell.Framework.ConfigurationE
lement.ToPSObject(ConfigurationElement parent)
at Microsoft.IIs.PowerShell.Framework.ConfigurationE
lement.ToPSObject(ConfigurationElement parent)
at Microsoft.IIs.PowerShell.Provider.GetWebsiteComma
nd.WriteSite(ConfigurationInfo o)
at Microsoft.IIs.PowerShell.Framework.Configuration.
XPathQueryToStream(String query, PipelineStreamWriter
writer)
at System.Management.Automation.CommandProcessor.Pro
cessRecord()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the
registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to
1.
Note: There is some performance penalty associated
with assembly bind failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].

TargetObject :
CategoryInfo : NotSpecified: (:) [Get-Website], FileNotFoundException
FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.IIs.PowerShel
l.Provider.GetWebsiteCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at ConfigureFarm, C:\AutoSPInstaller\SP\AutoSPInstaller
\AutoSPInstallerFunctions.ps1: line 1480
at Setup-Farm, C:\AutoSPInstaller\SP\AutoSPInstaller\Au
toSPInstallerMain.ps1: line 185
at <ScriptBlock>, C:\AutoSPInstaller\SP\AutoSPInstaller
\AutoSPInstallerMain.ps1: line 358
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

-----------------------------------
| Automated SP2013 install script |
| Started on: 6/13/2013 9:17:10 AM |
| Aborted: 6/13/2013 9:37:31 AM |
-----------------------------------

Second attempt immediatelly after the above:

[all is well until ...]
--------------------------------------------------------------
- Adding Managed Accounts
- Enabling Secondary Logon service...
- Starting Secondary Logon service...
--------------------------------------------------------------
- Script halted!

Exception : System.Management.Automation.ParameterBindingValidation
Exception: Cannot bind argument to parameter 'String'
because it is an empty string.
at System.Management.Automation.ExceptionHandlingOps
.CheckActionPreference(FunctionContext funcContext,
Exception exception)
at System.Management.Automation.Interpreter.ActionCa
llInstruction`2.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTry
CatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTry
CatchFinallyInstruction.Run(InterpretedFrame frame)
TargetObject :
CategoryInfo : InvalidData: (:) [ConvertTo-SecureString],
ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,M
icrosoft.PowerShell.Commands.ConvertToSecureStringComma
nd
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at AddManagedAccounts, C:\AutoSPInstaller\SP\AutoSPInst
aller\AutoSPInstallerFunctions.ps1: line 1580
at Setup-Farm, C:\AutoSPInstaller\SP\AutoSPInstaller\Au
toSPInstallerMain.ps1: line 189
at <ScriptBlock>, C:\AutoSPInstaller\SP\AutoSPInstaller
\AutoSPInstallerMain.ps1: line 358
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

-----------------------------------
| Automated SP2013 install script |
| Started on: 6/13/2013 10:49:19 AM |
| Aborted: 6/13/2013 10:49:55 AM |
-----------------------------------
PS C:\AutoSPInstaller\SP\AutoSPInstaller>
Comments: ** Comment from web user: mlopez_iattc **

Hi Brian,

Sorry to ask again but I need to move forward with SP2013. If there is an issue with PS 3.0 and ASPI, rather than a lack of understanding on my part, should I just not use ASPI for now? I undestand it may take some time to sort these things out.

Thanks again,

Commented Issue: Error Changing App Fabric Cache Service Account [19493]

CraigHumphrey — Tue, 18 Jun 2013 04:23:34 GMT

I've used version 3.85 of AutoSPInstaller several times now and I'm only running into one error. The Farm installs to completion but I'm finding an error in the log associated with changing the identity for the App Fabric Cache Service. I haven't found anything that doesn't work in the farm. Any idea what the error is or why we are changing the service account on the App Fabric to begin with. Here's the error in the Log:

- Applying service account SPDEV\spd_serviceapps to service AppFabricCachingService...
- Updating Distributed Cache to run as SPDEV\spd_serviceapps...
Exception calling "Deploy" with "0" argument(s):
"ErrorCode<ERRCAdmin010>:SubStatus<ES0001>:Specified host is not present in
cluster."
At C:\Install\AutoSPInstallerV3\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1
:1112 char:9
+ $serviceToUpdate.ProcessIdentity.Deploy()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : CmdletInvocationException

WARNING: An error occurred updating the service account for service
AppFabricCachingService.
Comments: ** Comment from web user: CraigHumphrey **

I'm getting the same issue with v3.87.

Specified host is not present in AutoSPInstaller log.
AppFabric service repeatedly crashes (.net error) and then is disabled.
Rest of SP moans because Distributed Cache service isn't running/responding.

Uninstalled AppFabric. Used the PreReq installer to re-install AppFabric.
Found that the DistributedCache.exe.config still had NT AUTHORITY\NETWORK SERVICE in the <host> line, though the service was set to run as DOMAIN\SPServices account.
Found I had no permissions to start/edit AppFabric service.

This is going from bad to worse.

Commented Issue: BSOD when process loads log in Wordpad [19491]

CraigHumphrey — Tue, 18 Jun 2013 02:59:35 GMT

I have a reproducible scenario whereby when the ASPI process completes and I press "any key" to complete the process, the logging transcript is loaded into Wordpad. For me (connected over RDP) everytime that happens the system crashes with the blue screen of death and a core dump.

Anybody else see this?

Windows Server 2008 RS SP1
SP 2013 Enterprise
ASPI 3.85
Comments: ** Comment from web user: CraigHumphrey **

Hey Guys,
I'm seeing the same thing with the output from v3.87. Opened the RTF file on my OWA server (so similar patch level, but not exactly the same) Srv2008R2SP1 on VMWare:
![Image](http://sdrv.ms/10seRqn)
Opened the RTF on my desktop (Win7sp1 x86) no problem.
Created a test RTF on my desktop, opened it on the OWA server - no problem.
Copied the content (using WordPad) of the AutoSPInstaller into a new (WordPad) RTF - opened just fine.
Note: the new RTF was 42KB, compared to 73KB for the original AutoSPInstaller generated one. All formatting was lost in the copy&paste.
Opened it in Word on my desktop, saved it out as a new RTF (77K, more formattin added) - opened just fine.

Google not revealing much...

Later'ish
Craig

Created Unassigned: Error with spaces in password with PowerShell remoting [19864]

Hugheser — Tue, 18 Jun 2013 00:41:44 GMT

When you have spaces in your password/passphrase, the script can fail when beginning PowerShell remoting into the other servers. I have corrected it by adding double double quotes or escaping the quotes on line 5392 of AutoSPInstallerLineFunctions. The new line is:

-ArgumentList "/acceptEula \\$server -u $username -p ""$password"" -h powershell.exe -Command `"$configureTargetScript`"" `

Thanks for the excellent work on this script and let me know if you have any questions.

Brian Hughes

Closed Unassigned: 2012 Server - A known issue occurred configuring .NET 4 / IIS [19861]

brianlala — Mon, 17 Jun 2013 14:46:42 GMT

I've been experiencing this issue noted in other threads with solution of running aspnet_regiis - but that doesn't seem to work on 2012 server.

Running AutoSPInstaller I repeatedly get this error :

```
- Prerequisite Installer completed in 00:02:57.
- SharePoint 2013 "missing hotfix" prerequisites...
- Checking for KB2765317...Already installed.
WARNING: 2013-06-14 12:55:16 - Error when enabling ASP.NET v4.0.30319
WARNING: 2013-06-14 12:55:16 - Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.
WARNING: 2013-06-14 12:55:16 - Last return code (1)
- A known issue occurred configuring .NET 4 / IIS.
- Setting AutoSPInstaller information in the registry...
--------------------------------------------------------------
- Script halted!
```

The I read other people's solution here and tried the aspnet_regiis solution and get this error:

```
D:\SP\AutoSPInstaller>"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe" -i -enable
Microsoft (R) ASP.NET RegIIS version 4.0.30319.17929
Administration utility to install and uninstall ASP.NET on the local machine.
Copyright (C) Microsoft Corporation. All rights reserved.
Start installing ASP.NET (4.0.30319.17929).
This option is not supported on this version of the operating system. Administrators should instead install/uninstall ASP.NET 4.5 with IIS8 using the "Turn Windows Features On/Off" dialog, the Server Manager management tool, or the dism.exe command line tool. For more details please see http://go.microsoft.com/fwlink/?LinkID=216771.
Finished installing ASP.NET (4.0.30319.17929).
```

Reading these two links:

* http://support.microsoft.com/kb/2736284
* http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45

It seems that .Net 4/4.5 can only be installed as a role/feature - Has anyone else had this issue? How have you gotten around it?

Created Unassigned: 2012 Server - A known issue occurred configuring .NET 4 / IIS [19861]

webguynj — Mon, 17 Jun 2013 13:45:54 GMT

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

webguynj — Mon, 17 Jun 2013 13:25:25 GMT

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: webguynj **

I guess direct links to skydrive images don't work - :-(

Commented Issue: Failed to create managed account! [16866]

gigaflare — Mon, 17 Jun 2013 04:57:09 GMT

The script does not seem to recognize that the managed accounts are already configured when re-running the script after a failure.
(Initial failure was due to an incorrect account in the MySitesHost service config)

- Adding Managed Accounts
- Creating local profile for TEST\spservice...Done.
- Registering managed account TEST\spservice...
New-SPManagedAccount : Account TEST\spservice has already been registered
.
At C:\sp2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1087 char:34
+ New-SPManagedAccount <<<< -Credential $credAccount | Out-Nul
l
+ CategoryInfo : InvalidData: (Microsoft.Share...wManagedAccount:
SPCmdletNewManagedAccount) [New-SPManagedAccount], InvalidOperationExcepti
on
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewManag
edAccount

--------------------------------------------------------------
- Script aborted!
- Failed to create managed account
Comments: ** Comment from web user: gigaflare **

I ran into the same problem but I followed RobertRFreeman's post and I can verify it works.

Commented Issue: EnableRemoteInstall set to False [19499]

brm013 — Mon, 17 Jun 2013 01:42:51 GMT

In the latest version (3.85), AutoSPInstaller refuses to execute code against remote servers on the first run through, saying that RemoteInstall is not set to "true". It is defined that way in the XML though. Looking through the code logic, I believe that it's because ASPI sets the 'autologon' key in the registry, reboots to apply whatever changes are needed, then reads the autologon key again and sets it the EnableRemoteInstall variable before it clears the key. The RemoteInstall only executes if the autologon key is not present.
Comments: ** Comment from web user: brm013 **

Hi Brian,

I have been struggling with this for a days now. I thought this was the problem.

And just to comment further on using the non-SP server as the controller, this makes much more sense to me. I think the documentation should refer more to this approach.

After trying this the scripts straight away went into remote/parallel installation modes and PS shells started firing up and everything just made sense. The previous (unsuccessful) way I was trying to do this meant that you had to get all the way to the end of the first server install before any remote/parallel installs started, and that just didn't make sense to me.

Cheers,
Brett

Commented Issue: SMTP Service Startup Type [19744]

brianlala — Sat, 15 Jun 2013 12:35:53 GMT

The SMTP service is set to Manual startup by default the following command should be run after installation to set the startup type to automatic:

Set-Service SMTPSVC -StartupType Automation
Comments: ** Comment from web user: brianlala **

I just discovered that in Windows Server 2012 at least, the SMTP service isn't available yet immediately after its installation (hence the warning about it needing a restart). If you try to run the above line you will get a warning that there is no service by the name SMTPSVC.

So we can still add the line, maybe with a -ErrorAction SilentlyContinue switch so the entire script doesn't error out. That way we can at least ensure the service is set properly on a subsequent run of the script, post-reboot.

Brian

Commented Unassigned: "The local farm is not accessible" [19850]

mlopez_iattc — Fri, 14 Jun 2013 18:02:59 GMT

I meant to say *WMF* 3.0. I am a bit confused because WMF 3.0 is a prerequiste for SP 2013, yet having WMF 3.0 installed on the server before running ASPI is what seems to break things. I'd appreciate being put straight on this.

Commented Unassigned: "The local farm is not accessible" [19850]

mlopez_iattc — Fri, 14 Jun 2013 17:55:22 GMT

I understand that the cause of all this was the presence of WMI 3.0 on the server prior to running ASPI. Because of the improvements in PowerShell 3.0 , I would like SP2013 and ASPI to get along well with WMI 3.0. Will installing WMI 3.0 once SP 2013 is installed break things? Is it simply a matter of time before we can use PS 3.0 with SP2013?

Thanks again!

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

brianlala — Fri, 14 Jun 2013 16:33:23 GMT

The images aren't coming through for me... anyone else?

Closed Issue: InstallSPHelpCollection is rerun even if it has been installed once [18214]

brianlala — Fri, 14 Jun 2013 16:31:09 GMT

If you are installing the first server and there is a failure after the SPHelpCollection has been installed, eg incorrect url in sitecollection, when you rerun the script the SPHelpCollection is rerun.

Commented Unassigned: "The local farm is not accessible" [19850]

mlopez_iattc — Fri, 14 Jun 2013 16:03:23 GMT

Thanks, I'll try that. In the meantime, and just in case it may be of interest, I tried uninstalling SP and re-running ASPI. The resutl was that just prior to:

--------------------------------------------------------------
- Checking farm membership for INTRANET in "Intranet1_Config"...

I saw a number of these:
Cannot process argument because the value of argument "implementingType" is null
. Change the value of argument "implementingType" to a non-null value.
could not create a CmdletConfiguration for CmdletName Remove-SPRSExtension, Cmld
etClass , CmdletHelpFile C:\Program Files\Common Files\Microsoft Shared\Web Ser
ver Extensions\15\CONFIG\PowerShell\Help\Microsoft.ReportingServices.SharePoint.
PowerShell.dll-help.xml.

The script continued to install the bits then ...

Configuration of the SharePoint Products has succeeded.
--------------------------------------------------------------
--------------------------------------------------------------
- Adding Managed Accounts
- Enabling Secondary Logon service...
- Starting Secondary Logon service...
--------------------------------------------------------------
- Script halted!

Exception : System.Management.Automation.ParameterBindingValidation
Exception: Cannot bind argument to parameter 'String'
because it is an empty string.
at System.Management.Automation.ExceptionHandlingOps
.CheckActionPreference(FunctionContext funcContext,
Exception exception)
at System.Management.Automation.Interpreter.ActionCa
llInstruction`2.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTry
CatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTry
CatchFinallyInstruction.Run(InterpretedFrame frame)
TargetObject :
CategoryInfo : InvalidData: (:) [ConvertTo-SecureString],
ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,M
icrosoft.PowerShell.Commands.ConvertToSecureStringComma
nd
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at AddManagedAccounts, C:\AutoSPInstaller\SP\AutoSPInst
aller\AutoSPInstallerFunctions.ps1: line 1580
at Setup-Farm, C:\AutoSPInstaller\SP\AutoSPInstaller\Au
toSPInstallerMain.ps1: line 189
at <ScriptBlock>, C:\AutoSPInstaller\SP\AutoSPInstaller
\AutoSPInstallerMain.ps1: line 358
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

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

webguynj — Fri, 14 Jun 2013 15:06:40 GMT

Here are my firewall settings on the SQL server

![Image](https://shw38w.bn1.livefilestore.com/y2plXgTK4mNLPhao1M66RFePBrlqDu-8xNDBJldKjovMqrVadPjT7XeWhBa214RzDB9gk8eDZ9Cb0gNG5_gTGMZHMDh8QJC_QXWhB7V5n03FVQ/130614-FireWallScreenShot.png?psid=1)

Here are the SQL Server Server and Client Protocol settings:
![Image](https://tbw38w.bn1.livefilestore.com/y2p_DW4iktWMn1uwaZbz2DnisG6iTd59um2Un-ABy26AJh0hoQHQmQAEOdOtk2TEjrVzdEpEOiTNVXeDHFRg1pf79ThlIuDD4K5nu0mzfLPQJs/130614-SQLClientProtocol.png?psid=1)

and

![Image](https://tbw38w.bn1.livefilestore.com/y2psplpX5tXWzwqBIpJy4ys_DxTzOqK_OrAHeJdxZUlZpL_6I-oL3OrYzzc1FYbh6hcCvxZfbllRQF_0bzUiXSroG5NVbUJTpKva8nANc0h7R4/130614-SQLServerNetworkProtocol.png?psid=1)

And yet even Local Telnet 1433 is failing Bizarre!!!
![Image](https://tbw38w.bn1.livefilestore.com/y2pTY67QrSBaZ6_3AJ_TsktCxo0fftsZq7P1fFI3zSt5wkJFdlS9cDGawIrKJrQaZWMdg4CyI_ULpz7xJLLGMiWt_O4NlOP9lxkHVLe2dCtMhs/telnetScreenshot.png?psid=1)

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

brianlala — Fri, 14 Jun 2013 14:46:27 GMT

@webguynj, have you enabled TCP as a protocol on the SQL server? Can you telnet to port 1433 on the SQL server (you might need to install the telnet client first).

On the SQL server, run the following in a cmd window:

netstat -an | find ":1433"

To determine if the SQL server is listening on that port.

Finally as another test for connectivity, are you able to create an ODBC DSN to your SQL instance on the SharePoint server, and successfully test the connection?

Brian

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

webguynj — Fri, 14 Jun 2013 13:29:25 GMT

Clarifying - Using 3.87
Also After the Above fails - I try creating a ODBC Connection to the server and it fails Witht he following Error:
```
SQLState:'01000'
SQL Server Error:10061
[Micorosoft][ODBC SQL Server Driver][TCP/IP Sockets] ConnectionOpen (Connect()).
Connection Failed:
SQL State '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/ip Sockets] SQL Server does ot exist or access denied
```
This is bizarre because I can repeated reproduce this result with cleanly built server

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

webguynj — Fri, 14 Jun 2013 13:20:07 GMT

I have been having this problem consistently now and I am here are my steps to create the issue:
* Have a Domain Server nothing but default policies
* Build Default Windows 2012 Server Called WFE Join to Domain
* Build Default Windows 2012 Server called SQL Join to domain
* Install SQL 2012 on SQL Server using Guildlines from Vlad Catrinescu White Paper
* Create named instance SP2013Dev on port 1433
* Create firewall rule allowing port 1433
* Use AutoSPInstaller 387, and AutoSPInstallerGUI create
* Verify port 1433 in open to SQL server
* Makes Sure SPInstall Account is Admin on Both Servers and SQL SysAdmin
* Basic install Specifying Create Alias true Sections as follows
```
<Database>
<DBServer>SP2013DEV_ALIAS</DBServer>
<DBAlias Create="true" DBInstance="SQL\SP2013" DBPort="" />
<DBPrefix>SP13Dev</DBPrefix>
<ConfigDB>Config</ConfigDB>
</Database>
```
* Run AutoSQInstaller

Output:
```
- Writing config.xml to (Get-Item C:\Users\SVC_SP~1\AppData\Local\Temp).FullName...
--------------------------------------------------------------
- Testing access to SQL server/instance/alias: SP2013DEV_ALIAS
- Trying to connect to "SP2013DEV_ALIAS"... - Fail
--------------------------------------------------------------
- Script halted!
- Connection Error. Check server name, port, firewall.
Press any key to exit...
```

Commented Unassigned: "The local farm is not accessible" [19850]

brianlala — Fri, 14 Jun 2013 11:52:49 GMT

It might be, but if you can I would go back further to a clean server - especially if this is a production environment.

Brian