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

New Post: Failure during rerun due to site collections already existing


Commented Issue: Script Aborted during the creation of mysite site collection [18263]

$
0
0
Right after the script grants my service account rights to my MySite Host...
The script then trys to create Site Collection "https://mysite.here.com and then aborts.
The exception that follows says:
Exception : Microsoft.SharePoint.PowerShell.SPCmdletPipeBindExcepti
on: Cannot find an SPWebApplication object that contain
s the following Name, Id, or Url: https://mysite.here.com
at Microsoft.SharePoint.PowerShell.SPWebApplicationP
ipeBind.Read(Boolean exactUrl)
at Microsoft.SharePoint.PowerShell.SPCmdletNewSite.I
nternalValidate()
at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessR
ecord()
TargetObject : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
CategoryInfo : InvalidData: (Microsoft.Share...SPCmdletNewSite:SPCmdle
tNewSite) [New-SPSite], SPCmdletPipeBindException
FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
PipelineIterationInfo : {0, 1}
PSMessageDetails :
Comments: ** Comment from web user: gkayton1 **

I have this same error but don't see the issue. Please help.
Guy

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

$
0
0
I just tried for a week to install Foundation 2013 - with disastrous results.
I'll post the changes to the files later.
Shortly, what I found was that not all Services would be installed, and would vary between runs.
The port of the CA is not set correctly from the config files.
The script looks for a key even with Foundation, so that has to be changed in the script as well.
I later gave up - ran it to where I had most of the stuff installed, and just worked from there.
Probably because of the lower incidence of Foundation users?

Commented Unassigned: dotNetFX4.5 "missing" [22100]

$
0
0
Before first use of AutoSPInstaller 3.99.51 the host (Windows Server 2012 R2 Standard) had all recent dotNet versions installed, including NDP46-KB3045557-x86-x64-AllOS-ENU.exe which 'upgrades' dotNet Framework 4.5 ("dotNetFX45") to 4.6

AutoSPInstaller then stops part way through installation saying that dotNetFX45 is not installed. any attempt to re-install dotNetFX45 then confirms that it is already installed. Further installation of AutoSPInstaller cannot continue.
Comments: ** Comment from web user: philoj **

For anyone who runs into this, the problem is that the SharePoint 2013 installer doesn't recognize .Net Framework 4.6 (or later) - so if you've installed the 4.6 framework, you can't move forward.

You *can* uninstall the .Net Fx 4.6. The problem here is that every time MSFT updates the damn thing, they change the KB number, and there's no easy way to find the new one. Currently the latest update that does it is KB3102467 - uninstall that from Add/Remove programs and SharePoint 2013 will install easily.

However, if they update the 4.6 framework again, you'll have to go hunting through your installed updates to find it. Obviously the number will be after 3102467.

I used this PowerShell to dump a list of installed updates to a CSV file:

```
$Session = New-Object -ComObject "Microsoft.Update.Session"
$Searcher = $Session.CreateUpdateSearcher()

$historyCount = $Searcher.GetTotalHistoryCount()

$Searcher.QueryHistory(0, $historyCount) | Select-Object Title, Description, Date,

@{name="Operation"; expression={switch($_.operation){

1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"}

}}} | Export-Csv -NoType -Path c:\temp\Updates.csv

```

Then I opened the CSV in Excel, highlighted the column with the KB numbers, and did a find & replace - replace "KB" with "https://support.microsoft.com/en-us/kb/" and you've got a list of URLs that will open the page for the KB article. Then open each page until you find a .Net Framework 4.6 installer.

(This was because as of January 2016 there's no web service to resolve a KB number to an article description, and you can't scrape pages because they're dynamic - a javascript framework that fills the content after it loads. What I think of the TechNet team right now isn't suitable for mixed company)

That was the quickest way I could find. If you can do better, please leave a note here for posterity.

Reviewed: AutoSPInstaller for SharePoint 201x (Jan 27, 2016)

$
0
0
Rated 5 Stars (out of 5) - The best and I mean it "THE BEST" SP installation tool ever created. When installing new farm almost every week, it's essential tool for SP administrators.

Reviewed: AutoSPInstaller for SharePoint 201x (Jan 27, 2016)

$
0
0
Rated 5 Stars (out of 5) - It is the best and I mean it is "THE BEST" SP installation tool ever created. When installing new farm almost every week, it's essential tool for SP administrators.

