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

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

$
0
0
Hello,

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

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

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

Thank in adavance,
Florent.
Comments: ** Comment from web user: Florent123 **

Hello,

I specify a web application with option add to host set to True, or in function "CreateWebApplications" this option launch execution of "AddToHOSTS" function without parameters.

# Updated so that we don't add URLs to the local hosts file of a server that's not running the Foundation Web Application service
If ($xmlinput.Configuration.WebApplications.AddURLsToHOSTS -eq $true -and !(($xmlinput.Configuration.Farm.Services.SelectSingleNode("FoundationWebApplication")) -and !(ShouldIProvision $xmlinput.Configuration.Farm.Services.FoundationWebApplication -eq $true)))
{AddToHOSTS}

And if function "AddToHOSTS" is executed without parameters, $Hosts variable equal all alternate urls:

if (!$hosts) # No hosts were passed as arguments, so look at the AAMs in the farm
{
# Get a list of the AAMs and weed out the duplicates
$hosts = Get-SPAlternateURL | ForEach-Object {$_.incomingurl.replace("https://","").replace("http://","")} | where-Object { $_.tostring() -notlike "*:*" } | Select-Object -Unique
}

And in the alternate urls list we can found central admin url, in my case this is the server name that it add to host file.

Regards,
Florent.


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

$
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 :)
Comments: ** Comment from web user: CraigHumphrey **

The reset of the install completed successfully - with respect to reboots and errors reported during by AutoSPInstaller

Created Unassigned: SP2016 Central Admin DB in compatibility mode [22220]

$
0
0
Just ran the 21 March 2016 AutoSPInstaller against the SP2016 RTM (trial) media.

Install process went fine.

However the Central Admin content DB has been left in compatibility mode:

```
Database Schema Versions

Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 16.0.79.0, Maximum Schema Version: 16.0.79.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSprocsSequence Current Schema Version: 16.0.93.0, Maximum Schema Version: 16.0.93.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 16.0.4.0, Maximum Schema Version: 16.0.4.0
Microsoft.SharePoint.Upgrade.SPGlobalExtensionUpgradeSequence Current Schema Version: 16.0.6.0, Maximum Schema Version: 16.0.6.0
Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__
```

I'll run a PSConfig and see if it cleans it up.

Commented Unassigned: SP2016 Central Admin DB in compatibility mode [22220]

$
0
0
Just ran the 21 March 2016 AutoSPInstaller against the SP2016 RTM (trial) media.

Install process went fine.

However the Central Admin content DB has been left in compatibility mode:

```
Database Schema Versions

Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 16.0.79.0, Maximum Schema Version: 16.0.79.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSprocsSequence Current Schema Version: 16.0.93.0, Maximum Schema Version: 16.0.93.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 16.0.4.0, Maximum Schema Version: 16.0.4.0
Microsoft.SharePoint.Upgrade.SPGlobalExtensionUpgradeSequence Current Schema Version: 16.0.6.0, Maximum Schema Version: 16.0.6.0
Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__
```

I'll run a PSConfig and see if it cleans it up.
Comments: ** Comment from web user: CraigHumphrey **

Bugger, can't do BOLD inside of CODE.

It's the last two lines that are key:

PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
and
SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__

Commented Unassigned: SP2016 Central Admin DB in compatibility mode [22220]

$
0
0
Just ran the 21 March 2016 AutoSPInstaller against the SP2016 RTM (trial) media.

Install process went fine.

However the Central Admin content DB has been left in compatibility mode:

```
Database Schema Versions

Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 16.0.79.0, Maximum Schema Version: 16.0.79.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSprocsSequence Current Schema Version: 16.0.93.0, Maximum Schema Version: 16.0.93.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 16.0.4.0, Maximum Schema Version: 16.0.4.0
Microsoft.SharePoint.Upgrade.SPGlobalExtensionUpgradeSequence Current Schema Version: 16.0.6.0, Maximum Schema Version: 16.0.6.0
Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__
```

I'll run a PSConfig and see if it cleans it up.
Comments: ** Comment from web user: CraigHumphrey **

Ran Upgrade-SPFarm in admin SP PowerShell. Fixed it with one warning - it skipped upgrading the SPContentDatabase, as it's version was already higher. Might log that with MS, probably a bug at their end.

So now I have the following for the Central Admin Content DB:

PDEUpgradeSequence Current Schema Version: __16.1.273.0__, Maximum Schema Version: __16.1.273.0__
and
SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__

Created Unassigned: Error sp2016 null-valued [22222]

$
0
0
- Granting DOMAIN\SPADMIN rights to "Portal Home"...--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.RuntimeException: You cannot call a method on a null-valued
expression.
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 : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : InvokeMethodOnNull
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2810
at CreateWebApplications, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 2670
at Setup-Farm, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 211
at <ScriptBlock>, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 410
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

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

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

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

