Issue with 2012 and 2014

[JasonCarter80]

js_0505[CodePlex]
I keep getting this error when I try to install SQL 2012 or SQL 2014 The specified value for setting 'PID' is invalid. The expected value type is SqlSecureString.

[JasonCarter80]

sarasotasql[CodePlex]
The option name was changed in SQL 2012 to support the new method of streamlining updates into the install. Did you copy the 2008R2 template to create the templates for 2012 and 2014? There should have been a 2012 template in the download package that
reflects the change and can be copied to also create a 2014 template.

[JasonCarter80]

js_0505[CodePlex]
Thank you! Okay got through that, I had to uncomment the key info in Run-Install.ps1 as well
Validate Product Key
$key = $editions.Key
if ($key -eq $null -or $key -eq )
{
#Handle the fact that eval editions don't use keys
if ($sqlEdition -ne Evaluation)
{
throw There is no matching product key in the configuration file for $sqlVersion - $sqlEdition edtion
}
}
else
{
if (!$Parameters.ContainsKey(ProductKey))
{
$Parameters.Add(ProductKey, $key)
}
}
and now I have this issue: you specified for PCUSOURCE does not exist. PCUSOURCE
should no longer be used; use UpdateSource instead. If PCUSOURCE must be used, supply a valid path.

[JasonCarter80]

sarasotasql[CodePlex]
The DefaultSetup.config is not being used. SPADE copies the appropriate template and then replaces certain values with the Run-Install.config and/or the template overrides passed into the Run-Install.ps1. You need to manually copy the PID value from the
DefaultSetup.config to the Edition/Key attribute in the Run-Install.config file. This only needs to be done when you add a new Edition/Version combination to the Run-Install.config file.

[JasonCarter80]

js_0505[CodePlex]
I did notice that the DefaultSetup.config files are different between 2008 and 2012:
2012
;SQL Server 2012 Configuration File
[OPTIONS]
PCUSOURCE=.\PCUSOURCE
PID=PopulatedwithKey

2008
;SQLSERVER2008 Configuration File
[SQLSERVER2008]
PID=PopulatedwithKey
PCUSOURCE=.\SP

[JasonCarter80]

js_0505[CodePlex]
Standard, it does not seem to be either a getting the Key from the default.config or it is not encrypting it. I cannot pull it from the Run-Install.ps1

[JasonCarter80]

sarasotasql[CodePlex]
Can you validate that the Edition\Key attribute in the Run-Install.config file is configured for the Edition and Version combination that you are trying to install? This field can only be left blank if you are installing an Evaluation edition of SQL Server.