Got it, thanks Andy - truly and honestly appreciated on my end as well - cheers! Let me know if you have any issues running AutoSPInstaller in the future - you've just earned 'premium support' :)
Brian
Brian
↧
New Post: Donation?
↧
New Post: An update conflict has occurred error when creating service applications with SharePoint 2016
Hello,
Has anyone had issues when using the autobuild script to install SharePoint 2016, the creation of some service accounts hang?
It is generally completely random on if a service application will hang when being created but it is usually happens on the word automation service application, the machine translation service application, or the app management service application.
This does not happen at all with SharePoint 2013. The workaround I have discovered is just to open central admin while the script is still running and delete the hung service application. I then get a error such as:
An update conflict has occurred, and you must re-try this action. The object
WordServiceApplication Name=Word Automation Services was updated by SHAREPOINT\USER, in the w3wp (3320) process,
on machine TEST. View the tracing log for more information about the conflict.
But then the script will continue on creating the other service applications with no problem.
So it seems like me may be related to config cache issues.
If anyone else has seen this or has any recommendations on how it can be fixed?
Thank you!
Has anyone had issues when using the autobuild script to install SharePoint 2016, the creation of some service accounts hang?
It is generally completely random on if a service application will hang when being created but it is usually happens on the word automation service application, the machine translation service application, or the app management service application.
This does not happen at all with SharePoint 2013. The workaround I have discovered is just to open central admin while the script is still running and delete the hung service application. I then get a error such as:
An update conflict has occurred, and you must re-try this action. The object
WordServiceApplication Name=Word Automation Services was updated by SHAREPOINT\USER, in the w3wp (3320) process,
on machine TEST. View the tracing log for more information about the conflict.
But then the script will continue on creating the other service applications with no problem.
So it seems like me may be related to config cache issues.
If anyone else has seen this or has any recommendations on how it can be fixed?
Thank you!
↧
↧
Commented Unassigned: SP2016 - "Portal" Managed Account problem [22225]
Hello!
Respect for all the work guys!
While installing SP2016 RTM on Win Srv 2012 Std + SQL 2014 SP1 everthing goes right (web apps, dbs and sites work fine) until the error is displayed:
__Error Provisioning the User Profiles Service Application__
But before that we can see __"Portal" Managed Account not found. Check your XML!__
This is Because I changed the __Common Name__ of "Portal" account in Online Configurator - after twitching output XML to contain "Portal" as this account's Common Name the Installer Worked fine. It probably should not be editable like __spservice__ account...
I know that Online Configurator is not supported for SP2016, but maybe if it is in the future take this under consideration.
Thanks again for your work! Rock on, Bullvan
Comments: ** Comment from web user: ahaist **
Respect for all the work guys!
While installing SP2016 RTM on Win Srv 2012 Std + SQL 2014 SP1 everthing goes right (web apps, dbs and sites work fine) until the error is displayed:
__Error Provisioning the User Profiles Service Application__
But before that we can see __"Portal" Managed Account not found. Check your XML!__
This is Because I changed the __Common Name__ of "Portal" account in Online Configurator - after twitching output XML to contain "Portal" as this account's Common Name the Installer Worked fine. It probably should not be editable like __spservice__ account...
I know that Online Configurator is not supported for SP2016, but maybe if it is in the future take this under consideration.
Thanks again for your work! Rock on, Bullvan
Comments: ** Comment from web user: ahaist **
Hi There,
I just run into the same issue, when using the latest version with the "Bata" of the online configurator. But even if I use the "Portal" as WebApp name, I get a Issue with the user profile service and could not create any mysites...
_Mysite provisioning failed for user:[i:0#.w|xxxx\xxxx] with correlationid:[95346f9d-60a9-9090-1933-e1ae7d84f9af] on retry attempt:[0] on queue type:[e94a6caa-b0f5-4897-b489-585ca50c7803]. Error:[Microsoft.Office.Server.UserProfiles.PersonalSiteCreateException: A failure was encountered while attempting to create the site. ---> Microsoft.SharePoint.SPException: Cannot complete this action._
Did you have the same issue with the mysite creation? (rights and root site in place)
↧
Created Unassigned: Change "Stop-DefaultWebsite" function logic [22232]
If you removed "Default Web Site" prior to setup SharePoint farm, then "SharePoint Web Services" will have an ID = 1.
When you try to provision first Web App, "SharePoint Web Services" site stopped and you're end up with AccessDenied exception because of STS is not available.
Please remove condition of trying to get Default Web Site by ID = 1:
change line
* $defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.ID -eq 1 -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}
to
* $defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}
When you try to provision first Web App, "SharePoint Web Services" site stopped and you're end up with AccessDenied exception because of STS is not available.
Please remove condition of trying to get Default Web Site by ID = 1:
change line
* $defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.ID -eq 1 -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}
to
* $defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}
↧
Created Unassigned: AutoSPInstaller Stuck on "Creating config database" [22234]
Hi all,
we've a strange issue with setting up a new farm.
While creating the Config DB, the AutoSPInstaller Script gets stuck. No error is thrown.
The config and central admin DB are created but after that, the script seems to get stuck.
SQL rights are all set up, service account checks are ok.
Did anyone encounter that issue before? Any hints on that?
Thanks in advance,
Sebastian
we've a strange issue with setting up a new farm.
While creating the Config DB, the AutoSPInstaller Script gets stuck. No error is thrown.
The config and central admin DB are created but after that, the script seems to get stuck.
SQL rights are all set up, service account checks are ok.
Did anyone encounter that issue before? Any hints on that?
Thanks in advance,
Sebastian
↧
↧
New Post: AutoSPInstaller does not support non english installations.
I realized that autospinstaller does not support non english installations. Reason seems to bee that some localiced value(s?) seems to be hardcoded using english (ie user profile sync permission). Force 1033 or implement resource files. Scenario would be non english installation media.
↧
Reviewed: AutoSPInstaller for SharePoint 201x (Apr 11, 2016)
Rated 5 Stars (out of 5) - I have been building Powershell scripts for years and after discovering this tool, I am happy to move toward using this tool as my primary tool for installations. One other point I would like to mention about SPAutoInstaller is that it is a great reference for learning how to do some nifty things in Powershell. MyProjectExpert / Michael Wharton, MVP Project
↧
Created Unassigned: Function Install-WindowsIdentityFoundation amendment [22238]
Hi There, fooling around with Windows 2016 remote install of WFE,
need to amend the autospinstallerfunctions.ps1 line 6661 to something similar to this...
If (!($remoteQueryOS.Version.Contains("6.2")) -and !($remoteQueryOS.Version.Contains("6.3")) -and !($remoteQueryOS.Version.StartsWith("10"))) # Only perform the stuff below if we aren't on Windows 2012 or 2012 R2 OR 2016
to cope with the new Windows OS. My amended fie attached.
cheers,
Ralph Dalton
need to amend the autospinstallerfunctions.ps1 line 6661 to something similar to this...
If (!($remoteQueryOS.Version.Contains("6.2")) -and !($remoteQueryOS.Version.Contains("6.3")) -and !($remoteQueryOS.Version.StartsWith("10"))) # Only perform the stuff below if we aren't on Windows 2012 or 2012 R2 OR 2016
to cope with the new Windows OS. My amended fie attached.
cheers,
Ralph Dalton
↧
New Post: SharePoint 2016 RTM Fails to find binaries
I built the folder structure as outlined and when I try and run the script using the installer input XML file I get an error message telling me that the application cannot find the SharePoint 2016 binaries.
Changed the AutoSPInstaller.xml file to meet one of the parameters in the launch.bat script and no matter how I name the input file (AutoSPInstallerInput-%COMPUTERNAME%, AutoSPInstallerInput-%Domain%) it will not detect the version or find/run the binaries.
If I right click the batch file and Run as Administrator the application detects the AutoSPInstallerInput.XML file, correctly detects the SharePoint version and attempts to run but obviously doesn't have the service accounts and configuration info I need.
Thoughts?
Changed the AutoSPInstaller.xml file to meet one of the parameters in the launch.bat script and no matter how I name the input file (AutoSPInstallerInput-%COMPUTERNAME%, AutoSPInstallerInput-%Domain%) it will not detect the version or find/run the binaries.
If I right click the batch file and Run as Administrator the application detects the AutoSPInstallerInput.XML file, correctly detects the SharePoint version and attempts to run but obviously doesn't have the service accounts and configuration info I need.
Thoughts?
↧
↧
New Post: Setting Content Access account for Search Service Application
Exception
The search service is not able to connect to the machine that hosts the administration component. Verify that theadministration component '5e97b1f6-4139-4b28-a877-3b55f45032cd' in search application 'Search Service Application' is
in a good state and try again.
+ CategoryInfo : InvalidData: (Microsoft.Offic...viceApplication:SetSearchServiceApplication) [Set-SPEnte+ FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchServiceApplication
+ PSComputerName : CORSP13WEB01
argument(s): "The search service is not able to connect to the machine that hosts the
administration component. Verify that the administration component
'5e97b1f6-4139-4b28-a877-3b55f45032cd' in search application 'Search Service Application' is
in a good state and try again." ---> System.InvalidOperationException: The search service is
not able to connect to the machine that hosts the administration component. Verify that the
administration component '5e97b1f6-4139-4b28-a877-3b55f45032cd' in search application 'Search
Service Application' is in a good state and try again.
at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(SearchServiceApplication
application)
at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.get_SearchApi()
at Microsoft.Office.Server.Search.Administration.Topology.SearchTopology.ThrowIfSearchServic
eApplicationIsPaused()
at Microsoft.Office.Server.Search.Administration.Topology.SearchTopology.Activate()
at CallSite.Target(Closure , CallSite , Object )
--- End of inner exception stack trace ---
at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext
funcContext, Exception exception)
at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame
frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)
at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
at System.Management.Automation.ScriptBlock.InvokeWithPipeImpl(ScriptBlockClauseToInvoke
clauseToInvoke, Boolean createLocalScope, Dictionary`2 functionsToDefine, List`1
variablesToDefine, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object
input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object[] args)
at System.Management.Automation.ScriptBlock.<>c__DisplayClassa.<InvokeWithPipe>b__8()
at System.Management.Automation.Runspaces.RunspaceBase.RunActionIfNoRunningPipelinesWithThre
adCheck(Action action)
at System.Management.Automation.ScriptBlock.InvokeWithPipe(Boolean useLocalScope,
Dictionary`2 functionsToDefine, List`1 variablesToDefine, ErrorHandlingBehavior
errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe,
InvocationInfo invocationInfo, Object[] args)
at System.Management.Automation.ScriptBlock.InvokeUsingCmdlet(Cmdlet contextCmdlet, Boolean
useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input,
Object scriptThis, Object[] args)
at Microsoft.PowerShell.Commands.ForEachObjectCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()CategoryInfo : NotSpecified: (:) [ForEach-Object], MethodInvocationException
FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.ForEachObjectCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at <ScriptBlock>,
\\CORSP13OWA01\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 5092
at CreateEnterpriseSearchServiceApp,
\\CORSP13OWA01\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 4710
at Setup-Services, \\CORSP13OWA01\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1:
line 229
at <ScriptBlock>, \\CORSP13OWA01\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1:
line 411
at <ScriptBlock>, <No file>: line 1PSMessageDetails :
↧
Created Unassigned: SharePoint foundation pid key error [22245]
Error on SharePoint foundation because check pid key. Add check in AutoSPInstallerFunctions if foundation to ignore pid key validity.
↧
New Post: How to provision User Profile without MySite ?
Hi,
I'm setting a SP2013 farm and I'm experiencing an error when the script is trying to create the user profile service application. It seems that it's excepting a value for MySiteHostLocation even though I do not want to use MySite. I only want the script to setup the User Profiles Service Application. I therefore did not specify a webapp of type "MySiteHost" and therefore the tag < MySiteHostLocation> is empty. I guess this is where it fails.
I get the following error message:
Thanks in advance guys
I'm setting a SP2013 farm and I'm experiencing an error when the script is trying to create the user profile service application. It seems that it's excepting a value for MySiteHostLocation even though I do not want to use MySite. I only want the script to setup the User Profiles Service Application. I therefore did not specify a webapp of type "MySiteHost" and therefore the tag < MySiteHostLocation> is empty. I guess this is where it fails.
I get the following error message:
New-SPProfileServiceApplication : Missing an argument for parameter ‘MySiteHostLocation’. Specify a parameter of type ‘Microsoft.Sharepoint.PowerShell.SPSitePipeBind’ and try again.Thanks in advance guys
↧
Commented Issue: Central Admin, on HTTPS, on multiple servers, does not create the additional AAMs on HTTPS [18217]
If I specify for Central Admin to be on HTTPS, and provide multiple server names to host it, the additional servers (I only had 1 additional server in my example) only created the AAM on HTTP, not HTTPS. I fixed it by changing the bindings myself.
Related Issue - perhaps we could provide a URL fro Central Admin instead?
Comments: ** Comment from web user: Florent123 **
Related Issue - perhaps we could provide a URL fro Central Admin instead?
Comments: ** Comment from web user: Florent123 **
Hello,
I encounter the same problem when I deploy the Central Administration HTTPS on two separate servers.
Regards,
Florent
↧
↧
New Post: TerminatingError(Get-SPFarm)
Hi Guys,
AutoSpInstaller has recently stopped working at my organization after we applied Windows updates to our test machine. We're trying to set up SharePoint 2013 SP 1 (15.0.4569.1506) on a Windows Server 2012 R2 box with SQL Server 2014 (12.0.4100.1).
Powershell errors with the message:
PS>TerminatingError(Get-SPFarm): "Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permission to access the database before trying again.
Has anyone come across this before after applying Windows updates? Unfortunately we run the autospinstaller as part of an msi so I don't know which line of code is causing the problem, hence making diagnosing the issue very tricky. I've looked through the AutoSPInstaller related scripts and there are around 20 instances of Get-SPFarm so any assistance with this would be greatly appreciated.
Thanks
Kevin White
AutoSpInstaller has recently stopped working at my organization after we applied Windows updates to our test machine. We're trying to set up SharePoint 2013 SP 1 (15.0.4569.1506) on a Windows Server 2012 R2 box with SQL Server 2014 (12.0.4100.1).
Powershell errors with the message:
PS>TerminatingError(Get-SPFarm): "Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permission to access the database before trying again.
Has anyone come across this before after applying Windows updates? Unfortunately we run the autospinstaller as part of an msi so I don't know which line of code is causing the problem, hence making diagnosing the issue very tricky. I've looked through the AutoSPInstaller related scripts and there are around 20 instances of Get-SPFarm so any assistance with this would be greatly appreciated.
Thanks
Kevin White
↧
Commented Unassigned: AutoSPInstaller Stuck on "Creating config database" [22234]
Hi all,
we've a strange issue with setting up a new farm.
While creating the Config DB, the AutoSPInstaller Script gets stuck. No error is thrown.
The config and central admin DB are created but after that, the script seems to get stuck.
SQL rights are all set up, service account checks are ok.
Did anyone encounter that issue before? Any hints on that?
Thanks in advance,
Sebastian
Comments: ** Comment from web user: MatthiasLoring **
we've a strange issue with setting up a new farm.
While creating the Config DB, the AutoSPInstaller Script gets stuck. No error is thrown.
The config and central admin DB are created but after that, the script seems to get stuck.
SQL rights are all set up, service account checks are ok.
Did anyone encounter that issue before? Any hints on that?
Thanks in advance,
Sebastian
Comments: ** Comment from web user: MatthiasLoring **
Hi Sebastian,
do you facing this issue?
Greetz
Matthias
↧
Created Unassigned: Installing SP2016 with SQLServer2014 SP1 [22256]
Hi
I have spent a few frustrating days trying to get SP2016 to install with SP2014SP1.
I get as far as testing the connect from the SP2016 server to the SQL2014SP1 server and it would fail.
Now the SQL2014SP1 server is using dynamic ports (because SQLServer 2012 is still there using port 1433).
Could I get this to work using the AutoSPInstaller input file and setting create = true for the DB Alias. ? No
So in the end, I handcrafted the DB Alias and setting the Dynamic ports check box to true.
I have spent a few frustrating days trying to get SP2016 to install with SP2014SP1.
I get as far as testing the connect from the SP2016 server to the SQL2014SP1 server and it would fail.
Now the SQL2014SP1 server is using dynamic ports (because SQLServer 2012 is still there using port 1433).
Could I get this to work using the AutoSPInstaller input file and setting create = true for the DB Alias. ? No
So in the end, I handcrafted the DB Alias and setting the Dynamic ports check box to true.
↧
Commented Unassigned: Installing SP2016 with SQLServer2014 SP1 [22256]
Hi
I have spent a few frustrating days trying to get SP2016 to install with SP2014SP1.
I get as far as testing the connection from the SP2016 server to the SQL2014SP1 server and it would fail.
Now the SQL2014SP1 server is using dynamic ports (because SQLServer 2012 is still there using port 1433).
Could I get this to work using the AutoSPInstaller input file and setting create = true for the DB Alias. ? No
So in the end, I handcrafted the DB Alias and setting the Dynamic ports check box to true. (See attachment).
I then set Create="False" in the AutoSPInstallerInput.xml file and it all worked.
So why cannot I use dynamic ports in the AutoSPInstallerInput.xml file ?
Regards
Nigel
Comments: ** Comment from web user: Nigel_Price **
I have spent a few frustrating days trying to get SP2016 to install with SP2014SP1.
I get as far as testing the connection from the SP2016 server to the SQL2014SP1 server and it would fail.
Now the SQL2014SP1 server is using dynamic ports (because SQLServer 2012 is still there using port 1433).
Could I get this to work using the AutoSPInstaller input file and setting create = true for the DB Alias. ? No
So in the end, I handcrafted the DB Alias and setting the Dynamic ports check box to true. (See attachment).
I then set Create="False" in the AutoSPInstallerInput.xml file and it all worked.
So why cannot I use dynamic ports in the AutoSPInstallerInput.xml file ?
Regards
Nigel
Comments: ** Comment from web user: Nigel_Price **
finished question
↧
↧
Commented Unassigned: Installing SP2016 with SQLServer2014 SP1 [22256]
Hi
I have spent a few frustrating days trying to get SP2016 to install with SP2014SP1.
I get as far as testing the connection from the SP2016 server to the SQL2014SP1 server and it would fail.
Now the SQL2014SP1 server is using dynamic ports (because SQLServer 2012 is still there using port 1433).
Could I get this to work using the AutoSPInstaller input file and setting create = true for the DB Alias. ? No
So in the end, I handcrafted the DB Alias and setting the Dynamic ports check box to true. (See attachment).
I then set Create="False" in the AutoSPInstallerInput.xml file and it all worked.
So why cannot I use dynamic ports in the AutoSPInstallerInput.xml file ?
Regards
Nigel
Comments: ** Comment from web user: brianlala **
I have spent a few frustrating days trying to get SP2016 to install with SP2014SP1.
I get as far as testing the connection from the SP2016 server to the SQL2014SP1 server and it would fail.
Now the SQL2014SP1 server is using dynamic ports (because SQLServer 2012 is still there using port 1433).
Could I get this to work using the AutoSPInstaller input file and setting create = true for the DB Alias. ? No
So in the end, I handcrafted the DB Alias and setting the Dynamic ports check box to true. (See attachment).
I then set Create="False" in the AutoSPInstallerInput.xml file and it all worked.
So why cannot I use dynamic ports in the AutoSPInstallerInput.xml file ?
Regards
Nigel
Comments: ** Comment from web user: brianlala **
Best not to use dynamic ports IMHO. Just pick another port other than 1433 and specify it in the alias config.
Personally I've never tried, because most customers would select a static, non-standard port and disable the Browser service and/or hide the instance.
Brian
↧
New Post: TerminatingError(Get-SPFarm)
I'd suggest you run the script outside the context of the MSI just to see where it's failing. Personally I've not run into this FWIW.
Brian
Brian
↧
New Post: How to provision User Profile without MySite ?
Regardless of whether you want to use MySites, you need a MySiteHostLocation if provisioning UPSA. You can always restrict site creation permissions etc. afterwards to prevent folks from actually creating/using a MySite or its features.
Brian
Brian
↧