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

Created Unassigned: Search Service failure [21732]

$
0
0
I'm stuck at this error in the scripted install. It appears that it is trying to attach my password to the SP_SearchService account. I think I have it configured correctly in managed accounts and I have verified the account and password. Suggestions?


TargetObject :
CategoryInfo : InvalidData: (:) [ForEach-Object], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.ForEachObje
ctCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at <ScriptBlock>, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 4483
at CreateEnterpriseSearchServiceApp, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line
4472
at Setup-Services, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 227
at <ScriptBlock>, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 409
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :

New Post: Error in granting rights to Profile and Social database (User Profile Service Application)

New Post: Error in granting rights to Profile and Social database (User Profile Service Application)

$
0
0
So what are the implications of this going forward without taking any action? What impact can we expect if the Portal account does not have Shell Admin role on the Social and Profile Databases?

Thanks

Created Unassigned: CustomTemplate in SiteCollection Node [21735]

$
0
0
Hi Brian,

The CustomTemplate Field in the SiteCollection Node is not used in thode code. This can be removed from the example xml.


Ivan

New Post: Script continuously fails when creating config DB

$
0
0
My issue was on a clean single server install. SQL was 2008 R2 but not SP3 (only non-SP1 for the media). Ran PSConfig and it said SQL was not a compatible version. Connected to SSMS and looked at my SQL version number, sure enough, R2 RTM version. Upgrading to SP3 for SQL 2008 R2. Should fix the prob. Microsoft® SQL Server® 2008 R2 Service Pack 3 from http://www.microsoft.com/en-us/download/details.aspx?id=44271

OS: Windows Server 2008 R2 with latest updates
SQL: RTM SQL 2008 R2 (Needed SP3)
SP: 2013 Enterprise
Topology: Single server dev box using least privileges

New Post: Script continuously fails when creating config DB

$
0
0
Issue turned out to be the config. 1. I didn't have localhost, <DBServer>localhost</DBServer>
  1. DB alias was set to true, but not configured. <DBAlias Create="false"
I turned off the alias and removed any junk in SQL Config manager for 64-bit aliases.
<Database>
            <!-- If you are creating an alias (recommended!), <DBServer> is actually the value of the SQL alias; otherwise it's the NetBIOS name of the SQL server or instance. 
                 If you leave <DBServer> blank or specify localhost, script will assume the local server for SQL databases -->
            <DBServer>LOCALHOST</DBServer>
            <!-- The script can create a SQL alias for you. Enter the DBInstance, and if you leave <DBPort> blank, script will assume default port value of 1433 -->
            <DBAlias Create="FALSE"
                     DBInstance=""
                     DBPort="" />
            <!-- The DBPrefix is prepended to all database names. e.g. If you set this to TEST, your config DB will be TEST_ConfigDB.
                 If you set the prefix to localhost, script will prepend each database with the name of the server on which the script is run. 
                 Leave this blank for no prefix.
                 NOTE: If you are installing a multi-server farm, it is recommended that you do not use localhost as services provisioned on different servers
                       will have different prefixes.
            -->
            <DBPrefix>SP2013</DBPrefix>
            <!-- The name of the farm configuration database -->
            <ConfigDB>Config</ConfigDB>
        </Database>

New Post: Cannot Locate SP Binaries - Cannot determine version of SharePoint setup binaries, and no Version was specific in xml

$
0
0
Hi Everyone

I am running Windows Server 2012 R2 and am trying to configure four SP servers.

When I run AutoSPInstallerLaunch.bat - I get the error:

WARNING: Cannot locate SharePoint binaries; please check the at the files are in the \SharePoint subfolder as per new folder structure. Enter 'y' to proceed if you know that SharePoint is already installed...

After pressing Y I get:
Cannot determine version of SharePoint setup binaries, and no version was specified in XXX.xml

~ The files are definitely in that location
~ the version is specified in line 28 of the .xml file as
<Install SPVersion="2013">
I should mention that I couldn't figure out this issue so I manually installed the SP and up to Sep 14 CU on all 4 servers but am still getting the same message.

Note: I know that this thread has already been posted here but that did not answer my issue.

Help!
Thank you

Commented Issue: Account invalid (SuperReader, SuperUser) [20601]

$
0
0
If the SuperReader and SuperUser Account exist in another domain, these accounts are marked as invalid. The problem is caused by the method:

function userExists ([string]$name)

In my view this function should use a domain parameter to work properly.
Comments: ** Comment from web user: SqueakyMetal **

I was able to replicate this on Win Server 2012 R2.

I did find that in my case, the Pre-Windows2000 Logon Name (i.e. 20 characters) account worked for the Super Reader account, while the normal account name was just fine as a Managed Account


New Post: Cannot Locate SP Binaries - Cannot determine version of SharePoint setup binaries, and no Version was specific in xml

$
0
0
Did you copy the SharePoint binaries in SP\2013 from the ISO or just placed the ISO in that location or something else? It should be the first option.

