Quantcast
Channel: autospinstaller Issue Tracker Rss Feed
Viewing all 1245 articles
Browse latest View live

Commented Feature: Function "Add-SQLAlias" does not add a 32bit alias [21941]

$
0
0
I realized today that the SQL Client Alias I have configured using AutoSPInstaller only adds a 64bit alias and not a 32bit alias. This is not a problem for straight SharePoint 2013 but it became a problem when I tried to configure Workflow Manager 1.0 on the server. It was not able to connect with the connection string I supplied because there is not 32bit alias matching the name I have in the string. WorkflowManager will not be the only thing that would need the alias, so I think having it included is pretty much a must-have.

My solution going forward for AutoSPInstaller is that I have modified the function and saved it to my "AutoSPInstallerFunctionsCustom.ps1" file. I've also pasted the modified function below if you're interested.
```
Function Add-SQLAlias()
{
<#
.Synopsis
Add a new SQL server Alias
.Description
Adds a new SQL server Alias with the provided parameters.
This custom version also adds the 32bit alias for the same.
.Example
Add-SQLAlias -AliasName "SharePointDB" -SQLInstance $env:COMPUTERNAME
.Example
Add-SQLAlias -AliasName "SharePointDB" -SQLInstance $env:COMPUTERNAME -Port '1433'
.Parameter AliasName
The new alias Name.
.Parameter SQLInstance
The SQL server Name os Instance Name
.Parameter Port
Port number of SQL server instance. This is an optional parameter.
#>
[CmdletBinding(DefaultParameterSetName="BuildPath+SetupInfo")]
param
(
[Parameter(Mandatory=$false, ParameterSetName="BuildPath+SetupInfo")][ValidateNotNullOrEmpty()]
[String]$aliasName = "SharePointDB",

[Parameter(Mandatory=$false, ParameterSetName="BuildPath+SetupInfo")][ValidateNotNullOrEmpty()]
[String]$SQLInstance = $env:COMPUTERNAME,

[Parameter(Mandatory=$false, ParameterSetName="BuildPath+SetupInfo")][ValidateNotNullOrEmpty()]
[String]$port = ""
)

If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\"))) {
$protocol = "dbmslpcn" # Shared Memory
}
else {
$protocol = "DBMSSOCN" # TCP/IP
}

$serverAliasConnection="$protocol,$SQLInstance"
If ($port -ne "")
{
$serverAliasConnection += ",$port"
}
$notExist = $true
$client = Get-Item 'HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client' -ErrorAction SilentlyContinue
# Create the key in case it doesn't yet exist
If (!$client) {$client = New-Item 'HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client' -Force}
$client.GetSubKeyNames() | ForEach-Object -Process { If ( $_ -eq 'ConnectTo') { $notExist=$false }}
If ($notExist)
{
$data = New-Item 'HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo'
}
# Add the 64bit Alias
$data = New-ItemProperty HKLM:\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo -Name $aliasName -Value $serverAliasConnection -PropertyType "String" -Force -ErrorAction SilentlyContinue
#
#
### Below is the part that is new. It's basically the same as the lines above added in but this time it will include the 32bit SQL Client Alias
$notExist = $true
$client = Get-Item 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo' -ErrorAction SilentlyContinue
# Create the key in case it doesn't yet exist
If (!$client) {$client = New-Item 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client' -Force}
$client.GetSubKeyNames() | ForEach-Object -Process { If ( $_ -eq 'ConnectTo') { $notExist=$false }}
If ($notExist)
{
$data = New-Item 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo'
}
# Add Alias
$data = New-ItemProperty HKLM:\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo -Name $aliasName -Value $serverAliasConnection -PropertyType "String" -Force -ErrorAction SilentlyContinue
}
```
Comments: ** Comment from web user: loknar777 **

Workflow Manager 1.0 (at least Refresh/CU2 version) use 64-bit aliases.
Have never had this issue with WFM (always used aliases to setup farm).


