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

Created Unassigned: Outgoing Email SP2016 tls yes bug [22426]

December 13, 2016, 5:48 am
$
0
0
This line:
$spGlobalAdmin.UpdateMailSettings($SMTPServer, $emailAddress, $replyToEmail, 65001)

for Sharepoint 2016 must be:
$spGlobalAdmin.UpdateMailsettings($smtpServer, $senderAddr, $replyAddr, 65001, $false, 25)
or for SharePoint 2016 with tsl:
$spGlobalAdmin.UpdateMailsettings($smtpServer, $senderAddr, $replyAddr, 65001, $true, 587)
↧
Search

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

December 13, 2016, 8:24 am
$
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: hWeishaupt **

This issue has been fixed in the latest release (with commit:117940)

↧
↧

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

December 13, 2016, 10:44 am
$
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: brianlala **

Yes thank you for pointing that out - cheers.

Brian

↧

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

December 13, 2016, 10:44 am
$
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
↧

Created Unassigned: Offline Prerequisite Installer Issue on Windows Server 2016 [22430]

December 18, 2016, 11:11 pm
$
0
0
Hi All,

I am in the process of testing the AutoSPInstaller script in the following SharePoint environment setup.

- Windows Server 2016 RTM
- SQL 2016
- SharePoint 2016 with November 2016 CU.

I have noticed that the AutoSPInstallerFunctions.ps1 script refers to a file with the incorrect name and this causes the script to fail when carrying out an offline prerequisite installation.

Line: 734
$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices.exe

Should be:

$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe

Hope this helps some of you! :)
↧
↧

Created Unassigned: AutoSPInstaller Hangs will creating services [22431]

December 19, 2016, 1:15 am
$
0
0
Hi,

I am in the process of testing the AutoSPInstaller script for the following environment:

Windows Server 2016 RTM
SQL Server 2016
SharePoint 2016 + November 2016 CU

I have noticed that on numerous occasions the installation script hangs while trying to create various services.

Until now I have seen the installer script stop while trying to provision the following services:

- App Management Service
- Machine Translation Service
- Managed Metadata Service

Can anyone provide any insight into why this might happen?

Thanks!
↧

Commented Unassigned: Offline Prerequisite Installer Issue on Windows Server 2016 [22430]

December 19, 2016, 6:08 am
$
0
0
Hi All,

I am in the process of testing the AutoSPInstaller script in the following SharePoint environment setup.

- Windows Server 2016 RTM
- SQL 2016
- SharePoint 2016 with November 2016 CU.

I have noticed that the AutoSPInstallerFunctions.ps1 script refers to a file with the incorrect name and this causes the script to fail when carrying out an offline prerequisite installation.

Line: 734
$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices.exe

Should be:

$env:SPbits\PrerequisiteInstallerFiles\WcfDataServices56.exe

Hope this helps some of you! :)
Comments: ** Comment from web user: brianlala **