Commented Issue: Trying to connect to "SQL"... - Fail [19412]

$
0
0
I am running into an issue with an installation on a new VM instance and VM database. When I ran the script for the first time it fails when trying to connect to the Dev (Connection Error. Check server name, port, firewall) and the second time the connection fails but different message (Exception calling “Open” with “0” argument(s): “Cannot generate SSPI context.”) . The error details are not pinpointing much or very detail so I was hoping someone has encounter the same issue and have a solution.

Both servers are in the same domain. I checked the SQL server and insured that all the accounts have access to the SQL Instance; Farm Account and Setup Account have sysadmin rights. The port 1433 is open on SQL's firewall. There is connectivity between the servers.

First Time I ran the script…
- Testing access to SQL server/instance/alias: Dev01
- Trying to connect to "Dev01"... - Fail
--------------------------------------------------------------
- Script halted!
- Connection Error. Check server name, port, firewall.
Press any key to exit...

Second Time I ran the script…
- Creating SQL alias “Dev01,1433”...
-Testing access to SQL server/instance/alias: Dev01
- Trying to connect to “Dev01”… - Fail
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Script halted!
- Exception calling “Open” with “0” argument(s): “Cannot generate SSPI context.”
Press any key to exit…
Comments: ** Comment from web user: DanKline **

For me, I manually created the alias in SSMS and unchecked create alias. It worked perfectly.

New Post: Cannot Locate SP Binaries - Cannot determine version of SharePoint setup binaries, and no Version was specific in xml

$
0
0
I mounted the ISO and copied the files to C:\AutoSPInstaller\2013\SharePoint. When I launch the .bat file in powershell I am changing the drive to \SERVERNAME\C$\AutoSPInstaller\2013\SharePoint (as it is for multiple servers).

New Post: Cannot Locate SP Binaries - Cannot determine version of SharePoint setup binaries, and no Version was specific in xml

$
0
0
And where do you have your XML, .bat and PS1 files?

New Post: Remote Install on Windows 2012 R2

$
0
0
I am trying to install SharePoint 2013 SP1 on Windows 2012R2 machines (2 WFE and 1 App). I start the install process from network location on the App server. But for some reason, I am unable to get AutoSP installer to install on binaries and configure WFEs (without manual intervention).
Both Remote Install and Parallel Install are set to True. All the Machines in the farm have access to Network location. Installer works perfectly when I try to manually run the installer on each machine. I thought Parallel install will install binaries on each machine simultaneously and configure.
Anybody help me on what I may be missing?

New Post: Remote Install on Windows 2012 R2

$
0
0
The problem is in MatchComputerName function. That function return null even though the $computerList argument has multiple computer names.
The reason is the if statement compares the computername (which is current server name) to the computer list with wild card on both ends. It will always return true when you are running from a server that is part of the SharePoint farm.
Commenting out that line in my case would correctly recognize multiple servers. Now it fails stating that WinRM client fails due to the authentication Mechanism requested.

Does AutoSPInstaller Support Win2012R2 at all or not?

New Post: WSMANCredSSP

$
0
0
I am guessing you are using Windows 2012 R2. I set some settings as well through GPO as well. I am facing the same situation as you are. I guess I have to manually run setup on each of the server.

New Post: Cannot Locate SP Binaries - Cannot determine version of SharePoint setup binaries, and no Version was specific in xml

$
0
0
My file structure is as follows:

C:\AutoSPInstaller\2010
C:\AutoSPInstaller\2013
C:\AutoSPInstaller\AutoSPInstaller

The files you ask about are:
C:\AutoSPInstaller\AutoSPInstaller\AutoSPInstallerConfigureRemoteTarget.ps1
C:\AutoSPInstaller\AutoSPInstaller\AutoSPInstallerFolderStructure.txt
C:\AutoSPInstaller\AutoSPInstaller\AutoSPInstallerFunctions.ps1
C:\AutoSPInstaller\AutoSPInstaller\AutoSPInstallerFunctionsCustom.ps1
C:\AutoSPInstaller\AutoSPInstaller\AutoSPInstallerInput-SERVERNAME.xml
C:\AutoSPInstaller\AutoSPInstaller\AutoSPInstallerLaunch.bat
C:\AutoSPInstaller\AutoSPInstaller\AutoSPInstallerMain.ps1

New Post: Cannot Locate SP Binaries - Cannot determine version of SharePoint setup binaries, and no Version was specific in xml

$
0
0
That should have worked but only from a server with the NETBIOSNAME = SERVERNAME . It does not matter where the files are located, but they have to be run from SERVERNAME.

So, are you running it from a Server with NETBIOSNAME = SERVERNAME? Are you using PSRemoting?

New Post: Cannot Locate SP Binaries - Cannot determine version of SharePoint setup binaries, and no Version was specific in xml

$
0
0
I am not using PSRemoting, I confirm I am running it from the same server that is on the xml file (I checked with $env:COMPUTERNAME = SERVERNAME).

