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

Created Unassigned: Microsoft SharePoint is not supported with version 4.0.30319.34209 of the Microsoft .Net Runtime [22199]

March 10, 2016, 1:51 pm
$
0
0
I am getting and error when using auto spinstaller to create my 2010 farm:

Microsoft SharePoint is not supported with version 4.0.30319.34209 of the Microsoft .Net Runtime

What have I done wrong?


- SharePoint 2010 binary file installation done!
Enter "y" to proceed with farm configuration: y
--------------------------------------------------------------
- Adding XXXX\svcspfarmdev to local Administrators (only for install)...
--------------------------------------------------------------
--------------------------------------------------------------
- Loading SharePoint PowerShell Snapin...
--------------------------------------------------------------
--------------------------------------------------------------
- Checking farm membership for GLBWSS202 in "WSS_Config"...Not joined yet.
- Attempting to join farm on "WSS_Config"...
- No existing farm found.
- __Creating config database "WSS_Config"...
New-SPConfigurationDatabase : Microsoft SharePoint is not supported with
version 4.0.30319.34209 of the Microsoft .Net Runtime.
At D:\install\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1710 char:13
__+ New-SPConfigurationDatabase -DatabaseName "$configDB"
-DatabaseServe ...
+
↧
Search

Created Unassigned: Error with SP2016 RTM (trial image) [22207]

March 14, 2016, 7:45 pm
$
0
0
Hey Guys,

just swapped out the Beta install bits for the RTM Trial image bits and got the following error from AutoSPInstaller:

_- Installing Prerequisite Software:
- Could not locate source for .Net Framework 3.5.1
- The PrerequisiteInstaller will attempt to download it.
- Running Prerequisite Installer (offline mode)....Done.
- Prerequisite Installer completed in 00:00:05.
WARNING: 2016-03-15 15:25:45 - Error: Unrecognized command line option
--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
parameter 'Message' because it is null.
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)
TargetObject :
CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningComman
d
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at InstallPrerequisites, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 875
at Run-Install, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184
at <ScriptBlock>, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 379
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :_

Any ideas? Prereq installer returning something unexpected?
↧
↧

New Post: EnterpriseSearchCenter Provisioning

March 15, 2016, 10:41 am
$
0
0
Hi all, i'm new to this fantastic script, and i'm trying to setup my environment.
Everything went correctly (two webapplications created, the main portal and the mysite), but i've a question. How can I create the SearchCenter site collection? Is that possible? Do i have to create another SiteCollection under <SiteCollections> XML node?

Thanks
↧

Commented Unassigned: Error with SP2016 RTM (trial image) [22207]

March 16, 2016, 2:19 pm
$
0
0
Hey Guys,

just swapped out the Beta install bits for the RTM Trial image bits and got the following error from AutoSPInstaller:

```
- Installing Prerequisite Software:
- Could not locate source for .Net Framework 3.5.1
- The PrerequisiteInstaller will attempt to download it.
- Running Prerequisite Installer (offline mode)....Done.
- Prerequisite Installer completed in 00:00:05.
WARNING: 2016-03-15 15:25:45 - Error: Unrecognized command line option
--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
parameter 'Message' because it is null.
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)
TargetObject :
CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at InstallPrerequisites, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 875
at Run-Install, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184
at <ScriptBlock>, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 379
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
```

Any ideas? Prereq installer returning something unexpected?
Comments: ** Comment from web user: skaggej **