Created Unassigned: SP2016 : TerminatingError(Get-SPFarm) [22276]

$
0
0
PS>TerminatingError(Get-SPFarm): "Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permissions to access the database before trying again."

- Installing SharePoint Language Packs:
- Installing extracted language pack nl-nl........Done.
- Language pack nl-nl setup completed in 00:00:38.
- Language Pack installation complete.
- Currently installed languages:
- English (United States)
- Dutch (Netherlands)

Solution : remove Installing Dutch Language Pack

Regards,
Reg

Commented Unassigned: Error creating SQL alias [22054]

$
0
0
When attempting to create an alias, autoSPinstaller creates a Shared Memory alias and not a tcp-ip alias. This prevents autospinstaller from connecting to SQL when creating a new farm.
Comments: ** Comment from web user: PerrySharePoint **

Just struggled through finding this same bug. It is still broken.

Going to need to hack around this in Add-SQLAlias in AutoSPInstallerFunctions.ps1

Commented Unassigned: SQL server alias on local machine is always created using shared memory despite the port is specified [20475]

$
0
0
I am installing all-in-one machine having SQL and sharepoint. I am specifying the sql alias for the same machine and the port as I want to have TCP connection. however the script tries to create the shared memory connection .

my computer is DEV1
my config is
<Database>
<DBServer>SPSQL</DBServer>
<DBAlias Create="true" DBInstance="DEV1" DBPort="1433" />
<DBPrefix>SP</DBPrefix>
<ConfigDB>Config</ConfigDB>
</Database>


solution:
change function Add-SQLAlias

replace the line
If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\"))) {

with
If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\")) -and ($port-eq '')) {
Comments: ** Comment from web user: PerrySharePoint **

Just struggled through finding this same bug.

It would be great if this were fixed in the source, so the next person doesn't have to spend the time trying to figure out why it doesn't work, and tracing it back into the powershell, and then coming up with some manual hack around this problem.

