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

Created Unassigned: SharePoint 2013 - Oct2016 CU. UPSA Cannot be Provisioned - Key cannot be null? [22377]

October 25, 2016, 11:07 am
$
0
0
Hey All,
I am doing a single server farm

One server and one sql server 2012 r2 SP 3.

SharePoint is 2013 Enterprise, Service Pack 1 with October 2016 CU.

When trying to run SP Installer I get this error.

PS C:\SP\AutoSPInstaller> CreateUserProfileServiceApplication
Key cannot be null.
Parameter name: key
At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:7642 char:5
+ $env:spVer = $spVersions.($xmlinput.Configuration.Install.SPVersion)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [], ArgumentNullException
+ FullyQualifiedErrorId : System.ArgumentNullException

- Error Provisioning the User Profile Service Application
At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:3487 char:9
+ Throw " - Error Provisioning the User Profile Service Application"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: ( - Error Provis...ice Application:String) [], RuntimeException
+ FullyQualifiedErrorId : - Error Provisioning the User Profile Service Application
↧
Search

Updated Release: AutoSPInstaller for SharePoint 201x (Nov 08, 2016)

November 8, 2016, 6:16 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.
↧
↧

Released: AutoSPInstaller for SharePoint 201x (Nov 08, 2016)

November 8, 2016, 6:18 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 (including Feature Pack 1), 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.
↧

Updated Release: AutoSPInstaller for SharePoint 201x (Nov 08, 2016)

November 8, 2016, 6:18 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 (including Feature Pack 1), 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.
↧

Updated Wiki: Home

November 8, 2016, 6:29 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 (including Feature Pack 1 found in the November 2016 PU), 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\201x\ProjectServer\ (optional; copy/extract the contents of the Project Server 2013 DVD/ISO here)
\SP\201x\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, a 3 or a 6 depending on whether you're installing SP2010, SP2013 or SP2016. 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 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 or better yet athttps://autospinstaller.com.

↧
↧

Source code checked in, #117940

November 8, 2016, 6:06 pm
$
0
0
Changes in this release: - Support for new Minroles introduced in SharePoint 2016 Feature Pack 1 AKA November 2016 PU - New function CheckForSP2016FeaturePack1 - Enhances/fixes to Project Server 2016 install/config functionality - Fix syntax in Install-AppFabricCU function - InstallUpdates function now picks up SP2016 public updates - Misc. comment updates and tweaks throughout e.g. removing trailing slashes from URLs - Function Start-RemoteInstaller now has faster way to check OS version - New function Set-ShortcutRunAsAdmin fixes a common annoyance - the SharePoint Management Shell will now always automatically run as Admin so we don't have to remember to explicitly do this ourselves each time - Custom Provision is now "true" by default in the XML - Implemented workaround to re-launch script when language packs are being installed along with SharePoint 2016; cause still unknown
↧

New Post: New-SPSecureStoreApplication Failes

November 16, 2016, 6:56 pm
$
0
0
Hi ravensorb, Tradelingua,

I am having the same issue. I am not sure if the error message "...SPSecureStoreApplication], AddressAccessDeniedException" refers to a permission issue for the account executing the script (which I would assume is the Setup account).

I have not yet resolved this, so if you have any suggestions I am all ears.

Cheers...
AG
↧

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

November 8, 2016, 6:06 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: Associated with changeset 117940: Changes in this release:

- Support for new Minroles introduced in SharePoint 2016 Feature Pack 1 AKA November 2016 PU
- New function CheckForSP2016FeaturePack1
- Enhances/fixes to Project Server 2016 install/config functionality
- Fix syntax in Install-AppFabricCU function
- InstallUpdates function now picks up SP2016 public updates
- Misc. comment updates and tweaks throughout e.g. removing trailing slashes from URLs
- Function Start-RemoteInstaller now has faster way to check OS version
- New function Set-ShortcutRunAsAdmin fixes a common annoyance - the SharePoint Management Shell will now always automatically run as Admin so we don't have to remember to explicitly do this ourselves each time
- Custom Provision is now "true" by default in the XML
- Implemented workaround to re-launch script when language packs are being installed along with SharePoint 2016; cause still unknown
↧
Search

Closed Issue: Function Install-WindowsIdentityFoundation amendment [22238]

November 8, 2016, 6:07 pm
$
0
0
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
Comments: Resolved with changeset 117940: Changes in this release:

- Support for new Minroles introduced in SharePoint 2016 Feature Pack 1 AKA November 2016 PU
- New function CheckForSP2016FeaturePack1
- Enhances/fixes to Project Server 2016 install/config functionality
- Fix syntax in Install-AppFabricCU function
- InstallUpdates function now picks up SP2016 public updates
- Misc. comment updates and tweaks throughout e.g. removing trailing slashes from URLs
- Function Start-RemoteInstaller now has faster way to check OS version
- New function Set-ShortcutRunAsAdmin fixes a common annoyance - the SharePoint Management Shell will now always automatically run as Admin so we don't have to remember to explicitly do this ourselves each time
- Custom Provision is now "true" by default in the XML
- Implemented workaround to re-launch script when language packs are being installed along with SharePoint 2016; cause still unknown
↧
↧

