During Setup of the Configuration Database, the Script ran into the error "max degree of parallelism". This can be configured as described in this TechNet Article:
http://technet.microsoft.com/en-us/library/ms189094.aspx
Isn't this a good thing that can be set by the script itself?
Cheers,
Alex
New-SPConfigurationDatabase : This SQL Server instance does not have the required "max degree of parallelism" setting
of 1. Database provisioning operations will continue to fail if "max degree of parallelism" is not set 1 or the
current account does not have permissions to change the setting. See documentation for details on manually changing
the setting.
At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:970 char:13
+ New-SPConfigurationDatabase -DatabaseName "$configDB" -DatabaseServe ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...urationDatabase:SPCmdletNewSPConfigurationDatabase) [New
-SPConfigurationDatabase], SPException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPConfigurationDatabase
Comments: ** Comment from web user: brianlala **
http://technet.microsoft.com/en-us/library/ms189094.aspx
Isn't this a good thing that can be set by the script itself?
Cheers,
Alex
New-SPConfigurationDatabase : This SQL Server instance does not have the required "max degree of parallelism" setting
of 1. Database provisioning operations will continue to fail if "max degree of parallelism" is not set 1 or the
current account does not have permissions to change the setting. See documentation for details on manually changing
the setting.
At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:970 char:13
+ New-SPConfigurationDatabase -DatabaseName "$configDB" -DatabaseServe ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...urationDatabase:SPCmdletNewSPConfigurationDatabase) [New
-SPConfigurationDatabase], SPException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPConfigurationDatabase
Comments: ** Comment from web user: brianlala **
It states right in the error message: "...the current account does not have permissions to change the setting". It's actually SharePoint that's checking and trying to change the setting on the SQL server - so you have two options: either grant the installation account sysadmin rights on the SQL instance, or pre-configure your SQL instance with MaxDOP=1.
AutoSPInstaller wouldn't be able to prevent this or work around it; it would still need sysadmin rights to set MaxDOP if it wasn't already set. And if we implement a check for sysadmin rights early on, it could cause the script to fail prematurely since these rights aren't strictly required if MaxDOP was already pre-set properly.
Brian