The AutoSPInstaller script works fine until it goes to create the content database...PowerShell errors out and says:
'New-SPConfigurationDatabase : This content database requires upgrade and could not be attached in this operation. Use either the [stsadm -o addcontentdb] command or [Mount-SPContentDatabase] cmdlet instead.'
The name of my configuration database is: SharePoint_Config
I am logged onto my SharePoint app server as the farm account, which is a local administrator. The account name is: sp_farm
Firewalls turned off. I can see the database actually getting created on the SQL side, but the script still errors out. I made sure to drop the database each time and make sure its fully gone from the SQL server as well.
Comments: ** Comment from web user: brianlala **
'New-SPConfigurationDatabase : This content database requires upgrade and could not be attached in this operation. Use either the [stsadm -o addcontentdb] command or [Mount-SPContentDatabase] cmdlet instead.'
The name of my configuration database is: SharePoint_Config
I am logged onto my SharePoint app server as the farm account, which is a local administrator. The account name is: sp_farm
Firewalls turned off. I can see the database actually getting created on the SQL side, but the script still errors out. I made sure to drop the database each time and make sure its fully gone from the SQL server as well.
Comments: ** Comment from web user: brianlala **
Not that it has any bearing on it, but you shouldn't be logged in with the farm account, nor should it be a local admin. Instead, use a dedicated install account w/ local admin rights.
More detail on this issue is probably available in the local ULS/setup log. Really strange though, I'm not sure why it would be stating that a brand new DB requires upgrade and could not be attached. Is there any chance it's hitting a different SQL server? Or that an issue occurred installing binaries or CUs earlier in the script?
Brian