Commented Unassigned: Error during "Installing Features" [22126]

$
0
0
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: CraigHumphrey **

Hey Guys,

I'm seeing this too, only on the first run (if I have to re-run) AutoSPInstaller.

If I use AutoSPInstaller, I find that I can't use PSConfigUI.exe any more, it gets an access denied on a SharePoint folder (sorry, didn't take down the details, will grab it next time).

Thanks
Craig

Commented Unassigned: Error: Custom file location is not accessible [22112]

$
0
0
I've downloaded the latest version of AutoSPInstaller 3.99.51. I've made a new .xml file for the Beta2 SP2016 SharePoint version. When I start the installation, when the script tries to install the Prerequisites, it breaks with the following message: Error: Custom File Location is not accessible.

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:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line
875
at Run-Install, C:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 184
at <ScriptBlock>, C:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 379
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

See the attachment for a picture of the error

I'm not able to install SharePoint 2016 Beta2 with the scripts.

**Update 12 december**
There is a workaround. When you install the SP2016 bits through the setup.exe and then finish (not doing the configuration wizard setup), After this, when you try again to run autospinstaller, the installation will complete. However, there are some issues installing SP2016 with autospinstaller.
When selecting SP2016, some options in the 'services' part will disappear. But in the .xml they will exist. When you install a singleserverfarm Role, the installation will complete, but in the end the installation will stop the Microsoft Web application timer service thus deleting all your IIS websites except for the Central administration. The default settings are:
<IncomingEmail Start="false" />
<DistributedCache Start="false" />
<WorkflowTimer Start="false" />
<FoundationWebApplication Start="false" />

You must manually set these options to 'true' for FoundationWebApplication and DistributedCache if you choose the SingleServerFarm role.
Another option is afterwards to run some scripts like
$svc = Get-SPServiceInstance | where {$_.TypeName -like "*Foundation Web*"}
$svc.Status = "Online"
$svc.Update()

and

$wa = Get-SPWebApplication http://webappurl
$wa.ProvisionGlobally()
Comments: ** Comment from web user: CraigHumphrey **


With the pre-reqs failing, I found that by using brian's [AutoSPSourceBuilder](https://autospsourcebuilder.codeplex.com/) I was able to pre-download the correct set of pre-reqs, which were different from some other blog post I was working from.

Good spotting on the Web Apps, I'd already spotted the Distributed Cache issue, but not the FoundationWebApplication.


Commented Unassigned: Error during "Installing Features" [22126]

$
0
0
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: CatoAntonsen **


I ended up doing a restart of the computer between installation of binaries and configuration of the farm and then re-launching ASPI after an automatical logon. This solved the problem for me.

Added this in AutoSPInstallerFunctionsCustom.ps1:

```
Function RestartAfterBinaryInstallation([xml]$xmlinput) {
$restartedAfterBinaryInstallation = (Get-ItemProperty "HKLM:\SOFTWARE\AutoSPInstaller").RestartedAfterBinaryInstallation -eq "1"

if ($RestartedAfterBinaryInstallation -eq $false) {

New-ItemProperty -Path "HKLM:\SOFTWARE\AutoSPInstaller" -Name "RestartedAfterBinaryInstallation" -Value 1 -PropertyType "String" -Force | Out-Null

New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "AutoAdminLogon" -Value 1 -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "DefaultDomainName" -Value $env:USERDOMAIN -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "DefaultUserName" -Value $env:USERNAME -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "DefaultPassword" -Value $password -PropertyType "String" -Force | Out-Null
New-ItemProperty -Path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion\WinLogon" -Name "AutoLogonCount" -Value 1 -PropertyType "Dword" -Force | Out-Null

Set-UserAccountControl 0

New-Item -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\" -Name RunOnce -ErrorAction SilentlyContinue | Out-Null
New-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\RunOnce" -Name AutoSPInstaller -Value "`"$env:dp0\AutoSPInstallerLaunch.bat`" `"$inputFile`"" -Force | Out-Null

Restart-Computer -ErrorAction SilentlyContinue
if (!$?)
{
Write-Warning "Restart failed; there may be (an) other user(s) logged in!"
$forceRestart = Read-Host -Prompt " - Do you want to force a restart? (y/n)"
if ($forceRestart -eq "y") {Restart-Computer -Force}
}
}

}