Probably needs to have an additional check for Foundation, if the detection needs to avoid false positives from SP Designer etc.
Comments: ** Comment from web user: brianlala **

Good point, would you happen to have the correct registry string for a Foundation install... I don't have any Foundation installs laying around :)

Cheers
Brian

Edited Issue: Function Get-SharePointInstall fails for Foundation [22165]

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

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

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

Commented Unassigned: Error sp2016 null-valued [22222]

$
0
0
- Granting DOMAIN\SPADMIN rights to "Portal Home"...--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.RuntimeException: You cannot call a method on a null-valued
expression.
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 : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : InvokeMethodOnNull
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2810
at CreateWebApplications, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 2670
at Setup-Farm, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 211
at <ScriptBlock>, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 410
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
Comments: ** Comment from web user: paololecchi **

Error is here:
$wa = Get-SPWebApplication | Where-Object {$_.DisplayName -eq $webAppName}
--> $wa.GrantAccessToProcessIdentity("$($spservice.username)")

Commented Unassigned: Error sp2016 null-valued [22222]

$
0
0
- Granting DOMAIN\SPADMIN rights to "Portal Home"...--------------------------------------------------------------
- Script halted!


Exception : System.Management.Automation.RuntimeException: You cannot call a method on a null-valued
expression.
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 : InvalidOperation: (:) [], RuntimeException
FullyQualifiedErrorId : InvokeMethodOnNull
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2810
at CreateWebApplications, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
line 2670
at Setup-Farm, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 211
at <ScriptBlock>, D:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 410
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
Comments: ** Comment from web user: paololecchi **

To fix: open central admin, delete web app "Portal Home" and relaunch script, work fine.

Commented Issue: Function Get-SharePointInstall fails for Foundation [22165]

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

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

Probably needs to have an additional check for Foundation, if the detection needs to avoid false positives from SP Designer etc.
Comments: ** Comment from web user: Emblematic **

Sure! Here are the values from 2013 and 2010.

Cheers
Bob

PS C:\> Get-CimInstance -ClassName Win32_Product -Filter "Name like 'Microsoft SharePoint%'" | format-list

IdentifyingNumber : {90150000-1110-0000-1000-0000000FF1CE}
Name : Microsoft SharePoint Foundation 2013
Vendor : Microsoft Corporation
Version : 15.0.4569.1506
Caption : Microsoft SharePoint Foundation 2013

IdentifyingNumber : {90150000-1014-0000-1000-0000000FF1CE}
Name : Microsoft SharePoint Foundation 2013 Core
Vendor : Microsoft Corporation
Version : 15.0.4569.1506
Caption : Microsoft SharePoint Foundation 2013 Core

IdentifyingNumber : {90150000-1015-0409-1000-0000000FF1CE}
Name : Microsoft SharePoint Foundation 2013 1033 Lang Pack
Vendor : Microsoft Corporation
Version : 15.0.4569.1506
Caption : Microsoft SharePoint Foundation 2013 1033 Lang Pack

IdentifyingNumber : {90150000-1158-0409-1000-0000000FF1CE}
Name : Microsoft SharePoint Foundation 2013 1033 SQL Express
Vendor : Microsoft Corporation
Version : 15.0.4569.1506
Caption : Microsoft SharePoint Foundation 2013 1033 SQL Express

PS C:\> Get-CimInstance -ClassName Win32_Product -Filter "Name like 'Microsoft SharePoint%'" | format-list

IdentifyingNumber : {90140000-1110-0000-1000-0000000FF1CE}
Name : Microsoft SharePoint Foundation 2010
Vendor : Microsoft Corporation
Version : 14.0.7015.1000
Caption : Microsoft SharePoint Foundation 2010

IdentifyingNumber : {90140000-1014-0000-1000-0000000FF1CE}
Name : Microsoft SharePoint Foundation 2010 Core
Vendor : Microsoft Corporation
Version : 14.0.7015.1000
Caption : Microsoft SharePoint Foundation 2010 Core

IdentifyingNumber : {90140000-1015-0409-1000-0000000FF1CE}
Name : Microsoft SharePoint Foundation 2010 1033 Lang Pack
Vendor : Microsoft Corporation
Version : 14.0.7015.1000
Caption : Microsoft SharePoint Foundation 2010 1033 Lang Pack

Commented Unassigned: SP2016 Central Admin DB in compatibility mode [22220]

$
0
0
Just ran the 21 March 2016 AutoSPInstaller against the SP2016 RTM (trial) media.

Install process went fine.

However the Central Admin content DB has been left in compatibility mode:

```
Database Schema Versions

Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 16.0.79.0, Maximum Schema Version: 16.0.79.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSprocsSequence Current Schema Version: 16.0.93.0, Maximum Schema Version: 16.0.93.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 16.0.4.0, Maximum Schema Version: 16.0.4.0
Microsoft.SharePoint.Upgrade.SPGlobalExtensionUpgradeSequence Current Schema Version: 16.0.6.0, Maximum Schema Version: 16.0.6.0
Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__
```

I'll run a PSConfig and see if it cleans it up.
Comments: ** Comment from web user: Emblematic **

A standard install using the GUI gave me the same results, so I don't think this is an AutoSPInstaller problem. Interestingly looks like all the database versions are unchanged from the release candidate, my config db is at 16.0.__4327__.1000 and the binaries at 16.0.__4351__.1000

Doubtless it will get tidied up once the CUs start rolling.

```Database Schema Versions

Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 16.0.79.0, Maximum Schema Version: 16.0.79.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSprocsSequence Current Schema Version: 16.0.93.0, Maximum Schema Version: 16.0.93.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 16.0.4.0, Maximum Schema Version: 16.0.4.0
Microsoft.SharePoint.Upgrade.SPGlobalExtensionUpgradeSequence Current Schema Version: 16.0.6.0, Maximum Schema Version: 16.0.6.0
Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: 4.0.0.0, Maximum Schema Version: 16.1.273.0
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: 16.0.4327.1000, Maximum Schema Version: 16.0.4315.1000```

Commented Issue: Function Get-SharePointInstall fails for Foundation [22165]

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

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

Probably needs to have an additional check for Foundation, if the detection needs to avoid false positives from SP Designer etc.
Comments: ** Comment from web user: Emblematic **

Oops - old method! Results are much the same though:
```
PS C:\> $val= Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "Microsoft SharePoint*"}
PS C:\> $val.DisplayName
Microsoft SharePoint Foundation 2013
Microsoft SharePoint Foundation 2013 Core
Microsoft SharePoint Foundation 2013 1033 Lang Pack
Microsoft SharePoint Foundation 2013
Microsoft SharePoint Foundation 2013 1033 SQL Express

PS C:\> $val= Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "Microsoft SharePoint*"}
PS C:\> $val.DisplayName
Microsoft SharePoint Foundation 2010
Microsoft SharePoint Foundation 2010 Core
Microsoft SharePoint Foundation 2010 1033 Lang Pack
Microsoft SharePoint Foundation 2010
```

New Post: Add Users or Groups to Farm Administrators group within Central Admin.

$
0
0
I like this one. Generally, I'll have a Windows Group such as SharePoint [Farm Designator] Administrators and add users to the group. Then, manually:
  1. Add group to Local Administrators on all farm servers
  2. Add group to CA -> Security -> Farm Administrators
  3. Add group to CA -> Site Collection Admins
  4. Grant group permissions on Service Applications where needed
  5. Grant permissions in SQL Server

Commented Unassigned: SP2016 Central Admin DB in compatibility mode [22220]

$
0
0
Just ran the 21 March 2016 AutoSPInstaller against the SP2016 RTM (trial) media.

Install process went fine.

However the Central Admin content DB has been left in compatibility mode:

```
Database Schema Versions

Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 16.0.79.0, Maximum Schema Version: 16.0.79.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSprocsSequence Current Schema Version: 16.0.93.0, Maximum Schema Version: 16.0.93.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 16.0.4.0, Maximum Schema Version: 16.0.4.0
Microsoft.SharePoint.Upgrade.SPGlobalExtensionUpgradeSequence Current Schema Version: 16.0.6.0, Maximum Schema Version: 16.0.6.0
Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__
```

I'll run a PSConfig and see if it cleans it up.
Comments: ** Comment from web user: CraigHumphrey **

Well done, I was just building a VM to do the same.

Looks like one to push up to Microsoft (how did this get out the door on RTM!!)


Created Unassigned: SP2016 - "Portal" Managed Account problem [22225]

$
0
0
Hello!

