Unable to update CM to R2 SP1

[mobit]

Hey all,

 

I've got a SCCM 2012 SP2 install that does not seem to be wanting to update to R2 SP1. It's already at SP2 and just needs the R2 upgrade, which from all the sources I've read is pretty much just a small <5mb msi that unlocks some features.

Following the guidance of a few blogs that details the upgrade I went ahead and grabbed the small iso from our volume licensing center that contains the Configmgr2012R2SP1.msi to upgrade this platform. I ran in to the "you must be a local administrator" issue and instead just ran the file from an elevated command prompt. It appeared to be successful at the end of this process, but after launching the CM console the about menu still indicated that we were on SP2. This condition persisted through a reboot and attempting to reinstall with the msi produced a message that we needed to have SP2 installed to do this.

I re-ran the msi with msiexec with verbose output to see where the issue was and it looks like it runs successfully as well. Yet, still not showing R2 in the about information, and the features that it should have enabled are still missing. Please see this pastebin link for the full upgrade log.

It's looking like I'm going to have to reinstall the entire primary CM site server to correct this, and I'm really not keen on that in what is an already-working production environment. I'd really appreciate any advice or assistance anyone can provide! Thanks!

[anyweb]

first thing first, check my post here http://www.windows-noob.com/forums/index.php?/topic/12852-how-can-i-upgrade-to-system-center-2012-r2-sp1-with-mdt-2013-update-1-integrated/and tell me did you follow it or possibly miss any points?

[mobit]

Thanks for the response anyweb.

 

When performing this upgrade the resources I was looking at gave me the indication that the only thing that was needed to upgrade from an SCCM 2012 SP2 environment was to run the appropriate package that would unlock the R2 features and the site would be at the 2012 R2 SP1 level. Clearly this wasn't the case, and going through the detailed list of steps you provided I was able to run in to a few errors that may hold clues as to what's going wrong with this installation. Both CU5 and CU1 failed to install.

 

CU5 errors out with the following when checking prerequisites:

Server update status: This update applies to product version 5.0.7958. The installed version on this computer is 5.0.8239.1000. This update is not applicable to this computer.


Console update status: No serviceable configuration manager role was found on the local system.

So it looks like the version I'm running is already above the version that CU5 wants to patch. So I moved along down the list on your page, uninstalled the ADK for Windows 8.1, installed the one for Windows 10, etc. and then tried to run CU1 - No prerequisite issues with the update compatibility, however it did throw an error when actually attempting to install the KB3074857 update and failed with the following text in the log:

<![LOG[    Preparing to launch installation for 'cm12_sp2r2sp1cu1-kb3074857-x64-enu.msi']LOG]!><time="15:20:45.792+480" date="12-08-2015" component="Configuration Manager Update Installer" context="" type="0" thread="3876" file="">
<![LOG[        MSI Properties: ' NODBUPGRADE="1" LAUNCHFROMBOOTSTRAP="1" SOURCEDIR="c:\c1891a52a5d3616ff0d9" REBOOT="ReallySuppress"']LOG]!><time="15:20:45.797+480" date="12-08-2015" component="Configuration Manager Update Installer" context="" type="0" thread="3876" file="">
<![LOG[        Installation Log file path: 'C:\Windows\TEMP\cm12_sp2r2sp1cu1-kb3074857-x64-enu.msi.log', verbosity level Verbose]LOG]!><time="15:20:45.803+480" date="12-08-2015" component="Configuration Manager Update Installer" context="" type="0" thread="3876" file="">
<![LOG[        Attended MSI install, setting UI verbosity to SourceResolutionOnly]LOG]!><time="15:20:45.810+480" date="12-08-2015" component="Configuration Manager Update Installer" context="" type="0" thread="3876" file="">
<![LOG[            Calling MSI to install 'cm12_sp2r2sp1cu1-kb3074857-x64-enu.msi' and waiting for results.]LOG]!><time="15:20:45.823+480" date="12-08-2015" component="Configuration Manager Update Installer" context="" type="0" thread="3876" file="">
<![LOG[        Installer launch attempt resulted in error. Error code: 1603]LOG]!><time="15:22:43.119+480" date="12-08-2015" component="Configuration Manager Update Installer" context="" type="0" thread="3876" file="">
<![LOG[        Installation completed with return code 1603]LOG]!><time="15:22:43.124+480" date="12-08-2015" component="Configuration Manager Update Installer" context="" type="0" thread="3876" file="">
<![LOG[    Task status detail added: failed
The following MSI installation failed.
MSI: cm12_sp2r2sp1cu1-kb3074857-x64-enu.msi
Exit code: 1603]LOG]!><time="15:22:43.130+480" date="12-08-2015" component="Configuration Manager Update Installer" context="" type="0" thread="3876" file="">
<![LOG[Task 'Install files for update KB3074857' completed, state is 'failed' LastStatus: Installing cm12_sp2r2sp1cu1-kb3074857-x64-enu.msi


failed
The following MSI installation failed.
MSI: cm12_sp2r2sp1cu1-kb3074857-x64-enu.msi
Exit code: 1603

And

[15:22:31] Start RunSQLScript
[15:22:31] Execute SQL statement: 
 execute spAddInstalledKB '3074857', 'XXXPRODSC01', 'XXX', 2, 'http://support.microsoft.com/KB/3074857''', 'English:00000409'


[15:22:31] Start RunSQLStatement
[15:22:31] Try to connect database : DRIVER={SQL Server};SERVER=XXXproddb02.XXX.com;Database=CM_XXX;Trusted_Connection=yes
MSI (s) (F8!30) [15:22:31:944]: PROPERTY CHANGE: Adding InstSMSValidSQLServer property. Its value is '1'.
[15:22:31] Update SQL database failed, retCode -1
[15:22:31] Running SQL Script failed with error code: 42000,Error Message: [Microsoft][ODBC SQL Server Driver][SQL Server]The EXECUTE permission was denied on the object 'spAddInstalledKB', database 'CM_XXX', schema 'dbo'.
[15:22:31] Exit SmsPatchAddInstalledPatch
Action ended 15:22:31: SmsPatchAddInstalledPatch. Return value 1.
MSI (s) (F8:50) [15:22:31:957]: Skipping action: SmsPatchRemoveInstalledPatch (condition is false)
MSI (s) (F8:50) [15:22:31:958]: Doing action: SmsProdPatchResetLangPack
MSI (s) (F8:50) [15:22:31:959]: Note: 1: 2205 2:  3: ActionText 
Action start 15:22:32: SmsProdPatchResetLangPack.
MSI (s) (F8:50) [15:22:32:046]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SmsProdPatchResetLangPack' 
MSI (s) (F8:D4) [15:22:32:049]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIA635.tmp, Entrypoint: SmsProdPatchResetLangPack
[15:22:32] SetupCore full path c:\Program Files\Microsoft Configuration Manager\bin\x64\setupcore.dll
CustomAction SmsProdPatchResetLangPack returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 15:22:42: SmsProdPatchResetLangPack. Return value 3.
Action ended 15:22:42: INSTALL. Return value 3.
Property(S): SmsGenerateFailureMIF = {A687702D-36B1-4278-98AA-BA511AD644D4}
CM12_SP2R2SP1CU1-KB3074857-X64-ENU.msi

As far as I am aware this is a fairly generic error message for an msi installer and Microsoft lists a few things to try in order to resolve it, including permissions to the system account, checking drive encryption and some other suggestions. The second log file for the MSI itself had a more telling story in my mind. The error message for the log of the MSI file gives me the indication that the problem was with SQL which did throw a warning during the prerequisites - I found this interesting because I'd indicated to the installer that I would manually update the database because of the warning during the prereq check that it generated when trying to connect to it.

Update: As it happens, I just ran the CU1 again and it completed without any errors this time. I rebooted the computer but was then unable to open the CM console because - looks like it's having an issue connecting to the site database. I'll go through the manual site database update procedure tomorrow and see if that resolves the problem I'm now seeing. In the meantime if you have any other suggestions for me, I'm all ears! Thanks!

Edited December 9, 2015 by mobit

[mobit]

I attempted the manual site database upgrade procedure and followed Microsoft's instructions on the topic.

 

I was able to execute the query against the database, which completed with errors.

 

<<removed many lines showing numbers of affected rows>>


(1 row(s) affected)


(1 row(s) affected)
Msg 103, Level 15, State 4, Line 48
The identifier that starts with '[SMS_ROOT]\bin\x64\CryptoUtility.dll'
    WITH PERMISSION_SET = UNSAFE'


--
-- Name         : fnReadMDMPolicyCertValidationD' is too long. Maximum length is 128.
Msg 102, Level 15, State 1, Line 49
Incorrect syntax near '[SMS_ROOT]\bin\x64\CryptoUtility.dll'
    WITH PERMISSION_SET = UNSAFE'


--
-- Name         : fnReadMDMPolicyCertValidationD'.
Msg 319, Level 15, State 1, Line 63
Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
Msg 156, Level 15, State 1, Line 64
Incorrect syntax near the keyword 'AS'.
Msg 111, Level 15, State 1, Line 76
'CREATE FUNCTION' must be the first statement in a query batch.
Msg 111, Level 15, State 1, Line 88
'CREATE FUNCTION' must be the first statement in a query batch.
Msg 102, Level 15, State 1, Line 138
Incorrect syntax near '


SET @UPDATESTATEMENT2 =
  '.
Msg 102, Level 15, State 1, Line 141
Incorrect syntax near '


SET @UPDATESTATEMENT3 = '.
Msg 111, Level 15, State 1, Line 144
'ALTER FUNCTION' must be the first statement in a query batch.
Msg 137, Level 15, State 2, Line 169
Must declare the scalar variable "@AllowFallback".
Msg 137, Level 15, State 2, Line 173
Must declare the scalar variable "@PackageID".
Msg 102, Level 15, State 1, Line 180
Incorrect syntax near 'legacy'.
Msg 102, Level 15, State 1, Line 184
Incorrect syntax near 'content'.
Msg 102, Level 15, State 1, Line 188
Incorrect syntax near 'legacy'.
Msg 137, Level 15, State 2, Line 190
Must declare the scalar variable "@PackageID".
Msg 102, Level 15, State 1, Line 194
Incorrect syntax near ''.
Msg 1038, Level 15, State 4, Line 195
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
Msg 137, Level 15, State 2, Line 208
Must declare the scalar variable "@PackageID".
Msg 1038, Level 15, State 4, Line 212
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
Msg 1038, Level 15, State 4, Line 213
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
Msg 156, Level 15, State 1, Line 228
Incorrect syntax near the keyword 'WHERE'.
Msg 178, Level 15, State 1, Line 235
A RETURN statement with a return value cannot be used in this context.
Msg 102, Level 15, State 1, Line 263
Incorrect syntax near '


SET @UPDATESTATEMENT2 =
  '.
Msg 102, Level 15, State 1, Line 266
Incorrect syntax near '
  
SET @UPDATESTATEMENT3 = '.
Msg 102, Level 15, State 1, Line 269
Incorrect syntax near '7'.
Msg 102, Level 15, State 1, Line 272
Incorrect syntax near '<'.
Msg 103, Level 15, State 4, Line 272
The identifier that starts with 'CDATA[SELECT * FROM Win32_OperatingSystem WHERE Version like ''''7%'''' AND OSType=36 AND Caption like ''''%Debian GNU/Linux 7%'' is too long. Maximum length is 128.
Msg 105, Level 15, State 1, Line 272
Unclosed quotation mark after the character string 'CDATA[SELECT * FROM Win32_OperatingSystem WHERE Version like ''''7%'''' AND OSType=36 AND Caption like ''''%Debian GNU/Linux 7%'''.

This doesn't leave me with a good feeling, and sure enough the Configuration Manager Console still cannot connect to the site. I re-run consolesetup.exe to see if this will help with the issue. It does not.

 

The Configuration Manager properties all indicate that the client is at 5.00.8239.1000 as are all the components. I'm not sure what to do next and feel that I'm far enough off track where I'm better off restoring from backup on both the Site and the DB server.

 

I didn't build out this SCCM site and don't have a ton of experience with it so I'm not overly optimistic about tearing it down and rebuilding it from the ground up. Still I'm not opposed to doing it to get things running smoothly and it would be a good learning opportunity, but I don't know what impact this will have with our systems as it is, as both WSUS and Endpoint Protection are currently integrated into our environment through SCCM. That's a big concern to me.

 

Thoughts anyone? Could really use some advice here. Thanks.

 

Edit - I have a backup of the DB, but not of the site server itself.

Edited December 9, 2015 by mobit

[anyweb]

first things first you cant upgrade from cu5 now because you've already upgraded to SP1 (or sp2 depending on how you look at it)

 

as regards your console not connecting, have you tried installing the console directly from the sp1 media ? would you like me to do a teamviewer session to your computer to have a look ?

[mobit]

first things first you cant upgrade from cu5 now because you've already upgraded to SP1 (or sp2 depending on how you look at it)

 

as regards your console not connecting, have you tried installing the console directly from the sp1 media ? would you like me to do a teamviewer session to your computer to have a look ?

 

Thanks again for the response. I will try reinstalling the console from the media as you've suggested and if you'd like to take a look at it I can probably arrange a time for that. We installed from the SC2012 SP2 media, so as far as I am aware the CU5 wasn't necessary anyway?

 

As I previously mentioned, while I don't have a lot of experience with SCCM and have never set it up before, I feel that my best opportunity to learn about it would be to reinstall the site server at the very least. My only worry is the current integration of WSUS and Endpoint Security in to the current environment and maintaining this through a reinstall.

 

I will also try to set up an SCCM installation in my home lab environment, hopefully that will get me more familiar with the things that are going on here as well.

 

I'll get back with you and let you know after I've tried.

[mobit]

The issue still exists after reinstalling the console from our installation media. Given that I am not sure what the health of the site is right now I am not sure how much good will come from troubleshooting the manager console connection.