Changes in this release:
- Tested/validated with SharePoint 2016 Release Candidate
- Renamed function AddSourcePathToLocalIntranetZone to UnblockFiles to reflect new use of Unblock-File cmdlet available in later OSes to further reduce or eliminates the number of file security prompts
- Updated all references of Blue text to Cyan for easier readability
- Updated list of SharePoint 2016 offline prerequisites to what the Release Candidate PrerequisiteInstaller.exe expects
- Cleaned up some old commented-out code
- Made function InstallLanguagePacks more robust to ensure "setup.exe" actually exists in subfolders
- Small fix to AssignCert function to better detect existing certs
- Updated CreateWebApplications function so we don't create HOSTS file entries on servers with the SP2016 Search MinRole, since they likely won't have any local websites to browse
- Updates throughout to remove trailing slashes from URLs
- Updated instances of Get-SPSite to use -Identity parameter instead of Where-Object
- Improved function CheckFor2010SP1 to quickly detect if we're installing a higher version of SharePoint
- Get-SharePointInstall now works much faster thanks to suggestions by SPRambler (https://www.codeplex.com/site/users/view/SpRambler)
- Updated file encoding to UTF-8 for AutoSPInstallerFunctions.ps1, AutoSPInstallerInput.xml, AutoSPInstallerMain.ps1
↧
Source code checked in, #116318
↧
Closed Issue: Open File Security Warning [22137]
Hi Brain. That's me again :-)
this time it's the AddSourcePathToLocalIntranetZone function which is not working when I try to install to service pack 1 from the updates folder or one of the prerequisites files 'WcfDataServices.exe'. There are several ways to disable this. I tried some of them but the the only one which worked is this one:
Disabling the prompt on the INTERNET zone (zone 3) for "Launching Applications and Unsafe Files".
Set-ItemProperty -Path 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3' -Name 1806 -Value 0
http://blogs.technet.com/b/askperf/archive/2007/11/27/managing-the-launching-applications-and-unsafe-files-setting.aspx
More details here:
https://support.microsoft.com/en-us/kb/182569
https://msdn.microsoft.com/en-us/library/ms537183(v=vs.85).aspx#internet
of course this is not safe and you we should not disable it in production permanently. What I do is as follow:
1. add this to the AddSourcePathToLocalIntranetZone with a value of 0
2. Create an additional function EnableIEUnsafeFilesPrompt which resets the value to 1 and call it in the Finalize-Install.
I'm using windows server 2012 R2
IE 11
IE Enhanced security is OFF.
The netbios name of server hosting share is present in the local intranet zone file://server (added by the autospinstaller script)
I think the warning pops up because the intranet zone settings are not detected correctly so the file is seen as being downloaded from the internet or an unsafe location. Like I said this is happening only for some files. the proposed fix takes care of this.
Comments: Resolved with changeset 116318: Changes in this release:
- Tested/validated with SharePoint 2016 Release Candidate
- Renamed function AddSourcePathToLocalIntranetZone to UnblockFiles to reflect new use of Unblock-File cmdlet available in later OSes to further reduce or eliminates the number of file security prompts
- Updated all references of Blue text to Cyan for easier readability
- Updated list of SharePoint 2016 offline prerequisites to what the Release Candidate PrerequisiteInstaller.exe expects
- Cleaned up some old commented-out code
- Made function InstallLanguagePacks more robust to ensure "setup.exe" actually exists in subfolders
- Small fix to AssignCert function to better detect existing certs
- Updated CreateWebApplications function so we don't create HOSTS file entries on servers with the SP2016 Search MinRole, since they likely won't have any local websites to browse
- Updates throughout to remove trailing slashes from URLs
- Updated instances of Get-SPSite to use -Identity parameter instead of Where-Object
- Improved function CheckFor2010SP1 to quickly detect if we're installing a higher version of SharePoint
- Get-SharePointInstall now works much faster thanks to suggestions by SPRambler (https://www.codeplex.com/site/users/view/SpRambler)
- Updated file encoding to UTF-8 for AutoSPInstallerFunctions.ps1, AutoSPInstallerInput.xml, AutoSPInstallerMain.ps1
this time it's the AddSourcePathToLocalIntranetZone function which is not working when I try to install to service pack 1 from the updates folder or one of the prerequisites files 'WcfDataServices.exe'. There are several ways to disable this. I tried some of them but the the only one which worked is this one:
Disabling the prompt on the INTERNET zone (zone 3) for "Launching Applications and Unsafe Files".
Set-ItemProperty -Path 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3' -Name 1806 -Value 0
http://blogs.technet.com/b/askperf/archive/2007/11/27/managing-the-launching-applications-and-unsafe-files-setting.aspx
More details here:
https://support.microsoft.com/en-us/kb/182569
https://msdn.microsoft.com/en-us/library/ms537183(v=vs.85).aspx#internet
of course this is not safe and you we should not disable it in production permanently. What I do is as follow:
1. add this to the AddSourcePathToLocalIntranetZone with a value of 0
2. Create an additional function EnableIEUnsafeFilesPrompt which resets the value to 1 and call it in the Finalize-Install.
I'm using windows server 2012 R2
IE 11
IE Enhanced security is OFF.
The netbios name of server hosting share is present in the local intranet zone file://server (added by the autospinstaller script)
I think the warning pops up because the intranet zone settings are not detected correctly so the file is seen as being downloaded from the internet or an unsafe location. Like I said this is happening only for some files. the proposed fix takes care of this.
Comments: Resolved with changeset 116318: Changes in this release:
- Tested/validated with SharePoint 2016 Release Candidate
- Renamed function AddSourcePathToLocalIntranetZone to UnblockFiles to reflect new use of Unblock-File cmdlet available in later OSes to further reduce or eliminates the number of file security prompts
- Updated all references of Blue text to Cyan for easier readability
- Updated list of SharePoint 2016 offline prerequisites to what the Release Candidate PrerequisiteInstaller.exe expects
- Cleaned up some old commented-out code
- Made function InstallLanguagePacks more robust to ensure "setup.exe" actually exists in subfolders
- Small fix to AssignCert function to better detect existing certs
- Updated CreateWebApplications function so we don't create HOSTS file entries on servers with the SP2016 Search MinRole, since they likely won't have any local websites to browse
- Updates throughout to remove trailing slashes from URLs
- Updated instances of Get-SPSite to use -Identity parameter instead of Where-Object
- Improved function CheckFor2010SP1 to quickly detect if we're installing a higher version of SharePoint
- Get-SharePointInstall now works much faster thanks to suggestions by SPRambler (https://www.codeplex.com/site/users/view/SpRambler)
- Updated file encoding to UTF-8 for AutoSPInstallerFunctions.ps1, AutoSPInstallerInput.xml, AutoSPInstallerMain.ps1
↧
↧
Closed Issue: Win32_Products to be avoided ! [22135]
the Get-SharePointInstall function takes a long time to process because it is using the wim (or cim) win32_products class. According to mister google this class should be avoided.
Explanation here:
https://sdmsoftware.com/group-policy-blog/wmi/why-win32_product-is-bad-news/
_When you query this class, the way the provider works is that it actually performs a Windows Installer “reconfiguration” on every MSI package on the system as its performing the query_
and here:
http://gregramsey.net/2012/02/20/win32_product-is-evil/
_even though you called a basic query of the Win32_Product class, you actually performed a consistency check of each installation._
in my case I replaced this line
if (Get-CimInstance -ClassName Win32_Product -Filter "Name like 'Microsoft SharePoint Server%'")
with this:
if(Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* ) | where-Object {$_.DisplayName -like "Microsoft SharePoint Server*"}
Comments: Resolved with changeset 116318: Changes in this release:
- Tested/validated with SharePoint 2016 Release Candidate
- Renamed function AddSourcePathToLocalIntranetZone to UnblockFiles to reflect new use of Unblock-File cmdlet available in later OSes to further reduce or eliminates the number of file security prompts
- Updated all references of Blue text to Cyan for easier readability
- Updated list of SharePoint 2016 offline prerequisites to what the Release Candidate PrerequisiteInstaller.exe expects
- Cleaned up some old commented-out code
- Made function InstallLanguagePacks more robust to ensure "setup.exe" actually exists in subfolders
- Small fix to AssignCert function to better detect existing certs
- Updated CreateWebApplications function so we don't create HOSTS file entries on servers with the SP2016 Search MinRole, since they likely won't have any local websites to browse
- Updates throughout to remove trailing slashes from URLs
- Updated instances of Get-SPSite to use -Identity parameter instead of Where-Object
- Improved function CheckFor2010SP1 to quickly detect if we're installing a higher version of SharePoint
- Get-SharePointInstall now works much faster thanks to suggestions by SPRambler (https://www.codeplex.com/site/users/view/SpRambler)
- Updated file encoding to UTF-8 for AutoSPInstallerFunctions.ps1, AutoSPInstallerInput.xml, AutoSPInstallerMain.ps1
Explanation here:
https://sdmsoftware.com/group-policy-blog/wmi/why-win32_product-is-bad-news/
_When you query this class, the way the provider works is that it actually performs a Windows Installer “reconfiguration” on every MSI package on the system as its performing the query_
and here:
http://gregramsey.net/2012/02/20/win32_product-is-evil/
_even though you called a basic query of the Win32_Product class, you actually performed a consistency check of each installation._
in my case I replaced this line
if (Get-CimInstance -ClassName Win32_Product -Filter "Name like 'Microsoft SharePoint Server%'")
with this:
if(Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* ) | where-Object {$_.DisplayName -like "Microsoft SharePoint Server*"}
Comments: Resolved with changeset 116318: Changes in this release:
- Tested/validated with SharePoint 2016 Release Candidate
- Renamed function AddSourcePathToLocalIntranetZone to UnblockFiles to reflect new use of Unblock-File cmdlet available in later OSes to further reduce or eliminates the number of file security prompts
- Updated all references of Blue text to Cyan for easier readability
- Updated list of SharePoint 2016 offline prerequisites to what the Release Candidate PrerequisiteInstaller.exe expects
- Cleaned up some old commented-out code
- Made function InstallLanguagePacks more robust to ensure "setup.exe" actually exists in subfolders
- Small fix to AssignCert function to better detect existing certs
- Updated CreateWebApplications function so we don't create HOSTS file entries on servers with the SP2016 Search MinRole, since they likely won't have any local websites to browse
- Updates throughout to remove trailing slashes from URLs
- Updated instances of Get-SPSite to use -Identity parameter instead of Where-Object
- Improved function CheckFor2010SP1 to quickly detect if we're installing a higher version of SharePoint
- Get-SharePointInstall now works much faster thanks to suggestions by SPRambler (https://www.codeplex.com/site/users/view/SpRambler)
- Updated file encoding to UTF-8 for AutoSPInstallerFunctions.ps1, AutoSPInstallerInput.xml, AutoSPInstallerMain.ps1
↧
Released: AutoSPInstaller for SharePoint 201x (Jan 29, 2016)
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 both SP2010and SP2013 and supports the latest service packs available for each (currently SP2 for 2010 and SP1 for 2013). In addition, SharePoint 2016 Release Candidate is now supported, both on Windows 2012 R2 as well as Windows Server 2016 Technical Preview 3& 4!
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.
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.
↧
Updated Release: AutoSPInstaller for SharePoint 201x (Jan 29, 2016)
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 both SP2010 and SP2013 and supports the latest service packs available for each (currently SP2 for 2010 and SP1 for 2013). In addition, SharePoint 2016 Release Candidate is now supported, both on Windows 2012 R2 as well as Windows Server 2016 Technical Preview 3 & 4!
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.
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.
↧
↧
Created Unassigned: ResourceFileManager does not contain at least one ResourceFile [22152]
I cant seem to get past this error. Can anyone help?
2016/01/29 19:20:31:784::[3464] Searching for default versions of resource files under the folder [C:\Sp2013InstallFiles\SP\2013\Foundation].
2016/01/29 19:20:31:784::[3464] Found [0] resource files under the default folder.
2016/01/29 19:20:31:784::[3464] Resource File Manager : Current user's LCID is [1033].
2016/01/29 19:20:31:801::[3464] Resource File Manager : __error : ResourceFileManager does not contain at least one ResourceFile. Unable to find best match ResourceFile for CultureTag=[en-US].__
__2016/01/29 19:20:31:801::[3464] Unable to locate a suitable resource file which contains resources that match the current user's Locale [1033].
2016/01/29 19:20:31:801::[3464] Checking the value of 'Software\Microsoft\Office\15.0\Common\LanguageResources[PreferredSetupLanguage]'
2016/01/29 19:20:31:801::[3464] Unable to select the language in which to run setup because no setup resource file(s) were located.
2016/01/29 19:20:31:801::[3464] Preparing to prompt user to select the language in which to run setup.exe in (i.e. the culture of the resource file to load.)
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : Initializing OSelectCulture UI...
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : error : ResourceFileManagerPtr has no language(s) for user to select from.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture.
2016/01/29 19:20:31:801::[3464] Showing parent-less message Title: 'Setup Error', Message: 'The language of this installation package is not supported by your system.
'
2016/01/29 19:20:48:853::[3464] Message returned: 1
2016/01/29 19:20:48:853::[3464] Catalyst execution finished: 01/29/2016 19:20:48. Return code: 30054. Exception caught: NoSupportedCulture.
2016/01/29 19:20:48:853::[3464] PERF: TickCount=4953015 Name=RunSetup Description=End function
2016/01/29 19:20:31:784::[3464] Searching for default versions of resource files under the folder [C:\Sp2013InstallFiles\SP\2013\Foundation].
2016/01/29 19:20:31:784::[3464] Found [0] resource files under the default folder.
2016/01/29 19:20:31:784::[3464] Resource File Manager : Current user's LCID is [1033].
2016/01/29 19:20:31:801::[3464] Resource File Manager : __error : ResourceFileManager does not contain at least one ResourceFile. Unable to find best match ResourceFile for CultureTag=[en-US].__
__2016/01/29 19:20:31:801::[3464] Unable to locate a suitable resource file which contains resources that match the current user's Locale [1033].
2016/01/29 19:20:31:801::[3464] Checking the value of 'Software\Microsoft\Office\15.0\Common\LanguageResources[PreferredSetupLanguage]'
2016/01/29 19:20:31:801::[3464] Unable to select the language in which to run setup because no setup resource file(s) were located.
2016/01/29 19:20:31:801::[3464] Preparing to prompt user to select the language in which to run setup.exe in (i.e. the culture of the resource file to load.)
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : Initializing OSelectCulture UI...
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : error : ResourceFileManagerPtr has no language(s) for user to select from.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture.
2016/01/29 19:20:31:801::[3464] Showing parent-less message Title: 'Setup Error', Message: 'The language of this installation package is not supported by your system.
'
2016/01/29 19:20:48:853::[3464] Message returned: 1
2016/01/29 19:20:48:853::[3464] Catalyst execution finished: 01/29/2016 19:20:48. Return code: 30054. Exception caught: NoSupportedCulture.
2016/01/29 19:20:48:853::[3464] PERF: TickCount=4953015 Name=RunSetup Description=End function
↧
Created Unassigned: SP2016 offline prerequisites [22153]
Problem with SP2016 offline prerequisites.
Replace this two line in PrerequisiteInstaller.exe -ArgumentList :
/MSVCRT11:`"$env:SPbits\PrerequisiteInstallerFiles\vcredist_x64.exe`" `
/WCFDataServices56:`"$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe`""
Replace this two line in PrerequisiteInstaller.exe -ArgumentList :
/MSVCRT11:`"$env:SPbits\PrerequisiteInstallerFiles\vcredist_x64.exe`" `
/WCFDataServices56:`"$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe`""
↧
Updated Wiki: FAQ
Frequently Asked Questions
- Is there a friendlier way to edit the XML than good ol' Notepad/Visual Studio/etc.?
- Yes - check out the new AutoSPInstaller Online. It includes real-time help/guidance, validation & smarts to avoid those "oops" moments during script run-time. We welcome your feedback!
- Is this thing safe/ready/appropriate for Production?
- It sure is! I've personally set up many live customer farms with AutoSPInstaller in the past few years. In fact it's even been used by organizations like CloudShare to create SharePoint VM templates. The standard caveats apply though: As the importance of your target farm increases, so should your level of knowledge about how to properly size, architect and build SharePoint. AutoSPInstaller does not mitigate this, it merely eases, standardizes and accelerates the process.
- Does AutoSPInstaller support SharePoint Foundation?
- Sort of. Some folks have had success getting it to work by editing the script themselves (search thru the discussions to find examples) but as I (selfishly) have no need for SPF I have not spent enough time researching this. If however someone puts forth a tried, tested & true patch that can (very) easily be integrated, I may consider including it.
- Can I use AutoSPInstaller to install Office Web Apps 2013?
- Office Web Apps 2013 (also known as WAC) is now a separate product which is not installed on the same server as SharePoint 2013. As it's technically-speaking no longer part of the SharePoint farm, and because of the complexity it would introduce, I've decided to leave Office Web Apps 2013 out of AutoSPInstaller for the time being.
- What about the Request Management service (in SharePoint 2013)? Will it be included in AutoSPInstaller?
- After a discussion with Spencer Harbar, it was agreed that it might be best to leave it out, as there can be some ramifications with provisioning it without full awareness of its intended use - e.g. by folks who want to blindly "turn everything on" in SharePoint 2013.
- Where's all the #@)%#$ documentation??
- Well, this FAQ is part of it I suppose :) I've written up a few pointers and gotchas which you can review here, but in addition, several AutoSPInstaller supporters have provided some great step-by-step guidance on their various blogs. For example:
- The new AutoSPInstaller Online guide
- Tobias Lekman's step-by-step: http://blog.lekman.com/2010/11/automated-sharepoint-2010-installations.html
- Wahid Saleemi's series on AutoSPInstaller: http://www.wahidsaleemi.com/series/autospinstaller
- Another step-by-step with some important prep items by Noorez Khamis: http://www.khamis.net/Blog/Post/315/Step-by-Step-SharePoint-2013-installation-instructions-using-AutoSPInstaller-V3-and-AutoSPInstallerGUI-–-System-Setup
- An article that helps clear up the steps & requirements for remote installations by Kartik Vega: http://sharepointjournal.com/2014/04/21/sharepoint-2013-remote-installation-using-autospinstaller-multi-server-farm
- Well, this FAQ is part of it I suppose :) I've written up a few pointers and gotchas which you can review here, but in addition, several AutoSPInstaller supporters have provided some great step-by-step guidance on their various blogs. For example:
- My SharePoint server(s) and SQL instance are in different, untrusted domains. Can I use SQL authentication instead of Windows Integrated?
- Although support for SQL auth in SharePoint (especially around things like the User Profile Service) has gotten better, AutoSPInstaller doesn't currently support connecting to your databases using anything other than Windows Integrated authentication. It certainly wouldn't be impossible to make the required modifications, but you'd have to do this yourself or reach out to the community for guidance.
- I want to make a single/isolated configuration change to an existing SharePoint farm (e.g. provision a service application). Do I really need to re-run the whole script?
- No - in fact you can usually just run individual functions to achieve what you're after by following the instructions here.
- Does AutoSPInstaller support creating web applications that use Kerberos authentication (instead of regular NTLM)? Or can AutoSPInstaller configure SPNs, delegation etc. associated with Kerberos?
- Kerberos usually requires special configuration by domain admins, so due to this and the complexities involved (and the combination of ways things can break) it's intentionally been left out of the master AutoSPInstaller project and won't be integrated in the foreseeable future. However there's no reason why anyone with the right knowledge (and permissions) could write, integrate and run custom commands/functions required to enable Kerberos authentication for SharePoint web apps created with AutoSPInstaller.
↧
Updated Wiki: FAQ
Frequently Asked Questions
- Is there a friendlier way to edit the XML than good ol' Notepad/Visual Studio/etc.?
- Yes - check out the new AutoSPInstaller Online. It includes real-time help/guidance, validation & smarts to avoid those "oops" moments during script run-time. We welcome your feedback!
- Is this thing safe/ready/appropriate for Production?
- It sure is! I've personally set up many live customer farms with AutoSPInstaller in the past few years. In fact it's even been used by organizations like CloudShare to create SharePoint VM templates. The standard caveats apply though: As the importance of your target farm increases, so should your level of knowledge about how to properly size, architect and build SharePoint. AutoSPInstaller does not mitigate this, it merely eases, standardizes and accelerates the process.
- Does AutoSPInstaller support SharePoint Foundation?
- Sort of. As of changeset 112238, AutoSPInstaller provides experimental support for SharePoint Foundation. As always though you should grab the latest release which supersedes this changeset.
- Can I use AutoSPInstaller to install Office Web Apps 2013?
- Office Web Apps 2013 (also known as WAC) is now a separate product which is not installed on the same server as SharePoint 2013. As it's technically-speaking no longer part of the SharePoint farm, and because of the complexity it would introduce, I've decided to leave Office Web Apps 2013 out of AutoSPInstaller for the time being.
- What about the Request Management service (in SharePoint 2013)? Will it be included in AutoSPInstaller?
- After a discussion with Spencer Harbar, it was agreed that it might be best to leave it out, as there can be some ramifications with provisioning it without full awareness of its intended use - e.g. by folks who want to blindly "turn everything on" in SharePoint 2013.
- Where's all the #@)%#$ documentation??
- Well, this FAQ is part of it I suppose :) I've written up a few pointers and gotchas which you can review here, but in addition, several AutoSPInstaller supporters have provided some great step-by-step guidance on their various blogs. For example:
- The new AutoSPInstaller Online guide
- Tobias Lekman's step-by-step: http://blog.lekman.com/2010/11/automated-sharepoint-2010-installations.html
- Wahid Saleemi's series on AutoSPInstaller: http://www.wahidsaleemi.com/series/autospinstaller
- Another step-by-step with some important prep items by Noorez Khamis: http://www.khamis.net/Blog/Post/315/Step-by-Step-SharePoint-2013-installation-instructions-using-AutoSPInstaller-V3-and-AutoSPInstallerGUI-–-System-Setup
- An article that helps clear up the steps & requirements for remote installations by Kartik Vega: http://sharepointjournal.com/2014/04/21/sharepoint-2013-remote-installation-using-autospinstaller-multi-server-farm
- Well, this FAQ is part of it I suppose :) I've written up a few pointers and gotchas which you can review here, but in addition, several AutoSPInstaller supporters have provided some great step-by-step guidance on their various blogs. For example:
- My SharePoint server(s) and SQL instance are in different, untrusted domains. Can I use SQL authentication instead of Windows Integrated?
- Although support for SQL auth in SharePoint (especially around things like the User Profile Service) has gotten better, AutoSPInstaller doesn't currently support connecting to your databases using anything other than Windows Integrated authentication. It certainly wouldn't be impossible to make the required modifications, but you'd have to do this yourself or reach out to the community for guidance.
- I want to make a single/isolated configuration change to an existing SharePoint farm (e.g. provision a service application). Do I really need to re-run the whole script?
- No - in fact you can usually just run individual functions to achieve what you're after by following the instructions here.
- Does AutoSPInstaller support creating web applications that use Kerberos authentication (instead of regular NTLM)? Or can AutoSPInstaller configure SPNs, delegation etc. associated with Kerberos?
- Kerberos usually requires special configuration by domain admins, so due to this and the complexities involved (and the combination of ways things can break) it's intentionally been left out of the master AutoSPInstaller project and won't be integrated in the foreseeable future. However there's no reason why anyone with the right knowledge (and permissions) could write, integrate and run custom commands/functions required to enable Kerberos authentication for SharePoint web apps created with AutoSPInstaller.
↧
↧
Created Unassigned: Can't enable a New Project Web App after Running Installer [22161]
Not sure where the bug is, but I found that when running the Installer you cannot enable the pwasite feature. Creating the Farm from scratch does allow this. It fails on "Enable-SPFeature pwasite -URL http://projects.portal.contoso.com/sites/pwa1" stating that the "The Project Content Database extension has not been provisioned for this content database."
↧
Commented Unassigned: ResourceFileManager does not contain at least one ResourceFile [22152]
I cant seem to get past this error. Can anyone help?
2016/01/29 19:20:31:784::[3464] Searching for default versions of resource files under the folder [C:\Sp2013InstallFiles\SP\2013\Foundation].
2016/01/29 19:20:31:784::[3464] Found [0] resource files under the default folder.
2016/01/29 19:20:31:784::[3464] Resource File Manager : Current user's LCID is [1033].
2016/01/29 19:20:31:801::[3464] Resource File Manager : __error : ResourceFileManager does not contain at least one ResourceFile. Unable to find best match ResourceFile for CultureTag=[en-US].__
__2016/01/29 19:20:31:801::[3464] Unable to locate a suitable resource file which contains resources that match the current user's Locale [1033].
2016/01/29 19:20:31:801::[3464] Checking the value of 'Software\Microsoft\Office\15.0\Common\LanguageResources[PreferredSetupLanguage]'
2016/01/29 19:20:31:801::[3464] Unable to select the language in which to run setup because no setup resource file(s) were located.
2016/01/29 19:20:31:801::[3464] Preparing to prompt user to select the language in which to run setup.exe in (i.e. the culture of the resource file to load.)
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : Initializing OSelectCulture UI...
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : error : ResourceFileManagerPtr has no language(s) for user to select from.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture.
2016/01/29 19:20:31:801::[3464] Showing parent-less message Title: 'Setup Error', Message: 'The language of this installation package is not supported by your system.
'
2016/01/29 19:20:48:853::[3464] Message returned: 1
2016/01/29 19:20:48:853::[3464] Catalyst execution finished: 01/29/2016 19:20:48. Return code: 30054. Exception caught: NoSupportedCulture.
2016/01/29 19:20:48:853::[3464] PERF: TickCount=4953015 Name=RunSetup Description=End function
Comments: ** Comment from web user: brianlala **
2016/01/29 19:20:31:784::[3464] Searching for default versions of resource files under the folder [C:\Sp2013InstallFiles\SP\2013\Foundation].
2016/01/29 19:20:31:784::[3464] Found [0] resource files under the default folder.
2016/01/29 19:20:31:784::[3464] Resource File Manager : Current user's LCID is [1033].
2016/01/29 19:20:31:801::[3464] Resource File Manager : __error : ResourceFileManager does not contain at least one ResourceFile. Unable to find best match ResourceFile for CultureTag=[en-US].__
__2016/01/29 19:20:31:801::[3464] Unable to locate a suitable resource file which contains resources that match the current user's Locale [1033].
2016/01/29 19:20:31:801::[3464] Checking the value of 'Software\Microsoft\Office\15.0\Common\LanguageResources[PreferredSetupLanguage]'
2016/01/29 19:20:31:801::[3464] Unable to select the language in which to run setup because no setup resource file(s) were located.
2016/01/29 19:20:31:801::[3464] Preparing to prompt user to select the language in which to run setup.exe in (i.e. the culture of the resource file to load.)
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : Initializing OSelectCulture UI...
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : error : ResourceFileManagerPtr has no language(s) for user to select from.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture.
2016/01/29 19:20:31:801::[3464] Showing parent-less message Title: 'Setup Error', Message: 'The language of this installation package is not supported by your system.
'
2016/01/29 19:20:48:853::[3464] Message returned: 1
2016/01/29 19:20:48:853::[3464] Catalyst execution finished: 01/29/2016 19:20:48. Return code: 30054. Exception caught: NoSupportedCulture.
2016/01/29 19:20:48:853::[3464] PERF: TickCount=4953015 Name=RunSetup Description=End function
Comments: ** Comment from web user: brianlala **
Can you confirm that this is an issue caused by AutoSPInstaller - in other words, do you get the same error during a manual installation, or does it work OK?
Actually just looking at the date on this, looks like we may have discussed and resolved this offline since then.
Brian
↧
Closed Unassigned: ResourceFileManager does not contain at least one ResourceFile [22152]
I cant seem to get past this error. Can anyone help?
2016/01/29 19:20:31:784::[3464] Searching for default versions of resource files under the folder [C:\Sp2013InstallFiles\SP\2013\Foundation].
2016/01/29 19:20:31:784::[3464] Found [0] resource files under the default folder.
2016/01/29 19:20:31:784::[3464] Resource File Manager : Current user's LCID is [1033].
2016/01/29 19:20:31:801::[3464] Resource File Manager : __error : ResourceFileManager does not contain at least one ResourceFile. Unable to find best match ResourceFile for CultureTag=[en-US].__
__2016/01/29 19:20:31:801::[3464] Unable to locate a suitable resource file which contains resources that match the current user's Locale [1033].
2016/01/29 19:20:31:801::[3464] Checking the value of 'Software\Microsoft\Office\15.0\Common\LanguageResources[PreferredSetupLanguage]'
2016/01/29 19:20:31:801::[3464] Unable to select the language in which to run setup because no setup resource file(s) were located.
2016/01/29 19:20:31:801::[3464] Preparing to prompt user to select the language in which to run setup.exe in (i.e. the culture of the resource file to load.)
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : Initializing OSelectCulture UI...
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : error : ResourceFileManagerPtr has no language(s) for user to select from.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture.
2016/01/29 19:20:31:801::[3464] Showing parent-less message Title: 'Setup Error', Message: 'The language of this installation package is not supported by your system.
'
2016/01/29 19:20:48:853::[3464] Message returned: 1
2016/01/29 19:20:48:853::[3464] Catalyst execution finished: 01/29/2016 19:20:48. Return code: 30054. Exception caught: NoSupportedCulture.
2016/01/29 19:20:48:853::[3464] PERF: TickCount=4953015 Name=RunSetup Description=End function
Comments: Resolved over email.
2016/01/29 19:20:31:784::[3464] Searching for default versions of resource files under the folder [C:\Sp2013InstallFiles\SP\2013\Foundation].
2016/01/29 19:20:31:784::[3464] Found [0] resource files under the default folder.
2016/01/29 19:20:31:784::[3464] Resource File Manager : Current user's LCID is [1033].
2016/01/29 19:20:31:801::[3464] Resource File Manager : __error : ResourceFileManager does not contain at least one ResourceFile. Unable to find best match ResourceFile for CultureTag=[en-US].__
__2016/01/29 19:20:31:801::[3464] Unable to locate a suitable resource file which contains resources that match the current user's Locale [1033].
2016/01/29 19:20:31:801::[3464] Checking the value of 'Software\Microsoft\Office\15.0\Common\LanguageResources[PreferredSetupLanguage]'
2016/01/29 19:20:31:801::[3464] Unable to select the language in which to run setup because no setup resource file(s) were located.
2016/01/29 19:20:31:801::[3464] Preparing to prompt user to select the language in which to run setup.exe in (i.e. the culture of the resource file to load.)
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : Initializing OSelectCulture UI...
2016/01/29 19:20:31:801::[3464] SELECT_CULTURE : error : ResourceFileManagerPtr has no language(s) for user to select from.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2016/01/29 19:20:31:801::[3464] Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture.
2016/01/29 19:20:31:801::[3464] Showing parent-less message Title: 'Setup Error', Message: 'The language of this installation package is not supported by your system.
'
2016/01/29 19:20:48:853::[3464] Message returned: 1
2016/01/29 19:20:48:853::[3464] Catalyst execution finished: 01/29/2016 19:20:48. Return code: 30054. Exception caught: NoSupportedCulture.
2016/01/29 19:20:48:853::[3464] PERF: TickCount=4953015 Name=RunSetup Description=End function
Comments: Resolved over email.
↧
New Post: Can AutoSPInstaller add another WFE to the Farm
Hello All,
After a long time i got a chance to come back and put a question to all experts here.. :)
I need your help..
I had Installed SharePoint 2013 with AutoSPInstaller which went pretty well with the below Architecture:
APP Server = 1
WFE Server = 2
Index Server = 2
Now, we have to add another WFE i.e. 3rd WFE to the Farm and i am not able to add manually. There are some issue with Alias DB. So, i want to know will our very own AutoSPInstaller will help me to add another WFE to the FARM??
If this is possible i will need guidance help how to do it.
It will be a great help.
Regards,
Aasmi
After a long time i got a chance to come back and put a question to all experts here.. :)
I need your help..
I had Installed SharePoint 2013 with AutoSPInstaller which went pretty well with the below Architecture:
APP Server = 1
WFE Server = 2
Index Server = 2
Now, we have to add another WFE i.e. 3rd WFE to the Farm and i am not able to add manually. There are some issue with Alias DB. So, i want to know will our very own AutoSPInstaller will help me to add another WFE to the FARM??
If this is possible i will need guidance help how to do it.
It will be a great help.
Regards,
Aasmi
↧
↧
Commented Unassigned: Can't enable a New Project Web App after Running Installer [22161]
Not sure where the bug is, but I found that when running the Installer you cannot enable the pwasite feature. Creating the Farm from scratch does allow this. It fails on "Enable-SPFeature pwasite -URL http://projects.portal.contoso.com/sites/pwa1" stating that the "The Project Content Database extension has not been provisioned for this content database."
Comments: ** Comment from web user: Bismarck41 **
Comments: ** Comment from web user: Bismarck41 **
It appears to be with the creation of the SharePoint_Config or SharePoint_AdminContent databases or both. I resolved the issue by creating these databases through the PSConfig and then let the AutoSPInstaller do the rest.
↧
New Post: Can AutoSPInstaller add another WFE to the Farm
In a nutshell, (assuming your first 2 WFEs are called "WFE1" and "WFE2") just search for references of "WFE1,WFE2" in your XML and update them to "WFE1,WFE2,WFE3" and then run AutoSPInstaller on the new WFE. It should pick up its roles/services and be added to the farm.
Or if you prefer you can accomplish the same by loading your input XML into https://autospinstaller.com, but IMO it would actually take longer that way.
Brian
Or if you prefer you can accomplish the same by loading your input XML into https://autospinstaller.com, but IMO it would actually take longer that way.
Brian
↧
Commented Unassigned: Can't enable a New Project Web App after Running Installer [22161]
Not sure where the bug is, but I found that when running the Installer you cannot enable the pwasite feature. Creating the Farm from scratch does allow this. It fails on "Enable-SPFeature pwasite -URL http://projects.portal.contoso.com/sites/pwa1" stating that the "The Project Content Database extension has not been provisioned for this content database."
Comments: ** Comment from web user: brianlala **
Comments: ** Comment from web user: brianlala **
That's strange because AutoSPInstaller just runs the PowerShell-equivalent commands of PSConfig. I'll check to see if anything's missing that needs to be run for Project.
Brian
↧
Edited Issue: Can't enable a New Project Web App after Running Installer [22161]
Not sure where the bug is, but I found that when running the Installer you cannot enable the pwasite feature. Creating the Farm from scratch does allow this. It fails on "Enable-SPFeature pwasite -URL http://projects.portal.contoso.com/sites/pwa1" stating that the "The Project Content Database extension has not been provisioned for this content database."
↧
↧
New Post: Service Application Environment Prefix
would be nice to visually differentiate between environments and see that you're not deleting the production service application :-) i know you have the env name in central admin but it is not as visible as naming your SA: Dev Search Service Application or Contoso Search Searvice Application, especially if you're managing several farms.
↧
Commented Issue: Can't enable a New Project Web App after Running Installer [22161]
Not sure where the bug is, but I found that when running the Installer you cannot enable the pwasite feature. Creating the Farm from scratch does allow this. It fails on "Enable-SPFeature pwasite -URL http://projects.portal.contoso.com/sites/pwa1" stating that the "The Project Content Database extension has not been provisioned for this content database."
Comments: ** Comment from web user: Bismarck41 **
Comments: ** Comment from web user: Bismarck41 **
OK, I have some more information from the ULS Logs. Maybe its a bug.
Unexpected System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Office.Project.Server.DataAccessLayer.DataStoreExtentions.GetSchemaName(DataStoreEnum store, IProjectServerSqlSessionProvider sessionProvider) at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.CreateStoredProcedureCommand(String storedProcedureName, Int32 timeout, SqlParameter[] parameters) at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.FillTypedDataSet(DataSet typedDataSet, String[] tables, String storedProcedureName, Int32 timeout, SqlParameter[] parameters) at Microsoft.Office.Project.Server.DataAccessLayer.Generated.AdminDalBase.GetAllWebAdminSettingsIfChanged(Nullable`1 cachedVersion) at Microsoft.Office.Project.Server.BusinessLayer.ServerSett... d9b05b9d-a499-7004-f1d6-039d5bb39137
Unexpected ...ings.SynchronousDataProvider(IPlatformContext context, Nullable`1 version) at Microsoft.Office.Project.Server.BusinessLayer.ServerSettings.GetSettingsInternal(IPlatformContext context, ISqlBatchRequest batchRequest) at Microsoft.Office.Project.Server.Base.ContextFactory.PlatformContext.get_DefaultLCID() at Microsoft.Office.Project.Server.Base.ContextFactory.PlatformContext..ctor(Guid trackingId, Guid siteId, SPUrlZone urlZone, CultureInfo languageCulture, CultureInfo localeCulture, Guid ulsCorrelationUid, DatabaseAccessLevel databaseAccessLevel, Boolean omitDatasetSchema, Boolean useSystemAccountForSPSite) d9b05b9d-a499-7004-f1d6-039d5bb39137
za
Bismarck
↧
Commented Unassigned: Error during "Installing Features" [22126]
Hi,
I'm unable to install SP2016 beta 2. I'm getting these errors during "Installing Features":
```
- Installing Features...
WARNING: Feature PointPublishing\Feature.xml had failed to install for the following reason: Failed to create receiver
object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingFeatureHandler" for feature
"PointPublishing" (ID: 8c9f9b9e-1f5a-42d5-8918-29b3f1bf27f0).: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingHub\feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Portal, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Portal.PointPublishingHubSiteFeatureReceiver" for feature
"PointPublishingHub" (ID: f8064795-884c-4ac8-b551-d87592ceeac9).: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingPersonal\feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingPersonalSiteFeatureReceiver"
for feature "PointPublishingPersonal" (ID: 1a337c2c-f2c0-4c81-b66a-11ae9a48bf20).: System.ArgumentNullException: Value
cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingTopic\Feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingTopicSiteFeatureReceiver" for
feature "PointPublishingTopic" (ID: a4426c43-c58b-419c-a5bb-883a10d0be7f).: System.ArgumentNullException: Value cannot
be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
- Creating Central Admin site...
- Waiting for Central Admin site...Online
- Updating Central Admin branding text to "Dev"...
- Installing Application Content...
- Checking Default Web Site...Stopping...OK.
- Done initial farm/server config.
```
Not sure if it's related, but further down I get these errors:
```
- Creating Web App "Portal Home"
New-SPWebApplication : An update conflict has occurred, and you must re-try this action. The object SPServer Name=SP201
6 was updated by UTV\SP_Farm, in the OWSTIMER (5548) process, on machine SP2016. View the tracing log for more informa
tion about the conflict.
At C:\BouvetDevSP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2692 char:9
+ New-SPWebApplication -Name $webAppName -ApplicationPool $appPool -Databa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...PWebApplication:SPCmdletNewSPWebApplication) [New-SPWebA
pplication], SPUpdatedConcurrencyException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWebApplication
--------------------------------------------------------------
- Script halted!
- Failed to create web application
```
The strange thing is that if I re-run AutoSPInstaller, everything works as expected...
Any clues?
Comments: ** Comment from web user: johnmcalvert **
I'm unable to install SP2016 beta 2. I'm getting these errors during "Installing Features":
```
- Installing Features...
WARNING: Feature PointPublishing\Feature.xml had failed to install for the following reason: Failed to create receiver
object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingFeatureHandler" for feature
"PointPublishing" (ID: 8c9f9b9e-1f5a-42d5-8918-29b3f1bf27f0).: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingHub\feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Portal, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Portal.PointPublishingHubSiteFeatureReceiver" for feature
"PointPublishingHub" (ID: f8064795-884c-4ac8-b551-d87592ceeac9).: System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingPersonal\feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingPersonalSiteFeatureReceiver"
for feature "PointPublishingPersonal" (ID: 1a337c2c-f2c0-4c81-b66a-11ae9a48bf20).: System.ArgumentNullException: Value
cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
WARNING: Feature PointPublishingTopic\Feature.xml had failed to install for the following reason: Failed to create
receiver object from assembly "Microsoft.SharePoint.Publishing, Version=16.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c", class "Microsoft.SharePoint.Publishing.PointPublishingTopicSiteFeatureReceiver" for
feature "PointPublishingTopic" (ID: a4426c43-c58b-419c-a5bb-883a10d0be7f).: System.ArgumentNullException: Value cannot
be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject().
- Creating Central Admin site...
- Waiting for Central Admin site...Online
- Updating Central Admin branding text to "Dev"...
- Installing Application Content...
- Checking Default Web Site...Stopping...OK.
- Done initial farm/server config.
```
Not sure if it's related, but further down I get these errors:
```
- Creating Web App "Portal Home"
New-SPWebApplication : An update conflict has occurred, and you must re-try this action. The object SPServer Name=SP201
6 was updated by UTV\SP_Farm, in the OWSTIMER (5548) process, on machine SP2016. View the tracing log for more informa
tion about the conflict.
At C:\BouvetDevSP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2692 char:9
+ New-SPWebApplication -Name $webAppName -ApplicationPool $appPool -Databa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...PWebApplication:SPCmdletNewSPWebApplication) [New-SPWebA
pplication], SPUpdatedConcurrencyException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWebApplication
--------------------------------------------------------------
- Script halted!
- Failed to create web application
```
The strange thing is that if I re-run AutoSPInstaller, everything works as expected...
Any clues?
Comments: ** Comment from web user: johnmcalvert **
CatoAntonsen, would you be willing to share your script / config with the community?
↧