Hi,
I'm unable to install SP2016 beta 2. I'm getting these errors during "Installing Features":
```
- Installing Features...
WARNING: Feature PointPublishing\Feature.xml had failed to install for the following reason: Failed to create receiver
object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingFeatureHandler" for feature
"PointPublishing" (ID: 8c9f9b9e-1f5a-42d5-8918-29b3f1bf27f0).: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingHub\feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Portal, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Portal.PointPublishingHubSiteFeatureReceiver" for feature
"PointPublishingHub" (ID: f8064795-884c-4ac8-b551-d87592ceeac9).: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingPersonal\feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingPersonalSiteFeatureReceiver"
for feature "PointPublishingPersonal" (ID: 1a337c2c-f2c0-4c81-b66a-11ae9a48bf20).: System.ArgumentNullException: Value
cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingTopic\Feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingTopicSiteFeatureReceiver" for
feature "PointPublishingTopic" (ID: a4426c43-c58b-419c-a5bb-883a10d0be7f).: System.ArgumentNullException: Value cannot
be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
- Creating Central Admin site...
- Waiting for Central Admin site...Online
- Updating Central Admin branding text to "Dev"...
- Installing Application Content...
- Checking Default Web Site...Stopping...OK.
- Done initial farm/server config.
```
Not sure if it's related, but further down I get these errors:
```
- Creating Web App "Portal Home"
New-SPWebApplication : An update conflict has occurred, and you must re-try this action. The object SPServer Name=SP201
6 was updated by UTV\SP_Farm, in the OWSTIMER (5548) process, on machine SP2016. View the tracing log for more informa
tion about the conflict.
At C:\BouvetDevSP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2692 char:9
+ New-SPWebApplication -Name $webAppName -ApplicationPool $appPool -Databa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...PWebApplication:SPCmdletNewSPWebApplication) [New-SPWebA
pplication], SPUpdatedConcurrencyException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWebApplication
--------------------------------------------------------------
- Script halted!
- Failed to create web application
```
The strange thing is that if I re-run AutoSPInstaller, everything works as expected...
Any clues?
Comments: ** Comment from web user: CatoAntonsen **
I ended up doing a restart of the computer between installation of binaries and configuration of the farm and then re-launching ASPI after an automatical logon. This solved the problem for me.
Added this in AutoSPInstallerFunctionsCustom.ps1:
```
Function RestartAfterBinaryInstallation([xml]$xmlinput) {
$restartedAfterBinaryInstallation = (Get-ItemProperty "HKLM:\SOFTWARE\AutoSPInstaller").RestartedAfterBinaryInstallation -eq "1"
if ($RestartedAfterBinaryInstallation -eq $false) {
New-ItemProperty -Path "HKLM:\SOFTWARE\AutoSPInstaller" -Name "RestartedAfterBinaryInstallation" -Value 1 -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "AutoAdminLogon" -Value 1 -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "DefaultDomainName" -Value $env:USERDOMAIN -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "DefaultUserName" -Value $env:USERNAME -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "DefaultPassword" -Value $password -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "AutoLogonCount" -Value 1 -PropertyType "Dword" -Force | Out-Null
Set-UserAccountControl 0
New-Item -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\" -Name RunOnce -ErrorAction SilentlyContinue | Out-Null
New-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\RunOnce" -Name AutoSPInstaller -Value "`"$env:dp0\AutoSPInstallerLaunch.bat`" `"$inputFile`"" -Force | Out-Null
Restart-Computer -ErrorAction SilentlyContinue
if (!$?)
{
Write-Warning "Restart failed; there may be (an) other user(s) logged in!"
$forceRestart = Read-Host -Prompt " - Do you want to force a restart? (y/n)"
if ($forceRestart -eq "y") {Restart-Computer -Force}
}
}
}
```
In AutoSPInstallerMain:.ps1
```
Function Setup-Farm
{
__ <...>
ConfigureLanguagePacks $xmlinput
__ RestartBinariesAfterInstallation $xmlinput # <--- ADDED
__ AddManagedAccounts $xmlinput
}
```
Notice, this doesn't handle installation on multiple servers. Maybe it works, maytbe not...
Brian, could you give us a complete AutoSPInstallerInput.xml-file that you know will work? I've tried the one made by autospinstaller.com with no success.
A little background: I've made a set of scripts for my company that creates a complete SharePoint developer environment (in Hyper-V) based on a settings.xml-file, all the way from creating an unattended installation of Windows Server, installation of AD, SQL and SharePoint and then all required dev-software (including Visual Studio). All this is done in a couple of hours with no user interventions needed since restarts and automatically logons are handled by the script(s). Having to manually restart AutoSPInstaller ruined that experience...