Commented Unassigned: Managed paths are not created in SP 2016 [22358]

November 14, 2016, 11:35 am
$
0
0
When installing SP 2016, no custom managed paths are actually created. The console output shows no error. But when a site collection, which requires a certain managed path to exist, is created, this obviously fails.

I couldn't figure out why the paths are not created. Running the same command manually works.
Also apparently restarting AutoSPInstaller works.

I also noticed, New-SPManagedPath is executed a second time with the -HostHeader switch. This doesn't work because you can't have both a HNSC and non-HNSC managed path with the same name. It's one or the other.

```
New-SPManagedPath -RelativeUrl $managedPath.RelativeUrl -WebApplication $url -Explicit -ErrorAction SilentlyContinue | Out-Null
# Let's create it for host-named site collections too, in case we have any
New-SPManagedPath -RelativeUrl $managedPath.RelativeUrl -HostHeader -Explicit -ErrorAction SilentlyContinue | Out-Null
```
Comments: ** Comment from web user: brianlala **

Can you confirm that this is still happening for you? I've created a bunch of farms myself in the last few days with custom managed paths, no issues. Maybe you can share the relevant lines of your input XML, too.

Brian

↧

Commented Unassigned: Offline Prerequisite Install [22354]

November 14, 2016, 11:42 am
$
0
0
I've been having issues getting AutoSPInstaller to install SharePoint 2016 offline and I've found the following line in the PrerequisiteInstall function

/WCFDataServices56:`"$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices.exe`"

Should actually be

/WCFDataServices56:`"$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe`"
Comments: ** Comment from web user: brianlala **

Folks, it's no longer called WcfDataServices56.exe - see the official list of prerequisites: https://technet.microsoft.com/en-ca/library/cc262485(v=office.16).aspx#section7. Both AutoSPInstaller and AutoSPSourceBuilder use the correct name now.

Brian

↧

Commented Unassigned: Error: Custom file location is not accessible while offline prerequisite installer [22339]

November 14, 2016, 11:46 am
$
0
0
I am having an issue when autoinstaller is trying to configure the SharePoint 2013 Standalone offline mode.

My system configurations: OS: Windows Server 2012 R2
SharePoint : 2013 Enterprise Trail

please see below error. I copied prerequisites in proper location.

--------------------------------------------------------------

- Installing Prerequisite Software:

- .Net Framework 3.5.1 from "C:\SP\2013\SharePoint\PrerequisiteInstallerFiles\sxs"...Already installed.

- Running Prerequisite Installer (offline mode)....Done.

- Prerequisite Installer completed in 00:00:05.

WARNING: 2016-08-24 21:43:44 - Error: Custom file location is not accessible

--------------------------------------------------------------

- 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, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 882

at Run-Install, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184

at <scriptblock>, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 381

at <scriptblock>, <no file="">: line 1

PipelineIterationInfo : {}

PSMessageDetails :

-----------------------------------

| Automated SP2013 install script |

| Started on: 8/24/2016 9:43:38 PM |

| Aborted: 8/24/2016 9:43:50 PM |

-----------------------------------

PS C:\SP\AutoSPInstaller>
Comments: ** Comment from web user: brianlala **

