Comments (3)

  1. sanlaan says:

    Hey guys starting to step through this, but noticed that on the Pre-requisite steps 1 and 2:

    Use the SQL Membership / role provider (which is installed by IIS, click here for more info)

    Use the LDAP Membership provider (which is part of the SharePoint 2010 Beta Server product, click here for more info)

    The click here for more info aren’t hyperlinks.

    Thanks for all of the info!

  2. sanlaan says:

    Hey guys

    The script keeps giving me this error:

       + CategoryInfo          : InvalidData: (Microsoft.Share…PWebApplication:

      SPCmdletNewSPWebApplication) [New-SPWebApplication], PipelineStoppedExcept

     ion

       + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWeb

      Application

    New-SPWebApplication : ApplicationPoolAccount is not found.

    Even though the account it tries to use (the default of the account I’m signed in with) is a valid domain account with full rights to the server, the domain, and the sharepoint installation. I even tried creating a dummy application pool account named exactly what it was trying to create (FBAldap-Claims-15000) with the application pool account in question, but still no luck.

    Guess I’ll go the manual route for now.

    Full error (from a try where I went with all defaults, but with same results) posted below:

    PS C:Usersadministrator.SHAREPOINTscripts> .claimswa.ps1 FBA

    PORT not specified; defaulting to 201

    OWNER not specified; defaulting to SHAREPOINTadministrator

    Detected SHIP flavor of MOSS installed on this farm!

    Creating FBAldap-Claims-201 web app on port 201

    New-SPWebApplication : The pipeline has been stopped.

    At line:1 char:21

    + New-SPWebApplication <<<<  -Name FBAldap-Claims-201 -ApplicationPool FBAldap-

    Claims-201 -ApplicationPoolAccount SHAREPOINTadministrator -Url http://FL192DE

    V01 -Port 201 -AuthenticationProvider $ap | Out-Null

       + CategoryInfo          : InvalidData: (Microsoft.Share…PWebApplication:

      SPCmdletNewSPWebApplication) [New-SPWebApplication], PipelineStoppedExcept

     ion

       + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWeb

      Application

    New-SPWebApplication : ApplicationPoolAccount is not found.

    At line:1 char:21

    + New-SPWebApplication <<<<  -Name FBAldap-Claims-201 -ApplicationPool FBAldap-

    Claims-201 -ApplicationPoolAccount SHAREPOINTadministrator -Url http://FL192DE

    V01 -Port 201 -AuthenticationProvider $ap | Out-Null

       + CategoryInfo          : InvalidArgument: (Microsoft.Share…PWebApplicat

      ion:SPCmdletNewSPWebApplication) [New-SPWebApplication], SPCmdletException

       + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWeb

      Application

  3. sanlaan says:

    Somewhere in step 2, under "Via sample script for PowerShell (Does not apply for Central Admin path)" you might want to mention that the user running the claimswa.ps1 command (whether it defaults to the logged in user or one specifies a user) should be a managed account. Probably obvious to you guys living in the SP 2010 world, but not so obvious to us getting familiar with it.

    That got the script to run and resolved my error from above.

    Thanks