```

In AutoSPInstallerMain:.ps1

```
Function Setup-Farm
{
__ <...>
ConfigureLanguagePacks $xmlinput
__ RestartBinariesAfterInstallation $xmlinput # <--- ADDED
__ AddManagedAccounts $xmlinput
}
```
Notice, this doesn't handle installation on multiple servers. Maybe it works, maytbe not...

Brian, could you give us a complete AutoSPInstallerInput.xml-file that you know will work? I've tried the one made by autospinstaller.com with no success.


A little background: I've made a set of scripts for my company that creates a complete SharePoint developer environment (in Hyper-V) based on a settings.xml-file, all the way from creating an unattended installation of Windows Server, installation of AD, SQL and SharePoint and then all required dev-software (including Visual Studio). All this is done in a couple of hours with no user interventions needed since restarts and automatically logons are handled by the script(s). Having to manually restart AutoSPInstaller ruined that experience...

Commented Unassigned: install SharePoint2016 beta2 [22123]

$
0
0
hello

in SP\AutoSPInstaller\AutoSPInstallerMain.ps1

BUG in string line from 242 to 251

if ($env:spVer -ge "15") # These are for SP2013+ only
{
CreateAppManagementServiceApp $xmlinput
CreateSubscriptionSettingsServiceApp $xmlinput
CreateWorkManagementServiceApp $xmlinput
CreateMachineTranslationServiceApp $xmlinput
CreateAccessServicesApp $xmlinput
CreatePowerPointConversionServiceApp $xmlinput
ConfigureDistributedCacheService $xmlinput
}


this code run only SP 2013 but not run in 2016!
Comments: ** Comment from web user: brianlala **

"-ge" means "Greater than or equal to". 16 is greater than 15, so the code will and does run.

Brian

Closed Unassigned: install SharePoint2016 beta2 [22123]

$
0
0
hello

in SP\AutoSPInstaller\AutoSPInstallerMain.ps1

BUG in string line from 242 to 251

if ($env:spVer -ge "15") # These are for SP2013+ only
{
CreateAppManagementServiceApp $xmlinput
CreateSubscriptionSettingsServiceApp $xmlinput
CreateWorkManagementServiceApp $xmlinput
CreateMachineTranslationServiceApp $xmlinput
CreateAccessServicesApp $xmlinput
CreatePowerPointConversionServiceApp $xmlinput
ConfigureDistributedCacheService $xmlinput
}


this code run only SP 2013 but not run in 2016!

Commented Unassigned: The tool was unable to install Application Server Role, Web Server (IIS) Role [22115]

$
0
0
Solution:

On a clean install of Windows 2012 R2

https://social.technet.microsoft.com/Forums/office/en-US/37cc20db-6cc7-45e0-928c-9a1ddbdab2ae/the-tool-was-unable-to-install-application-server-role-web-server-iis-role?forum=sharepointadmin

I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe"
Comments: ** Comment from web user: brianlala **

What's the net result of your investigations? I haven't run into this myself, so not sure what to "fix" yet. Is it still happening for you with the Release Candidate?

Brian

Closed Unassigned: 2012 Vs 2012 R2 : .net 3.5 install SXS Folder choice [22116]

$
0
0
I'm testing the install on both 2012 server and 2012 R2 (both RTM) and I couldn't install .net 3.5 without giving the installer two separate sxs folder based on server version. I added a folder sxs\2k12 and sxs\2K12R2 in the prerequisites folder and added code to check for version and use the appropriate folder in the .net install function.

Commented Unassigned: Secure store service have incorrect codes [21964]

$
0
0
When I was looking into the code for the secure store setup I came across some items which I think is incorrectly done.

First I notice that the password is not of secure string is that right?
```
# Set the field values
$secureUserName = ConvertTo-SecureString $unattendedAccount.UserName -AsPlainText -Force
$securePassword = $unattendedAccount.Password
$credentialValues = $secureUserName, $securePassword
```

2. The password field mask is set to false instead of true
```
# Set the account fields
$usernameField = New-SPSecureStoreApplicationField -Name "User Name" -Type WindowsUserName -Masked:$false
$passwordField = New-SPSecureStoreApplicationField -Name "Password" -Type WindowsPassword -Masked:$false
$fields = $usernameField, $passwordField
```
Hope you can fix it for the next version .

Cheers
Nicholas Ang
Comments: ** Comment from web user: brianlala **

I'm not sure that the password is ever displayed or saved anywhere (except of course the XML). So, closing this issue unless you feel there is a real and demonstrable security vulnerability.

Thanks,
Brian

Closed Unassigned: Secure store service have incorrect codes [21964]

$
0
0
When I was looking into the code for the secure store setup I came across some items which I think is incorrectly done.

First I notice that the password is not of secure string is that right?
```
# Set the field values
$secureUserName = ConvertTo-SecureString $unattendedAccount.UserName -AsPlainText -Force
$securePassword = $unattendedAccount.Password
$credentialValues = $secureUserName, $securePassword
```

2. The password field mask is set to false instead of true
```
# Set the account fields
$usernameField = New-SPSecureStoreApplicationField -Name "User Name" -Type WindowsUserName -Masked:$false
$passwordField = New-SPSecureStoreApplicationField -Name "Password" -Type WindowsPassword -Masked:$false
$fields = $usernameField, $passwordField
```
Hope you can fix it for the next version .

Cheers
Nicholas Ang

Commented Unassigned: Bug when creating DB Alias [21948]

$
0
0
When doing a two machine install (one sql server, one sharepoint everything) and the following names are chosen:

sql: sp2013sql
sharepoint: sp2013

The DB alias is not created correctly. In the above scenario, the protocol "sm" is used instead of "tcp/ip".
Comments: ** Comment from web user: brianlala **

The reason for this is your naming convention. One server name is a sub-string of the other. Try giving your servers names such as SP2013-SQL and SP2013-SP01.

HTH,
Brian

Commented Unassigned: The tool was unable to install Application Server Role, Web Server (IIS) Role [22115]

$
0
0
Solution:

On a clean install of Windows 2012 R2

https://social.technet.microsoft.com/Forums/office/en-US/37cc20db-6cc7-45e0-928c-9a1ddbdab2ae/the-tool-was-unable-to-install-application-server-role-web-server-iis-role?forum=sharepointadmin

I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe"
Comments: ** Comment from web user: SpRambler **

the fix I posted is ok. This is for SharePoint 2013 and not 2016. RTM version only.

Commented Unassigned: The tool was unable to install Application Server Role, Web Server (IIS) Role [22115]

$
0
0
Solution:

On a clean install of Windows 2012 R2

https://social.technet.microsoft.com/Forums/office/en-US/37cc20db-6cc7-45e0-928c-9a1ddbdab2ae/the-tool-was-unable-to-install-application-server-role-web-server-iis-role?forum=sharepointadmin

I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe"
Comments: ** Comment from web user: SpRambler **

the fix is:

add the function installIISRolePreSP1 to cutomfunctions
call the function in the beginning of pre-sp1 prerequisistes (windows 2012 R2) install
add the servermanager process gracefull kill in the pre-sp1 prereq install like I mention in the previous post.
Let me know if you need more info.
the Disable-ServerManagerlaunchOnLogon function is optional.

Commented Unassigned: The tool was unable to install Application Server Role, Web Server (IIS) Role [22115]

$
0
0
Solution:

On a clean install of Windows 2012 R2

https://social.technet.microsoft.com/Forums/office/en-US/37cc20db-6cc7-45e0-928c-9a1ddbdab2ae/the-tool-was-unable-to-install-application-server-role-web-server-iis-role?forum=sharepointadmin

I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe"
Comments: ** Comment from web user: brianlala **

OK, I'm going to leave this as something affected users can implement themselves - as ostensibly the more permanent fix is to just go with 2013 SP1. Let me know if I've misinterpreted things though.

Brian

Commented Unassigned: The tool was unable to install Application Server Role, Web Server (IIS) Role [22115]

$
0
0
Solution:

On a clean install of Windows 2012 R2

https://social.technet.microsoft.com/Forums/office/en-US/37cc20db-6cc7-45e0-928c-9a1ddbdab2ae/the-tool-was-unable-to-install-application-server-role-web-server-iis-role?forum=sharepointadmin

I copied and then renamed, this also fixed my issue. "rename the file C:\windows\System32\ServerManager.exe with ServerManagerCMD.exe"
Comments: ** Comment from web user: SpRambler **

It's ok with me. It can be a problem though for those trying to install RTM first and SP1 in the same process. In this case it just does not work. I have an RTM iso and I add SP1 in the updates to install.
for those with a slipstreamed sp1 re-release iso this is not a problem.

Viewing all 2279 articles
Browse latest View live


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