Respect for all the work guys!
While installing SP2016 RTM on Win Srv 2012 Std + SQL 2014 SP1 everthing goes right (web apps, dbs and sites work fine) until the error is displayed:
__Error Provisioning the User Profiles Service Application__
But before that we can see __"Portal" Managed Account not found. Check your XML!__
![Image](http://7dots.pl/bullvan/SP2016-AutoSpIntall_PortalAccount.jpg)

This is Because I changed the __Common Name__ of "Portal" account in Online Configurator - after twitching output XML to contain "Portal" as this account's Common Name the Installer Worked fine. It probably should not be editable like __spservice__ account...

I know that Online Configurator is not supported for SP2016, but maybe if it is in the future take this under consideration.

Thanks again for your work! Rock on, Bullvan

Commented Unassigned: Create Project Server Web Instance on Custom Web Application [22096]

$
0
0
We are not using the "Portal" web application to host Project server instances.

The out of the box script creates the project server web instances on the web application using the "Portal" type.

I modified the Config XML file and Installerfunction powershell file as follows to install on another web app:

Config.XML - added two new keys: WebAPP and WebAppPort

```
<ProjectServer Install="true" ConfigFile="config-ProjectServer2013.xml" PIDKeyProjectServer="TBD">
<ServiceApp Provision="ServerName" Name="Project Server Service Application" ProxyName="Project Server Service Application" ManagedPath="PWA" ServiceAccount="Domain\account" ServiceAccountPassword="TBD
WebApp="https://foo.com" WebAppPort="" >
```

Modified the InstallerFucntion file

```
# Create a Project Server Web Instance around line 5803
$projectManagedPath = $xmlinput.Configuration.ProjectServer.ServiceApp.ManagedPath
$projectWebApp = $xmlinput.Configuration.ProjectServer.ServiceApp.WebApp #this is new
$projectWebAppPort = $xmlinput.Configuration.ProjectServer.ServiceApp.WebAppPort #this is new
New-SPManagedPath -RelativeURL $xmlinput.Configuration.ProjectServer.ServiceApp.ManagedPath -WebApplication $projectWebApp -Explicit:$true -ErrorAction SilentlyContinue | Out-Null #this is modified
Write-Host -ForegroundColor White " - Creating Project Server site collection at `"$projectManagedPath`"..." -NoNewline
$projectSiteUrl = $projectWebApp+":"+$projectWebAppPort+"/"+$projectManagedPath #this is modified
```
Comments: ** Comment from web user: thefeds **

Is there any update for this bug? When I edit the .XML file and the InstallerFunction file the script stops due to not finding the SP installer version.

New Post: Script Haulting during portal Site Creation

$
0
0

- Granting i:0#.w|NAU\fgallardo Full Control to https://portal.sp2013dev.ucc.nau.edu:8443/...

- Creating Site Collection "https://portal.sp2013dev.ucc.nau.edu"...

  • Script halted!
Exception : Microsoft.SharePoint.PowerShell.SPCmdletPipeBindException: Cannot find an SPWebApplication
                    object that contains the following Name, Id, or Url: https://portal.sp2013dev.ucc.nau.edu.
                       at Microsoft.SharePoint.PowerShell.SPWebApplicationPipeBind.Read(Boolean exactUrl)
                       at Microsoft.SharePoint.PowerShell.SPCmdletNewSite.InternalValidate()
                       at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()
TargetObject : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
CategoryInfo : InvalidData: (Microsoft.Share...SPCmdletNewSite:SPCmdletNewSite) [New-SPSite],
                    SPCmdletPipeBindException
FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, C:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2889
                    at CreateWebApplications, C:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
                    line 2670
                    at Setup-Farm, C:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 211
                    at <ScriptBlock>, C:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 410
                    at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :


Here is the log file:
PS>TerminatingError(New-SPSite): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot find an SPWebApplication object that contains the following Name, Id, or Url: https://portal.sp2013dev.ucc.nau.edu."
TerminatingError(New-SPSite): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot find an SPWebApplication object that contains the following Name, Id, or Url: https://portal.sp2013dev.ucc.nau.edu."
TerminatingError(New-SPSite): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot find an SPWebApplication object that contains the following Name, Id, or Url: https://portal.sp2013dev.ucc.nau.edu."
TerminatingError(New-SPSite): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot find an SPWebApplication object that contains the following Name, Id, or Url: https://portal.sp2013dev.ucc.nau.edu."
Exception : Microsoft.SharePoint.PowerShell.SPCmdletPipeBindException: Cannot find an SPWebApplication
                    object that contains the following Name, Id, or Url: https://portal.sp2013dev.ucc.nau.edu.
                       at Microsoft.SharePoint.PowerShell.SPWebApplicationPipeBind.Read(Boolean exactUrl)
                       at Microsoft.SharePoint.PowerShell.SPCmdletNewSite.InternalValidate()
                       at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()
TargetObject : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
CategoryInfo : InvalidData: (Microsoft.Share...SPCmdletNewSite:SPCmdletNewSite) [New-SPSite],
                    SPCmdletPipeBindException
FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, C:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2889
                    at CreateWebApplications, C:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:
                    line 2670
                    at Setup-Farm, C:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 211
                    at <ScriptBlock>, C:\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 410
                    at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

New Post: Script Haulting during portal Site Creation

$
0
0
Please disregard this, I failed to update the Site Collection in my .XML file

New Post: Donation?

$
0
0
Done and done! Took a little bit longer than I hoped but it was kinda expected. Thanks again Brian for all the work you've put into creating/maintaining this project.. I appreciate it more than you know!

Andy
Viewing all 2279 articles
Browse latest View live