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

Commented Unassigned: Script halted on creating portal site collection [21890]

$
0
0
hi,


The script succesfully creates the webapplication but halts at the creation of the portal site collection.

Start of error: the server was unable to process the request due to an internal error.

Succesfully created:
IIS sites: Central Admin, Portal Home, Web services
SQL Content databases: Config, Central Admin and Portal

My environment:
Front/Backend: Server 2012 R2
SQL 2008 R2

Help would be very appreciated.


Greetings,
Pim
Comments: ** Comment from web user: brianlala **

Can you post the section of your XML that creates the Portal site collection? Alternately, you could validate your XML at https://autospinstaller.com for errors/issues.

I have also seen issues at this stage due to incorrectly or incompletely installed SP binaries or CUs.

Brian


New Post: New-SPConfigurationDatabase : Value cannot be null

$
0
0
No need to upload full XML, maybe just paste the section containing the <Farm>node. Note though that if the error still occurs outside of AutoSPInstaller, it might be a question best posed to another general SharePoint forum (e.g. MSDN, Stack Exchange, etc.)

Brian

New Post: June 1st. Release (RemoteInstall)

$
0
0
I couldn't find anything in your XML that would cause AutoSPInstaller to reject or not recognize the <RemoteInstall> element. Which server did you run this on BTW?

Also note that you do NOT need to create and specify a SQL alias (the same alias) for each web app and service app. You only need to specify <DBAlias Create="true"> within the Farm section, and every other web/service app will use it as default.

Brian

New Post: June 1st. Release (RemoteInstall)

$
0
0
Also, just remembering... since SharePoint 2013 requires a couple of reboots when installing prerequisites, if the server you are running the script on is a farm server, <RemoteInstall> will effectively be disabled - since after a reboot all the servers will be on their own resuming the script - and remote install wouldn't make much sense any more. So, each server will kick off the install "remotely" but after the first reboot they'll each be on their own. This is by design.

Brian

Edited Issue: Error when attaching existing content DB [21811]

$
0
0
The "create web application" function does the following steps:

- Check if Site Collection exists
- If it doesn't, create Content DB
- Create site collection

The problem is if I want to attach a content DB that already exists and contains site collections. When the content DB is attached, the site collection "springs into existence"

So the script checks for the site collection - it's not there. It creates (attaches) the content DB, which adds the site collection to the web app. Then when the script tries to create the site collection, it errors out (and fails)

You need to test for the existence of the site collection again *after* the database is attached. Alternatively, Fail gracefully, log the issue, and keep going.

Commented Unassigned: Assigning from services on server for streamlined SP2010 deployment [21765]

$
0
0
Hi, Great product thanks...Ran into a little issue. For now i will fix manually but you should prob know about it.

I have got 10 SP servers. 4 WFE, 2 x Batch, 2 x BI, 2 x Search
So trying to do a streamlined deployment with services like Access, Visio, MMS, Search Query, BDC on WFE
Search Index on own server
Batch servers have Timerjob, UPS...
BI Servers have Excel and BI items.

I have configured the script as above but after the script has completed it ignored some of the settings i have configured. So Access services will be running on a Search server and Timejob wil be running on WFE and quite a few more.

For now i am just changing them manually but this will probably be used quite a bit more on SharePoint 2013.
Comments: ** Comment from web user: brianlala **

Can you post sample sections of your XML? Or alternately, use https://autospinstaller.com to review it and ensure that you have indeed distributed the services as you intended. I haven't run into this problem myself.

Brian

Created Unassigned: Error in CheckConfigFiles [21911]

$
0
0
If you don't specify DataDir in the xml this function errors as it tries to remove the trailing '\' from a string that is null.
The line:
$dataDir = $dataDir.TrimEnd("\")
needs to be moved from before the line:
if ([string]::IsNullOrEmpty($dataDir)) {$dataDir = "%PROGRAMFILES%\Microsoft Office Servers\$env:spVer.0\Data"}
to after it.

New Post: A site collection could not be created as the provided managed path does not exist.

$
0
0
Hi,

We are currently facing an issue during the configuration of Portal Web application/Site Collection using the autospinstaller tool. Note that we are using the 3.99 XML version.

Exception: Microsoft.SharePoint.PowerShell.SPCmdletException: A site collection could not be created as the provided managed path does not exist. Change the URL to use an existing managed path or create the missing managed path prior to calling this command.

below is the associated portion of the XML file:

<WebApplications AddURLsToHOSTS="true">
<WebApplication Name="Portal">
        <Type>Portal</Type>
        <ApplicationPool>Portal</ApplicationPool>
        <Url>http://sp2013-auto</Url>
        <Port>80</Port>
        <UseHostHeader>false</UseHostHeader>
        <AddURLToLocalIntranetZone>true</AddURLToLocalIntranetZone>
        <GrantCurrentUserFullControl>true</GrantCurrentUserFullControl>
        <UseClaims>true</UseClaims>
        <UseBasicAuthentication>false</UseBasicAuthentication>
        <UseOnlineWebPartCatalog>false</UseOnlineWebPartCatalog>
        <Database>
            <Name>Content_Portal</Name>
            <DBServer></DBServer>
            <DBAlias Create="false">
                <DBInstance>SERVER\INSTANCE</DBInstance>
                <DBPort></DBPort>
            </DBAlias>
        </Database>
        <ManagedPaths>
            <ManagedPath explicit="false" relativeUrl="http://sp2013-auto/path/" />
        </ManagedPaths>
        <SiteCollections>
            <SiteCollection siteUrl="http://sp2013-auto/path/SiteCollectionAuto">
                <Name>Portal Home</Name>
                <Description>Portal Home Site</Description>
                <HostNamedSiteCollection>false</HostNamedSiteCollection>
                <Owner>ds\sharepoint.lab.admin</Owner>
                <CustomDatabase>Portal</CustomDatabase>
                <SearchUrl>http://SP2013Search</SearchUrl>
                <Template>SPSPORTAL#0</Template>
                <LCID>1033</LCID>
                <Locale>en-us</Locale>
                <Time24>false</Time24>
            </SiteCollection>
        </SiteCollections>
    </WebApplication>
</WebApplications>

Please note that we also tried <ManagedPath explicit="false" relativeUrl="http://sp2013-auto/path/" /> Hope you can help us.

New Post: A site collection could not be created as the provided managed path does not exist.

$
0
0
The managed path relativeurl is incorrect.
It should be:<ManagedPath explicit="false" relativeUrl="path" />


Cheers,
Ivan

Updated Wiki: FAQ

$
0
0

Frequently Asked Questions

  • Is there a friendlier way to edit the XML than good ol' Notepad/Visual Studio/etc.?
    • Yes - check out the new AutoSPInstaller Online. It includes real-time help/guidance, validation & smarts to avoid those "oops" moments during script run-time. We welcome your feedback!
  • Is this thing safe/ready/appropriate for Production?
    • It sure is! I've personally set up many live customer farms with AutoSPInstaller in the past few years. In fact it's even been used by organizations like CloudShare to create SharePoint VM templates. The standard caveats apply though: As the importance of your target farm increases, so should your level of knowledge about how to properly size, architect and build SharePoint. AutoSPInstaller does not mitigate this, it merely eases, standardizes and accelerates the process.
  • Does AutoSPInstaller support SharePoint Foundation?
    • Basically, no. Some folks have had success getting it to work by editing the script themselves (search thru the discussions to find examples) but as I (selfishly) have no need for SPF I have not spent any time researching this. If however someone puts forth a tried, tested & true patch that can (very) easily be integrated, I may consider including it.
  • Can I use AutoSPInstaller to install Office Web Apps 2013?
    • Office Web Apps 2013 (also known as WAC) is now a separate product which is not installed on the same server as SharePoint 2013. As it's technically-speaking no longer part of the SharePoint farm, and because of the complexity it would introduce, I've decided to leave Office Web Apps 2013 out of AutoSPInstaller for the time being.
  • What about the Request Management service (in SharePoint 2013)? Will it be included in AutoSPInstaller?
    • After a discussion with Spencer Harbar, it was agreed that it might be best to leave it out, as there can be some ramifications with provisioning it without full awareness of its intended use - e.g. by folks who want to blindly "turn everything on" in SharePoint 2013.
  • Where's all the #@)%#$ documentation??
  • My SharePoint server(s) and SQL instance are in different, untrusted domains. Can I use SQL authentication instead of Windows Integrated?
    • Although support for SQL auth in SharePoint (especially around things like the User Profile Service) has gotten better, AutoSPInstaller doesn't currently support connecting to your databases using anything other than Windows Integrated authentication. It certainly wouldn't be impossible to make the required modifications, but you'd have to do this yourself or reach out to the community for guidance.
  • I want to make a single/isolated configuration change to an existing SharePoint farm (e.g. provision a service application). Do I really need to re-run the whole script?
    • No - in fact you can usually just run individual functions to achieve what you're after by following the instructions here.

Updated Wiki: FAQ

$
0
0

Frequently Asked Questions

  • Is there a friendlier way to edit the XML than good ol' Notepad/Visual Studio/etc.?
    • Yes - check out the new AutoSPInstaller Online. It includes real-time help/guidance, validation & smarts to avoid those "oops" moments during script run-time. We welcome your feedback!
  • Is this thing safe/ready/appropriate for Production?
    • It sure is! I've personally set up many live customer farms with AutoSPInstaller in the past few years. In fact it's even been used by organizations like CloudShare to create SharePoint VM templates. The standard caveats apply though: As the importance of your target farm increases, so should your level of knowledge about how to properly size, architect and build SharePoint. AutoSPInstaller does not mitigate this, it merely eases, standardizes and accelerates the process.
  • Does AutoSPInstaller support SharePoint Foundation?
    • Basically, no. Some folks have had success getting it to work by editing the script themselves (search thru the discussions to find examples) but as I (selfishly) have no need for SPF I have not spent any time researching this. If however someone puts forth a tried, tested & true patch that can (very) easily be integrated, I may consider including it.
  • Can I use AutoSPInstaller to install Office Web Apps 2013?
    • Office Web Apps 2013 (also known as WAC) is now a separate product which is not installed on the same server as SharePoint 2013. As it's technically-speaking no longer part of the SharePoint farm, and because of the complexity it would introduce, I've decided to leave Office Web Apps 2013 out of AutoSPInstaller for the time being.
  • What about the Request Management service (in SharePoint 2013)? Will it be included in AutoSPInstaller?
    • After a discussion with Spencer Harbar, it was agreed that it might be best to leave it out, as there can be some ramifications with provisioning it without full awareness of its intended use - e.g. by folks who want to blindly "turn everything on" in SharePoint 2013.
  • Where's all the #@)%#$ documentation??
  • My SharePoint server(s) and SQL instance are in different, untrusted domains. Can I use SQL authentication instead of Windows Integrated?
    • Although support for SQL auth in SharePoint (especially around things like the User Profile Service) has gotten better, AutoSPInstaller doesn't currently support connecting to your databases using anything other than Windows Integrated authentication. It certainly wouldn't be impossible to make the required modifications, but you'd have to do this yourself or reach out to the community for guidance.
  • I want to make a single/isolated configuration change to an existing SharePoint farm (e.g. provision a service application). Do I really need to re-run the whole script?
    • No - in fact you can usually just run individual functions to achieve what you're after by following the instructions here.

New Post: Section of Code to remove DB Guids?

$
0
0
THanks Brian,

I thought that would be the case as well.
I keep getting stuck here when I run the installer
  • New-SPConfigurationDatabase -DatabaseName "$configDB" -DatabaseServe ...
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidData: (Microsoft.Share...urationDatabase:SPCmdletNewSPConfigurationDatabase) [New
      -SPConfigurationDatabase], Win32Exception
    • FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPConfigurationDatabase

  • Script halted!
  • Error creating new farm configuration database
    Press any key to exit...
Any ideas?

New Post: Section of Code to remove DB Guids?

$
0
0
The reason seems to be this.
Login failed for user 'Contoso\SP_Farm'. Reason: Failed to open the explicitly specified database 'SP2013_Config'. [CLIENT: 192.168.168.63]

Which would mean the autospinstaller is trying to access a db it hasnt created yet. Do I have to configuration wizard first?

Please excuse my ignorance, im no expert at SP2013 yet


Edit:
Modifying and running this script from Here
Add-PSSnapin Microsoft.SharePoint.PowerShell
$FarmCredential = Get-Credential -credential mikefrobbins\spExtranetFarm
$Passphrase = Read-Host -assecurestring "SP PassPhrase"
$DbName = "SP_Extranet_Config"
$DbServer = "sql01.mikefrobbins.com"
$AdminContentDb = "SP_Extranet_AdminContent"
New-SPConfigurationDatabase -DatabaseName $DbName -DatabaseServer $DbServer -AdministrationContentDatabaseName $AdminContentDb -FarmCredentials $FarmCredential -Passphrase $Passphrase
Install-SPHelpCollection -All
Initialize-SPResourceSecurity
Install-SPService
Install-SPFeature -AllExistingFeatures
New-SPCentralAdministration -Port 55000 -WindowsAuthProvider "NTLM"
Install-SPApplicationContent
``` and then returning to my custom autoSPinstall fixed made it all go smooth.

Thanks for your input Brian

New Post: Creating User Profile Service Application Error

$
0
0
Hi,

Any ideas why i'm getting this error?
I know it says password or username is incorrect but the farm account Im using up to that point that worked is the same and all service accounts were verified at the start of the install.
I even disabled UAC on the app server.

Any ideas?
Thanks.
  • My Site host already provisioned.
  • Creating User Profile Service Application...
    Start-Process : This command cannot be run due to the error: The user name or password is incorrect.
    At C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:3362 char:13
  • Start-Process -WorkingDirectory $PSHOME -FilePath "powershell.exe" - ...
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidOperation: (:) [Start-Process], InvalidOperationException
    • FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
Press any key to exit...
  • Waiting for User Profile Service Application................................................................
    ...................................................
    WARNING: Timed out waiting for service creation (maybe a UAC prompt?)

New Post: Can AutoSPInstaller be used to install "simple" Sharepoint 2010 Trial configuration?

$
0
0
Hi,

I am trying to standup just the simplest Sharepoint instances using Sharepoint 2010 Trial for a proof of concept. I need to standaup several instances so I'd like to do silent/unattended installations if possible. My impression is tht the Sharepoint 2010 Trial comes with SQL Server Express, and that it's possible to standup a small Sharepoint installation with just the SQL Server Express.

Is this something that AutoSPInstaller can do? Can anyone point me to maybe a howto for that?

Thanks,
Jim

New Post: Error just when autoSPinstaller is configuring Enterprise Search

$
0
0
  • Updating Microsoft SharePoint Foundation Tracing to run as CONTOSO\SP_Services...Done.

- Restarting service SPTraceV4...


  • Provisioning Enterprise Search...

- Configuring search service...Done.

  • Script halted!
Exception : System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to
                    parameter 'String' because it is an empty string.
                       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)
                       at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
                       at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
                       at System.Management.Automation.ScriptBlock.InvokeWithPipeImpl(ScriptBlockClauseToInvoke
                    clauseToInvoke, Boolean createLocalScope, Dictionary`2 functionsToDefine, List`1
                    variablesToDefine, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object
                    input, Object scriptThis, Pipe outputPipe, InvocationInfo invocationInfo, Object[] args)
                       at System.Management.Automation.ScriptBlock.<>c__DisplayClassa.<InvokeWithPipe>b__8()
                       at System.Management.Automation.Runspaces.RunspaceBase.RunActionIfNoRunningPipelinesWithThre
                    adCheck(Action action)
                       at System.Management.Automation.ScriptBlock.InvokeWithPipe(Boolean useLocalScope,
                    Dictionary`2 functionsToDefine, List`1 variablesToDefine, ErrorHandlingBehavior
                    errorHandlingBehavior, Object dollarUnder, Object input, Object scriptThis, Pipe outputPipe,
                    InvocationInfo invocationInfo, Object[] args)
                       at System.Management.Automation.ScriptBlock.InvokeUsingCmdlet(Cmdlet contextCmdlet, Boolean
                    useLocalScope, ErrorHandlingBehavior errorHandlingBehavior, Object dollarUnder, Object input,
                    Object scriptThis, Object[] args)
                       at Microsoft.PowerShell.Commands.ForEachObjectCommand.ProcessRecord()
                       at System.Management.Automation.CommandProcessor.ProcessRecord()
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 4489
                    at CreateEnterpriseSearchServiceApp, C:\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1: line
                    4478
                    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 :

| Automated SP2013 install script |
| Started on: 6/19/2015 4:07:30 PM |

| Aborted: 6/19/2015 4:16:34 PM |

PS C:\SP\AutoSPInstaller>

New Post: Error just when autoSPinstaller is configuring Enterprise Search

$
0
0
Nevermind, i forgot to put the Crawl Account Password is what that error was.

Thanks.

New Post: Creating User Profile Service Application Error

$
0
0
I just ended up not provisioning User Profile Service and thats how i got through that.
ALso, im going to be using FBA and not AD so it wasn't that important at this time

New Post: Can AutoSPInstaller be used to install "simple" Sharepoint 2010 Trial configuration?

$
0
0
If you mean, can you use AutoSPInstaller to spinoff a "standalone" instance of SharePoint. Then the answer is "No".

However, you could use AutoSPInstaller to build a single-server Farm.

Whether SharePoint 2010 is a trial or properly licensed, that does not make a difference to AutoSPInstaller as long as you have a PID Key.

New Post: Can AutoSPInstaller be used to install "simple" Sharepoint 2010 Trial configuration?

$
0
0
Correct, AutoSPInstaller doesn't support any installations that require SQL Express. It assumes SQL server is already installed somewhere and the instance name/address is merely referred to in the input XML.

Brian
Viewing all 2279 articles
Browse latest View live


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