(I don't know why the local memory provider option is broken, but that is less relevant to me than getting the install to work.)

Commented Unassigned: Error creating SQL alias [22054]

$
0
0
When attempting to create an alias, autoSPinstaller creates a Shared Memory alias and not a tcp-ip alias. This prevents autospinstaller from connecting to SQL when creating a new farm.
Comments: ** Comment from web user: PerrySharePoint **

Just submitted patch 18261 to fix this.

Commented Unassigned: SQL server alias on local machine is always created using shared memory despite the port is specified [20475]

$
0
0
I am installing all-in-one machine having SQL and sharepoint. I am specifying the sql alias for the same machine and the port as I want to have TCP connection. however the script tries to create the shared memory connection .

my computer is DEV1
my config is
<Database>
<DBServer>SPSQL</DBServer>
<DBAlias Create="true" DBInstance="DEV1" DBPort="1433" />
<DBPrefix>SP</DBPrefix>
<ConfigDB>Config</ConfigDB>
</Database>


solution:
change function Add-SQLAlias

replace the line
If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\"))) {

with
If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\")) -and ($port-eq '')) {
Comments: ** Comment from web user: PerrySharePoint **

Just submitted patch 18261 to fix this (using above fix).

Commented Issue: SQL alias TCP/IP incorrectly determined [20908]

$
0
0
Yesterday I experienced the following where
- SP server: INTRANETS
- SQL server: INTRANETSQL

This caused the SQL client alias to be created as Shared Memory instead of TCP/IP, because the server name matching logic would incorrectly return true.
Comments: ** Comment from web user: PerrySharePoint **

Just submitted patch 18261 which provides a workaround for this.

Commented Issue: Creates "wrong" format of SQL Client Alias [20228]

$
0
0
Tried allowing it to create an alias for me.

Parameters I provided in the script:
DBServer (or alias name if creating alias): SPSQL
Create Instance: TRUE
Instance Name: SQL01
PORT: 1433

The alias that it created had following settings:

Alias: SPSQL
Network Libraries: Other
File name: DBMSLPCN
Parameters: SPAPP03 (the machine on which I am running the script)
(Screen shot attached)

I looked in the functions PS1 and saw where its hardwiring the protocol to DBMSLPCN.


```
If ((MatchComputerName $SQLInstance $env:COMPUTERNAME) -or ($SQLInstance.StartsWith($env:ComputerName +"\"))) {
$protocol = "dbmslpcn"
}
else {
$protocol = "DBMSSOCN"
}

```

When I create SQL aliases I always use TCP/IP.
I've never used any other format and this appears to be the consensus.

I can tell you that when the script tries to use the weirdo alias format it creates it fails to establish communication with SQL.


If I pre-create the Alias and simply reference the alias in the script it communicates fine.

My assumption is that this format of Client Alias is no good.

Can you please advise?

Thanks much.
Comments: ** Comment from web user: PerrySharePoint **

autospinstaller with the xml has this same bug, and it causes the install to fail until the ps1 is fixed. (There are other issues reporting this problem as well.)

I just submitted a patch which provides a workaround--the user has to specify a dbport for every alias that will be used, to inform the ps1 to use tcpip aliases.

Just submitted patch 18261 to fix this.


Commented Unassigned: Why Add-SPShellAdmin fails [22139]

$
0
0
The error:

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

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

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

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


Note:

The SP_DATA_ACCESS role replaces the db_owner role in SharePoint 2013.

The SP_DATA_ACCESS role will have the following permissions:

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

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

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

We see this error a lot; thanks for posting info about it.

Would you be willing to post the code you used to fix the ps1 to avoid this error?

Created Unassigned: error Get-Process $pPatchFileName [22279]

$
0
0
I'm getting this error:
>> Patching now keep this PowerShell window open ...
Get-Process : Cannot find a process with the name "ubersrv2013-kb3115029-fullfile-x64-glb". Verify the process name
and call the cmdlet again.
At E:\software\patch\AutoSPCUInstaller_Func.ps1:235 char:11
+ $proc = Get-Process $pPatchFileName
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (ubersrv2013-kb3115029-fullfile-x64-glb:String) [Get-Process], ProcessCo
mmandException
+ FullyQualifiedErrorId : NoProcessFoundForGivenName,Microsoft.PowerShell.Commands.GetProcessCommand

> Could not get the installation process.

I know there the application found it earlier because it said it was found. I'm guessing there is a resolution for this since you were trapping the error. I was not able to find the resolution. Any help you can give is appreciated.

Regard,
Scott

Commented Unassigned: SP2016 offline prerequisites [22153]

$
0
0
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`""
Comments: ** Comment from web user: tolamac **

I have to perform only one replacement /WCFDataServices56:"$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe`""

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: franky113 **

We have the same problem. We try to install SP2016 on Server 2012R2 with a separate SQL 2016 Server.
The fix works fine, but is there any update or idea how to solve the problem without deleting the wep app and launch the script again?

Created Unassigned: SharePoint 2016 updates are not applied due to naming convention [22292]

$
0
0
When I put the CU Files of the May 2016 CU for SharePoint 2016 into the update folder, they are not applied. This is due to the naming convention, which seems to have changed. I have the following files in the CU:

sts2016-kb3115088-fullfile-x64-glb.exe
wssloc2016-kb2920690-fullfile-x64-glb.exe

Commented Unassigned: SharePoint 2016 updates are not applied due to naming convention [22292]

$
0
0
When I put the CU Files of the May 2016 CU for SharePoint 2016 into the update folder, they are not applied. This is due to the naming convention, which seems to have changed. I have the following files in the CU:

sts2016-kb3115088-fullfile-x64-glb.exe
wssloc2016-kb2920690-fullfile-x64-glb.exe
Comments: ** Comment from web user: owarya **

+1 this.

sts2016-kb3115181-fullfile-x64-glb.exe (June 2016) was also ignored. Installed it manually during the pause after SharePoint binary installation.

Created Unassigned: Possibility of Creating multiple Managed Metadata Service Application [22300]

$
0
0
I need to create a new MMS for use with RecordPoint however current AutoSPInstaller will not allow more than 1 MMS created as the function CreateMetadataServiceApp checks on the SPServiceInstance type rather than the display name as such

> $metadataServiceInstances = Get-SPServiceInstance | ? {$_.GetType().ToString() -eq "Microsoft.SharePoint.Taxonomy.MetadataWebServiceInstance"}

> $metaDataServiceAppProxy = Get-SPServiceApplicationProxy | ? {$_.GetType().ToString() -eq "Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplicationProxy"}

Changing it to the following solved my pain.

> $metadataServiceInstances = Get-SPServiceInstance | ? {$_.DisplayName -eq $metadataServiceName}

> $metaDataServiceAppProxy = Get-SPServiceApplicationProxy | ? {$_.DisplayName -eq $metadataServiceProxyName }

I was wondering can this flexibility be incorporated in AutoSPInstaller for the benefit of others who have similar requirement as mine?

Created Unassigned: Stop-DefaultWebsite stops wrong IIS website [22333]

$
0
0
Function Stop-DefaultWebsite

Specifically
```
$defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.ID -eq 1 -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}

```
Stops wrong site. In my case it stopped SPWeb services
```

Name ID State Physical Path Bindings
---- -- ----- ------------- --------
SharePoint Web 1 Started C:\Program Files\Common http *:32843:
Services Files\Microsoft Shared\Web https *:32844:
Server sslFlags=0
Extensions\16\WebServices\Root net.tcp 32845:*
net.pipe *

```
please remove this from where statement
```
$_.ID -eq 1
```

Commented Unassigned: SharePoint 2016 updates are not applied due to naming convention [22292]

$
0
0
When I put the CU Files of the May 2016 CU for SharePoint 2016 into the update folder, they are not applied. This is due to the naming convention, which seems to have changed. I have the following files in the CU:

sts2016-kb3115088-fullfile-x64-glb.exe
wssloc2016-kb2920690-fullfile-x64-glb.exe
Comments: ** Comment from web user: KoenZomers **

Same issue here. It comes down to the line in AutoSPInstallerFunctions.ps1 where it states:

```
$cumulativeUpdates = Get-ChildItem -Path "$bits\$spYear\Updates" -Name -Include office2010*.exe,ubersrv*.exe,ubersts*.exe,*pjsrv*.exe,sharepointsp2013*.exe,coreserver201*.exe -Recurse -ErrorAction SilentlyContinue | Where-Object {$_ -notlike "*ubersrvsp2013-kb2767999-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrvprjsp2013-kb2768001-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrv2010-kb2817527-fullfile-x64-glb.exe"} | Sort-Object -Descending
```

It should be:

```
$cumulativeUpdates = Get-ChildItem -Path "$bits\$spYear\Updates" -Name -Include office2010*.exe,ubersrv*.exe,ubersts*.exe,*pjsrv*.exe,sharepointsp2013*.exe,coreserver201*.exe,sts2016-kb*.exe,wssloc2016-kb*.exe -Recurse -ErrorAction SilentlyContinue | Where-Object {$_ -notlike "*ubersrvsp2013-kb2767999-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrvprjsp2013-kb2768001-fullfile-x64-glb.exe" -and $_ -notlike "*ubersrv2010-kb2817527-fullfile-x64-glb.exe"} | Sort-Object -Descending
```

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

$
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>

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

$
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: venukasa **

Please help I struck here

Created Unassigned: WebAdministration Error 2012 R2 [22344]

$
0
0
I have set the XML file up correctly and have all the pre-req's installed. About midway through the script when it starts creating webapplications it errors out saying the PowerShell module "WebAdministration" is not loaded. Attempting to do Import-Module does not work.
Viewing all 1245 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>