AutoSPInstaller

The AutoSPInstaller script works fine until it goes to create the content database...PowerShell errors out and says:

'New-SPConfigurationDatabase : This content database requires upgrade and could not be attached in this operation. Use either the [stsadm -o addcontentdb] command or [Mount-SPContentDatabase] cmdlet instead.'

The name of my configuration database is: SharePoint_Config

I am logged onto my SharePoint app server as the farm account, which is a local administrator. The account name is: sp_farm

Firewalls turned off. I can see the database actually getting created on the SQL side, but the script still errors out. I made sure to drop the database each time and make sure its fully gone from the SQL server as well.

Thanks, will be fixed in the next release.

Brian

Not that it has any bearing on it, but you shouldn't be logged in with the farm account, nor should it be a local admin. Instead, use a dedicated install account w/ local admin rights.

More detail on this issue is probably available in the local ULS/setup log. Really strange though, I'm not sure why it would be stating that a brand new DB requires upgrade and could not be attached. Is there any chance it's hitting a different SQL server? Or that an issue occurred installing binaries or CUs earlier in the script?

Brian

Also FYI this would have better been logged as a Discussion item, then if it turns out to be a real issue with AutoSPInstaller I would create an Issue from it.

Brian

Hello Brian,

Would it have any bearing that everything up to and including the latest CU was slipstreamed in?

Thank you,

Michael

I don't think that would have any bearing. Did anything go wrong during the installation phase as far as you can tell?

It could very likely be related to slipstreaming. The process has been broken for a while now. Grab the latest ISO from Microsoft. Download the latest CU and place it in SP/20XX/Updates, AutoSPInstaller has its own method that replaces slipstreaming. Do not slipstream anymore.

Ivan

Hi Brian,

For SP2010 install, i get this error
It seems to halt just when its supposed to create the proxy group.

- Search Query and Site Settings Service already started.
- Enterprise search service application proxy already exists, skipping creation
.
--------------------------------------------------------------
- Script halted!

```
Exception : System.Management.Automation.ParameterBindingArgumentTr
ansformationException: Cannot process argument transfor
mation on parameter 'groups'. Cannot convert the "Defau
lt" value of type "System.String" to type "System.Xml.X
mlElement[]". ---> System.Management.Automation.Argumen
tTransformationMetadataException: Cannot convert the "D
efault" value of type "System.String" to type "System.X
ml.XmlElement[]". ---> System.Management.Automation.PSI
nvalidCastException: Cannot convert the "Default" value
of type "System.String" to type "System.Xml.XmlElement
[]".
at System.Management.Automation.LanguagePrimitives.C
onvertTo(Object valueToConvert, Type resultType, Boolea
n recursion, IFormatProvider formatProvider, TypeTable
backupTypeTable)
at System.Management.Automation.ArgumentTypeConverte
rAttribute.Transform(EngineIntrinsics engineIntrinsics,
Object inputData, Boolean bindingParameters, Boolean b
indingScriptCmdlet)
--- End of inner exception stack trace ---
at System.Management.Automation.ArgumentTypeConverte
rAttribute.Transform(EngineIntrinsics engineIntrinsics,
Object inputData, Boolean bindingParameters, Boolean b
indingScriptCmdlet)
at System.Management.Automation.ParameterBinderBase.
BindParameter(CommandParameterInternal parameter, Compi
ledCommandParameter parameterMetadata, ParameterBinding
Flags flags)
--- End of inner exception stack trace ---
at System.Management.Automation.ParameterBinderBase.
BindParameter(CommandParameterInternal parameter, Compi
ledCommandParameter parameterMetadata, ParameterBinding
Flags flags)
at System.Management.Automation.ParameterBinderContr
oller.BindParameter(UInt32 parameterSets, CommandParame
terInternal argument, MergedCompiledCommandParameter pa
rameter, ParameterBindingFlags flags)
at System.Management.Automation.ParameterBinderContr
oller.BindPositionalParametersInSet(UInt32 validParamet
erSets, Dictionary`2 nextPositionalParameters, CommandP
arameterInternal argument, ParameterBindingFlags flags,
ParameterBindingException& bindingException)
at System.Management.Automation.ParameterBinderContr
oller.BindPositionalParameters(Collection`1 unboundArgu
ments, UInt32 validParameterSets, UInt32 defaultParamet
erSet, Boolean ignoreArgumentsThatLookLikeParameters, P
arameterBindingException& outgoingBindingException)
at System.Management.Automation.ScriptParameterBinde
rController.BindCommandLineParameters(Collection`1 argu
ments)
at System.Management.Automation.ScriptCommandProcess
or.EnterScope()
at System.Management.Automation.ScriptCommandProcess
or.RunClause(ParseTreeNode clause, Object dollarUnderba
r, Object inputToProcess)
at System.Management.Automation.ScriptCommandProcess
or.DoBegin()
at System.Management.Automation.Internal.PipelinePro
cessor.Start(Boolean incomingStream)
at System.Management.Automation.Internal.PipelinePro
cessor.SynchronousExecuteEnumerate(Object input, Hashta
ble errorResults, Boolean enumerate)
TargetObject :
CategoryInfo : InvalidData: (:) [ForEach-Object], ParameterBindin...ma
tionException
FullyQualifiedErrorId : ParameterArgumentTransformationError,Microsoft.PowerShe
ll.Commands.ForEachObjectCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
PipelineIterationInfo : {1, 1}
PSMessageDetails :