![Image](I've got a volume with all my AutoSPInstaller and SharePoint bits on it that I use for my farm builds. The SharePoint 2016 install failed with the message above, but the SharePoint 2013 install succeeded immediately after 2016 failed.

Comparing the folder structures, I found that the SP2013 version has an "sxs" folder in the prerequisiteinstallerfiles directory. That directory is empty, but even so, I found that the SP2016 version did not already have that folder...so I created it - add an "sxs" folder in the AutoSPInstaller/SP/2016/SharePoint/prerequisiteinstallerfiles directory.

Running the SP2016 install again, I was able to get one step further and it now acknowledges that .Net Framework 3.5.1 is installed, but it still failed with a similar message.

↧

Commented Unassigned: Error with SP2016 RTM (trial image) [22207]

March 16, 2016, 2:20 pm
$
0
0
Hey Guys,

just swapped out the Beta install bits for the RTM Trial image bits and got the following error from AutoSPInstaller:

```
- Installing Prerequisite Software:
- Could not locate source for .Net Framework 3.5.1
- The PrerequisiteInstaller will attempt to download it.
- Running Prerequisite Installer (offline mode)....Done.
- Prerequisite Installer completed in 00:00:05.
WARNING: 2016-03-15 15:25:45 - Error: Unrecognized command line option
--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
parameter 'Message' because it is null.
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)
TargetObject :
CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at InstallPrerequisites, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 875
at Run-Install, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184
at <ScriptBlock>, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 379
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
```

Any ideas? Prereq installer returning something unexpected?
Comments: ** Comment from web user: skaggej **

I've attached a screenshot of the updated 2016 folder structure.

↧
↧

Created Unassigned: Getting error when re-running AutoSPInstaller to install some other services [22214]

March 20, 2016, 7:26 am
$
0
0
Hi,
I am getting the following error when re-running the latest version of AutoSPInstaller 2nd time.
Any ideas?
- Granting rights to Metadata Service Application:
Get-SPServiceApplicationSecurity : Cannot convert 'System.Object[]' to the type
'Microsoft.SharePoint.PowerShell.SPServiceApplicationPipeBind' required by parameter 'Identity'. Specified method is
not supported.
At D:\03-SharePoint\01-AutoSPInstaller2013\AutoSPInstallerFunctions.ps1:2452 char:80
+ $metadataServiceAppSecurity = Get-SPServiceApplicationSecurity $ ...
+ ~
+ CategoryInfo : InvalidArgument: (:) [Get-SPServiceApplicationSecurity], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgument,Microsoft.SharePoint.PowerShell.SPCmdletGetServiceApplicationSecur
ity
↧

Commented Unassigned: Getting error when re-running AutoSPInstaller to install some other services [22214]

March 20, 2016, 7:30 am
$
0
0
Hi,
I am getting the following error when re-running the latest version of AutoSPInstaller 2nd time.
Any ideas?
- Granting rights to Metadata Service Application:
Get-SPServiceApplicationSecurity : Cannot convert 'System.Object[]' to the type
'Microsoft.SharePoint.PowerShell.SPServiceApplicationPipeBind' required by parameter 'Identity'. Specified method is
not supported.
At D:\03-SharePoint\01-AutoSPInstaller2013\AutoSPInstallerFunctions.ps1:2452 char:80
+ $metadataServiceAppSecurity = Get-SPServiceApplicationSecurity $ ...
+ ~
+ CategoryInfo : InvalidArgument: (:) [Get-SPServiceApplicationSecurity], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgument,Microsoft.SharePoint.PowerShell.SPCmdletGetServiceApplicationSecur
ity
Comments: ** Comment from web user: prawnz **

Please delete this issue. Just found out the code was crashing because I had created a 2nd Managed Metadata Service.

↧

Created Unassigned: AddResourcesLink function is broken [22215]

March 20, 2016, 8:24 am
$
0
0
When AutoSPInstaller reaches the point that it calls AddResourcesLink and the item already exist. It will throw the following

```
Exception : System.Management.Automation.RuntimeException: Cannot convert value "URL" to type
"System.Int32". Error: "Input string was not in a correct format." --->
System.Management.Automation.PSInvalidCastException: Cannot convert value "URL" to type
"System.Int32". Error: "Input string was not in a correct format." --->
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number,
NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.ComponentModel.Int32Converter.FromString(String value, NumberFormatInfo
formatInfo)
at System.ComponentModel.BaseNumberConverter.ConvertFrom(ITypeDescriptorContext context,
CultureInfo culture, Object value)
--- End of inner exception stack trace ---
at System.Management.Automation.LanguagePrimitives.ConvertStringToInteger(Object
valueToConvert, Type resultType, Boolean recursion, PSObject originalValueToConvert,
IFormatProvider formatProvider, TypeTable backupTable)
at CallSite.Target(Closure , CallSite , Object , String , String )
at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0,
T1 arg1, T2 arg2)
at System.Management.Automation.Interpreter.DynamicInstruction`4.Run(InterpretedFrame frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)
--- 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()
TargetObject :
CategoryInfo : InvalidArgument: (:) [ForEach-Object], RuntimeException
FullyQualifiedErrorId : InvalidCastFromStringToInteger,Microsoft.PowerShell.Commands.ForEachObjectCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at AddResourcesLink, D:\03-SharePoint\01-AutoSPInstaller2013\AutoSPInstallerFunctions.ps1:
line 7458
at <ScriptBlock>, D:\03-SharePoint\01-AutoSPInstaller2013\AutoSPInstallerFunctions.ps1: line
5061
at CreateEnterpriseSearchServiceApp,
D:\03-SharePoint\01-AutoSPInstaller2013\AutoSPInstallerFunctions.ps1: line 4614
at Setup-Services, D:\03-SharePoint\01-AutoSPInstaller2013\AutoSPInstallerMain.ps1: line 227
at <ScriptBlock>, D:\03-SharePoint\01-AutoSPInstaller2013\AutoSPInstallerMain.ps1: line 409
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
```


changing the function to the following will ensure that there are no duplicates of the resources link and fixing the issue above
```
Function AddResourcesLink([string]$title,[string]$url)
{
$centraladminapp = Get-SPWebApplication -IncludeCentralAdministration | ? {$_.IsAdministrationWebApplication}
$centraladminurl = $centraladminapp.Url
$centraladmin = (Get-SPSite $centraladminurl)

$item = $centraladmin.RootWeb.Lists["Resources"].Items | Where { $_.Name -eq $title }

If ($item -eq $null )
{
$item = $centraladmin.RootWeb.Lists["Resources"].Items.Add();
}
else
{
$item.Delete();
$item.Update();
$item = $centraladmin.RootWeb.Lists["Resources"].Items.Add();
}

$url = $centraladminurl + $url + ", $title";
$item["URL"] = $url;
$item.Update();
}
```
↧
Search

Closed Unassigned: Getting error when re-running AutoSPInstaller to install some other services [22214]

March 21, 2016, 7:35 pm
$
0
0
Hi,
I am getting the following error when re-running the latest version of AutoSPInstaller 2nd time.
Any ideas?
- Granting rights to Metadata Service Application:
Get-SPServiceApplicationSecurity : Cannot convert 'System.Object[]' to the type
'Microsoft.SharePoint.PowerShell.SPServiceApplicationPipeBind' required by parameter 'Identity'. Specified method is
not supported.
At D:\03-SharePoint\01-AutoSPInstaller2013\AutoSPInstallerFunctions.ps1:2452 char:80
+ $metadataServiceAppSecurity = Get-SPServiceApplicationSecurity $ ...
+ ~
+ CategoryInfo : InvalidArgument: (:) [Get-SPServiceApplicationSecurity], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgument,Microsoft.SharePoint.PowerShell.SPCmdletGetServiceApplicationSecur
ity
Comments: Closing as requested.
↧
↧

Commented Unassigned: Error with SP2016 RTM (trial image) [22207]

March 21, 2016, 7:39 pm
$
0
0
Hey Guys,

just swapped out the Beta install bits for the RTM Trial image bits and got the following error from AutoSPInstaller:

```
- Installing Prerequisite Software:
- Could not locate source for .Net Framework 3.5.1
- The PrerequisiteInstaller will attempt to download it.
- Running Prerequisite Installer (offline mode)....Done.
- Prerequisite Installer completed in 00:00:05.
WARNING: 2016-03-15 15:25:45 - Error: Unrecognized command line option
--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
parameter 'Message' because it is null.
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)
TargetObject :
CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at InstallPrerequisites, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 875
at Run-Install, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184
at <ScriptBlock>, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 379
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
```

Any ideas? Prereq installer returning something unexpected?
Comments: ** Comment from web user: brianlala **

One of the prerequisites (.Net Framework) was updated for RTM (from 4.5.2 to 4.6) which could be causing this. Check the newer version of AutoSPInstaller coming through any minute now.

Brian

↧

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

March 21, 2016, 7:42 pm
$
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.
Comments: ** Comment from web user: brianlala **

AddToHOSTS should never add the Central Admin URL to the HOSTS file. Have you specified other web apps that are host-named?

Brian

↧

Commented Unassigned: Why Add-SPShellAdmin fails [22139]

March 21, 2016, 7:47 pm
$
0
0
The error:

“Cannot add <user> to the SharePoint_Shell_Access role of the database SharePoint_Config_<Guid>. A possible cause of this error is that the account name was already added to the database as a login using a different user name than the account name.”

The DB_Owner Role is replaced by the SP_DataAccessRole in SharePoint 2013. This role is detailed here:

https://technet.microsoft.com/EN-US/library/cc678863.aspx#Section4

_The SP_DATA_ACCESS role is the default role for database access and should be used for all object model level access to databases. Add the application pool account to this role during upgrade or new deployments.


Note:

The SP_DATA_ACCESS role replaces the db_owner role in SharePoint 2013.

The SP_DATA_ACCESS role will have the following permissions:

Grant EXECUTE or SELECT on all SharePoint stored procedures and functions
Grant SELECT on all SharePoint tables
Grant EXECUTE on User-defined type where schema is dbo
Grant INSERT on AllUserDataJunctions table
Grant UPDATE on Sites view
Grant UPDATE on UserData view
Grant UPDATE on AllUserData table
Grant INSERT and DELETE on NameValuePair tables
Grant create table permission
_

This is the role given to the Install account by the farm account during the user profile sync service app creation instead of the db_owner role. This is because the Add-SPShellAdmin in SP 2013 starts by looking for the SP_Data_Access role on the database and if this role is found it is used. if not it uses the db_owner role.
The SP_Data_Access role does not give the install or setup account enough permissions to run an add-spshelladmin for other service accounts against the upsa databases (profile and social dbs). setting the setup account as db_owner on those dbs fixes this. Giving the setup account sysadmin rights fixes it too.

So I guess a new fix is on the way Brian :-)
Comments: ** Comment from web user: brianlala **

Hmm I've not run into this myself, probably because I always insist that the setup account has sysadmin on the SQL instance from the get-go. Yet another reason why I will continue to insist on this I guess :)

Brian

↧

Updated Wiki: Home

March 21, 2016, 7:50 pm
$
0
0

Project Description
Automated SharePoint 2010/2013/2016 PowerShell-based installation script.

Introducing AutoSPInstaller v3 with numerous enhancements including:

  • Granular SQL server assignment and aliasing for (almost) every service/web app (for control freaks)
  • Centralized, remote installation to all farm servers
  • Ability to specify any XML input file, by passing it as an argument to AutoSPInstallerLaunch.bat
  • Several tweaks & fixes
  • Experimental support for SharePoint Foundation 2013 (as of 3.98 release)

Be sure to check out the new AutoSPInstaller Online - it's AutoSPInstallerGUI in a browser (& on steroids!)

AutoSPInstaller works with SharePoint 2016, SharePoint 2013 (including SP1) and SharePoint 2010 with Service Pack 1 & 2. It takes advantage of some of the cmdlet updates in the newer SharePoint releases, while remaining largely backward-compatible older versions.

Newer versions often include updates to the input file XML schema, so make sure you compare any of your existing XML files to the newest AutoSPInstallerInput.XML. See below for highlights of changes in v3.x.

This being a CodePlex open-source project, it must be stressed that AutoSPInstaller itself isnot supported by Microsoft - if you contact them with a SharePoint support issue, please mention to them if AutoSPInstaller was used to perform your farm build. This doesnot mean your farm and servers won't be supported, instead it will help support engineers better assess your particular issue.

AutoSPInstaller has been used as the go-to SharePoint installation method for hundreds of SharePoint practitioners & partners worldwide! If you or your organization find AutoSPInstaller useful, making a donation (any amount) is a great way to support the ongoing development & improvement of the project.

Donate to AutoSPInstaller!

New! Frequently Asked Questions

This project consists of PowerShell scripts, an XML input file, and a standard windows batch file (to kick off the process) which together provide a quick and near-unattended installation and initial configuration (Service Apps, My Sites) of Microsoft SharePoint Server 2010/2013/2016. Works on Windows 2008 (though I hardly test on that OS these days), 2008 R2, Windows 2012 / 2012 R2 and Windows Server 2016 Technical Preview 3 (x64 only of course).

Perfect for repeated Virtual Machine-based installs/tear-downs, etc., but also great for production installs where you want to guarantee consistency and minimize data entry glitches. The immediate value is for installing and configuring the first/only server in a farm, but also supports using either server-specific input files or a single, all-encompassing input file for running the script on all farm servers (with parameters - e.g. for the service apps - set according to your desired topology).

"But doesn't SharePoint 2010 have a nice wizard now that does all this for me??" - Yes, and it's a huge improvement over what was available in MOSS 2007. However if you've ever seen the 'DBA nightmare' left behind on your SQL server after the Farm Configuration Wizard has completed (GUID'ed databases with inconsistent naming, etc.):



...then you'll see the value in having consistently-named but automatically-created databases:

DatabaseList-Clean

The scripts (Franken-scripts, really...) leverage previously-available resources (as PowerShell has now taken its place asthe automation platform for SharePoint) such as: Zach Rosenfield's blog, Jos Verlinde's script for creating a Farm, Gary Lapointe's Enterprise Search script functions and other miscellaneous tidbits in the wild.

The scripted process will:</form>

  • Re-launch itself in an elevated process to deal with User Access Control
  • Check the operating system of the target server
  • Prompt you to enter allmost (in progress) service accounts, passwords and the farm passphrase, unless you opt to just specify them in the AutoSPInstallerInput.xml
  • Validate connectivity and permissions to your SQL instance/alias
  • Validate the farm passphrase (for complexity), as well as the service account/password combinations specified in the input XML file
  • Automatically download and install platform-specific pre-requisites (e.g. IIS, .Net Framework) using the Prerequisiteinstaller.exe. You can also pre-download all the prerequisites/hotfixes usingthis script, then specify <OfflineInstall>true</OfflineInstall> in your AutoSPInstallerInput.xml instead of having Prerequisiteinstaller try to download fixes at script runtime.
  • Optionally disable some unnecessary Windows services, CRL checking and the dreaded IE Enhanced Security Configuration
  • Install the SharePoint binaries using an (optionally, server-specific) config.xml for input
  • Optionally install the Office Web Applications (OWA) 2010 binaries using config-OWA.xml for input
  • Create the Farm (Config & Central Admin content databases, Central Admin site, help collections, etc.)
  • Optionally configure and start many SharePoint services and service applications; currently the script can provision:
    • User Profile Service Application
    • User Profile Synchronization Service
    • Metadata Service Application
    • SharePoint Foundation User Code Service
    • State Service Application
    • Usage and Health Service Application
    • PowerPivot Service Application (removed due to complexity/misunderstandings around order of installation etc.)
    • Secure Store Service
    • Enterprise Search Service Application
    • Web Analytics Service Application
    • Outgoing Email
    • Business Data Connectivity Service Application
    • Excel Service Application
    • Access Service Application
    • PerformancePoint Service Application
    • Visio Graphics Service Application
    • Word Automation (Conversion) Service Application
    • The Office Web Applications 2010 service apps:
      • PowerPoint Service Application
      • Word Viewing Service Application
      • Excel Service Application (if not already provisioned by virtue of having an Enterprise license)
  • Create the main Portal web app and site collection (will try to provision and/or assign a certificate, too - all you need is an https://-based URL in the input XML)
  • Create/configure your My Sites web app and site collection (will also try to provision and/or assign a certificate if you have an https://-based URL in the Input XML)
  • Configure paths and options for both IIS and SharePoint (ULS) logging according to your preferences
  • (NEW) Discover other target servers in your farm (based on values in AutoSPInstallerInput.xml) and remote into each of them to perform the installation process (if <RemoteInstall> istrue)
  • Configure PDF indexing and icon display within SharePoint 2010 – effectively resolving what many consider to be a long-standing omission in the product in just a few seconds
  • Optionally install ForeFront Protection 2010 for SharePoint if the binaries are found in the correct path (see below)
  • Launch IE to display Central Administration, Portal and My Sites, and view the results of your hard work (just in time for your return from lunch)
  • Log all activity to a file on the current user's desktop, and pop open the log file for review when finished.

There are several input parameters to define in the input XML file (which illustrates how much stuff you really have to plan & gather during a regular SharePoint install). However this is a one-time-per-install effort, and the trade-off includes hours saved and better spent elsewhere (see lunch above) and an avoidance of the risks involved (typos, missed settings etc.) during manual installations.

New in v3:

  • Centralized, remote install of every SharePoint server in your farm using PowerShell remoting
  • Support for parallel binary installations, whether remote install is enabled or not (useful for speeding up multi-server farm installs)
  • Ability to specify a different SQL server/instance for each web application and service application, plus support for creating an alias for each SQL instance
  • Screen output and log both now display the elapsed time to install SharePoint and Office Web App binaries
  • Specify an arbitrary XML input file by passing the XML file name as an argument, or just dragging it onto AutoSPInstallerLaunch.bat

The full v3 change log can be found within the CodePlex source code changesets for the project. Also, see the post on my blog at spinsiders.com that provides an overview of the new features & fixes.

New in v2.5:
The ability to use a single AutoSPInstallerInput.XML file for your entire farm, and simply include the names of servers (comma-delimited) on which you want particular service instances or service applications installed. This works by using the Provision="" and Start="" attributes; for example, to provision the managed metadata service on your 2 app servers, you would specify:

<ManagedMetadataServiceApp Provision="SPAPPSRV1, SPAPPSRV2"
...

Further, the old way of specifying <ManagedMetadataServiceApp Provision="true"... still works, if you want to continue using a different XML input file for each server.

See the release notes associated with the original 2.5 changeset here for a more complete list of changes.

New in v2:

  • MAJOR code and XML schema refactoring effort by Andrew Woodward of 21apps to enable (among other things) easier editing and extending via a custom functions script file.
  • Both the launch batch file and the User Profile Service App creation (as farm account)self-elevate so no more need to right-click, Run as Administrator to successfully run AutoSPInstaller on a server with User Access Control (UAC) enabled!
  • Enterprise Search now properly sets both the service account and the crawl (content access) account
  • Much better multi-server farm support. Services can be tweaked to start on the servers you wish, and service applications won't be erroneously re-created on subsequent servers, etc.
  • Portal super user and super reader accounts can now be configured per best practices
  • Overall the install experience and results are more in line with community best practices; as always, this is a community-inspired and driven effort!

In addition to the scripts, you should create an installation source (local or shared) containingthe entire extracted contents of the SP201x install package. The zip package will by default create most of this folder structure when you extract it. When you're done, your folder structure should look something like this (Note: updated for v3):

\SP\AutoSPInstaller\AutoSPInstallerLaunch.bat
\SP\AutoSPInstaller\AutoSPInstallerInput.xml
\SP\AutoSPInstaller\AutoSPInstallerMain.ps1
\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1
\SP\AutoSPInstaller\AutoSPInstallerFunctionsCustom.ps1
\SP\AutoSPInstaller\AutoSPInstallerConfigureRemoteTarget.ps1
\SP\AutoSPInstaller\config.xml
\SP\201x\SharePoint\<installation files & folders>
\SP\201x\SharePoint\PreRequisiteInstallerFiles\
\SP\201x\SharePoint\Updates\ (extract Service Pack + Cumulative Updates here. NOTE not all updates support slipstreaming!)
\SP\2013\ProjectServer\ (optional; copy/extract the contents of the Project Server 2013 DVD/ISO here)
\SP\2013\ProjectServer\Updates (optional, for slipstreaming Service Packs and Public/Cumulative Updates. NOTE not all updates support slipstreaming!)

\SP\201x\LanguagePacks\xx-xx\ (optional)
\SP\201x\LanguagePacks\xx-xx\Updates\ (optional; extract Language Pack Service Pack / Cumulative Updates here)
OR
\SP\201x\LanguagePacks\<ServerLanguagePack_XX-XX.exe> (optional)
\SP\2010\OfficeWebApps\ (optional; only required/supported with SP2010)
\SP\2010\PDF\ (optional; only required/supported with SP2010)
\SP\2010\ForeFront\<ForeFront Protection 2010 for SharePoint install files> (optional, only required/supported with SP2010)

Note that x in the paths above is a0 or a 3 depending on whether you're installing SP2010 or SP2013. Spaces in the path to AutoSPInstallerLaunch.bat will cause the script to blow up, so avoid them.

Useful references:

  • autospinstaller.com - new online UI for editing/validating input XML
  • Config.xml reference (SharePoint Server)
  • List of SharePoint Templates Codes and description
  • ULSViewer - best SharePoint log viewer out there, displays events in real-time and super useful for troubleshooting farm, service and service application provisioning issues.
  • I also highly recommend slipstreaming SharePoint 2010 service packs, cumulative updates and hotfixes into your installation source too, to further automate the process. Just place extracted patches in the\Updates\ path listed above, and they'll be automatically applied during the SharePoint binary installation process! Todd Klindt provides a great overview of the processhere.


Finally, I highly recommend working on your XML input file using a good editor like Notepad++ or good old Visual Studio - this helps a ton, especially to highlight any errors.Be especially mindful of invalid characters such as $ & " in your passwords etc.! Many script blow-up errors can be attributed to illegal characters or syntax errors in the XML. Finally, once you've populated your XML file with your environment/server specifics and before you attempt to run the script, pass the XML through a validator likethis.

↧
↧

Closed Unassigned: Error with SP2016 RTM (trial image) [22207]

March 21, 2016, 7:57 pm
$
0
0
Hey Guys,

just swapped out the Beta install bits for the RTM Trial image bits and got the following error from AutoSPInstaller:

```
- Installing Prerequisite Software:
- Could not locate source for .Net Framework 3.5.1
- The PrerequisiteInstaller will attempt to download it.
- Running Prerequisite Installer (offline mode)....Done.
- Prerequisite Installer completed in 00:00:05.
WARNING: 2016-03-15 15:25:45 - Error: Unrecognized command line option
--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
parameter 'Message' because it is null.
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)
TargetObject :
CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at InstallPrerequisites, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 875
at Run-Install, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184
at <ScriptBlock>, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 379
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
```

Any ideas? Prereq installer returning something unexpected?
Comments: Resolved with changeset 116702: Changes in this release:

- Supports SharePoint 2016 RTM!
- Updated list of offline prerequisites to include .Net Framework 4.6
- New function Install-AppFabricCU: attempts to install AppFabric 1.1 CU 4, 5, 6 or 7 if any of those CU packages is found in the offline prerequisites path (starting with most recent)
- Update to AssignCert function to remove trailing slash, if found (thanks Kevin Kirkpatrick)
- Better handling of Distributed Cache and Foundation Web Application service provisioning in relevant MinRole scenarios
- ConfigureFoundationWebApplicationService function will now start the Web Application service if it has been requested for a particular server but detects it isn't running
↧

Released: AutoSPInstaller for SharePoint 201x (Mar 21, 2016)

March 21, 2016, 8:10 pm
$
0
0
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 SharePoint 2010, 2013and SharePoint 2016 RTM, and supports the latest service packs available for each (currently SP2 for 2010 and SP1 for 2013).

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 and the News on AutoSPInstaller.com, particularly if you are going to take advantage of things like the new v3 remote functionality and support for SharePoint 2016 Preview.
↧
Search

Updated Release: AutoSPInstaller for SharePoint 201x (Mar 21, 2016)

March 21, 2016, 8:10 pm
$
0
0
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 SharePoint 2010, 2013 and SharePoint 2016 RTM, and supports the latest service packs available for each (currently SP2 for 2010 and SP1 for 2013).

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 and the News on AutoSPInstaller.com, particularly if you are going to take advantage of things like the new v3 remote functionality and support for SharePoint 2016 Preview.
↧

Updated Wiki: Home

March 21, 2016, 8:12 pm
$
0
0

Project Description
Automated SharePoint 2010/2013/2016 PowerShell-based installation script.

Introducing AutoSPInstaller v3 with numerous enhancements including:

  • Granular SQL server assignment and aliasing for (almost) every service/web app (for control freaks)
  • Centralized, remote installation to all farm servers
  • Ability to specify any XML input file, by passing it as an argument to AutoSPInstallerLaunch.bat
  • Several tweaks & fixes
  • Experimental support for SharePoint Foundation 2013 (as of 3.98 release)

Be sure to check out the new AutoSPInstaller Online - it's AutoSPInstallerGUI in a browser (& on steroids!)

AutoSPInstaller works with SharePoint 2016, SharePoint 2013 (including SP1) and SharePoint 2010 with Service Pack 1 & 2. It takes advantage of some of the cmdlet updates in the newer SharePoint releases, while remaining largely backward-compatible older versions.

Newer versions often include updates to the input file XML schema, so make sure you compare any of your existing XML files to the newest AutoSPInstallerInput.XML. See below for highlights of changes in v3.x.

This being a CodePlex open-source project, it must be stressed that AutoSPInstaller itself isnot supported by Microsoft - if you contact them with a SharePoint support issue, please mention to them if AutoSPInstaller was used to perform your farm build. This doesnot mean your farm and servers won't be supported, instead it will help support engineers better assess your particular issue.

AutoSPInstaller has been used as the go-to SharePoint installation method for hundreds of SharePoint practitioners & partners worldwide! If you or your organization find AutoSPInstaller useful, making a donation (any amount) is a great way to support the ongoing development & improvement of the project.

Donate to AutoSPInstaller!

New! Frequently Asked Questions

This project consists of PowerShell scripts, an XML input file, and a standard windows batch file (to kick off the process) which together provide a quick and near-unattended installation and initial configuration (Service Apps, My Sites) of Microsoft SharePoint Server 2010/2013/2016. With SharePoint-specific OS requirements in mind, AutoSPInstaller works on Windows 2008 (though I hardly test on that OS these days), 2008 R2, Windows 2012 / 2012 R2 and Windows Server 2016 Technical Preview 4 (x64 only of course).

Perfect for repeated Virtual Machine-based installs/tear-downs, etc., but also great for production installs where you want to guarantee consistency and minimize data entry glitches. The immediate value is for installing and configuring the first/only server in a farm, but also supports using either server-specific input files or a single, all-encompassing input file for running the script on all farm servers (with parameters - e.g. for the service apps - set according to your desired topology).

"But doesn't SharePoint have a nice wizard now that does all this for me??" - Yes, and it's a huge improvement over what was available in MOSS 2007. However if you've ever seen the 'DBA nightmare' left behind on your SQL server after the Farm Configuration Wizard has completed (GUID'ed databases with inconsistent naming, etc.):



...then you'll see the value in having consistently-named but automatically-created databases:

DatabaseList-Clean

The scripts (Franken-scripts, really...) leverage previously-available resources (as PowerShell has now taken its place asthe automation platform for SharePoint) such as: Zach Rosenfield's blog, Jos Verlinde's script for creating a Farm, Gary Lapointe's Enterprise Search script functions and other miscellaneous tidbits in the wild.

The scripted process will:</form>

  • Re-launch itself in an elevated process to deal with User Access Control
  • Check the operating system of the target server
  • Prompt you to enter allmost (in progress) service accounts, passwords and the farm passphrase, unless you opt to just specify them in the AutoSPInstallerInput.xml
  • Validate connectivity and permissions to your SQL instance/alias
  • Validate the farm passphrase (for complexity), as well as the service account/password combinations specified in the input XML file
  • Automatically download and install platform-specific pre-requisites (e.g. IIS, .Net Framework) using the Prerequisiteinstaller.exe. You can also pre-download all the prerequisites/hotfixes usingthis script, then specify <OfflineInstall>true</OfflineInstall> in your AutoSPInstallerInput.xml instead of having Prerequisiteinstaller try to download fixes at script runtime.
  • Optionally disable some unnecessary Windows services, CRL checking and the dreaded IE Enhanced Security Configuration
  • Install the SharePoint binaries using an (optionally, server-specific) config.xml for input
  • Optionally install the Office Web Applications (OWA) 2010 binaries using config-OWA.xml for input
  • Create the Farm (Config & Central Admin content databases, Central Admin site, help collections, etc.)
  • Optionally configure and start many SharePoint services and service applications; currently the script can provision:
    • User Profile Service Application
    • User Profile Synchronization Service
    • Metadata Service Application
    • SharePoint Foundation User Code Service
    • State Service Application
    • Usage and Health Service Application
    • PowerPivot Service Application (removed due to complexity/misunderstandings around order of installation etc.)
    • Secure Store Service
    • Enterprise Search Service Application
    • Web Analytics Service Application
    • Outgoing Email
    • Business Data Connectivity Service Application
    • Excel Service Application
    • Access Service Application
    • PerformancePoint Service Application
    • Visio Graphics Service Application
    • Word Automation (Conversion) Service Application
    • The Office Web Applications 2010 service apps:
      • PowerPoint Service Application
      • Word Viewing Service Application
      • Excel Service Application (if not already provisioned by virtue of having an Enterprise license)
  • Create the main Portal web app and site collection (will try to provision and/or assign a certificate, too - all you need is an https://-based URL in the input XML)
  • Create/configure your My Sites web app and site collection (will also try to provision and/or assign a certificate if you have an https://-based URL in the Input XML)
  • Configure paths and options for both IIS and SharePoint (ULS) logging according to your preferences
  • (NEW) Discover other target servers in your farm (based on values in AutoSPInstallerInput.xml) and remote into each of them to perform the installation process (if <RemoteInstall> istrue)
  • Configure PDF indexing and icon display within SharePoint 2010 – effectively resolving what many consider to be a long-standing omission in the product in just a few seconds
  • Optionally install ForeFront Protection 2010 for SharePoint if the binaries are found in the correct path (see below)
  • Launch IE to display Central Administration, Portal and My Sites, and view the results of your hard work (just in time for your return from lunch)
  • Log all activity to a file on the current user's desktop, and pop open the log file for review when finished.

There are several input parameters to define in the input XML file (which illustrates how much stuff you really have to plan & gather during a regular SharePoint install). However this is a one-time-per-install effort, and the trade-off includes hours saved and better spent elsewhere (see lunch above) and an avoidance of the risks involved (typos, missed settings etc.) during manual installations.

New in v3:

  • Centralized, remote install of every SharePoint server in your farm using PowerShell remoting
  • Support for parallel binary installations, whether remote install is enabled or not (useful for speeding up multi-server farm installs)
  • Ability to specify a different SQL server/instance for each web application and service application, plus support for creating an alias for each SQL instance
  • Screen output and log both now display the elapsed time to install SharePoint and Office Web App binaries
  • Specify an arbitrary XML input file by passing the XML file name as an argument, or just dragging it onto AutoSPInstallerLaunch.bat

The full v3 change log can be found within the CodePlex source code changesets for the project. Also, see the post on my blog at spinsiders.com that provides an overview of the new features & fixes.

New in v2.5:
The ability to use a single AutoSPInstallerInput.XML file for your entire farm, and simply include the names of servers (comma-delimited) on which you want particular service instances or service applications installed. This works by using the Provision="" and Start="" attributes; for example, to provision the managed metadata service on your 2 app servers, you would specify:

<ManagedMetadataServiceApp Provision="SPAPPSRV1, SPAPPSRV2"
...

Further, the old way of specifying <ManagedMetadataServiceApp Provision="true"... still works, if you want to continue using a different XML input file for each server.

See the release notes associated with the original 2.5 changeset here for a more complete list of changes.

New in v2:

  • MAJOR code and XML schema refactoring effort by Andrew Woodward of 21apps to enable (among other things) easier editing and extending via a custom functions script file.
  • Both the launch batch file and the User Profile Service App creation (as farm account)self-elevate so no more need to right-click, Run as Administrator to successfully run AutoSPInstaller on a server with User Access Control (UAC) enabled!
  • Enterprise Search now properly sets both the service account and the crawl (content access) account
  • Much better multi-server farm support. Services can be tweaked to start on the servers you wish, and service applications won't be erroneously re-created on subsequent servers, etc.
  • Portal super user and super reader accounts can now be configured per best practices
  • Overall the install experience and results are more in line with community best practices; as always, this is a community-inspired and driven effort!

In addition to the scripts, you should create an installation source (local or shared) containingthe entire extracted contents of the SP201x install package. The zip package will by default create most of this folder structure when you extract it. When you're done, your folder structure should look something like this (Note: updated for v3):

\SP\AutoSPInstaller\AutoSPInstallerLaunch.bat
\SP\AutoSPInstaller\AutoSPInstallerInput.xml
\SP\AutoSPInstaller\AutoSPInstallerMain.ps1
\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1
\SP\AutoSPInstaller\AutoSPInstallerFunctionsCustom.ps1
\SP\AutoSPInstaller\AutoSPInstallerConfigureRemoteTarget.ps1
\SP\AutoSPInstaller\config.xml
\SP\201x\SharePoint\<installation files & folders>
\SP\201x\SharePoint\PreRequisiteInstallerFiles\
\SP\201x\SharePoint\Updates\ (extract Service Pack + Cumulative Updates here. NOTE not all updates support slipstreaming!)
\SP\2013\ProjectServer\ (optional; copy/extract the contents of the Project Server 2013 DVD/ISO here)
\SP\2013\ProjectServer\Updates (optional, for slipstreaming Service Packs and Public/Cumulative Updates. NOTE not all updates support slipstreaming!)

\SP\201x\LanguagePacks\xx-xx\ (optional)
\SP\201x\LanguagePacks\xx-xx\Updates\ (optional; extract Language Pack Service Pack / Cumulative Updates here)
OR
\SP\201x\LanguagePacks\<ServerLanguagePack_XX-XX.exe> (optional)
\SP\2010\OfficeWebApps\ (optional; only required/supported with SP2010)
\SP\2010\PDF\ (optional; only required/supported with SP2010)
\SP\2010\ForeFront\<ForeFront Protection 2010 for SharePoint install files> (optional, only required/supported with SP2010)

Note that x in the paths above is a0 or a 3 depending on whether you're installing SP2010 or SP2013. Spaces in the path to AutoSPInstallerLaunch.bat will cause the script to blow up, so avoid them.

Useful references:

  • autospinstaller.com - new online UI for editing/validating input XML
  • Config.xml reference (SharePoint Server)
  • List of SharePoint Templates Codes and description
  • ULSViewer - best SharePoint log viewer out there, displays events in real-time and super useful for troubleshooting farm, service and service application provisioning issues.
  • I also highly recommend slipstreaming SharePoint 2010 service packs, cumulative updates and hotfixes into your installation source too, to further automate the process. Just place extracted patches in the\Updates\ path listed above, and they'll be automatically applied during the SharePoint binary installation process! Todd Klindt provides a great overview of the processhere.


Finally, I highly recommend working on your XML input file using a good editor like Notepad++ or good old Visual Studio - this helps a ton, especially to highlight any errors.Be especially mindful of invalid characters such as $ & " in your passwords etc.! Many script blow-up errors can be attributed to illegal characters or syntax errors in the XML. Finally, once you've populated your XML file with your environment/server specifics and before you attempt to run the script, pass the XML through a validator likethis.

↧
↧

Commented Unassigned: Error with SP2016 RTM (trial image) [22207]

March 21, 2016, 8:25 pm
$
0
0
Hey Guys,

just swapped out the Beta install bits for the RTM Trial image bits and got the following error from AutoSPInstaller:

```
- Installing Prerequisite Software:
- Could not locate source for .Net Framework 3.5.1
- The PrerequisiteInstaller will attempt to download it.
- Running Prerequisite Installer (offline mode)....Done.
- Prerequisite Installer completed in 00:00:05.
WARNING: 2016-03-15 15:25:45 - Error: Unrecognized command line option
--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
parameter 'Message' because it is null.
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)
TargetObject :
CategoryInfo : InvalidData: (:) [Write-Warning], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteWarningCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at InstallPrerequisites, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 875
at Run-Install, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184
at <ScriptBlock>, \\ctadev02\devteam\SP16\AutoSPInstaller\AutoSPInstallerMain.ps1: line 379
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
```

Any ideas? Prereq installer returning something unexpected?
Comments: ** Comment from web user: CraigHumphrey **

Thanks Brian. Confirmed that this bug is fixed if you a) download the 21 March 2016 edition of AutoSPInstaller and replace the .NET Framework 4.5.2 installer with the 4.6, in the prereq's folder.

Good work!

Installing binaries now...

↧

Created Unassigned: Reboot missed (2016RTM) [22217]

March 21, 2016, 8:30 pm
$
0
0
Usually AutoSPInstaller picks up when a reboot is required (often happens thanks to prerequisite hotfixes), but having just run the 21 March 2016 edition of AutoSPInstaller, it was the Binary Installer that picked up that a reboot is required... Though AutoSPInstaller only saw it as a PreReqCheck fail.

Not so much of a bug as a minor inconvenience.... And plausible that the binary install itself caused the issue... Not sure.

```
--------------------------------------------------------------
- Installing SharePoint 2016 binaries..............................Done.
- SharePoint 2016 setup completed in 00:02:15.
WARNING: 2016/03/22 16:25:56:517::[8692] Error: Catalyst intermediate PreReqCheck has failed Type:
66::PreReqCheckFailure.
--------------------------------------------------------------
- Script halted!
- Review the log file and try to correct any error conditions.
Press any key to exit...
```

I'll update this after I reboot :)
↧

Source code checked in, #116702

March 21, 2016, 7:57 pm
$
0
0
Changes in this release: - Supports SharePoint 2016 RTM! - Updated list of offline prerequisites to include .Net Framework 4.6 - New function Install-AppFabricCU: attempts to install AppFabric 1.1 CU 4, 5, 6 or 7 if any of those CU packages is found in the offline prerequisites path (starting with most recent) - Update to AssignCert function to remove trailing slash, if found (thanks Kevin Kirkpatrick) - Better handling of Distributed Cache and Foundation Web Application service provisioning in relevant MinRole scenarios - ConfigureFoundationWebApplicationService function will now start the Web Application service if it has been requested for a particular server but detects it isn't running
↧
Viewing all 2279 articles
Browse latest View live
Search