Created Unassigned: List of available Site Collection Templates [21743]

$
0
0
The list of available Site Collection Templates for creating SharePoint 2013 is not comprehensive and is missing numerous Site Collection Template IDs.

The full list of Site Collection Templates and their respective IDs can be found here: [TEXT](http://www.funwithsharepoint.com/sharepoint-2013-site-templates-codes-for-powershell/)

It would be much nicer if AutoSPInstaller included all of the available Template IDs for configuring SharePoint 2013 Site Collections, thus making the overall AutoSPInstaller experience that much better.

Created Unassigned: Get-SPSite : The server was unable to process the request due to an internal error. [21745]

$
0
0
I've just built a 3 tier farm using AutpSPInstaller (Release )

All of the servers were provisioned succesfully apart from the second web server where I received the following error during the 'Checking for portal site collection phase':

```
Get-SPSite : The server was unable to process the request due to an internal error. For more information about the
error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
configuration behavior) on the server in order to send the exception information back to the client, or turn on
tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.
At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2696 char:36
+ $getSPSiteCollection = Get-SPSite -Limit ALL | Where-Object {$_.Url ...
+ ~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...SPCmdletGetSite:SPCmdletGetSite) [Get-SPSite], FaultExce
ption
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGetSite

- Creating Site Collection "http://portal-dev"...
--------------------------------------------------------------
- Script halted!


Exception : System.ServiceModel.FaultException: The server was unable to process the request due to an
internal error. For more information about the error, either turn on
IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the
<serviceDebug> configuration behavior) on the server in order to send the exception
information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK
documentation and inspect the server trace logs.
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst,
RequestSecurityTokenResponse& rstr)
at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)
at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean
bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo,
SPRequestSecurityTokenProperties properties)
at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForLegacyLoginContext(Uri context)
at Microsoft.SharePoint.SPSite.InitUserToken(SPRequest request)
at Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm farm, Guid applicationId, Guid
contentDatabaseId, Guid siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri requestUri,
String serverRelativeUrl, Boolean hostHeaderIsSiteName, SPUserToken userToken, Boolean
appWebRequest, String appHostHeaderRedirectDomain, String appSiteDomainPrefix, String
subscriptionName, String appSiteDomainId, Uri primaryUri)
at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite,
Boolean swapSchemeForPathBasedSites, SPUserToken userToken)
at Microsoft.SharePoint.Administration.SPSiteCollection.get_Item(String strSiteName)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.CreateSite(SPWebApplication
application, SPContentDatabase database, String originalPath, Guid id, Guid
siteSubscriptionId, Boolean useHostHeaderAsSiteName, Boolean bDeleted, DateTime deletionTime,
String subscriptionName, String appSiteDomainId, List`1 siteUrls, Boolean bResyncMode)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.CreateSite(SPWebApplication
application, SPContentDatabase database, String path, Boolean useHostHeaderAsSiteName)
at Microsoft.SharePoint.Administration.SPSiteCollection.Add(SPContentDatabase database,
SPSiteSubscription siteSubscription, String siteUrl, String title, String description, UInt32
nLCID, Int32 compatibilityLevel, String webTemplate, String ownerLogin, String ownerName,
String ownerEmail, String secondaryContactLogin, String secondaryContactName, String
secondaryContactEmail, String quotaTemplate, String sscRootWebUrl, Boolean
useHostHeaderAsSiteName, Boolean overrideCompatibilityRestriction)
at Microsoft.SharePoint.PowerShell.SPCmdletNewSite.CreateDataObject()
at Microsoft.SharePoint.PowerShell.SPNewCmdletBase`1.InternalProcessRecord()
at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()
TargetObject : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
CategoryInfo : InvalidData: (Microsoft.Share...SPCmdletNewSite:SPCmdletNewSite) [New-SPSite], FaultException
FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSite
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at CreateWebApp, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2715
at CreateWebApplications, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line 2506
at Setup-Farm, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 209
at <ScriptBlock>, C:\SP\AutoSPInstaller\AutoSPInstallerMain.ps1: line 408
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}
PSMessageDetails :
```

I also see the above error in the Application Event Log categorized as a 'Claims Authentication' issue.
I've also seen Event log errors about the Security Token Service.

The STS App Pool is running as the correct account (and has been restarted).
Browsing to the STS web service gave me a message about enabling Metadata publishing for this service which I did by editing the web.config and setting both httpGetEnabled and httpsGetEnabled as 'true.'
Once I did this it just states that the service has been created.

When trying to load the portal site I just receive an internal server errror with a correlation ID although it doesn't appear that the trace logging is working on this particular server as the logs are 0 KB, presumably the root cause it causing logging to fail as well.

I've tried uninstalling SP and trying to reinstall although I receive the same error.

I'd appreciate any help as I would very much prefer not to have this server rebuilt.

Kind regards,
David
Viewing all 2279 articles
Browse latest View live


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