June 23, 2015 at 4:33 am
Hi all,
I'm trying to do an unattended upgrade of 2014 RTM to 2014 SP1.
It's my first attempt at an upgrade configuration file, and its failing with missing registry entry for database engine service and replication service.
Error in summary.txt is:
The registry key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER2495\Setup is missing
That's a valid error, as the registry only has an entry for:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\Setup
Am I missing something obvious here, or how can this be resolved?
June 23, 2015 at 8:50 am
Is this a default instance?
June 23, 2015 at 10:01 am
Yes there is only a default instance on the server.
Box was SQL 2008 R2 which was updated recently to SQL 2012 successfully.
There appears to only be the one instance entry in the registry also - MSSQL12.MSSQLSERVER
If added the config file that I used as well. The files on the install media has been copied to the local server, and the Sp1 is located at the 'updatesource' location.
June 23, 2015 at 10:38 am
That's strange. There's no reason there should be a 2495 in that key. I haven't seen it. Have you tried it more than once?
June 23, 2015 at 2:24 pm
It could be a problem with your configuration file. For going from SQL Server 2014 RTM to SP1 the ACTION should be PATCH. You have UPGRADE. That is for upgrading major versions, not minor ones.
Joie Andrew
"Since 1982"
June 24, 2015 at 2:25 am
Good call Joie.
The PATCH option isn't that well documented. It isn't on the main MS page I hit for doing unattended installs.
However tried with ACTION=Patch, and it gets stranger
Errors out with:
The specified value 'Patch' is invalid. To run in unattended mode, you must specify a valid ACTION. The valid values for ACTION are: ' None RemovePatch Uninstall Install Upgrade Patch Repair LandingPage ClusterReport RunRules PrepareFailoverCluster CompleteFailoverCluster InstallFailoverCluster RemoveNode AddNode EditionUpgrade Bootstrap ComponentUpdate Help RebuildDatabase RunDiscovery PrepareImage CompleteImage ConfigureImage'
So my Patch isn't valid, but I should pick Patch as an action. Stumped on this 🙂
I tried this with the Action in the configuration file:
ACTION='Patch'
and also in the CMD:
D:\SQL Server 2014Media\setup.exe /ConfigurationFile=c:\temp\SQL2014Unattended_ConfigurationFileUpgrade.ini /ACTION=Patch
June 24, 2015 at 2:51 am
Try doing it without the configuration file. Something like:
<SQLServer2014SP1> /IACCEPTSQLSERVERLICENCETERMS=True /ACTION=PATCH /QS /ALLINSTANCES
Where <SQLServer2014SP1> is the SQL Server 2014 service pack.
Just so I am clear: are you trying to patch an existing SQL Server 2014 installation from RTM to SP1 or are you trying to do a new install with SP1 slipstreamed in?
Joie Andrew
"Since 1982"
June 24, 2015 at 4:11 am
It's a patch from 2012 RTM to SP1
June 24, 2015 at 4:36 am
Making progress running directly off the SP:
D:\SQLServer2014SP1-KB3058865-x64-ENU.exe /IACCEPTSQLSERVERLICENSETERMS=True /ACTION=PATCH /QS /ALLINSTANCES
Unfortunately can't complete the operation as SQL needs a reboot. That will have to wait til later in the day. Will try later and update the post.
I had hoped to have a series of configuration files for unattended installs (e.g. base 2014 RTM install, slipstream install of service packs and cumulative updates, and patch of service pack).
It appears from this issue that doing a service pack patch is not possible from a configuration file?
June 24, 2015 at 4:58 am
I had hoped to have a series of configuration files for unattended installs (e.g. base 2014 RTM install, slipstream install of service packs and cumulative updates, and patch of service pack).
It appears from this issue that doing a service pack patch is not possible from a configuration file?
This is absolutely possible. Slipstreaming is different than what you are doing now though. You are installing SQL Server 2014 RTM and then installing SP1. Slipstreaming does this in one install session, so after the install is done all updates identified are already applied without the need for additional installs.
For some reason I am having trouble finding the Books Online article at work. I found this one which will walk you through the process though:
Slipstreaming SQL Server 2012 and 2014[/url]
Joie Andrew
"Since 1982"
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply