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

New Post: SharePoint 2016 RTM Fails to find binaries

May 4, 2016, 8:46 pm
$
0
0
First, validate your XML input file at https://autospinstaller.com to make sure it doesn't contain any syntax errors etc. Then, you can simply drag your input XML file (whatever it's called) onto the batch file - it will automatically use it and self-elevate to run as administrator.

Brian
↧
Search

Edited Issue: Function Install-WindowsIdentityFoundation amendment [22238]

May 4, 2016, 8:52 pm
$
0
0
Hi There, fooling around with Windows 2016 remote install of WFE,

need to amend the autospinstallerfunctions.ps1 line 6661 to something similar to this...

If (!($remoteQueryOS.Version.Contains("6.2")) -and !($remoteQueryOS.Version.Contains("6.3")) -and !($remoteQueryOS.Version.StartsWith("10"))) # Only perform the stuff below if we aren't on Windows 2012 or 2012 R2 OR 2016

to cope with the new Windows OS. My amended fie attached.

cheers,
Ralph Dalton
Comments: ** Comment from web user: brianlala **

Thanks, will be in the next release.

Cheers
Brian

↧
↧

Edited Issue: Change "Stop-DefaultWebsite" function logic [22232]

May 4, 2016, 9:01 pm
$
0
0
If you removed "Default Web Site" prior to setup SharePoint farm, then "SharePoint Web Services" will have an ID = 1.
When you try to provision first Web App, "SharePoint Web Services" site stopped and you're end up with AccessDenied exception because of STS is not available.

Please remove condition of trying to get Default Web Site by ID = 1:
change line
* $defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.ID -eq 1 -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}
to
* $defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}
↧

New Post: SP2016 and ServerRoleOptional

May 5, 2016, 9:08 pm
$
0
0
How do I use ServerRoleOptional parameter with spautoinstaller? Does ServerRoleOptional equal Custom role?
↧

New Post: TerminatingError(Get-SPFarm)

May 6, 2016, 6:13 am
$
0
0
Thanks Brian, we narrowed the issue down to a big Windows Update (KB3000850) so we're just excluding that update for the time being.
↧
↧

Created Unassigned: Description not used when creating Site Collections [22260]

May 10, 2016, 8:44 am
$
0
0
When a site collection is being created the sitename is being used for both the name and description.
↧

Commented Issue: Change "Stop-DefaultWebsite" function logic [22232]

May 10, 2016, 9:13 am
$
0
0
If you removed "Default Web Site" prior to setup SharePoint farm, then "SharePoint Web Services" will have an ID = 1.
When you try to provision first Web App, "SharePoint Web Services" site stopped and you're end up with AccessDenied exception because of STS is not available.

Please remove condition of trying to get Default Web Site by ID = 1:
change line
* $defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.ID -eq 1 -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}
to
* $defaultWebsite = Get-Website | Where-Object {$_.Name -eq "Default Web Site" -or $_.physicalPath -eq "%SystemDrive%\inetpub\wwwroot"}
Comments: ** Comment from web user: noral **

The error is tricky too -
```
System.UnauthorizedAccessException:
<nativehr>0x80070005</nativehr><nativestack></nativestack>Access denied.
```
It took me some time to figure out that __SharePoint Web Services__ was stopped in IIS.

Thank you @loknar777!

↧

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

May 10, 2016, 1:54 pm
$
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).

↧
Search

New Post: What is the 'experimental' Foundation 2013 support??

May 23, 2016, 1:34 pm
$
0
0
I agree with the previous post. My attempted Foundation installation ended up with me running several manual scripts to finish the installation. I install Foundation fairly regularly since we have other s/w that uses it. Not sure if AutoSPIntaller makes it much better...yet. Might try it again, though.
↧
↧

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

May 25, 2016, 12:50 am
$
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]

May 25, 2016, 10:12 am
$
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]

May 25, 2016, 10:16 am
$
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.)

↧

Patch Uploaded: #18261

May 25, 2016, 10:33 am
$
0
0

PerrySharePoint has uploaded a patch.

Description:

Fix Add-SQLAlias to use TCPIP port if port specified, to avoid getting stuck with autospinstaller never working because it will only create Shared Memory aliases, which for whatever reason do not work with it.

This provides the user a reasonable workaround to be able to install on a single server; the user does have to go through and specify dbport for every alias in use, but they do not have to edit the .ps1 file to fix it.

$ diff -Naur AutoSPInstallerFunctions.ps1_original.txt AutoSPInstallerFunctions.ps1_fixed.txt > FixSqlAlias.txt

↧
↧

Commented Unassigned: Error creating SQL alias [22054]

May 25, 2016, 10:34 am
$
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]

May 25, 2016, 10:35 am
$
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).

↧
Search

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

May 25, 2016, 10:35 am
$
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]

May 25, 2016, 10:37 am
$
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]

May 25, 2016, 4:01 pm
$
0
0
The error:

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

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

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

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


Note:

The SP_DATA_ACCESS role replaces the db_owner role in SharePoint 2013.

The SP_DATA_ACCESS role will have the following permissions:

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

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

So I guess a new fix is on the way Brian :-)
Comments: ** Comment from web user: 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]

May 27, 2016, 2:24 pm
$
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]

June 4, 2016, 7:10 am
$
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`""

↧
Viewing all 2279 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>