No - this situation was due to a bug in the AutoSPSourceBuilder where it renamed WcfDataServices to WcfDataServices56 for 2016 (should only have applied to 2013. Rename the prerequisite file instead (and get a newer version of AutoSPSourceBuilder); no changes to AutoSPInstaller needed.

See https://autospinstaller.codeplex.com/workitem/22386 for previous fix

Brian

↧

Commented Unassigned: Excel Services Provisioning [22384]

December 21, 2016, 2:28 pm
$
0
0
I am running the latest AutoSPInstaller and keep getting the following error:

```
New-SPExcelServiceApplication : The term 'New-SPExcelServiceApplication' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the
path is correct and try again.
At D:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:5535 char:40
+ $excelServiceApp = New-SPExcelServiceApplication -name $exce ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (New-SPExcelServiceApplication:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


PS>TerminatingError(): " - Error provisioning Excel Service Application"
>> TerminatingError(): " - Error provisioning Excel Service Application"

```

Please help
Comments: ** Comment from web user: RainerJ **

Hi,
which SharePoint version? SharePoint 2016 does no longer contain Excel Services, they have been moved to Office Online Server (the next version of Office Web Apps Server).

The command should only work for SharePoint 2010 and 2013.

↧
Search

Commented Unassigned: Excel Services Provisioning [22384]

December 21, 2016, 4:17 pm
$
0
0
I am running the latest AutoSPInstaller and keep getting the following error:

```
New-SPExcelServiceApplication : The term 'New-SPExcelServiceApplication' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the
path is correct and try again.
At D:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:5535 char:40
+ $excelServiceApp = New-SPExcelServiceApplication -name $exce ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (New-SPExcelServiceApplication:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException


PS>TerminatingError(): " - Error provisioning Excel Service Application"
>> TerminatingError(): " - Error provisioning Excel Service Application"

```

Please help
Comments: ** Comment from web user: Bryan_H **

I should have updated this. It was for a 2013 deployment. The issue was resolved. The problem was that the client provided a license key for SharePoint standard and not enterprise. Once the proper key was provided the install with ASPI completed as expected.

↧
↧

Commented Unassigned: AutoSPInstaller Hangs will creating services [22431]

January 2, 2017, 2:06 pm
$
0
0
Hi,

I am in the process of testing the AutoSPInstaller script for the following environment:

Windows Server 2016 RTM
SQL Server 2016
SharePoint 2016 + November 2016 CU

I have noticed that on numerous occasions the installation script hangs while trying to create various services.

Until now I have seen the installer script stop while trying to provision the following services:

- App Management Service
- Machine Translation Service
- Managed Metadata Service

Can anyone provide any insight into why this might happen?

Thanks!
Comments: ** Comment from web user: SrikanthSetti **

Hello,

I'm also facing similar issue. The script stopped while creating App Management Service. When I checked the service application status in Central Administration the status shows "Starting".

My configuration:
Windows Server 2012 R2
SQL Server 2012
SP 2016 (no feature pack installed)

Please share if you find any clue.
Thanks!

↧

Commented Unassigned: AutoSPInstaller Hangs will creating services [22431]

January 3, 2017, 10:21 am
$
0
0
Hi,

I am in the process of testing the AutoSPInstaller script for the following environment:

Windows Server 2016 RTM
SQL Server 2016
SharePoint 2016 + November 2016 CU

I have noticed that on numerous occasions the installation script hangs while trying to create various services.

Until now I have seen the installer script stop while trying to provision the following services:

- App Management Service
- Machine Translation Service
- Managed Metadata Service

Can anyone provide any insight into why this might happen?

Thanks!
Comments: ** Comment from web user: SrikanthSetti **

Myatix,

I found the solution. When the script pauses and does not progress even after hours of waiting while provisioning above services, please restart the respective services along with the SP Foundation Subscription Settings Service from Central Administration>System Settings>Manage Services on Server.

Please let me know if this solution worked for you.

↧

Created Unassigned: Central admin database need upgrade [22445]

January 8, 2017, 8:38 am
$
0
0
I have just built 3 SharePoint 2016 Farm with December 2016 CU. All the 3 Farms had their Central admin content database requiring upgrade.

I had to run:


(Get-SPWebApplication -IncludeCentralAdministration | ? {$_.DefaultServerComment -match "SharePoint Central Administration V4"}).contentdatabases | Upgrade-SPContentDatabase

in order to fix it.
↧

Commented Unassigned: Central admin database need upgrade [22445]

January 9, 2017, 8:13 am
$
0
0
I have just built 3 SharePoint 2016 Farm with December 2016 CU. All the 3 Farms had their Central admin content database requiring upgrade.

I had to run:


(Get-SPWebApplication -IncludeCentralAdministration | ? {$_.DefaultServerComment -match "SharePoint Central Administration V4"}).contentdatabases | Upgrade-SPContentDatabase

in order to fix it.
Comments: ** Comment from web user: brianlala **

Hey Joseph, haven't noticed this myself yet. Any language packs in the equation? Are you thinking this is somehow introduced by AutoSPInstaller itself, and not just maybe the slipstreaming process etc.?

Brian

↧
↧

Commented Issue: Corner case bug in MatchComputerName function [21419]

January 12, 2017, 11:35 am
$
0
0
On line 6894 of AutoSPInstallerFunctions.ps1 is the following line of code:

```
If ($computersList -like "*$computerName*") { Return $true; }
```

While this is a nice one-liner, it will not work correctly if one computer name is subset of another. For example, assume that there is an app server named Box1 and a WFE named Box11. In this case Box1 will match both of these and the app server will get the WFE bits installed (assuming server names are used).

Interestingly, the fix is to just delete this line. The following lines, 6895 - 6904, achieve the same goal without this potential bug.
Comments: ** Comment from web user: EricNelson72 **

The issue remains on line 7371

Unfortunately removing this line does not solve the problem given line 7380:

```
if ($computerName -match $item) {return $true;}
```

This will continue to fail as long as one server name is a subset of the other.

↧

Commented Unassigned: Central admin database need upgrade [22445]

January 13, 2017, 1:40 pm
$
0
0
I have just built 3 SharePoint 2016 Farm with December 2016 CU. All the 3 Farms had their Central admin content database requiring upgrade.

I had to run:


(Get-SPWebApplication -IncludeCentralAdministration | ? {$_.DefaultServerComment -match "SharePoint Central Administration V4"}).contentdatabases | Upgrade-SPContentDatabase

in order to fix it.
Comments: ** Comment from web user: noral **

Hi Joseph,

I used AutoSPInstaller to create one environment, but I also created an environment without AutoSPInstaller. In *both* scenarios what you describe needed to be done, it is not an AutoSPInstaller issue.

Noral

↧
Search

Created Unassigned: Issue with SPTraceV4 and Managed Account automatic password changes [22453]

January 16, 2017, 9:52 pm
$
0
0
Brian,

Thank You for AutoSPInstaller - it makes deployment of SharePoint 2016 very simple.

There is an issue with how AutoSPInstaller is handling the SPTraceV4 service when provissioned. The ProcessIdentity for IsCredentialUpdateEnabled is set to False so once the password changes the service will not start, stating incorrect password. There seems to be an Event ID 5767, that happens once, in Event Viewer. Here is the event:
```
Level: Error
Source: SharePoint Foundation
Event ID: 5767
Task Category: Topology
General: Error updating the account password for process identity Id (GUID), please fix manually. The type initializer for 'System.Management.Automation.SessionStateScope' threw an exception.
```
I have run this PowerShell script to fix the issue in my environments.
```
Add-PSSnapin Microsoft.SharePoint.PowerShell

$SPService = "SPTraceV4"
$SPFarm = Get-SPFarm
$SPTimerv4 = $SPFarm.Services | Where {$_.Name -eq $SPService}
$SPTimerv4.ProcessIdentity.IsCredentialUpdateEnabled = $true
$SPTimerv4.ProcessIdentity.Update()
$SPTimerv4.ProcessIdentity
```
If the password is now generated from SharePoint the password in Services, for SPTraceV4, will get changed and the service will start normally.

Please contact me if you would like the MS case number.

Thank you,
Noral
↧

Commented Unassigned: Central admin database need upgrade [22445]

January 18, 2017, 4:14 pm
$
0
0
I have just built 3 SharePoint 2016 Farm with December 2016 CU. All the 3 Farms had their Central admin content database requiring upgrade.

I had to run:


(Get-SPWebApplication -IncludeCentralAdministration | ? {$_.DefaultServerComment -match "SharePoint Central Administration V4"}).contentdatabases | Upgrade-SPContentDatabase

in order to fix it.
Comments: ** Comment from web user: AshokGopalan **

Hello All:

I too noticed that on installing the RTM with Dec'16 CU. We do see the message "Database is in compatibility rage, upgrade is recommended."

Ashok

↧
↧

Created Unassigned: Distributed Cache service account (during setup) [22458]

January 18, 2017, 4:24 pm
$
0
0
Hi Brian,

Thank you for the incredible effort that you have put in to create this tool! It makes deployment such a piece of cake!!

Just realized that when the Distributed Cache service is being setup, the script is using the app pool account for the service; specifically it uses the ManagedAccount with CommonName="spservice".

I am referring to line# 1681 in the "AutoSPInstallerFunctions.ps1", function "UpdateProcessIdentity".
Specifically it is as shown below:
$managedAccountGen = Get-SPManagedAccount | Where-Object {$_.UserName -eq $($spservice.username)}

However the TechNet article (https://technet.microsoft.com/en-us/library/jj219613.aspx#changesvcacct) suggests that the "Farm Account" is used to setup the service.

Should this be changed to the default Farm Account?

Thank you
Ashok
↧

Commented Unassigned: Distributed Cache service account (during setup) [22458]

January 18, 2017, 4:56 pm
$
0
0
Hi Brian,

Thank you for the incredible effort that you have put in to create this tool! It makes deployment such a piece of cake!!

Just realized that when the Distributed Cache service is being setup, the script is using the app pool account for the service; specifically it uses the ManagedAccount with CommonName="spservice".

I am referring to line# 1681 in the "AutoSPInstallerFunctions.ps1", function "UpdateProcessIdentity".
Specifically it is as shown below:
$managedAccountGen = Get-SPManagedAccount | Where-Object {$_.UserName -eq $($spservice.username)}

However the TechNet article (https://technet.microsoft.com/en-us/library/jj219613.aspx#changesvcacct) suggests that the "Farm Account" is used to setup the service.

Should this be changed to the default Farm Account?

Thank you
Ashok
Comments: ** Comment from web user: AshokGopalan **

Hello again!

Thought of something additional as I was working through this in my mind.

Do you think it would be beneficial to have additional ManagedAccount elements defined with specific CommonName attributes like:
CommonName="SecureSote",
CommonName="DistCache"
etc..

and the same could be used in the corresponding service activation scripts? This will even take care of the MS security best practice recommendations of using least-privileged accounts for services.

I am thinking that this would be really useful for organizations that have the business need to implement least-privileged security model in their SharePoint environment.

Thank you
Ashok

↧

Commented Unassigned: Distributed Cache service account (during setup) [22458]

January 18, 2017, 6:28 pm
$
0
0
Hi Brian,

Thank you for the incredible effort that you have put in to create this tool! It makes deployment such a piece of cake!!

Just realized that when the Distributed Cache service is being setup, the script is using the app pool account for the service; specifically it uses the ManagedAccount with CommonName="spservice".

I am referring to line# 1681 in the "AutoSPInstallerFunctions.ps1", function "UpdateProcessIdentity".
Specifically it is as shown below:
$managedAccountGen = Get-SPManagedAccount | Where-Object {$_.UserName -eq $($spservice.username)}

However the TechNet article (https://technet.microsoft.com/en-us/library/jj219613.aspx#changesvcacct) suggests that the "Farm Account" is used to setup the service.

Should this be changed to the default Farm Account?

Thank you
Ashok
Comments: ** Comment from web user: brianlala **

No, that's the whole idea - SharePoint by default sets it to the Farm Account, but it's advised to change it to something else which Is exactly what AutoSPInstaller does. We use spservice to avoid a proliferation of accounts and because it's well-suited for this purpose. It would be overkill to use separate accounts for each and every service.

Brian

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