Quantcast
Channel: AutoSPInstaller
Viewing all 2279 articles
Browse latest View live

Commented Unassigned: Error during "Installing Features" [22126]

$
0
0
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 **

JohnMCalvert, I wish I could but it's made for use by company only ([Bouvet](https://www.bouvet.no)). We have open positions if you live in Norway, though... ;-)

I can outline the steps though:

1. PowerShell script that takes a XML as input and replaces REPLACEMENT-TOKENS in different configuration files used later:
** UnattendWindows.xml (used for unattende installation of Windows)
** AutoSPInstallerInput.xml (used by AutoSPInstaller for installation of SharePoint)
** Remote.rdp (Used by Remote Desktop Connection Manager for remote connection to new VM when it's starting. That way I can "sit on the console" watching everything install, including during restarts and auto-logons)
2. Using Convert-WindowsImage (https://github.com/Microsoft/Virtualization-Documentation/tree/master/hyperv-tools/Convert-WindowsImage) to create VHDX
3. Mounting VHDX and copying of installation-files during installation, including updated the cusomized configuration files
4. Starting VM which starts the unattended server installation using autorun configured in UnattendWindows.xml
** Rename computer
** Install AD
** Install SQL
** Install SharePoint using AutoSPInstaller
** Install needed applications using [Chocolatey](https://chocolatey.org) packages (including Visual Studio, SharePoint Designer, Notepad++, WinDiff etc etc)
** Automatically configuration of Windows Explorer settings (view hidden/system files), run Windows Update once

In 2-3 hours we have a complete setup ready to start code for a new customer.


New Post: Can AutoSPInstaller add another WFE to the Farm

$
0
0
Thank you for your quick reply as usual Brain,
FYI, this Farm is made in last 2 years, so if i make changes to XML and add WFE3, do think the WFE1 and WFE2 won't affect their configuration and settings? or there will not be any issue for the Farm?

Regards,
Aasmi

Created Unassigned: Function Get-SharePointInstall fails for Foundation [22165]

$
0
0
An issue found when repeating installer script with Foundation binaries already in place, the installer fails to detect the product installed and falls over after invoking setup again. Turns out the Get-SharePointInstall function is specifically looking for the Server class name:

Function Get-SharePointInstall
{
if (Get-Command Get-CimInstance -ErrorAction SilentlyContinue)
{
# New way, borrowed from xSharePoint DSC project (https://github.com/PowerShell/xSharePoint)
if (Get-CimInstance -ClassName Win32_Product -Filter "Name like 'Microsoft SharePoint Server%'")
...

Probably needs to have an additional check for Foundation, if the detection needs to avoid false positives from SP Designer etc.

Created Unassigned: SP2013SP1 + Feb2016CU [22166]

$
0
0
I get odd behaviour in Distributed Cache when installing in two server configuration as WEB (WFE) and APP (AppServer + CentralAdmin) - the APP server's Distributed Cache gets disabled while I try to push this to both servers. With January 2016 CU this worked well but February 2016 this breaks down.

Commented Unassigned: SP2013SP1 + Feb2016CU [22166]

$
0
0
I get odd behaviour in Distributed Cache when installing in two server configuration as WEB (WFE) and APP (AppServer + CentralAdmin) - the APP server's Distributed Cache gets disabled while I try to push this to both servers. With January 2016 CU this worked well but February 2016 this breaks down.
Comments: ** Comment from web user: tommig **

One more thing - if I try to start the distributed cache via Central Admin I get following error :

Sorry, something went wrong
cacheHostInfo is null

Created Unassigned: SP2013SP1 + Jan2016CU - UP Sync stuck at starting synchronization full or increment sync [22168]

$
0
0
SP2013SP1 + Jan2016CU - UP Sync stuck at starting synchronization full or increment sync when I leave the script update the Sync Service in SP to the SP_services account. I fixed the issue by commenting the flowing at the CreateUserProfileServiceApplication function
#UpdateProcessIdentity $profileSyncService
#$profileSyncService.Update()

this tested on 2 env. one on Azure IaaS and another on on client production On-premises

Regards,
Mahmoud Hamed

Created Unassigned: Function AddToHOSTS ($hosts) [22169]

$
0
0
Hello,

first of all I want to tell you that you are doing a great job !!! :)

i have problem with AddToHOSTS function, i use this script for a farm with two servers, i have provisonning Central Administration on one server with his Hostname in url (https://AppServerName) and when i execute script on the second server function add record "127.0.0.1 AppServerName" in host.
This record cause problem for Search Topology configuration because search service admin component is not on this server.

Could you modify script to don't add Central administration url in local host file if Central Administration is not provionned on local server ?

Thank in adavance,
Florent.

New Post: Running AutoSPInstaller within remote PS session

$
0
0
Ohh. seems to be WinRM config issues at my end. Credssp should be configured correctly.

New Post: How to bypass "proceed if you know that #SharePoint is already installed, or Ctrl-C to exit" "y" message?

$
0
0
Sure, make sense. Thanks for the input, brianlala.
Can be closed.

New Post: Running AutoSPInstaller within remote PS session

$
0
0
Can be closed.

Incorrect CredSSP config for WinRm at my side gave tons of funky errors. Pretty much, double hop thing resulting into half of the AutoSPInstaler functions not working, such as querying AD and so on.

Gosh :)

New Post: Multi-tenant config

$
0
0
Hm.. no comments on that?
Guys, would you please at least confirm that multi-tenant config is supported / not supported by AutoSPInstaller?

New Post: Multi-tenant config

$
0
0
In all honesty I've never tried it (having never had a need for multi-tenant myself). So assume at minimum you'd need to perform some customization to support this.

Brian

New Post: Multi-tenant config

$
0
0
I know first hand that the AutoSPInstaller Code is not Multi-Tenant-optimized. It will have to be extended to support that.

Commented Unassigned: SharePoint 2016 - Configuration Error: RPC Server is unavailable [22003]

$
0
0
I don't think this is an issue with the scripts, but hoping someone else has had this problem.

I've been trying to get a copy of the SharePoint 2016 preview up and running and I keep getting an error during the configuration wizard when it's trying to create the config database: An error occurred while getting information about the user sp_farm at server domain.com: The RPC server is unavailable.

The database does get created and I need to delete to try and run again.

The same error is coming up both using the AutoSPInstaller scripts and just trying to run the configuration wizard manually.

Weird thing is in the same dev environment I have no trouble installing SharePoint 2010 or 2013.

A lot of the solutions to this issue mention running ipconfig /flushdns and/or ipconfig /registerdns... but that hasn't changed anything...
Comments: ** Comment from web user: nannari **

Hi,

Did you ever get this figured out? I'm struggling with the same thing right now.

Commented Unassigned: SharePoint 2016 - Configuration Error: RPC Server is unavailable [22003]

$
0
0
I don't think this is an issue with the scripts, but hoping someone else has had this problem.

I've been trying to get a copy of the SharePoint 2016 preview up and running and I keep getting an error during the configuration wizard when it's trying to create the config database: An error occurred while getting information about the user sp_farm at server domain.com: The RPC server is unavailable.

The database does get created and I need to delete to try and run again.

The same error is coming up both using the AutoSPInstaller scripts and just trying to run the configuration wizard manually.

Weird thing is in the same dev environment I have no trouble installing SharePoint 2010 or 2013.

A lot of the solutions to this issue mention running ipconfig /flushdns and/or ipconfig /registerdns... but that hasn't changed anything...
Comments: ** Comment from web user: brianlala **

Let's move/reopen this to the Discussions area since as we've determined it's not an issue with AutoSPInstaller.

Though FWIW "RPC server is unavailable" often indicates a firewall or communications issue over (for example) ports 139 & 445. Also note that SP2016 is still in pre-release.

Brian


Closed Unassigned: SharePoint 2016 - Configuration Error: RPC Server is unavailable [22003]

$
0
0
I don't think this is an issue with the scripts, but hoping someone else has had this problem.

I've been trying to get a copy of the SharePoint 2016 preview up and running and I keep getting an error during the configuration wizard when it's trying to create the config database: An error occurred while getting information about the user sp_farm at server domain.com: The RPC server is unavailable.

The database does get created and I need to delete to try and run again.

The same error is coming up both using the AutoSPInstaller scripts and just trying to run the configuration wizard manually.

Weird thing is in the same dev environment I have no trouble installing SharePoint 2010 or 2013.

A lot of the solutions to this issue mention running ipconfig /flushdns and/or ipconfig /registerdns... but that hasn't changed anything...

Commented Unassigned: SharePoint 2016 - Configuration Error: RPC Server is unavailable [22003]

$
0
0
I don't think this is an issue with the scripts, but hoping someone else has had this problem.

I've been trying to get a copy of the SharePoint 2016 preview up and running and I keep getting an error during the configuration wizard when it's trying to create the config database: An error occurred while getting information about the user sp_farm at server domain.com: The RPC server is unavailable.

The database does get created and I need to delete to try and run again.

The same error is coming up both using the AutoSPInstaller scripts and just trying to run the configuration wizard manually.

Weird thing is in the same dev environment I have no trouble installing SharePoint 2010 or 2013.

A lot of the solutions to this issue mention running ipconfig /flushdns and/or ipconfig /registerdns... but that hasn't changed anything...
Comments: ** Comment from web user: MonkeyMaj1k **

I found this was occuring with any VM that had two NIC's.

Commented Unassigned: dotNetFX4.5 "missing" [22100]

$
0
0
Before first use of AutoSPInstaller 3.99.51 the host (Windows Server 2012 R2 Standard) had all recent dotNet versions installed, including NDP46-KB3045557-x86-x64-AllOS-ENU.exe which 'upgrades' dotNet Framework 4.5 ("dotNetFX45") to 4.6

AutoSPInstaller then stops part way through installation saying that dotNetFX45 is not installed. any attempt to re-install dotNetFX45 then confirms that it is already installed. Further installation of AutoSPInstaller cannot continue.
Comments: ** Comment from web user: PerrySharePoint **

It would be a nice addition to the Auto-SPInstaller exe to check for this problem up front, and fail with an error message referring to a relevant article.

Registry path to check

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client
String value: Version
Check if it does not begin with 4.5

If so, stop and warn user that they need to manually work around SharePoint 2013 incompatibility with .NET 4.6.

I suggest perhaps displaying these three links to the user at that point:

https://support.microsoft.com/en-us/kb/3087184

http://sharepoint.stackexchange.com/questions/61239/this-product-requires-microsoft-net-framework-4-5

http://geekswithblogs.net/bjackett/archive/2015/07/28/be-careful-installing-.net-4.6--visual-studio-2015-with.aspx

Commented Task: Product key dialog shows up during installation ? [22015]

$
0
0
Hello

I want to install a simple single server farm SP2013 Enterprise with your script, and after following all the instructions, Unfortunately at the " - Installing SharePoint 2013 binaries......." step the Product key dialog shows up as shown on the screenshot. Why this is happening ?

Shouldn't the installation proceeds by itself and picks the PIDKey value from the XML file? Why it doesn't?

One-Single farm info:
OS: Windows 2012 R2
SQL Server 2012 SP2
SP2013 media: SP1 Slipstream (Meaning the downloading ISO from MSDN contains SharePoint with SP1 together)

<Configuration Environment="SP2013Farm" Version="3.99.51">
<Install SPVersion="2013">
<ConfigFile>SP2013Farm.xml</ConfigFile>
<InstallDir>C:\Program Files\Microsoft Office Servers</InstallDir>
<DataDir>C:\Program Files\Microsoft Office Servers\SharePoint2013\Data</DataDir>
<PIDKey>MY-100%-CORRECT-KEY-VALUE</PIDKey>
<SKU>Enterprise</SKU>
<OfflineInstall>false</OfflineInstall>
<PauseAfterInstall>false</PauseAfterInstall>
<RemoteInstall Enable="false">
<ParallelInstall>false</ParallelInstall>
</RemoteInstall>
<AutoAdminLogon Enable="true">
<Password>Password</Password>
</AutoAdminLogon>

Could you please help out? Am I doing anything wrong?

Thank you !
Comments: ** Comment from web user: Lucero79 **

I am having the same issue here. Seemed to work fine, and now it's not.

The config.xml file is even named config.xml. I drag it onto the .bat file and the install starts. I can see from the PS window that it's using the config.xml from the right directory. %TEMP% is clear, but maybe there's another %TEMP% location I haven't checked.

Copying and pasting the key isn't an option (is that what armarhsall is suggesting) as the installer will continue and ignore the rest of the config.xml.

Any ideas?

Commented Unassigned: Error during "Installing Features" [22126]

$
0
0
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: CraigHumphrey **

FYI I've updated to the 29 Jan 2016 release of AutoSPInstaller and pushed my config back through AutoSPInstaller.com, but I still get the feature error, again, only the first time I run AutoSPInstaller.

Note: I'm now able to run PSConfigUI.

Viewing all 2279 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>