RemoteInstall Errors at Site Collection Creation

Mar 1, 2013 at 12:48 AM
Edited Mar 1, 2013 at 12:52 AM
Brian,

You mentioned in an earlier post in another thread that web apps are provisioned to farms not servers. This makes perfect sense, yet in my executing the AutoSPInstaller process on multiple (3) servers using the RemoteInstall Enable="true" option I am having trouble finishing without error. I start the process on the app server and everything completes fine without errors then the remote install occurs and the both front ends run fine until they get to the 1st site collection creation of the first web application then the script halts with the "another site already exists at http://..." which if the PS script is actually trying to create another SC with the same URL - it makes sense that it should barf. But why doesn't it just join the farm after all the prereq's and binaries are installed?

Here's the snippet of the log file where the error occurs:
  • Creating local profile for XXXXXX\SPFarm2MySitesApPl...Done.
  • Managed account XXXXXX\SPFarm2MySitesApPl already exists.
  • Creating local profile for XXXXXX\SPFarm2SPSearch...Done.
  • Managed account XXXXXX\SPFarm2SPSearch already exists.
  • Done Adding Managed Accounts
  • Creating web applications...
    • Web app "SPFarm2_TestSites1Host_Default" already provisioned.

- Creating Site Collection "http://TestSites1/"...

  • Script halted!
Exception : System.ArgumentException: Another site already exists a
                    t http://testsites1. Delete this site before attempting
                     to create a new site with the same URL, choose a new U
                    RL, or create a new inclusion at the path you originall
                    y specified. ---> Microsoft.SharePoint.SPException: Ano
                    ther site already exists at http://testsites1. Delete t
                    his site before attempting to create a new site with th
                    e same URL, choose a new URL, or create a new inclusion
                     at the path you originally specified.
Mar 5, 2013 at 6:31 PM
SteveP12345 wrote:
...But why doesn't it just join the farm after all the prereq's and binaries are installed?

Anyone have any ideas?
May 11, 2013 at 12:21 PM
I was having the same issue, the script strangely worked on one farm but not on a different farm setup. Different accounts and Web App and sites. Had a close look through each script and in particular the site collections and found out why it kept bombing out on the second farm config.

When creating the site collection DO NOT put a slash at the end of the url. Make the same as the Web App.

Web App url = http://mywebapp.com

Site Collection name = http://mywebapp.com

This resolved this issue for me :-)
May 23, 2013 at 11:55 PM
sadey2k - Thanks!

No slash at the end of the URL solved the problem for me as well. I also just recently saw someone else mention it too in another thread.
May 24, 2013 at 12:33 AM
It should have no slash at the end nor a "colon followed by a port number unless is not default" in the siteUrl Property.