Note, something like [AutoSPSourceBuilder](https://github.com/brianlala/AutoSPSourceBuilder) should handle the downloading and placement of the correct prerequisites files for you automatically, and is kept in sync with AutoSPInstaller too.

Brian

↧

Created Unassigned: could not disable CRL check [22410]

November 17, 2016, 4:03 am
$
0
0
Hi,
I try to install SP 2013 with the powerful AutoSPI but quickly I get this error about :
"could not disable CRL check"
Known issue ? How can i fix it ?
Best regards,
EM.
↧
↧

Created Unassigned: Multiple Server and SharePoint 2016 bug [22422]

December 5, 2016, 7:10 am
$
0
0
There is a problem with remote multi server install and SharePoint 2016.

The problem is in main here:
----
Setup-Services
Finalize-Install
# We only want to Install-Remote if we aren't already *in* a remote session, and if there are actually remote servers to install!
If ((Confirm-LocalSession) -and !([string]::IsNullOrEmpty($remoteFarmServers))) {Install-Remote}
------
We correct order is to move the complete line "Install-Remote" before "Setup-Services" .
We need to install all and then setup services.
(an classic/common example of problem if that same services, like "managed metadata" on frontend role require topology services that is present only on application role when I execute Install-SPService (the setup-farm of remote install).
↧

Commented Unassigned: SP2016 Prerequisites [22386]

December 6, 2016, 8:35 am
$
0
0
There is an error in the prerequisites for ShqrePoint 2016: AutoSPInstallerFunctions.ps1 line 731 should be:
/WCFDataServices56:`"$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe`" `
Comments: ** Comment from web user: brianlala **

No, that was for 2013. For 2016 the filename is just WcfDataServices.exe, from permalink http://go.microsoft.com/fwlink/?LinkId=320724. BTW if you use AutoSPSourceBuilder to get your prerequisites, it will put the right files in.

Brian

↧
Search

Edited Issue: SP2016 Prerequisites [22386]

December 6, 2016, 8:37 am
$
0
0
There is an error in the prerequisites for ShqrePoint 2016: AutoSPInstallerFunctions.ps1 line 731 should be:
/WCFDataServices56:`"$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe`" `
↧

Commented Issue: SP2016 Prerequisites [22386]

December 6, 2016, 9:19 am
$
0
0
There is an error in the prerequisites for ShqrePoint 2016: AutoSPInstallerFunctions.ps1 line 731 should be:
/WCFDataServices56:`"$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe`" `
Comments: ** Comment from web user: brianlala **

Actually, it turns out this was a bug in AutoSPSourceBuilder, in case that's what you used to download the files. It renames the executable for SharePoint 2013 but I neglected to put a check for 2016, whereby it "shouldn't* rename it. I'll publish a fix to AutoSPSourceBuilder on GitHub soon.

Brian

↧
↧

Commented Unassigned: WCFDataServices Prerequisite Issue [21531]

December 6, 2016, 9:20 am
$
0
0
I was able to consistently see this in a build I was doing and don't know if anyone else has seen it.

I'm doing an offline build on a W2K8 R2 SP1 box, installing SP2013 SP1 (media from MSDN) with SS2K12 already installed. Things seem to run smoothly through a number of prereqs until we hit the WCFDataServices area. The system seems to want to look for the version 5.6 (after instaling 5.0), and when it can't find it it tries to look on the 'net, but this being an offline build (and the server I'm running this on doesn't have access to the 'net) it errors out. See below:

*****************************************************************************************************************
Installing Prerequisite Software:
- Net Framework 3.5.1...Already installed.
- Running Prerequisite Installer (offline mode)...........................................................Done.
- Prerequisite Installer completed in 00:04:40.
- SharePoint 2013 "missing hotfix" prerequisites...
- Checking for KB2554876...Already installed.
- Checking for KB2708075...Missing; attempting to install...
- Hotfix file "Windows6.1-KB2708075-x64.msu" found.
- Installing hotfix Windows6.1-KB2708075-x64.msu...Done.
- Checking for KB2567680...Missing; attempting to install...
- Hotfix file "Windows6.1-KB2567680-x64.msu" found.
- Installing hotfix Windows6.1-KB2567680-x64.msu...Done.
- Checking for KB2759112...Missing; attempting to install...
- Hotfix file "NDP45-KB2759112-x64.exe" found.
- Installing hotfix NDP45-KB2759112-x64.exe...Done.
- Checking for KB2472264...Already installed.
WARNING: 2014-11-05 08:26:22 - Error: InternetOpenUrl failed (0X80072EE7=-2147012889)
WARNING: 2014-11-05 08:26:22 - Error: Failed to download WCF Data Services 5.6 installation package, (0X800700B7=-2147024713)
*****************************************************************************************************************

Adding the line to run/execute the 5.6 install in the AutoSPInstallerFunctions.ps1 (InstallPrerequisites function) gets me past this, but it's probably a quick fix.

Has anyone seen this behavior?

Thanks! - M
Comments: ** Comment from web user: brianlala **

Actually, it turns out this was a bug in AutoSPSourceBuilder, in case that's what you used to download the files. It renames the executable for SharePoint 2013 but I neglected to put a check for 2016, whereby it "shouldn't* rename it. I'll publish a fix to AutoSPSourceBuilder on GitHub soon.

Brian

↧

Created Unassigned: Set-SPUsageService update conflict multi-server [22424]

December 12, 2016, 12:54 am
$
0
0
If you do a multi-server install, on other server appear the error:

Set-SPUsageService : An update conflict has occurred, and you must re-try this action. The object SPUsageManager
was updated by domain\spadmin, in the powershell (4668) process, on machine SP01. View the tracing log
for more information about the conflict.
At E:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:3870 char:13
+ Set-SPUsageService -LoggingEnabled $loggingEnabled -Usage ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...SetUsageService:SPCmdletSetUsageService) [Set-SPUs
ageService], SPUpdatedConcurrencyException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletSetUsageService


It's safe to ignore it because already applied.
↧

Created Unassigned: Error search unprovision multi-server install [22425]

December 12, 2016, 1:08 am
$
0
0
If you configure Search on two server, on first server appear the error:

Checking for stuck Search Host Controller Service (known issue)...
- Server: SP01...
Re-provisioning...
Done.
- Server: SP02...
Re-provisioning...
PS>TerminatingError(ForEach-Object): "Exception calling "Unprovision" with "0" argument(s): "The executing code must run on server SP02.""

Ignore it, then re-execute autospinstaller on SP02 all fixed fine.
↧
Viewing all 2279 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>