```

-----------------------------------
| Automated SP2010 install script |
| Started on: 7/7/2015 11:51:34 AM |
| Aborted: 7/7/2015 11:52:31 AM |
-----------------------------------
PS C:\SP\AutoSPInstaller>

By the way, i left the proxy group as default on first try, on second try, i set the group to direct and still nothing

Hey,

This issue has been fixed in the latest build, can you please re download ASPI.

Thanks,
Ivan

Hello and Thanks Ivan,

I already have the latest I believe that was Released 06012015. <Configuration Version="3.99">

Never mind, it looks like its not fixed yet. For now you can can comment out line 4472 in AutoSPinstallerFunctions.ps1. This line adds the Search Service App to the specified proxy group. You can do this manually after.

Ivan

thanks again Ivan, that worked.

Yes, my bad. I've fixed it in the code but haven't checked it in yet. You can use Ivan's suggested workaround for now.

Brian

I realized today that the SQL Client Alias I have configured using AutoSPInstaller only adds a 64bit alias and not a 32bit alias. This is not a problem for straight SharePoint 2013 but it became a problem when I tried to configure Workflow Manager 1.0 on the server. It was not able to connect with the connection string I supplied because there is not 32bit alias matching the name I have in the string. WorkflowManager will not be the only thing that would need the alias, so I think having it included is pretty much a must-have.

My solution going forward for AutoSPInstaller is that I have modified the function and saved it to my "AutoSPInstallerFunctionsCustom.ps1" file. I've also pasted the modified function below if you're interested.

Function Add-SQLAlias()
{
    <#
    .Synopsis
        Add a new SQL server Alias
    .Description
        Adds a new SQL server Alias with the provided parameters.
        This custom version also adds the 32bit alias for the same.
    .Example
                Add-SQLAlias -AliasName "SharePointDB" -SQLInstance $env:COMPUTERNAME
    .Example
                Add-SQLAlias -AliasName "SharePointDB" -SQLInstance $env:COMPUTERNAME -Port '1433'
    .Parameter AliasName
        The new alias Name.
    .Parameter SQLInstance
                The SQL server Name os Instance Name
    .Parameter Port
        Port number of SQL server instance. This is an optional parameter.
    #>
    [CmdletBinding(DefaultParameterSetName="BuildPath+SetupInfo")]
    param
    (
        [Parameter(Mandatory=$false, ParameterSetName="BuildPath+SetupInfo")][ValidateNotNullOrEmpty()]
        [String]$aliasName = "SharePointDB",

        [Parameter(Mandatory=$false, ParameterSetName="BuildPath+SetupInfo")][ValidateNotNullOrEmpty()]
        [String]$SQLInstance = $env:COMPUTERNAME,

        [Parameter(Mandatory=$false, ParameterSetName="BuildPath+SetupInfo")][ValidateNotNullOrEmpty()]
        [String]$port = ""
    )

    If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\"))) {
        $protocol = "dbmslpcn" # Shared Memory
    }
    else {
        $protocol = "DBMSSOCN" # TCP/IP
    }

    $serverAliasConnection="$protocol,$SQLInstance"
    If ($port -ne "")
    {
         $serverAliasConnection += ",$port"
    }
    $notExist = $true
    $client = Get-Item 'HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client' -ErrorAction SilentlyContinue
    # Create the key in case it doesn't yet exist
    If (!$client) {$client = New-Item 'HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client' -Force}
    $client.GetSubKeyNames() | ForEach-Object -Process { If ( $_ -eq 'ConnectTo') { $notExist=$false }}
    If ($notExist)
    {
        $data = New-Item 'HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo'
    }
    # Add the 64bit Alias
    $data = New-ItemProperty HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo -Name $aliasName -Value $serverAliasConnection -PropertyType "String" -Force -ErrorAction SilentlyContinue
    #
    #
    ###  Below is the part that is new. It's basically the same as the lines above added in but this time it will include the 32bit SQL Client Alias
    $notExist = $true
    $client = Get-Item 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo' -ErrorAction SilentlyContinue
    # Create the key in case it doesn't yet exist
    If (!$client) {$client = New-Item 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client' -Force}
    $client.GetSubKeyNames() | ForEach-Object -Process { If ( $_ -eq 'ConnectTo') { $notExist=$false }}
    If ($notExist)
    {
        $data = New-Item 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo'
    }
    # Add Alias
    $data = New-ItemProperty HKLM:\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo -Name $aliasName -Value $serverAliasConnection -PropertyType "String" -Force -ErrorAction SilentlyContinue
}

Changes in this release: - Fixed case in AutoSPInstallerInput.xml to match what autospinstaller.com expects - Enhanced detection of previous XML schema version w/directions for remediation - Fixed bug in trimming trailing slashes from Data Directory (issue 21911) - Fixed SP2010 search regression introduced in last changeset (issue 21934) - In single-server farms (w/ SQL co-installed, e.g. Dev/Demo environments), AutoSPInstaller will now make the Forefront Identity Manager services dependent on SQL so they will start up properly upon server reboots - Fairly substantial changes to SP2013 search config; you can actually use AutoSPInstaller to reconfigure your search topology! In other words, AutoSPInstaller can now remove search components (in addition to adding components, which it already did) to effectively enable reconfigure a search topology - even on a farm that wasn't originally installed with AutoSPInstaller

If you don't specify DataDir in the xml this function errors as it tries to remove the trailing '\' from a string that is null.
The line:
$dataDir = $dataDir.TrimEnd("\")
needs to be moved from before the line:
if ([string]::IsNullOrEmpty($dataDir)) {$dataDir = "%PROGRAMFILES%\Microsoft Office Servers\$env:spVer.0\Data"}
to after it.
Comments: Resolved with changeset 114414: Changes in this release:

- Fixed case in AutoSPInstallerInput.xml to match what autospinstaller.com expects
- Enhanced detection of previous XML schema version w/directions for remediation
- Fixed bug in trimming trailing slashes from Data Directory (issue 21911)
- Fixed SP2010 search regression introduced in last changeset (issue 21934)
- In single-server farms (w/ SQL co-installed, e.g. Dev/Demo environments), AutoSPInstaller will now make the Forefront Identity Manager services dependent on SQL so they will start up properly upon server reboots
- Fairly substantial changes to SP2013 search config; you can actually use AutoSPInstaller to reconfigure your search topology! In other words, AutoSPInstaller can now remove search components (in addition to adding components, which it already did) to effectively enable reconfigure a search topology - even on a farm that wasn't originally installed with AutoSPInstaller

Package consisting of AutoSPInstaller (v3.x) files. The SharePoint / CodePlex community as always deserves big thanks for support, input and contributions! This release is stable for both SP2010and SP2013 and supports the latest service packs available for each (currently SP2 for 2010 and SP1 for 2013). Also, SharePoint 2010 w/SP2 is now supported on Windows 2012!

Please see the Changesets for a history of changes up to and including the latest release, as well as theFAQ.

Also, have a read through the Known Issues, particularly if you are going to take advantage of the new v3 remote functionality.

Package consisting of AutoSPInstaller (v3.x) files. The SharePoint / CodePlex community as always deserves big thanks for support, input and contributions! This release is stable for both SP2010 and SP2013 and supports the latest service packs available for each (currently SP2 for 2010 and SP1 for 2013). Also, SharePoint 2010 w/SP2 is now supported on Windows 2012!

Please see the Changesets for a history of changes up to and including the latest release, as well as the FAQ.

Also, have a read through the Known Issues, particularly if you are going to take advantage of the new v3 remote functionality.

Created Unassigned: Error when creating config database [21926]

Edited Issue: Error in CheckConfigFiles [21911]

Commented Unassigned: Error when creating config database [21926]

Commented Unassigned: Error when creating config database [21926]

Commented Unassigned: Error when creating config database [21926]

Commented Unassigned: Error when creating config database [21926]

Commented Unassigned: Error when creating config database [21926]

Created Unassigned: SP2010 AutoSPInstaller halts when Cannot convert the "Default" value of type "System.String" to type "System.Xml.XmlElement[]" [21934]

Commented Unassigned: SP2010 AutoSPInstaller halts when Cannot convert the "Default" value of type "System.String" to type "System.Xml.XmlElement[]" [21934]

Commented Unassigned: SP2010 AutoSPInstaller halts when Cannot convert the "Default" value of type "System.String" to type "System.Xml.XmlElement[]" [21934]

Commented Unassigned: SP2010 AutoSPInstaller halts when Cannot convert the "Default" value of type "System.String" to type "System.Xml.XmlElement[]" [21934]

Commented Unassigned: SP2010 AutoSPInstaller halts when Cannot convert the "Default" value of type "System.String" to type "System.Xml.XmlElement[]" [21934]

Commented Unassigned: SP2010 AutoSPInstaller halts when Cannot convert the "Default" value of type "System.String" to type "System.Xml.XmlElement[]" [21934]

Commented Unassigned: SP2010 AutoSPInstaller halts when Cannot convert the "Default" value of type "System.String" to type "System.Xml.XmlElement[]" [21934]

New Post: Function "Add-SQLAlias" does not add a 32bit alias

Source code checked in, #114414

Closed Issue: Error in CheckConfigFiles [21911]

Closed Unassigned: SP2010 AutoSPInstaller halts when Cannot convert the "Default" value of type "System.String" to type "System.Xml.XmlElement[]" [21934]

Released: AutoSPInstaller for SharePoint 2010 + 2013 (Jul 13, 2015)

Updated Release: AutoSPInstaller for SharePoint 2010 + 2013 (Jul 13, 2015)